How ibm-messaging/mq-helm works
Project type and purpose
• This repository is a Helm chart for deploying IBM MQ containers into Kubernetes (“ibm-mq” under charts/), plus a collection of sample deployments for various cloud/Kubernetes environments (samples/…).
• It is an infrastructure-as-code/DevOps project, not an application codebase. Its goal is to package IBM MQ container definitions, Kubernetes manifests, and knobs (via values.yaml) so operators can deploy MQ clusters, HA configurations, licensing annotations, and related resources reliably.
File structure
• Top-level directories:
• charts/ibm-mq/… → Helm chart code (Chart.yaml, values.yaml, templates/).
• samples/… → dozens of example overlays and scripts targeting AWS, Azure, GKE, OpenShift, Minikube, etc.
• charts/ibm-mq/templates contains Kubernetes manifest templates: ConfigMap, ServiceAccount, StatefulSet, PVC, Services (ClusterIP, LoadBalancer), Ingress/Route, Metrics Service.
• values.yaml drives templating of image versions, storage, HA mode, licensing annotations, ingress hosts, ports.
• CI/CD: .github/workflows/release.yml builds chart package and pushes to Helm repo.
README for additional insights
• README explains prerequisites (Helm 3, kubectl), chart features (MQ container version, native HA, licensing via IBM License Service).
• Mentions optional IBM License Service operator running in cluster to track usage via Pod annotations.
Elements
• Clear labels: “Helm Client”, “Kubernetes API”, “MQ StatefulSet”, “PVC (data, log)”, “ServiceAccount”, etc.
• Helm → API Server (install)
• API Server → each resource type (creation)
• MQ Pod → PVC (mount)
• MQ Pod → Service (serve traffic)
• Ingress → Service (ingress traffic)
• License Operator → LicenseService CR
• Orange for Helm/client-side elements
• Gray for optional License operator path
Detail and essential elements
• Break out the Helm chart folder as its own component, showing values.yaml feeding into templates.
• Dual-mode architecture: single MQ queue manager vs. Native HA multi-pod queue manager.
• Call out the licensing annotation extension point.