Load balancers: console walkthrough¶
The same operations as the step-by-step guide, done in the console.
This console page has a guided tour
Click Start the tour beside the create button for a walkthrough that highlights each field as you go.
List¶
WebHosting > Networking > LoadBalancers, or Networking > LoadBalancers, lists what the selected project publishes.
Both L7 and L4 endpoints appear here, even though they are different objects underneath - routes with a hostname, load balancer services with an address.
Create¶
Create LoadBalancer opens a guided form.
1. Pick the backend¶
Backend Endpoints lists the services in the project, leaving out ones that are already load balancers of their own.
2. Pick the type¶
Type is the decision that changes everything below it, so set it first:
- L7 - Reverse Proxy (Web, HTTP/HTTPS) creates a Route. You get a hostname and a certificate.
- L4 - LoadBalancer (TCP/UDP traffic) turns the service into a LoadBalancer Service with a public address of its own, forwarding traffic untouched.
3a. For L7, set the hostname¶
Enter a label and it becomes a subdomain of apps.grn.cloud. The form shows the full name
it will be reachable at as you type.
Tick Use a custom domain to enter a full hostname of your own instead.
A custom domain needs a DNS record you create
The form does not create one. Until that name points at the platform ingress, nothing arrives - and the endpoint will look perfectly healthy in this list the whole time.
3b. For L4, set the ports¶
Enter the Ports the service should accept. Only these are forwarded.
Leave Public IP alone unless you need a particular address - one is allocated for you. Advanced: choose a specific address is for cases where the address is already published somewhere you cannot change.
4. Read the summary and save¶
A Summary appears once the form is complete. Read it before saving: the hostname and the type are both awkward to change afterwards.
Change¶
The console form creates endpoints; it does not edit them. Changing the target, the ports
or the hostname is done with oc - see Change.
Changing a hostname is effectively creating a new endpoint. The old name stops working immediately.
Delete¶
Use the kebab menu at the end of the row.
For L4, prefer making the service private again
Deleting an L4 entry deletes the Service, which also breaks the workloads inside the
cluster that were calling it. To stop publishing it while keeping it working
internally, set its type back to ClusterIP - see Delete.
An L7 entry is its own object, so deleting it only removes the public endpoint.
Where the console differs from the CLI¶
| Console | oc |
|
|---|---|---|
| L7 vs L4 | One form, one Type field | Two different objects |
| Hostname | Subdomain built for you | You write out the full host |
| TLS | Edge termination with redirect, set for you | You choose the termination |
| Public IP | Allocated unless you ask otherwise | Same, via spec.loadBalancerIP |
| Custom domain DNS | Not created - still yours to do | Not created either |
Verify¶
Test from outside the cluster, not from a workload on it.
The most common reason a published service stays silent is a firewall in the same project: a rule set to Only this project or Anywhere in the cluster drops traffic from outside no matter what the load balancer does. See Firewalls.