kubectl

If a plugin's windows platform spec specifies something like bin: foo, we:

1. copy the executable to plugin's installation dir as foo
2. but we symlink it as kubectl-foo.exe on windows.

I am not at all sure that kubectl-foo.exe which points to foo (that has no .exe extension) can be executed. Can someone verify if this works or not?

Depending on that, (1) we need to make sure i

At the moment of writing this issue, kubectl trace only supports X86-64 as target architecture.

The tool should be able to schedule bpftrace programs against all the architectures supported by bpftrace, that are X86-64 and arm64 (aarch64) see the Cmake definition.

To achieve that we n

Is your feature request related to a problem?

if you configure a target-namespace for the k3s resources, you would expect isolation mode to restrict resources in that target-namespace. Instead it isolates the namespace which runs the k3s master node.

Which solution do you suggest?

either it automatically uses the "target-namespace" or you can specify the namespace in the isolation block

We have a small number of e2e tests for kpt live (outside of the bash-based approach). They currently run in serial and requires that a new cluster is created for several of the tests. This causes them to be very slow.

We should improve this by:

• Reduce the number of times we need to create a new kind cluster, as this takes ~1 minute. Tests should clean up after themselves and we can handle