Hello,
I followed steps given in the docs and ran on my minikube environment. The deployment is trying to create below pods and only some of them created and other returning with errors.
[test-cluster-cluster-controller-1] -created
[test-cluster-log-1] - created
[test-cluster-log-2] -FAILED
[test-cluster-log-3] -FAILED
[test-cluster-log-4]- FAILED
[test-cluster-storage-1] - created
[test-cluster-storage-2] -FAILED
[test-cluster-storage-3]- FAILED
[fdb-kubernetes-operator-controller-manager-cf7785889-qlmkd] -created
Errors:
[test-cluster-log-2] and [test-cluster-storage-2]
0/1 nodes are available: pod has unbound immediate PersistentVolumeClaims. preemption: 0/1 nodes are available: 1 No preemption victims found for incoming pod…
0/1 nodes are available: 1 Insufficient cpu. preemption: 0/1 nodes are available: 1 No preemption victims found for incoming pod…
Could you provide some more details about your setup? What Minikube driver are you using? How many resources are available in your Minikube setup? What architecture is your setup?
Hello Johannes,
Thanks for reaching out on this. Based on your info, I got striked and updated the minikube cpu and memory from default to higher and I see now pods executed.
I am now trying to connect to fdb and when I run the ‘status’, I get a message as “Could not communicate with a quorum of coordination servers”.
I am reviewing your document on how to update DNS but so far not successful. Can you tell me which yaml file I need to configure DNS changes? Referred here but not sure on where to make changes - https://github.com/FoundationDB/fdb-kubernetes-operator/blob/main/docs/manual/customization.md
Hello Johannes,
Thanks for reaching out on this. Based on your info, I got striked and updated the minikube cpu and memory from default to higher and I see now pods executed.
I am now trying to connect to fdb and when I run the ‘status’, I get a message as “Could not communicate with a quorum of coordination servers”.
Are you trying to connect to the cluster from outside of Minikube? That’s currently not possible, FDB requires to be able to connect to the FDB processes directly and the IP addresses assigned inside the Minikube setup are normally not reachable from your host. There might be a Minikube setup that allows you to do that.
Hello Johannes,
After updating the cluster.yaml with below setting, I was able to configure DNS changes. Thanks for the support.
routing: useDNSInClusterFile: true