-
Notifications
You must be signed in to change notification settings - Fork 244
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
Improving and modularizing the kclient package #2512
Comments
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
@openshift-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
We recently delivered the Kclient package in odo (#2458), and there are already PRs which are delivering into it (e.g. #2509)
On the odo dev call today, we discussed how we should avoid having kclient becoming one big, monolithic package, like occlient is today. We also discussed that it might be a good idea at some point, start to look at replacing usage of occlient with kclient, and that a modular kclient would help in this regard
Opening this issue for further discussion and eventual implementation.
CC @girishramnani @kadel
The text was updated successfully, but these errors were encountered: