Files
cozystack/packages
Ivan Okhotnikov 73c73df9ee docs(vertical-pod-autoscaler): clean up dangling references to the retired migrator/rollout hooks
Self-review after the tls-migrator removal caught a stale comment in
certificate.yaml still promising that a pre-upgrade hook would strip
Helm/Flux ownership so cert-manager could adopt the legacy Secret in
place. That hook no longer exists and — as kvaps' review pointed out
— could not have done what it claimed anyway: \`Secret.type\` is
immutable, so cert-manager cannot rewrite an Opaque Secret in place
into a \`kubernetes.io/tls\` one.

Rewrite the certificate.yaml secretName comment to describe the
actual migration path: Helm garbage-collects the legacy Opaque
Secret from the release manifest, cert-manager immediately writes a
fresh \`kubernetes.io/tls\` Secret of the same name via this
Certificate, and the same-upgrade rollout — driven by the fresh
\`checksum/tls-cert\` annotation — brings up a pod that re-registers
\`vpa-webhook-config\` with the new caBundle before the delete/
create window on the MWC matters (given failurePolicy: Ignore).

Also refresh patches/cert-manager-admission-tls.diff to reflect the
comment edit and re-verify end-to-end that
\`rm -rf charts && helm pull && patch\` produces a byte-identical
tree to what git tracks. 15/15 helm-unittest cases still pass.

Signed-off-by: Ivan Okhotnikov <ivan.okhotnikov@aenix.io>
2026-07-02 19:00:49 +03:00
..