You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had searched in the issues and found no similar issues.
What happened
Mounts:
/opt/dinky/sql-exec/ from dinky-config-volume (rw)
/opt/flink/conf from flink-config-volume (rw)
/opt/flink/pod-template from pod-template-volume (rw)
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-s86tf (ro)
Conditions:
Type Status
PodReadyToStartContainers True
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
dinky-config-volume:
Type: ConfigMap (a volume populated by a ConfigMap)
Name: dinky-config-paimon-test
Optional: false
flink-config-volume:
Type: ConfigMap (a volume populated by a ConfigMap)
Name: flink-config-paimon-test
Optional: false
pod-template-volume:
Type: ConfigMap (a volume populated by a ConfigMap)
Name: pod-template-paimon-test
Optional: false
What you expected to happen
Warning FailedMount 32m kubelet MountVolume.SetUp failed for volume "dinky-config-volume" : configmap "dinky-config-paimon-test" not found
Search before asking
What happened
Conditions:
Type Status
PodReadyToStartContainers True
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
dinky-config-volume:
Type: ConfigMap (a volume populated by a ConfigMap)
Name: dinky-config-paimon-test
Optional: false
flink-config-volume:
Type: ConfigMap (a volume populated by a ConfigMap)
Name: flink-config-paimon-test
Optional: false
pod-template-volume:
Type: ConfigMap (a volume populated by a ConfigMap)
Name: pod-template-paimon-test
Optional: false
What you expected to happen
Warning FailedMount 32m kubelet MountVolume.SetUp failed for volume "dinky-config-volume" : configmap "dinky-config-paimon-test" not found
How to reproduce
这个dinky-config-volume 挂盘失败是啥原因呀,flink 基础镜像里需要建 /op/dinky 这个目录嘛
Anything else
No response
Version
dev
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: