8000 Have a config option to enable OLMv1 operator · Issue #4689 · crc-org/crc · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Have a config option to enable OLMv1 operator #4689

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.

Sign up for GitHub

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

Jump to bottom
Open
praveenkumar opened this issue Mar 18, 2025 · 1 comment
Open

Have a config option to enable OLMv1 operator #4689

praveenkumar opened this issue Mar 18, 2025 · 1 comment
Labels
kind/enhancement New feature or request

Comments

@praveenkumar
Copy link
Member
praveenkumar commented Mar 18, 2025 •
edited
Loading

https://docs.openshift.com/container-platform/4.18/installing/overview/cluster-capabilities.html#cluster-operators-ref-olmv1_cluster-capabilities is now GA and some of users noticed that it is not enabled by default for CRC. We didn't enabled because it add more resource then what we currently expect. following is comparison

Without OLM-v1

Allocated resources:                                                                                               
  (Total limits may be over 100 percent, i.e., overcommitted.)                                                     
  Resource           Requests      Limits                                                                          
  --------           --------      ------                                                                          
  cpu                2302m (60%)   10m (0%)                                                                        
  memory             9483Mi (94%)  0 (0%)                                                                                                                                                                                              
  ephemeral-storage  0 (0%)        0 (0%)                                                                                                                                                                                              
  hugepages-1Gi      0 (0%)        0 (0%)                                                                                                                                                                                              
  hugepages-2Mi      0 (0%)        0 (0%)

With OLM-v1

Allocated resources:
  (Total limits may be over 100 percent, i.e., overcommitted.)
  Resource           Requests      Limits
  --------           --------      ------
  cpu                2432m (64%)   10m (0%)
  memory             9895Mi (99%)  0 (0%)
  ephemeral-storage  0 (0%)        0 (0%)
  hugepages-1Gi      0 (0%)        0 (0%)
  hugepages-2Mi      0 (0%)        0 (0%)

resources usage for olm-v1

$ oc describe node | grep -E '(operator-controller|catalogd|cluster-olm-operator)'
  openshift-catalogd                                catalogd-controller-manager-668f548fd9-vqp9x               105m (2%)     0 (0%)      264Mi (2%)       0 (0%)         22m
  openshift-cluster-olm-operator                    cluster-olm-operator-69974b6dc5-z8xzj                      10m (0%)      0 (0%)      20Mi (0%)        0 (0%)         22m
  openshift-operator-controller                     operator-controller-controller-manager-76f4c49b89-vhxp8    15m (0%)      0 (0%)      128Mi (1%)       0 (0%)         22m

Describe the solution you'd like

Either we need to add the specific config option in crc like we are doing for monitoring operator so user can use that if they need or we have it enabled by default which means increase resource for everyone.

Describe alternatives you've considered

No response

Additional context

No response
@praveenkumar praveenkumar added the kind/enhancement New feature or request label Mar 18, 2025
@acornett21
Copy link

I understand the resource concern, but if the OCP docs say a feature is GA, and then it's not on in CRC (or any other OCP flavor), that makes it super confusing from a users standpoint and they are going to question 'I thought this was GA, why is it not enabled?'. This then leads them to question the GAness (readiness) of said feature, so we need to make sure if this isn't enabled by default, that usability area is explored and documented well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@praveenkumar @acornett21
0