RabbitMQ - 'Expand manifest template' steps seem broken

[Geza Kerecsenyi]

Category:

Kubernetes apps

Type:

• Bug
• Feature Request
• Process

---

I have followed the steps to Install from the command line by cloning the repository, cding into it, and setting the exports. I am using the default namespace, but don't need RBAC, so I am currently trying the steps to Expand the manifest template.

I have run step 1, which completed successfully. However, when running step 2, I get:

Error: unknown flag: --name

When I remove the --name "$APP_INSTANCE_NAME" line, it completes successfully - but now, when I try applying the changes, I get:

@cloudshell:~/click-to-deploy/k8s/rabbitmq (gym-happy)$ kubectl apply -f "${APP_INSTANCE_NAME}_manifest.yaml" --namespace "${NAMESPACE}"
Error from server (Invalid): error when creating "rabbitmq-1_manifest.yaml": Secret "RELEASE-NAME-rabbitmq-secret" is invalid: metadata.name: Invalid value: "RELEASE-NAME-rabbitmq-secret": a DNS-1123 subdomain must consist of lower case alphanu
meric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')
Error from server (Invalid): error when creating "rabbitmq-1_manifest.yaml": ConfigMap "RELEASE-NAME-rabbitmq-config" is invalid: metadata.name: Invalid value: "RELEASE-NAME-rabbitmq-config": a DNS-1123 subdomain must consist of lower case alph
anumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')
Error from server (Invalid): error when creating "rabbitmq-1_manifest.yaml": Service "RELEASE-NAME-rabbitmq-discovery" is invalid: metadata.name: Invalid value: "RELEASE-NAME-rabbitmq-discovery": a DNS-1035 label must consist of lower case alph
anumeric characters or '-', start with an alphabetic character, and end with an alphanumeric character (e.g. 'my-name',  or 'abc-123', regex used for validation is '[a-z]([-a-z0-9]*[a-z0-9])?')
Error from server (Invalid): error when creating "rabbitmq-1_manifest.yaml": Service "RELEASE-NAME-rabbitmq-svc" is invalid: metadata.name: Invalid value: "RELEASE-NAME-rabbitmq-svc": a DNS-1035 label must consist of lower case alphanumeric cha
racters or '-', start with an alphabetic character, and end with an alphanumeric character (e.g. 'my-name',  or 'abc-123', regex used for validation is '[a-z]([-a-z0-9]*[a-z0-9])?')
Error from server (Invalid): error when creating "rabbitmq-1_manifest.yaml": StatefulSet.apps "RELEASE-NAME-rabbitmq" is invalid: metadata.name: Invalid value: "RELEASE-NAME-rabbitmq": a DNS-1123 subdomain must consist of lower case alphanumeri
c characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')
Error from server (Invalid): error when creating "rabbitmq-1_manifest.yaml": Application.app.k8s.io "RELEASE-NAME" is invalid: metadata.name: Invalid value: "RELEASE-NAME": a DNS-1123 subdomain must consist of lower case alphanumeric characters
, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')

I'm not sure where I've gone wrong, since I think I've followed the steps as faithfully as possible. The only difference I can find is the removal of the --name line - but when this is present, it doesn't run at all.

Any help would be appreciated! I have marked this as a 'bug' since I believe that it's an issue with the documentation, but do correct me if it's something I've messed up.

[Armando Miani]

@gezakerecsenyi , thank you for your collaboration.

Well, the helm template command in Helm 3 version should be called as:

helm template "${APP_INSTANCE_NAME}" \     # which is the release name
    --namespace "${NAMESPACE}" \
    --set ...

The command above will solve your issue.

The PR #1224 is fixing the README.

Best,