Fix documentation links

This commit is contained in:
Manuel de Brito Fontes 2018-01-18 12:28:27 -03:00
parent b50cdc0256
commit ac2c92e5ff
7 changed files with 9 additions and 9 deletions

View file

@ -10,7 +10,7 @@ The GCE ingress controller was moved to [github.com/kubernetes/ingress-gce](http
## Description
This repository contains the NGINX controller built around the [Kubernetes Ingress resource](http://kubernetes.io/docs/user-guide/ingress/) that uses [ConfigMap](https://kubernetes.io/docs/tasks/configure-pod-container/configmap/#understanding-configmaps) to store the NGINX configuration.
This repository contains the NGINX controller built around the [Kubernetes Ingress resource](http://kubernetes.io/docs/user-guide/ingress/) that uses [ConfigMap](https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-configmap/#understanding-configmaps-and-pods) to store the NGINX configuration.
Learn more about using Ingress on [k8s.io](http://kubernetes.io/docs/user-guide/ingress/)

View file

@ -5,8 +5,8 @@ This example demonstrates how to use the Rewrite annotations
## Prerequisites
You will need to make sure you Ingress targets exactly one Ingress
controller by specifying the [ingress.class annotation](/examples/PREREQUISITES.md#ingress-class),
and that you have an ingress controller [running](/examples/deployment) in your cluster.
controller by specifying the [ingress.class annotation](/README.md#annotation-ingressclass),
and that you have an ingress controller [running](/deploy/README.md) in your cluster.
## Deployment

View file

@ -6,8 +6,8 @@ This example demonstrates how to assign a static-ip to an Ingress on through the
You need a [TLS cert](/examples/PREREQUISITES.md#tls-certificates) and a [test HTTP service](/examples/PREREQUISITES.md#test-http-service) for this example.
You will also need to make sure your Ingress targets exactly one Ingress
controller by specifying the [ingress.class annotation](/examples/PREREQUISITES.md#ingress-class),
and that you have an ingress controller [running](/examples/deployment) in your cluster.
controller by specifying the [ingress.class annotation](/README.md#annotation-ingressclass),
and that you have an ingress controller [running](/deploy/README.md) in your cluster.
## Acquiring an IP

View file

@ -1,7 +1,7 @@
<!--
-----------------NOTICE------------------------
This file is referenced in code as
https://github.com/kubernetes/ingress-ingress/blob/master/docs/troubleshooting.md
https://github.com/kubernetes/ingress-nginx/blob/master/docs/troubleshooting.md
Do not move it without providing redirects.
-----------------------------------------------
-->

View file

@ -391,7 +391,7 @@ _References:_
Sets the name of the secret that contains Diffie-Hellman key to help with "Perfect Forward Secrecy".
_References:_
- https://www.openssl.org/docs/manmaster/apps/dhparam.html
- https://wiki.openssl.org/index.php/Manual:Dhparam(1)
- https://wiki.mozilla.org/Security/Server_Side_TLS#DHE_handshake_and_dhparam
- http://nginx.org/en/docs/http/ngx_http_ssl_module.html#ssl_dhparam

View file

@ -8,7 +8,7 @@ Each request to the default backend includes two headers:
**Important:** the custom backend must return the correct HTTP status code to be returned. NGINX do not changes the response from the custom default backend.
Using this two headers is possible to use a custom backend service like [this one](https://github.com/kubernetes/ingress-nginx/tree/master/examples/customization/custom-errors/nginx) that inspect each request and returns a custom error page with the format expected by the client. Please check the example [custom-errors](examples/customization/custom-errors/README.md)
Using this two headers is possible to use a custom backend service like [this one](https://github.com/kubernetes/ingress-nginx/tree/master/images/custom-error-pages) that inspect each request and returns a custom error page with the format expected by the client. Please check the example [custom-errors](https://github.com/kubernetes/ingress-nginx/tree/master/docs/examples/customization/custom-errors)
NGINX sends additional headers that can be used to build custom response:

View file

@ -286,7 +286,7 @@ type Configuration struct {
SSLECDHCurve string `json:"ssl-ecdh-curve,omitempty"`
// The secret that contains Diffie-Hellman key to help with "Perfect Forward Secrecy"
// https://www.openssl.org/docs/manmaster/apps/dhparam.html
// https://wiki.openssl.org/index.php/Manual:Dhparam(1)
// https://wiki.mozilla.org/Security/Server_Side_TLS#DHE_handshake_and_dhparam
// http://nginx.org/en/docs/http/ngx_http_ssl_module.html#ssl_dhparam
SSLDHParam string `json:"ssl-dh-param,omitempty"`