We would like to inform you that the API of the STACKIT Kubernetes Engine (SKE) will now include the email address of the user when requesting a Kubeconfig. As before, the Kubeconfig continues to grant admin rights within the corresponding cluster.
Our Help Center is always at your disposal if you have any questions.
Starting from 01 December 2025, STACKIT will introduce an updated billing structure for Windows Server, Red Hat Enterprise Linux (RHEL), and Confidential Kubernetes.
Previously, these services were billed as a combined product (Compute + License). Going forward, compute resources and operating system or service licenses will be billed separately, providing greater transparency and traceability across all workloads.
This change applies to both new and existing instances of the mentioned products. The respective pricing and SKU details are reflected in the updated service certificates.
Further information can be found in the updated Service Certificates for
Our Help Center is always at your disposal if you have any questions.
We now support Kubernetes version 1.33.
You can find documentation on how to manually apply minor or patch version updates in the official STACKIT Kubernetes Engine Documentation. For more information about our release management process, you can find them here.
Important: With Kubernetes 1.33 there will be a new deny-all NetworkPolicy introduced, which blocks Network Traffic in the namespace kube-system. If there is custom workload in the namespace, please apply additional NetworkPolicies for Ingress and Egress.
Additionally, please note that Kubernetes version 1.30 has reached the end of its official support and will be removed from the STACKIT Kubernetes Engine (SKE). On September 17, 2025, all SKE clusters running Kubernetes version 1.30 will be automatically migrated to Kubernetes version 1.31.
Our Help Center is always at your disposal if you have any questions.
From 29.07.2025 we can offer you a new Kubernetes version (1.33) as a preview for your STACKIT Kubernetes Engine (SKE) Cluster.
This new version offers you the possibility to benefit from the latest Kubernetes features and improvements.
We now support Kubernetes in the version 1.31.
This release consists of 45 enhancements: 11 enhancements have graduated to stable, 22 enhancements are moving to beta, and 12 enhancements are entering alpha. For more details refer to the official release announcement or official release notes.
The documentation how to manually apply minor or patch version updates can be found in the official STACKIT Kubernetes documentation. You can find additional information to our release process here.
Please be aware that SKE will align with the official End of Life for Kubernetes versions. Therefore, version 1.31 will be fully supported until the 28th of October 2025.
On the flip side, Kubernetes version 1.28 has reached the end of its official maintenance support. Therefore, this version will be removed from the STACKIT Kubernetes Engine (SKE). We will automatically update all clusters running with Kubernetes version 1.28 to 1.29 on 26th of February 2025.
To ensure the stability of your Kubernetes clusters, SKE reserves resources on all nodes of the cluster to provide memory and CPU for system components. The amount of reserved resources varies depending on the size of the respective nodes.
New Kubernetes clusters created from 21.07.2025 will have changes in their available resources. We will adjust the amount of reserved resources by SKE and utilize the calculation as described below.
For memory resources, SKE reserves the following:
For CPU resources, SKE reserves the following:
Existing Kubernetes clusters will (currently) remain unchanged in their available resources and will be adjusted on 22.07.2025. Thus, a node roll will be triggered on the next given maintenance window of the cluster.
More information can be found in the SKE documentation: Quotas and limits.
If you have any questions, please do not hesitate to contact our Help Center.
Today, we introduced a new option to give you more control over the resource usage of your SKE clusters: you can now disable system components on selected node pools. To use this new feature, you need to set the new field allowSystemComponents to false in the node pool configuration of your cluster. However, at least one node pool per cluster needs to have system components enabled.
Here is an example:
Disable System Components
kubernetes: version: "1.29"nodepools:- name: "pool 1" allowSystemComponents: true # ...more configuration options- name: "pool 2" allowSystemComponents: false # ...more configuration options- name: "pool 3"- allowSystemComponents: false # ...more configuration optionsIn the future, this option will be available in the STACKIT Cloud Portal.
Kubernetes version 1.26 has reached the end of its official maintenance support. Therefore, we will remove this version from the STACKIT Kubernetes Engine (SKE). We will automatically update all clusters running with Kubernetes version 1.26 to 1.27 on 31st of July 2024.
We already support three newer Kubernetes versions (1.27, 1.28 & 1.29). Please update your clusters soon.
In case you have questions you can find more information regarding the v1.27 Kubernetes version here & our SKE updating process here.
Change for accessing your SKE cluster:
Please note that Kubernetes version 1.27 no longer supports static token kubeconfigs. Instead, you can create short-live admin kubeconfigs. This change increases the security of your SKE cluster as you can limit the validity of a specific kubeconfig to a specific time period.
You can already use the new short-lived admin kubeconfigs with Kubernetes version 1.26. However, once you start using the new short-lived admin kubeconfigs, the old method of getting static token kubeconfigs will no longer work. Further information can be found in our STACKIT documentation.
In addition, we offer the option of accessing your SKE cluster via STACKIT CLI. Instructions can be found in our Release notes here.
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 offer known as STACKIT Load Balancer. This brings numerous benefits that include improved scalability, stability and performance.
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 Balancers for every Kubernetes service of type LoadBalancer.
For more information, see our documentation on Load Balancer in SKE.
We are happy to announce a new and more convenient way to access your SKE clusters: SKE Login
To use this new feature, you need to follow these steps:
stackit auth loginstackit config set --project-id IDstackit ske kubeconfig create CLUSTER_NAME --loginThe new kubeconfig type contains no user credentials, and instead retrieves valid short-lived credentials via the STACKIT CLI. You can therefore share this kubeconfig with your colleagues, and they will only be able to access the cluster if they have the permissions to do so.
We are happy to announce that the STACKIT Kubernetes Engine (SKE) is introducing Patchdays for the operating system (OS) of the worker nodes.
The Patchday takes place every second Wednesday of the month. The following actions are carried out on a patchday:
preview.preview OS images are supported.deprecated or even expired.On patchdays, the operating system of the worker nodes of your cluster is updated to a newer version if you have “automatic updates” activated. The update starts within the maintenance window set in the cluster. If this function is deactivated, we plan an update on the following patch day.
For more information, see our documentation on Updates for Kubernetes versions and Operating System versions in SKE and Updating and Maintaining an SKE Cluster.
We are happy to announce new Kubernetes versions for STACKIT Kubernetes Engine (SKE). We now support Kubernetes in the version 1.28.8.
This release consists of 45 enhancements: 12 enhancements have graduated to stable, 14 enhancements are moving to beta, and 19 enhancements are entering alpha. For more details refer to the official release announcement or official release notes.
The documentation how to manually apply minor or patch version updates can be found in the official STACKIT Kubernetes documentation. You can find additional information to our release process here.
This version is running in state “preview” for one week from now on and will be set to “supported” on 12.04.2024.
Please be aware that SKE will align with the official End of Life for Kubernetes versions. Therefore, version 1.28 will be fully supported until the 28th of October 2024.
We are happy to announce new Kubernetes versions for STACKIT Kubernetes Engine (SKE).
We now support Kubernetes in the version 1.27.11. Additionally, the Kubernetes patch versions 1.26.14 and 1.25.16 were introduced.
Please be aware that your static-token kubeconfig will be invalid as soon as you update to Kubernetes version 1.27. You need to create a new short-lived kubeconfig via STACKIT Cloud Portal or SKE-API. For additional information you can read our SKE documentation.
This release consists of 60 enhancements: 13 enhancements have graduated to stable, 29 enhancements are moving to beta, and 18 enhancements are entering alpha. Also, 14 features have been deprecated or removed. For more details refer to the official release announcement or official release notes.
The documentation how to manually apply minor or patch version updates can be found in the official STACKIT Kubernetes documentation. You can find additional information to our release process here.
This version is running in state “preview” for one week from now on and will be set to “supported” on 12.03.2024.
Please be aware that SKE will align with the official End of Life for Kubernetes versions. Therefore, version 1.27 will be fully supported until the 28th of June 2024.
Kubernetes version 1.25 has reached the end of its official maintenance support. Therefore, we will remove this version from the STACKIT Kubernetes Engine (SKE). We will automatically update all clusters running with Kubernetes version 1.25 to 1.26 on 29th of April 2024.
We already support two newer Kubernetes versions (1.26 and 1.27). Please update your clusters as soon as possible.
In case you have questions you can find more information regarding the v1.25 Kubernetes version here & our SKE updating process here.
A runc vulnerability (called “Leaky Vessels”) was recently identified by Snyk Security Labs. For Kubernetes this means an attacker could use this vulnerability to escape the container and gain unauthorized access to the underlying host operating system. For additional information, you can see the following resources:
This means for you:
If you have “Automatic OS Updates” enabled: You don’t need to do anything. We have released a new OS (Version 3760.2.0) which mitigates this vulnerability. A rolling update of the worker nodes of your cluster will be performed in your configured maintenance window. Detailed instructions how to configure “Automatic OS updates” can be found in the STACKIT Kubernetes Engine documentation.
If you have “Automatic OS Updates” disabled: You need to manually update the OS version of your worker nodes as soon as possible. We have also informed the project owners of affected clusters via email. Otherwise, remaining SKE clusters will be automatically updated on Wednesday, 28.02.2024, in their configured maintenance window. Additionally, we highly advise to use our “Automatic OS updates” feature in the future.
If there are any questions, support is available via the Help Center.