Ingress is an object that defines rules that are used to manage external access to the Services in a Kubernetes cluster. Typically, Ingress acts like a middleman between the internet and the Services running inside a cluster:
You will learn much more about Ingress and the major motivations for using it in Chapter 12, Your Application and HA. Due to this, we will not cover the implementation of Ingress here.
Now that we have learned about the different types of Services in Kubernetes, we will implement all of them to get an idea of how they would work together in a real-life scenario.
Activity 8.01: Creating a Service to Expose the Application Running on a Pod
Consider a scenario where the product team you're working with has created a survey application that has two independent and decoupled components – a frontend and a backend. The frontend component of the survey application renders the survey forms and needs...