Somefive

Dry-run objects once could work. It could be a possible solution. But the side-effect is that the traffic of requests to apiserver will be doubled. We can reserve this solution...

There are multiple problems for this proposal. 1. By far, I still have questions for the scope of Kyverno Policy while applied into KubeVela application. From my view, the Kyversno...

Also, `vela policy` is confusing. KubeVela also uses the name of Policy, but not completely aligned with the "policy" in Kubernetes Policy Management. An alternative name is strongly recommended. P.S....

https://www.youtube.com/watch?v=9gSrRNmmKBc Gives some comparisons between OPA GateKeeper & Kyverno. Generally, Kyverno has more advantages over OPA GateKeeper 1. Examples are clearer. 2. Do not need additional "policy definition" for extra...

It is a bit weird. Is there any idea if there is any other things that would delete the SidecarSet? BTW, the StateKeep should be able to bring them back...

Could you check the ResourceTracker object and see if the desired object still exists in it?

This is currently a feature. Offline clusters could return back later. Therefore we could use `vela delete --force` command to solve this problem. There should be a more detailed mechanism...

> > the application can be deleted by `vela delete --force` > > We need to support this feature in VelaUX. Not agree to that. `vela delete --force` is a...

> @Somefive Another way to do this is to remove the offline cluster from the application configuration and publish it again. The offline cluster could be used by lots of...

In general, I agree this problem is crucial. In CLI, we previously work on `vela delete --force` to give a solution, which I believe, is not a final elegant solution....