Open ameukam opened 3 years ago
I opened #1942 for Triage-Party
Things I noticed when I deployed #1942 :
ManagedCertificate
is activeSSL_ERROR_NO_CYPHER_OVERLAP
TLS errorCurrent default quota for the SSL certificates: https://console.cloud.google.com/iam-admin/quotas?service=compute.googleapis.com&metric=%22SSL%20certificates%22
https://cloud.google.com/load-balancing/docs/quotas#ssl_certificates.
/assign @thockin @spiffxp @ameukam
/priority important-soon
sippy is the only old-style cert remaining, except for the self-signed we use in k8s-io-canary (which maybe can just go away?)
We could shut down cert-manager, create self-signed cert manually, apply to canary ingress... but problem is every time we add a new domain to the canary domain, we need to regenerate the certificate again.
Other option is to see if we can cover in ManagedCertificate, maybe be complications, not clear how managed certificate controller works.
/milestone v1.23
/milestone v1.24
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale /lifecycle frozen
/priority important-longterm
/milestone clear
/milestone v1.32
Initial conversation : https://groups.google.com/g/kubernetes-wg-k8s-infra/c/MseI6bUqOfY.
/area cluster-mgmt
EDIT(spiffxp):
FYI @munnerz @rikatz I think we're doing this now? I'm not entirely sure what's tipped us over the edge, other than we're getting cert expiry warnings yet again.
This would obviate work in progress to improve cert-manager:
And obviate the following issues:
Services on
aaa
that need to be converted: