Cloud-friendly automated declarative update deployment

1 . A method comprising:

detecting, by a processor, a registration of a specification for an update resource;

subsequent to the registration of the specification, generating a controller to monitor requests associated with an update object;

in response to the controller receiving a request to generate the update object, generating the update object according to the request subsequent to validating the specification, wherein the update object is an instance of the update resource according to the specification;

in response to determining that there is a change is to be performed on the update object triggering an update process for a containerized application installed in a node using the update object to apply the change;

querying a status of the update process to reconcile a current state of the update process to a desired state; and

in response to the controller determining that the update process is complete and the current state of the update process is equal to the desired state based on the status of the update process, deleting the update object.

2 . The method of claim 1 , wherein the update resource is a custom resource that is an extension of an application programming interface of a container installation.

3 . The method of claim 1 , wherein the node includes a containerized firmware.

4 . The method of claim 1 , wherein each one of nodes in a cluster includes a particular update object.

5 . The method of claim 1 , further comprising validating the specification.

6 . The method of claim 1 , further comprising propagating the status of the update process to the controller.

7 . The method of claim 1 , further comprising reconciling the current state of the update process to the desired state.

8 . The method of claim 1 , further comprising applying the change to the update object according to another request.

9 . The method of claim 1 , further comprising deleting the update object according to another request after stopping the update process.

10 . The method of claim 1 , wherein the specification is in a JavaScript Object Notation format.

11 . An information handling system, comprising:

a processor; and

a memory storing code that when executed causes the processor to perform operations including:

detecting a registration of a specification for an update resource;

subsequent to the registration of the specification, generating a controller to monitor requests associated with an update object;

in response to the controller receiving a request to generate the update object, generating the update object according to the request subsequent to validating the specification, wherein the update object is an instance of the update resource according to the specification;

in response to determining that there is a change to be performed on the update object, triggering an update process for a containerized application installed in a node using the update object to apply the change;

querying a status of the update process to reconcile a current state of the update process to a desired state; and

in response to the controller determining that the update process is complete and the current state of the update process is equal to the desired state on the status of the update process, deleting the update object.

12 . The information handling system of claim 11 , wherein the update resource is a custom resource that is an extension of an application programming interface of a container installation.

13 . The information handling system of claim 11 , wherein the node includes a containerized firmware.

14 . The information handling system of claim 11 , wherein each one of nodes in a cluster includes a particular update object.

15 . The information handling system of claim 11 , wherein the operations further comprise propagating the status of the update process to the controller.

16 . A non-transitory computer-readable medium to store instructions that are executable to perform operations comprising:

detecting a registration of a specification for an update resource;

subsequent to the registration of the specification, generating a controller to monitor requests associated with an update object;

in response to the controller receiving a request to generate the update object, generating the update object according to the request subsequent to validating the specification, wherein the update object is an instance of the update resource;

in response to determining that there is a change is to be performed on the update object, triggering an update process for a containerized application installed in a node using the update object to apply the change;

querying a status of the update process to reconcile a current state of the update process to a desired state; and

in response to the controller determining that the update process is complete and the current state of the update process is equal to the desired state based on the status of the update process, deleting the update object.

17 . The non-transitory computer-readable medium of claim 16 , wherein the operations further comprise applying the change to the update object according to another request.

18 . The non-transitory computer-readable medium of claim 16 , wherein the operations further comprise deleting the update object according to another request after stopping the update process.

19 . The non-transitory computer-readable medium of claim 16 , wherein the operations further comprise reconciling the current state of the update process to the desired state.

20 . The non-transitory computer-readable medium of claim 16 , wherein each one of nodes in a cluster includes a particular update object.