Issue with configure vault-helm with consul on EKS cn-north-1

trying this setup on EKS

Here is my consul helm config:

```
syncCatalog:
consulNamespaces:
consulDestinationNamespace: "xyz-vault"

client:
enabled: true

Storage: 1Gi
StorageClass: standard-encrypted

server:
replicas: 2
bootstrapExpect: 1
disruptionBudget:
maxUnavailable: 0
Using consul helm chart version: 0.18.0
```

`helm install consul -f consul-eks/helm-consul-values.yaml vault-consul/consul-helm/
`
Vault config yaml:

```
server:
extraSecretEnvironmentVars:
- envName: AWS_ACCESS_KEY_ID
secretName: vault-aws
secretKey: AWS_ACCESS_KEY_ID
- envName: AWS_SECRET_ACCESS_KEY
secretName: vault-aws
secretKey: AWS_SECRET_ACCESS_KEY

ha:
enabled: true
replicas: 2
config: |
ui = true

listener "tcp" {
tls_disable = 1
address = "[::]:8200"
cluster_address = "[::]:8201"
}

seal "awskms" {
region = "cn-north-1"
kms_key_id = "XXXXXXXXXXX"
endpoint = "kms.cn-north-1.amazonaws.com.cn"
}

storage "consul" {
path = "vault"
address = "HOST_IP:8500"
}
```
Using vault 0.4.0 chart

`helm install vault -f vault-eks/values-eks.yaml vault-eks/vault-helm/`

At time of launch vault unseal but after that it start failing with below error :

```
==> Vault server configuration:
AWS KMS Endpoint: kms.cn-north-1.amazonaws.com.cn
AWS KMS KeyID: XXXXXXXXXXXXXXXXX
AWS KMS Region: cn-north-1
Seal Type: awskms
Api Address: http://10.0.1.4:8200
Cgo: disabled
Cluster Address: https://10.0.1.4:8201
Listener 1: tcp (addr: "[::]:8200", cluster address: "[::]:8201", max_request_duration: "1m30s", max_request_size: "33554432", tls: "disabled")
Log Level: info
Mlock: supported: true, enabled: false
Recovery Mode: false
Storage: consul (HA available)
Version: Vault v1.3.2
==> Vault server started! Log data will stream in below:
2020-04-21T10:50:29.411Z [INFO] proxy environment: http_proxy= https_proxy= no_proxy=
2020-04-21T10:50:29.411Z [WARN] storage.consul: appending trailing forward slash to path
2020-04-21T10:50:29.525Z [INFO] core: stored unseal keys supported, attempting fetch
2020-04-21T10:50:29.582Z [INFO] core.cluster-listener: starting listener: listener_address=[::]:8201
2020-04-21T10:50:29.582Z [INFO] core.cluster-listener: serving cluster requests: cluster_listen_address=[::]:8201
2020-04-21T10:50:29.582Z [INFO] core: entering standby mode
2020-04-21T10:50:29.586Z [INFO] core: vault is unsealed
2020-04-21T10:50:29.586Z [INFO] core: unsealed with stored keys: stored_keys_used=1
2020-04-21T10:50:29.595Z [INFO] core: acquired lock, enabling active operation
2020-04-21T10:50:29.657Z [INFO] core: post-unseal setup starting
2020-04-21T10:50:29.664Z [INFO] core: loaded wrapping token key
2020-04-21T10:50:29.664Z [INFO] core: successfully setup plugin catalog: plugin-directory=
2020-04-21T10:50:29.671Z [INFO] core: successfully mounted backend: type=system path=sys/
2020-04-21T10:50:29.671Z [INFO] core: successfully mounted backend: type=identity path=identity/
2020-04-21T10:50:29.671Z [INFO] core: successfully mounted backend: type=cubbyhole path=cubbyhole/
2020-04-21T10:50:29.697Z [INFO] core: successfully enabled credential backend: type=token path=token/
2020-04-21T10:50:29.697Z [INFO] core: restoring leases
2020-04-21T10:50:29.697Z [INFO] rollback: starting rollback manager
2020-04-21T10:50:29.701Z [INFO] expiration: lease restore complete
2020-04-21T10:50:29.707Z [INFO] identity: entities restored
2020-04-21T10:50:29.710Z [INFO] identity: groups restored
2020-04-21T10:50:29.770Z [INFO] core: post-unseal setup complete
```
after initiated failed error logs on vault:

```
2020-04-21T10:53:30.199Z [ERROR] core: error performing key upgrades: error="error reloading master key: error reloading master key: failed to read master key path: decryption failed: cipher: message authentication failed"
2020-04-21T10:53:30.199Z [INFO] core: marked as sealed
2020-04-21T10:53:30.205Z [INFO] core: stopping cluster listeners
2020-04-21T10:53:30.205Z [INFO] core.cluster-listener: forwarding rpc listeners stopped
2020-04-21T10:53:30.662Z [INFO] core.cluster-listener: rpc listeners successfully shut down
2020-04-21T10:53:30.663Z [INFO] core: cluster listeners successfully shut down
2020-04-21T10:53:30.663Z [INFO] core: vault is sealed
2020-04-21T10:53:32.840Z [INFO] core.autoseal: seal configuration missing, but cannot check old path as core is sealed: seal_type=recovery
2020-04-21T10:53:35.840Z [INFO] core.autoseal: seal configuration missing, but cannot check old path as core is sealed: seal_type=recovery
2020-04-21T10:53:38.842Z [INFO] core.autoseal: seal configuration missing, but cannot check old path as core is sealed: seal_type=recovery
2020-04-21T10:53:41.846Z [INFO] core.autoseal: seal configuration missing, but cannot check old path as core is sealed: seal_type=recovery
2020-04-21T10:53:44.842Z [INFO] core.autoseal: seal configuration missing, but cannot check old path as core is sealed: seal_type=recovery
2020-04-21T10:53:47.839Z [INFO] core.autoseal: seal configuration missing, but cannot check old path as core is sealed: seal_type=recovery
2020-04-21T10:53:50.836Z [INFO] core.autoseal: seal configuration missing, but cannot check old path as core is sealed: seal_type=recovery
2020-04-21T10:53:53.843Z [INFO] core.autoseal: seal configuration missing, but cannot check old path as core is sealed: seal_type=recovery
2020-04-21T10:53:56.832Z [INFO] core.autoseal: seal configuration missing, but cannot check old path as core is sealed: seal_type=recovery
2020-04-21T10:53:59.830Z [INFO] core.autoseal: seal configuration missing, but cannot check old path as core is sealed: seal_type=recovery
2020-04-21T10:54:02.838Z [INFO] core.autoseal: seal configuration missing, but cannot check old path as core is sealed: seal_type=recovery
2020-04-21T10:54:05.838Z [INFO] core.autoseal: seal configuration missing, but cannot check old path as core is sealed: seal_type=recovery
2020-04-21T10:54:08.842Z [INFO] core.autoseal: seal configuration
```