Skip to content

fix: NGINX Gateway Fabric: Gateway deployed to default namespace conflicts with NginxProxy in nginx-gateway namespace #2120

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
JTorreG wants to merge 1 commit into from
+9 −8
Closed

fix: NGINX Gateway Fabric: Gateway deployed to default namespace conflicts with NginxProxy in nginx-gateway namespace #2120

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 9 additions & 8 deletions content/ngf/install/deploy-data-plane.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,6 +31,7 @@ apiVersion: gateway.networking.k8s.io/v1
kind: Gateway
metadata:
name: cafe
namespace: nginx-gateway
spec:
gatewayClassName: nginx
listeners:
Expand All @@ -43,7 +44,7 @@ EOF
To check that the Gateway has deployed correctly, use `kubectl describe` to check its status:

```shell
kubectl describe gateway
kubectl describe gateway -n nginx-gateway
```

You should see these conditions:
Expand Down Expand Up @@ -79,7 +80,7 @@ Conditions:
Using `kubectl get` you can see the NGINX Deployment:

```shell
kubectl get deployments
kubectl get deployments -n nginx-gateway
```
```text
NAME READY UP-TO-DATE AVAILABLE AGE
Expand All @@ -89,7 +90,7 @@ cafe-nginx 1/1 1 1 3m18s
You can also see the Service fronting it:

```shell
kubectl get services
kubectl get services -n nginx-gateway
```
```text
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
Expand Down Expand Up @@ -173,7 +174,7 @@ type: NodePort
After saving the changes, use `kubectl get` on the service, and you should see the service type has changed to `NodePort`.

```shell
kubectl get service cafe-nginx
kubectl get service cafe-nginx -n nginx-gateway
```
```text
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
Expand All @@ -199,11 +200,11 @@ infrastructure:
After saving the changes, check the Service and NGINX deployment with `kubectl describe`.

```shell
kubectl describe deployment cafe
kubectl describe deployment cafe-nginx -n nginx-gateway
```
```text
Name: cafe-nginx
Namespace: default
Namespace: nginx-gateway
CreationTimestamp: Mon, 05 May 2025 16:49:33 -0700
...
Pod Template:
Expand All @@ -219,11 +220,11 @@ Pod Template:
```

```shell
kubectl describe service cafe-nginx
kubectl describe service cafe-nginx -n nginx-gateway
```
```text
Name: cafe-nginx
Namespace: default
Namespace: nginx-gateway
Labels: app.kubernetes.io/instance=ngf
app.kubernetes.io/managed-by=ngf-nginx
app.kubernetes.io/name=cafe-nginx
Expand Down
Loading