Open robinhuiser opened 3 years ago
Additional information:
Temporarily workaround - updated the spec for deployment maya-apiserver with:
env:
- name: MY_POD_IP
valueFrom:
fieldRef:
fieldPath: status.podIP
livenessProbe:
exec:
command:
- sh
- -c
- /usr/local/bin/mayactl
- -m $MY_POD_IP
- version
initialDelaySeconds: 30
periodSeconds: 60
readinessProbe:
exec:
command:
- sh
- -c
- /usr/local/bin/mayactl
- -m $MY_POD_IP
- version
initialDelaySeconds: 30
periodSeconds: 60
@robinhuiser did you try running by just doing ?
livenessProbe:
exec:
command:
- sh
- -c
- /usr/local/bin/mayactl
- version
What steps did you take and what happened:
kubectl apply -f https://openebs.github.io/charts/openebs-operator.yaml
on a 8 node Raspberry Pi 4 8Gb (arm64) microk8s clusterWhat did you expect to happen:
The output of the following commands will help us better understand what's going on:
Anything else you would like to add:
When attaching with a shell to the running pod, I can confirm the liveness probe fails since the command takes around 12 seconds (!) to finish:
When I run the same command, but specify the server and port using parameters, the command finishes within milliseconds:
I assume the CLI takes some of the environment variables to connect to its status endpoint, not sure what has been set incorrectly; I have included the environment set below:
Environment:
Maya version: 2.6.0-released
OpenEBS version: 2.6.0
Kubernetes version (use
kubectl version
):Kubernetes installer & version: microk8s 1.19/stable
Cloud provider or hardware configuration: Raspberry Pi 4 8Gb arm64
OS (e.g. from
/etc/os-release
):