Skip to content

Commit a264a42

Browse files
committed
Renaming
1 parent a44d84c commit a264a42

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

platform/gcloud/README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -278,7 +278,7 @@ The Ingress remains in the state *Creating ingress* for several minutes until th
278278

279279
You can also check the [load balancer status](https://console.cloud.google.com/net-services/loadbalancing/list/loadBalancers). It provides information about the backend using the service health check.
280280

281-
![Load balancer](images/loadbalancer.png)
281+
![Load balancer](images/lb.png)
282282

283283
In the Ingress details, you should get a *HEALTHY* state on all backends.
284284
This panel also provides some logs on the load balancer activity.
@@ -364,9 +364,9 @@ kubectl apply -f licensing-instance.yaml -n ibm-licensing
364364

365365
> NOTE: You can find more information and use cases on [this page](https://www.ibm.com/docs/en/cpfs?topic=software-configuration).
366366
367-
#### c. Modify Google Load Balancer settings
367+
#### c. Modify GKE Load Balancer settings
368368

369-
As Google native Ingress does not support the same URL rewriting rules as other ones (such as NGINX), some settings have to be modified directly on GCP Web UI.
369+
As Google native Load Balancer does not support the same URL rewriting rules as other ones (such as NGINX), some settings have to be modified directly on GCP Web UI.
370370

371371
You have to look for the ibm-licensing-service-instance in the list of Ingresses, then select its Load Balancer in the list of resources at the bottom:
372372

0 commit comments

Comments
 (0)