You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG REPORT
Version of Helm and Kubernetes:
Helm: v3.9.0
EKS version: 1.24
Which chart:
artifactory-ha - v7.55.6
Which product license (Enterprise/Pro/oss):
Enterprise
What happened:
EKS Fargate does not support classic load balancers. It only supports ALBs and NLBs and we want to use ALBs.
We also need NGINX rewrite rules because ALBs support routing, but not NGINX rewrite rules. We need to use both ALBs to allow traffic into the cluster and NGINX to rewrite requests to the artifactory service.
Using the following ingress values we can get EKS to spin up an ALB:
ingress:
enabled: true
className: alb
annotations:
alb.ingress.kubernetes.io/scheme: internal
alb.ingress.kubernetes.io/target-type: ip
However, it points directly to the artifactory service. We need the ability to create a rule that takes in traffic from the ALB ingress, sends it to NGINX for rewrites, which then sends the requests to artifactory.
What you expected to happen:
We need the ability to provision an ALB that sends traffic to the NGINX service as opposed to a classic load balancer.
How to reproduce it (as minimally and precisely as possible):
We tried to deploy the helm chart with the following ingress:
ingress:
enabled: true
className: alb
annotations:
alb.ingress.kubernetes.io/scheme: internal
alb.ingress.kubernetes.io/target-type: ip
We ended up with the following ingress pointing directly to the artifactory service instead of NGINX:
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG REPORT
Version of Helm and Kubernetes:
Helm: v3.9.0
EKS version: 1.24
Which chart:
artifactory-ha - v7.55.6
Which product license (Enterprise/Pro/oss):
Enterprise
What happened:
EKS Fargate does not support classic load balancers. It only supports ALBs and NLBs and we want to use ALBs.
We also need NGINX rewrite rules because ALBs support routing, but not NGINX rewrite rules. We need to use both ALBs to allow traffic into the cluster and NGINX to rewrite requests to the artifactory service.
We spin up ALBs in EKS Fargate using the AWS Load balancer controller for EKS described here:
https://docs.aws.amazon.com/eks/latest/userguide/aws-load-balancer-controller.html
Using the following ingress values we can get EKS to spin up an ALB:
However, it points directly to the artifactory service. We need the ability to create a rule that takes in traffic from the ALB ingress, sends it to NGINX for rewrites, which then sends the requests to artifactory.
What you expected to happen:
We need the ability to provision an ALB that sends traffic to the NGINX service as opposed to a classic load balancer.
How to reproduce it (as minimally and precisely as possible):
We tried to deploy the helm chart with the following ingress:
We ended up with the following ingress pointing directly to the artifactory service instead of NGINX:
Anything else we need to know:
We met with the Technical Account Manager and they said to submit this issue as a bug.
The text was updated successfully, but these errors were encountered: