-
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.22 and Notebooks WG #6353
Comments
Hi @kimwnasptd At ODH we want to deploy Notebook Controller on Openshift 4.9 (Kubernetes 1.22) so we would like to contribute to support K8S 1.22. Is there any PR in progress? If not, we can start with any of the outstanding items. |
Great to hear @samuelvl! I'll open a distinct issue for the Notebook Controller to track the required effort there. |
Do you need any help? |
/area jupyter |
Hi @mvoitko, first of all hope you are safe. Yes, we have some more work items for this effort. I'll create some more subissues for the different components. You can take a look at the overview in the first comment. Do you have any preference on where you could help? Golang controllers, Python backends, YAML manifests? |
Hi there, I have some availability to help with 1.22 compatibility. I believe that some of our other team members will reach out as well. |
I am also available to help on 1.22 compatibility. The sooner we upgrade to 1.22 syntax, the better! |
Opened a PR for updating Tensorboard CRD to |
Getting 1.22 support for Kubeflow is very important, but are there any known issues with 1.23 that should be called out for addressing as well? The reason for asking is that 1.22 goes end of active support at the end of Aug and EOL at the end of Oct based on https://endoflife.date/kubernetes. |
Awesome to see so much help on this one! I've also created two more issues to handle PodDefaults #6428 and the crud web apps (backend) #6427. The later should be an easier task. I'll be working also in parallel on using KinD within the Argo Workflows we use for E2E testing, so that we can also do some basic tests on K8s 1.22. EKS does not yes support K8s 1.22 so we'll have to compromise. |
How likely is it that support for 1.22 will be in the next release of Kubeflow and within the planned schedule? 1.21 is reaching end of life at the end of June and Kubeflow 1.6 is planned to be released on 20th July so there's a gap of about of month when you can only use Kubeflow on an unsupported Kubernetes version. Is there any possibility of a patch to make Kubeflow install-able on Kubernetes 1.22 to fill the gap? |
@chlun1 The community has been committed to delivering support for 1.22 in Kubeflow 1.6 and I will let @annajung and @kimwnasptd comment as well. Kubeflow 1.6 target release date is in August. The Kubeflow Working Groups may need some help. Are there folks on your team that might be able to contribute, perhaps in testing ? Which cloud environment are you running in or Kubeflow distribution do you plan to use ? |
@jbottum We are running Kubeflow on Azure. We can possibly help in testing on Azure. |
@jbottum I'm using Kubeflow pipelines and UI on GKE 1.21 right now and can also help test. GCP will automatically upgrade my GKE clusters from 1.21 to 1.22 at the end of this year according to their release schedule. So the target August release for Kubeflow 1.6 gives my team a good amount of time to upgrade both our clusters and Kubeflow. We don't want to be in a situation where our clusters are automatically upgraded to 1.22 and we have no compatible Kubeflow release or time to upgrade. 🙏 |
While for KF 1.5 release we are targeting K8s 1.20 and 1.21, I'm starting this tracking issue on the work items required for supporting K8s 1.22. Related issue #6098
This is an overview of the items I have in mind:
v1
forSubjectAccessReviews
https://kubernetes.io/docs/reference/using-api/deprecation-guide/#subjectaccessreview-resources-v122v1
forCustomResourceDefinitions
https://kubernetes.io/docs/reference/using-api/deprecation-guide/#customresourcedefinition-v122preserveUnknownFields: false
in the CRD, for upgrades betweenv1beta
andv1
CRDs https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/#field-pruningIgnore
toFail
https://kubernetes.io/docs/reference/using-api/deprecation-guide/#webhook-resources-v122. This is a good thing, but we need to double check edge cases scenarios with use of our PodDefaultsThese are the work items I have in mind. The first two are easy to implement. The only ones that might need more care are the CRDs and testing the webhook.
cc @kubeflow/wg-notebooks-leads
The text was updated successfully, but these errors were encountered: