Skip to content

Commit e302b5d

Browse files
JTorreGciarams87
authored andcommitted
fix: KIC-545 fix broken link (#2013)
1 parent c4a45c1 commit e302b5d

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/content/installation/using-the-jwt-token-docker-secret.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ This document explains how to use the NGINX Plus Ingress Controller image from t
3333

3434
3. This secret can now be added to a deployment spec, or to a service account to apply to all deployments for a given SA spec. See the official documentation [here](https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/#create-a-pod-that-uses-your-secret) and [here](https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/#add-imagepullsecrets-to-a-service-account) for more details.
3535

36-
4. Update the deployment spec with the chosen image path. Choose the image from the available images listed [here](nginx-ingress-controller/technical-specifications/#images-with-nginx-plus).
36+
4. Update the deployment spec with the chosen image path. Choose the image from the available images listed [here](/nginx-ingress-controller/technical-specifications/#images-with-nginx-plus).
3737

3838
5. You can use the certificate and key from the MyF5 portal and the Docker registry API to list the available image tags for the repositories, e.g.:
3939
```

0 commit comments

Comments
 (0)