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.

helm: upgrade to networking.k8s.io/v1 ingress

See original GitHub issue

Update Helm template files to fix the following warnings:

W0217 12:14:56.465497 1048297 warnings.go:67] extensions/v1beta1 Ingress is deprecated in v1.14+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress
W0217 12:14:56.849358 1048297 warnings.go:67] extensions/v1beta1 Ingress is deprecated in v1.14+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress

Perhaps also upgrade minimal Kubernetes version to 1.14 at the same time; currently, we declare:

kubeVersion: ">= 1.13.0-0 < 1.21.0-0"

Related PRs:

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:11 (6 by maintainers)

github_iconTop GitHub Comments

1reaction
tiborsimkocommented, Sep 22, 2021

@tiborsimko do we want to keep support for networking.k8s.io/v1beta1?

We don’t have to keep that support if we upgrade the declaration of the minimally-required Kubernetes version in the Helm charts…

1reaction
VMoiscommented, Sep 21, 2021
  1. In addition to ingress.yaml, we will need to upgrade traefik to version 10.0.0+ if we want to support Kubernetes 1.22+. Currently, traefik version is 1.85.x (very old, from obsolete Helm chart repo) and can support Kubernetes up to 1.21 (source). If we will upgrade to traefik 10.0+, we will not support Kubernetes =<1.15, which looks fine by me.
Read more comments on GitHub >

github_iconTop Results From Across the Web

Upgrading Kubernetes Ingresses from v1beta1 to v1 | by Paul ...
Here's an example of the Ingress shown above upgraded to v1: apiVersion: networking.k8s.io/v1 (a) kind: Ingress metadata: name: helloworld-ingress
Read more >
Code Issues Proposed changes - OpenDev
This change updates the helm-toolkit and ingress charts to migrate Ingress resources to the networking.k8s.io/v1 API version, available since v1.19.
Read more >
Issue actions - GitLab
Support setting Ingress APIVersion to networking.k8s.io/v1 to ... the newest available API version using Helm's Capabilities calculation.
Read more >
Upgrade Failled in Helm Upgrade stage - kubernetes
The script assumes that you want to change networking.k8s.io/v1beta1 to networking.k8s.io/v1. If you have a problem with another apiVersion, ...
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