Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

Trying to follow How to Set Up an Nginx Ingress with Cert-Manager on DigitalOcean Kubernetes tutorial for setting up the ingress rule for backendApi
The backend service are created correctly .
kubectl get svc
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
echo1 ClusterIP 10.245.254.205 <none> 80/TCP 3h
echo2 ClusterIP 10.245.187.179 <none> 80/TCP 3h
Ingress resource are created correctly
kubectl get ingress echo-ingress
NAME HOSTS ADDRESS PORTS AGE
echo-ingress echo1.example.com,echo2.example.com 157.230.67.78 80 3h
And I see external load balancer is created.
But it seems ingress cannot find the backend server ip , it shows <none>
kubectl describe ingress echo-ingress
Name: echo-ingress
Namespace: default
Address: 157.230.67.78
Default backend: default-http-backend:80 (<none>)
Rules:
Host Path Backends
---- ---- --------
echo1.example.com
echo1:80 (<none>)
echo2.example.com
echo2:80 (<none>)
Annotations:
Events: <none>
I don’t think it would forward traffic , should it be sth like
Host Path Backends
---- ---- --------
echo1.example.com
echo1:80 (10.245.254.205:80)
like in the official tutorial ?
Ken Loomis
lanbo
Azeem Cv
KFSys
doughboy
cos+digitalocean
Josep Esposito
Vivek V
Tony Rhoades
Wingrammer
gittyhubhubhub
Reaz NM