| Feature | Support Status | Requirements |
|---|---|---|
| LoadBalancer Service | Default Support | No additional deployment required. |
| Ingress | Default Support | Optionally enable Ingress Class functionality (once enabled, you can manually select ingress classes when creating ingress through the form interface). No additional deployment required. |
If you have created a GKE cluster, import the GKE cluster.
No manual deployment is required. GKE provides a managed built-in Ingress controller called GKE Ingress. This controller maps Ingress resources to Google Cloud Load Balancers to handle HTTP(S) workloads in GKE, making configuration simpler and more automated.
You can create ingress and LoadBalancer services simultaneously or choose one based on your needs.
Create Ingress
In Container Platform, click Network > Ingress in the left navigation.
Click Create Ingress and select GKE Ingress Class for Ingress Class.
Select Protocol. Default is HTTP. For HTTPS, first create a certificate and select it.
Click Create. Wait approximately 5 minutes for GKE platform to automatically assign a public IP address to the ingress.
Note: Different ingress resources will be assigned different public IP addresses.
Create LoadBalancer Service
In Container Platform, click Network > Services in the left navigation.
Click Create Service and select LoadBalancer for External Access.
Expand annotations and fill in LoadBalancer service annotations as needed.
Click Create.
Go to Google Cloud > Kubernetes Engine and click Services and Ingress in the left navigation.
Click INGRESS.
View information about corresponding Ingress resources in the list.
When using HTTPS protocol, save HTTPS certificate credentials as a Secret (TLS type) in advance.
In Container Platform, click Configuration > Secrets in the left navigation.
Click Create Secret.
Select TLS type and import or fill in Certificate and Private Key as needed.
Click Create.