Determine if we should remove special logic for Container Registry deployments
In k8s-workloads/gitlab-com we specify the specific version of the Container Registry to be running. Can we remove this logic and rely on our natural auto-deployment mechanism?
The goal here would be that when the Container Registry releases new versions, our current auto-deploy process will select the appropriate version and it be built via CNG already, and subsequently released via auto-deploy as most of our other components already do.
Milestones
-
Discussion reveals that we are okay with this process -
Research completed -
Versioning logic removed -
Auto-deploy confirmed to work as desired