Kubeflow: Expecetd timeline for support of Kubernetes 1.16

[indranilr]

/kind question

Question:
What is the expected timeline (I am assuming it will be a upcoming minor release) for Kubernetes 1.16 version support in Kubeflow ? 0.7 documentation suggests support till version 1.15.

[issue-label-bot[bot]]

Issue-Label Bot is automatically applying the labels:

| Label | Probability |
| ------------- | ------------- |
| kind/question | 0.63 |

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

[jtfogarty]

/area usage
/priority p2

[yanniszark]

I would expect the only roadblock for 1.16 to be the deprecated extensions apiVersion for Deployments, StatefulSets etc.
Doing a quick grep in the v0.7-branch of manifests reveals such apiVersion only in the Ingress resources of GCP and AWS.

/cc @Jeffwan @jlewi you may want to open issues for transitioning the Ingresses to networking.k8s.io/v1.

I would expect the on-prem configs, such as the existing_arrikto config to work as they are.
For the GCP, AWS configs, I expect that the Ingress creation will not succeed because it uses the extensions/v1beta1 API.

[jlewi]

Duplicate of kubeflow/manifests#375