Deploying to production

We already saw that prod.yml is almost the same as build.yml we deployed earlier, so there's probably no need to go through it in details. The only substantial difference is that we'll create the resources in the go-demo-3 Namespace, and that we'll leave Ingress to its original path /demo.

 1  kubectl -n go-demo-3-build \
 2      exec -it cd -c kubectl -- sh
 3
 4  cat k8s/prod.yml \
 5      | sed -e "s@:latest@:1.0@g" \
 6      | tee /tmp/prod.yml
 7
 8  kubectl apply -f /tmp/prod.yml --record

We used sed to convert latest to the tag we built a short while ago, and we applied the definition. This was the first release, so all the resources were created.

Subsequent releases will follow the rolling update process. Since that is something Kubernetes does out-of-the-box, the command will always be the same.

Next, we'll wait until...