Skip to content

Commit

Permalink
fix: change links to relref
Browse files Browse the repository at this point in the history
  • Loading branch information
Jcahilltorre committed Oct 26, 2022
1 parent b174c64 commit 26e0b5a
Showing 1 changed file with 3 additions and 3 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -9,8 +9,8 @@ docs: "DOCS-608"

This document explains how to use the NGINX Plus Ingress Controller image from the F5 Docker registry in your Kubernetes cluster by using your NGINX Ingress Controller subscription JWT token. **Please note that an NGINX Plus subscription certificate and key will not work with the F5 Docker registry.** You can also get the image using alternative methods:

* You can use Docker to pull an Ingress Controller image with NGINX Plus and push it to your private registry by following [these instructions](/nginx-ingress-controller/installation/pulling-ingress-controller-image).
* Please see the [information on how to build an Ingress Controller image](/nginx-ingress-controller/installation/building-ingress-controller-image) using the source code from this repository and your NGINX Plus subscription certificate and key.
* You can use Docker to pull an Ingress Controller image with NGINX Plus and push it to your private registry by following the [Pulling the Ingress Controller Image]({{< relref "/installation/pulling-ingress-controller-image.md" >}}) documentation.
* Please see the [information on how to build an Ingress Controller image]({{< relref "/installation/building-ingress-controller-image.md" >}}) using the source code from this repository and your NGINX Plus subscription certificate and key.
* Note that for NGINX Ingress Controller based on NGINX OSS, we provide the image through [DockerHub](https://hub.docker.com/r/nginx/nginx-ingress/).

## Prerequisites
Expand All @@ -34,7 +34,7 @@ This document explains how to use the NGINX Plus Ingress Controller image from t

3. You can now add this secret to a deployment spec or to a service account to apply to all deployments for a given SA spec. See the [Create a Pod that uses your Secret](https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/#create-a-pod-that-uses-your-secret) and [Add ImagePullSecrets to a service account](https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/#add-imagepullsecrets-to-a-service-account) documentation for more details.

4. Update the deployment spec with the chosen image path. Choose the image from the [available images](/nginx-ingress-controller/technical-specifications/#images-with-nginx-plus).
4. Update the deployment spec with the chosen image path. Choose the image from the [available images]({{< relref "/technical-specifications.md#images-with-nginx-plus" >}}).

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.:
```
Expand Down

0 comments on commit 26e0b5a

Please sign in to comment.