1.11. Troubleshooting application Kubernetes deployment version
A managed cluster with a deprecated Kubernetes apiVersion
might not be supported. See the Kubernetes issue for more details about the deprecated API version.
1.11.1. Symptom: Application deployment version 复制链接链接已复制到粘贴板!
If one or more of your application resources in the Subscription YAML file uses the deprecated API, you might receive an error similiar to the following error:
failed to install release: unable to build kubernetes objects from release manifest: unable to recognize "": no matches for kind "Deployment" in version "extensions/v1beta1"
failed to install release: unable to build kubernetes objects from release manifest: unable to recognize "": no matches for
kind "Deployment" in version "extensions/v1beta1"
Or with new Kubernetes API version in your YAML file named old.yaml
for instance, you might receive the following error:
error: unable to recognize "old.yaml": no matches for kind "Deployment" in version "deployment/v1beta1"
error: unable to recognize "old.yaml": no matches for kind "Deployment" in version "deployment/v1beta1"
Update the
apiVersion
in the resource. For example, if the error displays for Deployment kind in the subscription YAML file, you need to update theapiVersion
fromextensions/v1beta1
toapps/v1
.See the following example:
apiVersion: apps/v1 kind: Deployment
apiVersion: apps/v1 kind: Deployment
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Verify the available versions by running the following command on the managed cluster:
kubectl explain <resource>
kubectl explain <resource>
Copy to Clipboard Copied! Toggle word wrap Toggle overflow -
Check for
VERSION
.