-
Notifications
You must be signed in to change notification settings - Fork 32
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
staging -> prod (#477, #478, #480, #481, #482, #484, #486, #493, #494) #495
Conversation
dev gateway config
Switch to dev version of distributed
Add dask-gateway tokens
Change to latest Pangeo Docker tag
Switch to tjcrone/hubploy
Incorporate hubploy timeout option
Modify OOI placeholder resources and return to yuvipanda hubploy
Gives us free HTTPS, and avoids having an extra public IP!
update ocean image
update profile list
It looks like I need to add the gateway secrets for the prod deployments. I'll try to do that now. |
Custom configs for gateway clusters
@tjcrone - I added the dask-gateway secrets for the prod clusters on the google hubs. Can you make sure the ooi hub has the correct secrets? I don't have the git-crypt key for the ooi deployment. |
Anything I can do to anything I can do to help here? Our entire data catalog is broken until we can deploy this. |
To get around this for ocean, I added this: pangeo-cloud-federation/.circleci/config.yml Lines 55 to 58 in b52b559
The bigger question is, why does it now take 35 minutes to build these images? 🤦♂ |
I'm watching this and prepared to help. We are in a good spot in terms of a merge that might break our deployment. Shouldn't be a problem this week. Thank you very much for checking. Please go ahead and merge if you can, and if something goes wrong with our deployment, I will fix it. |
I have updated our secrets on our fork, but I'm not sure how to add these to this PR. Let's go ahead and merge this, and then I will do a separate PR to merge our secrets files. Does this sound reasonable? We are fine on our side for any merge you decide to do here. Thank you again! |
fixes pangeo-data/pangeo-datastore#74
fixes pangeo-data/pangeo-datastore#73
fixes pangeo-data/pangeo#754