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

[Announcement] Decoupling SDK framework to sigs.k8s.io/apiserver-runtime #541

Closed
yue9944882 opened this issue Sep 28, 2020 · 4 comments
Closed
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@yue9944882
Copy link
Member

both this repo and kubebuilder are founded to address the pain-points in developing extensions for kubernetes. by kubebuilder's philosophy, to reduce the "heavy" code-generation and copy-pasting, an SDK framework dedicated for developing kubernetes controller named controller-runtime was incubated and now getting mature and popular in the community. to follow the success of controller-runtime we're incubating an SDK framework for developing aggregated-apiserver named apiserver-runtime to similarly pack the complexity of underlying kubernetes sources into a user-friendly layer of abstraction. w/ the help of the new apiserver-runtime, we're even capable of minimizing the source of an aggregated apiserver to one line.

we will be migrating onto this new SDK framework together w/ bumping k8s dependencies to 1.19. it will be breaking some compatibility for existing repos but we will provide a document for doing the manual migration to make it work. the good news is that the interfaces from apiserver-runtime will be fairly intuitive and hopefully we can share the joy of landing onto the new runtime 🙂.

besides getting rid of code-generation, we will also promote the extensibility of custom storages into the new runtime, e.g. mysql storage is already landed and there will soon be more packages supporting more kinds of storage layers..

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

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

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 27, 2020
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 26, 2021
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/close

@k8s-ci-robot
Copy link
Contributor

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/close

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

3 participants