<p>Update for anyone else who runs into this issue, when Spinnaker is installed using helm it's using an older version of the Halyard container which doesn't have the AWS CLI tool. This seems to be hard to resolve as just updating the values file for helm to the latest version doesn't seem to work and I didn't dig much into the specifics as didn't want to go down that rabbit hole.</p>

CC BY-SA 4.0
2019-11-29T15:26:02.007Z
2019-11-29T15:26:02.007Z
joshk132
<p>I installed Spinnaker onto a Kubernetes cluster via Helm. I have tried to add the ECR registry as per the docs and so far not working. I found that the aws cli is missing even though in issue <a href="https://github.com/spinnaker/spinnaker/issues/2394" rel="nofollow noreferrer">2394</a> it was adding into the Dockerfile, looks like as of master it is included still. Wondering what helm used that was so wrong to not have it?</p>

<p>Am I missing something?</p>

CC BY-SA 4.0
2019-11-22T08:10:48.623Z
what docs ? also do you get any error at all ?
Iakovos Belonias
<amazon-web-services><kubernetes><cicd>
Issue connecting to ECR using Spinnaker on Kubernetes
joshk132
# Issue connecting to ECR using Spinnaker on Kubernetes

(Asked by: username_0 on 2019-11-22)

I installed Spinnaker onto a Kubernetes cluster via Helm. I have tried to add the ECR registry as per the docs and so far not working. I found that the aws cli is missing even though in issue [2394](https://github.com/spinnaker/spinnaker/issues/2394) it was adding into the Dockerfile, looks like as of master it is included still. Wondering what helm used that was so wrong to not have it?

Am I missing something?

**Tags:** amazon-web-services, kubernetes, cicd

> **Comments:**
> **username_1**: what docs ? also do you get any error at all ?  

---

## 1 answers

### Answer by username_0 on 2019-11-29. Score: 2 | Accepted answer

Update for anyone else who runs into this issue, when Spinnaker is installed using helm it's using an older version of the Halyard container which doesn't have the AWS CLI tool. This seems to be hard to resolve as just updating the values file for helm to the latest version doesn't seem to work and I didn't dig much into the specifics as didn't want to go down that rabbit hole.


---

