Traits in KubeVela can be attached to Helm based component seamlessly.
Note: when use traits with Helm based component, please make sure the target workload in your Helm chart strictly follows the qualified-full-name convention in Helm. For example in this chart, the workload name is composed of release name and chart name.
This is because KubeVela relies on the name to discovery the workload, otherwise it cannot apply traits to the workload. KubeVela will generate a release name based on your
Applicationname and component name automatically, so you need to make sure never override the full name template in your Helm chart.
You may need to wait a few seconds to check the trait attached because of reconciliation interval.
scaler trait takes effect.
After the application is deployed and workloads/traits are created successfully, you can update the application, and corresponding changes will be applied to the workload instances.
Let's make several changes on the configuration of the sample application.
Apply the new configuration and check the results after several minutes.
Check the new values (
image.tag = 5.1.3) from application's
properties are assigned to the chart.
Under the hood, Helm makes an upgrade to the release (revision 1 => 2).
Let's have a try detach a trait from the application.
Apply the application and check
manualscalertrait has been deleted.