Unable to run v0.2.0 in minikube. "pod has unbound PersistentVolumeClaims" about consul-helm

[s3than]

@mitchellh Is there anything I can provide to get this item resolved?

Making affinity a variable allows testing on Minikube

Thanks

[kohv]

I had to remove affinity rules on the StatefulSet, here

consul-helm/templates/server-statefulset.yaml

Line 40 in 100d14e

affinity:

After removing that anti-affinity rule, I was able to successfully launch consul server & consul-ui. I'm very new to k8s, but it seems to me that the anti-affinity rules are conflicting when running multiple consul server agents?

[ervikrant06]

Yes, I also hit the same issue this is happening because of affinity rules only. for redundancy purpose they want to start the single consul server on each node.

[mitchellh]

This seems like two things:

• We need docs to state you'll need at least N distinct nodes available where N is the number of Consul servers.
• OR: you need to get rid of the affinity rules. We need to add configuration to allow this.

[s3than]

We resolved this issue by making the affinity a variable

    {{- if .Values.affinity }}
      affinity:
{{ tpl .Values.affinity . | indent 8 }}
{{- end }}

And then in the values

### Consul Settings
affinity: |
  podAntiAffinity:
    preferredDuringSchedulingIgnoredDuringExecution:
      - labelSelector:
          matchLabels:
            app: {{ template "consul.name" . }}
            release: "{{ .Release.Name }}"
            component: server
        topologyKey: kubernetes.io/hostname

This then means in minikube you can override with

## Affinity settings, this allows us to configure and run in Minikube
affinity: |
  podAntiAffinity:
    preferredDuringSchedulingIgnoredDuringExecution:
    - weight: 1
      podAffinityTerm:
        topologyKey: kubernetes.io/hostname
        labelSelector:
          matchExpressions:
          - key: component
            operator: In
            values:
            - "{{ .Release.Name }}-{{ .Values.Component }}"

[adilyse]

Thanks to @s3than, server affinity is now configurable in the values file! Additional documentation will be added once this PR in the Consul repository is merged.