# Kubernetes AWS & LoadBalancers?

**URL:** <https://forums.rocket.chat/t/kubernetes-aws-loadbalancers/13591>\
**Category:** Community Support\
**Tags:** kubernetes\
**Created:** [March 16, 2022, 5:34pm UTC](https://forums.rocket.chat/t/kubernetes-aws-loadbalancers/13591 "2022-03-16T17:34:12Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![IDECFilms](https://sea1.discourse-cdn.com/flex021/user_avatar/forums.rocket.chat/idecfilms/32/3615_2.png) [@IDECFilms](https://forums.rocket.chat/u/IDECFilms)\
**Post date:** [March 16, 2022, 5:34pm UTC](https://forums.rocket.chat/t/kubernetes-aws-loadbalancers/13591/1 "2022-03-16T17:34:12Z")

</div>

### Description

Hello, I am trying to launch rocket chat within our Kubernetes cluster hosted on AWS EKS. I am able to deploy the app and access the application though kubectl’s prot-forward mechanism .

loclahost:8888 → localhost:3000

My issues is that when I try to set the application up behind a Network LoadBalancer the application does not load. Even when I create a route53 DNS record for rocket chat and point it at the load balancer the application will not load. The command I used to install the helm chart was the following.

```auto
helm install dev rocketchat/rocketchat \
--set mongodb.auth.password=<Password1> \
--set mongodb.auth.rootPassword=<Password2> \
--set mongodb.auth.username=rocketchat \
--set host=<DNS Name in Route53> \
--set ingress.enabled=true \
--set service.type=LoadBalancer \
--set service.port=80 \
--set service.annotations."service\.beta\.kubernetes\.io/aws-load-balancer-type"=nlb-ip \
--set service.annotations."service\.beta\.kubernetes\.io/aws-load-balancer-proxy-protocol"=* \
--set service.annotations."service\.beta\.kubernetes\.io/aws-load-balancer-scheme"=internet-facing

```

Any help on this subject would be very helpful.

Thanks,  
Edwin M.

### Server Setup Information

Rocket.Chat Version: 4.5.2  
NodeJS Version: 14.18.3 - x64  
MongoDB Version: 4.4.11  
MongoDB Engine: unknown  
Platform: linux  
Process Port: 3000  
Site URL: http://:8080  
ReplicaSet OpLog: Enabled  
Commit Hash: ed2cb3fe61  
Commit Branch: HEAD  
Deployment Method: Kubernetes  
Number of Running Instances: 1  
Proxy: AWS Network LB