This repository has been archived by the owner on May 3, 2022. It is now read-only.

Consider using labels & label selectors for cluster scheduling #244

Open

gmiroshnykov opened this issue Dec 9, 2019 · 0 comments

gmiroshnykov commented Dec 9, 2019

Currently Shipper only understands that clusters are running in "regions".

It also has an implicit assumption that multiple clusters inside the same region are running in different availability zones.

Moving to labels and label selectors would allow us to have arbitrary scheduling domains, similar to Kubernetes nodeSelector.

kanatohodets mentioned this issue

Target strategy steps to groups of clusters ('vertical' rollout progression) #252

Open

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.