can not unseal connection refused

[13567436138]

Describe the bug
A clear and concise description of what the bug is.

^Croot@ubuntu:~# kubectexec -it -n vault --kubeconfig ~/.kube/sveltos-member-04 vault-1 -- sh
/ $ vault operator init
Get "http://127.0.0.1:8200/v1/sys/seal-status": dial tcp 127.0.0.1:8200: connect: connection refused

       injector:
          enabled: true
          image:
            repository: "quay.mark.demo/admin/vault-k8s"
            tag: "1.7.0"
            pullPolicy: IfNotPresent
          agentImage:
            repository: "quay.mark.demo/admin/vault"
            tag: "1.20.1"
        server:
          enabled: true
          enterpriseLicense:
            secretName: ""
            secretKey: "license"

          image:
            repository: "quay.mark.demo/admin/vault"
            tag: "1.20.1"
            pullPolicy: IfNotPresent  
          ingress:
            enabled: true
            ingressClassName: "traefik"
            pathType: Prefix
            activeService: true
            hosts:
              - host: vault.mark.demo
                paths: []
          dataStorage:
            enabled: true
            size: 10Gi
            mountPath: "/vault/data"
            storageClass: longhorn
            accessMode: ReadWriteOnce
          auditStorage:
            enabled: true
            size: 10Gi
            mountPath: "/vault/audit"
            storageClass: longhorn
            accessMode: ReadWriteOnce
          standalone:
            enabled: false
          ha:
            enabled: true
            replicas: 3
            config: |
              ui = true

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

              seal "shamir" {}

              storage "consul" {
                path = "vault"
                address = "consul-consul-expose-servers.consul.svc.cluster.local:8500"
              }

              service_registration "kubernetes" {}

            disruptionBudget:
              enabled: false
        ui:
          enabled: true
        csi:
          enabled: true
          image:
            repository: "quay.mark.demo/admin/vault-csi-provider"
            tag: "1.5.1"
            pullPolicy: IfNotPresent
          agent:
            enabled: true
            image:
              repository: "quay.mark.demo/admin/vault"
              tag: "1.20.1"
              pullPolicy: IfNotPresent

To Reproduce
Steps to reproduce the behavior:

1. Run vault write ...
2. Run vault login....
3. See error

Expected behavior
A clear and concise description of what you expected to happen.

Environment:

• Vault Server Version (retrieve with vault status):
• Vault CLI Version (retrieve with vault version):
• / $ vault version
  Vault v1.20.1 (b403b1a), built 2025-07-24T13:33:51Z
• Server Operating System/Architecture:

Vault server configuration file(s):

# Paste your Vault config here.
# Be sure to scrub any sensitive values

Additional context
Add any other context about the problem here.

[heatherezell]

Please provide the info that is requested in the issue template so we can further assist you. Thanks!