question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

ingress networking.k8s.io/v1beta1 is deprecated

See original GitHub issue

Chart version: 7.12.0

Kubernetes version: 1.19

Kubernetes provider: E.g. GKE (Google Kubernetes Engine) n/a

Helm Version: n/a

helm get release output n/a

e.g. helm get elasticsearch (replace elasticsearch with the name of your helm release)

Be careful to obfuscate every secrets (credentials, token, public IP, …) that could be visible in the output before copy-pasting.

If you find some secrets in plain text in helm get release output you should use Kubernetes Secrets to managed them is a secure way (see Security Example).

Output of helm get release

Describe the bug: As of kubernetes 1.19 networking.k8s.io/v1beta1 version of Ingress is deprecated and is to be removed in kubernetes 1.22

It should be upgraded to networking.k8s.io/v1

Deprecation details: https://kubernetes.io/docs/reference/using-api/deprecation-guide/#ingress-v122

Steps to reproduce:

  1. https://github.com/elastic/helm-charts/blob/b3a4b753a564811713f1a5ff04669baa3a4adfd7/elasticsearch/templates/ingress.yaml#L5-L6

Expected behavior:

Provide logs and/or server output (if relevant):

Be careful to obfuscate every secrets (credentials, token, public IP, …) that could be visible in the output before copy-pasting

Any additional context:

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Reactions:2
  • Comments:9 (2 by maintainers)

github_iconTop GitHub Comments

4reactions
ruckccommented, Aug 16, 2021

Bumping this again as kibana refuses to deploy on kubernetes 1.22, which was released 10 days ago.

The recommended way to define API versions in helm is something like this from kube-prometheus-stack. It detects the current Kubernetes version, and uses the best apiversion for it.

2reactions
zerkmscommented, Jul 11, 2021

Right, I may do a PR if nobody from the team decides to fix themselves then 😃

Read more comments on GitHub >

github_iconTop Results From Across the Web

Deprecated API Migration Guide - Kubernetes
The networking.k8s.io/v1beta1 API version of IngressClass is no longer served as of v1.22. Migrate manifests and API clients to use the ...
Read more >
Logs complaining "extensions/v1beta1 Ingress is deprecated"
Now that ingress is the only resource remaining in that group, and is deprecated and has a GA replacement, 1.20 will drop it...
Read more >
Kubernetes 1.22 deprecated APIs - Google Cloud
The Beta API versions ( extensions/v1beta1 and networking.k8s.io/v1beta1 ) of Ingress are no longer served for GKE clusters created on versions 1.22 and ......
Read more >
Upgrading Kubernetes Ingresses from v1beta1 to v1 | by Paul ...
With Kubernetes v1.19, v1beta1 Ingress objects have been deprecated, and support will be removed with Kubernetes v1.22. Those supporting Kubernetes ...
Read more >
Ingress v1 and v1beta1 Differences - v2.8.x | Kong Docs
This document covers those changes as they relate to Kubernetes Ingress Controller and provides sample equivalent networking.k8s.io/v1beta1 and ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found