kubevela/kubevela v1.4.0-beta.1

on GitHub

We're going to release v1.4.0 at the end of the month if no big issues in this release. Please have a try and give us feedbacks! Thanks!

What's Changed since v1.4.0-alpha.3

Highlight Features

Multi-cluster and Authorization

• Feat(auth): controller auto-impersonation with the using kubeconfig by @Somefive in #3906
• Feat(auth): vela auth gen-kubeconfig by @Somefive in #3911
• Feat(auth): vela auth list-privileges by @Somefive in #3923
• Feat(auth): vela auth grant-privileges by @Somefive in #3943 #3953
• Feat(multi-cluster): vela kube apply --cluster by @Somefive in #3931
• Feat(multi-cluster): vela kube delete by @Somefive in #3952

Enhanced Workflow

• Feat(workflow): support step group with substep in the workflow by @zq200618 and @FogDong in #3772 , #3956

Enhanced built-in components and traits

• Feat(terraform): support force delete Terraform typed application by @zzxwill in #3929
• Feat(component): webservice support healthProbe With https by @ivyilike in #3930
• Feat(trait): gateway trait support https protocol (#3832) by @oiar in #3925
• Feat(trait): make gateway trait's host field optional by @chivalryq in #3912

CLI Features

• Feat(cli): added the offline flag to the dry-run command by @YourTechBud in #3875
• Feat(cli): add more detailed output for vela addon status by @charlie0129 in #3876
• Feat(cli): create the definition for built-in policies to support display in vela CLI and UI by @ZhongsJie96 in #3894
• Feat(cli): get mapValue type name for definition show by @cuichenli in #2474

velaql and policy

• Feat(policy): extend apply-once to allow the specified path configuration to drift by @fourierr in #3899
• Feat(velaql): velaql provider for get application resource-tree by @wangyikewxgm in #3944
• Feat(velaql): support filter the resource by kind or apiVersion by @barnettZQG in #3901

Enhanced VelaUX

• Feat(velaux): change the default workflow step in velaux by using deploy type by @barnettZQG in #3878
• Feat(velaux): add the component name field for the trigger by @barnettZQG in #3884
• Feat(velaux): API of retrieving image registry secrets by image and its tag by @zzxwill in #3719
• Feat(velaux): Refactoring the API Server module for better layering by @barnettZQG in #3945
• Feat(velaux): support to configure the qps and burst by @barnettZQG in #3961 and @s4rd1nh4 in #3960

Deprecates

• Feat(chart): disable the automatic CRD conversion from v1alpha2 -> v1beta1 of application crd by @JarHMJ in #3890
• Chore: Deprecate oam-runtime which is no longer maintained, users should use kubevela instead by @wonderflow in #3958

Bugfixes

• Fix: Can not query the environments by an empty name list in cloud service application by @barnettZQG in #3893
• Fix: addon compare vela version failure by @StevenLeiZhang in #3928

How to install

Install Vela Core by Using Vela CLI

curl -fsSl https://kubevela.io/script/install.sh | bash -s 1.4.0-beta.1
vela install -v 1.4.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.4.0-beta.1 --wait

Install VelaUX addon

vela addon enable velaux

How to upgrade from old version?

Notice

Please note if you're using terraform addon, you should upgrade the terraform addon to version 1.0.6+ along with the vela-core upgrade, you can follow the following steps:

1. upgrading vela-core to v1.3.4+, all existing Terraform typed Applications won't be affected in this process.
2. upgrade the terrorform addon, or the newly provisioned Terraform typed Applications won't become successful.
   • 2.1 Manually upgrade CRD Configuration https://github.com/oam-dev/terraform-controller/blob/v0.4.3/chart/crds/terraform.core.oam.dev_configurations.yaml.
   • 2.2 Upgrade add-on terraform to version 1.0.6+.

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.4.0-beta.1
vela install -v 1.4.0-beta.1 -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.4/charts/vela-core/crds/core.oam.dev_applicationrevisions.yaml
kubectl apply -f https://raw.githubusercontent.com/oam-dev/kubevela/release-1.4/charts/vela-core/crds/core.oam.dev_applications.yaml
kubectl apply -f https://raw.githubusercontent.com/oam-dev/kubevela/release-1.4/charts/vela-core/crds/core.oam.dev_resourcetrackers.yaml
kubectl apply -f https://raw.githubusercontent.com/oam-dev/kubevela/release-1.4/charts/vela-core/crds/core.oam.dev_componentdefinitions.yaml
kubectl apply -f https://raw.githubusercontent.com/oam-dev/kubevela/release-1.4/charts/vela-core/crds/core.oam.dev_definitionrevisions.yaml

1. 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.4.0-beta.1 --wait

1. Download the new CLI and enable velaux

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

Upgrade VelaUX

VelaUX was not updated, the newest version is v1.3.4 and it's compatible with the beta version.

vela addon upgrade velaux --version 1.3.4

New Contributors

• @kethavathsivanaik made their first contribution in #3913
• @Hanmengnan made their first contribution in #3932
• @ivyilike made their first contribution in #3930
• @cuichenli made their first contribution in #2474
• @oiar made their first contribution in #3925
• @YourTechBud made their first contribution in #3875
• @zq200618 made their first contribution in #3772

Full Changelog: v1.4.0-alpha.3...1.4.0-beta.1