We need a way to promote changes to prod that doesn't involve manual run of kubectl commands (prone to human errors).
Especially from the frontend team they have two microservices (daggregation and dexinfo) and they want to be able to deploy those independently.
The full CD pipeline would be to use a generated staging.json file that gets promoted to a prod.json file, containing all the deployed images tags. But since we are not there, maybe we can write a simpler action that takes repo and service names and image tag as params, and then deploys that image to prod.
We need a way to promote changes to prod that doesn't involve manual run of kubectl commands (prone to human errors). Especially from the frontend team they have two microservices (daggregation and dexinfo) and they want to be able to deploy those independently.
The full CD pipeline would be to use a generated
staging.jsonfile that gets promoted to aprod.jsonfile, containing all the deployed images tags. But since we are not there, maybe we can write a simpler action that takes repo and service names and image tag as params, and then deploys that image to prod.