-
Notifications
You must be signed in to change notification settings - Fork 38.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kubectl diff -Rf (recursive mode) does not work #71920
Comments
k8s-ci-robot
added
kind/bug
Categorizes issue or PR as related to a bug.
needs-sig
Indicates an issue or PR lacks a `sig/foo` label and requires one.
labels
Dec 10, 2018
/sig cli |
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
Dec 10, 2018
@apelisse I think the files are overwriting each other?
|
Yeah, good catch, I'll try to fix that asap |
Thanks! By the way, very nice work with dry-run and diff. I was waiting for this. |
@towolf Feel free to look at the PR and give your opinion! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened:
I get a diff, when I specify a file directly, but on recursive mode, no diff is shown anymore:
What you expected to happen:
Recursive mode should work
How to reproduce it (as minimally and precisely as possible):
Have a bunch of YAML manifest, but with name collisions, e.g. Service
heapster
, Deploymentheapster
, etcAnything else we need to know?:
I think the problem is that all objects have the same name, which should not be a problem per se.
Only heapster-binding has a different name, and looking at the generated temp files, only
heapster
andheapster-binding
are present:Environment:
kubectl version
):$ kubectl version --short
Client Version: v1.13.0
Server Version: v1.13.0
/kind bug
The text was updated successfully, but these errors were encountered: