Introduction
Lately I’ve been diving deeper into the inner workings of Kubernetes and plan to release multiples blogs on the various pieces that make a cluster “tick”. For starters, I thought I’d write a post on what exactly Kubernetes Custom Resources are and the very important role they play.
One of the more important features of the Kubernetes API is the ability to extend the resource types it will recognize. Out of the box you have Pod, Deployment, Service and so on, which are very useful for deploying your applications. However, there may come a time when you require additional functionality that can’t easily be accomplished with those resource types. This is where Custom Resources come in.
A resource is simply an endpoint that exists in the Kubernetes API that stores a collection of API objects of a certain type. So for our built-in Pod resource, we would have a collection of Pod objects.
A custom resource is an extension of the Kubernetes API
echo "This is a test code block"