Currently, the cicd pipeline is configured to pull the latest "geekzone/infra" image to use as the executor for the cicd pipeline.
We need to pin the image to a specific tag that we know works, which should be generated by a merge into main.
User Story
We want to use a specific tag (generated by merges into main in the "infra" repo) of the "geekzone/infra" image to run our cicd pipeline, so that we know it has been tested.
Currently, the cicd pipeline is broken because the "latest" image has the kubernetes cluster version not supported by Azure in the 'UK South' region.
Impact
High
Urgency
Now
Code of Conduct
[X] I agree to follow this project's Code of Conduct
What's your idea?
Currently, the cicd pipeline is configured to pull the latest "geekzone/infra" image to use as the executor for the cicd pipeline. We need to pin the image to a specific tag that we know works, which should be generated by a merge into main.
User Story
We want to use a specific tag (generated by merges into main in the "infra" repo) of the "geekzone/infra" image to run our cicd pipeline, so that we know it has been tested. Currently, the cicd pipeline is broken because the "latest" image has the kubernetes cluster version not supported by Azure in the 'UK South' region.
Impact
High
Urgency
Now
Code of Conduct