From fdc7e5bfd45f9089665bd5f8228ca3852c95194e Mon Sep 17 00:00:00 2001 From: ajay143444 Date: Fri, 24 Apr 2020 13:32:50 +0530 Subject: [PATCH] replaced based off of with based on (#10684) replaced based off of with based on --- get-started/swarm-deploy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/get-started/swarm-deploy.md b/get-started/swarm-deploy.md index 4c6af70c66..fd59e23ef8 100644 --- a/get-started/swarm-deploy.md +++ b/get-started/swarm-deploy.md @@ -36,7 +36,7 @@ services: - "8000:8080" ``` -In this Swarm YAML file, we have just one object: a `service`, describing a scalable group of identical containers. In this case, you'll get just one container (the default), and that container will be based off of your `bulletinboard:1.0` image created in [Part 2](part2.md) of the Quickstart tutorial. In addition, We've asked Swarm to forward all traffic arriving at port 8000 on our development machine to port 8080 inside our bulletin board container. +In this Swarm YAML file, we have just one object: a `service`, describing a scalable group of identical containers. In this case, you'll get just one container (the default), and that container will be based on your `bulletinboard:1.0` image created in [Part 2](part2.md) of the Quickstart tutorial. In addition, We've asked Swarm to forward all traffic arriving at port 8000 on our development machine to port 8080 inside our bulletin board container. > **Kubernetes Services and Swarm Services are very different!** Despite the similar name, the two orchestrators mean very different things by the term 'service'. In Swarm, a service provides both scheduling _and_ networking facilities, creating containers and providing tools for routing traffic to them. In Kubernetes, scheduling and networking are handled separately: _deployments_ (or other controllers) handle the scheduling of containers as pods, while _services_ are responsible only for adding networking features to those pods.