Closed damemi closed 5 months ago
@quentinmit
I'll leave the approval to quentin
We would need something slightly different for presubmits, right? Since those will also run tests and tear down. Or will those be separate cloud build files?
Yes this is separate from the presubmits. All this does is continuously deploy to the same cluster specified in the trigger.
This might not even redeploy the existing pods if there isn't a change to those, so that will probably be a follow up to this. I just want something basic first to test that we can deploy like this
Does this deploy with newly-built images, or does it use images built by upstream?
@dashpole this just uses the images from upstream, that's my goal right now. We don't actually have a need to build our own images yet, and we haven't figured that out for this repo itself, so getting both of those sorted out first will come before adding it to the automation.
This uses the
kubectl apply
steps to deploy the demo to a GKE cluster. The cluster name is set in a substitution in the GCP project to prevent leaking that info, and to allow other users to re-use this file.