Update Redis in Elasticache to Version 6.2 or Higher

laineymajor commented 1 year ago

Problem Statement

Our current development environment relies on Redis in Amazon Elasticache, specifically version 3. However, this version has become outdated and poses potential security and performance risks. To ensure the continued reliability and security of our development environment, we need to upgrade our Redis instance to version 6.2 or a higher compatible version.

Action Items

[x] Conduct a thorough assessment of the existing Redis configuration and dependencies within our development environment.
[x] Research and evaluate compatibility and potential impacts of upgrading to Redis version 6.2 or higher.
[x] Create a comprehensive upgrade plan, including a rollback strategy in case of unforeseen issues.
[x] Review above plan in relation to the PG retro and add relevant items to the plan.
[x] Review plan with key players (options: devops cop, tech team slack channel, coffee and code carnage, etc)
[x] Schedule a maintenance window for the upgrade to minimize disruption to development activities.
[x] Implement the Redis upgrade as per the plan.
[x] Thoroughly test the upgraded environment to ensure it functions as expected.
[x] Update documentation to reflect the new Redis version and any changes to configurations.
[x] Notify relevant stakeholders, including the development team, of the upgrade schedule and potential impacts on their work.
[x] Create ticket for the next redis upgrade. Be sure to include a timeline for the upgrade so it shows up on the roadmap.

Definition of Done

[x] Redis in Elasticache has been successfully upgraded to version 6.2 or a higher compatible version.
[x] The upgraded environment has been thoroughly tested and verified for performance, stability, and compatibility with existing applications.
[x] Documentation has been updated to reflect the new Redis version and any relevant configuration changes.
[x] Stakeholders have been informed of the successful upgrade and any necessary instructions for their work.
[x] Known future redis upgrades have been added to the roadmap (PM duty)

Timeline

Start Date: [Insert Start Date]
Target Completion Date: [Insert Target Completion Date]

OCTO Objectives:

Objective: O2: Our platforms are the best way to deliver products at VA OKR OKR1: Our platforms hit the "elite" level (as defined by DORA) on Deployment Frequency, Lead Time for Changes, Change Failure Rate, and Time to Restore Service

Dependencies

[List any dependencies or prerequisites for this upgrade]

Risks and Mitigations

[Identify potential risks and provide mitigation strategies]

laineymajor commented 11 months ago

@flooose @Kshitiz-devops @gia-lexa to sync and discuss best next steps for testing re postgres upgrade experience

LindseySaari commented 10 months ago

Chris started to brainstorm around this ticket.

laineymajor commented 10 months ago

[ ] review retro https://easyretro.io/publicboard/pl0f6ivhDjZcj5sjPDTP7mDtDxs2/6c602fa0-b190-4618-88c3-1979a1aafc6e
[ ] what stories/tickets need to be created?

laineymajor commented 10 months ago

This work will be entirely ON HOLD during the code freeze. We will pick this back up once we are in the new year.

department-of-veterans-affairs / va.gov-team