Closed ThomasObenaus closed 5 years ago
It is very important to mention that with this changes the AWS ECR ( Docker registry ) which has to be used is now bound to the one the cluster is running in!
Usually this is not a problem, since this will be the setup in most of the cases. Furthermore I would even consider it a best practice to reduce the inter-account dependencies. BUT it reduces the flexibility.
Hence it should be mentioned in the documentation.
Changes
With this adjustment it is possible to load docker images from public docker repositories (like Docker Hub) and from the ECR of the AWS account wherein the COS is deployed.
Therefore instead of using the docker credStore option, to enable the ecr-login helper, only the credHelper option is used only for this purpose. Thus it is possible to specify to use the ecr-login helper only for the ECR of the AWS account. All other docker pull requests (i.e. to Docker Hub) are made without credentials.
This solves #51.
Tested
image = "thobe/ping_service:0.0.9"
image = "<aws_account_id>.dkr.ecr.us-east-1.amazonaws.com"