Improve chart parameters and doc

charts/mq-advancedserver/README.md

@@ -25,9 +25,6 @@ This command accepts the [IBM MQ Advanced license](LICENSE) and deploys an MQ Ad
 
 > **Tip**: See all the resources deployed by the chart using `kubectl get all -l release=foo`
 
-## Verifying the Chart
-See NOTES.txt associated with this chart for verification instructions
-
 ## Uninstalling the Chart
 
 To uninstall/delete the `foo` release:
@@ -57,7 +54,7 @@ The following table lists the configurable parameters of the `mq-advancedserver`
 | `data.persistence.size`         | Size of data volume                             | `2Gi`                                                      |
 | `service.name`                  | Name of the Kubernetes service to create        | `qmgr`                                                     |
 | `service.type`                  | Kubernetes service type exposing ports, e.g. `NodePort`       | `ClusterIP`                                  |
-| `queuemanager.name`                  | MQ Queue Manager name       | Helm release name                                  |
+| `queueManager.name`                  | MQ Queue Manager name       | Helm release name                                  |
 
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`.
 
@@ -69,6 +66,16 @@ Alternatively, a YAML file that specifies the values for the parameters can be p
 
 The chart mounts a [Persistent Volume](http://kubernetes.io/docs/user-guide/persistent-volumes/).
 
+
+# Configuring MQ objects
+You have two major options for configuring the MQ queue manager itself:
+
+1. Use existing tools, such as `runmqsc`, MQ Explorer or the MQ Command Server to configure your queue manager directly.
+2. Create a new image with your configuration baked-in 
+
+## Configuring MQ objects with a new image
+You can create a new container image layer, on top of the IBM MQ Advanced base image.  You can add MQSC files to define MQ objects such as queues and topics, and place these files into `/etc/mqm` in your image.  When the MQ container starts, it will run any MQSC files found in this directory (in sorted order).
+
 # Copyright
 
 © Copyright IBM Corporation 2017

charts/mq-advancedserver/templates/service.yaml

@@ -25,8 +25,6 @@ spec:
   type: {{ .Values.service.type }}
   ports:
   - port: 1414
-    name: {{ .Values.service.name }}-1
-    #  - port: 9443
-    #name: {{ .Values.service.name }}-2
+    name: {{ .Values.service.name }}-server
   selector:
     app: {{ template "fullname" . }}

charts/mq-advancedserver/templates/stateful-set.yaml

@@ -43,12 +43,11 @@ spec:
           imagePullPolicy: {{ .Values.image.pullPolicy }} 
           ports:
           - containerPort: 1414
-          #- containerPort: 9443
           env:
           - name: LICENSE
             value: {{ .Values.license }}
           - name: MQ_QMGR_NAME
-            value: {{ .Values.queuemanager.name | default .Release.Name | replace "-" "" }}
+            value: {{ .Values.queueManager.name | default .Release.Name | replace "-" "" }}
           {{- if .Values.data.persistence.enabled }}
           volumeMounts:
           - mountPath: "/mnt/mqm"

charts/mq-advancedserver/values.yaml

@@ -43,7 +43,9 @@ resources:
   requests:
     cpu: 1
     memory: 1Gi
-queuemanager:
+# queueManager section specifies settings for the MQ Queue Manager
+queueManager:
+  # name allows you to specify the name to use for the queue manager.  Defaults to the Helm release name.
   name:
 # nameOverride can be set to partially override the name of the resources created by this chart
 nameOverride: