-
Notifications
You must be signed in to change notification settings - Fork 344
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
Add FAQ entry on keystore passwords #1354
Conversation
✅ Deploy Preview for cert-manager-website ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Signed-off-by: Ashley Davis <ashley.davis@venafi.com>
7901202
to
d30d336
Compare
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.
/lgtm
Thanks for explaining this @SgtCoDFish.
/hold in case you want someone else to read this too.
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: inteon 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 |
A huge LGTM from me also. Thanks Ash! I don't have reviewer permissions on this project yet, but I'm planning to create a PR for that. |
/unhold Thanks both! |
This has been a hotly requested thing when we've been talking about these passwords for both cert-manager and trust-manager, and it was discussed in the biweekly meeting on 2023-11-30.
Longer term, this FAQ entry should provide us with justification for allowing users to specify these "passwords" in plaintext in their
Certificate
resources, replacingpasswordSecretRef
on JKSKeystore and PKCS12Keystore.