-
Notifications
You must be signed in to change notification settings - Fork 39.9k
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 should process files recursively when given a directory #19767
Labels
area/app-lifecycle
area/kubectl
priority/backlog
Higher priority than priority/awaiting-more-evidence.
Comments
ghodss
changed the title
kubectl apply should work recursively when given a directory
kubectl apply should apply files recursively when given a directory
Jan 17, 2016
alex-mohr
added
the
sig/api-machinery
Categorizes an issue or PR as relevant to SIG API Machinery.
label
Jan 21, 2016
bgrant0607
added
priority/backlog
Higher priority than priority/awaiting-more-evidence.
area/app-lifecycle
area/kubectl
team/ux
and removed
sig/api-machinery
Categorizes an issue or PR as relevant to SIG API Machinery.
labels
Jan 22, 2016
We should do the same for all commands, not just apply. (That is, we should be consistent.) cc @kubernetes/kubectl |
Since this isn't the current behavior, we'll need to make it optional via a flag. |
bgrant0607
changed the title
kubectl apply should apply files recursively when given a directory
kubectl should process files recursively when given a directory
Jan 29, 2016
This was referenced Mar 17, 2016
k8s-github-robot
pushed a commit
that referenced
this issue
Mar 30, 2016
Automatic merge from submit-queue allow kubectl cmds to process files recursively, when given a dir This PR accomplishes two things: 1. It creates a `--recursive` flag for use with certain `kubectl` commands that _currently_ do not process files beyond their first level of children, as seen in the issue #19767 2. It enables the ability to use the `--recursive` flag in the `kubectl` commands that currently _only_ support processing a directory up to its first level of children.
This issue has been resolved by this set of PR's:
It can be closed |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/app-lifecycle
area/kubectl
priority/backlog
Higher priority than priority/awaiting-more-evidence.
When given a directory,
kubectl apply -f <directory>
should search a directory recursively for any JSON|YAML files when given a directory. Currently it only finds the immediate children of the given directory.I believe kubectl apply is exhibiting the same behavior as
kubectl create
,kubectl delete
, etc., but to enable the original #1702 use case of a nested directory of configuration objects being reconciled with the server's state, kubectl apply especially should act recursively.Current behavior:
Expected behavior:
The text was updated successfully, but these errors were encountered: