Improve and move the customization example

- Improve the customization example
- Move it to the docs folder
- Remove the example yaml files

README.md

@@ -35,7 +35,7 @@ We provide the following extensions to our Ingress controller:
 * [Session Persistence](examples/session-persistence) (NGINX Plus only), which guarantees that all the requests from the same client are always passed to the same backend container.
 * [Support for JWTs](examples/jwt) (NGINX Plus only), which allows NGINX Plus to authenticate requests by validating JSON Web Tokens (JWTs).
 
-Additional extensions as well as a mechanism to customize NGINX configuration are available. See [examples/customization](examples/customization).
+Additional extensions as well as a mechanism to customize NGINX configuration are available. See [ConfigMap and Annotations doc](docs/configmap-and-annotations.md).
 
 ## NGINX Ingress Controller Releases
 

docs/custom-annotations.md

@@ -4,7 +4,7 @@ Custom annotations enable you to quickly extend the Ingress Controller to suppor
 
 ## What are Custom Annotations
 
-NGINX Ingress Controller supports a number of annotations that fine tune NGINX configuration (for example, connection timeouts) or enable additional features (for example, JWT validation). The complete list of annotations is available [here](../examples/customization).
+NGINX Ingress Controller supports a number of annotations that fine tune NGINX configuration (for example, connection timeouts) or enable additional features (for example, JWT validation). The complete list of annotations is available [here](configmap-and-annotations.md).
 
 The annotations are provided only for the most common features and use cases, meaning that not every NGINX feature or a customization option is available through the annotations. Additionally, even if an annotation is available, it might not give you the satisfactory level of control of a particular NGINX feature. 
 

docs/installation.md

@@ -24,7 +24,7 @@ The installation manifests are located in the [deployments](../deployments) fold
 
     **Note**: The default server returns the Not Found page with the 404 status code for all requests for domains for which there are no Ingress rules defined. For testing purposes we include a self-signed certificate and key that we generated. However, we recommend that you use your own certificate and key.
 
-1. Create a config map for customizing NGINX configuration (read more about customization [here](../examples/customization)):
+1. Create a config map for customizing NGINX configuration (read more about customization [here](configmap-and-annotations.md)):
     ```
     $ kubectl apply -f common/nginx-config.yaml
     ```

docs/nginx-ingress-controllers.md

@@ -18,8 +18,8 @@ The table below summarizes the key difference between nginxinc/kubernetes-ingres
 | Commercial support | N/A | N/A | Included |
 | **Load balancing configuration** |
 | Merging Ingress rules with the same host | Supported | Supported | Supported |
-| HTTP load balancing extensions - Annotations | See the [supported annotations](https://github.com/kubernetes/ingress-nginx/blob/master/docs/user-guide/annotations.md) | See the [supported annotations](https://github.com/nginxinc/kubernetes-ingress/tree/master/examples/customization) | See the [supported annotations](https://github.com/nginxinc/kubernetes-ingress/tree/master/examples/customization)|
-| HTTP load balancing extensions -- ConfigMap | See the [supported ConfigMap keys](https://github.com/kubernetes/ingress-nginx/blob/master/docs/user-guide/configmap.md) | See the [supported ConfigMap keys](https://github.com/nginxinc/kubernetes-ingress/tree/master/examples/customization) | See the [supported ConfigMap keys](https://github.com/nginxinc/kubernetes-ingress/tree/master/examples/customization) |
+| HTTP load balancing extensions - Annotations | See the [supported annotations](https://github.com/kubernetes/ingress-nginx/blob/master/docs/user-guide/annotations.md) | See the [supported annotations](configmap-and-annotations.md) | See the [supported annotations](configmap-and-annotations.md)|
+| HTTP load balancing extensions -- ConfigMap | See the [supported ConfigMap keys](https://github.com/kubernetes/ingress-nginx/blob/master/docs/user-guide/configmap.md) | See the [supported ConfigMap keys](configmap-and-annotations.md) | See the [supported ConfigMap keys](configmap-and-annotations.md) |
 | TCP/UDP | Supported via a ConfigMap | Supported via a ConfigMap with native NGINX configuration | Supported via a ConfigMap with native NGINX configuration |
 | Websocket  | Supported | Supported via an [annotation](https://github.com/nginxinc/kubernetes-ingress/tree/master/examples/websocket) | Supported via an [annotation](https://github.com/nginxinc/kubernetes-ingress/tree/master/examples/websocket) |
 | TCP SSL Passthrough | Supported via a ConfigMap | Not supported | Not supported |

docs/report-ingress-status.md

@@ -13,7 +13,7 @@ The Ingress controller must be configured to report an Ingress status:
 
 1. Use the command-line flag `-report-ingress-status`.
 2. Define a source for an external address. This can be either of:
-    1. A user defined address, specified in the `external-status-address` [ConfigMap key](../examples/customization).
+    1. A user defined address, specified in the `external-status-address` [ConfigMap key](configmap-and-annotations.md).
     2. A Service of the type LoadBalancer configured with an external IP or address and specified by the `-external-service` command-line flag.
 3. If you're running multiple replicas of the Ingress controller, enable leader election with the `-enable-leader-election` flag
 to ensure that only one replica updates an Ingress status.

examples/custom-templates/README.md

@@ -1,6 +1,6 @@
 # Custom Templates
 
-The Ingress controller allows you to customize your templates through a [ConfigMap](https://github.com/nginxinc/kubernetes-ingress/tree/master/examples/customization) via the following keys:
+The Ingress controller allows you to customize your templates through a [ConfigMap](../../docs/configmap-and-annotations.md) via the following keys:
 * `main-template` - Sets the main NGINX configuration template.
 * `ingress-template` - Sets the Ingress NGINX configuration template for an Ingress resource.