Archiving client-python repo due to lack of maintainers

[aburdenthehand]

What this PR does / why we need it:

/hold
to allow for kubevirt/client-python#61 to be merged

As per the linked PR:
We've had a few folks on the mailing list have troubles with this, since it has not been maintained in a while but is automatically updated, which gives the appearance of the repo still being supported.

We had previously put a call out for maintainers for this repo but did not receive enough volunteers.

Release note:

NONE

[kubevirt-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign aglitke for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[sourcery-ai]

Hey there - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[dhiller]

Hey, @aburdenthehand! Thanks for raising this - indeed I believe this should be archived. However, we need to remove the client-python update from the release process: https://github.com/kubevirt/kubevirt/blob/main/automation/release.sh#L40

FYI @xpivarc @fossedihelm

[fossedihelm]

Should we also remove the client generator?https://github.com/kubevirt/kubevirt/blob/654c1fd6aa0bb84bbc13fc6435adc01bada527d4/hack/gen-client-python/generate.sh ·

Edit:
in case we should also adjust project-infra https://github.com/search?q=org%3Akubevirt+%22make+client-python%22&type=code

[kubevirt-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.

/lifecycle stale

[kubevirt-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.

/lifecycle rotten

[kubevirt-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

[kubevirt-bot]

@kubevirt-bot: Closed this PR.

Details

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/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-sigs/prow repository.

[kubevirt-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close