-
Notifications
You must be signed in to change notification settings - Fork 436
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[GCS FT] Add e2e tests for configuring GCS FT with annotations #2766
[GCS FT] Add e2e tests for configuring GCS FT with annotations #2766
Conversation
Signed-off-by: kaihsun <[email protected]>
Signed-off-by: kaihsun <[email protected]>
cc @rueian |
podTemplateAC := podTemplateSpecApplyConfiguration(headPodTemplateApplyConfiguration(), | ||
injectRayContainerEnv( | ||
func() []corev1ac.EnvVarApplyConfiguration { | ||
envs := []corev1ac.EnvVarApplyConfiguration{ | ||
*corev1ac.EnvVar().WithName("RAY_REDIS_ADDRESS").WithValue("redis:6379"), | ||
} | ||
if tc.redisPasswordEnv != "" { | ||
envs = append(envs, *corev1ac.EnvVar().WithName("REDIS_PASSWORD").WithValue(tc.redisPasswordEnv)) | ||
} | ||
return envs | ||
}(), | ||
), | ||
) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not simply headPodTemplateApplyConfiguration().Spec.Containers[0].WithEnv(...)
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I at first think this may make code simpler, but it seems not. I removed the helper function to inject env and rayStartParams.
Signed-off-by: kaihsun <[email protected]>
Signed-off-by: kaihsun <[email protected]>
Why are these changes needed?
Old GCS FT API uses annotations to configure GCS FT behavior. This PR adds e2e tests for it.
Related issue number
Checks