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

Remove TPR resource in favor of CRD #2070

Closed
maciaszczykm opened this issue Jun 28, 2017 · 4 comments
Closed

Remove TPR resource in favor of CRD #2070

maciaszczykm opened this issue Jun 28, 2017 · 4 comments
Assignees

Comments

@maciaszczykm
Copy link
Member

maciaszczykm commented Jun 28, 2017

Quoting from kubernetes/enhancements#95 (comment):

As mentioned in the 1.7 release notes and docs, TPR is now deprecated and we plan to remove it in 1.8. Users should switch to CRD during the 1.7 timeframe.

Please comment on the tracking issue for removal if you have any questions or concerns.

Should we remove all our customization related to them?


Tracker on core repository: kubernetes/kubernetes#48152


During migration to CRD we should also add detail page which is missing for TPR instances at the moment (more details in #1504).

@enisoc
Copy link
Member

enisoc commented Jun 28, 2017

I imagine it would make sense to port any TPR customizations to CRD, which is essentially the next version of TPR.

@maciaszczykm
Copy link
Member Author

@enisoc It is good news for us. I did not yet read full discussion, so thank you for you input.

@kenan435
Copy link
Contributor

I had a short look at this. I would suggest keeping TPR and introducing CRD side by side for the k8s 1.7 release, since that is the approach the community is taking. Will will then phase out TPR's for 1.8.

@maciaszczykm maciaszczykm changed the title Remove third party resources? Remove TPR resource in favor of CRD Jul 18, 2017
@maciaszczykm maciaszczykm self-assigned this Sep 7, 2017
@maciaszczykm maciaszczykm removed their assignment Sep 28, 2017
@maciaszczykm maciaszczykm self-assigned this Oct 18, 2017
@maciaszczykm
Copy link
Member Author

We will track from #2493.

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

No branches or pull requests

3 participants