Skip to content

Conversation

@JiangJiaWei1103
Copy link
Contributor

@JiangJiaWei1103 JiangJiaWei1103 commented Jan 16, 2026

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

  • Add --use-kubernetes-proxy for enabling the Kubernetes API server proxy mode:
    • Automatically load kubeconfig from default locations (KUBECONFIG env var or ~/.kube/config)
    • Route live cluster requests through the API server proxy subresource to in-cluster services

Related issue number

Closes #4403.

Tutorial and Test Result

I'll provide a video tutorial here.

Checks

  • I've made sure the tests are passing.
  • Testing Strategy
    • Unit tests
    • Manual tests
    • This PR is not tested :(

Signed-off-by: JiangJiaWei1103 <waynechuang97@gmail.com>
Signed-off-by: JiangJiaWei1103 <waynechuang97@gmail.com>
Signed-off-by: JiangJiaWei1103 <waynechuang97@gmail.com>
@Future-Outlier
Copy link
Member

cursor review

Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Signed-off-by: JiangJiaWei1103 <waynechuang97@gmail.com>
…ster

Signed-off-by: JiangJiaWei1103 <waynechuang97@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Feature] [history server] Develop the history server outside cluster

2 participants