Open vpavlin opened 4 years ago
Issue-Label Bot is automatically applying the labels:
Label | Probability |
---|---|
kind/feature | 0.74 |
Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback! Links: app homepage, dashboard and code for this bot.
Agreed @vpavlin Also, the metadata should use the proper case of "Kubeflow"
Check [KubeFlow Operator documentation]
/area engprod /priority p2
@animeshsingh Any thoughts on 2.? Do you want to keep IBM in there?
Issue-Label Bot is automatically applying the labels:
Label | Probability |
---|---|
area/kfctl | 0.99 |
Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback! Links: app homepage, dashboard and code for this bot.
I'll defer to whoever is developing the operator about what the correct values should be.
I have 2 issues with the recently merged PR for operator CSV
The name of the operator should be
kubeflow-operator
notkfctl
- the whole thing should be probably renamed to keep things consistent with the name of the deploymentRight now the operator shows up as
kfctl
in OperatorHub - https://operatorhub.io/operator/kfctl, it would be best to make things consistent and rename it to kubeflow-operatorWould it make more sense to use
Kubeflow
as a provider of community operator (https://github.com/kubeflow/kfctl/blob/master/deploy/olm-catalog/kfctl/0.1.0/kfctl.v0.1.0.clusterserviceversion.yaml#L92)? Since it is going to be maintained under the Kubeflow project and community, I think that would make perfect sense@animeshsingh @Tomcli @jlewi @pdmack Thoughs?