public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-09-26 13:08:11 +00:00
Code Issues Packages Projects Releases Wiki Activity

Copy edit in preparation for versioning the docs

Browse Source
This commit is contained in:
Catherine Luse
2021-01-12 05:28:16 -07:00
parent 1fe5b4213c
commit 2a8f22212a
107 changed files with 2453 additions and 1866 deletions
Download Patch File Download Diff File Expand all files Collapse all files
layouts/shortcodes/beta-note_azure.html
-4
View File
@@ -1,4 +0,0 @@
<blockquote>
<strong>Note:</strong>
<p>As of Rancher v2.0 GA, the Azure Kubernetes Service option is still in beta.</p>
</blockquote>
layouts/shortcodes/note_server-tags.html
-8
View File
@@ -1,8 +0,0 @@
<blockquote>
<p><strong>Notes:</strong></p>
<ul>
<li>If you are using RancherOS, make sure you switch the Docker engine to a supported version using <code>sudo ros engine switch docker-17.03.2-ce</code>
</li>
<li>The <code>rancher/rancher</code> container is hosted on <a href="https://hub.docker.com/r/rancher/rancher/tags/">DockerHub</a>. If you don't have access to DockerHub, or you are installing Rancher without an Internet connection, refer to how to prepare for an <a href="/docs/rancher/v2.x/en/installation/air-gap-installation/">Air Gap Installation</a>.</li>
</ul>
</blockquote>
layouts/shortcodes/ports-rancher-nodes.html
-55
View File
@@ -1,55 +0,0 @@
<table>
<thead>
<tr>
<th>Protocol</th>
<th>Port</th>
<th>Source</th>
<th>Destination</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td>TCP</td>
<td>80</td>
<td>Load Balancer / Reverse Proxy</td>
<td></td>
<td>HTTP traffic to Rancher UI / API.</td>
</tr>
<tr>
<td>TCP</td>
<td>443</td>
<td>Load Balancer / Reverse Proxy<br><br>Otherwise IPs of all cluster nodes and other Rancher API / UI clients.</td>
<td></td>
<td>HTTPS traffic to Rancher UI / API.</td>
</tr>
<tr>
<td>TCP</td>
<td>443</td>
<td></td>
<td>35.160.43.145<br>35.167.242.46<br>52.33.59.17</td>
<td>Rancher catalog (git.rancher.io).</td>
</tr>
<tr>
<td>TCP</td>
<td>22</td>
<td></td>
<td>Any node created using node driver.</td>
<td>SSH provisioning of node by node driver.</td>
</tr>
<tr>
<td>TCP</td>
<td>2376</td>
<td></td>
<td>Any node created using node driver.</td>
<td>Docker daemon TLS port used by node driver.</td>
</tr>
<tr>
<td>TCP</td>
<td>Provider Dependent</td>
<td></td>
<td>Port of the Kubernetes API endpoint in hosted clusters.</td>
<td>Kubernetes API.</td>
</tr>
</tbody>
</table>
layouts/shortcodes/ports_aws_securitygroup_nodedriver.html
-103
View File
@@ -1,103 +0,0 @@
<h3 id="amazonec2-securitygroup-nodedriver">Amazon EC2 security group when using Node Driver</h3>
<p>If you are <a href="/docs/rancher/v2.x/en/cluster-provisioning/rke-clusters/node-pools/ec2/">Creating an Amazon EC2 Cluster</a>, you can choose to let Rancher create a Security Group called <code>rancher-nodes</code>. The following rules are automatically added to this Security Group.
</p>
<div>
<p><strong>Security group: rancher-nodes</strong></p>
<h4>Inbound rules</h4>
<table>
<tr>
<th>Type</th>
<th>Protocol</th>
<th align="left">Port Range</th>
<th align="left">Source</th>
</tr>
<tr>
<td>SSH</td>
<td>TCP</td>
<td>22</td>
<td>0.0.0.0/0</td>
</tr>
<tr>
<td>HTTP</td>
<td>TCP</td>
<td>80</td>
<td>0.0.0.0/0</td>
</tr>
<tr>
<td>Custom TCP Rule</td>
<td>TCP</td>
<td>443</td>
<td>0.0.0.0/0</td>
</tr>
<tr>
<td>Custom TCP Rule</td>
<td>TCP</td>
<td>2376</td>
<td>0.0.0.0/0</td>
</tr>
<tr>
<td>Custom TCP Rule</td>
<td>TCP</td>
<td>2379-2380</td>
<td>sg-xxx (rancher-nodes)</td>
</tr>
<tr>
<td>Custom UDP Rule</td>
<td>UDP</td>
<td>4789</td>
<td>sg-xxx (rancher-nodes)</td>
</tr>
<tr>
<td>Custom TCP Rule</td>
<td>TCP</td>
<td>6443</td>
<td>0.0.0.0/0</td>
</tr>
<tr>
<td>Custom UDP Rule</td>
<td>UDP</td>
<td>8472</td>
<td>sg-xxx (rancher-nodes)</td>
</tr>
<tr>
<td>Custom TCP Rule</td>
<td>TCP</td>
<td>10250-10252</td>
<td>sg-xxx (rancher-nodes)</td>
</tr>
<tr>
<td>Custom TCP Rule</td>
<td>TCP</td>
<td>10256</td>
<td>sg-xxx (rancher-nodes)</td>
</tr>
<tr>
<td>Custom TCP Rule</td>
<td>TCP</td>
<td>30000-32767</td>
<td>0.0.0.0/0</td>
</tr>
<tr>
<td>Custom UDP Rule</td>
<td>UDP</td>
<td>30000-32767</td>
<td>0.0.0.0/0</td>
</tr>
</table>
<h4>Outbound rules</h4>
<table>
<tr>
<th>Type</th>
<th>Protocol</th>
<th align="left">Port Range</th>
<th align="left">Destination</th>
</tr>
<tr>
<td>All traffic</td>
<td>All</td>
<td>All</td>
<td>0.0.0.0/0</td>
</tr>
</table>
<br/>
</div>
layouts/shortcodes/prereq_cluster.html
-5
View File
@@ -1,5 +0,0 @@
<blockquote>
<p>
<strong>Prerequisites:</strong> Review the <a href="../../content/rancher/installation/requirements">Requirements</a> for your Linux host.
</p>
</blockquote>
layouts/shortcodes/prereq_install.html
-4
View File
@@ -1,4 +0,0 @@
<div>
<h2>Before You Start</h2>
<p>Provision a Linux host according to our <a href="../../content/rancher/installation/requirements">Requirements</a>.</p>
</div>
layouts/shortcodes/product.html
-1
View File
@@ -1 +0,0 @@
<span>Rancher</span>
layouts/shortcodes/requirements_ha.html
-11
View File
@@ -1,11 +0,0 @@
<div>
<ul>
<li>RKE Cluster</li>
<ul>
<li>3 nodes total minimum</li>
<li>3+ nodes for etcd role</li>
<li>2+ nodes for controlplane role</li>
<li>1+ node for worker role</li>
</ul>
</ul>
</div>
layouts/shortcodes/requirements_os.html
-7
View File
@@ -1,7 +0,0 @@
<div>
<ul>
<li>Ubuntu 16.04 (64-bit)</li>
<li>Red Hat Enterprise Linux 7.5 (64-bit)</li>
<li>RancherOS 1.4 (64-bit)</li>
</ul>
</div>
layouts/shortcodes/result_create-cluster.html
-8
View File
@@ -1,8 +0,0 @@
<div>
<p><strong>Result:</strong></p>
<ul>
<li>Your cluster is created and assigned a state of <strong>Provisioning</strong>. Rancher is standing up your cluster.</li>
<li>You can access your cluster after its state is updated to <strong>Active</strong>.</li>
<li><strong>Active</strong> clusters are assigned two Projects, <code>Default</code> (containing the namespace <code>default</code>) and <code>System</code> (containing the namespaces <code>cattle-system</code>,<code>ingress-nginx</code>,<code>kube-public</code> and <code>kube-system</code>, if present).
</ul>
</div>
layouts/shortcodes/step_create-cluster_cluster-options.html
-1
View File
@@ -1 +0,0 @@
<div><p>Use <strong>Cluster Options</strong> to choose the version of Kubernetes, what network provider will be used and if you want to enable project network isolation. To see more cluster options, click on <strong>Show advanced options</strong>.
layouts/shortcodes/step_create-cluster_member-roles.html
-8
View File
@@ -1,8 +0,0 @@
<div>
<p>Use <strong>Member Roles</strong> to configure user authorization for the cluster.</p>
<ul>
<li>Click <strong>Add Member</strong> to add users that can access the cluster.</li>
<li>Use the <strong>Role</strong> drop-down to set permissions for each user.</li>
</ul>
<br/>
</div>
layouts/shortcodes/step_create-cluster_node-pools.html
-9
View File
@@ -1,9 +0,0 @@
<p>Add one or more <strong>node pools</strong> to your cluster.<br/><br/>A <strong>node pool</strong> is a collection of nodes based on a node template. A node template defines the configuration of a node, like what operating system to use, number of CPUs and amount of memory. Each node pool must have one or more nodes roles assigned.</p>
<blockquote>
<p><strong>Notes:</strong></p>
<ul>
<li>Each node role (i.e. <code>etcd</code>, <code>Control Plane</code>, and <code>Worker</code>) should be assigned to a distinct node pool. Although it is possible to assign multiple node roles to a node pool, this should not be done for production clusters. </li>
<li>The recommended setup is to have a node pool with the <code>etcd</code> node role and a count of three, a node pool with the <code>Control Plane</code> node role and a count of at least two, and a node pool with the <code>Worker</code> node role and a count of at least two. Regarding the <code>etcd</code> node role, refer to the <a href="https://coreos.com/etcd/docs/latest/v2/admin_guide.html#optimal-cluster-size" target="_blank">etcd Admin Guide</a>.</li>
</ul>
</blockquote>
layouts/shortcodes/step_rancher-template.html
-24
View File
@@ -1,24 +0,0 @@
<p>The <a href="https://docs.docker.com/engine/docker-overview/#the-docker-daemon">Docker daemon</a> configuration options include:</p>
<ul>
<li>
<p>
<strong>Labels:</strong> For information on labels, refer to the <a href="https://docs.docker.com/config/labels-custom-metadata/"> Docker
object label documentation.</a>
</p>
</li>
<li>
<p>
<strong>Docker Engine Install URL:</strong> Determines what Docker version will be installed on the instance. Note: If you are using RancherOS, please check what Docker versions are available using <code>sudo ros engine list</code> on the RancherOS version you want to use, as the default Docker version configured might not be available. If you experience issues installing Docker on other operating systems, please try to install Docker manually using the configured Docker Engine Install URL to troubleshoot.
</p>
</li>
<li>
<p>
<strong>Registry mirrors:</strong> Docker Registry mirror to be used by the Docker daemon
</p>
</li>
<li>
<p><strong>Other advanced options:</strong> <a href="https://docs.docker.com/engine/reference/commandline/dockerd/">Refer to the Docker daemon option reference
</a>
</p>
</li>
</ul>
layouts/shortcodes/tag_latest.html
-1
View File
@@ -1 +0,0 @@
<span>v2.0.1</span>
layouts/shortcodes/version.html
-1
View File
@@ -1 +0,0 @@
<span>v2.0</span>