Will this configuration achieve fault tolerance for managers in a swarm?
Solution: one manager node for two worker nodes
Can this set of commands identify the published port(s) for a container?
Solution: `docker network inspect', `docker port'
Yes, the docker port command can be used to identify the published ports for a running container. It shows the mapping between the host ports and the container's exposed ports. The docker network inspect command can also provide information about the network settings of the container, including port mappings. However, it's important to note that docker network inspect requires the network's name or ID as an argument, not the container's. Therefore, to get the network details of a specific container, you would first need to identify the network the container is connected to. These commands, when used appropriately, can help you identify the published ports for a container.
Will this configuration achieve fault tolerance for managers in a swarm?
Solution: one manager node for two worker nodes
The Kubernetes yaml shown below describes a networkPolicy.
Will the networkPolicy BLOCK this trafftc?
Solution. a request issued from a pod bearing only the tier: frontend label, to a pod bearing the tier: backend label
The Kubernetes yaml shown below describes a networkPolicy.
Will the networkPolicy BLOCK this trafftc?
Solution. a request issued from a pod bearing the tier: api label, to a pod bearing the tier: backend label
Germaine
17 days agoSelene
21 days agoKaitlyn
1 months ago