...
Apply it and verify that Ingress Resource has been created. Please note that the IP address will not be defined right away (wait for the ADDRESS field to get populated). It is possible to follow the implementation of the LB step by step, from the creation of its components (Listener, Pool, Policy) to the assignment of the FIP, from the log of the Pod of the Ingress Controller (the whole operation can take a few minutes).
| Code Block | ||||
|---|---|---|---|---|
| ||||
$ kubectl get ing NAME CLASS HOSTS ADDRESS PORTS AGE lb <none> webserver-bar.com 131.154.97.200 80 3d1h |
Using a browser or the curl command, you should be able to access the backend service by sending HTTP request to the domain name specified in the Ingress Resource (remember to hook the hostname to the FIP in the /etc/hosts of the machine from which the request to the service starts)
...