Improve configuration only changes to k8s-workloads/gitlab-com
When configuration/secret changes happen outside of the k8s-workloads/gitlab-com repository, we are currently lacking in documentation associated with how to apply those changes into the Kubernetes cluster. We used to enforce that persons provide an empty commit such that pipelines run with an MR entitled to indicate the desired change. However, after gitlab-com/gl-infra/k8s-workloads/gitlab-com!233 (merged), an empty commit no longer suffices as the pipeline does not create the necessary jobs to ensure Kubernetes configurations/secrets are modified.
One can view an example of this from this empty commit MR: gitlab-com/gl-infra/k8s-workloads/gitlab-com!333 (merged)
This was corrected by abusing the *.yaml
declaration with this MR here: gitlab-com/gl-infra/k8s-workloads/gitlab-com!334 (merged)
Which was later reverted in another MR: gitlab-com/gl-infra/k8s-workloads/gitlab-com!335 (merged)
Utilize this issue to accomplish the following:
- Come up with a new/better/different/more exciting method of applying configuration change outside of this project into Kubernetes infrastructures
- Ensure we have well documented this procedure