Support configuration of Submariner components deployed by the Operator

[Kirubel-Fikru]

I would like to be able to configure Submariner components deployed by the operator through the Helm chart.

This includes:

• Setting resources.requests and resources.limits for CPU and memory.
• Defining the number of replicas (where applicable).
• Using a pre-provisioned LoadBalancer (by specifying its ID), instead of letting the operator create a new one automatically.

Why is this needed:

Currently, these components are managed by the operator, and their configuration is not exposed through the Helm chart. This limits the ability to:

Ensure predictable resource usage in resource-constrained environments.

Comply with internal policies that require explicit resource definitions.

Use custom/provisioned infrastructure components such as pre-created LoadBalancers, which is critical in regulated or cost-optimized environments.

Making these configurations available through the Helm chart would significantly improve flexibility, enable better integration into production workflows, and align with infrastructure-as-code practices.

[dfarrell07]

Setting resources.requests and resources.limits for CPU and memory.

Makes sense

Defining the number of replicas (where applicable).

This isn't something we imagined users configuring, do you have some specific use case in mind?

Using a pre-provisioned LoadBalancer (by specifying its ID), instead of letting the operator create a new one automatically.

There might be another way to do this today that @yboaron can comment on.

[yboaron]

Meanwhile, to workaround using pre-provisioned LoadBalancer, you can create your own LB and annotate [1] its IP address, then deploy submariner in non LoadBalance mode, Submariner should pick the annotated (LB) IP address.

[1]
kubectl annotate node $GW gateway.submariner.io/public-ip=ipv4:1.2.3.4

[dfarrell07]

@Kirubel-Fikru ping, any updates? Is this still relevant?

[Kirubel-Fikru]

@Kirubel-Fikru ping, any updates? Is this still relevant?
Thank you , the work around works perfectly for the custom load balancer usage, but it would be great if it can be configurable when deploying with the helm chart. we wanted to configure the resource limit /requests and the repllicas to manage the resources both horizontally and vertically when needed.

[dfarrell07]

@Kirubel-Fikru Ok, thanks for clarifying. Unfortunately we don't have developers able to focus on Helm much, but contributions are always welcome of course!

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further
activity occurs. Thank you for your contributions.