Extend strict TLS mode to fleet-agent container
#2556
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
Strict TLS mode must be applied not only in the `fleet-agent-register` init container, but also in the main agent container itself, which also reaches out to the upstream cluster.
manno
reviewed
Jun 26, 2024
This aligns lookup with how it is done in `runRegistration`.
manno
approved these changes
Jun 27, 2024
This was referenced Jul 2, 2024
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.
Strict TLS mode must be applied not only in the
fleet-agent-registerinit container, but also in the main agent container itself, which also reaches out to the upstream cluster.Refers to #2171.
Follow-up to #2507.