Closed jonsalvas closed 2 years ago
@jonsalvas Hi! I am glad that you find this plugin useful ❤️ !
Regarding to your question, the flag -n
represents the namespace of the target object(such as Service, Pod). I think we could add a new flag, like --server.namespace
, to override the current hard-coded default
namespace.
Nevertheless some required permissions must be granted to use this plugin. If you only want to forward traffic to a hostname, please make sure the following permissions is granted
rules:
- apiGroups:
- ""
resources:
- pods
- pods/portforward
verbs:
- create
- watch
- apiGroups:
- apps
resources:
- deployments
verbs:
- create
- get
- watch
@jonsalvas Hi! Please upgrade krelay
to the latest version v0.0.4
, and try out the following command:
kubectl relay --server.namespace mynamespace host/my.host.com 6333
First of all: Thanks for the awesome plugin, this is exactly what I need.
Unfortunately I am a bit stuck, because a `kubectl relay' seems to always create a deployment in the default namespace, for which I don't have access to. Is there a way to specify the target namespace somehow (-n is ignored)?
Command was:
Thanks!