Closed laineymajor closed 12 months ago
We are upgrading (hopefully) a shorter/simpler upgrade path! Fingers crossed. Chris continuing to research.
The update to redis 6 or 7 (see below) should be relatively straight-forward because backward compatibility has always been a design principle of the Redis project. The following points need to be addressed before moving to the actual upgrade.
terraform plan
aws elasticache create-snapshot \
--cache-cluster-id dsva-vagov-dev-sidekiq-002 \
--snapshot-name sidekiq-dev-$(date +'%Y%m%d%H%M%S')`
taken from main story https://app.zenhub.com/workspaces/platform-product-team-633af4074573d06c3cda142a/issues/gh/department-of-veterans-affairs/va.gov-team/64051
redis.yml
in the vets-api repo. @LindseyHattamer do you see this the same way?This is the documentation https://vfs.atlassian.net/wiki/spaces/TT1/pages/2806808593/Redis+Update
Seems like this can be closed since we have the proper documentation... correct @flooose ?
I'm of the opinion that it can be closed. Is it worth getting a second developer opinion on this though? Maybe there's something I failed to consider? @Kshitiz-devops or @LindseySaari maybe?
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 Conduct a thorough assessment of the existing Redis configuration and dependencies within our development environment.