Skip to content

fix(konk-service): rollout restart dependent deployments on cert rotation#623

Open
rsatal wants to merge 1 commit into
mainfrom
fix/cert-rotation-rollout-restart
Open

fix(konk-service): rollout restart dependent deployments on cert rotation#623
rsatal wants to merge 1 commit into
mainfrom
fix/cert-rotation-rollout-restart

Conversation

@rsatal

@rsatal rsatal commented May 19, 2026

Copy link
Copy Markdown
Contributor

When reconcile-kubeconfig detects that cert-manager has rotated the kubeconfig certificate (certSum != lastCertSum), it now:

  1. Lists all deployments in the namespace
  2. Finds those that mount the kubeconfig secret as a volume
  3. Patches their pod template with a konk.infoblox.com/cert-checksum annotation to trigger a rolling restart

This ensures consumer pods (e.g. tagging-aggregate-api) pick up the renewed TLS certificate instead of holding an expired one in memory, which previously caused Unauthorized errors and 503s after 12 hours.

RBAC: added 'list' and 'patch' verbs for deployments (was only 'get').

…tion

When reconcile-kubeconfig detects that cert-manager has rotated the
kubeconfig certificate (certSum != lastCertSum), it now:

1. Lists all deployments in the namespace
2. Finds those that mount the kubeconfig secret as a volume
3. Patches their pod template with a konk.infoblox.com/cert-checksum
   annotation to trigger a rolling restart

This ensures consumer pods (e.g. tagging-aggregate-api) pick up the
renewed TLS certificate instead of holding an expired one in memory,
which previously caused Unauthorized errors and 503s after 12 hours.

RBAC: added 'list' and 'patch' verbs for deployments (was only 'get').
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant