Velero: Setup ark using role on AWS

[pmquang]

Hi,

Im setting up heptio ark on K8S using role on AWS.

It's fine for ark deployment but minio:

$ kubectl logs --tail 100 minio-setup-t25t2 -n heptio-ark

mc: Unable to initialize new config from the provided credentials. The request signature we calculated does not match the signature you provided. Check your key and signing method.

Anyone knows how to add support role for minio ?

Regards

[ncdc]

Did you use our example yaml to deploy minio, or did you change anything?

On Wed, Jun 20, 2018 at 6:58 AM RAI [e-mail] wrote:

Hi,

Im setting up heptio ark on K8S using role on AWS.

It's fine for ark deployment but minio:

$ kubectl logs --tail 100 minio-setup-t25t2 -n heptio-ark

mc: Unable to initialize new config from the provided credentials. The
request signature we calculated does not match the signature you provided.
Check your key and signing method.

Anyone knows how to add support role for minio ?

Regards

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/heptio/ark/issues/562, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAABYjZQvPKTfV2nqvdewVmDzDoffbKdks5t-iq5gaJpZM4UvDWi
.

[pmquang]

I used the example yaml and remove lines of AWS key to deploy minio:

---

apiVersion: v1
kind: Secret
metadata:
namespace: heptio-ark
name: cloud-credentials
labels:
component: minio
stringData:
cloud: |
[default]
aws_access_key_id = xxx
aws_secret_access_key = xxx

These lines above were removed.

[ncdc]

It looks like the minio server only supports a single access key and secret (https://github.com/minio/minio/issues/5305).

[ncdc]

@pmquang did my answer make sense? Do you need any further assistance?

[pmquang]

Yes, thank you :)

[rosskukulinski]

Closing as question answered - please feel free to comment if you think I've been over zealous