Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reference service for target group binding in a different namespace #3932

Open
lumoVWGS opened this issue Nov 4, 2024 · 1 comment
Open
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@lumoVWGS
Copy link

lumoVWGS commented Nov 4, 2024

Is your feature request related to a problem?
As the loadbalancer controller's settings only allow the watch exact one OR all namespaces there can be the following situation:

We normally want to restrict the one watched namespace to our infrastructure namespaces, to avoid developers to be able to deploy ressources in their namespaces that create AWS ressources. But we still would like to have the possibility to create TargetGroupBindings for services that are outside of our infrastructure namespace - without the targetgroupbinding k8s ressource being outside of our infra namespace.
However, this is currently not possible as the kube api needs a namespace when getting requested for services - however a namespace is not configurable in the serviceRef so far:
https://kubernetes-sigs.github.io/aws-load-balancer-controller/latest/guide/targetgroupbinding/spec/#elbv2.k8s.aws/v1beta1.ServiceReference

Describe the solution you'd like
A namespace can be added to the serviceRef and the controller can handle TargetGroupBindings that reference services in another namespace.

Describe alternatives you've considered
Alternatively it would work if the loadbalancer controller can be configured to watch more than one namespace (but not all).

@M00nF1sh
Copy link
Collaborator

M00nF1sh commented Nov 5, 2024

@lumoVWGS
We can change the controller to support watch multiple namespaces(shall be simple with the recent controller-runtime changes).
But i'm not sure how this can address your request of binding to a different namespace.

@shraddhabang shraddhabang added the kind/feature Categorizes issue or PR as related to a new feature. label Nov 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

3 participants