Helm chart - K8s services : Why did you set publishNotReadyAddresses to true?

Hi everyone,

I try to figure out why publishNotReadyAddresses is set to true for k8s services vault, vault-standby, and vault-active. Which use case need it ?

I understand why it is set for the headless service vault-internal but not for the other services.

Thank you.

1 Like

my related question: why isn’t the service with the straight forward name – “vault” – that the agent use by default scoped to vault-active: "true"?

As the helm chart configures things by default the vault service sometimes stops working if any of the pods from the statefulset restart and are sealed.