-
Notifications
You must be signed in to change notification settings - Fork 661
[WIP] Historyserver beta version #4187
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?
Conversation
Signed-off-by: KunWuLuan <[email protected]>
Signed-off-by: KunWuLuan <[email protected]>
Signed-off-by: KunWuLuan <[email protected]>
Signed-off-by: KunWuLuan <[email protected]>
|
@KunWuLuan thanks for the PR, can you share any steps to follow to test the changes? |
71132f8 to
dc2f070
Compare
9ffd24a to
4042df9
Compare
17243dd to
d67d054
Compare
Signed-off-by: KunWuLuan <[email protected]>
Signed-off-by: KunWuLuan <[email protected]>
d67d054 to
b97507f
Compare
Signed-off-by: KunWuLuan <[email protected]>
3e1df23 to
7462b93
Compare
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.
probably need a README like this to test it locally https://github.com/ray-project/kuberay/blob/master/ray-operator/DEVELOPMENT.md
thank you!
|
@KunWuLuan can we split this PR into smaller ones? Maybe one PR for event collector, another for logging collector and one for history server? |
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.
Hi, I did these changes in my local diff.txt
and this work in my local.
- build the history server and load it to kind
kind create cluster --image=kindest/node:v1.24.0
# start the kuberay operator
cd historyserver
make localimage
docker tag historyserver:latest rayproject/historyserver:latest
kind load docker-image rayproject/historyserver:latest- create minio, service account, history server, and ray cluster
kubectl apply -f minio.yaml
kubectl apply -f sa.yaml
kubectl apply -f raycluster.yaml
kubectl apply -f historyserver.yaml- Accessing HistoryServer
kubectl port-forward svc/historyserver 8080:30080
open http://localhost:8080/#/overview
- Accessing Minio Console
kubectl port-forward svc/minio-service -n minio-dev 9001:9001
open http://localhost:9001/browser
# account: minioadmin
# password: minioadmin
Why are these changes needed?
Related issue number
Checks