You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We recently upgraded from harbor 2.1.3 to 2.3.3 and we observed that ingress got recreated due to a change in name of ingress.
this resulted in a change on IP on ingress and which caused the service disruption for over environment, since on over environment we are having a corporate firewall and this broke our entire harbor setup.
Request you either document these kinda breaking changes or possible not change the ingress setup or naming convention.
The text was updated successfully, but these errors were encountered:
Hello team,
We recently upgraded from harbor 2.1.3 to 2.3.3 and we observed that ingress got recreated due to a change in name of ingress.
this resulted in a change on IP on ingress and which caused the service disruption for over environment, since on over environment we are having a corporate firewall and this broke our entire harbor setup.
Request you either document these kinda breaking changes or possible not change the ingress setup or naming convention.
The text was updated successfully, but these errors were encountered: