-
Notifications
You must be signed in to change notification settings - Fork 25
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
Mpp prod move #541
Mpp prod move #541
Conversation
Build failed. ✔️ pre-commit SUCCESS in 1m 41s |
6ad343a
to
af337fe
Compare
Build failed. ✔️ pre-commit SUCCESS in 1m 41s |
Build failed. ✔️ pre-commit SUCCESS in 1m 41s |
Build failed. ✔️ pre-commit SUCCESS in 1m 42s |
Build failed. ✔️ pre-commit SUCCESS in 1m 39s |
Build failed. ✔️ pre-commit SUCCESS in 2m 18s |
Build failed. ✔️ pre-commit SUCCESS in 1m 41s |
6eea607
to
3b29dfa
Compare
Build failed. ✔️ pre-commit SUCCESS in 1m 41s |
When pulling the images from ghcr.io it is easy to reach the quotas / rate limiting, therefore create an image stream so it is possible to manually push the image to the MP+ registry. TODO by Jirka: research the possibility of mirroring the images into separate image registry dedicated to MP+. Signed-off-by: Matej Focko <[email protected]>
* Sandcastle uses different storage class on MP+ * We also use newer postgres on mp+ Signed-off-by: Matej Focko <[email protected]>
* namespace * storage type Signed-off-by: Matej Focko <[email protected]>
Co-authored-by: Jiří Popelka <[email protected]> Signed-off-by: Matej Focko <[email protected]>
tl;dr Production gets redeployed on each image build from `stable` After migration to MP+, we're switching to automatic pulling of the images by the OpenShift. This process allows us to monitor the production deployment during the working hours as opposed to the previous deployment at 2am and verification tests being run at the 4am. Signed-off-by: Matej Focko <[email protected]>
Signed-off-by: Matej Focko <[email protected]>
Build failed. ✔️ pre-commit SUCCESS in 1m 42s |
Signed-off-by: Matej Focko <[email protected]>
Build failed. ✔️ pre-commit SUCCESS in 1m 41s |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For what I can grasp this looks good to me.
Thanks a lot!
Rebased on top of @majamassarini PR, so it's easy to retry next time.