magn2o

#!/bin/sh

set -eu -o pipefail

CONTAINER_NAME="eap_proxy"
IMAGE_NAME="pbrah/eap_proxy-udmpro"
IMAGE_TAG="v1.1"

container_exists() {
	podman container inspect "${1}" &>/dev/null

magicalyak

#!/bin/bash

### Run this on the nplus instances to fix the issue where they start before the controller is running

sudo mkdir -p /etc/systemd/system/controller-agent.service.d/
{ echo "[Service]";
  echo "Restart=on-failure";
  echo "RestartSec=60s";
} | sudo tee /etc/systemd/system/controller-agent.service.d/10-restart-delay.conf
sudo systemctl daemon-reload

bgautrea

kind: ConfigMap
apiVersion: v1
metadata:
  name: nginx-config
  namespace: nginx-ingress
data:
  enable-debug: "True"
  main-template: |
    user  nginx;
    worker_processes  {{.WorkerProcesses}};

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