标题好像没法改了,在Kubernetes 1.17 安装的是Kubesphere 2.1.1 。
最初部署时按照最小化部署的,后面想添加应用管理功能,就将
openpitrix:
enabled: True
开始安装。
但是有一些 Pod 一直起不来
$ kubectl get pod -n openpitrix-system
NAME READY STATUS RESTARTS AGE
hyperpitrix-release-app-job-s7c2b 0/1 Init:0/2 0 14m
openpitrix-hyperpitrix-deployment-6df877b655-rhjlw 1/1 Running 0 95m
openpitrix-rp-kubernetes-deployment-cbb6786f7-spmzk 0/1 Init:1/2 0 15m
$ kubectl describe pod -n openpitrix-system openpitrix-rp-kubernetes-deployment-cbb6786f7-spmzk
....
wait-runtime-manager:
Container ID: docker://703ea8645dc57bfd615e7f200843b2a894d730dbd28ed8dccc18f3df9edf4eae
Image: alpine:3.10.4
Image ID: docker-pullable://alpine@sha256:7c3773f7bcc969f03f8f653910001d99a9d324b4b9caa008846ad2c3089f5a5f
Port: <none>
Host Port: <none>
Command:
sh
-c
until nc -z openpitrix-rp-manager.openpitrix-system.svc 9121; do echo "waiting for runtime-manager"; sleep 2; done;
State: Running
Started: Fri, 03 Apr 2020 16:04:39 +0800
Ready: False
Restart Count: 0
Environment: <none>
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from default-token-ddgcx (ro)
Containers:
openpitrix-rp-kubernetes:
Container ID:
Image: openpitrix/runtime-provider-kubernetes:v0.1.3
Image ID:
Port: 9121/TCP
Host Port: 0/TCP
Command:
runtime-provider
State: Waiting
Reason: PodInitializing
Ready: False
Restart Count: 0
Limits:
cpu: 500m
memory: 500Mi
Requests:
cpu: 100m
memory: 100Mi
Environment:
OPENPITRIX_GRPC_SHOW_ERROR_CAUSE: true
OPENPITRIX_LOG_LEVEL: debug
OPENPITRIX_ETCD_ENDPOINTS: etcd.kubesphere-system.svc:2379
OPENPITRIX_MYSQL_HOST: mysql.kubesphere-system.svc
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from default-token-ddgcx (ro)
Conditions:
Type Status
Initialized False
Ready False
ContainersReady False
PodScheduled True
Volumes:
default-token-ddgcx:
Type: Secret (a volume populated by a Secret)
SecretName: default-token-ddgcx
Optional: false
QoS Class: Burstable
Node-Selectors: <none>
Tolerations: node.kubernetes.io/not-ready:NoExecute for 300s
node.kubernetes.io/unreachable:NoExecute for 300s
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled <unknown> default-scheduler Successfully assigned openpitrix-system/openpitrix-rp-kubernetes-deployment-cbb6786f7-spmzk to 11.11.11.38
Normal Pulled 21m kubelet, 11.11.11.38 Container image "alpine:3.10.4" already present on machine
Normal Created 21m kubelet, 11.11.11.38 Created container wait-etcd
Normal Started 21m kubelet, 11.11.11.38 Started container wait-etcd
Normal Pulled 21m kubelet, 11.11.11.38 Container image "alpine:3.10.4" already present on machine
Normal Created 21m kubelet, 11.11.11.38 Created container wait-runtime-manager
Normal Started 21m kubelet, 11.11.11.38 Started container wait-runtime-manager
这里时说等待 wait-runtime-manager, 但是查看openpitrix-hyperpitrix-deployment 的日志
kubectl logs openpitrix-hyperpitrix-deployment-6df877b655-rhjlw -n openpitrix-system
2020-04-03 07:49:42.2971 -DEBUG- GetConf: &{Log:{Level:debug} Grpc:{ShowErrorCause:true} Mysql:{Host:mysql.kubesphere-system.svc Port:3306 User:root Password:password Database:openpitrix Disable:false} Etcd:{Endpoints:etcd.kubesphere-system.svc:2379} IAM:{SecretKey:OpenPitrix-lC4LipAXPYsuqw5F ExpireTime:2h0m0s RefreshTokenExpireTime:336h0m0s} Attachment:{AccessKey:openpitrixminioaccesskey SecretKey:openpitrixminiosecretkey Endpoint:http://minio.kubesphere-system.svc:9000 BucketName:openpitrix-attachment} DisableGops:false} (config.go:99)
2020-04-03 07:49:42.302454 I | proto: duplicate proto type registered: openpitrix.ErrorDetail
2020-04-03 07:49:42.30885 -INFO- Release OpVersion: v0.4.8-dev (main.go:53)
2020-04-03 07:49:42.30889 -INFO- Git Commit Hash: 4270bd112065f167526db521a0ad51f830ac3a25 (main.go:53)
2020-04-03 07:49:42.3089 -INFO- Build Time: 2020-02-21 08:00:54 (main.go:53)
2020-04-03 07:49:42.3089 -INFO- App service http://openpitrix-app-manager:9102 (main.go:55)
2020-04-03 07:49:42.30893 -INFO- Runtime service http://openpitrix-runtime-manager:9103 (main.go:56)
2020-04-03 07:49:42.30894 -INFO- Cluster service http://openpitrix-cluster-manager:9104 (main.go:57)
2020-04-03 07:49:42.30894 -INFO- Repo service http://openpitrix-repo-manager:9101 (main.go:58)
2020-04-03 07:49:42.30895 -INFO- Job service http://openpitrix-job-manager:9106 (main.go:59)
2020-04-03 07:49:42.30896 -INFO- Task service http://openpitrix-task-manager:9107 (main.go:60)
2020-04-03 07:49:42.30897 -INFO- Repo indexer service http://openpitrix-repo-indexer:9108 (main.go:61)
2020-04-03 07:49:42.30897 -INFO- Category service http://openpitrix-category-manager:9113 (main.go:62)
2020-04-03 07:49:42.30898 -INFO- Account service http://openpitrix-account-service:9115 (main.go:63)
2020-04-03 07:49:42.30899 -INFO- AM service http://openpitrix-am-service:9120 (main.go:64)
2020-04-03 07:49:42.309 -INFO- Api service start http://openpitrix-api-gateway:9100 (main.go:65)
2020-04-03 07:49:42.30901 -INFO- Market service http://openpitrix-market-manager:9117 (main.go:66)
2020-04-03 07:49:42.30902 -INFO- Attachment service http://openpitrix-attachment-manager:9122 (main.go:67)
2020-04-03 07:49:42.30903 -INFO- Isv service http://openpitrix-isv-manager:9118 (main.go:68)
2020-04-03 07:49:42.30904 -INFO- Service config http://localhost:9202 (main.go:69)
2020-04-03 07:49:42.30944 -DEBUG- Create dlock with key [dlock_global_config] (dlock.go:17)
这个 openpitrix-runtime-manager
是正常工作的啊?
请问这个应该怎么解决啊??