From 056f04f3b64745dd389d192b153d389149315157 Mon Sep 17 00:00:00 2001 From: Rob Date: Wed, 16 Aug 2023 21:04:22 +0100 Subject: [PATCH] Update examples/private-public-ingress/README.md Co-authored-by: Apoorva Kulkarni --- examples/private-public-ingress/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/examples/private-public-ingress/README.md b/examples/private-public-ingress/README.md index e73d891efb..3443aec009 100644 --- a/examples/private-public-ingress/README.md +++ b/examples/private-public-ingress/README.md @@ -5,8 +5,8 @@ This example demonstrates how to provision an Amazon EKS cluster with two ingre This solution: * Deploys Amazon EKS, with 1 Managed Node Group using the Bottlerocket Amazon EKS Optimized AMI spread accross 3 availability zones. * Installs the AWS Load Balancer controller for creating Network Load Balancers and Application Load Balancers. This is the recommended approach instead of the in-tree AWS cloud provider load balancer controller. -* Installs an nginx ingress controller for public traffic -* Intstalls an nginx ingress controller for internal traffic +* Installs an ingress-nginx controller for public traffic +* Intstalls an ingress-nginx controller for internal traffic To expose your application services via an `Ingress` resource with this solution you can set the respective `ingressClassName` as either `nginx-ingress-external` or `nginx-ingress-internal`.