Ability to "opt out" of Kubernetes clusters at the project-level
Proposal
Allow a project to "opt out" of using a Kubernetes cluster configured at the group or instance-level.
Why
If a Kubernetes cluster is configured at a group or instance level, sub-projects have no way to not use the cluster. This can be a problem as having a Kubernetes cluster present changes how some features work (e.g. deploying to an environment).
Internal example
I was attempting testing a deployment-related feature on staging.gitlab.com
, but my deployment jobs were failing with the error message This job failed because the necessary resources were not successfully created
. This was caused by an misconfigured instance-level Kubernetes cluster. I had no way to opt out of the Kubernetes deploy and execute a "basic" (non-Kubernetes) deployment job.