public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-09-25 04:28:15 +00:00
Code Issues Packages Projects Releases Wiki Activity

content from PR #470

Browse Source
This commit is contained in:
Denise Schannon
2018-07-16 16:54:35 -07:00
parent 9899263e5f
commit eea6909062
2 changed files with 80 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/rancher/v2.x/en/clusters/_index.md
+21
View File
@@ -49,3 +49,24 @@ Alternatively, you can use Rancher to create a cluster from your own existing no
## Kubernetes Importation
Finally, you also have the option of importing an existing Kubernetes cluster that you're already using into Rancher.
Using Rancher, you can create Kubernetes clusters using a variety of options. Use the option that best fits your use case.
## Hosted Kubernetes Providers
If you already have a cluster hosted by a Kubernetes provider such as Google GKE, Rancher can integrate with its cloud APIs, allowing you to manage your hosted cluster from the Rancher UI.
## Infrastructure Providers
Using Rancher, you can leverage APIs from major IaaS providers to create nodes and provision a new Kubernetes cluster.
## From Existing Nodes
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.
## Import Existing 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.
content/rancher/v2.x/en/clusters/hosted-kubernetes-clusters/_index.md
+59
View File
@@ -2,3 +2,62 @@
title: Hosted Kubernetes Providers
weight: 2100
---
---
title: Hosted Kubernetes Providers
weight: 25
aliases:
- /rancher/v2.x/en/tasks/clusters/creating-a-cluster/create-cluster-azure-container-service
- /rancher/v2.x/en/tasks/clusters/creating-a-cluster/create-cluster-eks
- /rancher/v2.x/en/tasks/clusters/creating-a-cluster/create-cluster-gke
---
If you already have a cluster hosted by a Kubernetes provider, Rancher can integrate with its cloud APIs, allowing you to manage your hosted cluster from the Rancher UI.
Rancher supports the following Kubernetes providers:
<!-- TOC -->
- [Google GKE (Google Container Engine)](#google-gke-google-container-engine)
- [Amazon EKS (Elastic Container Service)](#amazon-eks-elastic-container-service)
- [Microsoft AKS (Azure Container Service)](#microsoft-aks-azure-container-service)
<!-- /TOC -->
When setting up management of your hosted Kubernetes cluster in the Rancher UI, you are prompted for parameters required in all cluster creation scenarios: cluster name, user membership, how many nodes to create, and so on. However, each provider also requires information unique to the vendor. See more information about the information required for each provider below.
## Google GKE (Google Container Engine)
Before Rancher can manage a Google GKE cluster, you must create a service account with Google. This account also requires you to assign it the appropriate roles.
Create a service account using [Google Cloud Platform](https://console.cloud.google.com/projectselector/iam-admin/serviceaccounts). GKE uses this account to operate your cluster. Creating this account also generates a private key used for authentication.
The service account requires the following roles:
- `project/viewer`
- `kubernetes-engine/admin`
- `service-account/user`
For full instructions on how to complete these actions, see [Creating and Enabling Service Accounts](https://cloud.google.com/compute/docs/access/create-enable-service-accounts-for-instances).
After you create a service account, enter your service account private key into Rancher.
## Amazon EKS (Elastic Container Service)
Before Rancher can manage an Amazon EKS cluster, you must provide it with an Amazon access key that has the appropriate permissions assigned to it.
Log into the [Amazon AWS Management Console](https://aws.amazon.com/console/) to assign yourself the appropriate IAM permissions and create an access key. Complete the actions below.
- Assign the account you're using the IAM permissions to create clusters, modify clusters, and use the required API actions. For more information, see the official [EKS documentation](https://docs.aws.amazon.com/eks/latest/userguide/IAM_policies.html).
- Create an Amazon access key and secret key. For more information, see [Managing Access Keys for IAM Users](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html)
After you complete the two actions above, enter your access key and secret key in Rancher.
## Microsoft AKS (Azure Container Service)
Before Rancher can manage a Microsoft AKS cluster, you must provide it with information from your Azure Active Directory Service Principal (here after, _service principal_). Rancher uses this service principal to interact with the Azure API.
For instruction on how to create a service principal, see [Service Principals with Azure Kubernetes Service (AKS)](https://docs.microsoft.com/en-us/azure/aks/kubernetes-service-principal).
After you complete the action above, enter the information from your service principal in Rancher.