harbor
harbor copied to clipboard
EXT_ENDPOINT
Is EXT_ENDPOINT always set as system hostname in installation time or is it configurable somehow? Our external_url is set to the right url, but EXT_ENDPOINT in core env file seems to be set from system hostname.
What is your installation type? docker-compose or helm
After updated the external_url in harbor.yml, reinstallation or rerun./prepare --with-trivy
and restart Harbor are required.
What is your installation type? docker-compose or helm
After updated the external_url in harbor.yml, reinstallation or rerun
./prepare --with-trivy
and restart Harbor are required.
Thanks for your reply.
We use docker-compose installation and did absolutely as you described above, but EXT_ENDPOINT wasn't updated, that's why our oidc tests were redirecting us to a wrong url (https://<hostname>/<path>, e.g https://my-new-host-1/<path>). To resolve it we updated a hostname to a right fqdn and did installation again.
As far as i remember i double checked it, but will do additional tests this week
This issue is being marked stale due to a period of inactivity. If this issue is still relevant, please comment or remove the stale label. Otherwise, this issue will close in 30 days.
This issue was closed because it has been stalled for 30 days with no activity. If this issue is still relevant, please re-open a new issue.