[Feat] [history server] Enable running the history server outside the K8s cluster #4404
+174
−39
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?
To speed up development iteration without rebuilding the history server image for every code change, we enable the history server to run outside the Kubernetes cluster (e.g., local kind cluster) while interacting with in-cluster resources (e.g., the live Ray cluster).
Key Changes
--use-kubernetes-proxyfor enabling the Kubernetes API server proxy mode:KUBECONFIGenv var or~/.kube/config)Related issue number
Closes #4403.
Tutorial and Test Result
I'll provide a video tutorial here.
Checks