Design Artifact: Group-level Kubernetes page
At project level, we have CI/CD > Cluster page to create (and then use) a cluster on GKE. This page will be extended further to support more functions.
It is still impossible to define the same cluster for different projects in the same group, but this could be a very important feature for organizations that can set up a single cluster and make it available group-wide.
Add a CI/CD > Cluster page at group level, that is similar to the project level one.
But there are questions that should be considered:
- project namespace must be unique in the cluster, so it still should be specified at project level
- enable/disable the cluster integration will enable/disable the access to projects?
- how to show the availability of the group-level cluster at project level?
- security implications of different projects on the same cluster