-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Added a note to installation modules. #21554
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
Conversation
The preview will be available shortly at: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/always/also
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggest same change in the Helm module too.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the placement is good. The other option is to add it to the end of the section. But I think the current option tells users that this section has CLI instructions, but if he wants to use the console he can access it before reading all of the CLI instructions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggest: The following...different platforms using the CLI.
modules/helm-installing-helm.adoc
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggest adding an intro line here similar to that in odo: The following section describes how to install Helm on different platforms using the CLI.
Suggest adding the note before the prerequisite section, immediately after the above intro line.
/lgtm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just two comments
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's up to you, but to me, it feels like this warning about not being able to use odo in a restricted env belongs in the NOTE. And then the additional info about finding the binaries in the web console belongs in normal text below the NOTE.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Suggest simplifying to something like "You can also download the latest binaries from the {product-title} web console." Or even combining into "You can also download the latest binaries from the {product-title} web console by clicking the ? icon in the upper-right corner and select Command Line Tools."
- Use a comma instead of a semicolon in the second sentence.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can't really download them this way. Clicking the ? icon in the upper-right corner and selecting Command Line Tools will lead user to the page with titles and URLs of different CLI tools' folders on the file server (odo, helm etc). And there, on the file server, they can download the actual binary file.
Otherwise, good call, thank you! I've shortened the sentence and included it as a part of introduction in both modules.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fair enough!
New changes are detected. LGTM label has been removed. |
@bergerhoffer I completely forgot about this PR! Could you merge please if everything's okay? |
Sure thing @boczkowska, merging! Just FYI this will go into both 4.5 and 4.4 now. |
/cherrypick enterprise-4.5 |
/cherrypick enterprise-4.4 |
@bergerhoffer: new pull request created: #21858 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@bergerhoffer: new pull request created: #21859 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Branch 4.4