Ingress API is now GA with k8s 1.19 and no beta anymore

[bpereto]

What happened (please include outputs or screenshots):
kubernetes client model does not find "V1/Ingress"

What you expected to happen:
v1/ingress works on k8s 1.19

How to reproduce it (as minimally and precisely as possible):
Use/Testing with #989 against k8s 1.19:

Lookup info: {'group': 'Networking', 'version': 'v1', 'kind': 'ingress', 'items_kind': None, 'fcn_to_call': 'NetworkingV1Api', 'fnc_lookup': None}
Traceback (most recent call last):
  File "k8s-loader.py", line 35, in <module>
    o = utils.load_from_dict(data=obj, verbose=True)
  File "/home/beni/.local/lib/python3.8/site-packages/kubernetes/utils/deserialize.py", line 279, in load_from_dict
    raise FailToLoadError(load_exceptions)
kubernetes.utils.deserialize.FailToLoadError:  reason: Failed to find a function to inspect; lookup info: {'group': 'Networking', 'version': 'v1', 'kind': 'ingress', 'items_kind': None, 'fcn_to_call': 'NetworkingV1Api', 'fnc_lookup': None}

Anything else we need to know?:

Environment:

• Kubernetes version (kubectl version):

Server Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.3", GitCommit:"1e11e4a2108024935ecfcb2912226cedeafd99df", GitTreeState:"clean", BuildDate:"2020-10-14T12:41:49Z", GoVersion:"go1.15.2", Compiler:"gc", Platform:"linux/amd64"}

• OS (e.g., MacOS 10.13.6): Linux
• Python version (python --version) : Python 3.8.6
• Python client version (pip list | grep kubernetes) : kubernetes 10.0.0-snapshot
  testing with Adding utils.deserialize #989

[palnabarun]

Hi @bpereto 👋🏽, the Ingress API will be introduced to the client when client version v19.0.0 is released. Ref: #1320.

[palnabarun]

/assign

[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

[bpereto]

Released, right ? :)

[bpereto]

/remove-lifecycle stale

[bateau84]

Any action here?

[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

[jonkerj]

/remove-lifecycle stale

[OvervCW]

When will this be implemented? I'm using this library with a 1.20 cluster (which was released over 6 months ago) and it's warning about using deprecated APIs.

[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

[jonkerj]

/remove-lifecycle stale

[palnabarun]

#1584 will fix this. :)

[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

[bpereto]

#1584 is merged.
/close

[k8s-ci-robot]

@bpereto: Closing this issue.

In response to this:

#1584 is merged.
/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.