- Newest
- Most votes
- Most comments
Hello,
Hope you are well.
From the question I gathered that using ALB Ingress with Fargate launch type resulted in some validation error and some guidance is required on resolving this.
The ingress YAML file looks good and host does allow "-" according to the Application Load Balancer (ALB) documentation [1]. Error from the AWS Load Balancer Controller log does highlight regex error where value starts with "app*" at "tags.2.member.value" is the root cause. However the only reference to "app*" as a value is the host and there are no "tags.2.member.value" anywhere...
In order to confirm if the error relates to the host, replication was carried out using the below YAML file on Fargate (including the snippet from the ingress provided):
---
apiVersion: v1
kind: Namespace
metadata:
name: frontend
---
apiVersion: apps/v1
kind: Deployment
metadata:
namespace: frontend
name: deployment-frontend
spec:
selector:
matchLabels:
app: my-nginx
replicas: 1
template:
metadata:
labels:
app: my-nginx
spec:
containers:
- image: public.ecr.aws/nginx/nginx:1-alpine-perl
imagePullPolicy: Always
name: frontend-app
ports:
- containerPort: 80
---
apiVersion: v1
kind: Service
metadata:
namespace: frontend
name: frontend-service
spec:
ports:
- port: 80
targetPort: 80
protocol: TCP
type: NodePort
selector:
app: my-nginx
---
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
namespace: frontend
name: frontend-ingress
annotations:
alb.ingress.kubernetes.io/ingress.class: alb
alb.ingress.kubernetes.io/scheme: internet-facing
alb.ingress.kubernetes.io/target-type: ip
spec:
ingressClassName: alb
rules:
- host: "app-dev.marcelo.ai"
http:
paths:
- path: /
pathType: Exact
backend:
service:
name: frontend-service
port:
number: 80
The replication illustrated that there are no errors with the Ingress syntax/config as the ALB was created successfully with no errors as shown in the the AWS Load Balancer Controller logs.
For next steps:
- Please try use the same YAML spec above and see if it succeeds?
- Please kindly confirm the AWS Load Balancer Controller version used?
kubectl describe deployment -n kube-system aws-load-balancer-controller | grep Image
- Please kindly confirm if any mutatingwebhookconfiguration is present that could be adding tags?
kubectl get mutatingwebhookconfiguration
Looking forward to the response.
References:
[1] Listeners for your Application Load Balancers - Host conditions - https://docs.aws.amazon.com/elasticloadbalancing/latest/application/load-balancer-listeners.html#host-conditions
Relevant content
- asked a month ago
- asked 10 months ago
- asked a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 months ago
- How can I troubleshoot issues when I use the AWS Load Balancer Controller to create a load balancer?AWS OFFICIALUpdated a year ago