Fixed address in the Gateway API

Gilberto_de_Oliveira · November 28, 2025, 7:53pm

Kubernetes version: v1.33.1
Cloud being used: OKE - Cloud Oracle

This post is about migrating from ingress to gateway-api.
My problem is that the documentation says that if I don’t reference an address, a random public IP is assigned to my gateway…
Source: Gateway API | Kubernetes
Even with that reference, my gateway was created with 2 public IPs.
Below is my manifest file and a screenshot confirming the 2 IPs.
```yaml
apiVersion: gateway.networking.k8s.io/v1
kind: Gateway
metadata:
name: loki-gateway
namespace: loki
spec:
addresses:

type: IPAddress
value: 136.123.123.245
gatewayClassName: nginx
listeners:
name: loki-http
protocol: HTTP
port: 80
hostname: foo.example.com.br
allowedRoutes:
namespaces:
from: Same
name: loki-https
protocol: HTTPS
port: 443
hostname: foo.example.com.br
tls:
mode: Terminate
certificateRefs:
name: loki-tls
kind: Secret
group: “”
allowedRoutes:
namespaces:
from: Same
```

sodonovan · December 1, 2025, 9:43am

Hi @Gilberto_de_Oliveira thanks for your post!

I don’t see the screenshot that you are referring to. Could you double check that you’ve attached it?

From how you’re describing it, it seems like the two addresses you are seeing show up in the status.addresses field. Is that correct?

Gilberto_de_Oliveira · December 1, 2025, 11:58am

Follow print,

sodonovan · December 1, 2025, 1:00pm

Thanks!

When I tested with your Gateway resource, it only added one IP address to my Service’s External IP list.

Lets run a test. If you delete loki-gateway from your cluster, will both External IPs be remove from the loki-gateway-nginx service? Or does the 162.x.104.14 address stay there?

Gilberto_de_Oliveira · December 1, 2025, 2:31pm

Since it’s not possible to attach videos, I’m sending 1 screenshots that capture some of the assigned IPs immediately after the kubectl apply command.

Currently, it is no longer assigning two IPs simultaneously, as shown in the first image.

However, I still cannot assign a reserved IP address by referencing it.

spec:

addresses:

type: IPAddress

value

Gilberto_de_Oliveira · December 1, 2025, 6:09pm

It hadn’t happened at that moment, but I just checked, and the gateway has two public IPs. Check the application’s restart time.

sjberman · December 2, 2025, 7:13pm

@Gilberto_de_Oliveira Does the Service’s externalIPs field just have the single IP address that you specified in the Gateway? All that NGINX Gateway Fabric should be setting is that field.

If an additional IP address is being added, it tells me that the cloud provider is adding it. There may be a way to disable that, or you could try setting the following in the NginxProxy CRD

kubectl -n nginx-gateway edit nginxproxies.gateway.nginx.org ngf-proxy-config

spec:
   kubernetes:
     service:
       loadBalancerIP: x.x.x.x

Gilberto_de_Oliveira · December 3, 2025, 12:32pm

apiVersion: gateway.networking.k8s.io/v1
kind: Gateway
metadata:
name: loki-gateway
namespace: loki
spec:
addresses:

type: IPAddress
value: 136.123.123.245
gatewayClassName: nginx
listeners:

name: loki-http
protocol: HTTP
port: 80
hostname: my-dns.com.br
allowedRoutes:
namespaces:
from: Same

name: loki-https
protocol: HTTPS
port: 443
hostname: my-dns.com.br
tls:
mode: Terminate
certificateRefs:

name: loki-tls
kind: Secret
group: “”
allowedRoutes:
namespaces:
from: Same

The Gateway file, after being modified, now includes the IP Address.

==============================================
Command output
kubectl get -n loki svc/loki-gateway-nginx -o yaml

apiVersion: v1
kind: Service
metadata:
creationTimestamp: “2025-12-03T12:21:58Z”
finalizers:

service.kubernetes.io/load-balancer-cleanup
labels:
app.kubernetes.io/instance: nginx-gateway
app.kubernetes.io/managed-by: nginx-gateway-nginx
app.kubernetes.io/name: loki-gateway-nginx
gateway.networking.k8s.io/gateway-name: loki-gateway
name: loki-gateway-nginx
namespace: loki
resourceVersion: “332967551”
uid: 2950ac9f-3ad2-41f-748a7ea635d4
spec:
allocateLoadBalancerNodePorts: true
clusterIP: 10.96.101.194
clusterIPs:

10.96.101.194
externalIPs:

136.123.123.245          ( Fixed IP address, defined in the YAML file. )
externalTrafficPolicy: Local
healthCheckNodePort: 31843
internalTrafficPolicy: Cluster
ipFamilies:

IPv4
ipFamilyPolicy: PreferDualStack
ports:

name: port-80
nodePort: 32353
port: 80
protocol: TCP
targetPort: 80

name: port-443
nodePort: 30349
port: 443
protocol: TCP
targetPort: 443
selector:
app.kubernetes.io/instance: nginx-gateway
app.kubernetes.io/managed-by: nginx-gateway-nginx
app.kubernetes.io/name: loki-gateway-nginx
gateway.networking.k8s.io/gateway-name: loki-gateway
sessionAffinity: None
type: LoadBalancer
status:
loadBalancer:
ingress:

ip: 136.456.456.235 ( IP assigned automatically )
ipMode: VIP

Gilberto_de_Oliveira · December 3, 2025, 3:05pm

@sjberman
Could you check what I sent?

sjberman · December 3, 2025, 7:08pm

Did you happen to edit the NginxProxy resource as I suggested? I don’t see that configuration in your reply (it’s a little hard to read due to the formatting).

Gilberto_de_Oliveira · December 4, 2025, 11:39am

@sjberman
I tried editing, but right after applying it, it seems it wasn’t accepted, and it reverted to the previous IP, removing the lines I added.
The changes I sent in the comment were made via the manifest file.
Here’s a pastebin with better indentation.

sjberman · December 4, 2025, 3:02pm

Was there an error or something when you tried editing the NginxProxy CRD? This is the only way actually edit the NGINX Service with the loadBalancerIP field. Also be sure to check the status of your Gateway resource to see if there is any error messaging there regarding an Invalid NginxProxy configuration.

Here’s a guide on handling that resource: Data plane configuration | NGINX Documentation

Gilberto_de_Oliveira · December 5, 2025, 1:15pm

@sjberman
I believe that when you previously instructed me on how to edit the CRD, I did something wrong. I edited it correctly now, and it worked; the application only picked up one IP address, and it was the IP address I have reserved with my cloud provider.
Thank you very much for your support.

Gilberto_de_Oliveira · December 5, 2025, 1:34pm

One question: is this NginxProxy resource created when the Gateway Fabric is created?

sjberman · December 5, 2025, 3:07pm

That’s correct, when you first install NGINX Gateway Fabric, this resource is also installed. You can also create your own and attach it directly to the Gateway (the default one is attached to the GatewayClass), but that’s really only useful if you plan on defining multiple Gateways with different settings.

Glad you got it working!

Gilberto_de_Oliveira · December 9, 2025, 2:23pm

My problem has been explained and resolved. If anyone can close this topic, I would appreciate it.

system · December 16, 2025, 2:24pm

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.

Topic		Replies	Views
About the NGINX Gateway Fabric category NGINX Gateway Fabric	0	175	June 20, 2025
NGINX controller migration from ingress nginx NGINX Ingress Controller config , nginx-ingress , ingress-nginx	2	74	March 13, 2026
Except for one, multiple ingress resources within the same namespace are not being assigned a load balancer IP by the ingress controller NGINX Ingress Controller config	5	82	January 22, 2026
Migrating for k8s nginx ingress to f5 nginx ingress (ingress api) - no response NGINX Ingress Controller ingress-nginx	7	137	January 6, 2026
Curl command is working fine But UI URL is giving 404 Not Found issue NGINX Gateway Fabric nginx-gateway-fabric , web-server , rewrite , gateway-api	4	61	March 26, 2026

Fixed address in the Gateway API

Related topics