-
Notifications
You must be signed in to change notification settings - Fork 40
flag to deploy to specific namespace #93
Comments
ping @kedgeproject/maintainers, are we good with the UX on this before we proceed? |
Yup. |
Do we want to scope specifying namespace using Btw, namespace can also be specified in the kedge spec for the application alternatively since it's a part of ObjectMeta. |
@containscafeine do we have ObjectMeta? I don't think we have? |
@surajssd totally missed that :) Yeah, so namespace cannot go in the spec the way it is right now. |
I don't have problem in doing it in |
I don't think namespace should be there for If you are deploying such artifacts you have to be extra careful to deploy it to the right namespace. |
I'd agree with @kadel that --namespace should be within create / delete rather than generate (makes no sense there) |
ack |
This commit allows running "create", "delete" and "apply" kedge subcommands with an optional "-n/--namespace" flag, which specifies the Kubernetes namespace to perform the given operation on. The ExecuteKubectl() function in pkg/cmd/kubernetes.go is refactored to accept multiple arguments to pass to "kubectl" instead of just one, as before. Fixes kedgeproject#93
This commit allows running "create", "delete" and "apply" kedge subcommands with an optional "-n/--namespace" flag, which specifies the Kubernetes namespace to perform the given operation on. The ExecuteKubectl() function in pkg/cmd/kubernetes.go is refactored to accept multiple arguments to pass to "kubectl" instead of just one, as before. Fixes kedgeproject#93
This commit allows running "create", "delete" and "apply" kedge subcommands with an optional "-n/--namespace" flag, which specifies the Kubernetes namespace to perform the given operation on. The ExecuteKubectl() function in pkg/cmd/kubernetes.go is refactored to accept multiple arguments to pass to "kubectl" instead of just one, as before. Fixes kedgeproject#93
This commit allows running "create", "delete" and "apply" kedge subcommands with an optional "-n/--namespace" flag, which specifies the Kubernetes namespace to perform the given operation on. The ExecuteKubectl() function in pkg/cmd/kubernetes.go is refactored to accept multiple arguments to pass to "kubectl" instead of just one, as before. Fixes kedgeproject#93
implement namespace specific cluster operations This commit allows running "create", "delete" and "apply" kedge subcommands with an optional "-n/--namespace" flag, which specifies the Kubernetes namespace to perform the given operation on. The ExecuteKubectl() function in pkg/cmd/kubernetes.go is refactored to accept multiple arguments to pass to "kubectl" instead of just one, as before. Fixes #93
Right now
kedge deploy
, deploys to the current namespace that is selected. But it would be awesome to have a flag that we can use to deploy to specific namespace.Something like following:
The text was updated successfully, but these errors were encountered: