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 in our Helm charts to configure the image used to run the operator.
Chart | Parameter |
---|---|
kannika | operator.image.repository |
kannika | operator.image.tag |
kannika | operator.image.pullPollicy |
kannika-operator | image.repository |
kannika-operator | image.tag |
kannika-operator | image.pullPollicy |
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 in our Helm charts to configure the image:
Chart | Parameter |
---|---|
kannika | operator.config.coreImage.repository |
kannika | operator.config.coreImage.tag |
kannika | operator.config.coreImage.pullPollicy |
kannika-operator | config.coreImage.repository |
kannika-operator | config.coreImage.tag |
kannika-operator | config.coreImage.pullPolicy |
Configuring the API image
The kannika-api
image is used to provide the API.
The following configuration options are available in our Helm charts to configure the image for the API:
Chart | Parameter |
---|---|
kannika | api.image.repository |
kannika | api.image.tag |
kannika | api.image.pullPollicy |
kannika-api | image.repository |
kannika-api | image.tag |
kannika-api | image.pullPollicy |
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 in our Helm charts to configure the image:
Chart | Parameter |
---|---|
kannika | operator.config.schemaRegistryImage.repository |
kannika | operator.config.schemaRegistryImage.tag |
kannika | operator.config.schemaRegistryImage.pullPollicy |
kannika-operator | config.schemaRegistryImage.repository |
kannika-operator | config.schemaRegistryImage.tag |
kannika-operator | config.schemaRegistryImage.pullPollicy |
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.
global: imagePullSecrets: - name: registry-pull-secret-name
The following configuration options are available in our Helm charts to configure the image pull secrets per chart, which take precedence over the global configuration:
Chart | Parameter |
---|---|
kannika | operator.image.pullSecrets |
kannika | api.image.pullSecrets |
kannika | console.image.pullSecrets |
kannika-operator | image.pullSecrets |
kannika-api | image.pullSecrets |
kannika-console | image.pullSecrets |
It is also possible to specifically define the image pull secrets for pods spawned by the operator. See Default Pod Settings.