Pod stuck in Pending state after using custom release name in Helm

4/25/2018

Apologize if this comes under basic. I am using stable/rabbitmq community helm chart to install. But whenever I changed release name using --name option in install like helm install --name rabbitmq stable/rabbitmq, it gives this error: 0/7 nodes are available: 1 PodToleratesNodeTaints, 7 MatchNodeSelector and hangs indefinitely. And if default/auto generated name is used then it creates release. I don't want to use default release name as it creates unpredictable service name as well. Can someone please help me understanding this? Or is there a way to solve it.

Thanks in advance.

-- Swapnil B.
kubernetes
kubernetes-helm

0 Answers