Images

This page describes how to configure the Kannika Armory Docker images during installation.

Images are available from https://quay.io/kannika.

In case you want to use your own images, you can override the default images used by the Helm chart. This can be useful in case you want to use a different image repository.

Configuring the operator image

The kannika-operator image is used to run the operator. The following configuration options are available to configure the image used to run the operator.

Parameter	Description
operator.image.repository	The image repository to use, e.g. quay.io/kannika/kannika-operator
operator.image.tag	The image tag to use, e.g. latest
operator.image.pullPollicy	The image pull policy to use: IfNotPresent, Always, Never

Configuring the core image

The kannika-core image is used by the operator to run the Backup and Restore Pods. The following configuration options are available to configure the image:

Parameter	Description
operator.config.coreImage.repository	The image repository to use, e.g. quay.io/kannika/kannika-core
operator.config.coreImage.tag	The image tag to use, e.g. latest
operator.config.coreImage.pullPollicy	The image pull policy to use: IfNotPresent, Always, Never

Configuring the API image

The kannika-api image is used to provide the API. The following configuration options are available to configure the image for the API:

Parameter	Description
api.image.repository	The image repository to use, e.g. quay.io/kannika/kannika-api
api.image.tag	The image tag to use, e.g. latest
api.image.pullPollicy	The image pull policy to use: IfNotPresent, Always, Never

Configuring the SchemaRegistryBackup image

The kannika-schema-registry-backup image is used by the operator to run the SchemaRegistryBackup Pods. The following configuration options are available to configure the image:

Parameter	Description
operator.config.schemaRegistryImage.repository	The image repository to use, e.g. quay.io/kannika/kannika-schema-registry-backup
operator.config.schemaRegistryImage.tag	The image tag to use, e.g. latest
operator.config.schemaRegistryImage.pullPollicy	The image pull policy to use: IfNotPresent, Always, Never

Private image registry support

Configuring image pull secrets

In case you want to use a private image repository, you must configure image pull secrets.

You can configure image pull secrets in all the Helm charts by setting global.imagePullSecrets to an array of secret names.

values.yaml

global:
  imagePullSecrets:
    - name: registry-pull-secret-name

The following configuration options are available to configure the image pull secrets per chart, which take precedence over the global configuration:

values.yaml

operator:
  image:
    pullSecrets:
      - name: registry-pull-secret-name

api:
  image:
    pullSecrets:
      - name: registry-pull-secret-name

console:
  image:
    pullSecrets:
      - name: registry-pull-secret-name

It is also possible to specifically define the image pull secrets for pods spawned by the operator. See Default Pod Settings.