cockroachdb / cockroachdb/helm-charts
How to rotate Kubernetes signed certificates for those generated as part of the chart
Open
- Dominant language
- Go
- Stars
- 105
- Forks
- 152
- Avg merge
- 4d 23h
- Merged PRs (30d)
- 5
Description
As part of the cockroachdb bootstrapping, CSRs are created for the cluster in order to enable TLS communications for the cluster itself. These certificates are signed by the Kubernetes CA, but they are only valid for 1 year, after which they will need to get replaced. What is the recommended approach / is there guidance on this through deployments installed via the Helm chart ?
Jira issue: HELM-36
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.