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
The
relabelings
block of theserviceMonitor
configuration for the k8s-control-plane component does not include theaction
field.The default value for action is
replace
.Having this field undefined makes ArgoCD to be always unsynced.
The definitions in this repo code lack the
action
field, but when the object is created in Kubernetes, the field is written in the Kubernetes object with the default value (replace
). Then, ArgoCD compares with the code in the repo and tries to sync again (removing theaction
field). This causes an infinite loop of adding and removing theaction
field.Setting the
action
field to the default value (replace
) in the code solves this problem and does not change the behavior ofserviceMonitor
.Type of change
CHANGE
(fix or feature that would cause existing functionality to not work as expected)FEATURE
(non-breaking change which adds functionality)BUGFIX
(non-breaking change which fixes an issue)ENHANCEMENT
(non-breaking change which improves existing functionality)NONE
(if none of the other choices apply. Example, tooling, build system, CI, docs, etc.)Changelog entry