Installation on microk8s #3562
adamdunstan
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The documentation has glaring errors, that aside, after a lot of messing around and guesswork, I have all of the containers running except couchbase.
adamd@XPS:~/budibase$ k get pods
NAME READY STATUS RESTARTS AGE
proxy-service-9674df9fd-xsll6 1/1 Running 1 (7d1h ago) 14d
worker-service-56c54d7bf5-6qgf5 1/1 Running 1 (7d1h ago) 14d
minio-service-7f57f79454-hkz4t 1/1 Running 0 86m
redis-service-6667db9f46-jzwtp 1/1 Running 0 40m
app-service-5569958f79-ctscz 1/1 Running 0 20m
budibase-couchdb-1 1/2 Running 17 (21s ago) 38m
budibase-couchdb-0 1/2 CrashLoopBackOff 17 (17s ago) 38m
budibase-couchdb-2 1/2 Running 17 (7s ago) 38m
Warning Unhealthy 41m (x2 over 41m) kubelet Liveness probe failed: Get "http://10.1.71.222:5984/_up": dial tcp 10.1.71.222:5984: connect: connection refused
Warning Unhealthy 41m kubelet Liveness probe failed: HTTP probe failed with statuscode: 404
Normal Killing 41m kubelet Container couchdb failed liveness probe, will be restarted
My cluster CNI is operating correctly. I disabled the ngnix proxy, confused why you would deploy both ngnix and another proxy, envoy, in the proxy service container.
Can someone point me to a fix to this?
Beta Was this translation helpful? Give feedback.
All reactions