Adopt aggregated apiserver #1002
Labels
enhancement
New feature or request
status/WIP
Issue/PR is being worked on
tep
TiDB Enterprise Platform
Milestone
Feature Request
Is your feature request related to a problem? Please describe:
According to #986 #981 #936 , there are more and more features requires a feasible way to validate, defaults, converse and intercept custom resources.
CRD has been adopted in tidb-operator to define custom resources, but the resources defined by CRD are eventually processed by kube-apiserver. So custom logics upon the CRUD time of resources can only be implemented via hooks (typically webhook), which are tedious to setup and bounded by the extension point provided by kube-apiserver. For example, resource conversion hook is only available in k8s 1.15 or higher.
Describe the feature you'd like:
I propose to adopt aggregated apiserver to host custom resources that requires custom logic that hard to implement for CRD.
Progress
SharedInformer based watchTracked separately in SharedInformer based watch implementation #1059Detailed Usage example and recipeTracked separately in Detailed recipe of aggregated apiserver #1143The text was updated successfully, but these errors were encountered: