Page Comparison

In some cases, you may need to run an additional pod alongside the main pod—for pod — for example, for debugging purposes—or 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 registryrepository, you'll need to configure imagePullPolicy and imagePullSecrets to access the private registry repository 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:

   Code Block
   language yaml
   image: repository: docker.io/hivemq name: hivemq-platform-operator tag: 1.5.01 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

   Code Block
   language 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

\uD83D\uDCCB Related articles