Hey there.
I was trying to use Kubernetes Environment Scopes under a free private repository inside gitlab.com.
Looking at Project-level Kubernetes clusters (certificate-based) (deprecated) | GitLab I saw the following:
"You can associate more than one Kubernetes cluster to your project. That way you can have different clusters for different environments, like dev, staging, production, and so on.
Simply add another cluster, like you did the first time, and make sure to set an environment scope that will differentiate the new cluster with the rest."
However, I saw right bellow that I can use different kubernetes clusters but environment scopes is available only at Premium.
My use case is: I have an AWS account for staging and other one for production and different clusters for each cluster type.
For having different clusters for different environments I normally would use environment scopes for it as the documentation mentions.
Would not make sense to move environment scopes to core as well so the description fits the proposed use case?
Thanks for your time reviewing this