What's Next?
Recap what we have explored so far and what we are going to learn next.
We'll cover the following
Summary#
We explored some of the essential functions of Ingress resources and Controllers. To be more concrete, we examined almost all those that are defined in the Ingress API.
One notable feature we did not explore is TLS configuration. Without it, our services cannot serve HTTPS requests. To enable it, we’d need to configure Ingress to offload SSL certificates.
There are two reasons we did not explore TLS. For one, we do not have a valid SSL certificate. On top of that, we did not yet study Kubernetes Secrets. We’d suggest you to explore SSL setup yourself once you make a decision which Ingress controller to use. Secrets, on the other hand, will be explained soon.
We’ll explore other Ingress Controllers once we move our cluster to “real” servers that we’ll create with one of the hosting vendors. Until then, you might benefit from reading NGINX Ingress Controller documentation in more detail. Specifically, I suggest you pay close attention to its annotations.
The above illustration shows and defines the Kubernetes components we have explored so far.
ℹ️ If you’d like to know more about Ingress, please explore Ingress v1beta1 extensions API documentation.
In the next chapter, we’ll explore how to access the host’s file system using volumes.
