Add TLSStores to Kubernetes CRD #6270
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ldez
added
kind/enhancement
|
Blocked on TLS Store naming question |
mpl
requested changes
Feb 10, 2020
mpl
requested changes
Feb 11, 2020
mpl
requested changes
Feb 13, 2020
mpl
approved these changes
Feb 19, 2020
juliens
added
status/3-needs-merge
and removed
bot/no-merge
status/2-needs-review
labels
add correct anchor
traefiker
force-pushed
the
issue-5468
branch
from
bd61f49
to
190b33b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
This PR Adds the TLS Stores functionality to the CRD, allowing kubernetes users the ability to provide default certificates without using config files and mounting certificates.
Motivation
Fixes #5468
More
Additional Notes
For some reason
make validateseemed to update the kv-ref doc, but idk why 🤷♂