Project maintain
Overview
The pipeline tests are using kind cluster to test operator installation with local container registry setup.
Production bundle and catalog locations
| Type | Image | Description |
|---|---|---|
| Bundles | quay.io/operatorhubio/<operator-name>:v<operator-version> | Example: quay.io/operatorhubio/etcd:v0.9.4 |
| Temporary index (tags) | quay.io/operatorhubio/catalog_tmp:latest | Index contains packages with version same as bundle tag name |
| Temporary index (shas) | quay.io/operatorhubio/catalog_tmp:latests | Index contains packages with version as bundle sha (used for production) |
| Production index | quay.io/operatorhubio/catalog:latest | Multiarch production index image used in operatorhubio-catalog seen by OLM |
Kind cluster and Kubernetes version
By default, the latest k8s version supported by kind is used until the user doesn't limit it via operatorhub.io/ui-metadata-max-k8s-version defined in metadata.annotations in the CSV file. In case the following value is set operatorhub.io/ui-metadata-max-k8s-version: "1.21" then the kind cluster will use Kubernetes latest 1.21 version that kind supports. One can list available Kubernetes versions in kind project release section