Channels
extensions
rancher-extensions
supermicro-sixsq
ozt
os
one-point-x
rio
onlinemeetup
v16-v21-migration
events
onlinetraining
training-1220
training-0110
training-0124
k3s-contributor
submariner
storage
k3os
windows
ci-cd
theranchcast
rfed_ara
nederlands
ukranian
danish
training-0131
masterclass
training-0207
training-0214
terraform-controller
epinio
phillydotnet
swarm
rancher-wrangler
deutsch
russian
chinese
mesos
français
japanese
arm
longhorn-dev
terraform-provider-rke
service-mesh
azure
gcp
academy
random
elemental
espanol
lima
harvester-dev
portugues
kubernetes
kim
hypper
kubewarden
opni
logging
neuvector-security
rancher-setup
developer
office-hours
mexico
cabpr
rke
vsphere
longhorn-storage
k3s
k3d
terraform-provider-rancher2
fleet
amazon
harvester
rke2
s3gw
hobbyfarm
rancher-desktop
general
Title
v
victorious-table-33884
04/27/2023, 12:17 PM@careful-appointment-9763: do you have deployed an ingress-nginx like stated in the documentation?
c
careful-appointment-9763
04/27/2023, 3:03 PMI will double-check that.
I was following https://kubernetes-sigs.github.io/aws-load-balancer-controller/
and https://kubernetes.github.io/cloud-provider-aws/
The provided templates illustrate the setup for legacy in-tree service load balancer for AWS NLB. AWS provides the documentation on how to use Network load balancing on Amazon EKS with AWS Load Balancer Controller.
@victorious-table-33884 any comment on in-tree versus AWS-provided?
when we tried in-tree we got a classic application load balancer, but we need a network load balancer that does not terminate TLS