chore(preview-env): Use a static name for the TLS secret #1734
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
igpetrov
approved these changes
Jan 17, 2024
github-actions
bot
temporarily deployed
to
connectors-preview-env-fix-c8sm
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.
Description
Related to https://github.com/camunda/team-infrastructure/issues/510
This PR introduces the use of a static name for the secret containing the TLS certificate of the preview environment.
Reasons:
*in the ArgoCDignoreDifferencesconfiguration, which does not seem to be well supported as ArgoCD sometimes synchronizes the TLS secret (tls.crt,tls.key), whereas differences should be ignored