Ignoring changes in-cluster changes to annotation & label #34
Conversation
This file contains hidden or 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
Author
|
@davidmirror-ops can't assign you as a reviewer so just light ping. This repo was super useful in setting things up, kudos! |
Collaborator
|
@lucapericlp thanks for the nice comments and the PR!
Good question. I don't have a GKE environment handy but could you share the output of |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Not sure if this will be helpful, I haven't looked into this deeply but I'm assuming that after the first
terraform apply, annotations & labels are getting updated for theflyte-tls-secret(by cert-manager?). I've had to add this in order to make any future changes without disrupting current state.