Closed davimmt closed 1 year ago
Also, I can probably add a bunch of annotations to Ingress aws-alb-ingress
defining all the hosts to be added and it would work, but I'd rather this be granularly-based (each app ingress with its own host), such as it wolud if I were to use CLB.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs 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
/lifecycle rotten
/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 and PRs.
This bot triages issues and PRs 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".
I'm provisioning an AWS EKS cluster with Kong Ingress and ExternalDNS. I want the ingress tied to an Application Load Balancer (not Classic). Problem is, as per AWS EKS limitations (correct me if wrong), ingresses such as Kong or NGINX aren't able to create an ALB, only NLB or CLB.
The workaround is to use AWS Ingress ALB Controller to issue an Application Load Balancer and point it to the ingress service controller.
The architecture would be something like: ALB (created by AWS ALB Ingress Controller) → Kong Controller Service → Kong IngressClass → Ingress (kubernetes object; per application) → ClusterIP Service (kubernetes object; per application)
Example:
ALB (created by AWS ALB Ingress Controller)
Service
kong-proxy
generated by Helm or whatever, pointing to Kong pod controllerIngress (kubernetes object; per application)
ClusterIP Service (kubernetes object; per application)
In this kind of architecture, the Ingress
app-a
will get the address from the Kong controller service's ClusterIP, so thats the IP that ExternalDNS will use to create the DNS records, but the real domain name to be used is from the Ingressaws-alb-ingress
. Is there any way to go around this issue?