...
In the lower box we have multiple configuration options:
“Command” Tab: We can define environment variables, auto restart mode if the container stops, container user, different entry point…
“Volumes“ tab: It allows us to persist the information from the container to host’s filesystem where the container is deployed.
“Networking“ tab: In this tab we can define what type of network our containers will use (by default it will use the network managed by Docker). We can also add additional DNS or name resolution servers, establish a name to the container…
“Security/Host“ tab: Here we can set options to limit the access to the Host resources by the container i.e., memory, cpu… We can also set log parameters in this tab.
“Secrets“ tab: It will allow us to store private information, such as database access passwords.
“Health Check“ tab: This tab is important since it will determine part of the high availability of our services. Here we can define the port of the containerized application and its protocol (TCP / HTTP) and in case the port or service ceases to be operational, indicate the CaaS what to do. We will normally choose to recreate the service to ensure that if it crashes, it will reinitialize.
“Labels“ tab: Permite añadir etiquetas a nuestro servicio para posteriormente poder definir reglas de planificación de despliegue en base a ellas.
Pestaña “Scheduling“It allows the addition of labels to our service to later define rules for deployment based on them.
“Scheduling“ tab: Together with the previous tab, it allows us to define deployment planning rules based on labels, for example, that the service deploys only in the nodes labeled as "DEV"
Finally we will create our service and we can see it in the stack:
...