[Backport release-1.30] Enable and document the insecure field for Helm Repos #4672
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
Also mark required fields as such and make the rest optional. Signed-off-by: Tom Wieczorek <twieczorek@mirantis.com> (cherry picked from commit 9965d04)
The insecure field exists in the CRD for a long time already. Wire it up, so it can actually be used to enable TLS certificate checks. Signed-off-by: Tom Wieczorek <twieczorek@mirantis.com> (cherry picked from commit b6afccf)
16 tasks
twz123
added
area/configuration
area/helm
backport/release-1.29
ncopa
approved these changes
Jun 27, 2024
|
Successfully created backport PR for |
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.
Automated backport to
release-1.30, triggered by a label in #4660.See #4658.