-
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] Install kuberay operator in buildkite test #1308
[CI] Install kuberay operator in buildkite test #1308
Conversation
Signed-off-by: Archit Kulkarni <[email protected]>
Signed-off-by: Archit Kulkarni <[email protected]>
Signed-off-by: Archit Kulkarni <[email protected]>
Signed-off-by: Archit Kulkarni <[email protected]>
Signed-off-by: Archit Kulkarni <[email protected]>
.buildkite/kind-in-docker.yml
Outdated
- popd | ||
|
||
- pushd helm-chart/kuberay-operator | ||
- helm install kuberay-operator --set image.repository=kuberay/operator --set image.tag=nightly . |
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.
You can also consider using the --wait
option with Helm CLI (https://helm.sh/docs/helm/helm_install/) because kubectl wait
isn't a smart command. Relying solely on kubectl wait
might introduce flakiness. A lot of flakiness in KubeRay CI was introduced by kubectl wait
. You can refer #618 for some examples.
In this PR, what will happen if the CI pipeline executes kubectl wait
after the helm install
command but before the KubeRay operator Pod is created? I guess it will report error.
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.
Good point, let me switch to helm --wait
.
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.
Done.
Signed-off-by: Archit Kulkarni <[email protected]>
Signed-off-by: Archit Kulkarni <[email protected]>
.buildkite/kind-in-docker.yml
Outdated
|
||
# Install KubeRay operator | ||
- pushd ray-operator | ||
- IMG=kuberay/operator:nightly make docker-build |
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.
Or make docker-image
?
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.
Sure, I guess that will skip the unit tests and make the test run faster. Any other reason? Let me go ahead and make that change
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 guess that will skip the unit tests and make the test run faster.
yes
Signed-off-by: Archit Kulkarni <[email protected]>
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
This PR extends the basic kind-in-docker test to install the Kuberay operator. --------- Signed-off-by: Archit Kulkarni <[email protected]>
This PR extends the basic kind-in-docker test to install the Kuberay operator. --------- Signed-off-by: Archit Kulkarni <[email protected]>
Why are these changes needed?
This PR extends the basic
kind
-in-docker test to install the Kuberay operator.Related issue number
Checks