<p>Trying to deploy pods in my kubernetes cluster and some of the pods are giving me an error of some storage problems. Screen shot is given below:<a href="https://i.stack.imgur.com/8eVCw.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/8eVCw.png" alt="Kubernetes Dashboard"></a></p>

<p>I am sure the problem is with one of my worker node. its not a problem with pulsar i think. i'll also share the YAML file here just for a clear view of what the problem is. 
Link to YAML File:<a href="https://github.com/apache/pulsar/blob/master/deployment/kubernetes/generic/k8s-1-9-and-above/zookeeper.yaml" rel="nofollow noreferrer">https://github.com/apache/pulsar/blob/master/deployment/kubernetes/generic/k8s-1-9-and-above/zookeeper.yaml</a> </p>

<p>I need help with the YAML file to tweek it arround a little, so that the pods can be created with existing requirements i have on my worker nodes. I'll be happy if you need more information.</p>

<p>Thanks in advance</p>

basit khan
<p>It looks like the affinity rules are preventing the pods from starting. In production, you want to make sure the Zookeeper pods (and other pod groups like BookKeeper) don't run on the same worker node, which is why those rules are configured that way. You can increase your Kubernetes setup to 3 worker nodes, or remove the affinity rules from the various stateful sets and deployment files.</p>

<p>Alternatively, you can use this Helm chart (full disclosure: I am the creator) to deploy Pulsar to Kubernetes:</p>

<p><a href="https://helm.kafkaesque.io" rel="nofollow noreferrer">https://helm.kafkaesque.io</a></p>

<p>See the section "Installing Pulsar for development" for settings that will enable Pulsar to run in smaller Kubernetes setups, including disabling affinity rules.</p>
