Skip to content

Add ability for Subscription config to configure a specific container in the operator pod #1507

Open
@dkwon17

Description

@dkwon17

Today, we can use Subscription Config to conifgure resource limits and requests for the operator pod: https://github.com/operator-framework/operator-lifecycle-manager/blob/master/doc/design/subscription-config.md#resources

However, the limit and request is applied to all container of the pod. It looks like it's not possible to configure a specific container of the pod with the subscription config.

Proposal

My proposal is to add functionality to allow configuration for each container by introducing config.containers which can override the default pod spec:

config:
  containers:
    - name: <container I want to configure>
      resources:
        limits:
          memory: "2Gi"

Use case

Our operator pod contains two containers:

  • controller
  • kube-rbac-proxy for authorizing requests

We would like to configure the memory limit for only the controller container and not the kube-rbac-proxy.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions