Improve ray-cluster.external-redis.yaml #986
Merged
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.
Why are these changes needed?
The Kuberay pull request #950 discusses using Redis password secrets as environment variables, as described in the Kubernetes documentation.
Specifically, a new environment variable
RAY_REDIS_PASSWORD
is created and assigned a value from a secret:Additionally, the rayStartParams configuration includes a reference to this environment variable:
However, the current Kuberay implementation sets another environment variable,
REDIS_PASSWORD
based on rayStartParams["redis-password"] if the user does not define it.This leads to issues:
REDIS_PASSWORD
environment variable is redundant, as it only points to theRAY_REDIS_PASSWORD
environment variable.To resolve this, it is advisable to set
RAY_REDIS_PASSWORD
asREDIS_PASSWORD
in theray-cluster.external-redis.yaml
to eliminate duplicate environment variables.Related issue number
Checks
kubectl apply -f kuberay/ray-operator/config/samples/ray-cluster.external-redis.yaml kubectl describe $(kubectl get pods -o=name | grep head)