Abstract: A device can receive information indicating a set of instructions associated with a microservices application, where the microservices application is associated with one or more microservices. The device can generate a deployment specification. The device can deploy one or more containers and one or more replicate containers. The one or more containers and the one or more replicate containers are associated with the one or more microservices. The one or more containers and the one or more replicate containers can be associated with a distributed file system. The device can receive information associated with modifying the one or more microservices. The device can modify the one or more microservices, as one or more modified microservices, based on receiving the information associated with modifying the one or more microservices. The device can deploy the one or more modified microservices.

Abstract: A device can receive a specification identifying information associated with a stateful microservices application. The device can provide a request for storage information associated with the stateful microservices application based on the information included in the specification. The device can receive the storage information based on providing the request. The device can execute a storage installation procedure to provide the stateful microservices application with a storage volume based on receiving the storage information. The storage volume can be capable of providing persistent data storage. The device can provide a notification that the stateful microservices application is available for deployment on the device based on executing the storage installation procedure.

Abstract: A device can receive a request to deploy a container to provide a service. The request can include information identifying a set of parameters associated with the container. The device can validate the request using the information identifying the set of parameters. The device can deploy the container on a back-end host. The back-end host can lack connectivity to an external network. The device can receive a first indication that the container was successfully deployed on the back-end host. The device can deploy a proxy container on a front-end host. The front-end host can have connectivity to the external network. The device can receive a second indication that the proxy container was successfully deployed on the front-end host. The device can provide a third indication. The third indication can indicate that the container was successfully deployed.

Abstract: A first container of a first device can receive information that identifies a configuration of a first interface and a second interface of a second container of the first device. The first container can include a self-contained execution environment. The first container can configure a firewall of the first device to enable network traffic to be transferred between a second device and a third container of a third device via the first interface and the second interface.

Abstract: A device can receive, from a node of a set of nodes, a dynamic host configuration protocol (DHCP) discovery request. The device can determine a DHCP offer based on metadata associated with the node. The device can transmit, to the node, pre-boot execution environment (PXE) instructions, which can cause the node to load a minimal operating system image and execute a node installation service. The device can receive, from the node installation service, a request for information associated with a node type. The device can provide the information associated with the node type to the node, causing the node to generate configuration data relating to the node type. The device can receive, from the node, a request for a full operating system image, which can be provided to the node and can support one or more capabilities included in the configuration data.

Abstract: A device can determine that a container is deployed in a front-end of a private network. The container can include a self-contained execution environment. The container can include an interface that is configured for directing network traffic between the front-end of the private network and one or more applications operating in a back-end of the private network. The device can configure an interface of the container for directing network traffic between an external network and the container. The device can configure a firewall of the front-end of the private network to permit routing of network traffic between the external network and the container. The device can advertise a route for directing network traffic between the external network and the container. The device can perform routing of network traffic between the one or more applications operating in the back-end of the private network and the external network using the container.