-
Couldn't load subscription status.
- Fork 935
Switch to ManagedCertificate for Triage-Party. #1942
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
GKE cluster and meet the requirement to use the GA version of /hold |
Use a Google-managed SSL certificate through `ManagedCertificate` for Triage-Party. Signed-off-by: Arnaud Meukam <ameukam@gmail.com>
210d2b4 to
44d2d1b
Compare
|
/assign @cpanato |
|
/hold cancel |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgmt
/hold to wait when @ameukam is ready to deploy
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ameukam, cpanato The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/hold cancel |
|
Ingress is configured with a new TLS certificate provided by Google : openssl s_client -showcerts -connect release.triage.k8s.io:443
CONNECTED(00000003)
depth=2 C = US, O = Google Trust Services LLC, CN = GTS Root R1
verify return:1
depth=1 C = US, O = Google Trust Services LLC, CN = GTS CA 1D4
verify return:1
depth=0 CN = release.triage.k8s.io
verify return:1https://www.ssllabs.com/ssltest/analyze.html?d=release.triage.k8s.io |
|
The old certificate is removed : kubectl delete certificate release-triage-k8s-io -n triageparty-release
certificate.cert-manager.io "release-triage-k8s-io" deleted |
Use a Google-managed SSL certificate through
ManagedCertificatefor Triage-Party.
Signed-off-by: Arnaud Meukam ameukam@gmail.com