Website: Is kubeflow 1.0 compatible with kubernetes 1.19 ?

[alforik]

Is kubeflow 1.0 compatible with kubernetes 1.19 ?

Page https://www.kubeflow.org/docs/started/k8s/overview/ does not show about kubernetes 1.19 version

[issue-label-bot[bot]]

Issue-Label Bot is automatically applying the labels:

| Label | Probability |
| ------------- | ------------- |
| kind/question | 0.81 |
| area/docs | 1.00 |

Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!
Links: app homepage, dashboard and code for this bot.

[8bitmp3]

@alforik Hi.

@joeliedtke @Bobgy @animeshsingh @jlewi @PatrickXYS @RFMVasconcelos @alfsuse Have you tested KF 1.0 with k8s 1.19 by any chance?

On a similar note:

Which k8s versions is KF 1.1 compatible with? We can then update the table:

Update: Since "The recommended Kubernetes version is 1.14. Kubeflow has been validated and tested on Kubernetes 1.14", that covers k8s 1.14-1.16 as "compatible", I assume.

[alfsuse]

Thanks for this @8bitmp3! I think 1.18 and 1.17 have been used by the community for at least a couple of months so I would assume both maybe can be move to "compatible"... for 1.19 I'm going to test it and will report here my feedbacks asap.
I was wondering if we have already discussed a better way to test KF with K8's version in a more structured way...

[PatrickXYS]

In the future, we need to rely on Test-infra do periodical test against different versions of Kubeflow and Kubernetes.

That should be a better maintainable way for compatibility matrix.

We should not rely on user report to establish compatibility matrix

[Bobgy]

Also we need to add a Kubeflow 1.1 column

[8bitmp3]

@PatrickXYS I agree that there should be a automated way of doing this. Don't know how to do this, but we'll figure it out.

Let's update the table on the site page to include KF v1.1 using the existing methods.

Would you be OK if we replicate the KF v1.0 column for v1.1? Let us know if there are any issues with K8s v1.17-1.18 @joeliedtke @Bobgy @animeshsingh @jlewi @PatrickXYS @RFMVasconcelos @alfsuse @adrian555 @Tomcli @IronPan @numerology @neuromage @Jeffwan @aronchick @shawnzhu @rmgogogo @cliveseldon @knkski

[alfsuse]

No issue I'm aware for 1.17 and 1.18 (for minikube and other local deployment may require some flags when start clusters.. in case of minikube I've already documented it)

[8bitmp3]

fyi Related:

https://github.com/kubeflow/website/issues/2206
https://github.com/kubeflow/manifests/issues/1543 (kubeflow/manifests)
https://github.com/kubeflow/kfserving/issues/1070 (kubeflow/kfserving)
PR https://github.com/kubeflow/manifests/pull/1558

kfctl v1.1
K8s v.18+

[Bobgy]

+1 to replicating the 1.0 column first

[8bitmp3]

Would you be OK if we replicate the KF v1.0 column for v1.1? Let us know if there are any issues with K8s v1.17-1.18 @joeliedtke @Bobgy @animeshsingh @jlewi @PatrickXYS @RFMVasconcelos @alfsuse @adrian555 @Tomcli @IronPan @numerology @neuromage @Jeffwan @aronchick @shawnzhu @rmgogogo @cliveseldon @knkski

@eedorenko @sudivate - looping you in to keep you updated

[PatrickXYS]

Would you be OK if we replicate the KF v1.0 column for v1.1

Sounds good to me

[8bitmp3]

Going back to the original question, how should we proceed with K8s v1.19?

As @alforik said:

Page https://www.kubeflow.org/docs/started/k8s/overview/ does not show about kubernetes 1.19 version

@joeliedtke @Bobgy @animeshsingh @jlewi @PatrickXYS @RFMVasconcelos @alfsuse @adrian555 @Tomcli @IronPan @numerology @neuromage @Jeffwan @aronchick @shawnzhu @rmgogogo @cliveseldon @knkski @eedorenko @sudivate @jlewi

While you and your teams are testing, maybe we can add "no known issues" for k8s 1.19 under KF 1.0 and KF 1.1?

no known issues: the combination has not been fully tested but there are no reported issues

I can add a row for k8s 1.19 in a jiffy.

WDYT? Thank you all

[PatrickXYS]

Looks like folks are reporting the seldon is not compatible with k8s 1.18, so if the manifest is using seldon, you should expect to see some issue on 1.18

https://github.com/kubeflow/website/issues/2207

[Bobgy]

KFP is also not fully functional in 1.17+, see https://github.com/kubeflow/pipelines/issues/4627

But caching is alpha level feature, so we can say partially compatible.

[jlewi]

Should we really be making claims about things we aren't testing?

I think we need to rethink how we maintain this compatibility matrix and installation instructions.

[jlewi]

See: #2293

I think we need to move away from talking about "Kubeflow" as a whole and instead start talking about either

1. individual Kubeflow applications (e.g. KFP, notebooks, etc...)
2. Specific bundles/distributions of Kubeflow (e.g. GCP, AWS, etc...)

Questions about version compatibility should be the responsibility of the owners of the bundle and application respectively.