<p>I'm setting up Spinnaker in K8s with aws-ecr. My setup and steps are:</p>

<p><strong>on AWS side:</strong></p>

<ol>
<li>Added policies ecr-pull, ecr-push, and ecr-generate-token</li>
<li>Attached the policy to a role </li>
</ol>

<p><strong>Spinnaker setup:</strong></p>

<ol start="3">
<li><p>Modified <strong>values.yaml</strong> with below above settings:
```accounts:</p>

<ul>
<li>name: my-ecr
address: <a href="https://123456xxx.dkr.ecr.my-region.amazonaws.com" rel="nofollow noreferrer">https://123456xxx.dkr.ecr.my-region.amazonaws.com</a>
repositories:</li>
<li>123456xxx.dkr.ecr..amazonaws.com/spinnaker-test-project
```</li>
</ul></li>
<li><p>Annotated <strong>clouddriver.yaml</strong>: deployment to use created role (using the IAM role in a pod by referencing the role name in an annotation on the pod specification) </p></li>
</ol>

<p>But it doesn't work and the error on the cloudrvier side is :</p>

<p>.<code>d.r.p.a.DockerRegistryImageCachingAgent : Could not load tags for 1234xxxxx.dkr.ecr.&lt;my_region&gt;.amazonaws.com/spinnaker-test-project in https://1234xxxxx.dkr.ecr.&lt;my_region&gt;.amazonaws.com</code></p>

<p>Would like to get some help or advice what I'm missing, thank you</p>

<p>Got the answer from an official Spinnaker slack channel. That adding an iam policy to the clouddriver pod won't work unfortunately since it uses the docker client instead of the aws client. The workaround to make it work can be found  <a href="https://blog.spinnaker.io/using-aws-ecr-with-spinnaker-and-kubernetes-2b2a9bac8bd1" rel="nofollow noreferrer">here</a></p>

<p>Note* Ecr support currently is broken in halyard.This might get fixed in future after halyard migrates from the kubernetes v1 -> v2 or earlier so please verify with community or docs.</p>
