Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 73s default-scheduler Successfully assigned mongodb/mongodb-869dfbd697-nqxql to kerberos
Normal Pulled 72s kubelet Container image "docker.io/bitnami/mongodb:4.4.2-debian-10-r0" already present on machine
Normal Created 72s kubelet Created container mongodb
Normal Started 72s kubelet Started container mongodb
Warning Unhealthy 3s (x4 over 33s) kubelet Liveness probe failed: /bitnami/scripts/ping-mongodb.sh: line 2: mongosh: command not found
Warning Unhealthy 3s (x7 over 63s) kubelet Readiness probe failed: /bitnami/scripts/readiness-probe.sh: line 9: mongosh: command not found
I changed the mongodb tag in ./factory/yaml/mongodb/values-edge.yaml to 4.4.15-debian-10-r8 and now my mongodb instance starts and factory can connect :-)
I also tried the latest mongodb, which is 5.0.9, but kerberos does not work with mongodb 5. I'll also open an issue for this because this is not specified in the docs and after days of frustration of trying to get Vault to work, I gave up.
I changed the mongodb tag in
./factory/yaml/mongodb/values-edge.yaml
to4.4.15-debian-10-r8
and now my mongodb instance starts and factory can connect :-)I also tried the latest mongodb, which is
5.0.9
, but kerberos does not work with mongodb 5. I'll also open an issue for this because this is not specified in the docs and after days of frustration of trying to get Vault to work, I gave up.