Static IPs
This example demonstrates how to assign a static-ip to an Ingress on through the nginx controller.
Prerequisites
You need a TLS cert and a test HTTP service for this example. You will also need to make sure your Ingress targets exactly one Ingress controller by specifying the ingress.class annotation, and that you have an ingress controller running in your cluster.
Acquiring an IP
Since instances of the nginx controller actually run on nodes in your cluster, by default nginx Ingresses will only get static IPs if your cloudprovider supports static IP assignments to nodes. On GKE/GCE for example, even though nodes get static IPs, the IPs are not retained across upgrade.
To acquire a static IP for the nginx ingress controller, simply put it behind a Service of Type=LoadBalancer
.
First, create a loadbalancer Service and wait for it to acquire an IP
then, update the ingress controller so it adopts the static IP of the Service by passing the --publish-service
flag (the example yaml used in the next step already has it set to "nginx-ingress-lb").
Assigning the IP to an Ingress
From here on every Ingress created with the ingress.class
annotation set to nginx
will get the IP allocated in the previous step
Retaining the IP
You can test retention by deleting the Ingress
Note that unlike the GCE Ingress, the same loadbalancer IP is shared amongst all Ingresses, because all requests are proxied through the same set of nginx controllers.
Promote ephemeral to static IP
To promote the allocated IP to static, you can update the Service manifest
and promote the IP to static (promotion works differently for cloudproviders, provided example is for GKE/GCE) `
Now even if the Service is deleted, the IP will persist, so you can recreate the Service with spec.loadBalancerIP
set to 104.154.109.191
.
Last updated