kelos-dev / kelos-dev/kelos

Remove temporary Session server cleanup after the Console rollout

Open
#1,671 0 comments 0 reactions 1 assignee View on GitHub

@gjkim42 is already working on this.

Since Aug 20, 2026.

needs-actor needs-kind needs-priority triage-accepted
Dominant language
Go
Stars
331
Forks
40
Avg merge
1d 21h
Merged PRs (30d)
70

Description

Follow-up to #1670.

PR #1670 replaces the Session server with the Kelos Console. The dev deployment uses kelos install, whose server-side apply does not prune renamed resources, so .github/workflows/deploy-dev.yaml temporarily deletes the former Session server resources before installing the Console.

Keep this migration block through the first successful dev deployment of the Console.

Completion criteria

  • Merge and deploy #1670 with the KELOS_CONSOLE_TOKEN repository secret configured.
  • Confirm deployment/kelos-console-server becomes Available and its Service is reachable.
  • Confirm the legacy Session server Deployment, Service, ServiceAccount, Secret, ClusterRole, and ClusterRoleBinding no longer exist.
  • Remove the temporary kubectl delete commands and FIXME from .github/workflows/deploy-dev.yaml.
  • Verify the follow-up PR with the normal workflow checks.

Scope

Only remove the one-time dev-cluster migration block. Keep the legacy RBAC deletion in kelos uninstall; it remains necessary for user clusters upgraded from older releases.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.