-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixes #327: OCI Registry for use with path-based-routing #313
Fixes #327: OCI Registry for use with path-based-routing #313
Conversation
Can you add a description to this PR plus an issue as this is not clear for the reviewers to figure out what is the purpose of this PR ? Remark: PR should be rejected if they don't include an issue's link and/or description |
3eabbb8
to
3395b08
Compare
I agree, this is intentionally a quick draft PR to help with a need that @csantanapr had. I will create an issue and appropriate documentation before submitting the actual PR. |
3395b08
to
d622140
Compare
Signed-off-by: Jesse Sanford <[email protected]>
d622140
to
d101929
Compare
a0432df
to
d101929
Compare
Signed-off-by: Jesse Sanford <[email protected]>
4def81f
to
17ff7c2
Compare
Don't forget please to add the ticket and description |
Fixes #327 by setting up nginx rewrite rules on the ingress so that the generic OCI registry discovery urls can be found when using path based routing.