pleshakov

Steps:

kubectl apply -f cafe.yaml
kubectl apply -f full.yaml
kubectl apply -f wildcard.yaml
kubectl apply -f gateway.yaml
kubectl apply -f routes.yaml

GW_IP=XXX.YYY.ZZZ.III # public IP of the data plane

pleshakov

Steps:

kubectl apply -f cafe.yaml
kubectl apply -f gateway.yaml
kubectl apply -f routes.yaml

GW_IP=XXX.YYY.ZZZ.III # public IP of the data plane
GW_PORT=<port number> # public port

pleshakov

TLS Passthrough in NGINX Plus Ingress Controller

This gist shows how to configure TLS passthrough in NGINX Plus Ingress Controller.

Currently, TLS passthrough is not supported with NGINX Plus Ingress Controller. Long-term, we will be adding support for TLS passthrough via our Custom resources. Short term, there is a workaround solution to enable TLS passthrough which you can find below.

In our example, we will deploy an Ingress resource with TLS termination and a TLS passthrough configuration and test that both work.

Prerequisites

pleshakov

Description

This demo shows how to enable sticky learn session persistence for an Ingress resource with the sessions shared among multiple NGINX Plus Ingress Controller pods.

Setup

1. Deploy the Ingress Controller as a deployment -- https://github.com/nginxinc/kubernetes-ingress/blob/master/docs/installation.md
2. Deploy a headless service for the Ingress Controller that will be used for zone synchronization:

$ kubectl apply -f nginx-ingress-zonesync.yaml

pleshakov

kind: ConfigMap
apiVersion: v1
metadata:
  name: nginx-config
  namespace: nginx-ingress
data:
  worker-processes: "1"
  log-format: '[$time_local] $remote_addr "$request" $status "$upstream_response_time"'