-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Action items for adoption of Spark Kubernetes Operator in Kubeflow #1928
Comments
this looks complete, let's move this forward |
To share more information about repo config and |
Great, thank you, James! |
@andreyvelich any update on this |
We are working with @zijianjoy and Google team to transfer Spark Operator repository to Kubeflow GitHub. |
@andreyvelich do we know when will the work start on this? |
Once we transfer the Spark Operator repository to Kubeflow the team will start work on the items to make a release. |
I am not able to sign in to kubeflow slack. Please share the steps. Thank you |
@gangahiremath Please follow this link to join Kubeflow Slack: https://www.kubeflow.org/docs/about/community/#kubeflow-slack |
sure @andreyvelich |
We have this item in our design doc: https://docs.google.com/document/d/1rCPEBQZPKnk0m7kcA5aHPf0fISl0MTAzsa4Wg3dfs5M/edit#heading=h.sb3itb5lb4jl. |
The repo is migrated and renamed to https://github.com/kubeflow/spark-operator. |
This link is helpful for setting up tide and prow: https://github.com/kubeflow/community/blob/master/repository-setup.md#setup-prow |
With this move what's the name of the helm repo? The existing repo doesn't work
|
Nvm, I found the new repo link
|
Hello team, you might want to attend to repo migration side effect in #1926. |
Update to the spark-website repo: apache/spark-website#553 |
Since all of the items have been completed, we can close it. |
Related: kubeflow/community#648, kubeflow/community#672, #1892
We have to follow these action items to transfer Spark Operator to Kubeflow.
tide
for the new repository.Please let me know if I missed something @jbottum @james-jwu @zijianjoy.
Excited to see this moving forward 🎉
The text was updated successfully, but these errors were encountered: