Skip to content
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

Application Image Resilience #1821

Open
warrenchristian1telus opened this issue Jun 12, 2024 · 1 comment
Open

Application Image Resilience #1821

warrenchristian1telus opened this issue Jun 12, 2024 · 1 comment
Assignees
Labels
DevOps Related to OpenShift platform wide issues

Comments

@warrenchristian1telus
Copy link
Collaborator

To prevent any further issues with images being moved or removed from their expected locations (such as what recently happened with KeyCloak) we are recommended to build and/or deploy our base images to a repository we control.

We already have one setup on artifacts.developer.gov.bc.ca for all OpenShift projects, which we can leverage for this purpose.

The main focus of this ticket will be to create relevant workflows to build/copy each deployment image to the respective dev, test and prod locations to ensure that each image can be accessed until we change it.

This will mainly work to make our application more resilient by ensuring that all of our base images are in place and remain there during and after deployment. Eliminating any cases where a server or cluster restart or crash may lead to an unavailable image causing a crash loop and bringing down all or part of the application.

@warrenchristian1telus warrenchristian1telus added the DevOps Related to OpenShift platform wide issues label Jun 12, 2024
@Stella-Archer
Copy link
Collaborator

Stella-Archer commented Jun 13, 2024

Steps for updating images?
Initial set up will require DEVOpps
once set up any developer should be able to update

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DevOps Related to OpenShift platform wide issues
Projects
None yet
Development

No branches or pull requests

3 participants