CODEWITHSUNDEEP
kubernetesgoogle-kubernetes-enginehashicorp-vault
Nitin G
Nitin G

Reputation: 834

Hashicorp Vault HA cluster pod in pending state

We have a private GKE 3 node cluster with 2 vCPU and 8 GB RAM node pool config. We have installed Vault with helm using these values.

State of the Vault cluster.

enter image description here

State of nodes.

enter image description here

Node usage status.

enter image description here

State of the vault-1 pod

1

enter image description here

2

enter image description here

State of the PVC

enter image description here

State of services.

enter image description here

We referred to this article but no fate.

Please let me know what else info is needed

Upvotes: 0

Views: 394

Answers (1)

Harsh Manvar
Harsh Manvar

Reputation: 30120

i think it's due the affinity that is inplace in values.yaml

You can try adding the one more node to cluster and check once it will resolve the issue maybe.

it also giving error of insuffient CPU so could be one more reason behind the POD stuck in pending state.

Adding one more node will increase the CPU also you can check if there is any affinity issues or not.

Upvotes: 1

Related Questions