You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We were playing with deploying the gitlab.com/redhat gitlab-runner-operator. It does not specify resources in the rbac proxy in the csv. We tried overriding them with the Subscription object but it looks like the resources in the subscription don't have a way to reference a container name for which container to apply the resource config to when the csv references multiple containers. The resource requirements for the rbac proxy can be different then the requirements for the operator.
The text was updated successfully, but these errors were encountered:
By using SDK ( make bundle ) the CSV will be built with all permissions, see an example under the testdata samples dir: operator-sdk/testdata/go/v3/memcached-operator/bundle/
Also, could you please clarifies what do you mean with subscription resources per container? OLM allows you to create a subscription for the Operator? When/why are looking for it per container?
So, could you please let us know:
a) Do you see that it is still a requirement or this issue could be closed because it is outdated?
b) If it is still required could you please let us know:
What did you do?
What did you expect to see?
What did you see instead? Under which circumstances?
What is the proposed solution? What would you like that happens? Could you please provide an example?
We were playing with deploying the gitlab.com/redhat gitlab-runner-operator. It does not specify resources in the rbac proxy in the csv. We tried overriding them with the Subscription object but it looks like the resources in the subscription don't have a way to reference a container name for which container to apply the resource config to when the csv references multiple containers. The resource requirements for the rbac proxy can be different then the requirements for the operator.
The text was updated successfully, but these errors were encountered: