-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Bug 1712525, Configuring a custom PKI #18207
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
|
The preview will be available shortly at: |
|
Configuring a custom PKI assembly build: http://file.rdu.redhat.com/~choag/112019/ingress-cert/networking/configuring-a-custom-pki.html |
|
@danehans can you review the new docs I've created on Configuring a custom PKI? |
6a3bd25 to
d24ba39
Compare
|
/lgtm |
|
@lihongan can you review this content? Thanks! |
|
LGTM, thank you! |
d24ba39 to
9691ded
Compare
|
New changes are detected. LGTM label has been removed. |
|
@bergerhoffer can you review to ensure I followed all the rules? 🙂 This is a reorg of #18004. Thanks! |
bergerhoffer
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.
Just a few suggestions to consider!
9691ded to
1fdd604
Compare
|
/cherrypick enterprise-4.2 |
|
@codyhoag: new pull request created: #18285 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-4.3 |
|
@codyhoag: new pull request created: #18286 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. |
…onfig Reciprocating the builds -> proxy link from 1fdd604 (New assembly for configuring custom pki, 2019-11-07, openshift#18207), so folks who think "I need to add X.509 trust" and land on the "custom PKI" section can see "oh, I'm not using a proxy, I guess I should configure the build tooling directly..." and head over. Also, we're likely to have a number of additional cluster components that have their own custom CA injection mechanisms, and this new section gives us a convenient list we can extend.
https://bugzilla.redhat.com/show_bug.cgi?id=1712525
Reorganized from previous submission: #18004