Somefive

So if I'm understanding it correct, there is another one setting the context annotation to the workload? It is not very clear about the order of using these annotations. Is...

BTW, if you add context annotation to application, it looks more reasonable to me.

> * name: aidm-back > type: webservice > image: XXXXXXXXX > properties: > env: > - name: PP > values: SS Could you show a complete configuration for your application?...

@ixxeL2097 One of the key question is who deleted the associated resources? I haven't encountered similar problems before, but seems that in your case KubeVela created the resources and then...

I see. Seems this issue needs to be dealt with from the perspective of ArgoCD. Could you try add "argocd.argoproj.io/tracking-id" annotation to resources created by KubeVela application and see if...

@ixxeL2097 Well, if the annotation "argocd.argoproj.io/tracking-id" works, I guess it would be helpful if the abstraction of resources in KubeVela, like ComponentDefinition and TraitDefinition also adds the annotation to the...

Unlike helm, `vela addon enable` currently does not use --set for setting parameters for now. The parametrization is implemented through cue rendering process. Therefore, not all addons support parametrization by...

/cc @foursevenlove

For anyone who is interested in this issue, you can refer to https://hub.docker.com/r/oamdev/kubemark and https://github.com/kubevela/kubevela/tree/master/hack/pressure-test. P.S. The above doc might be a bit outdated.

We were doing the OwnerReference before v1.1. And we give up for doing that after v1.1 due to several reasons. 1. KubeVela application allows cross-namespace resource dispatch. While application itself...