To check if the ingress controller pods have started, run the following command:
-kubectl get pods --all-namespaces -l app=ingress-nginx --watch +kubectl get pods --all-namespaces -l app.kubernetes.io/name=ingress-nginx --watchOnce the operator pods are running, you can cancel the above command by typing
Ctrl+C. @@ -1447,7 +1447,7 @@ Now, you are ready to create your first ingress.Detect installed version¶
To detect which version of the ingress controller is running, exec into the pod and run
nginx-ingress-controller versioncommand.@@ -1462,7 +1462,7 @@ To install the chart with the release namePOD_NAMESPACE=ingress-nginx -POD_NAME=$(kubectl get pods -n $POD_NAMESPACE -l app=ingress-nginx -o jsonpath='{.items[0].metadata.name}') +POD_NAME=$(kubectl get pods -n $POD_NAMESPACE -l app.kubernetes.io/name=ingress-nginx -o jsonpath='{.items[0].metadata.name}') kubectl exec -it $POD_NAME -n $POD_NAMESPACE -- /nginx-ingress-controller --versionmy-nginx
Detect installed version:
-POD_NAME=$(kubectl get pods -l app=nginx-ingress -o jsonpath='{.items[0].metadata.name}') +diff --git a/examples/customization/custom-configuration/configmap.yaml b/examples/customization/custom-configuration/configmap.yaml index b5b5c02fd..df2a84bdd 100644 --- a/examples/customization/custom-configuration/configmap.yaml +++ b/examples/customization/custom-configuration/configmap.yaml @@ -4,7 +4,8 @@ metadata: name: nginx-configuration namespace: ingress-nginx labels: - app: ingress-nginx + app.kubernetes.io/name: ingress-nginx + app.kubernetes.io/part-of: ingress-nginx data: proxy-connect-timeout: "10" proxy-read-timeout: "120" diff --git a/examples/customization/custom-errors/custom-default-backend.yaml b/examples/customization/custom-errors/custom-default-backend.yaml index cc97c8c1f..0d6f2cd7a 100644 --- a/examples/customization/custom-errors/custom-default-backend.yaml +++ b/examples/customization/custom-errors/custom-default-backend.yaml @@ -4,10 +4,12 @@ kind: Service metadata: name: nginx-errors labels: - app: nginx-errors + app.kubernetes.io/name: nginx-errors + app.kubernetes.io/part-of: ingress-nginx spec: selector: - app: nginx-errors + app.kubernetes.io/name: nginx-errors + app.kubernetes.io/part-of: ingress-nginx ports: - port: 80 targetPort: 8080 @@ -18,15 +20,20 @@ kind: Deployment apiVersion: apps/v1beta2 metadata: name: nginx-errors + labels: + app.kubernetes.io/name: nginx-errors + app.kubernetes.io/part-of: ingress-nginx spec: replicas: 1 selector: matchLabels: - app: nginx-errors + app.kubernetes.io/name: nginx-errors + app.kubernetes.io/part-of: ingress-nginx template: metadata: labels: - app: nginx-errors + app.kubernetes.io/name: nginx-errors + app.kubernetes.io/part-of: ingress-nginx spec: containers: - name: nginx-error-server diff --git a/examples/customization/custom-headers/configmap.yaml b/examples/customization/custom-headers/configmap.yaml index 27fed44c8..133b0a1c8 100644 --- a/examples/customization/custom-headers/configmap.yaml +++ b/examples/customization/custom-headers/configmap.yaml @@ -6,4 +6,5 @@ metadata: name: nginx-configuration namespace: ingress-nginx labels: - app: ingress-nginx \ No newline at end of file + app.kubernetes.io/name: ingress-nginx + app.kubernetes.io/part-of: ingress-nginx diff --git a/examples/customization/ssl-dh-param/README/index.html b/examples/customization/ssl-dh-param/README/index.html index 19a903f1a..0e4dc298e 100644 --- a/examples/customization/ssl-dh-param/README/index.html +++ b/examples/customization/ssl-dh-param/README/index.html @@ -1148,7 +1148,8 @@ use a ConfigMap to configure custom Diffie-Hellman parameters file to help with name: nginx-configuration namespace: ingress-nginx labels: - app: ingress-nginx + app.kubernetes.io/name: ingress-nginx + app.kubernetes.io/part-of: ingress-nginxPOD_NAME=$(kubectl get pods -l app.kubernetes.io/name=ingress-nginx -o jsonpath='{.items[0].metadata.name}') kubectl exec -it $POD_NAME -- /nginx-ingress-controller --version
$ kubectl create -f configmap.yaml @@ -1168,7 +1169,8 @@ use a ConfigMap to configure custom Diffie-Hellman parameters file to help with name: nginx-configuration namespace: ingress-nginx labels: - app: ingress-nginx + app.kubernetes.io/name: ingress-nginx + app.kubernetes.io/part-of: ingress-nginx
$ kubectl create -f ssl-dh-param.yaml diff --git a/examples/customization/ssl-dh-param/configmap.yaml b/examples/customization/ssl-dh-param/configmap.yaml index 71dd2903c..f4382d9a8 100644 --- a/examples/customization/ssl-dh-param/configmap.yaml +++ b/examples/customization/ssl-dh-param/configmap.yaml @@ -6,4 +6,5 @@ metadata: name: nginx-configuration namespace: ingress-nginx labels: - app: ingress-nginx + app.kubernetes.io/name: ingress-nginx + app.kubernetes.io/part-of: ingress-nginx diff --git a/examples/multi-tls/multi-tls.yaml b/examples/multi-tls/multi-tls.yaml index 93fed805e..f6ae876d0 100644 --- a/examples/multi-tls/multi-tls.yaml +++ b/examples/multi-tls/multi-tls.yaml @@ -3,7 +3,8 @@ kind: Service metadata: name: nginx labels: - app: nginx + app.kubernetes.io/name: ingress-nginx + app.kubernetes.io/part-of: ingress-nginx spec: ports: - port: 80 @@ -11,18 +12,23 @@ spec: protocol: TCP name: http selector: - app: nginx + app.kubernetes.io/name: ingress-nginx + app.kubernetes.io/part-of: ingress-nginx --- apiVersion: v1 kind: ReplicationController metadata: name: nginx + labels: + app.kubernetes.io/name: ingress-nginx + app.kubernetes.io/part-of: ingress-nginx spec: replicas: 1 template: metadata: labels: - app: nginx + app.kubernetes.io/name: ingress-nginx + app.kubernetes.io/part-of: ingress-nginx spec: containers: - name: nginx @@ -35,7 +41,8 @@ kind: Service metadata: name: http-svc labels: - app: http-svc + app.kubernetes.io/name: http-svc + app.kubernetes.io/part-of: ingress-nginx spec: ports: - port: 80 @@ -43,18 +50,23 @@ spec: protocol: TCP name: http selector: - app: http-svc + app.kubernetes.io/name: http-svc + app.kubernetes.io/part-of: ingress-nginx --- apiVersion: v1 kind: ReplicationController metadata: name: http-svc + labels: + app.kubernetes.io/name: http-svc + app.kubernetes.io/part-of: ingress-nginx spec: replicas: 1 template: metadata: labels: - app: http-svc + app.kubernetes.io/name: http-svc + app.kubernetes.io/part-of: ingress-nginx spec: containers: - name: http-svc @@ -113,4 +125,4 @@ spec: - backend: serviceName: nginx servicePort: 80 - path: / \ No newline at end of file + path: / diff --git a/examples/static-ip/nginx-ingress-controller.yaml b/examples/static-ip/nginx-ingress-controller.yaml index 776525dca..6664d0ddd 100644 --- a/examples/static-ip/nginx-ingress-controller.yaml +++ b/examples/static-ip/nginx-ingress-controller.yaml @@ -3,16 +3,19 @@ kind: Deployment metadata: name: nginx-ingress-controller labels: - k8s-app: nginx-ingress-controller + app.kubernetes.io/name: ingress-nginx + app.kubernetes.io/part-of: ingress-nginx spec: replicas: 1 selector: matchLabels: - k8s-app: nginx-ingress-controller + app.kubernetes.io/name: ingress-nginx + app.kubernetes.io/part-of: ingress-nginx template: metadata: labels: - k8s-app: nginx-ingress-controller + app.kubernetes.io/name: ingress-nginx + app.kubernetes.io/part-of: ingress-nginx spec: # hostNetwork makes it possible to use ipv6 and to preserve the source IP correctly regardless of docker configuration # however, it is not a hard dependency of the nginx-ingress-controller itself and it may cause issues if port 10254 already is taken on the host diff --git a/examples/static-ip/static-ip-svc.yaml b/examples/static-ip/static-ip-svc.yaml index 27de0690d..b64cf96cb 100644 --- a/examples/static-ip/static-ip-svc.yaml +++ b/examples/static-ip/static-ip-svc.yaml @@ -4,7 +4,8 @@ kind: Service metadata: name: nginx-ingress-lb labels: - app: nginx-ingress-lb + app.kubernetes.io/name: ingress-nginx + app.kubernetes.io/part-of: ingress-nginx spec: externalTrafficPolicy: Local type: LoadBalancer @@ -18,5 +19,5 @@ spec: targetPort: 443 selector: # Selects nginx-ingress-controller pods - k8s-app: nginx-ingress-controller - + app.kubernetes.io/name: ingress-nginx + app.kubernetes.io/part-of: ingress-nginx diff --git a/search/search_index.json b/search/search_index.json index e9c48ffe2..b6bbbb0c9 100644 --- a/search/search_index.json +++ b/search/search_index.json @@ -17,7 +17,7 @@ }, { "location": "/deploy/", - "text": "Installation Guide\n\u00b6\n\n\nContents\n\u00b6\n\n\n\n\nGeneric Deployment\n\n\nMandatory command\n\n\nProvider Specific Steps\n\n\nDocker for Mac\n\n\nminikube\n\n\nAWS\n\n\nGCE - GKE\n\n\nAzure\n\n\nBare-metal\n\n\n\n\n\n\nVerify installation\n\n\nDetect installed version\n\n\nUsing Helm\n\n\n\n\nGeneric Deployment\n\u00b6\n\n\nThe following resources are required for a generic deployment.\n\n\nMandatory command\n\u00b6\n\n\nkubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/mandatory.yaml\n\n\n\n\n\nProvider Specific Steps\n\u00b6\n\n\nThere are cloud provider specific yaml files.\n\n\nDocker for Mac\n\u00b6\n\n\nKubernetes is available in Docker for Mac (from \nversion 18.06.0-ce\n)\n\n\nCreate a service\n\n\nkubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/provider/cloud-generic.yaml\n\n\n\n\n\nminikube\n\u00b6\n\n\nFor standard usage:\n\n\nminikube addons enable ingress\n\n\n\n\n\nFor development:\n\n\n\n\nDisable the ingress addon:\n\n\n\n\n$\n minikube addons disable ingress\n\n\n\n\n\n\nExecute \nmake dev-env\n\n\nConfirm the \nnginx-ingress-controller\n deployment exists:\n\n\n\n\n$\n kubectl get pods -n ingress-nginx \n\nNAME READY STATUS RESTARTS AGE\n\n\ndefault-http-backend-66b447d9cf-rrlf9 1/1 Running 0 12s\n\n\nnginx-ingress-controller-fdcdcd6dd-vvpgs 1/1 Running 0 11s\n\n\n\n\n\nAWS\n\u00b6\n\n\nIn AWS we use an Elastic Load Balancer (ELB) to expose the NGINX Ingress controller behind a Service of \nType=LoadBalancer\n.\nSince Kubernetes v1.9.0 it is possible to use a classic load balancer (ELB) or network load balancer (NLB)\nPlease check the \nelastic load balancing AWS details page\n\n\nElastic Load Balancer - ELB\n\u00b6\n\n\nThis setup requires to choose in which layer (L4 or L7) we want to configure the ELB:\n\n\n\n\nLayer 4\n: use TCP as the listener protocol for ports 80 and 443.\n\n\nLayer 7\n: use HTTP as the listener protocol for port 80 and terminate TLS in the ELB\n\n\n\n\nFor L4:\n\n\nkubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/provider/aws/service-l4.yaml\n\n\nkubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/provider/aws/patch-configmap-l4.yaml\n\n\n\n\n\nFor L7:\n\n\nChange line of the file \nprovider/aws/service-l7.yaml\n replacing the dummy id with a valid one \n\"arn:aws:acm:us-west-2:XXXXXXXX:certificate/XXXXXX-XXXXXXX-XXXXXXX-XXXXXXXX\"\n\nThen execute:\n\n\nkubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/provider/aws/service-l7.yaml\n\n\nkubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/provider/aws/patch-configmap-l7.yaml\n\n\n\n\n\nThis example creates an ELB with just two listeners, one in port 80 and another in port 443\n\n\n\n\nNetwork Load Balancer (NLB)\n\u00b6\n\n\nThis type of load balancer is supported since v1.10.0 as an ALPHA feature.\n\n\nkubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/provider/aws/service-nlb.yaml\n\n\n\n\n\nGCE - GKE\n\u00b6\n\n\nkubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/provider/cloud-generic.yaml\n\n\n\n\n\nImportant Note:\n proxy protocol is not supported in GCE/GKE\n\n\nAzure\n\u00b6\n\n\nkubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/provider/cloud-generic.yaml\n\n\n\n\n\nBare-metal\n\u00b6\n\n\nUsing \nNodePort\n:\n\n\nkubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/provider/baremetal/service-nodeport.yaml\n\n\n\n\n\n\n\nTip\n\n\nFor extended notes regarding deployments on bare-metal, see \nBare-metal considerations\n.\n\n\n\n\nVerify installation\n\u00b6\n\n\nTo check if the ingress controller pods have started, run the following command:\n\n\nkubectl get pods --all-namespaces -l app=ingress-nginx --watch\n\n\n\n\n\nOnce the operator pods are running, you can cancel the above command by typing \nCtrl+C\n.\nNow, you are ready to create your first ingress.\n\n\nDetect installed version\n\u00b6\n\n\nTo detect which version of the ingress controller is running, exec into the pod and run \nnginx-ingress-controller version\n command.\n\n\nPOD_NAMESPACE=ingress-nginx\n\n\nPOD_NAME=$(kubectl get pods -n $POD_NAMESPACE -l app=ingress-nginx -o jsonpath='{.items[0].metadata.name}')\n\n\nkubectl exec -it $POD_NAME -n $POD_NAMESPACE -- /nginx-ingress-controller --version\n\n\n\n\n\nUsing Helm\n\u00b6\n\n\nNGINX Ingress controller can be installed via \nHelm\n using the chart \nstable/nginx-ingress\n from the official charts repository. \nTo install the chart with the release name \nmy-nginx\n:\n\n\nhelm install stable/nginx-ingress --name my-nginx\n\n\n\n\n\nIf the kubernetes cluster has RBAC enabled, then run:\n\n\nhelm install stable/nginx-ingress --name my-nginx --set rbac.create=true\n\n\n\n\n\nDetect installed version:\n\n\nPOD_NAME=$(kubectl get pods -l app=nginx-ingress -o jsonpath='{.items[0].metadata.name}')\n\n\nkubectl exec -it $POD_NAME -- /nginx-ingress-controller --version", + "text": "Installation Guide\n\u00b6\n\n\nContents\n\u00b6\n\n\n\n\nGeneric Deployment\n\n\nMandatory command\n\n\nProvider Specific Steps\n\n\nDocker for Mac\n\n\nminikube\n\n\nAWS\n\n\nGCE - GKE\n\n\nAzure\n\n\nBare-metal\n\n\n\n\n\n\nVerify installation\n\n\nDetect installed version\n\n\nUsing Helm\n\n\n\n\nGeneric Deployment\n\u00b6\n\n\nThe following resources are required for a generic deployment.\n\n\nMandatory command\n\u00b6\n\n\nkubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/mandatory.yaml\n\n\n\n\n\nProvider Specific Steps\n\u00b6\n\n\nThere are cloud provider specific yaml files.\n\n\nDocker for Mac\n\u00b6\n\n\nKubernetes is available in Docker for Mac (from \nversion 18.06.0-ce\n)\n\n\nCreate a service\n\n\nkubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/provider/cloud-generic.yaml\n\n\n\n\n\nminikube\n\u00b6\n\n\nFor standard usage:\n\n\nminikube addons enable ingress\n\n\n\n\n\nFor development:\n\n\n\n\nDisable the ingress addon:\n\n\n\n\n$\n minikube addons disable ingress\n\n\n\n\n\n\nExecute \nmake dev-env\n\n\nConfirm the \nnginx-ingress-controller\n deployment exists:\n\n\n\n\n$\n kubectl get pods -n ingress-nginx \n\nNAME READY STATUS RESTARTS AGE\n\n\ndefault-http-backend-66b447d9cf-rrlf9 1/1 Running 0 12s\n\n\nnginx-ingress-controller-fdcdcd6dd-vvpgs 1/1 Running 0 11s\n\n\n\n\n\nAWS\n\u00b6\n\n\nIn AWS we use an Elastic Load Balancer (ELB) to expose the NGINX Ingress controller behind a Service of \nType=LoadBalancer\n.\nSince Kubernetes v1.9.0 it is possible to use a classic load balancer (ELB) or network load balancer (NLB)\nPlease check the \nelastic load balancing AWS details page\n\n\nElastic Load Balancer - ELB\n\u00b6\n\n\nThis setup requires to choose in which layer (L4 or L7) we want to configure the ELB:\n\n\n\n\nLayer 4\n: use TCP as the listener protocol for ports 80 and 443.\n\n\nLayer 7\n: use HTTP as the listener protocol for port 80 and terminate TLS in the ELB\n\n\n\n\nFor L4:\n\n\nkubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/provider/aws/service-l4.yaml\n\n\nkubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/provider/aws/patch-configmap-l4.yaml\n\n\n\n\n\nFor L7:\n\n\nChange line of the file \nprovider/aws/service-l7.yaml\n replacing the dummy id with a valid one \n\"arn:aws:acm:us-west-2:XXXXXXXX:certificate/XXXXXX-XXXXXXX-XXXXXXX-XXXXXXXX\"\n\nThen execute:\n\n\nkubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/provider/aws/service-l7.yaml\n\n\nkubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/provider/aws/patch-configmap-l7.yaml\n\n\n\n\n\nThis example creates an ELB with just two listeners, one in port 80 and another in port 443\n\n\n\n\nNetwork Load Balancer (NLB)\n\u00b6\n\n\nThis type of load balancer is supported since v1.10.0 as an ALPHA feature.\n\n\nkubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/provider/aws/service-nlb.yaml\n\n\n\n\n\nGCE - GKE\n\u00b6\n\n\nkubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/provider/cloud-generic.yaml\n\n\n\n\n\nImportant Note:\n proxy protocol is not supported in GCE/GKE\n\n\nAzure\n\u00b6\n\n\nkubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/provider/cloud-generic.yaml\n\n\n\n\n\nBare-metal\n\u00b6\n\n\nUsing \nNodePort\n:\n\n\nkubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/provider/baremetal/service-nodeport.yaml\n\n\n\n\n\n\n\nTip\n\n\nFor extended notes regarding deployments on bare-metal, see \nBare-metal considerations\n.\n\n\n\n\nVerify installation\n\u00b6\n\n\nTo check if the ingress controller pods have started, run the following command:\n\n\nkubectl get pods --all-namespaces -l app.kubernetes.io/name=ingress-nginx --watch\n\n\n\n\n\nOnce the operator pods are running, you can cancel the above command by typing \nCtrl+C\n.\nNow, you are ready to create your first ingress.\n\n\nDetect installed version\n\u00b6\n\n\nTo detect which version of the ingress controller is running, exec into the pod and run \nnginx-ingress-controller version\n command.\n\n\nPOD_NAMESPACE=ingress-nginx\n\n\nPOD_NAME=$(kubectl get pods -n $POD_NAMESPACE -l app.kubernetes.io/name=ingress-nginx -o jsonpath='{.items[0].metadata.name}')\n\n\nkubectl exec -it $POD_NAME -n $POD_NAMESPACE -- /nginx-ingress-controller --version\n\n\n\n\n\nUsing Helm\n\u00b6\n\n\nNGINX Ingress controller can be installed via \nHelm\n using the chart \nstable/nginx-ingress\n from the official charts repository. \nTo install the chart with the release name \nmy-nginx\n:\n\n\nhelm install stable/nginx-ingress --name my-nginx\n\n\n\n\n\nIf the kubernetes cluster has RBAC enabled, then run:\n\n\nhelm install stable/nginx-ingress --name my-nginx --set rbac.create=true\n\n\n\n\n\nDetect installed version:\n\n\nPOD_NAME=$(kubectl get pods -l app.kubernetes.io/name=ingress-nginx -o jsonpath='{.items[0].metadata.name}')\n\n\nkubectl exec -it $POD_NAME -- /nginx-ingress-controller --version", "title": "Installation Guide" }, { @@ -87,17 +87,17 @@ }, { "location": "/deploy/#verify-installation", - "text": "To check if the ingress controller pods have started, run the following command: kubectl get pods --all-namespaces -l app=ingress-nginx --watch Once the operator pods are running, you can cancel the above command by typing Ctrl+C .\nNow, you are ready to create your first ingress.", + "text": "To check if the ingress controller pods have started, run the following command: kubectl get pods --all-namespaces -l app.kubernetes.io/name=ingress-nginx --watch Once the operator pods are running, you can cancel the above command by typing Ctrl+C .\nNow, you are ready to create your first ingress.", "title": "Verify installation" }, { "location": "/deploy/#detect-installed-version", - "text": "To detect which version of the ingress controller is running, exec into the pod and run nginx-ingress-controller version command. POD_NAMESPACE=ingress-nginx POD_NAME=$(kubectl get pods -n $POD_NAMESPACE -l app=ingress-nginx -o jsonpath='{.items[0].metadata.name}') kubectl exec -it $POD_NAME -n $POD_NAMESPACE -- /nginx-ingress-controller --version", + "text": "To detect which version of the ingress controller is running, exec into the pod and run nginx-ingress-controller version command. POD_NAMESPACE=ingress-nginx POD_NAME=$(kubectl get pods -n $POD_NAMESPACE -l app.kubernetes.io/name=ingress-nginx -o jsonpath='{.items[0].metadata.name}') kubectl exec -it $POD_NAME -n $POD_NAMESPACE -- /nginx-ingress-controller --version", "title": "Detect installed version" }, { "location": "/deploy/#using-helm", - "text": "NGINX Ingress controller can be installed via Helm using the chart stable/nginx-ingress from the official charts repository. \nTo install the chart with the release name my-nginx : helm install stable/nginx-ingress --name my-nginx If the kubernetes cluster has RBAC enabled, then run: helm install stable/nginx-ingress --name my-nginx --set rbac.create=true Detect installed version: POD_NAME=$(kubectl get pods -l app=nginx-ingress -o jsonpath='{.items[0].metadata.name}') kubectl exec -it $POD_NAME -- /nginx-ingress-controller --version", + "text": "NGINX Ingress controller can be installed via Helm using the chart stable/nginx-ingress from the official charts repository. \nTo install the chart with the release name my-nginx : helm install stable/nginx-ingress --name my-nginx If the kubernetes cluster has RBAC enabled, then run: helm install stable/nginx-ingress --name my-nginx --set rbac.create=true Detect installed version: POD_NAME=$(kubectl get pods -l app.kubernetes.io/name=ingress-nginx -o jsonpath='{.items[0].metadata.name}') kubectl exec -it $POD_NAME -- /nginx-ingress-controller --version", "title": "Using Helm" }, { @@ -1477,7 +1477,7 @@ }, { "location": "/examples/customization/ssl-dh-param/README/", - "text": "Custom DH parameters for perfect forward secrecy\n\u00b6\n\n\nThis example aims to demonstrate the deployment of an nginx ingress controller and\nuse a ConfigMap to configure custom Diffie-Hellman parameters file to help with\n\"Perfect Forward Secrecy\".\n\n\nCustom configuration\n\u00b6\n\n\n$\n cat configmap.yaml\n\napiVersion: v1\n\n\ndata:\n\n\n ssl-dh-param: \"ingress-nginx/lb-dhparam\"\n\n\nkind: ConfigMap\n\n\nmetadata:\n\n\n name: nginx-configuration\n\n\n namespace: ingress-nginx\n\n\n labels:\n\n\n app: ingress-nginx\n\n\n\n\n\n$\n kubectl create -f configmap.yaml\n\n\n\n\nCustom DH parameters secret\n\u00b6\n\n\n$\n> openssl dhparam \n1024\n \n2\n> /dev/null \n|\n base64\n\nLS0tLS1CRUdJTiBESCBQQVJBTUVURVJ...\n\n\n\n\n\n$\n cat ssl-dh-param.yaml\n\napiVersion: v1\n\n\ndata:\n\n\n dhparam.pem: \"LS0tLS1CRUdJTiBESCBQQVJBTUVURVJ...\"\n\n\nkind: ConfigMap\n\n\nmetadata:\n\n\n name: nginx-configuration\n\n\n namespace: ingress-nginx\n\n\n labels:\n\n\n app: ingress-nginx\n\n\n\n\n\n$\n kubectl create -f ssl-dh-param.yaml\n\n\n\n\nTest\n\u00b6\n\n\nCheck the contents of the configmap is present in the nginx.conf file using:\n\nkubectl exec nginx-ingress-controller-873061567-4n3k2 -n kube-system cat /etc/nginx/nginx.conf", + "text": "Custom DH parameters for perfect forward secrecy\n\u00b6\n\n\nThis example aims to demonstrate the deployment of an nginx ingress controller and\nuse a ConfigMap to configure custom Diffie-Hellman parameters file to help with\n\"Perfect Forward Secrecy\".\n\n\nCustom configuration\n\u00b6\n\n\n$\n cat configmap.yaml\n\napiVersion: v1\n\n\ndata:\n\n\n ssl-dh-param: \"ingress-nginx/lb-dhparam\"\n\n\nkind: ConfigMap\n\n\nmetadata:\n\n\n name: nginx-configuration\n\n\n namespace: ingress-nginx\n\n\n labels:\n\n\n app.kubernetes.io/name: ingress-nginx\n\n\n app.kubernetes.io/part-of: ingress-nginx\n\n\n\n\n\n$\n kubectl create -f configmap.yaml\n\n\n\n\nCustom DH parameters secret\n\u00b6\n\n\n$\n> openssl dhparam \n1024\n \n2\n> /dev/null \n|\n base64\n\nLS0tLS1CRUdJTiBESCBQQVJBTUVURVJ...\n\n\n\n\n\n$\n cat ssl-dh-param.yaml\n\napiVersion: v1\n\n\ndata:\n\n\n dhparam.pem: \"LS0tLS1CRUdJTiBESCBQQVJBTUVURVJ...\"\n\n\nkind: ConfigMap\n\n\nmetadata:\n\n\n name: nginx-configuration\n\n\n namespace: ingress-nginx\n\n\n labels:\n\n\n app.kubernetes.io/name: ingress-nginx\n\n\n app.kubernetes.io/part-of: ingress-nginx\n\n\n\n\n\n$\n kubectl create -f ssl-dh-param.yaml\n\n\n\n\nTest\n\u00b6\n\n\nCheck the contents of the configmap is present in the nginx.conf file using:\n\nkubectl exec nginx-ingress-controller-873061567-4n3k2 -n kube-system cat /etc/nginx/nginx.conf", "title": "Custom DH parameters for perfect forward secrecy" }, { @@ -1487,12 +1487,12 @@ }, { "location": "/examples/customization/ssl-dh-param/README/#custom-configuration", - "text": "$ cat configmap.yaml apiVersion: v1 data: ssl-dh-param: \"ingress-nginx/lb-dhparam\" kind: ConfigMap metadata: name: nginx-configuration namespace: ingress-nginx labels: app: ingress-nginx $ kubectl create -f configmap.yaml", + "text": "$ cat configmap.yaml apiVersion: v1 data: ssl-dh-param: \"ingress-nginx/lb-dhparam\" kind: ConfigMap metadata: name: nginx-configuration namespace: ingress-nginx labels: app.kubernetes.io/name: ingress-nginx app.kubernetes.io/part-of: ingress-nginx $ kubectl create -f configmap.yaml", "title": "Custom configuration" }, { "location": "/examples/customization/ssl-dh-param/README/#custom-dh-parameters-secret", - "text": "$ > openssl dhparam 1024 2 > /dev/null | base64 LS0tLS1CRUdJTiBESCBQQVJBTUVURVJ... $ cat ssl-dh-param.yaml apiVersion: v1 data: dhparam.pem: \"LS0tLS1CRUdJTiBESCBQQVJBTUVURVJ...\" kind: ConfigMap metadata: name: nginx-configuration namespace: ingress-nginx labels: app: ingress-nginx $ kubectl create -f ssl-dh-param.yaml", + "text": "$ > openssl dhparam 1024 2 > /dev/null | base64 LS0tLS1CRUdJTiBESCBQQVJBTUVURVJ... $ cat ssl-dh-param.yaml apiVersion: v1 data: dhparam.pem: \"LS0tLS1CRUdJTiBESCBQQVJBTUVURVJ...\" kind: ConfigMap metadata: name: nginx-configuration namespace: ingress-nginx labels: app.kubernetes.io/name: ingress-nginx app.kubernetes.io/part-of: ingress-nginx $ kubectl create -f ssl-dh-param.yaml", "title": "Custom DH parameters secret" }, { diff --git a/sitemap.xml b/sitemap.xml index 35f7b5076..8feba4972 100644 --- a/sitemap.xml +++ b/sitemap.xml @@ -2,227 +2,227 @@\ No newline at end of file / -2018-09-04 +2018-09-05 daily /deploy/ -2018-09-04 +2018-09-05 daily /deploy/baremetal/ -2018-09-04 +2018-09-05 daily /deploy/rbac/ -2018-09-04 +2018-09-05 daily /deploy/upgrade/ -2018-09-04 +2018-09-05 daily /user-guide/nginx-configuration/ -2018-09-04 +2018-09-05 daily /user-guide/nginx-configuration/annotations/ -2018-09-04 +2018-09-05 daily /user-guide/nginx-configuration/configmap/ -2018-09-04 +2018-09-05 daily /user-guide/nginx-configuration/custom-template/ -2018-09-04 +2018-09-05 daily /user-guide/nginx-configuration/log-format/ -2018-09-04 +2018-09-05 daily /user-guide/cli-arguments/ -2018-09-04 +2018-09-05 daily /user-guide/custom-errors/ -2018-09-04 +2018-09-05 daily /user-guide/default-backend/ -2018-09-04 +2018-09-05 daily /user-guide/exposing-tcp-udp-services/ -2018-09-04 +2018-09-05 daily /user-guide/external-articles/ -2018-09-04 +2018-09-05 daily /user-guide/miscellaneous/ -2018-09-04 +2018-09-05 daily /user-guide/monitoring/ -2018-09-04 +2018-09-05 daily /user-guide/multiple-ingress/ -2018-09-04 +2018-09-05 daily /user-guide/tls/ -2018-09-04 +2018-09-05 daily /user-guide/third-party-addons/modsecurity/ -2018-09-04 +2018-09-05 daily /user-guide/third-party-addons/opentracing/ -2018-09-04 +2018-09-05 daily /examples/ -2018-09-04 +2018-09-05 daily /examples/PREREQUISITES/ -2018-09-04 +2018-09-05 daily /examples/affinity/cookie/README/ -2018-09-04 +2018-09-05 daily /examples/auth/basic/README/ -2018-09-04 +2018-09-05 daily /examples/auth/client-certs/README/ -2018-09-04 +2018-09-05 daily /examples/auth/external-auth/README/ -2018-09-04 +2018-09-05 daily /examples/auth/oauth-external-auth/README/ -2018-09-04 +2018-09-05 daily /examples/customization/configuration-snippets/README/ -2018-09-04 +2018-09-05 daily /examples/customization/custom-configuration/README/ -2018-09-04 +2018-09-05 daily /examples/customization/custom-errors/README/ -2018-09-04 +2018-09-05 daily /examples/customization/custom-headers/README/ -2018-09-04 +2018-09-05 daily /examples/customization/custom-upstream-check/README/ -2018-09-04 +2018-09-05 daily /examples/customization/external-auth-headers/README/ -2018-09-04 +2018-09-05 daily /examples/customization/ssl-dh-param/README/ -2018-09-04 +2018-09-05 daily /examples/customization/sysctl/README/ -2018-09-04 +2018-09-05 daily /examples/docker-registry/README/ -2018-09-04 +2018-09-05 daily /examples/grpc/README/ -2018-09-04 +2018-09-05 daily /examples/multi-tls/README/ -2018-09-04 +2018-09-05 daily /examples/rewrite/README/ -2018-09-04 +2018-09-05 daily /examples/static-ip/README/ -2018-09-04 +2018-09-05 daily /examples/tls-termination/README/ -2018-09-04 +2018-09-05 daily /development/ -2018-09-04 +2018-09-05 daily /how-it-works/ -2018-09-04 +2018-09-05 daily /troubleshooting/ -2018-09-04 +2018-09-05 daily