Node failures

Intentionally (to save costs) or unintentionally, nodes can go down. When that happens, you don't want to get the proverbial 3AM call when Kubernetes can handle it automatically for you instead. In this exercise, we are going to bring a node down in our cluster and see what Kubernetes does in response:

  1. Ensure that your cluster has at least two nodes:

  1. Check that your URL is working as shown in the following output, using the external IP to reach the frontend:
kc get svcNAME           TYPE           CLUSTER-IP     EXTERNAL-IP     PORT(S)        AGEfrontend       LoadBalancer   10.0.196.116   EXTERNAL-IP   80:30063/TCP   14h
  1. Go to http://<EXTERNAL-IP>:
  1. Let's see where ...

Get Hands-On Kubernetes on Azure now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.