Closed kylebisley closed 1 month ago
Hello @kylebisley ,
Have tried using this configuration to expose multiple ports for your service on NLB
apiVersion: v1
kind: Service
metadata:
name: my-service
annotations:
service.beta.kubernetes.io/aws-load-balancer-type: external
service.beta.kubernetes.io/aws-load-balancer-scheme: internet-facing
service.beta.kubernetes.io/aws-load-balancer-nlb-target-type: ip
namespace: my-namespace
spec:
type: LoadBalancer
selector:
app.kubernetes.io/name: MyApp
ports:
- name: http
port: 80
targetPort: 7777
- name: https
port: 443
targetPort: 7778
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/reopen
/remove-lifecycle rotten
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
@k8s-triage-robot: Closing this issue, marking it as "Not Planned".
Hey All, Asking here hoping someone can at least point me where to start. I'm using
aws-load-balancer-controller
to provision aNLB service
that is directing traffic atnginx
inside my cluster. This has been necessitated by some client architectural oddities I'll not go into (Normally I'd just use anALB
and be on my way)The
NLB
needs to listen on two specific ports withHTTP
(the firewalls forward my traffic on non-standard ports) lets call the ports7777
and7778
. I cannot figure out how to get theaws-load-balancer-controller
to provision listeners on those non-standard ports. I've tested it creating them manually and it works as intended but the7777
and7778
listeners get removed by theALB
eventually.With an ALB I'd use the annotation alb.ingress.kubernetes.io/listen-ports but I can't find a similar annotation or configuration option in the NLB/service documentation.
I'm close to abandoning the aws-load-balancer-controller at this point but frankly would struggle with how to get my traffic into my pods without its special sauce.
Any direction on this would be very much appreciated.
I'd happily create an update for the docs to codify this guidance if it's thought to be appropriate. Would love to save someone else my troubles.