Merge branch 'main' into vs-config-refactor

Author: jjngx

CHANGELOG.md

@@ -691,8 +691,7 @@ CHANGES:
   `redirect-to-https` and `ssl-redirect` ConfigMap keys no longer have any effect on generated configs for VirtualServer
   resources.
 - [745](https://github.com/nginx/kubernetes-ingress/pull/745): Improve routing rules. Update the spec of
-  VirtualServer and VirtualServerRoute accordingly. See YAML examples of the changes
-  [here](https://github.com/nginx/kubernetes-ingress/pull/745).
+  VirtualServer and VirtualServerRoute accordingly. See [YAML examples of the changes](https://github.com/nginx/kubernetes-ingress/pull/745).
 - [710](https://github.com/nginx/kubernetes-ingress/pull/710): Run IC as non-root. Make sure to use the updated
   manifests to install/upgrade the Ingress Controller.
 - [603](https://github.com/nginx/kubernetes-ingress/pull/603): Update apiVersion in Deployments and DaemonSets to
@@ -1095,7 +1094,7 @@ CHANGES:
 - [399](https://github.com/nginx/kubernetes-ingress/pull/399): Improve secret handling. **Note**: the PR changed how
   the Ingress Controller processes Ingress resources with TLS termination enabled but without any referenced (or with
   invalid) secrets and Ingress resources with JWT validation enabled but without any referenced (or with invalid) JWK.
-  Please read [here](https://github.com/nginx/kubernetes-ingress/pull/399) for more details.
+  Please [read here](https://github.com/nginx/kubernetes-ingress/pull/399) for more details.
 - [357](https://github.com/nginx/kubernetes-ingress/pull/357): Improve Project Layout and Refactor Controller
   Package. **Note**: the PR significantly changed the layout of the project to follow best practices.
 - [347](https://github.com/nginx/kubernetes-ingress/pull/347): Use edge version in manifests and Helm chart.
@@ -1262,8 +1261,8 @@ UPGRADE:
 - [166](https://github.com/nginx/kubernetes-ingress/pull/166): Watch Secret resources for updates. **Note**: If a
   Secret referenced by one or more Ingress resources becomes invalid or gets removed, the configuration for those
   Ingress resources will be disabled until there is a valid Secret.
-- [160](https://github.com/nginx/kubernetes-ingress/pull/160): Add support for events. See the details
-  [here](https://github.com/nginx/kubernetes-ingress/pull/160).
+- [160](https://github.com/nginx/kubernetes-ingress/pull/160): Add support for events.
+  See [the details here](https://github.com/nginx/kubernetes-ingress/pull/160).
 - [157](https://github.com/nginx/kubernetes-ingress/pull/157): Add graceful termination - when the Ingress Controller
   receives `SIGTERM`, it shutdowns itself as well as NGINX, using `nginx -s quit`.
 

CONTRIBUTING.md

@@ -76,7 +76,7 @@ fill in the template as provided.
 
 ### F5 Contributor License Agreement (CLA)
 
-F5 requires all external contributors to agree to the terms of the F5 CLA (available [here](https://github.com/f5/.github/blob/main/CLA/cla-markdown.md))
+F5 requires all external contributors to agree to [the terms of the F5 CLA](https://github.com/f5/.github/blob/main/CLA/cla-markdown.md))
 before any of their changes can be incorporated into an F5 Open Source repository.
 
 If you have not yet agreed to the F5 CLA terms and submit a PR to this repository, a bot will prompt you to view and

charts/nginx-ingress/values.schema.json

@@ -1,4 +1,4 @@
 # Installation
 
-This folder includes Kubernetes manifests for installing NGINX or NGINX Plus Ingress Controller. Read the installation
-instructions [here](https://docs.nginx.com/nginx-ingress-controller/installation/).
+This folder includes Kubernetes manifests for installing NGINX or NGINX Plus Ingress Controller. Read [the installation
+instructions](https://docs.nginx.com/nginx-ingress-controller/installation/).

deployments/README.md

@@ -57,16 +57,15 @@ kubectl apply -f webapp.yaml
 
 To set up Keycloak:
 
-1. Follow the steps in the "Configuring Keycloak" section of the documentation
-   [here](https://docs.nginx.com/nginx/deployment-guides/single-sign-on/keycloak/#configuring-keycloak):
+1. Follow the steps in the "Configuring Keycloak" [section of the documentation](https://docs.nginx.com/nginx/deployment-guides/single-sign-on/keycloak/#configuring-keycloak):
     1. To connect to Keycloak, use `https://keycloak.example.com`.
     1. Make sure to save the client secret for NGINX-Plus client to the `SECRET` shell variable:
 
         ```console
         SECRET=value
         ```
 
-1. Alternatively, execute the commands [here](./keycloak_setup.md).
+1. Alternatively, [execute the commands](./keycloak_setup.md).
 
 ## Step 5 - Deploy the Client Secret
 

examples/custom-resources/oidc/README.md

@@ -3,5 +3,4 @@
 You can deploy the NGINX or NGINX Plus controller as a [Daemon Set](https://kubernetes.io/docs/admin/daemons/). This
 allows you to deploy the controller on all or select nodes of your cluster.
 
-Read the installation instructions
-[here](https://docs.nginx.com/nginx-ingress-controller/installation/installation-with-manifests/).
+Read [the installation instructions](https://docs.nginx.com/nginx-ingress-controller/installation/installation-with-manifests/).

examples/ingress-resources/daemon-set/README.md

@@ -1,5 +1,5 @@
 # RBAC
 
 It is possible to run the Ingress Controller in a cluster with
-[RBAC](https://kubernetes.io/docs/admin/authorization/rbac/) enabled. Read the installation instructions
-[here](https://docs.nginx.com/nginx-ingress-controller/installation/installation-with-manifests/).
+[RBAC](https://kubernetes.io/docs/admin/authorization/rbac/) enabled.
+Read the [installation instructions](https://docs.nginx.com/nginx-ingress-controller/installation/installation-with-manifests/).

examples/shared-examples/rbac/README.md

@@ -191,7 +191,7 @@ For more information about the _LoadBalancer_ service, refer to the [Kubernetes
         kubectl apply -f deployments/service/loadbalancer-aws-elb.yaml
         ```
 
-        For more details see service guide [here](https://kubernetes-sigs.github.io/aws-load-balancer-controller/latest/)
+        For more details see service guide [here](https://kubernetes-sigs.github.io/aws-load-balancer-controller/latest/guide/service/annotations/#annotations)
 
 2. AWS users: Follow these additional steps to work with ELB in TCP mode.