-
Notifications
You must be signed in to change notification settings - Fork 3.3k
Missing an example in how to run a "apply -f" #1737
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
Comments
Adding server side apply doc |
I have submitted a PR adding additional examples for using utils.create_from_directory and utils.create_from_yaml. I believe this is some of the functionality that you are looking for an examples of. It will not be the full functionality of kubectl apply -f but it gives you a better example than what was previously up there. |
Thanks @RonMallory |
@roycaihw: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
I was looking at the examples in the PR Ron mentioned above #1752 and don't see any example of kubectl apply, only kubectl create. It appears to me this library doesn't actually support the apply operation. Is that true? |
We should support server-side apply: #1430 |
Link to the issue (please include a link to the specific documentation or example):
Most of the resources https://github.com/kubernetes-client, https://github.com/kubernetes-client/python/tree/master/examples are lacking one of the most needed examples: how to perform a
kubectl apply -f file.yaml
Description of the issue (please include outputs or screenshots if possible):
Currently it seems the API has examples for how to create and delete resources, and most of its examples are around connectivity. An example on the apply -f should be given, especially since these closed tickets should have not been closed at all as no solution was given:
#1215
#1168
The text was updated successfully, but these errors were encountered: