Add ArgoCD sync options to prevent premature pruning of bootstrap deployment #127
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.
With the new setup, the bootstrap deployment is at some point deleted (to be replaced by the operator-managed one). However, this has to happen after the operator-managed ArgoCD is deployed. To prevent premature pruning, the bootstrap deployment is set to not be auto-pruned. A post-sync job in the ArgoCD component will remove these annotations at the appropriate time.
Checklist
bug
,enhancement
,documentation
,change
,breaking
,dependency
as they show up in the changelog