Zum Inhalt springen

Application Load Balancer

STACKIT Load Balancer distributes network traffic amongst service instances to prevent overload and outages.

  • changed

    STACKIT Load Balancer available in SKE

    We are happy to announce that newly created SKE clusters will use the STACKIT Load Balancer.

    Previously, users could create and manage load balancers within SKE using a solution known as yawol. However, to better align with industry standards and best practices, we launch our dedicated STACKIT Load Balancer service.

    As of June 3, 2024, the transition to this dedicated service will begin. New SKE clusters created after this date will automatically provision STACKIT Load Balancer for every Kubernetes service of type LoadBalancer.

    For more information, see our documentation on Load Balancer in SKE.

  • announcement

    Essential Network Load Balancer is available as GA

    We are happy to announce the release of our brand new service Essential Network Load Balancer.

    This service is designed to provide high availability for your application by distributing incoming traffic across multiple servers.

    The API of the Essential Network Load Balancer enables easy integration into applications and workflows. It also provides extensive integration into various tools such as Terraform.

    With our getting started guide at our customer documentation you get everything to start right now.

  • feature

    Existing Public IP Address can now be used for load balancers in SKE

    You can now use existing Public IP Addresses for load balancers in STACKIT Kubernetes Engine (SKE). This feature allows you to use a static Public IP Address that persists even if the service is deleted and recreated. This is beneficial if you want to rely on a service to have a static Public IP Address, for example if you can’t use dynamic DNS.

    For more information, see our documentation on using existing Public IP Address for load balancers.