vela dry-run fails when installing kubevela to non-vela-system namespace

[nuclearwu]

Describe the bug

'vela dry-run -f guestbook-app.yaml' error when installing kubevela to non-vela-system namespace, the error message is workloaddefinitions.core.oam.dev “k8s-objects” not found. but specifying namespace like this 'vela dry-run -f guestbook-app.yaml -n karmada-system' works well. So I wonder if this is a problem, In theory, no matter which namespace kubevela is installed in, it should know and find objects such as workloaddefinitions.core.oam.dev "k8s-objects" when executing vela dry-run.

To Reproduce

Expected behavior 'vela dry-run -f guestbook-app.yaml' executed successfully when installing kubevela to non-vela-system namespace

Screenshots

KubeVela Version 1.5.7

Cluster information 1.21.5

Additional context

[wonderflow]

Yes, currently the CLI will use vela-system as the system capability namespace, we should support to override it in some mechanism. In your case, we should support somthing such like:

export DefaultKubeVelaNS="karmada-system" vela dry-run -f guestbook-app.yaml

[nuclearwu]

Yes, currently the CLI will use vela-system as the system capability namespace, we should support to override it in some mechanism. In your case, we should support somthing such like:

export DefaultKubeVelaNS="karmada-system" vela dry-run -f guestbook-app.yaml

I was wondering if it is possible to import the environment variables of the default installation namespace when specifying a non-vela-system namespace to install vela-core, and then read the environment variables directly during vela dry-run, if the environment variables exist, use the environment variables as The default namespace, if it does not exist, the default vela-system namespace is used

[wonderflow]

yes, it's also one of the solutions. Vela-core already supports different namespace other than vela-system.

[pbxie]

After executing the command export DefaultKubeVelaNS="my-vela-system" vela addon list, there was no output.

[neteric]

After executing the command export DefaultKubeVelaNS="my-vela-system" vela addon list, there was no output.

+1

[TheGthr]

Instead of a variable, would it be more consistent with the vela install command to have a -n and/or --namespace flag for all the other commands?

[Jamel-jun]

Damn it, I installed it in another namespace and deleted my namespace directly. vela uninstall -nxx I'm a little shocked. Can anyone prove that I'm not alone. .