Page Comparison

Sometimes it is necessary In some cases, you may need to run an additional pod along with alongside the main pod , — for example, for debugging purposes , — or in an additional init container, for exampleinstance, to establish a connection to external services like Hashicorp HashiCorp Vault , Hashicorp or HashiCorp Consul, etc.

Often, When using a docker image for the container is located in a private registry. To access a private registry from Kubernetes, it is required to specify imagePullPolicy and imagePullSecretDocker image from a private repository, you'll need to configure imagePullPolicy and imagePullSecrets to access the private repository from Kubernetes. This article explains how to configure this feature these settings in the HiveMQ Platform Operator (new) Helm chart.

\uD83D\uDCD8 Instructions

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

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

   HiveMQ Platform Operator Helm chart:

   Code Block
   language yaml
   globalimage: rbac: create: true # Create a PodSecurityPolicy, cluster role, role binding and service account for the HiveMQ pods and assign the service account to them. # Disabled by default. PodSecurityPolicy has been removed from Kubernetes versions starting with v1.25 https://kubernetes.io/docs/concepts/security/pod-security-policy/ pspEnabled: false pspAnnotations: {} securityContext: runAsNonRoot: true runAsUser: 1000 allowedCapabilities: [] # Image pull secrets for operator, hivemq or other images. imagePullSecrets: [] <-- applied dynamically on all managed platforms # - name: hivemq-pull-secretrepository: docker.io/hivemq name: hivemq-platform-operator tag: 1.5.1 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