Why Does kubectl get Show a Different API Group for a Resource Than Specified?

Sometimes, when you use the kubectl get command to retrieve Kubernetes resources, the API group and version shown may differ from what you originally specified in the resource specification. For instance, you might create a Deployment resource using the apps/v1 API group, but when you check the resource with kubectl get deployment -o yaml, it appears under the extensions/v1beta1 API group:

Original Deployment YAML:

apiVersion: apps/v1
kind: Deployment
[...]

Output of 'kubectl get deployment -o yaml':

apiVersion: extensions/v1beta1
kind: Deployment
[...]

Kubernetes resources, like Deployments, can exist in multiple API groups. If you don't specify an API group and version when using kubectl, it defaults to the first group listed in the Kubernetes API server's discovery documentation. In the current example, the Deployment resource is available under both the apps/v1 and extensions/v1beta1 API groups. For backward compatibility, the API server might list extensions/v1beta1 first.

To ensure that kubectl retrieves the resource from the desired API group, you can fully qualify the resource type. For example, to get Deployment resources from the apps API group, use 'kubectl get deployments.apps -o yaml'. To specify a particular version, you can use 'kubectl get deployments.v1.apps -o yaml'.