我正在尝试在EKS上设置AWS ALB入口。但Argo用户界面不起作用。但端口转发运行正常。
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
annotations:
alb.ingress.kubernetes.io/healthcheck-path: /
alb.ingress.kubernetes.io/listen-ports: '[{"HTTP": 80}]'
alb.ingress.kubernetes.io/scheme: internal
kubernetes.io/ingress.class: alb
name: admin-ns-endpoints
namespace: admin
spec:
rules:
- host: argo-nonprod.sample.com
http:
paths:
- backend:
serviceName: argo-server
servicePort: 2746
path: /*
status:
loadBalancer:
ingress:
- hostname: xxxxxxx.ap-south-1.elb.amazonaws.com
访问终结点时获取404。
apiVersion: apps/v1
kind: Deployment
metadata:
name: argo-server
namespace: admin
spec:
replicas: 1
template:
spec:
containers:
- args:
- server
- --configmap=argo-workflow-controller-configmap
env:
- name: BASE_HREF
value: /
- name: IN_CLUSTER
value: "true"
- name: ARGO_NAMESPACE
valueFrom:
fieldRef:
apiVersion: v1
fieldPath: metadata.namespace
image: argoproj/argocli:v2.9.3
imagePullPolicy: Always
name: argo-server
ports:
- containerPort: 2746
name: web
protocol: TCP
我使用Helm Chart部署了图表。
我尝试更改入口文件中的不同值,但未成功。
您是否可以尝试删除spec.rules.Http.host?另外,这对我们也适用:
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
name: nginx-alb-ingress
namespace: argo
annotations:
kubernetes.io/ingress.class: aws-alb
alb.ingress.kubernetes.io/load-balancer-attributes: access_logs.s3.enabled=false
alb.ingress.kubernetes.io/backend-protocol: HTTPS
alb.ingress.kubernetes.io/scheme: internet-facing
alb.ingress.kubernetes.io/listen-ports: '[{"HTTPS": 443}]'
alb.ingress.kubernetes.io/subnets: REDACTED
alb.ingress.kubernetes.io/security-groups: REDACTED
alb.ingress.kubernetes.io/healthcheck-protocol: HTTPS
alb.ingress.kubernetes.io/healthcheck-path: /
external-dns.alpha.kubernetes.io/hostname: REDACTED
labels:
app: nginx-service
spec:
rules:
- http:
paths:
- path: /*
backend:
serviceName: argo-server
servicePort: 2746