Description
Hi
when i start the fisrt step of " kubectl apply -f zookeeper_micro.yaml" ,the pods 'zk-0' is pending status .
describ pods follow:
Name: zk-0
Namespace: lai2
Priority: 0
PriorityClassName:
Node:
Labels: app=zk
controller-revision-hash=zk-64bdbd78
statefulset.kubernetes.io/pod-name=zk-0
Annotations:
Status: Pending
IP:
Controlled By: StatefulSet/zk
Containers:
kubernetes-zookeeper:
Image: pharosproduction/zookeeper_k8s:v1
Ports: 2181/TCP, 2888/TCP, 3888/TCP
Host Ports: 0/TCP, 0/TCP, 0/TCP
Command:
sh
-c
start-zookeeper --servers=1 --data_dir=/var/lib/zookeeper/data --data_log_dir=/var/lib/zookeeper/data/log --conf_dir=/opt/zookeeper/conf --client_port=2181 --election_port=3888 --server_port=2888 --tick_time=2000 --init_limit=10 --sync_limit=5 --heap=512M --max_client_cnxns=60 --snap_retain_count=3 --purge_interval=12 --max_session_timeout=40000 --min_session_timeout=4000 --log_level=INFO
Limits:
cpu: 300m
memory: 300Mi
Requests:
cpu: 250m
memory: 256Mi
Liveness: exec [sh -c zookeeper-ready 2181] delay=10s timeout=5s period=10s #success=1 #failure=3
Readiness: exec [sh -c zookeeper-ready 2181] delay=10s timeout=5s period=10s #success=1 #failure=3
Environment:
Mounts:
/var/lib/zookeeper from datadir (rw)
/var/run/secrets/kubernetes.io/serviceaccount from default-token-4hnlb (ro)
Conditions:
Type Status
PodScheduled False
Volumes:
datadir:
Type: PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
ClaimName: datadir-zk-0
ReadOnly: false
default-token-4hnlb:
Type: Secret (a volume populated by a Secret)
SecretName: default-token-4hnlb
Optional: false
QoS Class: Burstable
Node-Selectors:
Tolerations: node.kubernetes.io/not-ready:NoExecute for 300s
node.kubernetes.io/unreachable:NoExecute for 300s
Events:
Type Reason Age From Message
Warning FailedScheduling 50s (x26654 over 24h) default-scheduler pod has unbound PersistentVolumeClaims (repeated 3 times)
please, how to solve the question?