You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In mybinder.org, we use chartpress to build images and set image tags in a deployment config file (such as config/staging.yaml or config/prod.yaml). Currently, values.yaml is hardcoded - would be nice to allow this to change.
The text was updated successfully, but these errors were encountered:
yuvipanda
added a commit
to yuvipanda/mybinder.org-deploy
that referenced
this issue
Nov 1, 2018
- We only push to prod, not staging, since chartpress isn't set up
to do multiple pushes. jupyterhub/chartpress#25
should help with that.
- Staging can read all prod images for now, to work around this.
- Create and use a new prod service acct that has image read / write perms.
In mybinder.org, we use chartpress to build images and set image tags in a deployment config file (such as config/staging.yaml or config/prod.yaml). Currently, values.yaml is hardcoded - would be nice to allow this to change.
The text was updated successfully, but these errors were encountered: