kyma-project / kyma

Kyma is an opinionated set of Kubernetes-based modular building blocks, including all necessary capabilities to develop and run enterprise-grade cloud-native applications.
https://kyma-project.io
Apache License 2.0
1.51k stars 404 forks source link

Define process to provide consistent testing windows for new Kyma versions #13985

Closed varbanv closed 6 months ago

varbanv commented 2 years ago

Description

Provide a way for customers to test and validate new Kyma versions before their managed production clusters are upgraded.

Reasons

Kyma version upgrades can introduce breaking changes for customer workloads. We extensively test the upgrades with our components but we do not have an official process on how to enable our customers to test their workloads with the new version. Customers have requested that there is a defined window when they can test Kyma version upgrades on their Dev and Test managed environments and that window should be longer than few days. We also have requests from internal teams to be able to test new functionality for longer periods with the help of a subset of users in order to get better feedback and detect any potential issues. Providing a testing window to customers would give us such capability.

Attachments


:warning: Funnel process - do not remove!
Name|Value :--- | :--- theme | Enterprise-grade business value | 10 technical value | 0 user value | 10 open-source value | 0 effort | requested by |
Sawthis commented 2 years ago

Collect stage/dev global accounts from customers and perform upgrade together with kyma-integration upgrade. Provide one week window for customers tests.

ghost commented 2 years ago

This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions.

github-actions[bot] commented 2 years ago

This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions.

kyma-bot commented 1 year ago

This issue or PR has been automatically marked as stale due to the lack of recent activity. Thank you for your contributions.

This bot triages issues and PRs according to the following rules:

You can:

If you think that I work incorrectly, kindly raise an issue with the problem.

/lifecycle stale

mperumalswamy commented 1 year ago

Any updates on this issue about availability?

Best regards, Madhu

varbanv commented 1 year ago

Hi @mperumalswamy we are making steady progress with our modularization approach that includes the concept of release channels. Based on the release channels, end users would be able to select and use upcoming versions of each component in their clusters in order to preview and/or test new functionality ahead of the official releases. And, of course, the new approach allows users to only select the components they need in order to reduce upgrade times and disruption potential.

kyma-bot commented 1 year ago

This issue or PR has been automatically marked as stale due to the lack of recent activity. Thank you for your contributions.

This bot triages issues and PRs according to the following rules:

You can:

If you think that I work incorrectly, kindly raise an issue with the problem.

/lifecycle stale

mperumalswamy commented 1 year ago

Hi @mperumalswamy we are making steady progress with our modularization approach that includes the concept of release channels. Based on the release channels, end users would be able to select and use upcoming versions of each component in their clusters in order to preview and/or test new functionality ahead of the official releases. And, of course, the new approach allows users to only select the components they need in order to reduce upgrade times and disruption potential.

Hi @varbanv Any timeline regarding this?

varbanv commented 1 year ago

Hi @mperumalswamy we will be doing a gradual migration to the new architecture. So some components could have this as early as end of Q1 while others could stretch into Q3.

kyma-bot commented 1 year ago

This issue or PR has been automatically marked as stale due to the lack of recent activity. Thank you for your contributions.

This bot triages issues and PRs according to the following rules:

You can:

If you think that I work incorrectly, kindly raise an issue with the problem.

/lifecycle stale

kyma-bot commented 1 year ago

This issue or PR has been automatically marked as stale due to the lack of recent activity. Thank you for your contributions.

This bot triages issues and PRs according to the following rules:

You can:

If you think that I work incorrectly, kindly raise an issue with the problem.

/lifecycle stale

kyma-bot commented 1 year ago

This issue or PR has been automatically marked as stale due to the lack of recent activity. Thank you for your contributions.

This bot triages issues and PRs according to the following rules:

You can:

If you think that I work incorrectly, kindly raise an issue with the problem.

/lifecycle stale

kyma-bot commented 1 year ago

This issue or PR has been automatically marked as stale due to the lack of recent activity. Thank you for your contributions.

This bot triages issues and PRs according to the following rules:

You can:

If you think that I work incorrectly, kindly raise an issue with the problem.

/lifecycle stale

kyma-bot commented 10 months ago

This issue or PR has been automatically marked as stale due to the lack of recent activity. Thank you for your contributions.

This bot triages issues and PRs according to the following rules:

You can:

If you think that I work incorrectly, kindly raise an issue with the problem.

/lifecycle stale

kyma-bot commented 8 months ago

This issue or PR has been automatically marked as stale due to the lack of recent activity. Thank you for your contributions.

This bot triages issues and PRs according to the following rules:

You can:

If you think that I work incorrectly, kindly raise an issue with the problem.

/lifecycle stale

github-actions[bot] commented 6 months ago

This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions.

varbanv commented 6 months ago

We have completed the Kyma modularization project and will migrate the last component in existing clusters to the corresponding module this weekend. From then on, users can test upcoming versions of any module by using the Fast channel in their non-production clusters and will receive that same module version in the Regular channel 2 weeks later. Please, do not use Fast channel on production clusters!