title: UI 404 - Vault Kubernetes
body: <p>I'm testing out Vault in Kubernetes and am installing via the Helm chart. I've created an overrides file,  it's an amalgamation of a few different pages from the official docs.</p>
  <p>The pods seem to come up OK and into Ready status and I can unseal vault manually using 3 of the keys generated. I'm having issues getting 404 when browsing the UI though, the UI is presented externally on a Load Balancer in AKS. Here's my config:</p>
  <pre><code>global:
    enabled: true
    tlsDisable: false
  
  injector:
    enabled: false
  
  server:
  
    readinessProbe:
      enabled: true
      path: &quot;/v1/sys/health?standbyok=true&amp;sealedcode=204&amp;uninitcode=204&quot;
    # livenessProbe:
    #   enabled: true
    #   path: &quot;/v1/sys/health?standbyok=true&quot;
    #   initialDelaySeconds: 60
  
    extraEnvironmentVars:
      VAULT_CACERT: /vault/userconfig/vault-server-tls/vault.ca
  
    extraVolumes:
      - type: secret
        name: vault-server-tls # Matches the ${SECRET_NAME} from above
  
    standalone:
      enabled: true
      config: |
        listener &quot;tcp&quot; {
          address = &quot;[::]:8200&quot;
          cluster_address = &quot;[::]:8201&quot;
          tls_cert_file = &quot;/vault/userconfig/vault-server-tls/vault.crt&quot;
          tls_key_file  = &quot;/vault/userconfig/vault-server-tls/vault.key&quot;
          tls_client_ca_file = &quot;/vault/userconfig/vault-server-tls/vault.ca&quot;
        }
  
        storage &quot;file&quot; {
          path = &quot;/vault/data&quot;
        }
  
  # Vault UI
  ui:
    enabled: true
    serviceType: &quot;LoadBalancer&quot;
    serviceNodePort: null
    externalPort: 443
  
    # For Added Security, edit the below
    #  loadBalancerSourceRanges:
            #    5.69.25.6/32
  </code></pre>
  <p>I'm still trying to get to grips with Vault. My liveness probe is commented out because it was permanently failing and causing the pod to be re-scheduled, even though checking the vault service status it appeared to be healthy and awaiting an unseal. That's a side issue though compared to the UI, just mentioning in case the failing liveness is related.</p>
  <p>Thanks!</p>