Configuring Container Resources

To configure the controller-manager resources, modify the Subscription Config

• https://github.com/operator-framework/operator-lifecycle-manager/blob/master/doc/design/subscription-config.md
• https://pkg.go.dev/github.com/operator-framework/api/pkg/operators/v1alpha1#SubscriptionConfig
• https://github.com/operator-framework/api/blob/v0.27.0/pkg/operators/v1alpha1/subscription_types.go#L42

---

To configure ibm-metrics-operator parameters, modify the Subscription spec.config.env

Config env properties for ibm-metrics-operator are specified in the config pkg

• https://github.com/redhat-marketplace/redhat-marketplace-operator/blob/develop/v2/pkg/config/config.go

Example: Specify the initial number of data-service replicas when installing and creating the Subscription

• data-service does not support scale-in

apiVersion: operators.coreos.com/v1alpha1
kind: Subscription
metadata:
  name: ibm-metrics-operator
  namespace: ibm-software-central
spec:
  channel: stable
  config:
    env:
    - name: DATA_SERVICE_REPLICAS
      value: "1"
  installPlanApproval: Automatic
  name: ibm-metrics-operator
  source: certified-operators
  sourceNamespace: openshift-marketplace

---

To configure the component containers resources, modify the Subscription spec.config.env to specify name: CONFIG

• SubscriptionConfig spec is passed down to the container resources

Example: specify metric-state container memory limit

apiVersion: operators.coreos.com/v1alpha1
kind: Subscription
metadata:
  name: ibm-metrics-operator
  namespace: ibm-software-central
spec:
  channel: stable
  config:
    env:
    - name: CONFIG
      value: '{"resources":{"containers":{"metric-state":{"limits":{"memory":"1000Mi"}}}}}'
  installPlanApproval: Automatic
  name: ibm-metrics-operator
  source: certified-operators
  sourceNamespace: openshift-marketplace

---

Customize ibm-metrics-operator Subscription as needed for containers

• metric-state
• rhm-data-service
• meter-report
• authcheck
• kube-rbac-proxy-1
• kube-rbac-proxy-2
• watch-keeper

---

Multiple containers can be configured, ex:

{"resources":{"containers":{"system":{"limits":{"cpu":"500m"}},"system2":{"limits":{"cpu":"1"}}}}}