Open juliusvonkohout opened 4 days ago
(Orthogonal question, but why is this called Kubeflow Platform
and includes Manifests and Security WGs in it?
Especially once we'll have the repos broken up after the discussion in https://github.com/kubeflow/kubeflow/issues/7549#issuecomment-2181054114
Similar to what @kimwnasptd said, it's hard to imagine that "Kubeflow Platform" should not also involve the distribution owners? I am not sure we should be calling the meetings "Kubeflow Platform" if they are only referring to Manifests/Security WGs.
(Orthogonal question, but why is this called
Kubeflow Platform
and includes Manifests and Security WGs in it?Especially once we'll have the repos broken up after the discussion in kubeflow/kubeflow#7549 (comment)
@kimwnasptd The main motivation is to identify contributors who can maintain Kubeflow Platform components. E.g. Kubeflow Manifests, Profile Controller, KFAM, Central Dashboard, etc. So if users have any questions about these components they can join the Kubeflow Platform community calls. Since @juliusvonkohout was driving the security effort around Kubeflow ecosystem, he included the security roadmap to the Kubeflow Platform discussion.
From my perspective, distributions should certainly join those meetings since they are main consumers of Kubeflow Manifests.
Describe your issue
Tracker for 1.10 @rimolive @kimwnasptd Follow up of https://github.com/kubeflow/manifests/issues/2598 and https://github.com/kubeflow/manifests/issues/2592
Organizational:
Security external:
Security JWTs:
Rootless Kubeflow & Istio:
Rest: