Play with the Sample API Server
Explore how to deploy a sample aggregated API server to extend Kubernetes APIs with custom resource types. Understand the configuration of the kube-aggregator component, TLS certificates, and authentication for API aggregation. Gain hands-on experience testing and managing custom APIs within the Kubernetes cluster.
We'll cover the following...
Overview
Aggregated API servers are usually built with the generic API server library k8s.io/apiserver. They run as stand-alone processes serving API groups with multiple versions. They could run inside or outside of the cluster. In the former case, they run as Pods, with a service in the front. By declaring an APIService object, we can hook our aggregated apiservers up to the kube-apiserver, which can make them work coherently. In the APIService object, we can correlate a service to indicate the accessible endpoint of our aggregated apiservers. If they are running in the cluster, the service could be a normal ClusterIP service. If running outside of a Kubernetes cluster, the service could also be an ExternalName service.
In this lesson, we’re going to deploy a sample aggregate apiserver and take a closer look at what aggregated apiservers look like. Seeing is believing. Then we’ll know how to implement our own aggregated apiservers. ...