– SKS

New Works with Exoscale Partner: Airlock Microgateway

Thu, 17 Sep 2026 08:00:00 +0000

Airlock Microgateway by Ergon Informatik AG is now certified as Works with Exoscale, bringing Kubernetes-native application and API protection to workloads running on Exoscale SKS.

Built on open standards, Airlock Microgateway runs directly inside the Kubernetes cluster and combines the Kubernetes Gateway API with Web Application and API Protection (WAAP), identity-aware access control, reporting and monitoring. Routing rules and security policies are managed as code, allowing teams to integrate security directly into existing GitOps and DevSecOps workflows.

Security that fits into Kubernetes

Airlock Microgateway gives platform and application teams a consistent way to manage routing and security without adding a separate security layer outside the cluster:

Kubernetes-native protection: Protect web applications and APIs directly at the cluster entry point.
Security as code: Define routing and security policies declaratively and manage them through existing GitOps workflows.
Identity-aware access: Control access using standards including OIDC, JWT, OAuth 2.0 Token Exchange and mTLS.
Application and API protection: Protect workloads against common web attacks and enforce API specifications with OpenAPI and GraphQL schema validation.
Built on open standards: Use a conformant implementation of the Kubernetes Gateway API together with established technologies including Istio and Cilium.
A path beyond Ingress NGINX: Migrate existing Ingress NGINX resources to Gateway API using the Kubernetes ingress2gateway tool, including its Airlock Microgateway emitter.

Airlock Microgateway can be deployed directly on Exoscale SKS. Its Community Edition provides Kubernetes Gateway API capabilities and reverse proxy capabilities without a license or throughput limit, while advanced security capabilities are available with the Premium Edition.

Protect your Kubernetes workloads →

SKS: Kubernetes 1.37 Now Available

Mon, 31 Aug 2026 11:45:00 +0000

Kubernetes 1.37 is now available on Exoscale Scalable Kubernetes Service (SKS) for new and existing clusters.

Named Garhwal, Kubernetes 1.37 includes 67 enhancements, with 16 features graduating to Stable. The release strengthens established Kubernetes APIs and improves the foundations for secure workloads and reliable cluster upgrades.

Key benefits

A stable resource Metrics API: The metrics.k8s.io/v1 API now carries Kubernetes’ Stable API guarantees. This gives tooling that uses pod and node CPU and memory metrics a more durable integration target. Existing v1beta1 clients remain supported during the transition, and using the new API requires a compatible metrics provider.
Stronger foundations for workload identity: Pod Certificates and Cluster Trust Bundles are now Stable, providing standard Kubernetes building blocks for issuing X.509 certificates and distributing trust material to workloads. This can simplify TLS and mutual TLS integrations when used with a compatible certificate signer.
Safer mixed-version operation: Node Declared Features are now Stable. Control-plane components can identify the features available on each node, improving behavior when clusters temporarily contain different node versions during upgrades.
Continued security and reliability improvements: Upgrading keeps clusters on an actively supported Kubernetes release and provides the latest upstream fixes and improvements included in Kubernetes 1.37.

Upgrade notes

Existing SKS clusters are not upgraded automatically.
Review the Kubernetes 1.37 release announcement and test the upgrade in a non-production environment before upgrading production clusters.
Upgrade the control plane and node pools using the Exoscale Portal, CLI, or API. Kubernetes minor versions must be upgraded sequentially.

Learn how to upgrade and manage the Kubernetes version of an SKS cluster

SKS: Container registry mirroring for Karpenter nodes

Wed, 19 Aug 2026 08:00:00 +0000

Exoscale SKS now supports configuring OCI registry mirrors for nodes provisioned by Karpenter. Registry mirror endpoints and pull credentials can be defined in an ExoscaleNodeClass and applied consistently to new nodes created from that class.

What this enables

Faster and more reliable image pulls: Route image requests through private mirrors located closer to your workloads.
Lower egress costs: Reduce repeated downloads from public registries by caching commonly used container images.
Fewer upstream limits: Avoid relying solely on public registries and reduce the impact of their rate limits or availability issues.
Greater supply-chain control: Use private registries, authenticated mirrors, and trusted TLS configurations for container images.

Why it matters

Registry mirroring gives teams more control over how container images reach their SKS clusters. It improves reliability and supports production environments that require private access, predictable image delivery, or tighter control over external dependencies.

Learn how to configure OCI registry mirroring for Karpenter nodes.

SKS: CPU Manager policies for Karpenter-provisioned nodes

Mon, 17 Aug 2026 08:00:00 +0000

Exoscale SKS now supports configuring Kubernetes CPU Manager policies for nodes provisioned by Karpenter. You can define the kubelet CPU Manager configuration in an ExoscaleNodeClass and apply it consistently to every node created from that class.

What this enables

More predictable performance: Assign exclusive CPUs to eligible workloads that are sensitive to latency or CPU contention.
Consistent node configuration: Apply the selected CPU policy automatically to new nodes provisioned by Karpenter.
Flexible workload isolation: Reserve CPU capacity for Kubernetes and system components while keeping application resources separate.

Why it matters

CPU Manager policies give teams greater control over how processor resources are allocated across their SKS workloads. This is especially useful for high-performance, real-time, and other compute-intensive applications that benefit from stable CPU placement.

Learn how to configure CPU Manager policies with Karpenter.

SKS: GPU MIG partitioning support

Tue, 21 Jul 2026 00:00:00 +0000

Exoscale SKS now supports GPU MIG partitioning for MIG-capable GPU nodepools.

With Multi-Instance GPU (MIG), customers can split a supported physical GPU into multiple isolated GPU instances, each with dedicated compute and memory resources. This makes it easier to run several smaller GPU workloads on the same SKS node instead of assigning a full GPU to each workload.

Availability and setup

MIG partitioning is available for Exoscale A30, RTX Pro 6000 and B300 GPUs.
Standard SKS nodepools can be configured with MIG profiles through the Exoscale Portal, CLI, or Terraform provider.
Karpenter-managed GPU nodepools can use MIG through the ExoscaleNodeClass configuration.

Why use MIG?

Run multiple smaller GPU workloads on one physical GPU.
Improve GPU utilization and reduce underused capacity.
Keep workloads isolated at the GPU partition level.
Better accommodate AI inference, development and testing, and smaller batch workloads.

Note: Existing nodes must be cycled before a changed MIG profile takes effect. Billing is based on the selected GPU node instance type, not on individual MIG partitions.

For setup instructions, see:

Configure GPU MIG partitioning on SKS

SKS Node Templates update for Copy Fail and Dirty Frag

Fri, 08 May 2026 14:11:00 +0000

We re-released the SKS Node Operating System images to include mitigations for the recently disclosed Copy Fail and Dirty Frag security vulnerabilities.

The updated images include mitigations for:

Copy Fail (CVE-2026-31431)
Dirty Frag (CVE-2026-43284, CVE-2026-43500)

To ensure your SKS clusters are no longer impacted, worker nodes managed by both SKS NodePools and SKS Karpenter must:

Run Kubernetes 1.33.11, 1.34.7, 1.35.4 or 1.36.0
Have been deployed after May 8, 2026 at 15:55 CEST

Clusters meeting these requirements no longer need the temporary workarounds communicated in the previous security advisory sent on May 1st, 2026.

Existing clusters running older nodes should be upgraded and nodes should be cycled to apply the updated images.

Upgrade your SKS clusters and cycle worker nodes to ensure the updated mitigations are applied.

Check SKS Lifecycle Management Documentation

SKS: Karpenter autoscaling integration is now Generally Available

Thu, 19 Mar 2026 10:00:00 +0000

We’re happy to announce that the Karpenter autoscaling integration for Exoscale Scalable Kubernetes Service (SKS) is now Generally Available.

With this release, Exoscale becomes the first European cloud provider to offer a fully integrated Karpenter experience for managed Kubernetes, enabling modern, workload-aware autoscaling for production environments.

Check it out: https://github.com/kubernetes-sigs/karpenter?tab=readme-ov-file#karpenter-implementations

Why move beyond traditional autoscaling?

Karpenter doesn’t just scale, it optimizes, provisioning the exact compute resources needed in real time.

Simplified autoscaling: No manual node pool configuration.
Continuous auto-healing: Automatic replacement of unhealthy nodes.
Cost efficiency: Reduced overprovisioning and lower cloud costs.

This provides a powerful, sovereign foundation for elastic workloads like AI pipelines, CI/CD, and high-traffic applications, all while keeping your data strictly within European infrastructure.

Ready to streamline your Kubernetes operations?

Check out our documentation to get started with Karpenter on SKS today

SKS: Veeam Ready Kubernetes

Thu, 26 Feb 2026 16:18:00 +0000

Exoscale Scalable Kubernetes Service (SKS) is now listed as Veeam Ready Kubernetes for Veeam Kasten for Kubernetes.

This validation confirms that SKS has been qualified to support Veeam Kasten Kubernetes-native backup and restore capabilities, including coverage for the platform (distribution) and CSI integration coverage, verified by Veeam.

What this enables

Run Veeam Kasten for Kubernetes on SKS in order to back up and restore your applications
Use Veeam Kasten workflows for disaster recovery and migration of Kubernetes applications on and off SKS
Rely on a Veeam-qualified Kubernetes platform for Kasten operations (per Veeam Ready Kubernetes)

Getting started

To protect workloads running on SKS with Veeam Kasten:

Create an SKS cluster (matching your target Kubernetes version)
Install Veeam Kasten for Kubernetes on the cluster using the Kubernetes native installation method
Configure storage integration and backup locations as per Veeam Kasten documentation

Follow Veeam Kasten installation documentation to get started

SKS: New GPU node template - NVIDIA RTX Pro 6000 support

Tue, 10 Feb 2026 15:12:32 +0000

A new GPU node template for SKS is now available, supporting NVIDIA RTX Pro 6000 and Kubernetes versions 1.33, 1.34, and 1.35, enabling customers to run AI and inference workloads on managed Kubernetes.

The template uses the open-source NVIDIA driver, which is aligned with current NVIDIA support and is better suited for the long-term operation of GPU-enabled Kubernetes clusters.

Existing GPU node pools are not updated automatically and must be recreated to use the new template.

Note: Due to limitations of the open-source NVIDIA driver, GPU2 (Tesla V100) is no longer supported with this template.

For more details and prerequisites, check the documentation

SKS: Kubernetes 1.35 Now Available

Mon, 29 Dec 2025 12:00:15 +0000

We’re happy to announce that Kubernetes 1.35 is now available on Exoscale SKS.

Just a few days after the upstream release, the Timbernetes (The World Tree Release) was rolled out on Exoscale on December 22, 2025.

Kubernetes 1.35 brings improvements to resource management and node requirements and continues the cleanup of legacy components, helping keep Kubernetes clusters efficient and future-ready.

Key benefits

Improved workload availability: With Kubernetes 1.35, workloads can be vertically scaled without restarts, improving availability and resource efficiency.
Simpler model distribution for AI workloads: OCI images can now be mounted as read-only volumes, making it easier to ship and run models without additional storage layers.

Upgrade notes

Existing SKS clusters are not upgraded automatically.
We recommend testing upgrades in a non-production environment before upgrading production clusters.
You can upgrade your clusters using the Exoscale Portal, CLI, or API.

SKS upgrade and lifecycle management

SKS: Karpenter Autoscaling Integration (Public Preview)

Tue, 11 Nov 2025 13:03:02 +0000

We’re bringing next-generation Kubernetes autoscaling to Exoscale, now in Public Preview.

Our new Karpenter integration brings advanced, real-time autoscaling to Exoscale Kubernetes clusters. It automatically provisions and removes compute or GPU nodes as demand changes, improving efficiency and reducing idle costs.

Source: Karpenter

The integration extends Exoscale’s existing autoscaling to full node lifecycle management, delivering hyperscaler-level scalability within a sovereign European cloud.

Karpenter automatically selects the optimal instance type for each workload, supports GPU-based AI and ML use cases, and scales clusters down to zero when idle, so users pay only for the resources they use.

Based on the open source Karpenter project, this add-on is included in SKS PRO Cluster at no additional cost.

Note: Karpenter is currently in Public Preview. Some features may change before General Availability, and you may encounter bugs. If you experience any issues, please open a support ticket in the Exoscale Portal.

For more details, check out our blog: https://www.exoscale.com/blog/sks-karpenter/

Learn how to enable Karpenter

SKS: Kubernetes Audit Webhook Support

Tue, 09 Sep 2025 13:01:50 +0000

We’ve introduced Kubernetes Audit Webhook support for SKS clusters. With this feature, you can now enable and configure Kubernetes Auditing on your cluster and forward audit events directly from the kube-apiserver to your own backend web server.

What’s changed?

You can enable/disable Kubernetes auditing at the cluster level.
Configuration is available via the Exoscale Portal. CLI and Terraform implementations are coming soon.
Auditing parameters can be defined, including:
- Endpoint URL
- Authentication via bearer token (with rotation support)
- Initial backoff

Key advantages

This functionality gives you complete visibility into Kubernetes API activity in your cluster, enabling integration with security and monitoring tools such as Falco or SIEM platforms. You gain:

Centralized auditing of API calls
Easier compliance reporting
Flexible configuration to match your security workflows

Check our documentation for details

SKS: Kubernetes 1.34 Now Available

Thu, 04 Sep 2025 07:08:38 +0000

We've made Kubernetes 1.34.0 available in our Scalable Kubernetes Service (SKS) for all customers just 24 hours after the upstream open-source release, enabling them to stay up to date as soon as possible. This update reinforces our commitment to providing a secure, up-to-date, and reliable managed Kubernetes platform.

What’s new

Kubernetes 1.34.0 is now available for both new and existing SKS clusters.
Enhanced GPU Node Support: nvidia-device-plugin should not be manually installed anymore when using these Kubernetes node versions: 1.31.12, 1.32.8, 1.33.4, 1.34.0

Key Benefits

Faster Innovation: Immediate access to the latest Kubernetes features and security fixes.
Simplified GPU Setup: Streamlined configuration with automated plugin deployment.
Reduced Operations: Lower operational overhead and minimized risk of misconfiguration.

For detailed information about GPU support in SKS, refer to our documentation

SKS: Option to Automatically Create Security Group Rules on Cluster Creation

Tue, 15 Jul 2025 12:53:27 +0000

We’ve added a new option to automatically create the required security group rules when provisioning a Kubernetes cluster. When enabled, Exoscale will automatically create a Security Group with the necessary network rules based on the selected CNI (Container Network Interface). It will be automatically attached to any node pool created in this cluster. This ensures your cluster has the correct communication paths between nodes and services, without requiring manual configuration.

Availability

Enabled by default in the portal
Available in the Exoscale Web Portal
Soon to be available in the Exoscale CLI (as a flag)
Not available in the Terraform provider, to preserve consistency with existing resource semantics

This addition enhances the onboarding experience by reducing the need for manual network configuration, while still allowing users who prefer to manage their own rules to maintain complete control over their settings.

Check our SKS documentation

Decoupled CCM & CSI Add-ons

Fri, 13 Jun 2025 12:30:00 +0000

We’ve introduced a credential separation improvement for Kubernetes clusters using Exoscale SKS. The Cloud Controller Manager (CCM) and Container Storage Interface (CSI) add-ons now use independent IAM API keys and roles, improving security and lifecycle management, as well as allowing CSI to be deployed independently.

What's new?

When creating or updating an SKS cluster with add-ons enabled, separate IAM roles and API keys are now automatically created per add-on and per cluster.
These credentials follow a clear naming pattern: sks-<addon>-<cluster-id>
Credential lifecycles are fully managed by Exoscale: they’re created with the cluster and automatically removed when the cluster is deleted.

Why does this matter?

Improved Security: Credentials are isolated per add-on, minimizing permission exposure.
Granular Access Control: Fine-tune or audit CCM and CSI access independently.
Easier Auditing: Identify and monitor actions from each add-on individually.
Simplified Operations: In case of accidental deletion or suspected compromise, credentials can be rotated easily.

This change applies automatically to newly created or updated clusters. Existing clusters continue to work as-is and can adopt the new model by updating the cluster configuration or rotating the respective credentials.

Learn more in our docs

SKS Enhancements – Now Supporting Kubernetes 1.30 to 1.33 with Improved Security Defaults

Thu, 22 May 2025 12:29:43 +0000

We're excited to announce that Exoscale Scalable Kubernetes Service (SKS) now supports the following Kubernetes versions:

1.30.13
1.31.9
1.32.5
1.33.1

What's New

🔐 User Namespaces Enabled by Default in 1.33.1

Kubernetes 1.33.1 introduces user namespaces as a default feature in SKS. This critical security enhancement provides an extra isolation layer between containers and the host system, helping you run workloads more securely in multi-tenant and zero-trust environments.

User namespaces have been stable since Kubernetes 1.30.0, but with 1.33.1, we're enabling them out of the box.

Action required: To benefit from this security improvement, please upgrade your cluster nodes to version 1.33.1.

Learn more: Kubernetes Documentation on User Namespaces

🛡️ AppArmor Enforcement Introduced

We've also introduced explicit AppArmor compatibility checks starting with this release.

While AppArmor has been usable in most past SKS versions, a recent regression highlighted the need for stricter validation. We now enforce prerequisites to ensure AppArmor is consistently available across all future Kubernetes versions on SKS.

Learn more about our Kubernetes offering

Rancher Integration for SKS Management

Fri, 09 May 2025 13:26:14 +0000

Our SKS product is now natively integrated with Rancher, the leading multicloud Kubernetes management platform. Thanks to our new cluster driver, Rancher users can now easily manage Kubernetes clusters across multiple environments, including Exoscale.

Manage Exoscale SKS clusters through Rancher’s centralized interface
Native integration with Exoscale — no additional Exoscale charges
Simplified cluster lifecycle management: provisioning, scaling, updating
Unified UI with RBAC-based access control for streamlined Kubernetes operations

SKS Now Ships Kubernetes 1.32

Tue, 18 Feb 2025 08:59:02 +0000

We’re happy to announce that Kubernetes 1.32 is now available in SKS! This latest release brings a set of improvements designed to make your clusters more efficient than ever.

What’s New in SKS?

In addition to shipping Kubernetes 1.32 as supported version, we revamped our Node Operating System templates with the following characteristic:

About 40% faster boot times
No SSH Server anymore and reduced amount of installed software
Better Resource Management of system workloads like containerd and kubelet.
Containerd 2.0: The latest version of the container runtime, replacing containerd 1.

How to benefit from those improvements?

We encourage you to stay as much up-to-date as possible to improve your security posture, so you can upgrade to the latest release of Kubernetes 1.32.2.

However, we have also backported those changes in older, still supported, versions like: 1.29.14, 1.30.10 and 1.31.6.

You can find more information about how to upgrade here.

Support of Kubernetes 1.25.0

Fri, 14 Oct 2022 11:11:16 +0000

The latest Kubernetes release 1.25.0 (Combiner) is now available on SKS and has already passed the CNCF conformance test successfully.

Kubernetes 1.25 brings some new features to Exoscale SKS like the introduction of PodSecurity admission, replacing PodSecurityPolicies. The release of Kubernetes 1.25 includes 40 enhancements in total.

With the latest release we also stopped supporting version branch 1.23. The minor version 1.24 is supported from now on. Upgrade easily with SKS.

SKS lifecycle management documentation

Cilium CNI & SKS

Fri, 03 Jun 2022 08:50:26 +0000

The Cilium CNI is now even easier to use with SKS. While SKS has had previous support for other CNIs than our default Calico setup, we now enabled a simple switch to specify Cilium instead. While initiating your cluster you can specify Cilium as CNI plugin using the --cni flag:

exo compute sks create my-test-cluster \
 --zone de-fra-1 \
 --cni cilium \
 --service-level pro \
 --nodepool-name my-test-nodepool \
 --nodepool-size 3 \
 --nodepool-security-group sks-security-group

Cilium is an open source software providing and securing network connectivity between application workloads like containers or processes. The software is integrated into orchestration frameworks like Kubernetes.

A Linux eBPF Kernel is at the foundation of Cilium. The kernel supports dynamic insertion of eBPF bytecode, like security, visibility, and networking control logic. eBPF is used to provide high-performance networking, multi-cluster capabilities, extensive network security capabilities and more.

How to use Cilium on SKS

SKS Cluster Autoscaler

Thu, 05 May 2022 13:54:38 +0000

The Cluster Autoscaler option is now available on SKS. Dynamically scale the numbers of nodes by resizing the nodepool based on node utilization or Pod deployment requirements to run the required tasks continuously.

$ kubectl -n kube-system logs deployment/cluster-autoscaler

[...]

I0324 19:50:12.521062 1 scale_up.go:675] Scale-up: setting group 0f4cd2ad-2825-4ae7-aaa2-1fd0f8e0af19 size to 5
I0324 19:50:12.530709 1 log.go:32] exoscale-provider: scaling SKS Nodepool afe7aa21-b4f6-409b-a70b-6fc31d6fada1 to size 5

[...]

The new feature helps to reduce the number of unused nodes or add nodes without manual intervention.

Full documentation

New Academy Exams: SKS Starter & Advanced

Wed, 05 Jan 2022 12:13:44 +0000

Two new exams are now available in our Exoscale Academy:

SKS Starter Exam
SKS Advanced Exam

The new SKS exams complete the SKS Foundation learning path:

Prove your knowledge and get certified on SKS with the new exams or start your SKS learning journey with our SKS Starter and SKS Advanced courses.

See all exams

Support of Kubernetes 1.23.0 & 1.22.4

Tue, 21 Dec 2021 15:07:36 +0000

The latest Kubernetes releases, 1.23.0 and 1.22.4, are now available on SKS.

Kubernetes 1.23 brings some new features to Exoscale SKS of which:

HorizontalPodAutoscaler reaches GA
OpenAPI v3 marks its debut
CSI is now the only supported way for Storage as FlexVolume is deprecated

Note: IPv4/IPv6 Dual-stack Networking par of the upstream Kubernetes 1.23 release is not yet fully compatible with Exoscale SKS. IPv6 support is being worked on for a further update on SKS.

With the latest releases we also stopped supporting version branch 1.21. The two minor versions 1.22 and 1.23 are supported from now on. Upgrade easily with SKS.

SKS lifecycle management documentation

SKS supports OpenID & Taints

Wed, 01 Dec 2021 07:52:31 +0000

Our Scalable Kubernetes Service (SKS) is constantly evolving. With our latest feature update we now support OpenID Connect as authentication method. This gives customers enhanced access control to the SKS clusters.

Additionally, SKS now also supports labels and taints. Taints can be associated to your nodepool workers during cluster creation. By using taints customers have the possibility to repel sets of pods on a node. Together with Tolerations this ensures that pods are not scheduled onto inappropriate nodes.

SKS documentation

Support of Kubernetes 1.22.2 & 1.21.5

Tue, 28 Sep 2021 13:28:17 +0000

The latest Kubernetes releases, 1.22.2 and 1.21.5, are now available on SKS.

SKS documentation

Support of Kubernetes 1.22.1 & 1.21.4

Mon, 30 Aug 2021 13:15:59 +0000

The latest Kubernetes releases, 1.22.1 and 1.21.4, are available on SKS.

With the latest release we also stopped supporting version 1.20.9 and previous. Only the latest two minor versions are supported from now on.

Full SKS documentation

New SKS features and support of Kubernetes 1.21.3 & 1.20.9

Tue, 20 Jul 2021 13:59:07 +0000

The latest Kubernetes releases, 1.21.3 and 1.20.9, are now available on SKS.

Additionally, we released several new features on our Kubernetes offering:

Auto-upgrades: Configure the control plane of your clusters to be automatically upgraded to the latest patch release available for your Kubernetes minor version.
Private networks support: Attach private networks to nodepools. Virtual machines belonging to these nodepools will automatically join the managed private networks. Use this feature to enable the communication between applications running on Kubernetes and applications running on regular virtual machines on your managed private network.
Labels: Add labels to clusters and nodepools to organize them more easily. Nodepools labels are automatically propagated to the underlying instance pool and virtual machines.
Dedicated hypervisor support for nodepools: Users can run SKS nodepools on dedicated hypervisors by specifying the hypervisor group in a new "deploy-target" parameter on nodepools. This feature is also available for regular instance pools (not managed by SKS).
Instance prefix: By default, virtual machines (workers) for SKS are named "pool-<first 5 chars of the underlying instance pool id>-<5 random char>". Users can now control the prefix and replace "pool" by something else. This feature enables users to organize machines by name, which makes it easier to work with. It is also available in both nodepools and instance pools.

Learn more in our SKS documentation

SKS supports Kubernetes 1.21

Tue, 27 Apr 2021 10:27:35 +0000

SKS now supports Kubernetes 1.21.

As part of our lifecycle management commitment, SKS now has the below supportability matrix:

1.21 is the new minor release and enters a 180 days support from Exoscale SKS
1.20.6 is the latest version from the previous minor release

K8S 1.21 brings amongst many features and improvements cronjobs in stable release as well as Immutable Secrets and ConfigMaps.

SKS Lifecycle Management

SKS has reached General Availability

Wed, 31 Mar 2021 14:00:23 +0000

We are really proud to announce that SKS has now been rolled out in all Exoscale Zones and has reached general availability.

Like detailed in our introductory announcement, this also means that starting tomorrow April 1st, 2021:

SLAs on SKS are fully enforced - PRO version
Support is fully active
Billing for PRO clusters begins
Web portal access will be live

Documentation on SKS has already been extended and will continue to grow in the next weeks.

The service has also already received a list of new features and upgrades:

Terraform support in the Exoscale Terraform Provider
Lifecycle management: easy upgrade of control plane and node pools
Credentials rotation

Happy clustering!

SKS product features

Introducing Scalable Kubernetes Service

Sun, 14 Feb 2021 20:20:37 +0000

Today we introduce SKS - Scalable Kubernetes Service - the last addition to Exoscale consumable infrastructure service.

SKS brings simplicity and reliability to any Kubernetes workload with:

Fully managed control plane
Dynamic NodePool attachment
Integration with NLB
Wide choice of instance types

SKS launches today to all customers with Limited Availability in 3 zones :

Geneva
Frankfurt
Vienna

and sets a General Availability in all zones for mid March 2021 as well as activation of full SLAs on the service.

5 steps Quick-Start guide

Exoscale Kubernetes Cloud Controller Manager release

Thu, 06 Aug 2020 13:35:28 +0000

An official Kubernetes Cloud Controller Manager is now available, allowing a deeper integration of your clusters with our platform.

You can now transparently map k8s functionalities to the corresponding Exoscale ones.

Marketplace: Compliant Kubernetes - by Elastisys

Thu, 02 Apr 2020 00:00:46 +0000

Compliant Kubernetes (CK8s) is a Managed Service by Elastisys. It provides a container platform built for strong security and full lifecycle compliance with ISO-27001, GDPR and PCI-DSS, running on Exoscale.com

Compliant Kubernetes - by Elastisys

Discover more on the Exoscale Marketplace