Wrong resource configuration being displayed after updating ingress

[quintonthompson]

Describe the bug
I recently updated the ingress resources in our cluster to use apiVersion networking.k8s.io/v1. After applying the yaml file, it still shows the old manifest inside k9s. When running kubectl -n <namespace> get ingress <ingress name> -oyaml, it shows the correct version and modifications. It also shows the correct manifest inside GCP console.

To Reproduce
Steps to reproduce the behavior:

1. Have a ingress using extensions/v1beta1
2. Apply updated ingress that uses networking.k8s.io/v1
3. navigate to namespace where ingress is deployed via k9s
4. view yaml file via k9s
5. compare that to output of kubectl -n <namespace> get ingress <ingress name> -oyaml

Expected behavior
Expect k9s to match what is shown through kubectl

Screenshots
k9s:

kubectl:

GCP console:

Versions:

• OS: macOS Monterey
• K9s: v0.24.2
• K8s: v1.21.10-gke.2000

[VltraHeaven]

Hey @quintonthompson, does the correct ingress show up in k9s when you put in networking.k8s.io/v1/ingress instead of just ingress? If so, that might be a good workaround until a patch is merged in.

I'll try my hand at this one over the coming weeks and see what I can come up with.

[quintonthompson]

Hi, I have not tried that. But the issue was resolved when I updated k9s to version v0.25.18 via homebrew.

[derailed]

@quintonthompson Thank you all for weighting in! Fixed v0.25.19