-
Notifications
You must be signed in to change notification settings - Fork 402
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
[CI] Verify kubectl in kind-in-docker step #1305
Conversation
Signed-off-by: Archit Kulkarni <[email protected]>
Next steps for followup PRs:
The second step is currently blocked by the following issue. Every time we delete the kind cluster and start a new kind cluster on the same machine, it fails with
|
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. Would you mind opening an issue to track #1305 (comment)? Thanks!
Signed-off-by: Archit Kulkarni <[email protected]>
The newly added test passed: https://buildkite.com/ray-project/ray-ecosystem-ci-kuberay-ci/builds/1205#0189db69-4db3-4bbe-b56d-77cae3af83a3 The other tests are unrelated. Merging |
This PR configures kind to allow kubectl to connect to it. This is a prerequisite for testing sample YAML files end-to-end in Buildkite. The configuration is copied from @simon-mo's work in ray-project/ray#22035. --------- Signed-off-by: Archit Kulkarni <[email protected]>
This PR configures kind to allow kubectl to connect to it. This is a prerequisite for testing sample YAML files end-to-end in Buildkite. The configuration is copied from @simon-mo's work in ray-project/ray#22035. --------- Signed-off-by: Archit Kulkarni <[email protected]>
Why are these changes needed?
This PR configures
kind
to allowkubectl
to connect to it. This is a prerequisite for testing sample YAML files end-to-end in Buildkite. The configuration is copied from @simon-mo's work in ray-project/ray#22035.Related issue number
Checks