From c56e3e5af32a4d79d7081edbf9642abbdfa6da2d Mon Sep 17 00:00:00 2001 From: The-smooth-operator Date: Mon, 28 Jan 2019 12:34:53 +0100 Subject: [PATCH] extend AWS NoCredentialsProviders troubleshooting docs with kube2iam case Signed-off-by: The-smooth-operator --- docs/debugging-install.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/docs/debugging-install.md b/docs/debugging-install.md index ac31e6d69..bf8d8716a 100644 --- a/docs/debugging-install.md +++ b/docs/debugging-install.md @@ -20,6 +20,8 @@ kubectl -n heptio-ark logs deployment/ark ## AWS ### `NoCredentialProviders: no valid providers in chain` + +#### Using credentials This means that the secret containing the AWS IAM user credentials for Ark has not been created/mounted properly into the Ark server pod. Ensure the following: * The `cloud-credentials` secret exists in the Ark server's namespace @@ -34,6 +36,11 @@ into the Ark server pod. Ensure the following: * The `cloud-credentials` secret is defined as a volume for the Ark deployment * The `cloud-credentials` secret is being mounted into the Ark server pod at `/credentials` +#### Using kube2iam +This means that Ark can't read the content of the S3 bucket. Ensure the following: +* There is a Trust Policy document allowing the role used by kube2iam to assume Ark's role, as stated in the AWS config documentation. +* The new Ark role has all the permissions listed in the documentation regarding S3. + ## Azure @@ -56,4 +63,4 @@ into the Ark server pod. Ensure the following: * The `cloud-credentials` secret is defined as a volume for the Ark deployment * The `cloud-credentials` secret is being mounted into the Ark server pod at `/credentials` -[0]: azure-config#credentials-and-configuration \ No newline at end of file +[0]: azure-config#credentials-and-configuration