Extending the Kubernetes API in-process

1. A method comprising:

compiling, by a processing device, each of one or more custom resource definition (CRD) controllers that are created in a cluster at run-time into a respective isolation module to generate one or more isolation modules, wherein the one or more isolation modules are all hosted in a service; and

in response to detecting an API event serviced by a CRD controller of the one or more CRD controllers, executing a respective isolation module of the CRD controller.

2. The method of claim 1 , further comprising:

updating an informer with controller metadata of each of the one or more CRD controllers, wherein the informer performs the monitoring for API events serviced by each of the one or more CRD controllers based on the controller metadata of each of the one or more CRD controllers.

3. The method of claim 2 , further comprising:

in response to detecting an API event serviced by a CRD controller of the one or more CRD controllers, transmitting an indication of the CRD controller to an isolation module interface, wherein the isolation module interface executes the respective isolation module of the CRD controller using a set of APIs that facilitate input/output operations between each of the one or more isolation modules and the service.

4. The method of claim 1 , wherein each of the one or more isolation modules are isolated from the service.

5. The method of claim 1 , wherein the service comprises a controller-manager service executing on a control plane of a container orchestration engine.

6. The method of claim 1 , wherein the service comprises a service that is separate from a controller-manager service executing on a control plane of a container orchestration engine.

7. The method of claim 1 , further comprising:

monitoring resource consumption of a pod on which the one or more isolation modules are hosted using a vertical autoscaler; and

in response to determining that additional resources are needed, allocating additional resources to the pod.

8. A system comprising:

a memory; and

a processing device, operatively coupled to the memory, the processing device to:

in response to creation of a CRD controller, compile the CRD controller into a respective isolation module, the respective isolation module hosted on a service along with one or more other isolation modules; and

in response to detecting an API event serviced by the CRD controller, executing, by an isolation module interface, the respective isolation module of the CRD controller to transition the CRD controller from an inactive state to an active state.

9. The system of claim 8 , wherein the controller metadata of the CRD controller indicates API events serviced by the CRD controller.

10. The system of claim 9 , wherein the processing device is further to:

in response to detecting an API event serviced by the CRD controller, transmit an indication of the CRD controller to the isolation module interface, wherein the isolation module interface executes the respective isolation module of the CRD controller using a set of APIs that facilitate input/output operations between the isolation module and the service.

11. The system of claim 8 , wherein the isolation module isolates the CRD controller from the service.

12. The system of claim 8 , wherein the service comprises a controller-manager service executing on a control plane of a container orchestration engine.

13. The system of claim 8 , wherein the isolation module comprises a web assembly module (WASM).

14. The system of claim 8 , wherein the processing device is further to:

monitor resource consumption of a pod on which the isolation modules are hosted using a vertical autoscaler; and

in response to determining that additional resources are needed, allocate additional resources to the pod.

15. A non-transitory computer readable medium, having instructions stored thereon which, when executed by a processing device, cause the processing device to:

in response to creation of a CRD controller, compile, by the processing device, the CRD controller into a respective isolation module, the respective isolation module hosted on a service along with one or more other isolation modules; and

update an informer of the service with controller metadata of the CRD controller, the informer to monitor for application program interface (API) events serviced by the CRD controller based on the controller metadata.

16. The non-transitory computer readable medium of claim 15 , wherein the controller metadata of the CRD controller indicates API events serviced by the CRD controller.

17. The non-transitory computer readable medium of claim 16 , wherein the processing device is further to:

in response to detecting an API event serviced by the CRD controller, transmit an indication of the CRD controller to an isolation module interface, wherein the isolation module interface executes the respective isolation module of the CRD controller using a set of APIs that facilitate input/output operations between the isolation module and the service.

18. The non-transitory computer readable medium of claim 17 , wherein the isolation module isolates the CRD controller from the service.

19. The non-transitory computer readable medium of claim 17 , wherein the service comprises a controller-manager service executing on a control plane of a container orchestration engine.

20. The non-transitory computer readable medium of claim 17 , wherein the isolation module comprises a web assembly module (WASM).