mirrors/velero
1
0
Fork 0
mirror of https://github.com/vmware-tanzu/velero.git synced 2026-08-15 11:46:06 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

extend AWS NoCredentialsProviders troubleshooting docs with kube2iam case

Browse Source 
Signed-off-by: The-smooth-operator <alberto.delbarrio.albelda@gmail.com>
This commit is contained in:
The-smooth-operator
2019-01-28 12:34:53 +01:00
parent 78cb813210
commit c56e3e5af3
1 changed files with 8 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/debugging-install.md
+8 -1
View File
@@ -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
[0]: azure-config#credentials-and-configuration