Skip to content
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

cloudwatch-agent CPU request too high, unable to patch #171

Open
cyounkins opened this issue May 31, 2024 · 0 comments
Open

cloudwatch-agent CPU request too high, unable to patch #171

cyounkins opened this issue May 31, 2024 · 0 comments

Comments

@cyounkins
Copy link

cyounkins commented May 31, 2024

I have v1.7.0-eksbuild.1 of the amazon-cloudwatch-observability add-on installed. Kubernetes 1.27.

kubectl get daemonset cloudwatch-agent -n amazon-cloudwatch -o yaml | grep -A6 'resources:'
        resources:
          limits:
            cpu: 500m
            memory: 512Mi
          requests:
            cpu: 250m
            memory: 128Mi

This is too high for our use on a small cluster with 2 vCPU nodes. I would like to reduce it.

kubectl patch daemonset cloudwatch-agent -n amazon-cloudwatch --type='json' -p='[{"op": "replace", "path": "/spec/template/spec/containers/0/resources/requests/cpu", "value": "50m"}]'

But it is immediately reverted. I also tried pulling down the yaml, editing, and applying to have the same result. Is there something in the background monitoring that config to confirm compliance with the add-on? Is there any strategy I can use to reduce the CPU request?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant