Azure-docs: cluster-autoscaler deployment error -- no matches for kind "Deployment" in version "extensions/v1"

Created on 22 Oct 2018  Â·  16Comments  Â·  Source: MicrosoftDocs/azure-docs

When executing aks-cluster-autoscaler.yml, I am seeing below exception.

unable to recognize "D:\dockerbuild\aks-cluster-autoscaler.yml": no matches for kind "Deployment" in version "extensions/v1"

any changes required for apiVersion?


Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

assigned-to-author container-servicsvc doc-bug triaged

Most helpful comment

or apiVersion: apps/v1

All 16 comments

@bob999c Hi, can you please share more details about which document you are referring to? Thanks a lot!

content inside Deployment file.

apiVersion: extensions/v1
kind: Deployment
metadata:
labels:
app: cluster-autoscaler
name: cluster-autoscaler
namespace: kube-system
spec:
replicas: 1
selector:
matchLabels:
app: cluster-autoscaler
template:
metadata:
labels:
app: cluster-autoscaler
spec:
serviceAccountName: cluster-autoscaler
containers:
- image: gcr.io/google-containers/cluster-autoscaler:v1.2.2
imagePullPolicy: Always
name: cluster-autoscaler
resources:
limits:
cpu: 100m
memory: 300Mi
requests:
cpu: 100m
memory: 300Mi
command:
- ./cluster-autoscaler
- --v=3
- --logtostderr=true
- --cloud-provider=azure
- --skip-nodes-with-local-storage=false
- --nodes=3:10:nodepool1
env:
- name: ARM_SUBSCRIPTION_ID
valueFrom:
secretKeyRef:
key: SubscriptionID
name: cluster-autoscaler-azure
- name: ARM_RESOURCE_GROUP
valueFrom:
secretKeyRef:
key: ResourceGroup
name: cluster-autoscaler-azure
- name: ARM_TENANT_ID
valueFrom:
secretKeyRef:
key: TenantID
name: cluster-autoscaler-azure
- name: ARM_CLIENT_ID
valueFrom:
secretKeyRef:
key: ClientID
name: cluster-autoscaler-azure
- name: ARM_CLIENT_SECRET
valueFrom:
secretKeyRef:
key: ClientSecret
name: cluster-autoscaler-azure
- name: ARM_VM_TYPE
valueFrom:
secretKeyRef:
key: VMType
name: cluster-autoscaler-azure
- name: AZURE_CLUSTER_NAME
valueFrom:
secretKeyRef:
key: ClusterName
name: cluster-autoscaler-azure
- name: AZURE_NODE_RESOURCE_GROUP
valueFrom:
secretKeyRef:
key: NodeResourceGroup
name: cluster-autoscaler-azure
restartPolicy: Always

This is about AKS cluster node auto scaling.

@bob999c Please let us know the version of your AKS cluster

AKS 1.11.2.

try this apiVersion: extensions/v1beta1

or apiVersion: apps/v1

@bob999c Like @lukenny suggested we can use apiVersion: extensions/v1beta1.
Try with that and let us know. Meanwhile I will also deploy to my cluster and let you know the status.

@sakthivetrivel I deployed a cluster-autoscaler with the yaml file from the document. Like @bob999c mentioned i got an error. I changed the API version for deployments from v1 to v1beta1. After that I was able to deploy the cluster-autoscaler. API version app/v1 also works.
I also see that recently all the v1beta1 versions are changed to v1.
Please investigate further and make changes in the document as appropriate.

API app/v1 and v1/beta1 work for me but Im getting CrashLoopBackOff error

Events:
  Type     Reason     Age               From                               Message
  ----     ------     ----              ----                               -------
  Normal   Scheduled  2m                default-scheduler                  Successfully assigned kube-system/cluster-autoscaler-7b9f77c9cf-cb2jm to aks-nodepool1-29924583-4
  Normal   Pulling    35s (x4 over 2m)  kubelet, aks-nodepool1-29924583-4  pulling image "gcr.io/google-containers/cluster-autoscaler:v1.2.2"
  Normal   Pulled     35s (x4 over 1m)  kubelet, aks-nodepool1-29924583-4  Successfully pulled image "gcr.io/google-containers/cluster-autoscaler:v1.2.2"
  Normal   Created    33s (x4 over 1m)  kubelet, aks-nodepool1-29924583-4  Created container
  Normal   Started    33s (x4 over 1m)  kubelet, aks-nodepool1-29924583-4  Started container
  Warning  BackOff    1s (x6 over 1m)   kubelet, aks-nodepool1-29924583-4  Back-off restarting failed container

I even tried v1.3.3 no dice

v1/beta1 worked fine. Thank you.

AKS Cluster-autoscaler status struck in Initializing state.
Please see the below

D:\dockerbuild>kubectl -n kube-system describe configmap cluster-autoscaler-status
Name: cluster-autoscaler-status
Namespace: kube-system
Labels:
Annotations: cluster-autoscaler.kubernetes.io/last-updated=2018-10-25 16:43:49.278121089 +0000 UTC

Data

status:

Cluster-autoscaler status at 2018-10-25 16:43:49.278121089 +0000 UTC:
Initializing
Events:

when status move to ready status?

@bob999c Status should move to ready within minutes.
If its not, we need to look at the pods logs created by that deployment.
@bob999c @lukenny Please look at the pods logs.
I have deployed my autoscaler in kube-system namespace.

@jpconnock The author of this page is no longer available for assignment.
We need to change the API version in the Yaml file. Please suggest.
CC: @MicahMcKittrick-MSFT

Thanks issue got fixed.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

paulmarshall picture paulmarshall  Â·  3Comments

ianpowell2017 picture ianpowell2017  Â·  3Comments

JamesDLD picture JamesDLD  Â·  3Comments

Agazoth picture Agazoth  Â·  3Comments

spottedmahn picture spottedmahn  Â·  3Comments