Coder's OIDC init was crashlooping with x509: certificate signed by unknown authority against auth.renner.uno, because every ingress uses letsencrypt-staging.
Mount staging roots (Pretend Pear X1 + Bogus Broccoli X2) via coder.certs.secrets; Go picks them up from /etc/ssl/certs/.
Remove once the cluster moves to letsencrypt-prod.
Test plan
Coder pod starts past OIDC init (no more x509 error in logs)
## Summary
- Coder's OIDC init was crashlooping with `x509: certificate signed by unknown authority` against `auth.renner.uno`, because every ingress uses `letsencrypt-staging`.
- Mount staging roots (Pretend Pear X1 + Bogus Broccoli X2) via `coder.certs.secrets`; Go picks them up from `/etc/ssl/certs/`.
- Remove once the cluster moves to `letsencrypt-prod`.
## Test plan
- [ ] Coder pod starts past OIDC init (no more x509 error in logs)
- [ ] OIDC login against Authentik succeeds
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Coder's OIDC init was crashlooping with "x509: certificate signed by
unknown authority" when fetching auth.renner.uno's OpenID discovery
document, because every ingress in this cluster uses the
letsencrypt-staging ClusterIssuer today.
Mount the staging roots (Pretend Pear X1 + Bogus Broccoli X2) via
coder.certs.secrets; the chart drops them at /etc/ssl/certs/ where
Go's crypto/x509 picks them up on Linux.
Remove once the cluster migrates to letsencrypt-prod.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
x509: certificate signed by unknown authorityagainstauth.renner.uno, because every ingress usesletsencrypt-staging.coder.certs.secrets; Go picks them up from/etc/ssl/certs/.letsencrypt-prod.Test plan
🤖 Generated with Claude Code