Support multiple environment scopes for Kubernetes Cluster
### Problem to solve I would like to use the same Kubernetes Cluster for multiple environments. ### Intended users Developer, Release Manager ### Further details It may be useful to deploy multiple environments to the same Kubernetes cluster. E.g. it is useful to have a staging and review environment, but using multiple clusters for this might not be worth the cost. ### Proposal 1. Make the environment scope comma separated. For example `staging,review/*` would mean Kubernetes deployments can be done for environments to `staging`, `review/foo`, and `review/bar`. 2. Use globs, not wildcards. The environment scope would then become `{staging,review/*}` 3. Add multiple fields for the environment scope. ### Permissions and Security ### Documentation ### Testing ### What does success look like, and how can we measure that? ### Links / references
issue