V1beta1 is done now, so we can start deprecating the V1alpha API and controller logic.
Keeping v2alpha2 for now?
I would like to delete both if possible. Deleting v1alpha1 seems like a good start since we have already removed it from the kubeflow components.
Do you see value in keeping v1alpha2? The only reason I have is that people might still be using it. But switching to v1beta1 is fairly trivial (just need to update the API version).
I have the same opinion.
@jlewi Shall we delete v1alpha1 and v1alpha2 versions now? AS @richardsliu , It is trivial to switch version to v1beta1
I think we could keep v1alpha2 in 0.4, since maybe there are some users still using it. We can claim that we will deprecate it in the next release (1.0).
Talked to @jlewi. We will keep v1alpha2 until all our examples have been updated to v1beta1.
Another reason: Kubeflow ML Pipelines is also using v1alpha2, so we cannot deprecate it right now.
Most helpful comment
I would like to delete both if possible. Deleting v1alpha1 seems like a good start since we have already removed it from the kubeflow components.
Do you see value in keeping v1alpha2? The only reason I have is that people might still be using it. But switching to v1beta1 is fairly trivial (just need to update the API version).