From the course: Cloud Native Development with Node.js, Docker, and Kubernetes

Unlock the full course today

Join today to access over 24,200 courses taught by industry experts.

Liveness and readiness endpoints

Liveness and readiness endpoints

- [Instructor] So far, we've seen how we can take our application, create a docker image for it, package it with a Helm chart, and then deploy it to Kubernetes so that we have multiple instances running and Kubernetes is load-balancing across those instances. At this point though, our application is just cloud hosted. It's not yet cloud native because we're not doing anything to exploit the capabilities of the platform, and Kubernetes provides quite a number of capabilities. One of those is self healing. This is where Kubernetes will take an application that fails and replaces it and restarts it with a new instance. Now to do that, by default, it just looks to see whether our application is running inside the container. Whilst that's a reasonable thing to do, it does require a crash to occur or for our application to unexpectedly exit. There are many other scenarios where our application needs to be restarted that can't be detected that way. For example, if our application still…

Contents