[Bug]: existing virtualserver ip address is not updated, when using external-status-address

[chris8205]

Version

nginx: 5.1.0
chart: 2.2.1

What Kubernetes platforms are you running on?

Other

Steps to reproduce

1. create a virtualserver
2. the virtual server takes the ip from the service ex. 10.0.0.1
3. create a classic ingress the addess is filled with the same 10.0.0.1 from the service
4. override the config with creating "controller.config.extries" --> creaties a config map with entry external-status-address: 172.10.0.1
5. take a look at the ingress and virtualserver
   ingress is changed to 172.10.0.1
   virtual server is still on old entry 10.0.0.1
6. create a new virtualserver and look at the ip --> 172.10.0.1 is shown...

can you confirm this?

[github-actions]

Hi @chris8205 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!

[vepatel]

@chris8205 thanks for reporting, we'll triage and get back!

[hamelchRIT]

@vepatel hope it's quick to fix ;)
actually i can start on a greenfield, but in case of changing the ip we have to redeploy the virtualservers

or in other case maybe in "normal" mode; if the nginx service ip changes, the virtualserver is maybe also not updated... (not confirmed) but can try to proof...

edited:

so... i've done the proof....
if the service-ip changes, the virtualserver is updated properly so maybe i've a work-around for this moment...

[vepatel]

@chris8205 @hamelchRIT can confirm that this is an issue:

Status:
  External Endpoints:
    Ip:     <should_change>
    Ports:  [80,443]
  Message:  Configuration for default/webapp was added or updated 
  Reason:   AddedOrUpdated
  State:    Valid

issue is cosmetic and shouldn't affect the actual service but just the reporting of service ip to VS status field https://docs.nginx.com/nginx-ingress-controller/configuration/global-configuration/reporting-resources-status/

We'll work on a fix 👍🏼