-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Updated URL #4455
Updated URL #4455
Conversation
@siamaksade @tiwillia PTAL |
@ahardin-rh We might just not want to include a link here. There are several free-tier clusters, meaning there are several internal registries. The one linked is just one of those. |
@tiwillia Thanks! Updated with a replaceable instead. |
@ahardin-rh help me out here, whats a replaceable? Do we have a way to replace it with the right URL depending on which cluster the user is a part of? |
@tiwillia The example is just updated to not be specific (<registry_URL>), since the path can change. Would the user already know the URL, or would they have to look it up somewhere? If they have to look it up, we can provide guidance here as to how they can do that. |
@ahardin-rh I don't know of any other way to retrieve the registry URL. Users don't have access to list routes in the default namespace. It might actually make sense to have it somewhere within the web console on e.g. About page. Alternatively if registry URLs follow a pattern across online clusters, we could specify the pattern: We can document then that the |
@abhgupta and I yesterday discussed the possibility of adding this URL into the console Perhaps we can hold off on setting the URL in the docs and instead document the existence of the URL in the console, once its ready? |
@ahardin-rh @timothyh @siamaksade Here are my thoughts.
On point 3, the introduction of new free/paid tier clusters is not something that happens overnight. So, the docs team should be able to keep this section updated, if they choose to maintain the mapping in the docs. |
@abhgupta that sounds great. We can probably move this PR to complete # 2 in your list for now. |
@tiwillia @abhgupta @siamaksade Thanks! I updated the PR, satisfying # 2 on @abhgupta's list. Point # 3 Is something worth discussing with @aheslin |
LGTM 👍 |
No revision history needed |
Addresses #4454