Group-level Kubernetes clusters information
Hello,
I have a Group-level Kubernetes clusters created through gitlab.com on AWS.
I have a number of projects within the group.
I am not an expert on kuberenetes for this, before opening a real issue I would like to ask you if the operation I noticed is normal.
I have projects that use auto devops for cluster deployment. For these projects I noticed that roles, secret, rolebinding etc. persist on the cluster also for merge-requests / deploy now closed. Is this normal?
In practice, I also continue to view namespace roles such as:
my-project-16239554-review-13-ui-ux-m-iiwj8n
(merge request now resolved and without an active environment)
I also have projects that don't use auto devops and are released on aws with a gitlab-ci via serverless.
Also for these projects, which do not need to be released on the cluster, I notice that roles, secret, rolebinding etc. are created.
I repeat, I'm not an expert and I don't know if this could be a problem on the cluster nor if there is a way to avoid mainly this second point.
I leave it to you to deduce.
Thank you
Activity
mentioned in issue gitlab-org/quality/triage-reports#1 (closed)
mentioned in issue gitlab-org/quality/triage-reports#2 (closed)
mentioned in issue gitlab-org/quality/triage-reports#4 (closed)
Based on the information given, this issue is out of the scope of the Issue tracker (which is for Bug Reports and Feature Proposals). Unfortunately, I won't be able to help get it resolved. However, there are plenty of resources that you can use to find help and support from the Community, including:
If you believe this was closed in error, please re-open the issue and fill out the "Bug" template in the description as completely as possible, so that we may better evaluate the problem.
added support request label
