robincher

image:
  repository: kong/kong-gateway
  tag: 3.4.3.5

env:
  prefix: /kong_prefix/
  database: "off"
  role: data_plane
  cluster_control_plane: kong-cp-cluster.kong-cp.svc.cluster.local:8005
  cluster_telemetry_endpoint: kong-cp-cluster-telemetry.kong-cp.svc.cluster.local:8006

robincher

image:
  repository: kong/kong-gateway
  tag: 3.4.3.5

env:
  # Env variables to overwrite, read more here https://github.com/Kong/kong/blob/master/kong.conf.default
  prefix: /kong_prefix/
  role: control_plane

  #Logs Output level https://docs.konghq.com/gateway/latest/configure/logging/

robincher

apiVersion: eksctl.io/v1alpha5
kind: ClusterConfig

metadata:
  name: kong-tal-eks
  region: ap-southeast-1

addons:
- name: vpc-cni
  version: latest

robincher

## Run Kong 3.2 with Docker Containers


#### Create Docker Network
docker network create kong-net

# Export License
export KONG_LICENSE_DATA=''

### Start a Postgres Container (If running db mode)

robincher

apiVersion: source.toolkit.fluxcd.io/v1beta2
kind: HelmRepository
metadata:
  name: kong
  namespace: flux-system
spec:
  interval: 30m
  url: https://charts.konghq.com
---
apiVersion: helm.toolkit.fluxcd.io/v2beta1

robincher

# Kong for Kubernetes with Kong Enterprise with Enterprise features enabled and
# exposed via TLS-enabled Ingresses. Before installing:
# * Several settings (search for the string "CHANGEME") require user-provided
#   Secrets. These Secrets must be created before installation.
# * Ingresses reference example "<service>.kong.CHANGEME.example" hostnames. These must
#   be changed to an actual hostname that resolve to your proxy.
# * Ensure that your session configurations create cookies that are usable
#   across your services. The admin session configuration must create cookies
#   that are sent to both the admin API and Kong Manager, and any Dev Portal
#   instances with authentication must create cookies that are sent to both

robincher

#!/bin/bash
export AWS_ACCOUNT_ID=$1
export AWS_INSTANCE_ROLE=$2
export EKS_CLUSTER_NAME=$3


if [ -z "$AWS_ACCOUNT_ID" ]
then
      echo -n "AWS Account Number: "
      read AWS_ACCOUNT_ID

robincher

#!/bin/bash
echo "Please enter database Password:"

read DB_PASSWD

if [ -z "DB_PASSWD" ]; then
  echo "Please DB Password"
  exit 1
fi

robincher

#!/bin/bash

# Create manual mappings between certificate and Consumer objec
curl -X POST -H 'Kong-Admin-Token:xxxxxx'  http://localhost:8001/Scratch/consumers/helios/mtls-auth  -d 'subject_name=helios.gemsapi.io'

# Test route with MTLS and Basic Auth Plugin enabled
 curl -kv -H 'Authorization: Bearer Basic xxxxxxx'  --key helios.key --cert helios.crt https://localhost:8443/mockbin/request

robincher

#!/bin/bash

#Generate Self-signed CA
openssl req -x509 -sha256 -nodes -days 365 -newkey rsa:2048 -keyout ca.key -out ca.crt

#Make a directory
mkdir client

#Generate Corresponding client certificate
openssl genrsa -out client/helios.key 2048