[Bug]: virtualserver is not getting updated into R53

[jainpratik163]

Version

2.3.0

What Kubernetes platforms are you running on?

EKS Amazon

Steps to reproduce

we are trying to create ingress into common NS for Cross-namespace and follow documentation , vs and vsr created and there state are valid but still that host is not sync in R53.
when I try to nslookup host is not resolvable.

in order to resolve what extra we need to perform.

Our use case is we want to create an ingress which will be in a common namespace and need to route to diff applications which are in blue or green namespaces , how we can do this.

[github-actions]

Hi @jainpratik163 thanks for reporting!

Be sure to check out the docs and the Contributing Guidelines while you wait for a human to take a look at this 🙂

Cheers!

[AlexFenlon]

Hi @jainpratik163,

are you using NGINX Ingress controller or ingress-nginx?

If you are using NGINX Ingress Controller, I would recommend an upgrade to a newer version as v2.3.0 has reached end of support as of July 2024.

Are you using NGINX Ingress Controller with the external DNS integration?

[jainpratik163]

yes we are using NGINX Ingress Controller(nginx-plus-ingress) with the external DNS integration

[AlexFenlon]

@jainpratik163

Ah okay, please update to a newer version if are able to.

As you are using NGINX Ingress Controller with NGINX Plus, If you still are having issues after upgrading, please contact F5 Technical Support for assistance.

[jainpratik163]

We'll definitely upgrade, but we're curious about how ingress will be updated in R53, as the documentation doesn't mention it.

[AlexFenlon]

@jainpratik163

Understood, I will try look into this. Thank you for bringing this up. I will try clarify it.