Repository navigation
ci: deploy releases to the K3s cluster - #1
Merged
Merged
Conversation
Plane moved from docker compose on 207.57.124.102 to the K3s cluster (namespace plane, database "plane" in the shared CloudNativePG cluster pg-main). The deploy job no longer uses sshpass and deploy.sh: - add deployments/k3s/plane.yaml (the manifests running in the cluster, with __DOCKER_USERNAME__/__VERSION__ placeholders), migrator-job.yaml and backup-job.yaml - deploy job: pg_dump into PVC plane-predeploy-backups, run the migrator Job, apply the manifests, wait for every Deployment and roll the application Deployments back if any of them fails, then check the public URL - prepare job validates KUBE_CONFIG instead of SERVER_IP/USER/PWD - needs repository secret KUBE_CONFIG (ServiceAccount plane/ci-deployer) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Production moved from Docker on 207.57.124.102 to the K3s cluster (
k3s.seasonschange.cn) on 2026-11-11. The service is already running there; this PR only changes how releases reach it.Changes
deployments/k3s/plane.yaml, the manifests running in the cluster, with__DOCKER_USERNAME__/__VERSION__placeholders. Also addsmigrator-job.yamlandbackup-job.yamldeployjob:pg_dumpinto PVCplane-predeploy-backups(last 5 kept)rollout undoon all application Deployments; migrations are not reversedhttps://plane.tmlab.toppreparejob validatesKUBE_CONFIGinstead ofSERVER_IP/USER/PWD.promoteis unchangedVerification
kubectl diffagainst the running cluster shows no changes other than the new backup PVCv1.2.9-hotfix.6. Everything succeeded and no pod was restartedSecrets
KUBE_CONFIGis set: a kubeconfig for ServiceAccountplane/ci-deployerSERVER_*are now used only by the manual Deployment Preflight workflow, which still targets the old Docker host🤖 Generated with Claude Code