So far we have spent most of our time understanding the basic Kubernetes concepts and simple workflows to build a solid foundation. In this chapter we will briefly cover a limited number of advanced topics.
Among the Service Types the NodePort and LoadBalancer are most often used. In this chapter, we will explore the Ingress API resource, which represents a layer of abstraction deployed in front of the Service API, offering a unified method of managing access to our application from the external world.
While Deploying an application, we may need to pass runtime paramaters like passwords, config details, or passwords. We can use the ConfigMap for runtime parameters and for sensitive Information we can use the Secret API resource.
Kubernetes uses Volumes of several types and few other forms of storage resources for container data management. In this chapter, we will learn about PersistentVolume and PersistenVolumeClaim objects, which helps us attach persistent storage Volumes to Pods.
In this chapter, we will learn about Service objects used to abstract the communication between cluster internal microservices, or with the external world. We will also learn about the kube-proxy daemon which implemets the services configuration and provide access to services.
Every API request reaching the API server has to go through several control stages before being accepted. We are going to learn about Authentication, Authorization and Admission Control stages of the API access control.