Discovery update of unmodified Upstreams when K8s service has changed

[bdecoste]

Version

1.13.x

Is your feature request related to a problem? Please describe.

A K8s service selector was modified and the corresponding discovered Upstream was not updated.

Describe the solution you'd like

Discovery should update discovered Upstreams when changes to the corresponding K8s service are detected if the Upstreams have not been modified. Possibly use kubectl.kubernetes.io/last-applied-configuration annotation or the discovered_by: kubernetesplugin label to determine if the resource has been changed since discovery.

Describe alternatives you've considered

Delete discovered Upstream to force re-discovery

Additional Context

No response

[github-actions]

This issue has been marked as stale because of no activity in the last 180 days. It will be closed in the next 180 days unless it is tagged "no stalebot" or other activity occurs.