python-getting-started
python-getting-started copied to clipboard
build image and use kustomize on the fly
A user brought up the fact that if you take this sample, change a file, commit, and then deploy on cloud, the latest code doesn't get applied. What do you think about this pattern for the getting-started samples? That way they work as-is on any Kube cluster, but on Okteto-powered clusters, the image is built.