Closed micmel5997 closed 1 year ago
@micmel5997, since the target-type is IP, could you verify whether the backend service app-name has ready endpoints? You can check for the Endpoint/Endpointslice resource corresponding to the app-name service. Do you see any errors in the controller logs?
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.
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".
So I have been working with the ALB controller in order to control ALB spend on our AWS EKS cluster. While I have a working application and listener for the default listener rule, I am unable to add a secondary listener successfully. Below is what I am using in my values file for an ingress in a new helm project. The Listener rule gets created, and a target group gets created, but there are no targets that get registered. What am I missing?
ingress: metadata: name: group-name annotationEnabled: enabled annotations: alb.ingress.kubernetes.io/target-type: ip alb.ingress.kubernetes.io/certificate-arn: ########### alb.ingress.kubernetes.io/ssl-policy: ########### alb.ingress.kubernetes.io/listen-ports: '[{"HTTPS":443}]' alb.ingress.kubernetes.io/healthcheck-port: '8080' alb.ingress.kubernetes.io/group.name: group-name spec: ingressClassName: alb rules: