search

kubernetes-sigs / aws-load-balancer-controller

A Kubernetes controller for Elastic Load Balancers
https://kubernetes-sigs.github.io/aws-load-balancer-controller/
Apache License 2.0
3.93k stars 1.46k forks source link

Multiple ALB controllers #2847

Closed anoopmun closed 1 year ago

anoopmun commented 2 years ago

Having issues when creating ingress.

Have two ALB controllers ss-dev-external and ss-dev-internal in 2 different namespaces. When configuring ingress in the ss-dev-internal namespace, the following errors in noticed in the ALB controller logs.

{"level":"error","ts":1666470035.5002139,"logger":"controller-runtime.manager.controller.ingress","msg":"Reconciler error","name":"aws-alb-ingress-internal-int-dev-to-nginx-ingress","namespace":"ss-dev-internal","error":"Internal error occurred: failed calling webhook \"mtargetgroupbinding.elbv2.k8s.aws\": Post \"https://aws-load-balancer-webhook-service.ss-dev-external.svc:443/mutate-elbv2-k8s-aws-v1beta1-targetgroupbinding?timeout=10s\": x509: certificate is valid for ss-dev-external-webhook-service.ss-dev-external, ss-dev-external-webhook-service.ss-dev-external.svc, ss-dev-external-webhook-service.ss-dev-external.svc.cluster.local, not aws-load-balancer-webhook-service.ss-dev-external.svc"}

The above error seems a bit odd, as the endpoint being used belongs to the initial one (ss-dev-external).. Also the endpoint aws-load-balancer-webhook-service.ss-dev-external.svc seems incorrect as well and it should have been ss-dev-external-webhook-service.ss-dev-external.svc.

Any thoughts on this issue.

kishorj commented 2 years ago

@anoopmun, we currently don't support deploying multiple installations of the aws load balancer controller in the same cluster. While it is possible to configure multiple deoloyments, you'd need to disable the webhooks and SG rule management on subsequent controllers. Please refer to #2185 for further details.

k8s-triage-robot commented 1 year ago

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:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 1 year ago

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:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot commented 1 year ago

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:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

k8s-ci-robot commented 1 year ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes-sigs/aws-load-balancer-controller/issues/2847#issuecomment-1482011830): >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: >- After 90d of inactivity, `lifecycle/stale` is applied >- After 30d of inactivity since `lifecycle/stale` was applied, `lifecycle/rotten` is applied >- After 30d of inactivity since `lifecycle/rotten` was applied, the issue is closed > >You can: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.