Group-level Cluster page

Description

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.

Proposal

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?

Documentation blurb

Overview

What is it? Why should someone use this feature? What is the underlying (business) problem? How do you use this feature?

Use cases

Who is this for? Provide one or more use cases.

Feature checklist

Make sure these are completed before closing the issue, with a link to the relevant commit.

• Feature assurance
• Documentation
• Added to features.yml

/cc @bikebilly

mentioned in issue gitlab-foss#31218 (moved)

changed the description

changed the description

mentioned in issue gitlab-foss#34777 (closed)

mentioned in issue gitlab-foss#35616 (moved)

mentioned in issue gitlab-foss#35956

@bikebilly Would it make sense first to get rid of Kubernetes/integration and extend Cluster implementation to be a full replacement for Kubernetes/integration? Otherwise we might not be able to do it cleanly with current way of handling data.

Yes. As we move into direction of making Kubernetes integration a first-class thing.

added Deliverable in GitLab FOSS label

changed milestone to %10.3

changed milestone to %10.3

moved from gitlab-foss#34758 (moved)