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

Switch from legacy client to clientsets and start using new API endpoints #13422

Closed
mfojtik opened this issue Mar 17, 2017 · 3 comments
Closed
Assignees
Labels
area/techdebt kind/post-rebase lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/P2
Milestone

Comments

@mfojtik
Copy link
Contributor

mfojtik commented Mar 17, 2017

Ref: #13412

With API groups merged, we should start switching from the legacy API client (pkg/client) to a generated clientsets and start hitting the new API endpoints.
This will require updating the client sets and we should probably start with this work early after 1.6 lands.

@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 9, 2018
@0xmichalis
Copy link
Contributor

@mfojtik is this fixed now?

@soltysh
Copy link
Contributor

soltysh commented Feb 13, 2018

Yeah, all the bits are in.
/close

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/techdebt kind/post-rebase lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/P2
Projects
None yet
Development

No branches or pull requests

5 participants