-
Notifications
You must be signed in to change notification settings - Fork 7.9k
fix: adding the kube ca cert to the truststores #25586
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
|
@ahus1 the project_name convention is not currently used in the release notes, you may want to create an issue to replace all of those references. |
Thank you for pointing this out. I'm skipping it for now as we don't use the content directly for RHBK release notes, as RHBK release notes are created manually by using copy-and-past and re-arranging of contents. It will helps if the content you are copying contains the attributes. Once someone from the cloud native team approves it, I'm happy to merge it. |
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.
@shawkins Thanks, LGTM.
It's necessary to rebase and squash commits to pass the DCO check and WebAuthn job.
closes keycloak#10794 Signed-off-by: Steve Hawkins <[email protected]>
Co-authored-by: Alexander Schwartz <[email protected]>
Following the last suggestion by @stianst I'm just setting the DCO as passing and enabled auto-merge with a squashed message that includes the sign-off from the initial commit. |
Unreported flaky test detectedIf the below flaky tests below are affected by the changes, please review and update the changes accordingly. Otherwise, a maintainer should report the flaky tests prior to merging the PR. org.keycloak.testsuite.x509.X509BrowserCRLTest#loginFailedWithIntermediateRevocationListFromFileKeycloak CI - FIPS IT (non-strict) org.keycloak.testsuite.x509.X509BrowserCRLTest#loginFailedWithIntermediateRevocationListFromFileKeycloak CI - FIPS IT (strict) |
ghost
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.
Unreported flaky test detected, please review
ahus1
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.
Approving as of @mabartos's review.
The only issue here is that we're not monitoring the file, so a rotation will require a manual restart of the keycloak instances. We could have the operator watch the kube-root-ca.crt configmap and restart the keycloaks.
closes #10794