Catalog source pod scheduling

Catalog source pod scheduling

When an Operator Lifecycle Manager (OLM) catalog source of source type grpc defines a spec.image, the Catalog Operator creates a pod that serves the defined image content. By default, this pod defines the following in its spec:

Only the kubernetes.io/os=linux node selector
No priority class name
No tolerations

As an administrator, you can override these values by modifying fields in the CatalogSource object’s optional spec.grpcPodConfig section.

Additional resources

OLM concepts and resources → Catalog source

Overriding the node selector for catalog source pods

Prequisites

CatalogSource object of source type grpc with spec.image defined

Procedure

Edit the CatalogSource object and add or modify the spec.grpcPodConfig section to include the following:
```
  grpcPodConfig:
    nodeSelector:
      custom_label: <label>
```
where <label> is the label for the node selector that you want catalog source pods to use for scheduling.

Additional resources

Placing pods on specific nodes using node selectors

Overriding the priority class name for catalog source pods

Prequisites

CatalogSource object of source type grpc with spec.image defined

Procedure

Edit the CatalogSource object and add or modify the spec.grpcPodConfig section to include the following:
```
  grpcPodConfig:
    priorityClassName: <priority_class>
```
where <priority_class> is one of the following:
- One of the default priority classes provided by Kubernetes: system-cluster-critical or system-node-critical
- An empty set ("") to assign the default priority
- A pre-existing and custom defined priority class

Previously, the only pod scheduling parameter that could be overriden was priorityClassName. This was done by adding the operatorframework.io/priorityclass annotation to the CatalogSource object. For example:

apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  name: example-catalog
  namespace: namespace: olm
  annotations:
    operatorframework.io/priorityclass: system-cluster-critical

If a CatalogSource object defines both the annotation and spec.grpcPodConfig.priorityClassName, the annotation takes precedence over the configuration parameter.

Additional resources

Pod priority classes

Overriding tolerations for catalog source pods

Prequisites

CatalogSource object of source type grpc with spec.image defined

Procedure

Edit the CatalogSource object and add or modify the spec.grpcPodConfig section to include the following:

  grpcPodConfig:
    tolerations:
      - key: "<key_name>"
        operator: "<operator_type>"
        value: "<value>"
        effect: "<effect>"

Additional resources

Understanding taints and tolerations