-
Notifications
You must be signed in to change notification settings - Fork 664
[RayService] auth token mode e2e test #4225
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
base: master
Are you sure you want to change the base?
[RayService] auth token mode e2e test #4225
Conversation
|
e2e test ci failed, plz fix it. |
|
Please don't review for now. It's still wip. Will be investigate it further. |
5c05505 to
b4cd1e2
Compare
Signed-off-by: Ryan <ryan980053@gmail.com>
Signed-off-by: Ryan <ryan980053@gmail.com>
95d58a8 to
3145953
Compare
Signed-off-by: Ryan <ryan980053@gmail.com>
Signed-off-by: Ryan Huang <ryankert01@gmail.com>
Removed worker group spec and related verification for auth token propagation in RayService tests. Signed-off-by: Ryan Huang <ryankert01@gmail.com>
|
@400Ping PTAL |
400Ping
left a comment
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.
Over LGTM
Signed-off-by: Ryan Huang <ryankert01@gmail.com>
Refactor test for RayService authentication to improve clarity and maintainability. Signed-off-by: Ryan Huang <ryankert01@gmail.com>
Future-Outlier
left a comment
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.
Can we do something like
g.Expect(rayService.Status.NumServeEndpoints).To(BeNumerically(">", 0),
"RayService should have at least one serve endpoint")to test RayService auth token mode, or this PR is just doing the same thing as the raycluster one.
cc @machichima @JiangJiaWei1103 to review together, thank you
Future-Outlier
left a comment
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.
cc @AndySung320 @justinyeh1995 @400Ping for review if you are interested
Co-authored-by: Han-Ju Chen (Future-Outlier) <eric901201@gmail.com> Signed-off-by: Ryan Huang <ryankert01@gmail.com>
|
@ryankert01 overall LG, and please fix the CI error. |
Co-authored-by: Jun-Hao Wan <ken89@kimo.com> Signed-off-by: Ryan Huang <ryankert01@gmail.com>
Signed-off-by: ryankert01 <ryan980053@gmail.com>
Signed-off-by: ryankert01 <ryan980053@gmail.com>
Signed-off-by: Future-Outlier <eric901201@gmail.com>
Future-Outlier
left a comment
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.
LGTM, thank you!
Signed-off-by: Future-Outlier <eric901201@gmail.com>
| g.Expect(headPod).NotTo(BeNil()) | ||
| LogWithTimestamp(test.T(), "Found head pod %s/%s", headPod.Namespace, headPod.Name) | ||
|
|
||
| // Verify Ray container has auth token env vars |
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.
| // Verify Ray container has auth token env vars | |
| // Verify Ray container has auth token env vars | |
| g.Expect(len(headPod.Spec.Containers)).To(BeNumerically(">", utils.RayContainerIndex), | |
| "Head pod should have at least %d containers", utils.RayContainerIndex+1) |
How about adding a container bounds checking?
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 think current implementation is good enough, thank you for the review!
JiangJiaWei1103
left a comment
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.
LGTM, thanks!
Why are these changes needed?
AuthModeTokenenabledRAY_AUTH_MODEandRAY_AUTH_TOKENenvironment variables are correctly set in head podSecretKeyRefwith the correct keyKey implementation details:
RayServiceSampleYamlApplyConfiguration()and adds auth options and a worker group programmatically (no separate YAML file needed)VerifyContainerAuthTokenEnvVars()helper fromtest/support/ray.goRelated issue number
Related to #4203
Checks