You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
And re-ran the same command, kubectl -n woot -R -f ./manifests --prune -l env=woot. To my surprise, however, the deployment wasn't removed; the only output from kubectl was namespace/woot unchanged.
What you expected to happen:
I expected the pruner to find the deployment with the matching label, env=woot, and prune it.
How to reproduce it (as minimally and precisely as possible):
I believe my example above is minimal and easily reproducible.
Anything else we need to know?:
This small change to the code for kubectl apply resolves the issue:
k8s-ci-robot
added
sig/cli
Categorizes an issue or PR as relevant to SIG CLI.
and removed
needs-sig
Indicates an issue or PR lacks a `sig/foo` label and requires one.
labels
Nov 15, 2019
What happened:
While testing out the
--prune
flag, I created a manifest with the following contents:I ran
kubectl -n woot -R -f ./manifests --prune -l env=woot
, and the resources appeared on my minikube cluster:Then, I removed the deployment from the manifest:
And re-ran the same command,
kubectl -n woot -R -f ./manifests --prune -l env=woot
. To my surprise, however, the deployment wasn't removed; the only output from kubectl wasnamespace/woot unchanged
.What you expected to happen:
I expected the pruner to find the deployment with the matching label,
env=woot
, and prune it.How to reproduce it (as minimally and precisely as possible):
I believe my example above is minimal and easily reproducible.
Anything else we need to know?:
This small change to the code for
kubectl apply
resolves the issue:Environment:
kubectl version
): v1.16.3cat /etc/os-release
): N/Auname -a
): N/AThe text was updated successfully, but these errors were encountered: