-
Notifications
You must be signed in to change notification settings - Fork 20
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
Support multiple AmazonCloudWatchAgent CRs and add integration for Prometheus Target Allocator #126
Conversation
… Prometheus monitoring with Target Allocator (#86) * add support for configurable modes for cloudwatch agent CR * Adding more configurable fields * adding support for certs with multiple agent workloaf * Adding support for conditional target-allocator cluster roles * adding support for replicas * adding support for replicas * fixing values.yaml * fixing values.yaml * Updating operator cluster-role to perform CRUD operations on pdb * adding support for custom target-allocator images * bug fixed for parsing prom config * Update Agent workload comment Co-authored-by: Kaushik Surya <[email protected]> --------- Co-authored-by: okankoAMZ <[email protected]> Co-authored-by: Kaushik Surya <[email protected]>
# Conflicts: # charts/amazon-cloudwatch-observability/templates/certmanager.yaml # charts/amazon-cloudwatch-observability/templates/linux/cloudwatch-agent-custom-resource.yaml
allocationStrategy: "consistent-hashing" | ||
{{- if $customAgent.prometheus.targetAllocator.prometheusCR }} | ||
prometheusCR: {{ $customAgent.prometheus.targetAllocator.prometheusCR.enabled | default false }} | ||
{{- end }} |
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.
We need to add this to allow the user to use the agent
values.
{{- end }} | |
{{- end }} | |
{{- else if $.Values.agent.prometheus.targetAllocator }} | |
targetAllocator: | |
enabled: {{ $.Values.agent.prometheus.targetAllocator.enabled | default false }} | |
image: {{ include "target-allocator.modify-image" (merge (dict "image" $.Values.agent.prometheus.targetAllocator.image) $ ) }} | |
allocationStrategy: "consistent-hashing" | |
{{- if $.Values.agent.prometheus.targetAllocator.prometheusCR }} | |
prometheusCR: {{ $.Values.agent.prometheus.targetAllocator.prometheusCR.enabled | default false }} | |
{{- end }} |
{{- with $customAgent.prometheus.config }} | ||
config: | ||
{{- toYaml . | nindent 6 }} | ||
{{- end }} |
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.
We need to add this to allow the user to use the agent
values.
{{- end }} | |
{{- end }} | |
{{- else if $.Values.agent.prometheus.config }} | |
prometheus: | |
{{- with $.Values.agent.prometheus.config }} | |
config: | |
{{- toYaml . | nindent 6 }} | |
{{- end }} |
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.
we need to update: operator tag:tag: 1.9.0
# Conflicts: # charts/amazon-cloudwatch-observability/templates/linux/cloudwatch-agent-custom-resource.yaml # charts/amazon-cloudwatch-observability/values.yaml
There's room for improvements with how we handle the overlays for Did a helm template render of the chart with and without this change and the diffs look as expected - essentially a no-op in the default case. |
I don't understand why this is merged into the main, but no new releases are done. How can we know if this available on release 2.6.0 or not ? |
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.