C1: clean up cv + docs minikube artifacts #343
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "cleanup-cv-docs-minikube-artifacts"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Follow-up to #342. The cv and docs services are now live on indri (Caddy file_server backed by ansible-managed tarball extraction) and verified working. This PR removes the dead minikube artifacts and the tooling shims that referenced them.
Changes
Deletions:
argocd/apps/{cv,docs}.yamlargocd/manifests/{cv,docs}/(deployment, service, ingress, pdb, kustomization)containers/{cv,quartz}/(Dockerfiles + start scripts)Tooling:
mise-tasks/container-version-check: remove thequartz→docsCONTAINER_TO_SERVICE mapping (containers/quartz no longer exists)service-versions.yaml: bumpdocs.current-versiontov1.16.0(the blumeops docs release tag) and trim the migration-window commentLive state context
The argocd Applications
cvanddocswere already deleted from the cluster manually as part of the cutover; this PR just removes the YAML files that theappsapp-of-apps was still ingesting. After merge,argocd app sync appswill reconcile and theappsApplication returns to Synced.The Caddyfile
handle_errorsbug that briefly crashed all*.ops.eblu.meservices during cutover is fixed in a separate C0 (2ee53fe) on main, not here.Test plan
mise run container-version-check --all-filescleanmise run service-review --type ansibleshows cv at 1.0.3, docs at v1.16.0argocd app sync appsreturns clean (cv/docs entries gone, no children to reconcile)🤖 Generated with Claude Code