GKE Ingress
Adding an Ingress for DuploCloud Google Cloud Platform Load Balancers
Last updated
Was this helpful?
Adding an Ingress for DuploCloud Google Cloud Platform Load Balancers
Last updated
Was this helpful?
GCP's Ingress Controller for GKE automatically manages traffic routing to Kubernetes services, integrating Kubernetes workloads with Google Cloud's load-balancing infrastructure. It simplifies external access to applications, handling SSL termination and global load distribution.
GCP offers its own Ingress Controller, specifically created for Google Kubernetes Engine (GKE), to seamlessly integrate Kubernetes services with Google Cloud's advanced load balancing features.
Container-native load balancing on Google Cloud Platform (GCP) allows Load Balancers to directly target Kubernetes Pods instead of using a node-based proxy. This approach improves performance by enabling more efficient routing, reducing latency by eliminating extra hops, and providing better health-checking capabilities.
It leverages the network endpoint groups (NEGs) feature to ensure that traffic is directed to the appropriate container instances, enabling more granular and efficient load distribution for applications running on GKE.
Before you can create an Ingress, you must create the following DuploCloud resources:
GKE Standard users: create a DuploCloud Tenant, Node Pool, and Service.
GKE Autopilot users: create a DuploCloud Tenant, and Service.
Add a Load Balancer listener that uses Kubernetes (K8s) ClusterIP.
In the DuploCloud Portal, navigate Kubernetes -> Services.
On the Services page, select the Service name from the NAME column.
Click the Load Balancers tab.
Click Configure Load Balancer. The Add Load Balancer Listener pane appears.
From the Select Type list box, select K8s ClusterIP.
Optionally, enable Advanced Kubernetes Settings and configure the External Traffic Policy and Extra Selector Labels fields.
Optionally, select Set HealthCheck annotations (this ensures the Kubernetes Service is recognized by the GKE Ingress Controller).
Optionally, enable Additional health check configs.
Click Add. The Load Balancer listener details will appear in the Load Balancers tab on the Service details page.
To enable SSL, create a GCP-managed certificate resource in the application namespace.
Once a Service and Load Balancer are deployed, add an Ingress:
Select Kubernetes -> Ingress from the navigation pane.
Click Add. The Add Kubernetes Ingress page displays.
Enter an Ingress Name.
From the Ingress Controller list box, select GCE.
From the Visibility list box, select Internal Only or Public.
Enter your DNS prefix in the DNS Prefix field.
Select your ARN from the Certificate ARN list box.
Enter labels in the Labels field, if required.
Click Add to add the Ingress.
In the Add Kubernetes Ingress page, click Add Rule. The Add Ingress Rule pane displays.
Specify the Path (/samplePath/ in the example).
From the Service Name list box, select the Service exposed through the K8S ClusterIP (nginx-test in the example). The Container port field is completed automatically.
Click Add Rule. The rule displays on the Add Kubernetes Ingress page. Repeat the preceding steps to add additional rules.
Click Add to add the Kubernetes Ingress. The Ingress displays on the Ingress page.
The Ingress creation will take a few minutes. Once the IP is attached to the Ingress, you are ready to use your path- or host-based routing defined via Ingress.
You can view the Ingresses you have created by navigating to Kubernetes -> Ingress.
See the DuploCloud GCP User Guide for steps on how to create , and . Once your Tenant and Service are deployed, you can add and configure a Load Balancer listener.
If you have , add the following annotations in the Annotations field to link the Ingress with your GCP-managed certificate
To add a Kubernetes Ingress, you must define . Continue to the next section to add rules to Kubernetes Ingress and complete the Ingress setup.
Optionally, specify the Path Type and Host. In this example, we specify a Path Type of Exact. Clicking the Info Tip icon ( ) provides more information for these optional fields.
