extensions/v1beta1 for ingress deprecated but new api not found in models

[frederiksf]

The kubernetes documentation tells me the following ;

_The extensions/v1beta1 and networking.k8s.io/v1beta1 API versions of Ingress will no longer be served in v1.22.

Migrate manifests and API clients to use the networking.k8s.io/v1 API version, available since v1.19._

I have the models but i was not able to find the new models based on networking.k8s.io/v1. This is something not yet made and will come in the future or do i miss something? Methods i used;

body = client.ExtensionsV1beta1Ingress(
            api_version="extensions/v1beta1",
            kind="Ingress",
            metadata=client.V1ObjectMeta(name="blabla-tenant-ingress",
                                         annotations=annotations),
            spec=client.ExtensionsV1beta1IngressSpec(
                rules=rules
            ))

[roycaihw]

/assign @yliaog

[yliaog]

you're right, 1.19 has networking.k8s.io/v1, but python client library latest release is 1.18. the release for 1.19 will likely start next week. so check in a few weeks for the 1.19 release.

[OvervCW]

@yliaog Why is the Python library so far behind on the regular releases? Is it because of extensive testing, lack of contributors, ...?

[yliaog]

it is due to lack of contributors, help is welcome!

@yliaog Hello, when will version 1.19 be updated?

[yliaog]

it is in the works, i think it'll take a few weeks

[bateau84]

Any progress on this yet?

[yliaog]

/cc @roycaihw

[roycaihw]

v19.15.0a1 has been released. Please give it a try and file any issue you find. I plan to release a beta version in the next week or two.

[OvervCW]

it is due to lack of contributors, help is welcome!

What kind of work is involved besides rerunning a generator on the latest OpenAPI spec?

[yliaog]

please see https://github.com/kubernetes-client/python/blob/master/devel/release.md for the release process.

[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