ingress networking.k8s.io/v1beta1 is deprecated
See original GitHub issueChart 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:
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:
- Created 2 years ago
- Reactions:2
- Comments:9 (2 by maintainers)
Top GitHub Comments
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.
Right, I may do a PR if nobody from the team decides to fix themselves then 😃