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.

Abstract: Described embodiments provide systems and methods for routing client requests. A device may be arranged intermediary to a plurality of clients and a domain name system (DNS) controller. The device may generate a query for the DNS controller. The query may correspond to a service to be accessed by the clients. The device may receive, from the DNS controller, a response to the query. The response may include a value used by the device to route respective client requests for accessing the service to a corresponding version of a plurality of versions of the service. The device may receive, from a client, a client request for accessing the service. The device may route the client request to one of the versions of the service according to the value included in the response to manage traffic between various versions of the service.

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.

Abstract: Disclosed herein includes a system, a method, and a device for disabling services in a cluster. A master node of a plurality of nodes of a cluster can receive a disable instruction for a service of the cluster. The master node can transmit to the plurality of nodes a transition instruction to instruct the other nodes to stop accepting requests from one or more client devices for the service. The master node can receive, from each of the plurality of nodes, a client count value indicative of a number of current client connections from the one or more client devices to one or more respective nodes of the plurality of nodes. The master node can determine that the client count value is a zero value for each node of the plurality of nodes. The master node can transmit an out of service instruction to each node of the plurality of nodes to disable the service on the cluster.

Abstract: Described embodiments provide systems and methods for routing client requests. A device may be arranged intermediary to a plurality of clients and a domain name system (DNS) controller. The device may generate a query for the DNS controller. The query may correspond to a service to be accessed by the clients. The device may receive, from the DNS controller, a response to the query. The response may include a value used by the device to route respective client requests for accessing the service to a corresponding version of a plurality of versions of the service. The device may receive, from a client, a client request for accessing the service. The device may route the client request to one of the versions of the service according to the value included in the response to manage traffic between various versions of the service.

Abstract: Disclosed herein includes a system, a method, and a device for disabling services in a cluster. A master node of a plurality of nodes of a cluster can receive a disable instruction for a service of the cluster. The master node can transmit to the plurality of nodes a transition instruction to instruct the other nodes to stop accepting requests from one or more client devices for the service. The master node can receive, from each of the plurality of nodes, a client count value indicative of a number of current client connections from the one or more client devices to one or more respective nodes of the plurality of nodes. The master node can determine that the client count value is a zero value for each node of the plurality of nodes. The master node can transmit an out of service instruction to each node of the plurality of nodes to disable the service on the cluster.

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.