redis-ha无法启动
JeffK零SK壹S
rysinal https://kubernetes.io/docs/tasks/debug-application-cluster/debug-service/ 可以看下这个帖子，学习下debug技巧。一般DNS解析不了，可以试下直接使用dns pod的地址，如果还是解析不了，看下dns pod的ip地址 53 端口是否通，不通就是容器网络有问题了
rysinalK零S- 已编辑
Jeff 这个minio安装失败，尝试在installer配置了可以解析的dns，删掉job重新安装 仍提示：
/ # /usr/local/bin/helm upgrade --install ks-minio /etc/kubesphere/minio-ha -f /etc/kubesphere/custom-values-minio.yaml --set fullnameOverride=minio --namespace kubesphere-system --debug
[debug] Created tunnel using local port: '36822'
[debug] SERVER: "127.0.0.1:36822"
Release "ks-minio" does not exist. Installing it now.
[debug] CHART PATH: /etc/kubesphere/minio-ha
Error: timed out waiting for the condition- rysinalK零S
- 已编辑
@Jeff DNS解决了，安装minio还是超时，对应的svc也在，这个如何调试呢
[root@master1 kubesphere-all-v2.1.kubectl get svc -A
NAMESPACE NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
default kubernetes ClusterIP 10.233.0.1 <none> 443/TCP 9h
kube-system coredns ClusterIP 10.233.0.3 <none> 53/UDP,53/TCP,9153/TCP 8h
kube-system tiller-deploy ClusterIP 10.233.29.11 <none> 44134/TCP 8h
kubesphere-system minio ClusterIP 10.233.33.247 <none> 9000/TCP 76m
kubesphere-system openldap ClusterIP None <none> 389/TCP 8h
kubesphere-system redis ClusterIP 10.233.33.128 <none> 6379/TCP 8h
kubesphere-system redis-ha ClusterIP None <none> 6379/TCP,26379/TCP 8h
kubesphere-system redis-ha-announce-0 ClusterIP 10.233.53.122 <none> 6379/TCP,26379/TCP 8h
kubesphere-system redis-ha-announce-1 ClusterIP 10.233.37.63 <none> 6379/TCP,26379/TCP 8h
kubesphere-system redis-ha-announce-2 ClusterIP 10.233.58.36 <none> 6379/TCP,26379/TCP 8h
[root@master1 kubesphere-all-v2.1.1]# kubectl get ep -A
NAMESPACE NAME ENDPOINTS AGE
default kubernetes 172.19.186.76:6443,172.19.186.77:6443,172.19.186.80:6443 9h
kube-system coredns 10.233.101.1:53,10.233.96.1:53,10.233.98.2:53 + 6 more... 9h
kube-system kube-controller-manager <none> 9h
kube-system kube-scheduler <none> 9h
kube-system openebs.io-local <none> 8h
kube-system tiller-deploy 10.233.99.1:44134 9h
kubesphere-system minio 10.233.103.1:9000,10.233.108.2:9000 76m
kubesphere-system openldap 10.233.101.4:389,10.233.98.5:389 8h
kubesphere-system redis 10.233.101.7:6379,10.233.96.8:6379,10.233.98.3:6379 8h
kubesphere-system redis-ha 10.233.101.6:6379,10.233.96.7:6379,10.233.98.7:6379 + 3 more... 8h
kubesphere-system redis-ha-announce-0 10.233.96.7:6379,10.233.96.7:26379 8h
kubesphere-system redis-ha-announce-1 10.233.98.7:6379,10.233.98.7:26379 8h
kubesphere-system redis-ha-announce-2 10.233.101.6:6379,10.233.101.6:26379 8h[root@master1 kubesphere-all-v2.1.1]# kubectl -n kubesphere-system exec -it ks-installer-79f84bd7c-m5q2f sh
/ # nslookup kubernetes.default
nslookup: can't resolve '(null)': Name does not resolve
Name: kubernetes.default
Address 1: 10.233.0.1 kubernetes.default.svc.cluster.local[root@master1 ~]# helm del --purge ks-minio
release "ks-minio" deleted
[root@master1 ~]# kubectl delete job -n kubesphere-system minio-make-bucket-job
job.batch "minio-make-bucket-job" deleted
[root@master1 ~]# kubectl -n kubesphere-system exec -it ks-installer-79f84bd7c-m5q2f sh
/ # /usr/local/bin/helm upgrade --install ks-minio /etc/kubesphere/minio-ha -f /etc/kubesphere/custom-values-minio.yaml --set fullnameOverride=minio --namespace kubesphere-system
Release "ks-minio" does not exist. Installing it now.
Error: timed out waiting for the conditio
CauchyK零SK壹S
helm部署minio的时候，会有个make-bucket的job，可以看看那个job的日志，一般minio超时，都是那个玩意造成的。
21 天 后
您好，请问Redis-ha的问题解决了吗
2 个月 后
我也碰到和你一模一样的问题
yunkunraoK零S
dns pod是正常的吗？执行kubectl get pods --namespace=kube-system -l k8s-app=kube-dns