mirror of
https://github.com/rancher/rancher-docs.git
synced 2026-09-24 20:18:18 +00:00
Denise
@@ -18,3 +18,25 @@ RKE launched clusters are separated into two categories:
|
||||
- [Custom Nodes]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/custom-nodes/):
|
||||
|
||||
For use cases where you want to provision bare-metal servers, on-premise virtual machines, or bring virtual machines that are already exist in a cloud provider. With this option, you will run a Rancher agent Docker container on the machine.
|
||||
|
||||
<br/>
|
||||
|
||||
### Requirements
|
||||
|
||||
If you use RKE to set up a cluster, your cluster nodes must meet the following requirements.
|
||||
|
||||
{{< accordion id="os" label="Operating System" >}}
|
||||
{{< requirements_os >}}
|
||||
{{< /accordion >}}
|
||||
{{< accordion id="hardware" label="Hardware" >}}
|
||||
{{< requirements_hardware >}}
|
||||
{{< /accordion >}}
|
||||
{{< accordion id="software" label="Software" >}}
|
||||
{{< requirements_software >}}
|
||||
{{< /accordion >}}
|
||||
{{< accordion id="ports-rancher" label="Ports for Rancher" >}}
|
||||
{{< requirements_ports_rancher >}}
|
||||
{{< /accordion >}}
|
||||
{{< accordion id="ports-rke" label="Ports for RKE" >}}
|
||||
{{< requirements_ports_rke >}}
|
||||
{{< /accordion >}}
|
||||
@@ -13,7 +13,7 @@ Using Rancher, you can create pools of nodes based on a [node template](#node-te
|
||||
|
||||
Each node pool is assigned with a [node component]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/#node-components) to specify how these nodes should be configured for the Kubernetes cluster.
|
||||
|
||||
## Node templates
|
||||
## Node Templates
|
||||
|
||||
A node template is the saved configuration for the parameters to use when provisioning nodes in a specific cloud provider. Rancher provides a nice UI to be able to launch these nodes and uses [Docker Machine](https://docs.docker.com/machine/) to provision these nodes. The available cloud providers to create node templates are based on the active node drivers in Rancher.
|
||||
|
||||
|
||||
@@ -0,0 +1,72 @@
|
||||
---
|
||||
title: Nodes
|
||||
weight:
|
||||
aliases:
|
||||
---
|
||||
|
||||
After you launch a Kubernetes cluster in Rancher, you can manage individual nodes from the cluster's **Node** tab. Depending on the [option used]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/#cluster-creation-in-rancher) to provision the cluster, there are different node options available.
|
||||
|
||||
>**Note:** If you want to manage the _cluster_ and not individual nodes, see [Editing Clusters]({{< baseurl >}}/rancher/v2.x/en/k8s-in-rancher/editing-clusters).
|
||||
|
||||
To manage individual nodes, browse to the cluster that you want to manage and then select **Nodes** from the main menu. The following sections list what node management options are available for each cluster type.
|
||||
|
||||
<!-- TOC -->
|
||||
|
||||
- [Nodes Provisioned by Node Pool](#nodes-provisioned-by-node-pool)
|
||||
- [Nodes Provisioned with the Custom Nodes Option](#nodes-provisioned-with-the-custom-nodes-option)
|
||||
- [Nodes Provisioned by Hosted Kubernetes Providers](#nodes-provisioned-by-hosted-kubernetes-providers)
|
||||
- [Imported Nodes](#imported-nodes)
|
||||
|
||||
<!-- /TOC -->
|
||||
|
||||
|
||||
## Nodes Provisioned by Node Pool
|
||||
|
||||
Clusters provisioned using [one of the node pool options]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/node-pools/#node-pools) automatically maintain the node scale that's set during the initial cluster provisioning. This scale determines the number of active nodes that Rancher maintains for the cluster.
|
||||
|
||||
- Mark nodes as unschedulable (i.e., **Cordon**). When a node is cordoned, no new pods are scheduled for the node, but the existing pods continue to run.
|
||||
- Delete defective nodes from the cloud provider. When you the delete a defective node, Rancher automatically replaces it with an identically provisioned node.
|
||||
|
||||
>**Note:** If you want to scale down the number of nodes, use the scaling controls rather than deleting the node.
|
||||
- Scale the number of nodes in the cluster up or down.
|
||||
- Enter a **Custom Name**, **Description**, or **Label** for a node.
|
||||
- Download the SSH key pair for a node. You can use this key pair to remote into the node using an SSH connection from your workstation. For more instructions on how to remote into the node, see [Remoting into a Node Pool Node](#remoting-into-a-node-pool-node).
|
||||
- View API Data.
|
||||
|
||||
### Remoting into a Node Pool Node
|
||||
|
||||
1. From the Node Pool cluster, select **Nodes** from the main menu.
|
||||
1. Find the node that you want to remote into. Select **Ellipsis (...) > Download Keys**.
|
||||
|
||||
**Step Result:** A ZIP file containing files used for SSH is downloaded.
|
||||
|
||||
1. Extract the ZIP file to any location.
|
||||
1. Open Terminal. Change your location to the extracted ZIP file.
|
||||
1. Enter the following command:
|
||||
|
||||
```
|
||||
ssh -i id_rsa root@<IP_OF_HOST>
|
||||
```
|
||||
|
||||
## Nodes Provisioned with the Custom Nodes Option
|
||||
|
||||
For nodes provisioned using the [custom nodes option]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/custom-nodes/#custom-nodes), you can use the following options from the Rancher UI:
|
||||
|
||||
- Mark nodes as unschedulable (i.e., **Cordon**). When a node is cordoned, no new pods are scheduled for the node, but the existing pods continue to run.
|
||||
- Delete node objects from the **Nodes** ist. When you the delete a custom node, you still have to delete it from the node itself.
|
||||
- Enter a **Custom Name**, **Description**, or **Label** for a node.
|
||||
- View API Data.
|
||||
|
||||
## Nodes Provisioned by Hosted Kubernetes Providers
|
||||
|
||||
Options for managing nodes [hosted by a Kubernetes provider]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters/) are somewhat limited in Rancher. Rather than using the Rancher UI to make edits such as scaling the number of nodes up or down, edit the cluster directly.
|
||||
|
||||
From the Rancher UI, you can:
|
||||
|
||||
- Mark nodes as unschedulable (i.e., **Cordon**). When a node is cordoned, no new pods are scheduled for the node, but the existing pods continue to run.
|
||||
- Enter a **Custom Name**, **Description**, or **Label** for a node.
|
||||
- View node API Data.
|
||||
|
||||
## Imported Nodes
|
||||
|
||||
Although you can deploy workloads to an [imported cluster]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/imported-clusters/) using Rancher, you cannot manage individual cluster nodes. All management of imported cluster nodes must take place outside of Rancher.
|
||||
@@ -1,5 +1,36 @@
|
||||
---
|
||||
title: Managing Node Templates
|
||||
weight: 7010
|
||||
draft: true
|
||||
---
|
||||
|
||||
when you provision a [node pool]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/node-pools) cluster, [node templates]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/node-pools/#node-templates) are used to provision the cluster nodes. These templates use Docker Machine commands to configure an operating system image and setting/parameters for the node. You can create node templates in two contexts:
|
||||
|
||||
- While [provisioning a node pool cluster]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/node-pools).
|
||||
- At any time, from your [user settings](#creating-a-node-template-from-user-settings).
|
||||
|
||||
When you create a node template, it is bound to your user profile. Node templates cannot be shared among users. You can delete stale node templates that you no longer user from your user settings.
|
||||
|
||||
## Creating a Node Template from User Settings
|
||||
|
||||
1. From your user settings, select **User Avatar > Node Templates**.
|
||||
1. Click **Add Template**.
|
||||
1. Select one of the cloud providers available. Then follow the instructions on screen to configure the template.
|
||||
|
||||
**Result:** The template is configured. You can use the template later when you [provision a node pool cluster]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/node-pools).
|
||||
|
||||
## Cloning Node Templates
|
||||
|
||||
When creating new node templates from your user settings, you can clone an existing template and quickly update its settings rather than creating a new one from scratch. Cloning templates saves you the hassle of re-entering access keys for the cloud provider.
|
||||
|
||||
1. From your user settings, select **User Avatar > Node Templates**.
|
||||
1. Find the template you want to clone. Then select **Ellipsis > Clone**.
|
||||
1. Complete the rest of the form.
|
||||
|
||||
**Result:** The template is cloned and configured. You can use the template later when you [provision a node pool cluster]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/node-pools).
|
||||
|
||||
## Deleting a Node Template
|
||||
|
||||
When you no longer use a node template, you can delete it from your user settings.
|
||||
|
||||
1. From your user settings, select **User Avatar > Node Templates**.
|
||||
1. Select one or more template from the list. Then click **Delete**. Confirm the delete when prompted.
|
||||
Reference in New Issue
Block a user