I am adding topologySpreadConstraints as an option for a pod in the Pi-hole chart. This allows for ensuring a specific spread of pods across multiple availability zones (as defined by the user) and what to do in the case that the spread cannot be maintained. Related K8s documentation is here.
I have a mixed-architecture cluster at home and my primary use case is to ensure that at least one instance exists in each "Zone" of my cluster (or in this case, one in my virtualized instances (amd64) and one in my physical instances (arm64)).
I have bumped to 1.10.0 based on adding a new feature, but if there is a different version we need to bump to, please let me know and I am happy to update.
MoJo2600
commented
3 years ago
I am adding
topologySpreadConstraintsas an option for a pod in the Pi-hole chart. This allows for ensuring a specific spread of pods across multiple availability zones (as defined by the user) and what to do in the case that the spread cannot be maintained. Related K8s documentation is here.I have a mixed-architecture cluster at home and my primary use case is to ensure that at least one instance exists in each "Zone" of my cluster (or in this case, one in my virtualized instances (amd64) and one in my physical instances (arm64)).
I have bumped to 1.10.0 based on adding a new feature, but if there is a different version we need to bump to, please let me know and I am happy to update.