Testing Operator Deployment with OLM

Note: before continuing, please read the caveats section below.

operator-sdk run bundle assumes OLM is already installed and running on your cluster. It also assumes that your Operator has a valid . See the [creating a bundle][creating-bundle] guide for more information. See the CLI overview for commands to work with an OLM installation and generate a bundle.

Let’s look at the configuration shared between run bundle, run packagemanifests and cleanup:

• kubeconfig: the local path to a kubeconfig. This uses well-defined default loading rules to load the config if empty.
• namespace: the cluster namespace in which Operator resources are created. This namespace must already exist in the cluster. This is an optional field which will default to the kubeconfig context if not provided.
• timeout: a time string dictating the maximum time that run can run. The command will return an error if the timeout is exceeded.

• bundle-image: specifies the Operator bundle image, this is a required parameter. The bundle image must be pullable.
• index-image: specifies an index image in which to inject the given bundle. This is an optional field which will default to quay.io/operator-framework/upstream-opm-builder:latest
• install-mode: specifies which supported should be used to create an OperatorGroup by configuring its spec.targetNamespaces field. The InstallModeType string passed must be marked as “supported” in the CSV being installed.
  • This is an optional parameter, but if the CSV does not support AllNamespaces then this parameter becomes required to instruct run bundle with the appropriate InstallModeType.

operator-sdk run packagemanifests assumes OLM is already installed and running on your cluster, and that your Operator has a valid package manifests format. See the for commands to work with an OLM installation and generate a package manifests format.

Let’s look at the configuration shared between run bundle, run packagemanifests and cleanup:

• kubeconfig: the local path to a kubeconfig. This uses well-defined default loading rules to load the config if empty.
• namespace: the cluster namespace in which Operator resources are created. This namespace must already exist in the cluster. This is an optional field which will default to the kubeconfig context if not provided.
• timeout: a time string dictating the maximum time that run can run. The command will return an error if the timeout is exceeded.

Let’s look at the anatomy of the run packagemanifests configuration model:

• packagemanifests-root-dir: a directory containing the Operator’s package manifests, this is a required parameter.
• install-mode: specifies which supported installMode should be used to create an OperatorGroup by configuring its spec.targetNamespaces field. The InstallModeType string passed must be marked as “supported” in the CSV being installed.
  • This option understands the following strings (assuming your CSV does as well):
    • OwnNamespace: the Operator will watch its own namespace (from namespace or the kubeconfig default).
    • SingleNamespace="my-ns": the Operator will watch a namespace, not necessarily its own.
  • This is an optional parameter, but if the CSV does not support then this parameter becomes required to instruct run packagemanifests with the appropriate InstallModeType.
• version: the version of the Operator to deploy. It must be a semantic version, ex. 0.0.1. This version must match the version of the CSV manifest found in manifests-dir, e.g. packagemanifests/0.0.1 in an Operator SDK project.

Let’s look at the configuration shared between run bundle, run packagemanifests and cleanup:

• kubeconfig: the local path to a kubeconfig. This uses well-defined default loading rules to load the config if empty.
• namespace: the cluster namespace in which Operator resources are created. This namespace must already exist in the cluster. This is an optional field which will default to the kubeconfig context if not provided.
• timeout: a time string dictating the maximum time that run can run. The command will return an error if the timeout is exceeded.

Let’s look at the anatomy of the cleanup configuration model:

• operatorPackageName: the Operator’s package name which you want to remove from the cluster, e.g. memcached-operator. This is a required parameter.

• run bundle, run packagemanifests, and cleanup are intended to be used for testing purposes only, since this command creates a transient image registry that should not be used in production. Typically a registry is deployed separately and a set of catalog manifests are created in the cluster to inform OLM of that registry and which Operator versions it can deploy and where to deploy the Operator.
• run bundle and can only deploy one Operator and one version of that Operator at a time, hence its intended purpose being testing only.