I have set up a microk8s cluster on my home machine. Now I would like to install kuberay and so I followed these instructions:
kuberay/helm-chart/kuberay-operator/README.md at master · ray-project/kuberay · GitHub (the first version using helm)
But kuberay-operator pod fails to start. “Back-off restarting failed container kuberay-operator in pod kuberay-operator-6c5…”
Liveness and Readiness probes fail.
Unfortunately the log is also not very telling:
2024-07-13T10:24:59.711Z INFO setup the operator {“version:”: “”}
2024-07-13T10:24:59.711Z INFO setup Flag watchNamespace is not set. Watch custom resources in all namespaces.
2024-07-13T10:24:59.711Z INFO setup Setup manager
I am a complete kubernetes rookie so I struggle to get more meaningful error logs from the pod and so I am pretty lost figuring out why it fails.
This is the description:
Name: kuberay-operator-6c55b68dd-9q62z
Namespace: default
Priority: 0
Service Account: kuberay-operator
Node: xxx
Start Time: Sat, 13 Jul 2024 11:24:24 +0200
Labels: app.kubernetes.io/component=kuberay-operator
app.kubernetes.io/instance=kuberay-operator
app.kubernetes.io/name=kuberay-operator
pod-template-hash=6c55b68dd
Annotations: cni.projectcalico.org/containerID: ad438881693157eac3ab3b42dc1ed934f109b084b7f587529631b02be349421b
cni.projectcalico.org/podIP: 10.1.8.165/32
cni.projectcalico.org/podIPs: 10.1.8.165/32
kubectl.kubernetes.io/restartedAt: 2024-07-13T09:24:23Z
Status: Running
IP: 10.1.8.165
IPs:
IP: 10.1.8.165
Controlled By: ReplicaSet/kuberay-operator-6c55b68dd
Containers:
kuberay-operator:
Container ID: containerd://a1514b1737cb8f83d1b606407797b979c2bbaed6784e8de1b138dd55dd3c6b5a
Image: kuberay/operator:v1.0.0
Image ID: docker.io/kuberay/operator@sha256:4e6ac8a3a2c482d6c841cca72e88bad0e2ae8da6b1dfbe7ebabf8082be70d8e7
Port: 8080/TCP
Host Port: 0/TCP
Command:
/manager
State: Waiting
Reason: CrashLoopBackOff
Last State: Terminated
Reason: Error
Exit Code: 1
Started: Sat, 13 Jul 2024 12:30:30 +0200
Finished: Sat, 13 Jul 2024 12:31:00 +0200
Ready: False
Restart Count: 23
Limits:
cpu: 100m
memory: 512Mi
Requests:
cpu: 100m
memory: 512Mi
Liveness: http-get http://:http/metrics delay=10s timeout=1s period=5s #success=1 #failure=5
Readiness: http-get http://:http/metrics delay=10s timeout=1s period=5s #success=1 #failure=5
Environment:
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-pnm7k (ro)
Conditions:
Type Status
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
kube-api-access-pnm7k:
Type: Projected (a volume that contains injected data from multiple sources)
TokenExpirationSeconds: 3607
ConfigMapName: kube-root-ca.crt
ConfigMapOptional:
DownwardAPI: true
QoS Class: Guaranteed
Node-Selectors:
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
Warning BackOff 3m44s (x268 over 66m) kubelet Back-off restarting failed container kuberay-operator in pod kuberay-operator-6c55b68dd-9q62z_default(d08cb2c0-f55e-47f0-a933-37179c47a0b4)