metaphor for multicluster kubefirst platform

[johndietz]

What is your feature idea?

metaphor is going through a bit of an evolution in 2.3 that will require us to break main as we propagate multicluster out to all of the clouds. today (2.2) metaphor gets delivered to the management cluster in a development, staging, and production namespace. when we introduce cluster management in 2.3, the development, staging, and production spaces will become “environments” instead of namespaces, and environments will be optionally bound to workload clusters. the end result will be that you can have a management cluster that builds and sets the desired state of a development, staging, and production instance of metaphor, but it’ll be up to our users to decide what clusters should host which environments

Why is it needed?

developer apps go to workload clusters

Is this missing feature preventing you from using kubefirst?

• Yes

Code of Conduct

• I agree to follow this project's Code of Conduct