Reusable client/server infrastructure #13541
Labels
kind/design
Categorizes issue or PR as related to design.
lifecycle/rotten
Denotes an issue or PR that has aged beyond stale and will be auto-closed.
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
sig/api-machinery
Categorizes an issue or PR as relevant to SIG API Machinery.
Forked from #8190, #8132, #6363, #2742, #2098, and probably other issues.
We need to choose/build a reusable client/server infrastructure, either based on apiserver or something new, such as grpc. While many components will slave off the core apiserver, some won't, and we also want to support federated apiservers.
cc @kubernetes/goog-csi
The text was updated successfully, but these errors were encountered: