# Vault-Consul deployment in kubernetes failing

**URL:** <https://discuss.hashicorp.com/t/vault-consul-deployment-in-kubernetes-failing/50715>\
**Category:** Vault\
**Tags:** k8s, connect, consul-vault\
**Created:** [February 27, 2023, 12:53pm UTC](https://discuss.hashicorp.com/t/vault-consul-deployment-in-kubernetes-failing/50715 "2023-02-27T12:53:31Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![soundarya3098](https://avatars.discourse-cdn.com/v4/letter/s/e9bcb4/32.png) [@soundarya3098](https://discuss.hashicorp.com/u/soundarya3098)\
**Post date:** [February 27, 2023, 12:53pm UTC](https://discuss.hashicorp.com/t/vault-consul-deployment-in-kubernetes-failing/50715/1 "2023-02-27T12:53:31Z")

</div>

In an AWS Kubernetes service, I have deployed vault and consul using helm chart with the chart versions vault-0.10.0 and consul-0.30.0 respectively.

Both vault and consul servers are installed with 3 replicas for enabling high availability. Now, all the replicas in both servers are crashing. Below are the error logs found in vault

> WARNING! Unable to read storage migration status.  
> 2023-02-27T12:33:07.665Z [INFO] proxy environment: http\_proxy= https\_proxy= no\_proxy=  
> 2023-02-27T12:33:14.771Z [WARN] storage migration check error: error=“Unexpected response code: 500”

In consul, spotted the below logs,

> [ERROR] agent.server.connect: Failed to initialize Connect CA: routine=“CA initialization” error=“stored CA root is not the active root”

Attaching the screenshot of the errors.

Vault:

 ![Screenshot from 2023-02-27 18-03-19](https://global.discourse-cdn.com/hashicorp/original/3X/5/5/55b8268b2ab9e5887e578aad6a00a4f393217ed6.png)

Consul:

 ![Screenshot from 2023-02-27 18-02-51](https://global.discourse-cdn.com/hashicorp/original/3X/4/d/4da3df3feb84173059c7b27d67813b9c59f224f4.png)

I am Unable to figure out the cause of the issue and fix it. Can anyone please guide me to resolve it.

Thanks in Advance.