kfctl
kfctl copied to clipboard
Operator Roadmap
- Support remote cluster deployment and "watcher". Additionally Operator should also be able to create the Kube cluster and deploy on that cluster
- Test and certify kfdef for different Cloud providers (public/private)
- Currently the main inputs for kfdef is either parsing from a URL or a local yaml file. Should also have a new helper functions to create kfApp objects using kfdef go type spec.
- Update the reconciler logic to be more robust and able to handle more error situations.
- Add CRD for KFUpgrade
- Add monitoring logic to react on critical stages.
Issue-Label Bot is automatically applying the labels:
Label | Probability |
---|---|
feature | 0.97 |
Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback! Links: app homepage, dashboard and code for this bot.
/assign @Tomcli @adrian555 @animeshsingh
@animeshsingh: GitHub didn't allow me to assign the following users: adrian555.
Note that only kubeflow members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. For more information please see the contributor guide
In response to this:
/assign @Tomcli @adrian555 @animeshsingh
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
@swiftdiaries the roadmap is listed here - and remote deployment is on top of the list of requirements. https://github.com/kubeflow/kfctl/issues/193
- Operator versioning scheme https://github.com/kubeflow/kfctl/issues/284
- fix kfapp directory in operator container. The current
/tmp/
does not work for cases where the CR is updated and other cases. One of them was reported in #242
- update operator to support deployment of multiple kfdef instances (one per namespace assuming).
- some improvement to the watch and reconcile functions:
[ ] change to look up the kubeflow resources based on
ownerReference
[ ] handle other events on kubeflow resources (currently only Delete event is handled) [ ] can the operator bypass some kfApply logic for just a specific kubeflow resource update?
- these are probably common to kfctl cmd and operator [ ] use some mechanism to check/mark the manifest outdated cache [ ] ability to delete the applications if removed from the kfdef configuration file