K
Q

apiversion changed after kubectl create

1/24/2018

In kubernetes 1.8, when I create a deployment for example

apiVersion: apps/v1beta2 # for versions before 1.8.0 use apps/v1beta1
kind: Deployment
metadata:
  name: nginx-deployment
  labels:
    app: nginx
spec:
  replicas: 3
  selector:
    matchLabels:
      app: nginx
  template:
    metadata:
      labels:
        app: nginx
    spec:
      containers:
      - name: nginx
        image: nginx:1.7.9
        ports:
        - containerPort: 80

Then when I do a

kubectl get deploy nginx-deployment -o yaml

I got

apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  annotations:
    deployment.kubernetes.io/revision: "1"
  creationTimestamp: 2018-01-24T01:01:01Z

....

Why the apiversion is extension/v1beta1 instead of apiVersion: apps/v1beta2

-- Huy Le
kubernetes

Similar Questions

Failed to pull image "gcr.io/blah/blah":
How to remove host header
command to output map of cluster / node / public IPs
How does the kubernetes scheduler know what HostPorts are used on what Hosts?

2 Answers

1/24/2018

You might use an old version of kubectl. If so, please upgrade your kubectl to 1.8, then create the deployment again.

-- Yan
Source: StackOverflow
1/24/2018

When you create a deployment, the apiserver persists it and is capable of converting the persisted deployment into any supported version.

kubectl get deployments actually requests the extensions/v1beta1 version (you can see this by adding --v=6)

To get apps/v1beta2 deployments, do kubectl get deployments.v1beta2.apps

-- Jordan Liggitt
Source: StackOverflow