Metadata driven static determination of controller availability
Systems and methods for determining if a controller that can service a custom resource (CR) exists are disclosed. The method includes evaluating a custom resource (CR) and determining whether a controller among a plurality of controllers can service the CR based on filter metadata associated with each of the plurality of controllers.
1. A method comprising:
evaluating a custom resource (CR); and
comparing, by a processing device, definitions of the CR with filter metadata from each of a plurality of controllers to determine whether a controller among the plurality of controllers can service the CR based on the filter metadata associated with each of the plurality of controllers, wherein the definitions of the CR comprise an object type of the CR.
2. The method of claim 1 , further comprising:
in response to determining a controller among a plurality of controllers can service the CR, providing an alert indicating that there is the controller that can service the CR.
3. The method of claim 1 , wherein the filter metadata of each of the plurality of controllers comprises one or more class filters indicating classes of the object type that the controller is to observe and reconcile, and the definitions of the CR further comprise one or more class annotations indicating one or more classes of the object type of the CR that the CR is to operate with.
4. The method of claim 1 , further comprising:
in response to determining that none of the plurality of controllers have filter metadata matching the definitions of the CR, determining whether any of the plurality of controllers have filter metadata partially matching the definitions of the CR.
5. The method of claim 1 , further comprising:
obtaining each of a plurality of deployments in response to evaluating the CR and reading the filter metadata of each of the plurality of controllers from a corresponding one of the plurality of deployments.
6. The method of claim 1 , further comprising:
generating for each of the plurality of controllers, an application program interface (API) to provide the filter metadata for that controller in response to a request.
7. A system comprising:
a memory; and
a processing device operatively coupled to the memory, the processing device to:
evaluate a custom resource (CR); and
compare definitions of the CR with filter metadata from each of a plurality of controllers to determine whether a controller among the plurality of controllers can service the CR based on the filter metadata associated with each of the plurality of controllers, wherein the definitions of the CR comprise an object type of the CR.
8. The system of claim 7 , wherein the processing device is further to:
in response to determining a controller among a plurality of controllers can service the CR, provide an alert indicating that there is the controller that can service the CR.
9. The system of claim 7 , wherein the filter metadata of each of the plurality of controllers comprises one or more class filters indicating classes of the object type that the controller is to observe and reconcile, and the definitions of the CR further comprise one or more class annotations indicating one or more classes of the object type of the CR that the CR is to operate with.
10. The system of claim 7 , wherein the processing device is further to:
in response to determining that none of the plurality of controllers have filter metadata matching the definitions of the CR, determine whether any of the plurality of controllers have filter metadata partially matching the definitions of the CR.
11. The system of claim 7 , wherein the processing device is further to:
generate for each of the plurality of controllers, an application program interface (API) to provide the filter metadata for each of the plurality of controllers in response to a request.
12. The system of claim 9 , wherein the processing device is further to:
generate for each of the plurality of controllers, an application program interface (API) to provide the filter metadata for that controller in response to a request.
13. A non-transitory computer readable medium having instructions stored thereon that, when executed by a processing device, cause the processing device to:
evaluate a custom resource (CR); and
compare, by the processing device, definitions of the CR with filter metadata from each of a plurality of controllers to determine whether a controller among a plurality of controllers can service the CR based on filter metadata associated with each of the plurality of controllers, wherein the definitions of the CR comprise an object type of the CR.
14. The non-transitory computer readable medium of claim 13 , wherein the processing device is further to:
in response to determining a controller among a plurality of controllers can service the CR, provide an alert indicating that there is the controller that can service the CR.
15. The non-transitory computer readable medium of claim 13 , wherein the filter metadata of each of the plurality of controllers comprises one or more class filters indicating classes of the object type that the controller is to observe and reconcile, and the definitions of the CR further comprise one or more class annotations indicating one or more classes of the object type of the CR that the CR is to operate with.
16. The non-transitory computer readable medium of claim 13 , wherein the processing device is further to:
in response to determining that none of the plurality of controllers have filter metadata matching the definitions of the CR, determine whether any of the plurality of controllers have filter metadata partially matching the definitions of the CR.
17. The non-transitory computer readable medium of claim 13 , wherein the processing device is further to:
generate for each of the plurality of controllers, an application program interface (API) to provide the filter metadata for that controller in response to a request.