\n\n# RabbitMQ Advanced Helm Chart\n\nRabbitMQ is a popular open-source message broker. The RabbitMQ Advanced Helm chart automates the deployment and configuration of RabbitMQ in Kubernetes clusters using the Minimus RabbitMQ Advanced image with **TLS encryption** and **init container support**.\n\n\n## {{icon-list-search}} Prerequisites\n\n- A subscription to the Minimus images included in the chart\n- A running Kubernetes cluster (v1.21 or higher is recommended)\n- `kubectl` installed and configured\n- Helm v3.8 or higher for OCI support ([Installation instructions](https://helm.sh/docs/intro/install/))\n- Cluster Admin privileges\n\n\n

\n\n---\n\n

\n \n## {{icon-rocket}}Try It Out\n\n\nIn this example we will deploy RabbitMQ on a Minikube cluster using the Minimus Helm chart. To test the deployment, we will connect to RabbitMQ, publish messages, and verify the management interface.\n\n\n

\n\n### Step 1: Start Cluster\n\n

\n\n\nIf you have a cluster to work with, skip this step. Otherwise, start a Minikube cluster. [Deployment instructions](https://minikube.sigs.k8s.io/docs/start/?arch=%2Flinux%2Fx86-64%2Fstable%2Fbinary+download)\n\n

\n\n### Step 2: Create Namespace\n\n

\n\nCreate a namespace:\n\n```\nkubectl create ns rabbitmq-advanced-fips\n```\n\n{{if-enterprise}}\n\nNext, create a Kubernetes secret for the Minimus token:\n\n```\nkubectl create secret docker-registry minimus-registry \\\n --docker-server=reg.mini.dev \\\n --docker-username=minimus \\\n --docker-password={{pull-token}} \\\n --namespace=rabbitmq-advanced-fips\n```\n\n{{/if-enterprise}}\n\n

\n\n### Step 3: Save Values File Locally \n\n

\n\nGo to the Values tab and save a copy of the it locally. You will need to add the flag `-f values.yaml` to override the defaults when you deploy the chart in the next step.\n\n**Note**: The values.yaml uses default metrics configurations. If you need ServiceMonitor for an external Prometheus, you can add the metrics configuration to your values file.\n\n\n

\n\n### Step 4: Deploy the Helm Chart\n\nDeploy the Minimus Helm chart with the values.yaml file you saved in the previous step.\n\n

\n\nRun the following command:\n\n```\nhelm install my-rabbitmq-advanced-fips {{oci-url}} \\\n --version {{chart-version}} \\\n-f values.yaml \\\n-n rabbitmq-advanced-fips\n```\n\n\n

\n\n### Step 5: Verify RabbitMQ is Running\n\n

\n\nTo check that the pod was successfully created run:\n\n```\nkubectl get pods -n rabbitmq-advanced-fips -l app.kubernetes.io/name=rabbitmq\n```\n\nYou should see output similar to:\n\n```\nNAME READY STATUS RESTARTS AGE\nmy-rabbitmq-0 1/1 Running 0 2m\n```\n

\n \n### Step 6: Access Management Interface\n\n

\n\nPort forward to access the RabbitMQ management interface:\n\n```\nkubectl port-forward -n rabbitmq-advanced-fips svc/my-rabbitmq-advanced-fips 15672:15672\n```\n\nOpen your browser and navigate to `http://localhost:15672`\n\nLogin with the following:\n- Username: `rmquser`\n- Password: `rmqpass123`\n\n

\n\n### Step 7: Test TLS Message Publishing\n\n

\n\nCreate a test job to verify RabbitMQ TLS functionality:\n\n```\ncat < \n \n### Step 8: Access Metrics (Optional)\n\n\n\nRabbitMQ metrics are available by default. You can access them via port-forwarding:\n\n```bash\nkubectl port-forward -n rabbitmq-advanced-fips svc/my-rabbitmq-advanced-fips 9419:9419\n```\n\nIn another terminal, test the metrics endpoint:\n\n```bash\ncurl http://localhost:9419/metrics\n```\n\n

\n \n### Step 9: Cleanup\n\n

\n\nTo clean up the deployment:\n\n```bash\nhelm uninstall my-rabbitmq-advanced-fips -n rabbitmq-advanced-fips\nkubectl delete namespace rabbitmq-advanced-fips\n```\n\n

\n\n\n---\n\n

\n\n## {{icon-info-circle}}Terms & Info\n\n

\n\n### Trademark\n\n

\n\nThis catalog is published by Minimus. All product names, logos, and marks, other than those belonging to Minimus, shown are owned by their respective rights holders and appear here only to identify the open source software each image contains. Minimus claims no ownership of those marks and implies no affiliation with, endorsement by, certification by, or sponsorship by any rights holder.\n\n\n{{if-anonymous}} \n\n

\n\n### Disclaimer\n\n

\n\n\nImages are provided \"as-is\" without warranty of any kind. \"Hardened\" refers to the security configuration applied at the time of build and does not constitute a guarantee of ongoing security or absence of vulnerabilities. The free tier is provided without support, SLA, or guaranteed patching timelines. Security updates may be applied to paid subscriptions before or instead of free tier images. By pulling or using any image you agree to our [Terms of Use](https://www.minimus.io/terms-of-use).\n\n{{/if-anonymous}}\n\n\n

","ociDigest","sha256:aa54358dfe28fee545169744e1ee505d8e3d5b39376cfcdce786b3796bf574e6","tarballDigest","sha256:89c5fb517a7b01edb1d1d56ae91fc8d75ead563ed97e6d6f43388571a192167b","data","advanced",41,"etcd-advanced-fips","etcd Advanced with hardened security and production-grade configuration. FIPS-validated version. ","2025-12-15T09:56:25.721144Z","2026-06-23T12:24:48.761097Z",[284,304,285],{"_25":299,"_275":286,"_33":276,"_277":298,"_43":300,"_45":290,"_278":301,"_280":302,"_282":303},[294,295],{"_25":297,"_269":270,"_244":287,"_271":298},{"_25":296,"_269":270,"_244":274,"_271":36},726,725,"3.6.7",70,"2026-01-15T10:17:38.054649Z","

\n\n# Etcd Advanced FIPS Helm Chart\n\netcd is a distributed key-value store used to coordinate and manage configuration data for distributed systems such as Kubernetes.\nThe etcd Advanced FIPS Helm chart automates deployment and configuration of etcd in Kubernetes clusters using the Minimus etcd-Advanced-FIPS image, which provides hardened security, TLS support, FIPS-validated cryptography, and pre-configured lifecycle hooks for safe startup and shutdown.\n\n## {{icon-list-search}} Prerequisites\n\n- A subscription to the Minimus images included in the chart\n- A running Kubernetes cluster (v1.21 or higher is recommended)\n- `kubectl` installed and configured\n- Helm v3.8 or higher for OCI support ([Installation instructions](https://helm.sh/docs/intro/install/))\n- Cluster Admin privileges\n\n\n

\n\n---\n

\n\n## {{icon-fips}}Test FIPS Compatibility \n\nTo test that the OpenSSL FIPS provider module is configured, follow the instructions in the [FIPS tab]({{fips-tab}}).\n\nThe Minimus Cryptographic Module has one or more of the following FIPS certifications (depending on the image and technology):\n\n- [NIST Certificate 5040](https://csrc.nist.gov/projects/cryptographic-module-validation-program/certificate/5040)\n- [NIST Certificate 4912](https://csrc.nist.gov/projects/cryptographic-module-validation-program/certificate/4912)\n\n\n

\n\n---\n\n

\n \n## {{icon-rocket}}Try It Out\n\n\nIn this example we will deploy etcd on a Minikube cluster using the Minimus Helm chart.\nWe will test the deployment by storing and retrieving a key from etcd.\n\n

\n\n### Step 1: Start Cluster\n\n

\n\n### Step 2: Create Namespace\n\n

\n\nCreate a namespace:\n\n```\nkubectl create ns etcd-advanced-fips\n```\n\n{{if-enterprise}}\n\nNext, create a Kubernetes secret for the Minimus token:\n\n```\nkubectl create secret docker-registry minimus-registry \\\n --docker-server=reg.mini.dev \\\n --docker-username=minimus \\\n --docker-password={{pull-token}} \\\n --namespace=etcd-advanced-fips\n```\n\n{{/if-enterprise}}\n\n

\n\n### Step 3: Save Values File Locally \n\n

\n\nGo to the Values tab and save a copy of the it locally. You will need to add the flag `-f values.yaml` to override the defaults when you deploy the chart in the next step.\n\n\n

\n\n### Step 4: Deploy the Helm Chart\n\n

\n\nDeploy the Minimus Helm chart with the values.yaml file you saved in the previous step:\n\n```\nhelm install my-etcd-advanced-fips {{oci-url}} \\\n --version {{chart-version}} \\\n -f values.yaml \\\n -n etcd-advanced-fips\n```\n\n\n

\n\n### Step 5: Verify etcd is Running\n\n

\n\nConfirms the chart deployed successfully and etcd started:\n\n```\nkubectl get pods -n etcd-advanced-fips\n```\n\nYou should see output similar to:\n\n```\nNAME READY STATUS RESTARTS AGE\nmy-etcd-advanced-fips-0 1/1 Running 0 2m\n```\n

\n \n### Step 6: Test Key Storage and Retrieval\n\n

\n\nSet variables for your deployment (replace `my-etcd-advanced-fips` and `etcd-advanced-fips` with your actual release name and namespace):\n```\nexport RELEASE_NAME=my-etcd-advanced-fips\nexport NAMESPACE=etcd-advanced-fips\n```\n\nFind the etcd service name (it may differ from the release name):\n```\nexport ETCD_SERVICE=$(kubectl get svc -n $NAMESPACE -l app.kubernetes.io/name=etcd,app.kubernetes.io/component=etcd -o jsonpath='{.items[0].metadata.name}')\necho \"Using etcd service: $ETCD_SERVICE\"\n```\n\nVerify the service exists and has endpoints:\n```\nkubectl get svc $ETCD_SERVICE -n $NAMESPACE\nkubectl get endpoints $ETCD_SERVICE -n $NAMESPACE\n```\n\nThe endpoints should show the pod IP address. If endpoints are empty, wait a few seconds and check again.\n\nExport the etcd root password:\n```\nexport ETCD_ROOT_PASSWORD=$(kubectl get secret --namespace $NAMESPACE $RELEASE_NAME -o jsonpath=\"{.data.etcd-root-password}\" | base64 -d)\n```\n\nRun a temporary etcd client pod:\n```\nkubectl run etcd-client --restart='Never' \\\n --image reg.mini.dev/etcd-advanced-fips:3.6.5 \\\n --env ROOT_PASSWORD=$ETCD_ROOT_PASSWORD \\\n --env ETCDCTL_API=3 \\\n --namespace $NAMESPACE \\\n --command -- sleep infinity\n```\n\nWait for the etcd-client pod to be ready:\n```\nkubectl wait --for=condition=ready pod etcd-client -n $NAMESPACE --timeout=60s\n```\n\nWrite and read a key (this command runs inside the etcd-client pod):\n```\nkubectl -n $NAMESPACE exec etcd-client -- bash -lc \"etcdctl --endpoints=http://${ETCD_SERVICE}.${NAMESPACE}.svc.cluster.local:2379 --user root:\\$ROOT_PASSWORD put /message 'Hello from Minimus FIPS' && etcdctl --endpoints=http://${ETCD_SERVICE}.${NAMESPACE}.svc.cluster.local:2379 --user root:\\$ROOT_PASSWORD get /message\"\n```\n\nAlternatively, you can run the commands separately:\n```\nkubectl -n $NAMESPACE exec etcd-client -- bash -lc \"etcdctl --endpoints=http://${ETCD_SERVICE}.${NAMESPACE}.svc.cluster.local:2379 --user root:\\$ROOT_PASSWORD put /message 'Hello from Minimus FIPS'\"\nkubectl -n $NAMESPACE exec etcd-client -- bash -lc \"etcdctl --endpoints=http://${ETCD_SERVICE}.${NAMESPACE}.svc.cluster.local:2379 --user root:\\$ROOT_PASSWORD get /message\"\n```\n\nExpected output:\n```\nOK\n/message\nHello from Minimus FIPS\n```\n\n\n

\n\n### Step 7: Access etcd Locally\n

\n\nYou can interact with your etcd cluster directly from your local machine through kubectl port-forward.\n\n```\nkubectl port-forward -n etcd-advanced-fips svc/my-etcd-advanced-fips 2379:2379\n```\nYou should see:\n```\nForwarding from 127.0.0.1:2379 -> 2379\nForwarding from [::1]:2379 -> 2379\n```\nKeep this terminal open\n\nOpen a second terminal and export the password:\n\n```\nexport ETCD_ROOT_PASSWORD=$(kubectl -n etcd-advanced-fips get secret my-etcd-advanced-fips \\\n -o jsonpath='{.data.etcd-root-password}' | base64 -d)\n```\nVerify connectivity and read the key:\n```\ncurl -s localhost:2379/health\n\nETCDCTL_API=3 etcdctl \\\n --endpoints=http://127.0.0.1:2379 \\\n --user \"root:$ETCD_ROOT_PASSWORD\" \\\n get /message\n```\n\nExpected output:\n```\n{\"health\":\"true\",\"reason\":\"\"}\n/message\nHello from Minimus FIPS\n```\n\n### Step 8: Cleanup (Optional)\n\n\n\nIf you're done testing:\n\n```bash\nhelm uninstall my-etcd-advanced-fips -n etcd-advanced-fips\nkubectl delete namespace etcd-advanced-fips\n```\n\n

\n\n---\n\n

\n\n## {{icon-info-circle}}Terms & Info\n\n

\n\n### Trademark\n\n

\n\n### Disclaimer\n\n

\n\n","sha256:6f92db9ba7db9633b3bd0d29ea661295af2aad26952f378be4942a1bc4bac7c8","sha256:f7170f56f9ac377baa99cdaeb0eae38026fcee6131c4c0dc746fd38f36b62567","fips",[285,304,315,316],"thirdPartyImageName","","2025-12-03T11:05:55.044215Z","2026-06-24T12:50:37.218935Z","private","isCustom","groups",[314],"os-shell","stig","utils","webappURL","https://images.minimus.io","docsURL","https://docs.minimus.io/","docsMap",{"_327":328,"_329":330,"_331":307,"_332":333,"_334":335,"_336":337,"_338":339,"_340":341,"_342":307,"_343":307,"_344":307,"_345":346,"_347":348,"_349":350,"_351":352,"_353":354,"_355":356,"_357":358,"_359":307,"_360":307,"_361":307,"_362":307,"_363":307,"_364":307,"_365":307,"_366":307,"_367":307,"_368":307,"_369":370,"_371":372,"_373":374,"_375":376,"_377":378,"_379":307,"_380":381,"_382":307,"_383":307,"_384":307,"_385":307,"_386":387,"_388":307,"_389":390,"_391":392,"_393":394,"_395":394,"_396":397,"_398":307,"_399":307,"_400":401,"_402":403,"_404":405,"_406":407,"_408":409},"user","isAnonymous","isTokensExpired","license","/","https://docs.minimus.io","/actions","https://docs.minimus.io/remediate/actions","/actions/?","/actions/create","https://docs.minimus.io/remediate/create-action","/advisories","https://docs.minimus.io/remediate/advisories","/advisories/?","https://docs.minimus.io/remediate/cve-advisory","/advisories/?/exploitability","https://docs.minimus.io/remediate/threat-intel#threat-intel","/advisories/?/packages","https://docs.minimus.io/remediate/cve-advisory#status-history","/advisories/?/packages/?","/advisories/?/references","/advisories/?/severity","/charts","https://docs.minimus.io/foundations/helm-charts","/creator/list","https://docs.minimus.io/advanced-tooling/image-creator","/creator/files","https://docs.minimus.io/advanced-tooling/file-bundles","/supply-chain-protection","https://docs.minimus.io/advanced-tooling/supply-chain","/gallery","https://docs.minimus.io/gallery","/gallery/images/?","https://docs.minimus.io/foundations/image-card","/gallery/images/?/changelog","https://docs.minimus.io/foundations/image-card#changelog","/gallery/images/?/changelog/?","/gallery/images/?/changelog/?/versions/?/?","/gallery/images/?/changelog/?/versions/?/?/exploitability","/gallery/images/?/changelog/?/versions/?/?/packages","/gallery/images/?/changelog/?/versions/?/?/packages/?","/gallery/images/?/changelog/?/versions/?/?/references","/gallery/images/?/changelog/?/versions/?/?/severity","/gallery/images/?/changelog/?/versions/?/digest-history","/gallery/images/?/lines","/gallery/images/?/lines/?","/gallery/images/?/lines/?/versions/?","https://docs.minimus.io/foundations/image-version","/gallery/images/?/lines/?/versions/?/digest-history","https://docs.minimus.io/foundations/image-version#digest-history","/gallery/images/?/lines/?/versions/?/sbom","https://docs.minimus.io/foundations/image-version#sbom","/gallery/images/?/lines/?/versions/?/specification","https://docs.minimus.io/foundations/image-version#specification","/gallery/images/?/lines/?/versions/?/vulnerabilities","https://docs.minimus.io/foundations/image-version#vulnerabilities","/gallery/images/?/quick-start","/gallery/images/?/risk-reduction","https://docs.minimus.io/foundations/image-card#risk-reduction","/gallery/images/?/risk-reduction/?","/gallery/images/?/risk-reduction/?/exploitability","/gallery/images/?/risk-reduction/?/references","/gallery/images/?/risk-reduction/?/severity","/gallery/images/?/compliance/cis","https://docs.minimus.io/foundations/image-card#compliance","/manage","/manage/self-hosting","https://docs.minimus.io/manage/self-hosted-registry","/manage/subscription","https://docs.minimus.io/introduction/subscription","/manage/logs/activity-log","https://docs.minimus.io/manage/activity-log","/manage/logs/audit-log","/manage/tokens","https://docs.minimus.io/manage/token","/manage/tokens/create","/manage/tokens/delete/?","/manage/access/users","https://docs.minimus.io/manage/users","/manage/access/users/create","https://docs.minimus.io/manage/users#add-users","/manage/access/users/saml","https://docs.minimus.io/sso/saml","/manage/access/groups","https://docs.minimus.io/manage/user-groups","/manage/minicli","https://docs.minimus.io/advanced-tooling/minicli","toast","gtmID","GTM-56RQNQ3D","hubspotID","42541238"]

This page is available on desktop