This is one of the numerous posts by TechCommanders in a series for studying for the Certified Kubernetes Administrator (CKA) Exam. Become a Certified Kubernetes Administrator (CKA)!

In this post, we will explore API and interact with it by sending the REST requests without using kubectl. When we are using Kubernetes we can have multiple API versions on different API Paths, such as/API/v1 or /APIs/extensions/v1beta2.

The versioning of API is important as it shows different stability and support levels on each version.

• **Alpha Level: **This version’s names contain alpha. Like v1alpha. This version can contain bugs and it’s disabled by default. This version can contain backend changes that are not compatible with current changes. And the support for any feature can be dropped at any moment.
• **Beta Level: **The version name contains the word “Beta” like apiv1Beta. In this, the code is tested properly, and enabling or making this feature live is considered safe. That’s why it’s enabled by default. Support for the overall feature is not dropped, though details may change.
• Stable Level: The version name is in structure VX where X stands for an integer. The stable version of features will appear in released software for many subsequent versions.

So, after reading about API levels. Let’s explore what API groups are.

#development #kubernetes-cluster #kubernetes #devops #cka