Support registry http.relativeurls in harbor.yml #20339
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Support registry http.relativeurls in harbor.yml
Hi there, in this PR, I have attempted to resolve one of the issues we’ve been having with Harbor for a long time. After each upgrade, we have to manually set
http.relativeurls: true
incommon/config/registry/config.yml
because this setting doesn’t exist in the harbor.yml and it gets overwritten when the./install
script is executed.Setting relativeurls is essential for our kind of workflow and the absence of it causes
unknown blob
errors while pushing images.This issue has been fixed in harbor-helm here and in this PR, the relativeurls setting becomes available in harbor.yml.
Thank you for considering this change. If there are any suggestions or problems I need to address, I’m available.
Issue being fixed
Fixes #12135
Please indicate you've done the following: