Switch Redis to Valkey

[Samze]

WHAT is this change about?

CAPI Release will switch Redis to Valkey as part of cloudfoundry/capi-release#428 . This is due to Licensing changes in Redis.

Has a cf-deployment including this change passed cf-acceptance-tests?

• YES
• NO

Does this PR introduce a breaking change? Please take a moment to read through the examples before answering the question.

• YES - please choose the category from below. Feel free to provide additional details.
• NO

Types of breaking changes:
3. modifies, deletes or moves the name of a job or instance group in the main manifest

How should this change be described in cf-deployment release notes?

Replace Redis with Valkey in API instance group

Does this PR introduce a new BOSH release into the base cf-deployment.yml manifest or any ops-files?

• YES - please specify
• NO

Does this PR make a change to an experimental or GA'd feature/component?

• experimental feature/component
• GA'd feature/component

Please provide Acceptance Criteria for this change?

bosh ssh api/123

ps -ef | grep valkey

/var/vcap/packages/valkey/valkey-cli -s /var/vcap/data/valkey/valkey.sock

valkey /var/vcap/data/valkey/valkey.sock> keys *
1) "metrics:cc.requests.outstanding.gauge"

What is the level of urgency for publishing this change?

• Urgent - unblocks current or future work
• Slightly Less than Urgent

[jochenehret]

I can merge this when we have a new capi-release with valkey.

[ctlong]

I can merge this when we have a new capi-release with valkey.

Seems like there is one now: https://github.com/cloudfoundry/capi-release/releases/tag/1.184.0