Deployment Working Group

[Juana Nakfour]

Hi Everyone,

As we discussed in the last community meeting, KF Deployment WG has not started it yet. I wanted to see if we have a list of group members who volunteered before, and why it has not started yet. Also what would be the charter for this Working Group?

Thanks

Juana

[Mathew Wicks]

I believe the charter is on the `kubeflow/community` repo: https://github.com/kubeflow/community/tree/master/wg-deployment

If there has been no meetings, I would ask one of the leads to clarify what is happening with the WG:

• Yao Xiao (@PatrickXYS), AWS
• Animesh Singh (@animeshsingh), IBM
• Igor Mameshin (@mameshini), Agile Stacks
• Vaclav Pavlin (@vpavlin), Red Hat
• Yannis Zarkadas (@yanniszark), Arrikto

However, I think there are some decisions to be made around the future of `kfctl`,  which is the only code owned by the Deployment WG.

Kfctl seems to not be used after the release of Kubeflow 1.3, given the `kubeflow/manifests` changes https://github.com/kubeflow/manifests/issues/1735

[Juana Nakfour]

Hi Mathew,

Thank you very much for the information, it is very helpful. So it is still not clear to me, for after KF 1.3, the installation instructions on Kubernetes here (https://www.kubeflow.org/docs/started/k8s/kfctl-k8s-istio/) refer to using kfctl, how will that change? What is replacing kfctl build/apply ? Are we moving to "kubectl apply -k" ? 

Thanks

Juana

--
You received this message because you are subscribed to the Google Groups "kubeflow-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubeflow-discu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubeflow-discuss/0d7ddd8e-6812-426e-89e0-8713ab5d034an%40googlegroups.com.

[Yannis Zarkadas]

Hi Juana, these are good questions.

> What is replacing kfctl build/apply ? Are we moving to "kubectl apply -k" ?

From the Manifests WG side, we will provide instructions for installing the Kubeflow components and common services with kubectl + kustomize.
Then, distributions can choose to follow the simple native kustomize way, or use their own tool that works with kustomizations.

Please also take a look at the release tracking issue for the complete list of steps:

https://github.com/kubeflow/manifests/issues/1777

https://groups.google.com/u/1/g/kubeflow-discuss/c/sCKfoCE4cCs