v1.7.0

We're excited to announce the KubeVela v1.7 has released now !! Happy New Year!! 🎉 🎉

In this release, we are mainly focus on issues about user adoptions, such as adopting exist workload as vela applications, performance tunning, VelaUX enhancements and so on.

Thanks to all our contributors! We can't release so many powerful features without your great work! ❤️❤️

Highlight Features

Workloads Adoption

This feature adopt resources as a KubeVela application. This command is useful when you already have resources applied in your Kubernetes cluster. These resources could be applied natively or with other tools, such as Helm. This command will automatically find out the resources to be adopted and assemble them into a new application which won't trigger any damage such as restart on the adoption.

There are two types of adoption supported by far, native Kubernetes resources (by default) and helm releases.

1. For native type, you can specify a list of resources you want to adopt in the application. Only resources in local cluster are supported for now.
2. For helm type, you can specify a helm release name. This helm release should be already published in the local cluster. The command will find the resources managed by the helm release and convert them into an adoption application.

There are two working mechanism (called modes here) for the adoption by far, read-only mode (by default) and take-over mode.

1. In read-only mode, adopted resources will not be touched. You can leverage vela tools (like Vela CLI or VelaUX) to observe those resources and attach traits to add new capabilities. The adopted resources will not be recycled or updated. This mode is recommended if you still want to keep using other tools to manage resources updates or deletion, like Helm.
2. In take-over mode, adopted resources are completely managed by application which means they can be modified. You can use traits or directly modify the component to make edits to those resources. This mode can be helpful if you want to migrate existing resources into KubeVela system and let KubeVela to handle the life-cycle of target resources.

Detail docs: https://kubevela.net/docs/next/end-user/policies/resource-adoption

Thanks to @Somefive for contributing this powerful features in:

• Feat: takeover & readonly policy #5102
• Feat: vela adopt command #5197
• Feat: gc orphan resources #4847

Performance Tunning

In this release, we optimized the default Helm chart values for 5-10x better performance and capacity increase:

Tunning values that can cause break changes

• applicationRevisionLimit changes from 10 to 2, by default it will reserve only 2 app revisions instead of 10, which mean you don't have many revisions as options for rolling back. If you want to keep the value, you can specify by:

  helm upgrade --set applicationRevisionLimit=10
  

• optimize.disableComponentRevision by default, we'll turn off component revision, it will affect users who use the older rollout addon, users who're using kruise-rollout won't be affected. If you still want to use it, please specify the paramter when installing/upgrading.

  helm upgrade --set optimize.disableComponentRevision=false
  

Other tunning values

• definitionRevisionLimit changes from 20 to 2, by default it will reserve only 2 revisions for each definitions instead of 10.
• featureGates.zstdResourceTracker by default, the controller will use zstd for resourceTracker compression.
• featureGates.zstdApplicationRevision by default, the controller will use zstd for applicationRevision compression.
• kubeClient.qps and kubeClient.burst changes to 100 and 200, double sized from older ones.
• enableFluxcdAddon deprecated as it's already widely used as being installed as addon.

Thanks to @charlie0129 and @wonderflow for contributing this feature:

• Feat: add support for compressing apprev using gzip and zstd by @charlie0129 in #5090
• Feat: optimize controller default value for better performance by @wonderflow in #5194

Dry Run Enhancement

Dry run with policy and workflow files

With this feature, you can you can specify different policy and workflow with application files, for example:

Run application for test environment:

vela dry-run  -f app.yaml -f test-policy.yaml -f test-workflow.yaml

Run application for production environment:

vela dry-run  -f app.yaml -f prod-policy.yaml -f prod-workflow.yaml

Additionally, if the provided policy and workflow files are not referenced by application file, warning message will show up
and those files will be ignored. You can use "merge" flag to make those standalone files effective:

vela dry-run  -f app-with-no-reference-policy-and-workflow.yaml -f prod-policy.yaml -f prod-workflow.yaml --merge

Detail design can be check here: #5184

Thanks to @cezhang for contributing this powerful feature: #4815.

Dry run check before any resource dispatch

Previously, when application contains objects that should not be dispatched (like invalid resource, target cluster disconnected, authorization failed), the dispatch of the resources are recorded in ResourceTracker, which will trigger these resources to be recycled and state-kept afterwards. However, since these dispatch are not successful, we will encounter errors during gc or state-keep.

This feature add pre-dispatch DryRun check for the to-dispatch resources before recording them into ResourceTrackers. Therefore, invalid resources will not be recorded if they are detected during the dryrun process. It will greatly reduce the possibility of recording not-dispatched resources into ResourceTrackers.

Thanks to @Somefive for contributing this feature in #5277

Interactive Resource Delete

The interactive resource delete allow you to delete part of your aplication resources in the vela delete command.

Now we support delete application in various modes. Natively, you can use it like "kubectl delete app [app-name]".

• In the cases you only want to delete the application but leave the resources there, you can use the --orphan parameter.
• In the cases the server-side controller is uninstalled, or you want to manually skip some errors in the deletion process (like lack privileges or handle cluster disconnection), you can use the --force parameter.
• In the case you want to delete resources partially, you can use -i parameter to delete in interactive mode.

Thanks to @Somefive for contributing this feature in #5266

Allow Specified Privileged Users

This feature allows us to configure some accounts as privileged users without creating accounts in managed clusters, this can help protect privileges leaking. We're using the PrivilegedIdentityExchanger Mechanism from cluster-gateway.

Thanks to @Somefive for contributing this feature in #5284

Component orchestration with multi-clusters

Previously, we can't use deploy workflow step to handle component level parameter input and output, which means we can't support component level parameter input/output in multi-cluster scenarios. This feature allow us this feature, to define component input/output with multi-cluster policies.

Docs: https://kubevela.net/docs/next/end-user/workflow/component-dependency-parameter#multi-cluster-orchestration

Thanks to @chivalryq for contributing this feature in #5161

Dynamic Notification for Addon Installation

The NOTES.cue file allows you to display dynamic notifications once the addon has been enabled, based on specified parameters.

For example, you can write the NOTES.cue as shown below:

info: string
if !parameter.pluginOnly {
	info: """
		By default, the backstage app is strictly serving in the domain `127.0.0.1:7007`, check it by:
		            
		    vela port-forward addon-backstage -n vela-system
		
		You can build your own backstage app if you want to use it in other domains. 
		"""
}
if parameter.pluginOnly {
	info: "You can use the endpoint of 'backstage-plugin-vela' in your own backstage app by configuring the 'vela.host', refer to example https://github.com/wonderflow/vela-backstage-demo."
}
notes: (info)

and parameter.cue as shown below:

paramters: {
	pluginOnly: *false | string 
}

Once the addon is enabled using the CLI, you will see different results according to the parameters from end users.

This example is from the backstage addon, you can find more information by visiting this link.

Thanks to @wonderflow in #5195

Workflow Enhancement

Feature Enhancement

• Support workflow to restart from a specified failed step like:

   vela workflow restart <app-name> --step=<step-name>

• Support automatic generation of name for workflow step if it is empty.
• Previously, if the key in inputs.parameterKey is also specified in parameter, it will cause conflict. In the new version, the inputs will replace the value in parameter and there will be no confict like:

     workflow:
       steps:
       - inputs:
         - from: context.name
           parameterKey: slack.message.text
         name: slack-message
         properti...

v1.7.0-beta.2

What's Changed

Highlights

• Feat: vela dry-run render results should be affected by override policy and deploy workflowstep by @cezhang in #4815

Enhancements

• Test: use mock server in addon tests to make it more stable by @charlie0129 in #5286
• Fix: delete appplication fails if status.workflow.endTime not specified. by @LiuFang07 in #5287
• Fix: fix vela debug cli to find id for step by @FogDong in #5294
• Fix: don't return err if subresource type is not found when listing application resources. by @hnd4r7 in #5295
• Fix: provide more explicit error when addon package hasn't a metadata.yaml by @wangyikewxgm in #5298
• Fix: Index structure map[string]string,Mongo resulting in inconsistent results obtained by filtering non-string type by index. by @LiuFang07 in #5274
• Fix: enhance the application synchronizer with publishVersion by @barnettZQG in #5299
• Fix: create a config with the same name reported an incorrect error by @nuclearwu in #5270
• Fix: error msg when uninstall vela by @Xunzhuo in #5304

How to install

Install Vela Core by Using Vela CLI

curl -fsSl https://kubevela.io/script/install.sh | bash -s 1.7.0-beta.2
vela install -v 1.7.0-beta.2

Install Vela Core by Using Helm:

helm repo add kubevela https://charts.kubevela.net/core
helm repo update
helm install --create-namespace -n vela-system kubevela kubevela/vela-core --version 1.7.0-beta.2 --wait

Install VelaUX addon

vela addon enable velaux --version=v1.7.0-beta.2

How to upgrade from old version?

Refer to the docs( https://kubevela.net/docs/platform-engineers/system-operation/migration-from-old-version ) if you're migrating from older versions.

Upgrade by using Vela CLI

The install command will also handle the upgrade automatically：

curl -fsSl https://kubevela.io/script/install.sh | bash -s 1.7.0-beta.2
vela install -v 1.7.0-beta.2 -r

Upgrade by using Helm

⚠️ Please upgrade the CRD first if you're upgrading to this release.

1. Upgrade the CRDs, please make sure you upgrade the CRDs first before upgrade the helm chart.

kubectl apply -f https://raw.githubusercontent.com/oam-dev/kubevela/release-1.7/charts/vela-core/crds/core.oam.dev_applicationrevisions.yaml
kubectl apply -f https://raw.githubusercontent.com/oam-dev/kubevela/release-1.7/charts/vela-core/crds/core.oam.dev_applications.yaml
kubectl apply -f https://raw.githubusercontent.com/oam-dev/kubevela/release-1.7/charts/vela-core/crds/core.oam.dev_resourcetrackers.yaml
kubectl apply -f https://raw.githubusercontent.com/oam-dev/kubevela/release-1.7/charts/vela-core/crds/core.oam.dev_componentdefinitions.yaml
kubectl apply -f https://raw.githubusercontent.com/oam-dev/kubevela/release-1.7/charts/vela-core/crds/core.oam.dev_definitionrevisions.yaml

2. Upgrade your kubevela chart

Since we have migrated some workflowstep definitions and views from workflow addon to KubeVela core repo, so it may cause the following error if you upgrade:

Error: Could not install KubeVela control plane installation: error when installing/upgrading Helm Chart kubevela in namespace vela-system: rendered manifests contain a resource that already exists. Unable to continue with update: WorkflowStepDefinition "apply-deployment" in namespace "vela-system" exists and cannot be imported into the current release: invalid ownership metadata; label validation error: missing key "app.kubernetes.io/managed-by": must be set to "Helm"; annotation validation error: missing key "meta.helm.sh/release-name": must be set to "kubevela"; annotation validation error: missing key "meta.helm.sh/release-namespace": must be set to "vela-system"

You can execute this script to solve it before upgrade helm chart:

curl -fsSl https://kubevela.net/script/checklegacy.sh | bash

The script will just help patch helm annotations for you, you can also do that manually one by one like:

kubectl patch -n vela-system workflowstepdefinition <item> --type=merge -p '{"metadata":{"annotations":{"meta.helm.sh/release-name":"kubevela","meta.helm.sh/release-namespace":"vela-system"},"labels":{"app.kubernetes.io/managed-by":"Helm"}}}'
kubectl patch -n vela-system configMap <item> --type=merge -p '{"metadata":{"annotations":{"meta.helm.sh/release-name":"kubevela","meta.helm.sh/release-namespace":"vela-system"},"labels":{"app.kubernetes.io/managed-by":"Helm"}}}'

Then you can upgrade the helm chart now:

helm repo add kubevela https://charts.kubevela.net/core
helm repo update
helm upgrade -n vela-system --install kubevela kubevela/vela-core --version 1.7.0-beta.2 --wait

3. Download the new CLI and enable velaux

curl -fsSl https://kubevela.io/script/install.sh | bash -s 1.7.0-beta.2
vela addon enable velaux

Upgrade VelaUX

vela addon upgrade velaux --version=v1.7.0-beta.2

New Contributors

• @hnd4r7 made their first contribution in #5295
• @Xunzhuo made their first contribution in #5304

Full Changelog: v1.7.0-beta.1...v1.7.0-beta.2

v1.6.7

What's Changed

• [Backport release-1.6] Fix: keep the workflow data structure in MongoDB by @github-actions in #5283
• [Backport release-1.6] Test: use mock server in addon tests by @github-actions in #5289
• [Backport release-1.6] Fix: delete appplication fails if status.workflow.endTime not specified. by @github-actions in #5296
• [Backport release-1.6] Fix: create a config with the same name reported an incorrect error by @github-actions in #5306
• [Backport release-1.6] Fix: error msg when uninstall vela by @github-actions in #5309
• [Backport release-1.6] Fix: don't return err if subresource type is not found when listing application resources. by @github-actions in #5311

How to install

Install Vela Core by Using Vela CLI

curl -fsSl https://kubevela.io/script/install.sh | bash -s 1.6.7
vela install -v 1.6.7

Install Vela Core by Using Helm:

helm repo add kubevela https://charts.kubevela.net/core
helm repo update
helm install --create-namespace -n vela-system kubevela kubevela/vela-core --version 1.6.7 --wait

Install VelaUX addon

vela addon enable velaux --version=v1.6.6

How to upgrade from old version?

Refer to the docs( https://kubevela.net/docs/platform-engineers/system-operation/migration-from-old-version ) if you're migrating from older versions.

Upgrade by using Vela CLI

The install command will also handle the upgrade automatically：

curl -fsSl https://kubevela.io/script/install.sh | bash -s 1.6.7
vela install -v 1.6.7 -r

Upgrade by using Helm

1. Upgrade the CRDs, please make sure you upgrade the CRDs first before upgrade the helm chart.

kubectl apply -f https://raw.githubusercontent.com/oam-dev/kubevela/release-1.6/charts/vela-core/crds/core.oam.dev_applicationrevisions.yaml
kubectl apply -f https://raw.githubusercontent.com/oam-dev/kubevela/release-1.6/charts/vela-core/crds/core.oam.dev_applications.yaml
kubectl apply -f https://raw.githubusercontent.com/oam-dev/kubevela/release-1.6/charts/vela-core/crds/core.oam.dev_resourcetrackers.yaml
kubectl apply -f https://raw.githubusercontent.com/oam-dev/kubevela/release-1.6/charts/vela-core/crds/core.oam.dev_componentdefinitions.yaml
kubectl apply -f https://raw.githubusercontent.com/oam-dev/kubevela/release-1.6/charts/vela-core/crds/core.oam.dev_definitionrevisions.yaml

2. Upgrade your kubevela chart

helm repo add kubevela https://charts.kubevela.net/core
helm repo update
helm upgrade -n vela-system --install kubevela kubevela/vela-core --version 1.6.7 --wait

3. Download the new CLI and enable velaux

curl -fsSl https://kubevela.io/script/install.sh | bash -s 1.6.7
vela addon enable velaux

Upgrade VelaUX

vela addon upgrade velaux --version=v1.6.6

Full Changelog: v1.6.6...v1.6.7

v1.7.0-beta.1

What's Changed

Highlight Features

Interactive Delete Mode

• Feat: support interactive mode to manually skip encountered errors by @Somefive in #5266

Client Identity Exchanger

Proposal detail: oam-dev/cluster-gateway#120
In this release, we've supported PrivilegedIdentityExchanger that will directly use the original identity registered by the cluster. by @Somefive in #5284

Others

• Feat: support hostpath in storage and vela cli by @FogDong in #5265
• Feat: add the API that rollbacks the application by @barnettZQG in #5273
• Feat: add pre-dispatch dryrun check by @Somefive in #5277

Enhancement

• Fix: fix inputs conflict for workflow by @FogDong in #5251
• Chore: update broken link of bot.md by @aimuz in #5262
• Fix: make the impersonation feature work by @barnettZQG in #5261
• Fix: apiserver k8sclient have duplicated multicluster wrapper by @chivalryq in #5275
• Fix: check the legacy definitions in vela install by @FogDong in #5268
• Fix: move notes to the right to avoid package head to be invalid format by @wonderflow in #5280
• Fix: make the synced workflow name normative by @barnettZQG in #5278
• Fix: keep the workflow data structure in MongoDB by @barnettZQG in #5276
• Fix: the addon management APIs support the user impersonation by @barnettZQG in #5282

How to install

Install Vela Core by Using Vela CLI

curl -fsSl https://kubevela.io/script/install.sh | bash -s 1.7.0-beta.1
vela install -v 1.7.0-beta.1

Install Vela Core by Using Helm:

helm repo add kubevela https://charts.kubevela.net/core
helm repo update
helm install --create-namespace -n vela-system kubevela kubevela/vela-core --version 1.7.0-beta.1 --wait

Install VelaUX addon

vela addon enable velaux --version=v1.7.0-beta.1

How to upgrade from old version?

Refer to the docs( https://kubevela.net/docs/platform-engineers/system-operation/migration-from-old-version ) if you're migrating from older versions.

Upgrade by using Vela CLI

The install command will also handle the upgrade automatically：

curl -fsSl https://kubevela.io/script/install.sh | bash -s 1.7.0-beta.1
vela install -v 1.7.0-beta.1 -r

Upgrade by using Helm

⚠️ Please upgrade the CRD first if you're upgrading to this release.

1. Upgrade the CRDs, please make sure you upgrade the CRDs first before upgrade the helm chart.

kubectl apply -f https://raw.githubusercontent.com/oam-dev/kubevela/release-1.7/charts/vela-core/crds/core.oam.dev_applicationrevisions.yaml
kubectl apply -f https://raw.githubusercontent.com/oam-dev/kubevela/release-1.7/charts/vela-core/crds/core.oam.dev_applications.yaml
kubectl apply -f https://raw.githubusercontent.com/oam-dev/kubevela/release-1.7/charts/vela-core/crds/core.oam.dev_resourcetrackers.yaml
kubectl apply -f https://raw.githubusercontent.com/oam-dev/kubevela/release-1.7/charts/vela-core/crds/core.oam.dev_componentdefinitions.yaml
kubectl apply -f https://raw.githubusercontent.com/oam-dev/kubevela/release-1.7/charts/vela-core/crds/core.oam.dev_definitionrevisions.yaml

2. Upgrade your kubevela chart

Since we have migrated some workflowstep definitions and views from workflow addon to KubeVela core repo, so it may cause the following error if you upgrade:

Error: Could not install KubeVela control plane installation: error when installing/upgrading Helm Chart kubevela in namespace vela-system: rendered manifests contain a resource that already exists. Unable to continue with update: WorkflowStepDefinition "apply-deployment" in namespace "vela-system" exists and cannot be imported into the current release: invalid ownership metadata; label validation error: missing key "app.kubernetes.io/managed-by": must be set to "Helm"; annotation validation error: missing key "meta.helm.sh/release-name": must be set to "kubevela"; annotation validation error: missing key "meta.helm.sh/release-namespace": must be set to "vela-system"

You can execute this script to solve it before upgrade helm chart:

curl -fsSl https://kubevela.net/script/checklegacy.sh | bash

The script will just help patch helm annotations for you, you can also do that manually one by one like:

kubectl patch -n vela-system workflowstepdefinition <item> --type=merge -p '{"metadata":{"annotations":{"meta.helm.sh/release-name":"kubevela","meta.helm.sh/release-namespace":"vela-system"},"labels":{"app.kubernetes.io/managed-by":"Helm"}}}'
kubectl patch -n vela-system configMap <item> --type=merge -p '{"metadata":{"annotations":{"meta.helm.sh/release-name":"kubevela","meta.helm.sh/release-namespace":"vela-system"},"labels":{"app.kubernetes.io/managed-by":"Helm"}}}'

Then you can upgrade the helm chart now:

helm repo add kubevela https://charts.kubevela.net/core
helm repo update
helm upgrade -n vela-system --install kubevela kubevela/vela-core --version 1.7.0-beta.1 --wait

3. Download the new CLI and enable velaux

curl -fsSl https://kubevela.io/script/install.sh | bash -s 1.7.0-beta.1
vela addon enable velaux

Upgrade VelaUX

vela addon upgrade velaux --version=v1.7.0-beta.1

New Contributors

• @aimuz made their first contribution in #5262

Full Changelog: v1.7.0-alpha.3...v1.7.0-beta.1

v1.7.0-alpha.3

What's Changed

• Fix: add permission for release ci by @Somefive in #5245
• Feat: versioned the context backend values to the app revision by @barnettZQG in #5231
• Fix: dry run from revision application patch error by @LiuFang07 in #5246
• Fix: apply label to pod for vela-cli workflow step definition. Fixes #5247 by @jamesdobson in #5248
• Docs: correct update project user api's doc description by @william302 in #5244
• Feat: add trait to support HorizontalPodAutoscaler of CPU/MEM/CustomMetrics by @StevenLeiZhang in #5225
• Test: prevent notification step definition test from failing when re-run. by @jamesdobson in #5253
• Feat: Detect the correctness of the custom addon repository when adding add… by @suwliang3 in #5221
• Feat: enhance the workflow restful APIs by @barnettZQG in #5252

How to install

Install Vela Core by Using Vela CLI

curl -fsSl https://kubevela.io/script/install.sh | bash -s 1.7.0-alpha.3
vela install -v 1.7.0-alpha.3

Install Vela Core by Using Helm:

helm repo add kubevela https://charts.kubevela.net/core
helm repo update
helm install --create-namespace -n vela-system kubevela kubevela/vela-core --version 1.7.0-alpha.3 --wait

⚠️ Please upgrade the CRD first if you're upgrading to this release.

New Contributors

• @jamesdobson made their first contribution in #5248
• @william302 made their first contribution in #5244

Full Changelog: v1.7.0-alpha.2...v1.7.0-alpha.3

v1.6.6

What's Changed

• [Backport release-1.6] Feat: rollout support statefulsets by @github-actions in #5203
• [Backport release-1.6] Fix: addon ls command does not show the componentless application by @github-actions in #5204
• [Backport release-1.6] Fix: remove useless field when loading pod in top by @github-actions in #5230
• [Backport release-1.6] Fix: gc failure cause workflow restart not working properly by @Somefive in #5242
• [Backport release-1.6] Fix: dry run from revision application patch error by @github-actions in #5250
• Chore: update workflow vendor to fix Workflow status bug caused by invalid inputs by @FogDong in #5254

How to install

Install Vela Core by Using Vela CLI

curl -fsSl https://kubevela.io/script/install.sh | bash -s 1.6.6
vela install -v 1.6.6

Install Vela Core by Using Helm:

helm repo add kubevela https://charts.kubevela.net/core
helm repo update
helm install --create-namespace -n vela-system kubevela kubevela/vela-core --version 1.6.6 --wait

Install VelaUX addon

vela addon enable velaux --version=v1.6.6

How to upgrade from old version?

Refer to the docs( https://kubevela.net/docs/platform-engineers/system-operation/migration-from-old-version ) if you're migrating from older versions.

Upgrade by using Vela CLI

The install command will also handle the upgrade automatically：

curl -fsSl https://kubevela.io/script/install.sh | bash -s 1.6.6
vela install -v 1.6.6 -r

Upgrade by using Helm

1. Upgrade the CRDs, please make sure you upgrade the CRDs first before upgrade the helm chart.

kubectl apply -f https://raw.githubusercontent.com/oam-dev/kubevela/release-1.6/charts/vela-core/crds/core.oam.dev_applicationrevisions.yaml
kubectl apply -f https://raw.githubusercontent.com/oam-dev/kubevela/release-1.6/charts/vela-core/crds/core.oam.dev_applications.yaml
kubectl apply -f https://raw.githubusercontent.com/oam-dev/kubevela/release-1.6/charts/vela-core/crds/core.oam.dev_resourcetrackers.yaml
kubectl apply -f https://raw.githubusercontent.com/oam-dev/kubevela/release-1.6/charts/vela-core/crds/core.oam.dev_componentdefinitions.yaml
kubectl apply -f https://raw.githubusercontent.com/oam-dev/kubevela/release-1.6/charts/vela-core/crds/core.oam.dev_definitionrevisions.yaml

2. Upgrade your kubevela chart

helm repo add kubevela https://charts.kubevela.net/core
helm repo update
helm upgrade -n vela-system --install kubevela kubevela/vela-core --version 1.6.6 --wait

3. Download the new CLI and enable velaux

curl -fsSl https://kubevela.io/script/install.sh | bash -s 1.6.6
vela addon enable velaux

Upgrade VelaUX

vela addon upgrade velaux --version=v1.6.6

Full Changelog: v1.6.5...v1.6.6

v1.5.10

What's Changed

• [Backport release-1.5] Fix: dry run from revision application patch error by @github-actions in #5249
• [Backport release-1.5] Fix: gc failure cause workflow restart not working properly by @Somefive in #5243

Full Changelog: v1.5.9...v1.5.10

v1.4.14

What's Changed

• [Backport release-1.4] Chore: change the package name of the readme-generator-for-helm by @github-actions in #4895
• [Backport release-1.4] Fix: gc failure cause workflow restart not working properly by @Somefive in #5241

Full Changelog: v1.4.13...v1.4.14

v1.7.0-alpha.2

New Features

• Feat: support data-passing in deploy step by @chivalryq in #5161
• Feat: Support SSH for retrieving terraform modules in private git repo by @motilayo in #5059

Bug Fixes & Enhancement

• Fix: optimize build push image step by @FogDong in #5215
• Chore: enhance workflow with specific git commit id by @wonderflow in #5220
• Feat: the webservice component has no args parameter #5226 by @xingming01 in #5227
• Fix: remove useless field when loading pod in top by @chivalryq in #5228
• Feat: add prestart-hook for vela-core and implement the apprev crd guard check by @Somefive in #5232
• Chore: update workflow version to add restart from step and fix bugs by @FogDong in #5233
• Fix: remove cluster field from pod view in vela top and optimize some ui by @Hanmengnan in #5237
• Fix: gc failure cause workflow restart not working properly by @Somefive in #5240

Code Style & Library Updates

• Fix: pin dependencies to hash by @chivalryq in #5223
• Fix: dependency makefile variable error by @chivalryq in #5234
• Feat: upgrade dependency by @Somefive in #5217
• Chore(deps): Bump github.com/containerd/containerd from 1.6.6 to 1.6.12 by @dependabot in #5235
• Chore: cleanup ioutil for newer go version by @my-git9 in #5238

New Contributors

• @motilayo made their first contribution in #5059
• @xingming01 made their first contribution in #5227
• @my-git9 made their first contribution in #5238

Full Changelog: v1.7.0-alpha.1...v1.7.0-alpha.2

v1.7.0-alpha.1

Highligh Features

Command Vela Adopt

Adopt resources into a KubeVela application. This command is useful when you already have resources applied in your Kubernetes cluster. These resources could be applied natively or with other tools, such as Helm. This command will automatically find out the resources to be adopted and assemble them into a new application which won't trigger any damage such as restart on the adoption.

There are two types of adoption supported by far, native Kubernetes resources (by default) and helm releases.

1. For native type, you can specify a list of resources you want to adopt in the application. Only resources in local cluster are supported for now.
2. For helm type, you can specify a helm release name. This helm release should be already published in the local cluster. The command will find the resources managed by the helm release and convert them into an adoption application.

There are two working mechanism (called modes here) for the adoption by far, read-only mode (by default) and take-over mode.

1. In read-only mode, adopted resources will not be touched. You can leverage vela tools (like Vela CLI or VelaUX) to observe those resources and attach traits to add new capabilities. The adopted resources will not be recycled or updated. This mode is recommended if you still want to keep using other tools to manage resources updates or deletion, like Helm.
2. In take-over mode, adopted resources are completely managed by application which means they can be modified. You can use traits or directly modify the component to make edits to those resources. This mode can be helpful if you want to migrate existing resources into KubeVela system and let KubeVela to handle the life-cycle of target resources.

Related Pull Requests:

• Feat: takeover & readonly policy by @Somefive in #5102
• Feat: vela adopt command by @Somefive in #5197
• Feat: gc orphan resources by @Somefive in #4847

5-10x scale up for applications capacity and performance

In this release, we optimized the default chart value for better performance:

Noteable Changes

• applicationRevisionLimit changes from 10 to 2, by default it will reserve only 2 app revisions instead of 10, which mean you don't have many revisions as options for rolling back. If you want to keep the value, you can specify by:

  helm upgrade --set applicationRevisionLimit=10
  

• optimize.disableComponentRevision by default, we'll turn off component revision, it will affect users who use the older rollout addon, users who're using kruise-rollout won't be affected. If you still want to use it, please specify the paramter when installing/upgrading.

  helm upgrade --set optimize.disableComponentRevision=false
  

Other Changes

• definitionRevisionLimit changes from 20 to 2, by default it will reserve only 2 revisions for each definitions instead of 10.
• featureGates.zstdResourceTracker by default, the controller will use zstd for resourceTracker compression.
• featureGates.zstdApplicationRevision by default, the controller will use zstd for applicationRevision compression.
• kubeClient.qps and kubeClient.burst changes to 100 and 200, double sized from older ones.
• enableFluxcdAddon deprecated as it's already widely used as being installed as addon.

• Feat: add support for compressing apprev using gzip and zstd by @charlie0129 in #5090
• Feat: optimize controller default value for better performance by @wonderflow in #5194

More Built-in Traits and Workflow Steps

• Feat: add topologySpreadConstraints traits by @jguionnet in #5081
• Feat: add built-in workflow step definitions by @FogDong in #5199
• Feat: Add startup probe trait by @jguionnet in #5093

Community

• Docs: add KEPs introduction to the main repo by @Somefive in #5099
• Fix: add fogdong to codeowners of packages by @Somefive in #5134

Enhancements

• Feat: vela top supports custom theme features by @Hanmengnan in #5180
• Feat: support NOTES.cue in addon for additional info printer by @wonderflow in #5195
• Feat: support fallback to kubeconfig namespace when env not set by @wonderflow in #5182
• Feat: return notFound error when deleting app by @suwliang3 in #5189
• Chore: add ossf/scorecard-action to secure workflows by @wonderflow in #5209
• Feat: support outputs objects for policy by @wonderflow in #5183

Deprecation

• Chore: remove legacy o11y logic by @chivalryq in #5046

How to install

Install Vela Core by Using Vela CLI

curl -fsSl https://kubevela.io/script/install.sh | bash -s 1.7.0-alpha.1
vela install -v 1.7.0-alpha.1

Install Vela Core by Using Helm:

helm repo add kubevela https://charts.kubevela.net/core
helm repo update
helm install --create-namespace -n vela-system kubevela kubevela/vela-core --version 1.7.0-alpha.1 --wait

⚠️ Please upgrade the CRD first if you're upgrading to this release.

New Contributors

• @tangoliu made their first contribution in #4944
• @lvyanru8200 made their first contribution in #5062
• @jguionnet made their first contribution in #5081
• @zhaohuiweixiao made their first contribution in #5143
• @suwliang3 made their first contribution in #5189

Full Changelog: v1.6.5...v1.7.0-alpha.1