Deployment Complete Access Return 503

Basic information

• On-premises: YES
• Cloud-Provider: none
• Installation type: demo
• Kubernetes version: 1.14.2
• Helm version: 3.16.2
• Installed with Kubespray: no
• (Helm) Charts version: 5.5.0
• List of installed top-level charts:
• Other related technologies + version:

How did you install Wire?

Use documents from https://docs.wire.com/how-to/install/helm.html
Ubuntu：18.0.4

Question

After the installation is completed through the document, visit https://webapp/<your-domain> in the browser and return to 503.
Use the command kubectl get pods -A to display as follows：
NAMESPACE NAME READY STATUS RESTARTS AGE
default brig-7dfbd9d6fc-zkzrz 1/1 Running 0 124m
default brig-index-migrate-data-d4t9r 0/1 Completed 0 82m
default cannon-0 1/1 Running 0 124m
default cargohold-df7db4d47-8nlwf 1/1 Running 0 124m
default cassandra-ephemeral-0 1/1 Running 0 3h16m
default cassandra-migrations-mgptj 0/1 Completed 0 82m
default demo-smtp-787d886bd5-qvlxg 1/1 Running 0 3h1m
default elasticsearch-ephemeral-7566f75456-ptfqj 1/1 Running 0 57m
default elasticsearch-index-create-d4h5t 0/1 Completed 0 82m
default fake-aws-s3-5dfff8cf88-x4c5d 1/1 Running 0 3h2m
default fake-aws-s3-reaper-77d478d5d-dswsv 1/1 Running 0 3h2m
default fake-aws-sns-5c56774d95-wltnc 2/2 Running 0 3h2m
default fake-aws-sqs-5d4cb76758-zk8pn 1/1 Running 0 3h2m
default galley-5875cdd498-xsmrd 1/1 Running 0 124m
default galley-migrate-data-grtqw 0/1 Completed 0 82m
default gundeck-65f66b65-6pls9 1/1 Running 0 124m
default gundeck-migrate-data-sjqtd 0/1 Completed 0 81m
default nginx-ingress-controller-controller-4vqgd 1/1 Running 0 111m
default nginx-ingress-controller-default-backend-9866b44fd-ntn7h 1/1 Running 0 111m
default nginz-fd66f9bf4-m8xrk 2/2 Running 0 124m
default redis-ephemeral-master-0 1/1 Running 0 3h16m
default spar-migrate-data-xrwjp 0/1 Completed 0 81m
kube-system coredns-fb8b8dccf-w5nq2 1/1 Running 7 2d1h
kube-system coredns-fb8b8dccf-z2rzk 1/1 Running 7 2d1h
kube-system etcd-test 1/1 Running 0 2d1h
kube-system kube-apiserver-test 1/1 Running 7 2d1h
kube-system kube-controller-manager-test 1/1 Running 3 2d1h
kube-system kube-flannel-ds-amd64-jgbwm 1/1 Running 0 2d1h
kube-system kube-proxy-rq9d9 1/1 Running 0 2d1h
kube-system kube-scheduler-test 1/1 Running 3 2d1h

Check the nginx log prompt "service" default/webapp-http "does not have any active endpoint."but I can't find out when "webapp-http" was installed.

Start with the Helm installation documentation and the reported kubectl get pods -A output, then inspect the nginx log entry for the default/webapp-http service. Trace where webapp-http is configured in the deployment and determine why it has no active endpoint. Done means identifying the cause of the 503 and documenting or correcting the deployment configuration.