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
Installing the Harbor (+ Contour) supervisor service in a vSphere 8U2 + NSX + AVI setup according to the official documentation does not work correctly, since AKO is installed on the Supervisor. I deinstalled the Contour Supervisor service and tried to configure an Ingress object using AKO to access Harbor. I could reach the web portal but could not log into Harbor using the admin password I configured in the harbor-values.yaml file (Error message: wrong user or password). So either
the Harbor operator needs some changes to make this work and some additional documentation should be created to show how to configure it with AKO (using passthrough and non-passthrough mode).
or no changes are needed but then also some additional documentation should be created to show how to configure it with AKO (using passthrough and non-passthrough mode).
In any case customers should be able to use AVI out of the box with supervisor services.
The text was updated successfully, but these errors were encountered:
tschwaller
changed the title
Harbor supervisor service not working correctly in vsphere 8U2 + NSX + AVI setup
Harbor supervisor service not working correctly with vSphere 8.0U2 + NSX + AVI setup
Feb 15, 2024
Installing the Harbor (+ Contour) supervisor service in a vSphere 8U2 + NSX + AVI setup according to the official documentation does not work correctly, since AKO is installed on the Supervisor. I deinstalled the Contour Supervisor service and tried to configure an Ingress object using AKO to access Harbor. I could reach the web portal but could not log into Harbor using the admin password I configured in the harbor-values.yaml file (Error message: wrong user or password). So either
In any case customers should be able to use AVI out of the box with supervisor services.
The text was updated successfully, but these errors were encountered: