We're using the AWS ECR as our registry, of which you can have only one per account.
We want to run multiple Kubernetes clusters (with Deis on top), which causes trouble because the repository names inside the registry are all flat and cause collisions when DeisA and DeisB both have the same app name. (DeisA and DeisB are running completely separately, on different clusters with separate storage and domains.)
Is it possible to create a namespace or prefix/ for Deis-created repositories, so that app1 becomes deisA/app1 ? If that works correctly, it should also be possible to use IAM to segregate access to the repositories based on the prefix.
From @mariusmarais on June 2, 2017 10:31
We're using the AWS ECR as our registry, of which you can have only one per account.
We want to run multiple Kubernetes clusters (with Deis on top), which causes trouble because the repository names inside the registry are all flat and cause collisions when DeisA and DeisB both have the same app name. (DeisA and DeisB are running completely separately, on different clusters with separate storage and domains.)
Is it possible to create a namespace or
prefix/for Deis-created repositories, so thatapp1becomesdeisA/app1? If that works correctly, it should also be possible to use IAM to segregate access to the repositories based on the prefix.Copied from original issue: deis/builder#519