Currently, job deployment is assumed to be in the same namespace as the
targetted pod. When utilizing bpf tracing, for example, a privileged
pod may be required. In many situations, namespaces have security
restrictions preventing them from scheduling privileged pods.
This commit adds an optional argument target-namespace to allow
selecting pods from an unprivileged namespace.
I confirm that this contribution is made under the terms of the license found in the root directory of this repository's source tree and that I have the authority necessary to make this contribution on behalf of its copyright owner.
edeNFed
commented
2 years ago
Currently, job deployment is assumed to be in the same namespace as the targetted pod. When utilizing bpf tracing, for example, a privileged pod may be required. In many situations, namespaces have security restrictions preventing them from scheduling privileged pods.
This commit adds an optional argument
target-namespaceto allow selecting pods from an unprivileged namespace.I confirm that this contribution is made under the terms of the license found in the root directory of this repository's source tree and that I have the authority necessary to make this contribution on behalf of its copyright owner.