PVC on 2 node Deployment deployed with this helm chart #255
-
I'm using longhorn as my PVC storage class. I wan to run two pi-hole nodes as two separate master/master DNS nodes on K8s. What I had initially though to do is set the replica count to 2 but when I do that I get complaints because the same longhorn volume can not be mounted to two pods. Here is how I tried to setup my PVC:
How is this helm chart meant to be used? My work around: Instead I use the helm char once in two different name spaces. The upside of this is I get two completely separate IP addresses for DNS and the web socket. Then I can add two DNS servers to all my DNS clients. The downside is I cant figure out a way to use anti-affinity across namespaces/deployments to keep them off the same k8s node. Sometimes I just delete one and it pops up on another node but that is sub optimal Here is how I tried to setup antiaffinity. I set these on each helm deployment in each namespace:
I guess I'd actually prefer to know how to just keep these pods off the same node but still allow them to deploy to ANY node so long as another copy of the same type of pod isn't there. Baring that I'd love to know how to make my PVC not cause conflicts when using 2 replica count. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
This PR should resolve my issue: #256 |
Beta Was this translation helpful? Give feedback.
This PR should resolve my issue: #256