Migrate from kube.py to kubernetes.core.k8s* modules

[VannTen]

What would you like to be added:
Replace all usages of the custom kube module in kubespray with kubernetes.core.k8s / info / etc, then remove kube.py

Why is this needed:

• Less code to maintain.
• kubernetes.core.k8s* modules are more featureful (things like server-side apply for instances)
• In particular, kubernetes.core.k8s allow to supply a list of templates (rather than looping at the task-level), which would allow us to consolidate some of the manifests tasks and remove some Ansible overhead.

wdyt @yankay @MrFreezeex ?

Related: #10694

[MrFreezeex]

I don't think we had to do too much changes over time on kube.py, so I don't think that would be a huge priority but still a good thing nonetheless 👍

[mirwan]

Hi,
I once walked the same path with #3534 when I was (more) active on the project.
It brought 2 main drawbacks:

• System packages for k8s client are (at least they exist now for most of the distributions supported by Kubespray) way behind the latest k8s python client's version. Some of the distributions versions supported by Kubespray would require backports to handle latest k8s versions integrated in Kubespray or risking to face incompatibility between installed client and k8s version.
• Having Python clients deployed with pip on remote servers is seen as a security issue by secteams (...).

Another minor drawback is that kubernetes/preinstall role ensures every host in inventory is installed the same, adding k8s python client pkg would end up with a useless package on worker nodes

I think that, until deb/rpm packages catch up and remain up-to-date with k8S lifecycle, I agree with @MrFreezeex

My two cents

[VannTen]

In fact, I'll probably pursue the the "conversion to Helm charts" direction rather than using the k8s module this year. That was one of the potential points in #6400 (and other) and I think that's an easier path forward. But first I need to re-work that helm-apps role into a less awkward form ^.

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[VannTen]

/remove-lifecycle stale /lifecycle active /assign

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
• Close this issue 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.

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle rotten
• Close this issue 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 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 with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

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

This bot triages issues 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 with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close not-planned

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.