Integrate with ECR about gitkube

[tirumaraiselvan]

It is either an HTTP call or aws cli. Either way it breaks the current pattern and proves an exception (till now). If we come up with some other registry which also has the same problem then we need to think about solving the problem more generally. I guess for the time being we can make it a manual step.

[tirumaraiselvan]

One way is to ask (infer) the repo in remote CR and create tags instead of creating repositories i.e.

tirumarai/test:247ff5 (dockerhub) becomes

tirumarai:test-247ff5 (ecr)

[shahidhk]

How easy is it to create the registry? Provided the cluster has required IAM to do so?

[coco98]

I don't know enough about this problem, but for now we should just have documentation that can be a manual step. I think all these problems will go away in the months to come anyway. So we should definitely not try to solve it from inside gitkube or the gitkube CLI.

…

-- Tanmai

On Thu, May 24, 2018 at 11:36 PM Shahidh K Muhammed < ***@***.***> wrote: How easy is it to create the registry? Provided the cluster has required IAM to do so? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#68 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAIAWCOy0_Up8USd4R8eh6Ng02Ke3BRzks5t16ZpgaJpZM4ULe7j> .

[nizar-m]

Also the authentication to the AWS container registry lasts only for 12 hours. You have to keep renewing the docker credentials. Something like this cronjob will have to be run to keep the imagePullSecret renewed.

[tirumaraiselvan]

@nizar-m Yes, but that is clearly out of the scope of gitkube.

[nizar-m]

Docker push will fail if you use the command 'aws ecr get-login' to create the dockerPullSecrets and you end up doing it after 12 hours.