Allow a single environment to deploy to multiple Kubernetes clusters
Problem to solve
Deploying to a single K8S cluster is great, but some teams need redundancy and the ability to spread a single environment to multiple K8S clusters (whether in the same cloud provider or across multiple cloud providers as well).
Target audience
Release Manager
Proposal
I'd like to see the ability to define multiple clusters an environment will consist of and have that reflected in the K8S Deploy Boards showing the pods within each defined cluster.
This issue is the result of an internal Slack conversation around a tool one of our customers wrote to handle this kind of thing... https://github.com/bookingcom/shipper
Kubernetes is a wonderful platform, but implementing mature rollout strategies on top of it requires subtle multi-step orchestration: Deployment objects are a building block, not a solution.
When implemented as a set of scripts in CI/CD systems like Jenkins, GitLab, or Brigade, these strategies can become hard to debug, or leave out important properties like safe rollbacks.
These problems become more severe when the rollout targets multiple Kubernetes clusters in multiple regions: the complex, multi-step orchestration has many opportunities to fail and leave clusters in inconsistent states.