# Load Balancer Managed FKE products are developed from Kubernetes Native and integrated with Kubernetes as cloud provider components, including the FPT Cloud Controller Manager component. This component manages worker nodes and load balancer-type services within the cluster. Users have several methods available to expose their applications to the internet and enable their customers to access the applications or services. These methods include creating an ingress to the service, creating a NodePort-type service and assigning a floating IP to a VM worker node, or using a load balancer-type service. FPTCloud supports creating load balancer-type services and automatically assigning a public IP address to that load balancer. When using a load balancer-type service, in addition to creating the default load balancer for worker nodes, you can add optional configurations to the load balancer using annotations within the service manifest file.
Key Value Default Meaning
service.beta.kubernetes.io/fpt-load-balancer-internal true/false false Whether the service is exposed to the internet. If not exposed, no floating IP connecting to the load balancer will be created.
loadbalancer.fptcloud.com/enable-ingress-hostname true/false false Used in combination with the proxy protocol to enable connection to the ingress domain from within a Pod.
Users can create load balancer-style services by adding annotations to the service configuration based on their use case. **Example:**
This diagram illustrates creating a load balancer-type service with the type set to advanced. Applying the manifest file to the service results in a load balancer-type service being obtained on the k8s cluster.
The application becomes accessible from outside the internet via the ip public or a domain using that ip public once the external-ip component changes from pending to ip public.
Users can also create an internal-type load balancer service that cannot be accessed from outside the cluster, enabling calls only between internal services.
When an internal service is created, its \`external-ip\` will be a private IP address, not a public IP address.
Furthermore, M-FKE supports users as follows: * Specify the \`loadBalancerIP\` setting in the \`spec\` section of the service configuration to create a service with a public IP address.
Note that the public IP must be assigned to a VPC and be **in an inactive state.** Users can verify this under **\[Networking] -> \[Floating Ips].** * Use the \`loadBalancerSourceRanges\` setting in the \`spec\` section of the service configuration to restrict access to the load balancer.
Note that the \`loadBalancerSourceRanges\` setting contains the range of public IP addresses permitted to access the load balancer ( ). By default, M-FKE creates a load balancer service type with an IP source range setting of 0.0.0.0/0. * Additionally, if you wish to use the PROXY PROTOCOL in the Load Balancer Pool, please request support from FPTCloud. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://ai-docs.fptcloud.com/fpt-gpu-cloud/gpu-cluster/managed-k8s-with-gpu-virtual-machine/tutorial/load-balancer.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.