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

Support of ui.service.loadBalancerIP missing #5

Open
ttww opened this issue Nov 13, 2022 · 1 comment
Open

Support of ui.service.loadBalancerIP missing #5

ttww opened this issue Nov 13, 2022 · 1 comment

Comments

@ttww
Copy link

ttww commented Nov 13, 2022

If you want to use the plain MetalLB and specify the ui.service.type=LoadBalancer type,
you should also be able to specify an ui.service.type=LoadBalancerIP

Without this, the load balancer is using the first specified IP from the load balancer configuration (eg. 192.168.0.200 if the MetalLB range is 192.168.0.200-192.168.0.220

The generated Service entry should look s like

.........cut......cut......cut..........
spec:
  type: LoadBalancer
  loadBalancerIP: 192.168.0.207
  ports:
  - port: 80
.........cut......cut......cut..........

See your example in the docker-registry service.yaml template file.

I try to add it and do a pr....

@Joxit
Copy link
Owner

Joxit commented Nov 14, 2022

Hi, thank you for using my project and submitting issues 😄

Can you use the property ui.service.additionalSpec to achieve your goal ? (use the 0.4.2, I added a fix)

ui:
  service:
    type: LoadBalancer
    additionalSpec: |
      loadBalancerIP: 192.168.0.207

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants