More cross info between cloud provider and EC2 node pool

This commit is contained in:
Sebastiaan van Steenis
2018-08-02 14:07:54 -07:00
committed by Denise
parent 63ad237862
commit eccfba7c94
2 changed files with 6 additions and 6 deletions
@@ -22,12 +22,12 @@ Use {{< product >}} to create a Kubernetes cluster in Amazon EC2.
[Amazon Documentation: Creating Access Keys](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html#Using_CreateAccessKey). [Amazon Documentation: Creating Access Keys](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html#Using_CreateAccessKey).
See [Example Node IAM policy](#example-node-iam-policy) for an example policy that can be applied to these credentials. See [Example Node Pool IAM policy](#example-node-pool-iam-policy) for an example policy that can be applied to these credentials.
- **Zone and Network** configures the availability zone and network settings for your cluster. - **Zone and Network** configures the availability zone and network settings for your cluster.
- **Security Groups** creates or configures the Security Groups applied to your nodes. Please refer to [Amazon EC2 security group when using Node Driver]({{< baseurl >}}/rancher/v2.x/en/installation/references/#amazonec2-securitygroup-nodedriver) to see what rules are created in the `rancher-nodes` Security Group. - **Security Groups** creates or configures the Security Groups applied to your nodes. Please refer to [Amazon EC2 security group when using Node Driver]({{< baseurl >}}/rancher/v2.x/en/installation/references/#amazonec2-securitygroup-nodedriver) to see what rules are created in the `rancher-nodes` Security Group.
- **Instance** configures the instances that will be created. Make sure you configure the correct **SSH User** for the configured AMI. - **Instance** configures the instances that will be created. Make sure you configure the correct **SSH User** for the configured AMI.
If you need to pass an **IAM Instance Profile Name** (not ARN), for example, when you want to use a [Kubernetes Cloud Provider]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/options/cloud-providers), you will need an additional permission in your policy. See [Example Node IAM policy with PassRole](#example-node-iam-policy-with-passrole) for an example policy. If you need to pass an **IAM Instance Profile Name** (not ARN), for example, when you want to use a [Kubernetes Cloud Provider]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/options/cloud-providers), you will need an additional permission in your policy. See [Example Node Pool IAM policy with PassRole](#example-node-pool-iam-policy-with-passrole) for an example policy.
1. {{< step_rancher-template >}} 1. {{< step_rancher-template >}}
1. Click **Create**. 1. Click **Create**.
@@ -36,7 +36,7 @@ Use {{< product >}} to create a Kubernetes cluster in Amazon EC2.
{{< result_create-cluster >}} {{< result_create-cluster >}}
### Example Node IAM Policy ### Example Node Pool IAM Policy
```json ```json
{ {
@@ -88,7 +88,7 @@ Use {{< product >}} to create a Kubernetes cluster in Amazon EC2.
} }
``` ```
### Example Node IAM Policy with PassRole ### Example Node Pool IAM Policy with PassRole
```json ```json
{ {
@@ -27,7 +27,7 @@ When using the `Amazon` cloud provider, you can leverage the following capabilit
- Create/configure an IAM role - Create/configure an IAM role
- Configuring the ClusterID - Configuring the ClusterID
> **Note:** When you create an [Amazon EC2 Cluster]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/node-pools/ec2/#create-the-amazon-ec2-cluster), the `ClusterID` is automatically configured. > **Note:** When you create an [Amazon EC2 Cluster]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/node-pools/ec2/#create-the-amazon-ec2-cluster), the `ClusterID` is automatically configured for the created nodes. Other resources still need to be tagged manually.
#### Create/Configure an IAM Role #### Create/Configure an IAM Role
@@ -35,7 +35,7 @@ All nodes added to the cluster must be able to interact with EC2 so that they ca
[EC2 documentation: Creating an IAM Role](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/iam-roles-for-amazon-ec2.html#create-iam-role) [EC2 documentation: Creating an IAM Role](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/iam-roles-for-amazon-ec2.html#create-iam-role)
- While creating an [Amazon EC2 cluster]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/node-pools/ec2/#create-the-amazon-ec2-cluster), you must insert the name of the IAM role when creating the **Node Template**. - While creating an [Amazon EC2 cluster]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/node-pools/ec2/#create-the-amazon-ec2-cluster), you must fill in the **IAM Instance Profile Name** (not ARN) when creating the **Node Template**. This requires an additional IAM permission, see [Example Node Pool IAM Policy with PassRole]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/node-pools/ec2/#example-node-pool-iam-policy-with-passrole).
- While creating a [Custom cluster]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/custom-clusters/), you must manually attach the IAM role to the instance(s). - While creating a [Custom cluster]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/custom-clusters/), you must manually attach the IAM role to the instance(s).
The following IAM role can be created: The following IAM role can be created: