This repository was archived by the owner on Nov 2, 2025. It is now read-only.
Redis deployment on k8s #7
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Added Redis on k8s
How was this PR tested?
helm install <Release Name> ./feathr-online<Release Name>-feathr-online-redis, then go to its Pod and copy the Pod name.
4. Run `kubectl exec -it -- redis-cli` and enter the Redis Pod. 5. Once you are in, make sure you can run `CONFIG GET maxmemory` to see if Redis is up and running.Does this PR introduce any user-facing changes?