-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ecr: secret not being generated #11
Comments
I would also update the documentation (https://deis.com/docs/workflow/installing-workflow/configuring-registry/) with one section for ECR and one section for GCR with samples. |
deis/workflow#779 represents the docs update |
FWIW I ran into the same error all of a sudden
So I deleted the token refresher pod to start a new one and everything worked again:
|
I'm running into this same problem, but I'm not able to recover. Originally I setup values with both However, after removing them and running
Restarting the pod has no effect and it isn't generating any log output, which is making debugging very difficult (quay.io/deis/registry-token-refresher:v1.1.2). Please help :) Update: Granting the follow access via IAM resolves the issue, since Deis needs to be able to create a repository for every app: {
"Effect": "Allow",
"Action": [
"ecr:*"
],
"Resource": [
"*"
]
} Can this be limited further? |
This issue was moved to teamhephy/registry-token-refresher#2 |
When setting up values for using ECR as the off-cluster registry option, a sample snippet of Workflow's global
values.yaml
would look something like:Yet, when the
registryid
andhostname
values are non-empty as above, it seems a bug is hit and the necessaryprivate-registry-ecr
secret is not created correctly. When an attempt to build/deploy an example app, the following is hit:Meanwhile, counterintuitively, if both
registryid
andhostname
are just kept at""
then the aforementioned secret is created properly and build/deploys work as intended.The text was updated successfully, but these errors were encountered: