-
Feature
-
Resolution: Unresolved
-
Undefined
-
ACM 2.11.3
-
False
-
None
-
False
-
Not Selected
Feature Overview
We need to increase the klusterlet-agent resources because the current memory usage is higher than the allocated requests, as shown below:
oc adm top pod
NAME CPU(cores) MEMORY(bytes)
klusterlet-agent-58b8579ff5-cj4xg 1m 30Mi
klusterlet-agent-58b8579ff5-cvx54 1m 27Mi
klusterlet-agent-58b8579ff5-rfxvs 10m 71Mi
oc -n open-cluster-management-agent get pod -o yaml | yq '.items[] | select(.metadata.labels.app == "klusterlet-agent") | [{"name": .metadata.name, "resources": .spec.containers[].resources}]'
- name: klusterlet-agent-58b8579ff5-cj4xg
resources:
requests:
cpu: 2m
memory: 16Mi
- name: klusterlet-agent-58b8579ff5-cvx54
resources:
requests:
cpu: 2m
memory: 16Mi
- name: klusterlet-agent-58b8579ff5-rfxvs
resources:
requests:
cpu: 2m
memory: 16Mi
We tried modifying the deployment to increase the resource requests, but the operator reverted the values back to their defaults.
Since the pods are currently under-provisioned, this results in frequent alerts related to resource under-dimensioning.
Goals
This Section: Provide high-level goal statement, providing user context
and expected user outcome(s) for this feature
- We should be able to increase the klusterlet-agent resources
Requirements
This Section: A list of specific needs or objectives that a Feature must
deliver to satisfy the Feature.. Some requirements will be flagged as MVP.
If an MVP gets shifted, the feature shifts. If a non MVP requirement slips,
it does not shift the feature.
Requirement | Notes | isMvp? |
---|---|---|
CI - MUST be running successfully with test automation | This is a requirement for ALL features. |
YES |
Release Technical Enablement | Provide necessary release enablement details and documents. |
YES |
(Optional) Use Cases
This Section:
- Main success scenarios - high-level user stories
- Alternate flow/scenarios - high-level user stories
- ...
Questions to answer
- ...
Out of Scope
- …
Background, and strategic fit
This Section: What does the person writing code, testing, documenting
need to know? What context can be provided to frame this feature?
Assumptions
- ...
Customer Considerations
- ...
Documentation Considerations
Questions to be addressed:
- What educational or reference material (docs) is required to support this
product feature? For users/admins? Other functions (security officers, etc)? - Does this feature have a doc impact?
- New Content, Updates to existing content, Release Note, or No Doc Impact
- If unsure and no Technical Writer is available, please contact Content
Strategy. - What concepts do customers need to understand to be successful in
[action]? - How do we expect customers will use the feature? For what purpose(s)?
- What reference material might a customer want/need to complete [action]?
- Is there source material that can be used as reference for the Technical
Writer in writing the content? If yes, please link if available. - What is the doc impact (New Content, Updates to existing content, or
Release Note)?
- relates to
-
ACM-15963 Create a standard way for adjusting limits and requests to the addon-framework components
- New