Repository navigation
fix(k8s): restore prod TLS through CI/CD - #105
Merged
Merged
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
rhanka
force-pushed
the
fix/prod-tls-renewal-cicd
branch
from
September 13, 2026 15:12
2f0c3b9 to
d50d8e2
Compare
rhanka
force-pushed
the
fix/prod-tls-renewal-cicd
branch
from
September 13, 2026 15:14
d50d8e2 to
7713531
Compare
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.
deces.matchid.iocurrently serves a certificate that expired on 2026-09-07. cert-manager has been retrying since 2026-08-08, butmatchid-produses all 10 allowed Secrets and issuance needs a temporary private-key Secret.The infrastructure quota fix is merged in
rhanka/k8s-ops#61(ad7fc7de0fb4a75fbb2111b1f0056bb3a889adc5). This PR adds the explicit CI/CD promotion path requested for the incident: a manual workflow, restricted tomainand the protectedproductionenvironment, loads its dedicated platform kubeconfig, fails closed unless it can patch ResourceQuota, and verifies that Kubernetes, the expected Traefik load balancer and public DNS all identify the same production cluster. It applies only the merged Secret ceiling of 16, waits for certificate revision 2 with the correct hostname and at least seven days of remaining validity, and then performs a strict public HTTPS readiness check.It also hardens future production releases: the certificate gate now validates the actual PEM stored in
matchid-prod-tls. cert-manager leftReady=Truestale after expiry, so the previous condition-only wait could report success for an expired certificate.Validation:
bash -non all 30 shell blocks in both workflowsgit diff --checkNo Kubernetes Secret value is printed or changed by this workflow. The former repo-wide platform kubeconfig secret has been replaced with
KUBE_CONFIG_DATA_PLATFORMin the protectedproductionenvironment. No workload, PVC, or application data is modified.