One of the things that my team and I are sticklers about is using the proper terminology for the proper technology. It’s just not the debate of “Principle” vs “Principal”, it’s the inferred technology that is applied by the terms you use. For instance, if a client told me they had a Docker Cluster, I might infer they are using Kubernetes, as that is correct terminology. When, in fact, they may be using Docker EE and should have used the term Docker Swarm.

Recently, when I was learning more about Docker EE Swarm at DockerCon ‘19, I started to realize the concepts are similar in Kubernetes, but the terminology was subtly different. I started to put together my own cheat sheet of similar components, so that I could keep things straight between the different sessions I attended. Now, I can speak both Swarm and Kubernetes without mingling terms, something my team will certainly appreciate!

Swarm TermKubenetes TermLoose Definition
SwarmClusterA group of machines that are running that provide high availability of containers.
NodeCluster MemberEither a physical or virtual host that is participating within the Swarm/Cluster.
ManagerMasterManages the strategy of how work is distributed within the Swarm/Cluster.
Worker(Worker) NodeA participating member of the Swarm/Cluster that is providing compute capacity.
ContainerContainerA standard unit of software that packages up code and all its dependencies, so the application runs quickly and reliably from one computing environment to another.
TaskPodA group of containers that are deployed together on the same host.
ServiceReplicaSetStarts and manages the tasks/pods, ensuring the desired state.
ServiceDeploymentProvides declarative updates to ensure the desired state is maintained.
StackStackA collection of services to run an application.
VIPClusterIP ServiceThe IP address representing the service definition.

Please contact us for your Docker needs.

Share This