DevOps with Kubernetes - Second Edition

Managing rollouts

Once the rollout process is triggered, Kubernetes silently completes all tasks in the background. Let's try some hands-on experiments. Again, the rolling update process won't be triggered even if we've modified something with the commands mentioned earlier, unless the associated pod's specification is changed. The example we prepared is a simple script that will respond to any request with its hostname and the Alpine version it runs on. First, we create deployment and check its response in another Terminal:

$ kubectl apply -f ex-deployment.ymldeployment.apps/my-app createdservice/my-app-svc created$ kubectl proxy &[1] 48334Starting to serve on 127.0.0.1:8001## switch to another terminal, #2$ while :; do curl http://localhost:8001/api/v1/namespaces/default/services/my-app-svc:80/proxy/; ...