-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: allow prometheus extend rule [ATMOSPHERE-48] #1215
base: main
Are you sure you want to change the base?
Conversation
2221e7f
to
67d7c0f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see a few issues with this current approach.
This means that there's no way of actually editing the existing rules, this is just extending/adding to the additional existing rules. This means that this can simply be replaced with kube_prometheus_stack_helm_values.additionalPrometheusRulesMap
instead which becomes just a documentation change.
I'd rather we do that than introduce a new variable for this.
@mnaser Is don't know if i understand this correctly but when you use at the combine filter use 'list_merge=append' it will extend the string and then you can use the feature from jsonnet to overide/extend the existing settings. |
If we need override existing, another way we I can try is to write an ansible plugin so we can handle combine on real recursive ( and avoid constraint that brought by existing combine function https://github.com/vexxhost/atmosphere/pull/1215/files#diff-2162201c39f35aed971e9b5b2fc33cb1860cfa756c8cf776683d15fe686b9cfaR291-R296 ) |
67d7c0f
to
1bc350f
Compare
The issue with directly using list_merge=append for combine, is that will give us two rule group with same name and makes error for charts like
I just added a plugin to handle that error |
1bc350f
to
424d094
Compare
recheck |
fix: #738