Skip to content
This repository has been archived by the owner on May 6, 2022. It is now read-only.

Remove TPR storage backend after Custom Resource Definitions are widely supported #1089

Closed
arschles opened this issue Aug 1, 2017 · 1 comment
Closed

Remove TPR storage backend after Custom Resource Definitions are widely supported #1089

arschles opened this issue Aug 1, 2017 · 1 comment
Labels
third-party-resources

Comments

@arschles
Copy link
Contributor

arschles commented Aug 1, 2017 •
edited
Loading

Since TPRs are deprecated and will soon disappear, we are implementing a Custom Resource Definition (CRD) storage backend (see #987). At some point after Kubernetes 1.8 is released, we'll need to remove the TPR storage backend. This will likely be necessary when we rebase onto a k8s.io/client-go version that no longer has TPR support in its API.

cc/ @nilebox @mengqiy
@arschles arschles mentioned this issue Aug 1, 2017
Closed
@MHBauer
Copy link
Contributor

MHBauer commented Jan 10, 2018

TPR storage is gone as of #1322.

@MHBauer MHBauer closed this as completed Jan 10, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
third-party-resources
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@arschles @MHBauer