Deploying ingress controller on eks fargate (private cluster)

[jainhitesh9998]

nginx ingress deploys very easily on eks managed node cluster, but while deploying on a private fargate cluster i'm getting the following error i deployed the nginx ingress controller in fargate with AllowPriviligeEscalation as False.

nginx: the configuration file /tmp/nginx-cfg370196987 syntax is ok
2021/03/31 12:06:40 [emerg] 71#71: bind() to 0.0.0.0:80 failed (13: Permission denied)
nginx: [emerg] bind() to 0.0.0.0:80 failed (13: Permission denied)
nginx: configuration file /tmp/nginx-cfg370196987 test failed ```

 Any inputs on deploying ingress controller(nginx or any) on a private fargate cluster

[TBBle]

Answered this at #4888 (comment)

[jainhitesh9998]

So Basically Ingress Controller won't work on fargate with all feature set

[TBBle]

Yeah, on Fargate you won't be able to use the TCP/UDP forwarding feature for ports below 1024. All other features (i.e. http/https on any port, and TCP/UDP forwarding on ports above 1024) should work with AllowPriviligeEscalation set to false, and appropriate other configuration changes.

[TBBle]

That said, I'm not sure why you'd use Ingress for TCP/UDP forwarding, if you're on AWS, you can use NLB-IP with Fargate for exposing TCP/UDP services from your cluster instead.

[rikatz]

As this is answered I’ll close the issue ;)

@TBBle thanks for your help on this!
/close

[k8s-ci-robot]

@rikatz: Closing this issue.

In response to this:

As this is answered I’ll close the issue ;)

@TBBle thanks for your help on this!
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.