Skip to content

Fix broken links and example output #1373

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

Merged
merged 4 commits into from
Dec 13, 2023
Merged

Fix broken links and example output #1373

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
d5f05bc
Fix broken links and example output
Dec 12, 2023
9e402d8
Fix relref
Dec 12, 2023
921854e
Merge branch 'main' into docs/small-fixes
ADubhlaoich Dec 13, 2023
51e3850
Add md extension to relref
kate-osborn Dec 13, 2023
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
8 changes: 4 additions & 4 deletions examples/https-termination/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ reference a Secret in a different Namespace.

## 1. Deploy NGINX Gateway Fabric

1. Follow the [installation instructions](/docs/installation.md) to deploy NGINX Gateway Fabric.
1. Follow the [installation instructions](https://docs.nginx.com/nginx-gateway-fabric/installation/) to deploy NGINX Gateway Fabric.

1. Save the public IP address of NGINX Gateway Fabric into a shell variable:

Expand Down Expand Up @@ -195,19 +195,19 @@ You can also check the conditions of the Gateway `https` Listener to verify the
Conditions:
Last Transition Time: 2023-06-26T20:23:56Z
Message: Certificate ref to secret certificate/cafe-secret not permitted by any ReferenceGrant
Observed Generation: 2
Observed Generation: 1
Reason: RefNotPermitted
Status: False
Type: Accepted
Last Transition Time: 2023-06-26T20:23:56Z
Message: Certificate ref to secret certificate/cafe-secret not permitted by any ReferenceGrant
Observed Generation: 2
Observed Generation: 1
Reason: RefNotPermitted
Status: False
Type: ResolvedRefs
Last Transition Time: 2023-06-26T20:23:56Z
Message: Certificate ref to secret certificate/cafe-secret not permitted by any ReferenceGrant
Observed Generation: 2
Observed Generation: 1
Reason: Invalid
Status: False
Type: Programmed
Expand Down
2 changes: 1 addition & 1 deletion site/content/how-to/traffic-management/advanced-routing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -125,7 +125,7 @@ This request should receive a response from the `coffee-v1` Pod.

```text
Server address: 10.244.0.9:8080
Server name: coffee-v2-68bd55f798-s9z5q
Server name: coffee-v1-76c7c85bbd-cf8nz
```

If we want our request to be routed to `coffee-v2`, then we need to meet the defined conditions. We can include a header:
Expand Down
2 changes: 1 addition & 1 deletion site/content/how-to/traffic-management/routing-traffic-to-your-app.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -132,7 +132,7 @@ spec:
EOF
```

This gateway is associated with the NGINX Gateway Fabric through the **gatewayClassName** field. The default installation of NGINX Gateway Fabric creates a GatewayClass with the name **nginx**. NGINX Gateway Fabric will only configure gateways with a **gatewayClassName** of **nginx** unless you change the name via the `--gatewayclass` [command-line flag](/docs/cli-help.md#static-mode).
This gateway is associated with the NGINX Gateway Fabric through the **gatewayClassName** field. The default installation of NGINX Gateway Fabric creates a GatewayClass with the name **nginx**. NGINX Gateway Fabric will only configure gateways with a **gatewayClassName** of **nginx** unless you change the name via the `--gatewayclass` [command-line flag]({{< relref "/reference/cli-help.md#static-mode" >}}).

We specify a [listener](https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1.Listener) on the gateway to open an entry point on the cluster. In this case, since the coffee application accepts HTTP requests, we create an HTTP listener, named **http**, that listens on port 80.

Expand Down