Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

In some cases, you may need to run an additional pod alongside the main pod — for example, for debugging purposes—or an additional init container, for instance, to establish a connection to external services like HashiCorp Vault or HashiCorp Consul.

When using a Docker image from a private registry, you'll need to configure imagePullPolicy and imagePullSecrets to access the private registry from Kubernetes. This article explains how to configure these settings in the HiveMQ Platform Operator Helm chart.

\uD83D\uDCD8 Instructions

There are two options for configuring pullPolicy and pullSecretName: globally at the HiveMQ Platform Operator level or at the HiveMQ Platforms' level.

  1. Option 1: Define global pullPolicy and pullSecretName in the Platform Operator, then they are applied to all managed HiveMQ Platforms. 

    HiveMQ Platform Operator Helm chart:

    image:
  repository: docker.io/hivemq
  name: hivemq-platform-operator
  tag: 1.5.0
  initImageName: hivemq-platform-operator-init
  pullPolicy: IfNotPresent
  pullSecretName: ""

  2. Option 2: Configure pullPolicy and pullSecret in the HiveMQ Platform image: section, and they apply to all containers, including sidecars and init containers.

    HiveMQ Platform values.yaml

    # HiveMQ Platform container image configuration
image:
  repository: docker.io/hivemq
  name: hivemq4
  tag: 4.31.0
  pullPolicy: IfNotPresent <-- applied to all containers
  pullSecretName: "" <-- applied to all containers

  • No labels