We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
during gcs ft development, i realized compatibility test is not using the right kuberaty build image. This need to be fixed.
manually checked the kuberay operator & apiserver images after deployed in local kind-based k8s cluster.
I am working on a patch for this.
The text was updated successfully, but these errors were encountered:
patch is in #294
Sorry, something went wrong.
@wilsonwang371 Can we split the bug fix and HA stuff? Some HA features are only available in master. We may need more time to merge the PR.
ok. I will do a separate patch for this
The patch is under review. #327
No branches or pull requests
Search before asking
KubeRay Component
ci
What happened + What you expected to happen
during gcs ft development, i realized compatibility test is not using the right kuberaty build image. This need to be fixed.
Reproduction script
manually checked the kuberay operator & apiserver images after deployed in local kind-based k8s cluster.
Anything else
I am working on a patch for this.
Are you willing to submit a PR?
The text was updated successfully, but these errors were encountered: