Ken Cochrane
Ken Cochrane
@ambrons so to sum up the issue it looks like there are 2 problems. 1. Need the IAM permissions to get the ecr tokens (http://docs.aws.amazon.com/AmazonECR/latest/userguide/ecr_managed_policies.html#AmazonEC2ContainerRegistryReadOnly) 2. The ecr tokens expire...
@ambrons thank you for the details. This is what I'm thinking, let me know if that works for you. We add a new template question that asks if you want...
> I agree with the Cloud Formation question for ECR support as well as adding the AmazonEC2ContainerRegistryReadOnly. Let that be a Parameter of the template. I don't think they would...
short answer. Yes, the goal is to allow someone to pick the "enable ECR support" and it will deal with the IAM profile, and keeping the Token up to date.
@jeffhuys it is on the road map, current estimate is for it to arrive with 17.06-ce
It has been a while since I have commented on this issue, so I think it is time for an update, to let everyone know where we are with this...
@blaketastic2 did this approach work for you? At first glance, I don't think it will work because running the `aws ect get-login` will not update the password that is tied...
@blaketastic2 yes, if you run the `service update` after the `aws ecr get-login` that should work. It isn't ideal since it will cause a rolling update of the service. You...
As of right now, I do not know of a way to update the credentials without causing a rolling update of the service.
Thanks, It is on our roadmap to support windows worker nodes in the future.