# Roadmap

*Last updated: 16 October 2026*

Our product roadmap outlines planned improvements for MetaKube Core customers. Below is an overview of our current priorities, what comes next, and what we are considering for later.

---

## Understanding Now, Next, Later

**Now**: Our current priorities for product improvements.

**Next**: Planned work to follow our current priorities.

**Later**: Longer-term plans and opportunities under consideration.

Priorities, scope, and timing may change. Please refer to the [product documentation](<https://documentation.syseleven.de/en/products/metakube-core/>) and [release notes](<https://documentation.syseleven.de/en/products/metakube-core/release-notes/>) for current availability.

## Overview

| Now | Next | Later |
| --- | --- | --- |
| Node-to-Node Encryption | Cluster Mesh Self-Service | Management API Resilience |
|  |  | SCS KaaS Certification |
|  |  | Edge Cloud Pilot |

## Roadmap Details

**Node-to-Node Encryption** is intended to protect supported network traffic between cluster nodes. Feature documentation will describe the covered traffic types, supported configurations, and activation process.

**Cluster Mesh Self-Service** will simplify establishing and removing connections between supported MetaKube Core clusters. The initial release scope, network prerequisites, and supported scenarios will be documented before availability.

**Management API Resilience** covers the API used to create and manage clusters. **SCS KaaS certification** is a goal that requires a successful assessment. **The Edge Cloud pilot** remains under consideration.

Supported configurations, regional availability, release states, and any required customer actions will be communicated before rollout.

## Key Milestones

- **Q1 2026:** Expanded Kubernetes support with version 1.35.
- **Q2 2026:** Updated supported Kubernetes versions and the container runtime.
- **Q3 2026:** Added support for Kubernetes 1.37.
- **Q4 2026 — Current focus:** Introducing encryption for supported network traffic between cluster nodes.

## Stay Updated

Please contact our team for more information about planned capabilities or to share requirements for your use case.
