-
Notifications
You must be signed in to change notification settings - Fork 2.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
K8s 1.17 compatibility #4822
Comments
Issue Label Bot is not confident enough to auto-label this issue. |
Hey 👋, do we have an overview about what needs to be done to support 1.17 somewhere? |
Hi @openrory @saschagrunert! I would start from there.
|
I've deployed Kubeflow 1.0.0 on the latest Kubernetes master (1f2e1967d1c) via
The first thing I notices is that the
If I change the datadir to something else, then the mysql server comes up. The same applies to the katib mysql server. After that change I'm able to connect to kubeflow. If I now start a notebook, then I'm getting more or less a simliar issue:
|
Seems related #4827 |
@saschagrunert the Notebook Pods rely on the FSGroup being set correctly, in order to set correct permissions on the PVC.
I know for example, that hostPath provisioning doesn't support this. |
Thanks for the hint. I'm not running on an NFS provisioner and then the deployment works seamlessly. I'm continuing my tests now. |
@yanniszark is there a test-suite I can run agains my local cluster? Looks like the tests running here are relying on Google Cloud, right? |
You are or aren't running on the NFS provisioner? I assume you meant "If I'm not running on a NFS Provisioner and then the dpeloyment works seamlessly". If so, Kubeflow doesn't work with it due to mysql containers not starting and functioning properly. #4827 (comment) I'm trying to figure out why, but its extremely slow going. The other error you are seeing with the |
Hi there, Except API version deprecation made from k8s 1.16, is there any other incompatibility features blocking kubeflow deploy? We're currently using kubeflow 1.0 on k8s 1.17 and there wasn't any issues so far. |
Removing from 1.1 because we aren't explicitly targeting support for K8s 1.17 in 1.1. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Issue-Label Bot is automatically applying the labels:
Please mark this comment with 👍 or 👎 to give our bot feedback! |
Tested 1.17 with KF 1.1. We don't see breaking changes there. It should be able to run on 1.17. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
/kind question
/platform k8s
Question:
Hi there,
I really appreciate the work you're putting into Kubeflow. However, we will be moving to k8s 1.17 in a few months: will you be supporting k8s 1.17 anytime soon?
Cheers
The text was updated successfully, but these errors were encountered: