Web Ingress should be bumped to API version v1
bw-abrowne opened this issue · 0 comments
bw-abrowne commented
Describe the bug
web-ingress uses an api version which was removed in k8s v1.22. This should be updated in order to allow k8s compatibility >=1.22
Steps to reproduce the issue:
Can use kube-no-trouble to view this on a running cluster, which outputs:
❯ kubent
4:35PM INF >>> Kube No Trouble `kubent` <<<
4:35PM INF version 0.6.0 (git sha 126e47b9b45550a45404b599c546bf911ffae571)
4:35PM INF Initializing collectors and retrieving data
4:35PM INF Target K8s version is 1.21.14-eks-fb459a0
4:35PM INF Retrieved 66 resources from collector name=Cluster
4:35PM INF Retrieved 0 resources from collector name="Helm v2"
4:36PM INF Retrieved 72 resources from collector name="Helm v3"
4:36PM INF Loaded ruleset name=custom.rego.tmpl
4:36PM INF Loaded ruleset name=deprecated-1-16.rego
4:36PM INF Loaded ruleset name=deprecated-1-22.rego
4:36PM INF Loaded ruleset name=deprecated-1-25.rego
4:36PM INF Loaded ruleset name=deprecated-1-26.rego
4:36PM INF Loaded ruleset name=deprecated-future.rego
__________________________________________________________________________________________
>>> Deprecated APIs removed in 1.22 <<<
------------------------------------------------------------------------------------------
KIND NAMESPACE NAME API_VERSION REPLACE_WITH (SINCE)
Ingress cadence cadence-web networking.k8s.io/v1beta1 networking.k8s.io/v1 (1.19.0)
__________________________________________________________________________________________
>>> Deprecated APIs removed in 1.25 <<<
------------------------------------------------------------------------------------------
KIND NAMESPACE NAME API_VERSION REPLACE_WITH (SINCE)
PodSecurityPolicy <undefined> eks.privileged policy/v1beta1 <removed> (1.21.0)
Expected behavior
chart made compatible with k8s >= 1.22
Screenshots
n/a
Additional context
v1.22 changelog