add .readthedocs.yaml config file to fix docs pipeline

[aapjeisbaas]

What type of PR is this?

/kind documentation

What this PR does / why we need it:

Fix the broken read the docs build: https://readthedocs.org/projects/kubernetes/builds/

Special notes for your reviewer:

Build works on my branch and output looks the same but witt up to date readme:
https://app.readthedocs.org/projects/python-kubernetes-client/builds/25015241/

My other documentation questions:

1. Why is this not in the published docs:
   https://github.com/kubernetes-client/python/blob/master/kubernetes/README.md
   Yes the github interface works but a published version would be nicer to use.

2. Why are these pages empty:
   https://python-kubernetes-client.readthedocs.io/en/latest/kubernetes.client.models.v1_container.html

[k8s-ci-robot]

Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

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.

[k8s-ci-robot]

Welcome @aapjeisbaas!

It looks like this is your first PR to kubernetes-client/python 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-client/python has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[yliaog]

why are many lines commented out?

[aapjeisbaas]

I found those lines in the old working build runs and kept them for reference.
Maybe you’ve added something special that is now missing.
Having the comments with the commands there is just for checking this.

[roycaihw]

/assign @yliaog

[yliaog]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aapjeisbaas, yliaog

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [yliaog]

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

[k8s-triage-robot]

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

This bot triages 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 PR is closed

You can:

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

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

/lifecycle stale

[aapjeisbaas]

Pr has status approved why isn’t it being merged?
@roycaihw @yliaog