bridgecrew-perf7 / mq-infra

MQ Devops pipeline - Deploys Queuemanager and its configurations

mq-infra

This project contains necessary artifacts for deploying queuemanager on Openshift.

Table of Contents

• Introduction
• Pre-requisites
• Queuemanager Details

Introduction

This guide provides a walkthrough on how to set up an Queuemanager. The Github repository is a template containing a Dockerfile and Helm Chart which is used with the Cloud Native Toolkit to register a Tekton pipeline to build a Queuemanager image and deploy it on a containerized instance of IBM MQ.

This repo contains the below artifacts.

.
├── Dockerfile
├── chart
│   └── base
│       ├── Chart.yaml
│       ├── .helmignore
│       ├── templates
│       │   ├── NOTES.txt
│       │   ├── _helpers.tpl
│       │   └── qm-template.yaml
│       └── values.yaml
└── config example

• ibm-mqadvanced-server-integration docker image that comes with CloudPaks. This image can be further customized if we need additional configurations that are part of queuemanager.
• Helm Charts - Currently, we are using quickstart template for deploying the queuemanager.
• Configurations - Like mentioned earlier, the configurations can be embedded as part of Dockerfile. Alternatively, they can also be injected as configmaps.

Pre-requisites

• IBM Catalog Operator
• IBM Common Services
• IBM MQ Operator

Queuemanager Details

• Intially, security is disabled.
• To enable security, set security to true in Values.yaml.
• To enable high availability, set ha to true in Values.yaml.

Note: This project demonstrates how to add in the mqsc configuration files. Similarly, if you want to configure an qm.ini, please create a configMap for the same and inject it under spec.queueManager in the qm-template.yaml using the below snippet.

ini:
- configMap:
    name: {{ .Values.ini.configmap }}
    items:
    - {{ .Values.ini.name }}