You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 17, 2023. It is now read-only.
I've heard the Operator, like kfctl, does not clean up no-longer-wanted resources when upgrading a kubeflow (like a component which has disappeared in the latest version will still exist in the Kubernetes cluster after kubeflow upgrade to latest version).
Could you confirm?
If so, is it planned to add such support in the Operator or will still run using kustomize as its core which does not allow it?
The text was updated successfully, but these errors were encountered:
I've heard the Operator, like kfctl, does not clean up no-longer-wanted resources when upgrading a kubeflow (like a component which has disappeared in the latest version will still exist in the Kubernetes cluster after kubeflow upgrade to latest version).
Could you confirm?
If so, is it planned to add such support in the Operator or will still run using kustomize as its core which does not allow it?
The text was updated successfully, but these errors were encountered: