Add a support to delete kubernetes API objects from yaml

[marukaz]

What is the feature and why do you need it:

There is already a util to create kubernetes API objects from yaml and it's very useful.
However, when I create an object from a yaml file, I sometimes want to delete the object created using that file, but there is no util for that.
I think it would be useful to have a util for delete that is paired with create_from_yaml.py, in other words, something like kubectl delete -f.

Describe the solution you'd like to see:

from kubernetes import utils, client

yaml_path = "path/to/yaml"
k8s_client = client.ApiClient()

utils.create_from_yaml(k8s_client, yaml_path)
utils.delete_with_yaml(k8s_client, yaml_path)

[adammrozik]

Hey! I was looking for similar functionality, but I guess if we do it, maybe we should generalize?
I see all that is happening inside the code is basically looking for a function called create_namespaced_{0}.

We could replace it with something like: {action}_namespaced_{resource} and have a function like:

utils.action_from_yaml(client, yaml_path, action='delete') # or 'patch', 'create' etc...

WDYT?

For now I just did copy these YAML functions and altered them like this in my own private repo

[roycaihw]

/assign

[roycaihw]

There is a PR already: #1197. It needs some rebase work to clean the changes up, but feel free to leave comments and suggestions there.

[adammrozik]

Great! What about patch from yaml or replace from Yaml? pon., 1 mar 2021, 20:40 użytkownik Haowei Cai (Roy) < [email protected]> napisał:

…

There is a PR already: #1197 <#1197>. It needs some rebase work to clean the changes up, but feel free to leave comments and suggestions there. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1373 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ARPF4NULFSPE2RKXOHUKDD3TBPUR3ANCNFSM4XGY6ILQ> .

[roycaihw]

We don't have in-progress work for those functionalities. I imagine patching/replacing could be significantly more difficult than creating/deleting, since you may want to parse yaml into an object and calculate diff against the existing object. You may want to consider using #989 for that.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten

[DiptoChakrabarty]

/remove-lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

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.