Loading...

XML

Word

Printable

Type: Feature Request
Resolution: Unresolved
Priority: Major
Fix Version/s: None
Affects Version/s: None
Component/s: GitOps
Labels:
None

Target Version:
None
Activity Type:
Product / Portfolio Work
Status Summary:
None
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Products:
None
Hierarchy Progress Bar:
None

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

PX Review Complete:
None
PX Impact Score:
PX Impact Range:
None
PX Priority Data:
None
PX Technical Impact:
None
PX Technical Impact Notes:
None
PX Scheduling Request:
None

Proposed title of this feature request
What is the nature and description of the request?
Why does the customer need this? (List the business requirements here)
List any affected packages or components.

Define cpu/mem resources for gitops operator manager container to follow the best practices
Starting from operator version 1.14.1, we have stopped defining the cpu/mem resources for the manager container to avoid issues with customers complaining about the container taking more memory than defined. ( https://access.redhat.com/solutions/7089994) ( https://github.com/redhat-developer/gitops-operator/pull/783)
We recommend customers to always define resources for containers for their application containers as it's a K8S best practice as it helps customers to plan for capacity and run applications optimally.

Assignee:: Sho Weimer

Reporter:: Anand Paladugu

Need Info From:: None

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Created:: 2025/12/20 6:42 PM

Updated:: 2026/01/12 7:54 PM

Target start:: None

Target end:: None