Add documentation for servies of type loadbalancer#18
Draft
DebakelOrakel wants to merge 1 commit intomainfrom
Draft
Add documentation for servies of type loadbalancer#18DebakelOrakel wants to merge 1 commit intomainfrom
DebakelOrakel wants to merge 1 commit intomainfrom
Conversation
DebakelOrakel
added
enhancement
DebakelOrakel
force-pushed
the
doc/loadbalancer
branch
from
c5d220e to
f626854
Compare
simu
reviewed
Apr 8, 2026
Member
There was a problem hiding this comment.
Generally, I feel like the current revision of this page creates the wrong impression that exposing applications via service type LoadBalancer just works on all clusters.
I've added some inline comments for some obvious caveats, but I think this will need quite a bit more detail before it's actually suitable to publish.
Comment on lines
+47
to
+48
| L2 Announcements is a feature which makes services visible and reachable on the machine network of the cluster. | ||
| This feature is primarily intended for on-premises deployments within networks without BGP based routing. |
| @@ -0,0 +1,165 @@ | |||
| = Service Type LoadBalancer | |||
|
|
|||
| Depending on the infrastructure there are different implementations of services of type LoadBalancer. | |||
Member
There was a problem hiding this comment.
Suggested change
| Depending on the infrastructure there are different implementations of services of type LoadBalancer. | |
| Depending on the infrastructure there are different implementations of services of type LoadBalancer. | |
| [IMPORTANT] | |
| ==== | |
| For some infrastructures, no `LoadBalancer` service types are available out of the box. | |
| Please contact us if you need `LoadBalancer` services on such infrastructures. | |
| ==== |
| protocol: TCP | ||
| ---- | ||
| <1> Define the selector associated with your deployment. | ||
| <2> Allow access from `world`. |
Member
There was a problem hiding this comment.
Suggested change
| <2> Allow access from `world`. | |
| <2> Allow access from anywhere (CIDR `0.0.0.0/0`). | |
| Note that, depending on the `LoadBalancer` implementation, it may or may not be possible to restrict access to specific IPs via network policy. |
| kind: Service | ||
| metadata: | ||
| name: your-service-lb | ||
| namespace: your-namespace |
Member
There was a problem hiding this comment.
This example should have a few of the useful annotations such as access control and a link to https://github.com/cloudscale-ch/cloudscale-cloud-controller-manager?tab=readme-ov-file#loadbalancer-service-configuration
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Checklist
change,decision,requirement/quality,requirement/functional,dependencyas they show up in the changelog