From fd8f239d28ae700ddca3b312f9931d91860c40df Mon Sep 17 00:00:00 2001 From: Sebastiaan van Steenis Date: Mon, 12 Aug 2019 16:45:16 +0200 Subject: [PATCH] Add info on using ECR with Amazon cloud provider --- .../rke-clusters/options/cloud-providers/_index.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/content/rancher/v2.x/en/cluster-provisioning/rke-clusters/options/cloud-providers/_index.md b/content/rancher/v2.x/en/cluster-provisioning/rke-clusters/options/cloud-providers/_index.md index 96088b6c645..0a08766d8bc 100644 --- a/content/rancher/v2.x/en/cluster-provisioning/rke-clusters/options/cloud-providers/_index.md +++ b/content/rancher/v2.x/en/cluster-provisioning/rke-clusters/options/cloud-providers/_index.md @@ -163,6 +163,11 @@ Setting the value of the tag to `owned` tells the cluster that all resources wit **Key** = `kubernetes.io/cluster/CLUSTERID` **Value** = `shared`. + +#### Using Amazon Elastic Container Registry (ECR) + +The kubelet component has the ability to automatically obtain ECR credentials, when the IAM profile mentioned in [Create an IAM Role and attach to the instances](#create-an-iam-role-and-attach-to-the-instances) is attached to the instance(s). When using a Kubernetes version older than v1.15.0, the Amazon cloud provider needs be configured in the cluster. Starting with Kubernetes version v1.15.0, the kubelet can obtain ECR credentials without having the Amazon cloud provider configured in the cluster. + ## Azure When using the `Azure` cloud provider, you can leverage the following capabilities: