-
Notifications
You must be signed in to change notification settings - Fork 74
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
Document how to work around unknown AWS regions in S3 driver #104
Comments
I think that such complex changes should be made only in the upstream, and we should get it with the next version (or backport of merged upstream PR). Otherwise we will endup with really complicate carry patch. |
Agree, but we may have to be the ones to submit the upstream PR. |
After investigation: If we send a PR that removes this check at the start, I'm pretty sure that such a change will be rejected. Also, this check is optional and it's happens only when the
|
So we should have provided that workaround to the user who recently hit this? Perhaps it's worth documenting here: https://docs.openshift.org/latest/install_config/registry/extended_registry_configuration.html#docker-registry-configuration-reference-storage ? That seems like a sufficient resolution to this issue. |
You tell me. I just follow the directions.
If you think that it's worth it, then we can. |
well it's largely moot now since the fix will be in their hands shortly and I think they found another workaround in the meantime. I was mostly asking if, in hindsight, you think this would have been a reasonable workaround for them if we'd known about it at the time. If the answer is yes, then I think it is worth documenting it so we don't forget about it the next time it comes up (e.g. when AWS introduces another new region). |
Yes. As a quick fix it should help, but in long term we should add new region and backport it to allow this check to work again. So in general for us nothing will change. |
yes, we're going to have to keep adding new regions as they show up. |
i've updated the title to reflect this is a documentation effort |
much like k8s has done, we (well the upstream s3 filesystem driver) should trust the region list from AWS instead of us hardcoding it:
kubernetes/kubernetes#38880
that way when new regions are introduced, we automatically support them.
@legionus @dmage any reason this is a bad idea or hard to do?
Edit: see comment #104 (comment) which summarizes why we can't easily do this and describes a workaround we should document for users that allows them to bypass this check entirely.
The text was updated successfully, but these errors were encountered: