Systems and method updating adc configuration with intended state using desired state api

Abstract

Described herein are systems and methods for updating configuration of a device based on changes to microservices. A device may receive a request via a desired state application programming interface (API) to update a configuration of the device to manage a desired set of instances of microservices. The device may identify from the request, a first set of endpoint information for each instance of a microservice in the desired set of instances of microservices. The first set of endpoint information may include an internet protocol (IP) address and port of an endpoint of a respective instance of the microservice. The first set or second set of endpoint information may include a weight for each instance of the microservice.

We claim: 
     
         1 . A method comprising:
 receiving, by a device, an internet protocol (IP) address and port of an endpoint of each instance of a first one or more microservices on one or more servers to be configured to be managed by the device;   identifying, by a device, the IP address and port of the endpoint of each instance of a second one or more microservices on one or more servers for which a configuration of the device is currently configured to manage over one or more networks;   determining, by the device, a change with at least one of the internet protocol (IP) address or port of at least one endpoint between the first one or more microservices and the second one or more microservices; and   modifying, by the device based at least on the change, the configuration of the device to manage network traffic over the one or more networks to the first one or more microservices on the one or more servers.   
     
     
         2 . The method of  claim 1 , wherein the device is intermediary to a plurality of clients and the one or more microservices on the one or more servers. 
     
     
         3 . The method of  claim 1 , further comprising receiving, by the device, a request via an application programming interface (API) to update the configuration of the device to manage the first one or more microservices. 
     
     
         4 . The method of  claim 3 , wherein the API comprises a desired state API. 
     
     
         5 . The method of  claim 3 , further comprising determining, by the device, the change responsive to the request. 
     
     
         6 . The method of  claim 1 , further comprising communicating, by the device, the change to one or more packet engines on the device to update the configuration of the one or more packet engines to manage the first one or more microservices. 
     
     
         7 . The method of  claim 1 , further comprising modifying, by the device, the configuration to one of add or remove one of the internet protocol address or the port of at least one endpoint. 
     
     
         8 . A system comprising:
 a device comprising one or more processors, coupled to memory and configured to:   receive an internet protocol (IP) address and port of an endpoint of each instance of a first one or more microservices on one or more servers to be configured to be managed by the device;   identify the IP address and port of the endpoint of each instance of a second one or more microservices on one or more servers for which a configuration of the device is currently configured to manage over one or more networks;   determine a change with at least one of the internet protocol (IP) address or port of at least one endpoint between the first one or more microservices and the second one or more microservices; and   modify based at least on the change, the configuration of the device to manage network traffic over the one or more networks to the first one or more microservices on the one or more servers.   
     
     
         9 . The system of  claim 8 , wherein the device is intermediary to a plurality of clients and the one or more microservices on the one or more servers. 
     
     
         10 . The system of  claim 8 , wherein the device is further configured to receive a request via an application programming interface (API) to update the configuration of the device to manage the first one or more microservices. 
     
     
         11 . The system of  claim 10 , wherein the API comprises a desired state API. 
     
     
         12 . The system of  claim 10 , wherein the device is further configured to determine the change responsive to the request. 
     
     
         13 . The system of  claim 8 , wherein the device is further configured to communicate the change to one or more packet engines on the device to update the configuration of the one or more packet engines to manage the first one or more microservices. 
     
     
         14 . The system of  claim 8 , wherein the device is further configured to modify the configuration to one of add or remove one of the internet protocol address or the port of at least one endpoint. 
     
     
         15 . A non-transitory computer-readable medium storing instructions that, when executed by one or more processors of a device, cause the one or more processors to:
 receive an internet protocol (IP) address and port of an endpoint of each instance of a first one or more microservices on one or more servers to be configured to be managed by the device;   identify the IP address and port of the endpoint of each instance of a second one or more microservices on one or more servers for which a configuration of the device is currently configured to manage over one or more networks;   determine a change with at least one of the internet protocol (IP) address or port of at least one endpoint between the first one or more microservices and the second one or more microservices; and   modify, based at least on the change, the configuration of the device to manage network traffic over the one or more networks to the first one or more microservices on the one or more servers.   
     
     
         16 . The non-transitory computer-readable medium of  claim 15 , wherein the device is intermediary to a plurality of clients and the one or more microservices on the one or more servers. 
     
     
         17 . The non-transitory computer-readable medium of  claim 16 , further comprising instructions that, when executed by one or more processors, cause the one or more processors to receive a request via an application programming interface (API) to update the configuration of the device to manage the first one or more microservices. 
     
     
         18 . The non-transitory computer-readable medium of  claim 17 , further comprising instructions that, when executed by one or more processors, cause the one or more processors to determine the change responsive to the request. 
     
     
         19 . The non-transitory computer-readable medium of  claim 16 , further comprising instructions that, when executed by one or more processors, cause the one or more processors to communicate the change to one or more packet engines to update the configuration of the one or more packet engines to manage the first one or more microservices. 
     
     
         20 . The non-transitory computer-readable medium of  claim 16 , further comprising instructions that, when executed by one or more processors, cause the one or more processors to modify the configuration on the device to one of add or remove one of the internet protocol address or the port of at least one endpoint.