Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

K8s API deprecation breaks console ingress on k8s 1.22.x #7072

Open
RaananHadar opened this issue Nov 6, 2021 · 0 comments
Open

K8s API deprecation breaks console ingress on k8s 1.22.x #7072

RaananHadar opened this issue Nov 6, 2021 · 0 comments

Comments

@RaananHadar
Copy link
Contributor

What happened?:
I've attempted to install Pachyderm with console using Traefik via the official docs on an AKS with version 1.22.x (preview). It failed, downgrading to the default version of AKS (1.20.9 at time of writing) solves this (although forcing a downgrade their cluster isn't optimal and shouldn't work once 1.22.X becomes stable). This works with the following warning:

networking.k8s.io/v1beta1 Ingress is deprecated in v1.19+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress

What you expected to happen?:
Pachyderm should use the updated api in the helm chart to avoid deprecation.
How to reproduce it (as minimally and precisely as possible)?:
Attempt to deploy Pachyderm on AKS with Traefik.

Environment?:

  • Kubernetes version (use kubectl version): AKS 1.22.X
  • Pachyderm CLI and pachd server version (use pachctl version): 2.0.1
@RaananHadar RaananHadar added the bug label Nov 6, 2021
@RaananHadar RaananHadar changed the title Traefik deprecation breaks console ingress on k8s 1.22.x K8s API deprecation breaks console ingress on k8s 1.22.x Nov 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants