Skip to content

    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.

    ChartParameter
    kannikaoperator.image.repository
    kannikaoperator.image.tag
    kannikaoperator.image.pullPollicy
    kannika-operatorimage.repository
    kannika-operatorimage.tag
    kannika-operatorimage.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:

    ChartParameter
    kannikaoperator.config.coreImage.repository
    kannikaoperator.config.coreImage.tag
    kannikaoperator.config.coreImage.pullPollicy
    kannika-operatorconfig.coreImage.repository
    kannika-operatorconfig.coreImage.tag
    kannika-operatorconfig.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:

    ChartParameter
    kannikaapi.image.repository
    kannikaapi.image.tag
    kannikaapi.image.pullPollicy
    kannika-apiimage.repository
    kannika-apiimage.tag
    kannika-apiimage.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:

    ChartParameter
    kannikaoperator.config.schemaRegistryBackup.image.repository
    kannikaoperator.config.schemaRegistryBackup.image.tag
    kannikaoperator.config.schemaRegistryBackup.image.pullPollicy
    kannika-operatorconfig.schemaRegistryBackup.image.repository
    kannika-operatorconfig.schemaRegistryBackup.image.tag
    kannika-operatorconfig.schemaRegistryBackup.image.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.

    values.yaml
    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:

    ChartParameter
    kannikaoperator.image.pullSecrets
    kannikaapi.image.pullSecrets
    kannikaconsole.image.pullSecrets
    kannika-operatorimage.pullSecrets
    kannika-apiimage.pullSecrets
    kannika-consoleimage.pullSecrets

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