[英]Setup Kubeflow on minikube: No resources found in kubeflow namespace
当我尝试在本地桌面(Ubuntu 20.0.4)上使用 minikube 设置 kubeflow 并根据此官方文档运行kubectl create -f bootstrapper.yaml
时,我得到了AlreadyExists
以下错误。
来自服务器的错误(已存在):创建时出错
“bootstrapper.yaml”:命名空间“kubeflow-admin”已经存在错误
从服务器(已经存在):创建“bootstrapper.yaml”时出错:
persistentvolumeclaims “kubeflow-ksonnet-pvc” 已经存在 [无法
识别“bootstrapper.yaml”:没有匹配的种类
版本“rbac.authorization.k8s.io/v1beta1”中的“ClusterRoleBinding”,
无法识别“bootstrapper.yaml”:种类不匹配
版本“apps/v1beta2”中的“StatefulSet”]
删除命名空间和持久卷并运行相同的命令后,我收到了这个version
的错误消息。
命名空间/kubeflow-admin 创建
persistentvolumeclaim/kubeflow-ksonnet-pvc 创建无法识别
“bootstrapper.yaml”:没有匹配类型“ClusterRoleBinding”的
版本“rbac.authorization.k8s.io/v1beta1”无法识别
“bootstrapper.yaml”:版本中没有匹配类型“StatefulSet”的匹配项
“应用程序/v1beta2”
因此,我根据this将 ClusterRoleBinding 和 StatefulSet 的版本更改为 v1,然后出现此错误。
persistentvolumeclaim/kubeflow-ksonnet-pvc 创建
statefulset.apps/kubeflow-bootstrapper 创建了来自服务器的错误
(已经存在):创建“bootstrapper.yaml”时出错:
clusterrolebindings.rbac.authorization.k8s.io “kubeflow-cluster-admin”
已经存在
因此,我还删除了 clusterrolebindings kubeflow-cluster-admin
并重新运行kubectl create -f bootstrapper.yaml
。 然后,我得到了预期的结果。
namespace/kubeflow-admin created
clusterrolebinding.rbac.authorization.k8s.io/kubeflow-cluster-admin created
persistentvolumeclaim/kubeflow-ksonnet-pvc created
statefulset.apps/kubeflow-bootstrapper created
我检查了kubectl get ns
创建的命名空间的存在,然后
NAME STATUS AGE
default Active 8h
kube-node-lease Active 8h
kube-public Active 8h
kube-system Active 8h
kubeflow-admin Active 60s
kubernetes-dashboard Active 8h
但是,我No resources found in kubeflow namespace.
通过kubectl -n kubeflow get svc
我已经检查了这篇文章。 我等了很久,但我没有得到任何结果。
我运行docker images
然后没有gcr.io/kubeflow-images-public/bootstrapper:v0.2.0
。 因此,引导程序似乎失败了。
原装bootstrapper.yaml
---
# Namespace for bootstrapper
apiVersion: v1
kind: Namespace
metadata:
name: kubeflow-admin
---
# Make kubeflow-admin admin
apiVersion: rbac.authorization.k8s.io/v1beta1
kind: ClusterRoleBinding
metadata:
name: kubeflow-cluster-admin
subjects:
- kind: ServiceAccount
name: default
namespace: kubeflow-admin
roleRef:
kind: ClusterRole
name: cluster-admin
apiGroup: rbac.authorization.k8s.io
---
# Store ksonnet apps
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: kubeflow-ksonnet-pvc
namespace: kubeflow-admin
labels:
app: kubeflow-ksonnet
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 5Gi
---
apiVersion: apps/v1beta2
kind: StatefulSet
metadata:
name: kubeflow-bootstrapper
namespace: kubeflow-admin
spec:
selector:
matchLabels:
app: kubeflow-bootstrapper
serviceName: kubeflow-bootstrapper
template:
metadata:
name: kubeflow-bootstrapper
labels:
app: kubeflow-bootstrapper
spec:
containers:
- name: kubeflow-bootstrapper
image: gcr.io/kubeflow-images-public/bootstrapper:v0.2.0
workingDir: /opt/bootstrap
command: [ "/opt/kubeflow/bootstrapper"]
args: [
"--in-cluster",
"--namespace=kubeflow",
"--apply",
# change config here if you want to use customized config.
# "--config=/opt/kubeflow/default.yaml"
# app-dir: path to store your ks apps in pod's PersistentVolume
"--app-dir=/opt/bootstrap/default"
]
volumeMounts:
- name: kubeflow-ksonnet-pvc
mountPath: /opt/bootstrap
volumes:
- name: kubeflow-ksonnet-pvc
persistentVolumeClaim:
claimName: kubeflow-ksonnet-pvc
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.