update roadmap (#962)
Signed-off-by: Jianbo Sun <jianbo.sjb@alibaba-inc.com> Signed-off-by: Jianbo Sun <jianbo.sjb@alibaba-inc.com>
This commit is contained in:
parent
13758bd693
commit
fb1a820c6d
|
|
@ -4,6 +4,8 @@ title: Migrate from Old Versions
|
|||
|
||||
This doc aims to provide a migration guide from old versions to the new ones without disturb the running business. However scenarios are different from each other, we strongly recommend you to test the migration with a simulation environment before real migration for your production.
|
||||
|
||||
KubeVela has [release cadence](../../contributor/release-process) for every 2-3 months, we'll only maintain for the last 2 releases. As a result, you're highly recommended to upgrade along with the community. We'll strictly align with the [semver version rule](https://semver.org/) for compatibility.
|
||||
|
||||
## From v1.4.x to v1.5.x
|
||||
|
||||
1. Upgrade the CRDs, please make sure you upgrade the CRDs first before upgrade the helm chart.
|
||||
|
|
|
|||
|
|
@ -0,0 +1,26 @@
|
|||
---
|
||||
title: Roadmap 2022.12
|
||||
---
|
||||
|
||||
Date: 2022-10-01 to 2022-12-31
|
||||
|
||||
## Core Platform
|
||||
|
||||
- Support Iot/Edge Application Delivery: https://github.com/kubevela/kubevela/issues/4326
|
||||
- Support adopt existing workload such as Deployment/StatefulSet and CRD controllers, manage it by KubeVela Application.
|
||||
- Support application template and build application registry along with addon registry. Provide application export/load capability.
|
||||
- Support build application from source code for developer and use OCI infrastructure to delivery application.
|
||||
- Enhance the security for end to end application delivery and management.
|
||||
- Make automated out-of-box application level observability for more scenarios.
|
||||
- Enhance the input/output capability for Component and Workflow.
|
||||
|
||||
|
||||
## Third-party integrations and more addons
|
||||
|
||||
- Integrate with OPA/Kyverno/Cosign and other projects to provide a secure software supply chain.
|
||||
- Integrate with OpenSergo for micro services governance.
|
||||
- Integrate with OpenYurt for Iot/edge application delivery.
|
||||
|
||||
## Best practices
|
||||
|
||||
- Provide one or more best practices about how to use KubeVela in game/financial/edge scenario.
|
||||
|
|
@ -2,6 +2,15 @@
|
|||
title: Roadmap
|
||||
---
|
||||
|
||||
The goal of KubeVela is to **make deploying and operating applications across today's hybrid, multi-cloud environments easier, faster and more reliable**. We will make effort on the following aspects to make the goal achievable:
|
||||
|
||||
* Provide a **modular, extensible, and portable control plane** for modeling application deployment with **higher level yet consistent** API. The control plane can both adapt to the existing infrastructure and extend with the fast growing cloud native ecosystem as **reusable building blocks**.
|
||||
* Enable simple and robust **application delivery across hybrid environments** including Kubernetes, cloud, or even IoT devices. This also enables you to have a vendor agnostic application platform.
|
||||
* Build an **open, inclusive, and vibrant OSS developer community** focused on solving real-world application delivery and operation problems, sharing the reusable building blocks and best practices.
|
||||
|
||||
They're aligned with the roadmap direction for the next three years. As for the detailed roadmap, we'll update and list below.
|
||||
|
||||
- [2022 Winter Roadmap](./2022-12-roadmap)
|
||||
- [2022 Fall Roadmap](./2022-09-roadmap)
|
||||
- [2022 Summer Roadmap](./2022-06-roadmap)
|
||||
- [2022 Spring Roadmap](./2022-03-roadmap)
|
||||
|
|
|
|||
|
|
@ -4,6 +4,8 @@ title: 从旧版本进行迁移
|
|||
|
||||
本文档旨在提供在不会干扰正在运行的业务的情况下从旧版本到新版本的迁移指南。但是考虑到场景彼此不同,我们强烈建议你在实际迁移之前使用模拟环境对迁移进行测试。
|
||||
|
||||
KubeVela 的[发布周期](../../contributor/release-process)定为每隔 2-3 个月发布一个版本,我们将维护最近的 2 个版本。所以,我们强烈推荐你跟着社区的节奏一同升级,我们会严格遵循 [semver 版本](https://semver.org/)定义的兼容性规则。
|
||||
|
||||
## 从 v1.4.x 版本 到 v1.5.x 版本
|
||||
|
||||
1. 升级 CRD,请确保在升级 helm chart 之前先升级 CRD。
|
||||
|
|
|
|||
|
|
@ -4,6 +4,8 @@ title: 从旧版本进行迁移
|
|||
|
||||
本文档旨在提供在不会干扰正在运行的业务的情况下从旧版本到新版本的迁移指南。但是考虑到场景彼此不同,我们强烈建议你在实际迁移之前使用模拟环境对迁移进行测试。
|
||||
|
||||
KubeVela 的[发布周期](../../contributor/release-process)定为每隔 2-3 个月发布一个版本,我们将维护最近的 2 个版本。所以,我们强烈推荐你跟着社区的节奏一同升级,我们会严格遵循 [semver 版本](https://semver.org/)定义的兼容性规则。
|
||||
|
||||
## 从 v1.4.x 版本 到 v1.5.x 版本
|
||||
|
||||
1. 升级 CRD,请确保在升级 helm chart 之前先升级 CRD。
|
||||
|
|
|
|||
|
|
@ -361,7 +361,7 @@ spec:
|
|||
message:
|
||||
msgtype: text
|
||||
text:
|
||||
context: Workflow starting...
|
||||
content: Workflow starting...
|
||||
- name: application
|
||||
type: apply-application
|
||||
- name: slack-message
|
||||
|
|
|
|||
|
|
@ -4,6 +4,8 @@ title: Migrate from Old Versions
|
|||
|
||||
This doc aims to provide a migration guide from old versions to the new ones without disturb the running business. However scenarios are different from each other, we strongly recommend you to test the migration with a simulation environment before real migration for your production.
|
||||
|
||||
KubeVela has [release cadence](../../contributor/release-process) for every 2-3 months, we'll only maintain for the last 2 releases. As a result, you're highly recommended to upgrade along with the community. We'll strictly align with the [semver version rule](https://semver.org/) for compatibility.
|
||||
|
||||
## From v1.4.x to v1.5.x
|
||||
|
||||
1. Upgrade the CRDs, please make sure you upgrade the CRDs first before upgrade the helm chart.
|
||||
|
|
|
|||
|
|
@ -0,0 +1,26 @@
|
|||
---
|
||||
title: Roadmap 2022.12
|
||||
---
|
||||
|
||||
Date: 2022-10-01 to 2022-12-31
|
||||
|
||||
## Core Platform
|
||||
|
||||
- Support Iot/Edge Application Delivery: https://github.com/kubevela/kubevela/issues/4326
|
||||
- Support adopt existing workload such as Deployment/StatefulSet and CRD controllers, manage it by KubeVela Application.
|
||||
- Support application template and build application registry along with addon registry. Provide application export/load capability.
|
||||
- Support build application from source code for developer and use OCI infrastructure to delivery application.
|
||||
- Enhance the security for end to end application delivery and management.
|
||||
- Make automated out-of-box application level observability for more scenarios.
|
||||
- Enhance the input/output capability for Component and Workflow.
|
||||
|
||||
|
||||
## Third-party integrations and more addons
|
||||
|
||||
- Integrate with OPA/Kyverno/Cosign and other projects to provide a secure software supply chain.
|
||||
- Integrate with OpenSergo for micro services governance.
|
||||
- Integrate with OpenYurt for Iot/edge application delivery.
|
||||
|
||||
## Best practices
|
||||
|
||||
- Provide one or more best practices about how to use KubeVela in game/financial/edge scenario.
|
||||
|
|
@ -2,6 +2,15 @@
|
|||
title: Roadmap
|
||||
---
|
||||
|
||||
The goal of KubeVela is to **make deploying and operating applications across today's hybrid, multi-cloud environments easier, faster and more reliable**. We will make effort on the following aspects to make the goal achievable:
|
||||
|
||||
* Provide a **modular, extensible, and portable control plane** for modeling application deployment with **higher level yet consistent** API. The control plane can both adapt to the existing infrastructure and extend with the fast growing cloud native ecosystem as **reusable building blocks**.
|
||||
* Enable simple and robust **application delivery across hybrid environments** including Kubernetes, cloud, or even IoT devices. This also enables you to have a vendor agnostic application platform.
|
||||
* Build an **open, inclusive, and vibrant OSS developer community** focused on solving real-world application delivery and operation problems, sharing the reusable building blocks and best practices.
|
||||
|
||||
They're aligned with the roadmap direction for the next three years. As for the detailed roadmap, we'll update and list below.
|
||||
|
||||
- [2022 Winter Roadmap](./2022-12-roadmap)
|
||||
- [2022 Fall Roadmap](./2022-09-roadmap)
|
||||
- [2022 Summer Roadmap](./2022-06-roadmap)
|
||||
- [2022 Spring Roadmap](./2022-03-roadmap)
|
||||
|
|
|
|||
Loading…
Reference in New Issue