kubesphere2.1 使用inject-ks-account脚本对接LDAP后，console无法打开访问，
相关信息如下：
kubectl -n kubesphere-system get pods
NAME READY STATUS RESTARTS AGE
etcd-5769d4997f-bmdvj 1/1 Running 0 4d23h
ks-account-84695f7c9d-4vdkf ½ CrashLoopBackOff 9 23m
ks-account-84695f7c9d-kww9j ½ CrashLoopBackOff 9 23m
ks-account-9ffb94b99-5gmng 1/1 Running 0 4d23h
ks-account-9ffb94b99-wtthr 1/1 Running 0 4d23h
ks-apigateway-d899b7b98-48gzs 1/1 Running 0 4d23h
ks-apigateway-d899b7b98-r2d4c 1/1 Running 0 18h
ks-apigateway-d899b7b98-vrxzc 1/1 Running 1 18h
ks-apiserver-5c5759c866-ctsrb 1/1 Running 4 18h
ks-apiserver-5c5759c866-hjkpl 1/1 Running 4 18h
ks-apiserver-5c5759c866-m6bwm 1/1 Running 0 4d23h
ks-console-97cf4db85-9jhkz 1/1 Running 0 4d23h
ks-console-97cf4db85-h7qzp 1/1 Running 0 4d23h
ks-console-97cf4db85-wgcn6 1/1 Running 0 4d23h
ks-controller-manager-9dcc6599f-99sgk 1/1 Running 0 4d23h
ks-controller-manager-9dcc6599f-bch4w 1/1 Running 1 4d23h
ks-controller-manager-9dcc6599f-hdqtc 1/1 Running 0 4d23h
ks-installer-7d9fb945c7-gpj2d 1/1 Running 0 4d23h
minio-845b7bd867-qvqmm 1/1 Running 1 4d23h
mysql-66df969d-4lxff 1/1 Running 0 4d23h
openldap-0 1/1 Running 0 4d23h
openldap-1 1/1 Running 0 4d23h
redis-ha-haproxy-ffb8d889d-9rlwv 1/1 Running 0 4d23h
redis-ha-haproxy-ffb8d889d-g5jzh 1/1 Running 0 4d23h
redis-ha-haproxy-ffb8d889d-pn6qx 1/1 Running 0 4d23h
redis-ha-server-0 2/2 Running 0 4d23h
redis-ha-server-1 2/2 Running 0 4d23h
redis-ha-server-2 2/2 Running 0 4d23h
kubectl -n kubesphere-system describe pod ks-account-84695f7c9d-4vdkf
Name: ks-account-84695f7c9d-4vdkf
Namespace: kubesphere-system
Priority: 0
Node: paas03.liuheco.com/10.10.40.103
Start Time: Sun, 15 Mar 2020 14:57:51 +0800
Labels: app=ks-account
pod-template-hash=84695f7c9d
tier=backend
version=v2.1.1
Annotations: kubectl.kubernetes.io/restartedAt: 2020-03-10T07:50:49Z
Status: Running
IP: 10.233.92.14
IPs:
IP: 10.233.92.14
Controlled By: ReplicaSet/ks-account-84695f7c9d
Init Containers:
wait-redis:
Container ID: docker://ecf6b67fa429ed37c1e56d66f19dcd051995c8e6f514cd43a0f21330472eff46
Image: alpine:3.10.4
Image ID: docker-pullable://alpine@sha256:7c3773f7bcc969f03f8f653910001d99a9d324b4b9caa008846ad2c3089f5a5f
Port: <none>
Host Port: <none>
Command:
sh
-c
until nc -z redis.kubesphere-system.svc 6379; do echo “waiting for redis”; sleep 2; done;
State: Terminated
Reason: Completed
Exit Code: 0
Started: Sun, 15 Mar 2020 14:57:52 +0800
Finished: Sun, 15 Mar 2020 14:57:52 +0800
Ready: True
Restart Count: 0
Environment: <none>
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from kubesphere-token-ftdwx (ro)
wait-ldap:
Container ID: docker://82dc44454fafe88d16d1018462b1ddccf68c1ed7a6888a0a666b536fd2b5c9b2
Image: alpine:3.10.4
Image ID: docker-pullable://alpine@sha256:7c3773f7bcc969f03f8f653910001d99a9d324b4b9caa008846ad2c3089f5a5f
Port: <none>
Host Port: <none>
Command:
sh
-c
until nc -z openldap.kubesphere-system.svc 389; do echo “waiting for ldap”; sleep 2; done;
State: Terminated
Reason: Completed
Exit Code: 0
Started: Sun, 15 Mar 2020 14:57:54 +0800
Finished: Sun, 15 Mar 2020 14:57:54 +0800
Ready: True
Restart Count: 0
Environment: <none>
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from kubesphere-token-ftdwx (ro)
Containers:
ks-account:
Container ID: docker://79ee9611213f3f2975ed68dd26acf07be55f2f0ec6366bfe988c597b7ad380c0
Image: kubesphere/ks-account:v2.1.1
Image ID: docker-pullable://kubesphere/ks-account@sha256:6fccef53ab7a269160ce7816dfe3583730ac7fe2064ea5c9e3ce5e366f3470eb
Port: 9090/TCP
Host Port: 0/TCP
Command:
ks-iam
–logtostderr=true
–jwt-secret=$(JWT_SECRET)
–admin-password=$(ADMIN_PASSWORD)
–enable-multi-login=False
–token-idle-timeout=40m
–redis-url=redis://redis.kubesphere-system.svc:6379
–generate-kubeconfig=true
State: Running
Started: Sun, 15 Mar 2020 14:57:55 +0800
Ready: True
Restart Count: 0
Limits:
cpu: 1
memory: 500Mi
Requests:
cpu: 20m
memory: 100Mi
Environment:
KUBECTL_IMAGE: kubesphere/kubectl:v1.0.0
JWT_SECRET: <set to the key ‘jwt-secret’ in secret ‘ks-account-secret’> Optional: false
ADMIN_PASSWORD: <set to the key ‘admin-password’ in secret ‘ks-account-secret’> Optional: false
Mounts:
/etc/ks-iam from user-init (rw)
/etc/kubesphere from kubesphere-config (rw)
/etc/kubesphere/rules from policy-rules (rw)
/var/run/secrets/kubernetes.io/serviceaccount from kubesphere-token-ftdwx (ro)
ad-sidecar:
Container ID: docker://9ada1158c20d97f2122b685e609c1a52f0233f35095edbfd5e91325124166516
Image: kubespheredev/ad-sidecar:v0.0.1
Image ID: docker-pullable://kubespheredev/ad-sidecar@sha256:0cc69753a7503176c7175e2962648de0b7e6014fc7c5910c6feacf7a8ac08fa3
Port: 19090/TCP
Host Port: 0/TCP
Command:
ad-sidecar
–logtostderr=true
–v=2
State: Waiting
Reason: CrashLoopBackOff
Last State: Terminated
Reason: Error
Exit Code: 2
Started: Sun, 15 Mar 2020 15:18:49 +0800
Finished: Sun, 15 Mar 2020 15:18:49 +0800
Ready: False
Restart Count: 9
Environment: <none>
Mounts:
/etc/kubesphere/sync.yaml from ad-sync-config (rw,path=“sync.yaml”)
/var/run/secrets/kubernetes.io/serviceaccount from kubesphere-token-ftdwx (ro)
Conditions:
Type Status
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
policy-rules:
Type: ConfigMap (a volume populated by a ConfigMap)
Name: policy-rules
Optional: false
user-init:
Type: ConfigMap (a volume populated by a ConfigMap)
Name: user-init
Optional: false
kubesphere-config:
Type: ConfigMap (a volume populated by a ConfigMap)
Name: kubesphere-config
Optional: false
ad-sync-config:
Type: ConfigMap (a volume populated by a ConfigMap)
Name: ad-sync-config
Optional: false
kubesphere-token-ftdwx:
Type: Secret (a volume populated by a Secret)
SecretName: kubesphere-token-ftdwx
Optional: false
QoS Class: Burstable
Node-Selectors: <none>
Tolerations: CriticalAddonsOnly
node-role.kubernetes.io/master:NoSchedule
node.kubernetes.io/not-ready:NoExecute for 60s
node.kubernetes.io/unreachable:NoExecute for 60s
Events:
Type Reason Age From Message
Normal Scheduled <unknown> default-scheduler Successfully assigned kubesphere-system/ks-account-84695f7c9d-4vdkf to paas03.liuheco.com
Normal Pulled 24m kubelet, paas03.liuheco.com Container image “alpine:3.10.4″ already present on machine
Normal Created 24m kubelet, paas03.liuheco.com Created container wait-redis
Normal Started 24m kubelet, paas03.liuheco.com Started container wait-redis
Normal Pulled 24m kubelet, paas03.liuheco.com Container image “alpine:3.10.4″ already present on machine
Normal Created 24m kubelet, paas03.liuheco.com Created container wait-ldap
Normal Started 24m kubelet, paas03.liuheco.com Started container wait-ldap
Normal Pulled 24m kubelet, paas03.liuheco.com Container image “kubesphere/ks-account:v2.1.1” already present on machine
Normal Created 24m kubelet, paas03.liuheco.com Created container ks-account
Normal Started 24m kubelet, paas03.liuheco.com Started container ks-account
Normal Pulling 24m kubelet, paas03.liuheco.com Pulling image “kubespheredev/ad-sidecar:v0.0.1″
Normal Pulled 24m kubelet, paas03.liuheco.com Successfully pulled image “kubespheredev/ad-sidecar:v0.0.1”
Normal Started 24m (x3 over 24m) kubelet, paas03.liuheco.com Started container ad-sidecar
Normal Created 23m (x4 over 24m) kubelet, paas03.liuheco.com Created container ad-sidecar
Normal Pulled 23m (x3 over 24m) kubelet, paas03.liuheco.com Container image “kubespheredev/ad-sidecar:v0.0.1” already present on machine
Warning BackOff 4m17s (x93 over 24m) kubelet, paas03.liuheco.com Back-off restarting failed container
kubectl -n kubesphere-system logs ks-account-84695f7c9d-4vdkf
Error from server (BadRequest): a container name must be specified for pod ks-account-84695f7c9d-4vdkf, choose one of: [ks-account ad-sidecar] or one of the init containers: [wait-redis wait-ldap]
