feat: controllers can access zot via https #116
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
frewilhelm
force-pushed
the
impl_artifacts
branch
3 times, most recently
from
2e78025 to
4b0a1ce
Compare
frewilhelm
force-pushed
the
impl_artifacts
branch
9 times, most recently
from
2a83a21 to
ce9492f
Compare
frewilhelm
force-pushed
the
impl_artifacts
branch
2 times, most recently
from
847f0e1 to
b0a18be
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Why is this a draft?
@frewilhelm and me decided to merge this change directly to
main, but only if #98 is merged first. I.e. waiting for #98 to be merged.What this PR does / why we need it
With this PR the in-cluster
zotregistry can also be accessed viahttps. I.e. thesnapshotartifacts can be pushed/fetched viahttps.Which issue(s) this PR fixes
This PR is related to #75