Allow for MetalLB in k3s in SCALE
Description
is cloned by
SmartDraw Connector
Katalon Manual Tests (BETA)
Activity
Kjeld Schouten-lebbing December 10, 2021 at 11:18 PM
@Stavros Kois It's already closed
"Suggestion Accepted" is the positive "closed" for suggestions, after which a feature is made (see https://ixsystems.atlassian.net/browse/NAS-111019#icft=NAS-111019), which is also closed due to those PR's
Stavros Kois December 10, 2021 at 10:37 PM
@Triage Team This can be closed as its done in https://github.com/truenas/webui/pull/6104 and https://github.com/truenas/middleware/pull/7834
Kjeld Schouten-lebbing April 29, 2021 at 9:18 AM
@Triage Team Thats 12 Votes (10 excluding iX employees). So above the required 10 votes for a consideration
Kjeld Schouten-lebbing April 28, 2021 at 6:57 PM
The added flexibility of Metal-LB is basically a must-have once people start moving away from single-node deployments. BGP is also a must have for any serieus professional deployment.
Simply put:
A alpha grade Loadbalancer like the current klipperLB is not really acceptable and should at least be removable, or (preferably) replaceable.
Details
Details
Priority
LowAssignee
Reporter
More fields
Time tracking
More fields
Time trackingKatalon Platform
Linked Test Cases, Katalon Defect Results, Katalon Studio Test Results
Katalon Platform
The announcement of using kubernetes in SCALE has many of us excited for things to come. However, it seems that as of now the plan is to lock down k3s usage to just replace jails with it as a kinda-closed ecosystem of predetermined use.
While I understand the usecase here, I'd request more freedom of usage of the system. As it is now, it is limited to using just the IP of the NAS, limiting usage of ports that contend with already running services. This is because k3s is running with servicelb by default, and cannot be turned off without modifying the systemd service. By allowing to turn it off, and integrating metallb, the user could specify any IP from the local network, allowing for more broad usecases. This is of course with the gotcha, that the IP of the host server is no longer available for services (I'm taling about service type LoadBalancer). As far as I know it is impossible to run both servicelb and metallb at the same time.
The forum thread where discussion has started https://www.truenas.com/community/threads/questions-about-kubernetes-and-updates.89935/