no matches for kind “Deployment” in version "extensions/v1beta1 問題解決
# 查看當前k8s支持的對象 kubectl api-versions | grep deployment kubectl api-versions | grep -i apps # 修改deployment apiVersion # 增加 selector ...
原文：no matches for kind "Deployment" in version "extensions/v1beta1"
x Problem x Solution 修改 apiVersion 選項： apps v 因為我的 k s 版本是 . . ，在這個版本中 Deployment 已經從 extensions v beta 棄用 DaemonSet, Deployment, StatefulSet, and ReplicaSet resources will no longer be served from e ...
2019-11-01 21:23 0 8629 推薦指數：
相關推薦
no matches for kind "ReplicaSet" in version "extensions/v1beta1"
原來的yaml的資源清單為 運行的時候，直接報錯 解決：查看版本 修改成 apiVersion: apps/v1 各種apiVersion的含義 alpha beta stable ...
no matches for kind "Deployment" in version "apps/v1beta1"
修改為： apiVersion: apps/v1kind: Deploymentmetadata: name: redis namespace: kube-ops labels: name: redisspec: selector: matchLabels ...
depolyment報錯error: unable to recognize "nfs-client-deployment.yaml": no matches for kind "Deployment" in version "extensions/v1beta1" 是deployment
$ kubectl api-resources | grep deployment deployments deploy apps true Deployment ...
unable to recognize "*.yaml": no matches for kind "RoleBinding" in version "rbac.authorization.k8s.io/v1beta1"
問題的原因為資源文件的版本定義過期了。需要修改下 修改下版本 ...
Error: unable to build kubernetes objects from release manifest: [unable to recognize "": no matches for kind "*" in version
helm 安裝遇到 K8s中RBAC權限處理在Kubernetes的1.5版本中引入，在1.6版本時升級為Beta版本，在1.8版本時升級為GA。所以資源文件的定義和集群版本不兼容導致的，一般為集群版本太高了，不支持資源對象版本了 對於上面問題，直接找集群對應的版本修改即可 查看當前 ...
Error: failed to install CRD crds/crd-alertmanager.yaml: unable to recognize "": no matches for kind "CustomResourceDefinition" in version
我的問題是在K8s集群安裝 prometheus-operator 報這個錯 問題的原因 我的集群版本太高了，1.22的版本，而且 prometheus-operator 之后的版本改 ...
Kubectl 創建 Deployment 錯誤 Deployment in version "v1" cannot be handled as a Deployment.....
”: Deployment in version “v1” cannot be handled as a Deploy ...