You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Total new guy to Kubernetes and HA in general but I ran into a problem when, if I lost a node for updates, it was possible to lose my traefik instance if the scheduler put all three pods on that one node. I inserted these lines at the bottom of the traefik values.yaml file and updated the traefik deployment and now it spreads my three replicas across three different nodes in the cluster. I haven't figured out how to get the pod scheduled on the node I take down to spin back up on a different running node so if you guys have any ideas, that would be awesome!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Total new guy to Kubernetes and HA in general but I ran into a problem when, if I lost a node for updates, it was possible to lose my traefik instance if the scheduler put all three pods on that one node. I inserted these lines at the bottom of the traefik values.yaml file and updated the traefik deployment and now it spreads my three replicas across three different nodes in the cluster. I haven't figured out how to get the pod scheduled on the node I take down to spin back up on a different running node so if you guys have any ideas, that would be awesome!
affinity:
podAntiAffinity:
requiredDuringSchedulingIgnoredDuringExecution:
- labelSelector:
matchLabels:
app.kubernetes.io/name: '{traefik}'
app.kubernetes.io/instance: '{traefik-traefik}'
topologyKey: kubernetes.io/hostname
Beta Was this translation helpful? Give feedback.
All reactions