-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Correct the steps for redeploying router certificates #13941
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
|
Hi @bysnupy. Thanks for your PR. I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/ok-to-test |
|
@stuartchuan - can you PTAL? @huffmanca - FYI. If QE passes it, we should be ok to merge and CP. |
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.
... can be triggered to be recreated by removing annotations to the router service, deleting the secret and re-adding annotations to the router service, I think the secret should be deleted after removing the annotation, otherwise it will be recreated immediately.
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.
Line 708: service.alpha.openshift.io/serving-cert-signed-by- this annotation should not be removed.
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.
others LGTM, thanks
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.
Thank you for your review and kind correction @lihongan,
You're right. I changed the sequence of the steps as you mentioned. (removing secret step is after removing annotation step)
And I think it had better to remove service.alpha.openshift.io/serving-cert-signed-by annotation at same time. The annotation also added automatically with the current OpenShift CA signer value, when it is added service.alpha.openshift.io/serving-cert-secret-name again. For example, if new CA is deployed before the router certs deploying work, it can cause not matching CA issue with new CA, because the service.alpha.openshift.io/serving-cert-signed-by's value is old or different with new CA signer value.
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.
That make sense. Thank you @bysnupy
|
/lgtm |
|
/assign vikram-redhat |
|
@stuartchuan - can you confirm if this is ok from QE's point of view? |
|
@vikram-redhat , |
|
Thanks @stuartchuan! @huffmanca - can you please do a peer review and followup if needed? |
|
Could you PTAL @lihongan ? "redeploy-router-certificates.yml" makes changes to wrong "service serving certificate secrets" annotation status has already been changed to |
huffmanca
left a comment
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.
I sincerely apologize for the delays in submitting this review. Overall it looks good, just need to tweak two lines so that the numbering isn't broken from the text.
Once these changes are made I will merge and cherry-pick.
"router-metrics-tls" secret should be service serving certificates secret. "router-certs" secret is using as wild card certificates and not service serving certificates secret. - Fix: https://bugzilla.redhat.com/show_bug.cgi?id=1672011
|
@huffmanca I've complete to fix it as mentioned from you. Could you PTAL again ? |
|
Thanks for making these changes. It looks good to me! |
|
/cherrypick enterprise-3.11 |
|
/cherrypick enterprise-3.10 |
|
@huffmanca: new pull request created: #14419 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/cherrypick enterprise-3.9 |
|
@huffmanca: new pull request created: #14420 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
@huffmanca: new pull request created: #14421 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/cherrypick enterprise-3.7 |
|
@huffmanca: new pull request created: #14422 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/cherrypick enterprise-3.6 |
|
/cherrypick enterprise-3.5 |
|
@huffmanca: new pull request created: #14423 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/cherrypick enterprise-3.4 |
|
@huffmanca: #13941 failed to apply on top of branch "enterprise-3.5": DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/cherrypick enterprise-3.3 |
|
@huffmanca: #13941 failed to apply on top of branch "enterprise-3.4": DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
@huffmanca: #13941 failed to apply on top of branch "enterprise-3.3": DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Fix: "redeploy-router-certificates.yml" makes changes to wrong "service serving certificate secrets" annotation
Version:
v3.3~v3.11Description:
If your
routerinstalled initially withrouter-metrics-tlsannotation in therouter Service,router-metrics-tls secretshould beservice serving certificates secret. In contrast,router-certs secretis using aswild card certificatesand notservice serving certificates secret.