replaced instances of k8s

This commit is contained in:
Mark Bishop
2018-07-18 18:27:30 -07:00
parent 41c1aadce2
commit 8c359ff6c5

View File

@@ -16,17 +16,17 @@ A _Kubernetes Cluster_ is a cluster that uses the [Kubernetes container-orchestr
### Kubernetes Cluster Node Components
Each computing resource in a Kubernetes Cluster is called a _node_. Node can be either bare-metal servers or virtual machines. Kubernetes (here after, K8s) classifies nodes into three distinct types: _etcd_ nodes, _control plane_ nodes, and _worker_ nodes. Understanding the role of each node will help you create your own K8s cluster.
Each computing resource in a Kubernetes Cluster is called a _node_. Node can be either bare-metal servers or virtual machines. Kubernetes classifies nodes into three distinct types: _etcd_ nodes, _control plane_ nodes, and _worker_ nodes. Understanding the role of each node will help you create your own Kubernetes cluster.
#### etcd Nodes
[etcd](https://kubernetes.io/docs/concepts/overview/components/#etcd) nodes run the `etcd` database. The `etcd` database component is a key value store used as K8s storage for all cluster data, such as cluster coordination and state management.
[etcd](https://kubernetes.io/docs/concepts/overview/components/#etcd) nodes run the `etcd` database. The `etcd` database component is a key value store used as Kubernetes storage for all cluster data, such as cluster coordination and state management.
`etcd` is a distributed key value store, meaning it runs on multiple nodes so that there's always a backup available for fail over. Even though you can run `etcd` on a single node, you should run it on multiple nodes. We recommend 3, 5, or 7 nodes for redundancy.
#### Control Plane Nodes
[Control plane](https://kubernetes.io/docs/concepts/#kubernetes-control-plane) nodes run the K8s API server, scheduler, and controller manager. These nodes take care of routine tasks to ensure that your K8s cluster is running according to your configuration. Because all cluster data is stored on your `etcd` nodes, control plane nodes are stateless. You can run control plane on a single node, although two or more nodes are recommended for redundancy. Additionally, you can a single node can share the control plane and `etcd` roles.
[Control plane](https://kubernetes.io/docs/concepts/#kubernetes-control-plane) nodes run the Kubernetes API server, scheduler, and controller manager. These nodes take care of routine tasks to ensure that your Kubernetes cluster is running according to your configuration. Because all cluster data is stored on your `etcd` nodes, control plane nodes are stateless. You can run control plane on a single node, although two or more nodes are recommended for redundancy. Additionally, you can a single node can share the control plane and `etcd` roles.
#### Worker Nodes
@@ -39,9 +39,9 @@ Worker nodes also run storage and networking drivers, and ingress controllers wh
## Cluster Creation in Rancher
Now that you know what a K8s Cluster is, how does Rancher fit in?
Now that you know what a Kubernetes Cluster is, how does Rancher fit in?
Rancher simplifies creation of K8s clusters by allowing you to create them through the Rancher UI rather than more complex alternatives. Rancher provides multiple options for launching a K8s cluster. Use the option that best fits you use case.
Rancher simplifies creation of Kubernetes clusters by allowing you to create them through the Rancher UI rather than more complex alternatives. Rancher provides multiple options for launching a Kubernetes cluster. Use the option that best fits you use case.
## Cluster Creation Options
@@ -60,25 +60,25 @@ Options include:
### Hosted Kubernetes Cluster
If you already use a K8s provider such as Google GKE, Rancher can integrate with its cloud APIs, allowing you to create and manage your hosted cluster from the Rancher UI.
If you already use a Kubernetes provider such as Google GKE, Rancher can integrate with its cloud APIs, allowing you to create and manage your hosted cluster from the Rancher UI.
[Hosted Kubernetes Cluster]({{< baseurl >}}/rancher/v2.x/en/cluster-providers/hosted-kubernetes-clusters)
### Rancher Launched Kubernetes
Alternatively, you can use Rancher to create a cluster from your own existing nodes, using RKE. RKE is Ranchers own lightweight K8s installer. It works with any bare metal server, cloud provider, or virtualization platform. It integrates with node drivers to automatically provision nodes on AWS, Azure, DigitalOcean, vSphere, OpenStack, etc. Users can add custom nodes to the cluster by running the Rancher agent on these nodes.
Alternatively, you can use Rancher to create a cluster from your own existing nodes, using RKE. RKE is Ranchers own lightweight Kubernetes installer. It works with any bare metal server, cloud provider, or virtualization platform. It integrates with node drivers to automatically provision nodes on AWS, Azure, DigitalOcean, vSphere, OpenStack, etc. Users can add custom nodes to the cluster by running the Rancher agent on these nodes.
[Rancher Launched Kubernetes]({{< baseurl >}}/rancher/v2.x/en/cluster-providers/rke-clusters/)
#### Node Pools
Using Rancher, you can leverage <a href='https://docs.docker.com/machine/' target='_blank'>Docker Machine</a> in combination with RKE to create nodes and provision a new K8s cluster.
Using Rancher, you can leverage <a href='https://docs.docker.com/machine/' target='_blank'>Docker Machine</a> in combination with RKE to create nodes and provision a new Kubernetes cluster.
[Node Pools]({{< baseurl >}}/rancher/v2.x/en/cluster-providers/rke-clusters/#node-pools)
#### Custom Nodes
Use Rancher to create a K8s cluster on your on-premise bare metal servers. This option creates a cluster using RKE, which is Rancher's own lightweight K8s installer.
Use Rancher to create a Kubernetes cluster on your on-premise bare metal servers. This option creates a cluster using RKE, which is Rancher's own lightweight Kubernetes installer.
In addition to bare metal servers, RKE can also create clusters on less popular IaaS providers by integrating with node drivers.
@@ -86,6 +86,6 @@ In addition to bare metal servers, RKE can also create clusters on less popular
### Import Existing Cluster
Users can import an existing K8s cluster into Rancher. Rancher does not automate the provisioning, scaling, and upgrade of imported K8s clusters. All other cluster management, policy management, and workload management capabilities of Rancher apply to imported clusters.
Users can import an existing Kubernetes cluster into Rancher. Rancher does not automate the provisioning, scaling, and upgrade of imported Kubernetes clusters. All other cluster management, policy management, and workload management capabilities of Rancher apply to imported clusters.
[Importing Existing Cluster]({{< baseurl >}}/rancher/v2.x/en/cluster-providers/imported-clusters/)