Closed wmhutchison closed 2 months ago
At present the upgrade methodology goes like this.
Ignoring whether or not we're talking about LAB or PROD, we want to strengthen overall communications and testing processes as follows.
Moving to Backlog due to me going on vacation. If there's a desire to promote work on this in my absence, can move out of Backlog.
back from vacation, this ticket can resume work.
Moving to Backlog for now, as this is not really the same thing and priority as work spent on the Canary apps for documentation/testing. Making Canary work a priority for now, this will still exist as a reminder for Platform Operations to continue working on it as time permits and keep this item in mind during Openshift upgrades in the future.
Discussed with team during Backlog grooming. It was felt that this ticket no is applicable, since we now track dependencies with automation and docs for creating our ZenHub tickets. Actual handling/tracking of unit tests has now been delegated to the Platform Services team with the use of N8N.
Describe the issue We need to create a suitable framework that can be re-used for maintenance activities and ensure that all stakeholders with the Openshift environments are properly reviewed and evaluated before, during and after each maintenance activity is completed. This will leverage automation as needed, with the option for manual checks to supplement where appropriate or still needed.
Additional context (coming soon)
Definition of done