-
Notifications
You must be signed in to change notification settings - Fork 206
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
Glossary project (M to Rancher E) #1332
base: main
Are you sure you want to change the base?
Conversation
I just closed #358 Glossary project #1125 but the info you might want there is now in the comments of the parent issue, Add a glossary of Rancher-specific terms |
<p> | ||
<b>Related terms:</b> <i>Neuvector</i> | ||
</p> |
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'm not sure if we should include Neuvector as a related term. If we do, we should define it as well, or at least link to an official page describing it.
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.
+1 on not mentioning a term as related unless we have a definition.
<ul> | ||
<li>rancher-privileged: The most permissive configuration. It doesn't restrict the behavior of any pods. This allows for known privilege escalations. This policy has no exemptions.</li> | ||
<li>rancher-restricted: A heavily restricted configuration that follows current best practices for hardening pods. You must make namespace-level exemptions for Rancher components.</li> | ||
</ul> |
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.
<ul> | |
<li>rancher-privileged: The most permissive configuration. It doesn't restrict the behavior of any pods. This allows for known privilege escalations. This policy has no exemptions.</li> | |
<li>rancher-restricted: A heavily restricted configuration that follows current best practices for hardening pods. You must make namespace-level exemptions for Rancher components.</li> | |
</ul> |
I feel like we don't need to list the levels here, just for brevity.
<dl> | ||
<dt> | ||
Machine Pool |
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.
We should define what a machine is first.
<p> | ||
<b>Related terms:</b> <i>Neuvector</i> | ||
</p> |
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.
+1 on not mentioning a term as related unless we have a definition.
The Rancher CLI (Command Line Interface) is a unified tool that you can use to interact with Rancher. With this tool, you can operate Rancher using a command line rather than the GUI. | ||
</dd> | ||
<dt> | ||
Rancher Enterprise |
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.
We currently don't use this to refer to the product and we have zero usage in our docs. We should remove it as a term and any references to it as a term.
Co-authored-by: Marty Hernandez Avedon <[email protected]>
Co-authored-by: Billy Tat <[email protected]>
Co-authored-by: Marty Hernandez Avedon <[email protected]>
Description
Define terms (M to Rancher E) listed in #358
Comments