Joaquin Menchaca

I tried using `{{ .Release.Name }}` from with `{{ readFile "templates/common.yaml" }}`, and it yields an error: ``` err: failed to read helmfile.yaml: reading document at index 1: yaml: invalid...

Any update? I was able to do this with ```bash helm install test -f secrets.yaml -f config.yaml --dry-run --debug path/to/chart/ ```

Actually, they are saying just add `--listen` for services that need it, when running `chef-client -z` on the remote system. If I am reading this correctly, the fix is easy....

I changed the types of systems to that I don't run into the CPU quota. How about the static address? Another way, override it? Recommendations?

@adaumann RabbitMQ uses multiple ports, so likely the source of the problem is a single service resource that is listening on multiple ports. One way you determine this is is...

As consul-server is a StatefulSet, which uses external volumes (like AWS EBS for example), should a hardware VM fail, where a K8S node and the pods running on it are...

https://github.com/hashicorp/consul-k8s/issues/1612

From what I understand, a service with an advertised port is required for consul connect injector to configure envoy proxy and register the service in consul. This is required to...

@codex70 This is exactly my thoughts as well, because there are such a thing as a pure client scenario. Regardless, this is a hard requirement by Consul. The good news...

Is this the secret you can get with `kubectl get --namespace consul secrets/consul-bootstrap-acl-token --template={{.data.token}}`? One thing I hit is that if you ever deployed consul service mesh, and didn't delete...