Skip to content

Naresh240/kong-ingress-controller

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

11 Commits
 
 
 
 
 
 

Repository files navigation

kong-ingress-controller

Pre-Requisites

1. EKS Cluster
2. Install Helm
3. Create Hosted zone under Route53 with our domain name
4. SetUP Kong
5. SetUP External DNS

SetUP EKS Cluster

EKS Cluster Setup

Helm Installation with Specific Version

curl -fsSL -o get_helm.sh https://raw.githubusercontent.com/helm/helm/main/scripts/get-helm-3
chmod 700 get_helm.sh
./get_helm.sh -v v3.8.2

Create Hosted zone under Route53 with our domain name

  1. Created Hosted zone as shown in belowImage

image

  1. COPY Name Servers Where we have purchased our Domain

image

SetUP Kong on EKS Cluster

## Kong Gateway (OSS) on Kubernetes native
kubectl apply -f https://bit.ly/kong-ingress-dbless

## Check the install status
kubectl get pods -n kong

SetUP External DNS on EKS Cluster

# Create ```aws-creds.conf``` file with below content
[default]
aws_access_key_id = XXXXXXXXXXXX
aws_secret_access_key = XXXXXXXXXXXXXXXXXXXXXXXXX

# create secret with below command
kubectl create secret generic aws-creds --from-file=creds=./aws-creds.conf

# Also create ```exnaldns-values.yaml``` file
---			  
clusterDomain: <domain name>
aws:
  credentials:
    secretName: aws-creds
  region: "us-east-1"
  
# Installation of External DNS
helm repo add bitnami https://charts.bitnami.com/bitnami
helm install external-dns bitnami/external-dns -f exnaldns-values.yaml

Deploy Application using below commands

kubectl apply -f deployment.yaml
kubectl apply -f service.yaml
kubectl apply -f ingress.yaml

Check pods, services and ingress details

kubectl get pods
kubectl get svc
kubectl get ingress

Check Hosted zone for new records added or not

image

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors