Thanks for the great post!

I am still wondering tho how would be the best way to actually create a new deployment from scratch to the GKE.

The cloudbuild.yamlin your article only sets the new built and deployed docker image into a current existing deployment in GKE by changing the deployment to the $REVISION_ID , but it fails if trying to set the image for an inexistent deployment.

What is the best way for me to keep the local kubernetes.yamlmanifest into control version updated as we release, but also be able to bootstrap it from scratch if needed from CI?

Should my cloudbuild.yaml also run kubectl apply -f . for example?

Should I deploy both $REVISION_ID and latest tags and keep the kubernetes.yamlfile using the latest tag of the docker image?

Then run kubectl apply -f . then kubectl set image ... in the cloudbuild.yaml ? (the later command is not even required since latest would get deployed)

This makes me feel a lil bit that running kubectl apply -f . is more appropriate to apply changes in a continuous matter.

Sorry if I made this quite confusing too, I am trying my best 😄

Thanks once again!

Armando is a Brazilian Software Engineer based in Amsterdam, currently working at Netflix as a Senior Software Engineer in EMEA.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store