Update charts to match ICp naming convention
This commit is contained in:
@@ -14,6 +14,6 @@
|
||||
|
||||
apiVersion: v1
|
||||
description: IBM MQ queue manager
|
||||
name: mq-advancedserver
|
||||
name: ibm-mq-dev
|
||||
version: 1.0.0
|
||||
icon: https://developer.ibm.com/messaging/wp-content/uploads/sites/18/2017/07/IBM-MQ-Square-200.png
|
||||
@@ -18,7 +18,7 @@ This chart deploys a single IBM MQ Advanced for Developers server (queue manager
|
||||
To install the chart with the release name `foo`:
|
||||
|
||||
```bash
|
||||
helm install --name foo stable/mq-devserver --set license=accept
|
||||
helm install --name foo stable/ibm-mq-dev --set license=accept
|
||||
```
|
||||
|
||||
This command accepts the [IBM MQ Advanced for Developers license](LICENSE) and deploys an MQ Advanced for Developers server on the Kubernetes cluster. The [configuration](#configuration) section lists the parameters that can be configured during installation.
|
||||
@@ -40,7 +40,7 @@ kubectl delete pvc -l release=foo
|
||||
```
|
||||
|
||||
## Configuration
|
||||
The following table lists the configurable parameters of the `mq-advancedserver` chart and their default values.
|
||||
The following table lists the configurable parameters of the `ibm-mq-dev` chart and their default values.
|
||||
|
||||
| Parameter | Description | Default |
|
||||
| -------------------------------- | ----------------------------------------------- | ---------------------------------------------------------- |
|
||||
@@ -14,6 +14,6 @@
|
||||
|
||||
apiVersion: v1
|
||||
description: IBM MQ queue manager
|
||||
name: mq-devserver
|
||||
name: ibm-mq-prod
|
||||
version: 1.0.0
|
||||
icon: https://developer.ibm.com/messaging/wp-content/uploads/sites/18/2017/07/IBM-MQ-Square-200.png
|
||||
icon: https://developer.ibm.com/messaging/wp-content/uploads/sites/18/2017/07/IBM-MQ-Square-200.png
|
||||
@@ -18,7 +18,7 @@ This chart deploys a single IBM MQ Advanced server (queue manager) into an IBM C
|
||||
To install the chart with the release name `foo`:
|
||||
|
||||
```bash
|
||||
helm install --name foo stable/mq-advancedserver --set license=accept
|
||||
helm install --name foo stable/ibm-mq-prod --set license=accept
|
||||
```
|
||||
|
||||
This command accepts the [IBM MQ Advanced license](LICENSE) and deploys an MQ Advanced server on the Kubernetes cluster. The [configuration](#configuration) section lists the parameters that can be configured during installation.
|
||||
@@ -40,7 +40,7 @@ kubectl delete pvc -l release=foo
|
||||
```
|
||||
|
||||
## Configuration
|
||||
The following table lists the configurable parameters of the `mq-advancedserver` chart and their default values.
|
||||
The following table lists the configurable parameters of the `ibm-mq-prod` chart and their default values.
|
||||
|
||||
| Parameter | Description | Default |
|
||||
| ------------------------------- | ----------------------------------------------- | ---------------------------------------------------------- |
|
||||
@@ -152,7 +152,7 @@ SET AUTHREC OBJTYPE(QMGR) GROUP('mqclient') AUTHADD(CONNECT,INQ)
|
||||
SET AUTHREC PROFILE('EXAMPLE.**') OBJTYPE(QUEUE) GROUP('mqclient') AUTHADD(INQ,PUT,GET,BROWSE)
|
||||
```
|
||||
|
||||
Next create a `Dockerfile` that expands on the MQ Advanced server image to create the users and groups. It should contain the following, replacing <IMAGE NAME> with the mqadvanced image you want to base this new image off:
|
||||
Next create a `Dockerfile` that expands on the MQ Advanced server image to create the users and groups. It should contain the following, replacing <IMAGE NAME> with the ibm-mq-prod image you want to base this new image off:
|
||||
|
||||
```
|
||||
FROM <IMAGE NAME>
|
||||
Reference in New Issue
Block a user