helm 安装 manager init-config 起不来
本地docker-desktop 下载chart 包,
NAME READY STATUS RESTARTS AGE
elasticsearch-master-0 0/1 Running 0 160m
know-manager-knowstreaming-manager-86854bddf-hfd77 0/1 Init:CrashLoopBackOff 6 (4m23s ago) 11m
know-manager-knowstreaming-web-56c65d498d-pmvhc 1/1 Running 0 160m
know-manager-ksmysql-0 1/1 Running 0 160m
考虑了本机的资源,调小了启动资源,减少了副本数。不知道为啥know-manager-knowstreaming-manager-86854bddf-hfd77起不来。
Name: know-manager-knowstreaming-manager-86854bddf-hfd77
Namespace: know-manager
Priority: 0
Node: docker-desktop/192.168.65.4
Start Time: Fri, 09 Sep 2022 11:01:20 +0800
Labels: app.kubernetes.io/instance=know-manager
app.kubernetes.io/name=knowstreaming-manager
pod-template-hash=86854bddf
release=know-manager
Annotations: <none>
Status: Pending
IP: 10.1.0.149
IPs:
IP: 10.1.0.149
Controlled By: ReplicaSet/know-manager-knowstreaming-manager-86854bddf
Init Containers:
init-config:
Container ID: docker://a042546165b200248c20cdba1db55fc4cbbbfbae0a55f4b2244918110739612a
Image: knowstreaming/knowstreaming-manager:latest
Image ID: docker-pullable://knowstreaming/knowstreaming-manager@sha256:b6c81aa6efcfe029a5035b6062105b68632a7cb0d883d3dc9e678c99c6d89b1f
Port: <none>
Host Port: <none>
Command:
/bin/bash
/conf/init_es_index.sh
State: Waiting
Reason: CrashLoopBackOff
Last State: Terminated
Reason: Error
Exit Code: 1
Started: Fri, 09 Sep 2022 11:08:13 +0800
Finished: Fri, 09 Sep 2022 11:08:13 +0800
Ready: False
Restart Count: 6
Environment: <none>
Mounts:
/conf from configmap (rw)
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-nfvk9 (ro)
Containers:
knowstreaming-manager:
Container ID:
Image: knowstreaming/knowstreaming-manager:latest
Image ID:
Port: 80/TCP
Host Port: 0/TCP
Command:
/usr/bin/java
-Xmx2g
-Xms2g
-jar
/km-rest.jar
--spring.config.location=/conf/application-test.yml
State: Waiting
Reason: PodInitializing
Ready: False
Restart Count: 0
Limits:
cpu: 2
memory: 5Gi
Requests:
cpu: 2
memory: 5Gi
Liveness: http-get http://:http/ks-km/api/v3/open/health delay=0s timeout=1s period=10s #success=1 #failure=3
Readiness: http-get http://:http/ks-km/api/v3/open/health delay=0s timeout=1s period=10s #success=1 #failure=3
Environment:
POD_NAME: know-manager-knowstreaming-manager-86854bddf-hfd77 (v1:metadata.name)
TZ: Asia/Shanghai
Mounts:
/conf from configmap (rw)
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-nfvk9 (ro)
Conditions:
Type Status
Initialized False
Ready False
ContainersReady False
PodScheduled True
Volumes:
configmap:
Type: ConfigMap (a volume populated by a ConfigMap)
Name: know-manager-knowstreaming-manager
Optional: false
kube-api-access-nfvk9:
Type: Projected (a volume that contains injected data from multiple sources)
TokenExpirationSeconds: 3607
ConfigMapName: kube-root-ca.crt
ConfigMapOptional: <nil>
DownwardAPI: true
QoS Class: Burstable
Node-Selectors: <none>
Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 7m47s default-scheduler Successfully assigned know-manager/know-manager-knowstreaming-manager-86854bddf-hfd77 to docker-desktop
Normal Pulled 7m37s kubelet Successfully pulled image "knowstreaming/knowstreaming-manager:latest" in 9.234653097s
Normal Pulled 7m23s kubelet Successfully pulled image "knowstreaming/knowstreaming-manager:latest" in 11.447294211s
Normal Pulled 6m58s kubelet Successfully pulled image "knowstreaming/knowstreaming-manager:latest" in 9.069085055s
Normal Created 6m24s (x4 over 7m37s) kubelet Created container init-config
Normal Pulled 6m24s kubelet Successfully pulled image "knowstreaming/knowstreaming-manager:latest" in 8.23885446s
Normal Started 6m23s (x4 over 7m35s) kubelet Started container init-config
Normal Pulling 5m35s (x5 over 7m46s) kubelet Pulling image "knowstreaming/knowstreaming-manager:latest"
Warning BackOff 2m35s (x21 over 7m20s) kubelet Back-off restarting failed container
请问这个是啥问题?
@wangdongfang-aden 辛苦东方关注一下是什么原因
这是来自QQ邮箱的假期自动回复邮件。 你好,我最近正在休假中,无法亲自回复你的邮件。我将在假期结束后,尽快给你回复。
knowstreaming-manager 的init容器执行了es初始化的脚本,无法启动的原因是因为es容器没有Ready
knowstreaming-manager 的init容器执行了es初始化的脚本,无法启动的原因是因为es容器没有Ready
是否可以给es初始化脚本添加重试,直到成功再进行下一步操作?
目前es初始化脚本是由km的 initContainer来执行,执行成功后km的主容器才会启动
这是来自QQ邮箱的假期自动回复邮件。 你好,我最近正在休假中,无法亲自回复你的邮件。我将在假期结束后,尽快给你回复。