Jeremy Lewi

@swiftdiaries this is the issue tracking trying to come up with a better way of testing kfctl.

Should we punt this to post 1.0? I don't think anyone is working on this and I'm not sure we will have cycles to fix it before we want to...

Also I think the direction we want to move is kfctl should mostly be focused on helping users build manifests and not applying/deleting them. apply/delete(#293) should mostly be synonymous with...

Bump to P0 because this must land in 0.7

@gabrielwen Any update on this do you have an ETA? Based on some of our discussions * kubeflow/kubeflow#4106 uses errors to determine whether apply is complete or needs to be...

reconcile semantics will be needed for the kfctl operator; see kubeflow/kubeflow#4570.

/lifecycle frozen Related to kubeflow/kfctl#193 operator roadmap

Bump to P1. We need this to better handle errors like kubeflow/manifests#806 Right now if a single resource (e.g. certmanager) takes a long time to start we wait until it...

I would not expect manifests and kfctl to be on different release cyles.

Here's my initial thought. An E2E test probably looks like the folling 1. Build kfctl 1. Deploy v0X 1. Test Kubeflow is ready 1. Upgrade Kubeflow 1. Verify Kubeflow is...