Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

how to upgrade smoothly from v1alpha1 to v1alpha2? #697

Closed
u2takey opened this issue Jun 25, 2018 · 2 comments
Closed

how to upgrade smoothly from v1alpha1 to v1alpha2? #697

u2takey opened this issue Jun 25, 2018 · 2 comments

Comments

@u2takey
Copy link
Contributor

u2takey commented Jun 25, 2018

After I upgrade crd of tfjob from v1alpha1 to v1alpha2, all tfjobs of v1alpha1 lost. Is there a way to upgrade smoothly from v1alpha1 to v1alpha2 without affecting old user's experience? ( In kubernetes, they have internal and external version of resources for that ? )

@gaocegege
Copy link
Member

Hi @u2takey

This is a good question. When we designed the v1alpha2, we consider it a breaking change. We will keep compatibility after v1alpha2. And I will check if there is any way to keep TFJobs.

@jlewi
Copy link
Contributor

jlewi commented Jul 3, 2018

I think this is a K8s issue to the extent Kubernetes doesn't allow us to have multiple versions of a CRD simultaneously. I believe this is fixed in 1.11.

kubernetes/enhancements#544

I think we can close this issue.

On K8s versions of 1.11 and later we can simultaneously support multiple versions of a CRD. I don't think its worth it to try to improve the experience on older versions of K8s.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants