-
Notifications
You must be signed in to change notification settings - Fork 399
Open
Description
Problem statement
Customers cannot test their workloads with the upcoming Kubernetes versions scheduled to be deployed in Kyma clusters.
What is the current state, unmet need, or symptom?
- There is no way for a customer to get a Kyma cluster with the next planned Kubernetes version.
- Customers have no way to test their applications end-to-end for upcoming Kyma versions.
Who is affected?
- Cluster operators
- Developers
- Kyma org - we risk outages because of Kubernetes breaking changes
When and where does this problem occur?
Usually happens when customers need to test Kubernetes version changes because we warned them about them or they read about those changes.
Why does it matter?
- If we cannot provide a way for customers to test their applications we risk outages which lead to bad reputation for Kyma.
- Since we cannot provide that capability, it falls on us to do the heavy lifting around k8s upgrades.
Original request/trigger
https://github.tools.sap/kyma/backlog/issues/4940
Success metrics and targets
Risks, unknowns, and constraints
Dependencies and stakeholder map
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels