Skip to content

Products

Featured Pages

Developer Tools

For partners

Latest Updates

  • announcementdata-and-ai

    STACKIT AI Model Serving: New Model Release Qwen3.8 27B (Replacement for Qwen3.6 27B)

    Section titled “STACKIT AI Model Serving: New Model Release Qwen3.8 27B (Replacement for Qwen3.6 27B)”

    We are excited to announce that we are upgrading our model lineup by introducing Qwen/Qwen3.8-27B, which will serve as the successor to our current Qwen offerings.

    As the successor of Qwen3.6 27B the newer Qwen3.8 27B generally improves quality across all fields of application, while maintaining the focus on coding tasks. It was trained on a broad mix of publicly available data and post-trained for code generation, debugging, and technical reasoning, while also supporting general assistant tasks. With a context window of 262K tokens, it can handle large codebases and complex multi-step workflows.

    As part of this transition, we are officially deprecating the following model:

    • Qwen/Qwen3.6-27B

    We kindly ask all customers to migrate their workloads to the new model Qwen/Qwen3.8-27B before December 08, 2026.

    Explore our full model portfolio, and access detailed examples and tutorials in our documentation. Our Help Center is always at your disposal if you have any questions.

  • announcementruntime

    SKE patchday October 2026 – Remove Docker from Flatcar

    Section titled “SKE patchday October 2026 – Remove Docker from Flatcar”

    With the upcoming October patch day, we are adjusting the Flatcar OS images provided in STACKIT Kubernetes Engine (SKE) by removing Docker.

    Docker has been deprecated and removed as the container runtime in SKE for more than two years. By removing it, we ensure the OS footprint remains small and remove unneeded dependencies that could potentially introduce security vulnerabilities.

    Key Dates:

    • October 14, 2026: A new preview Flatcar OS version (the latest stable release available in October) will be added to SKE. This version will not contain Docker.
    • November, 11, 2026: The Flatcar version without Docker will be promoted to the supported OS version. If you have auto updates enabled, your Kubernetes worker nodes will automatically update to this version.

    What you need to do

    Test your SKE workloads beforehand using the new preview Flatcar version once it becomes available on October 14, 2026. Testing is highly recommended to ensure your configurations function exactly as expected before the automatic upgrade takes place in November.

    Our Help Center is always at your disposal if you have any questions.

  • changedruntime

    Improved Kubernetes API server load balancing and strict RFC compliance

    Section titled “Improved Kubernetes API server load balancing and strict RFC compliance”

    We are updating our ingress mechanism to make use of improved Kubernetes API server load balancing in the STACKIT Kubernetes Engine (SKE). We will begin rolling out this update gradually across all clusters starting September 15, 2026. This update significantly benefits the overall stability of SKE and decreases the response times from the API servers under high load.

    To achieve this improved load balancing, the new ingress mechanism strictly enforces RFC compliance. This means that misconfigured clients—specifically those where the Server Name Indication (SNI) does not match the Host or :authority HTTP header—will be rejected with a 421 Misdirected Request error. Previously, these clients might have worked because the former L4 load balancers did not take HTTP headers into consideration.

    As we roll out this change gradually across our production environments, non-compliant clients will receive a 421 Misdirected Request error when attempting to access the API server. To ensure a smooth transition and minimize disruption, we are proactively monitoring our logs for these 421 Misdirected Request errors. If we detect that your cluster is affected during the rollout, our support team will:

    1. Temporarily apply a compatibility fix on our end to restore your traffic flow.

    2. Open a support ticket to notify you, providing your project ID and cluster details.

    3. Inform you of the temporary nature of this fix and provide a strict deadline to update your non-compliant clients before the compatibility mode is permanently removed.

    To learn how to make sure your clients stay compatible, refer to our how-to guide “Ensure RFC-compliant API requests to your SKE cluster”.