diff --git a/slides/images/ci-cd-with-docker.png b/slides/images/ci-cd-with-docker.png
new file mode 100644
index 00000000..333d7ecc
Binary files /dev/null and b/slides/images/ci-cd-with-docker.png differ
diff --git a/slides/swarm-fullday.yml b/slides/swarm-fullday.yml
index 9a558279..356ee521 100644
--- a/slides/swarm-fullday.yml
+++ b/slides/swarm-fullday.yml
@@ -41,6 +41,7 @@ chapters:
   - swarm/btp-manual.md
   - swarm/swarmready.md
   - swarm/compose2swarm.md
+  - swarm/cicd.md
   - swarm/updatingservices.md
   #- swarm/rollingupdates.md
   - swarm/healthchecks.md
diff --git a/slides/swarm-halfday.yml b/slides/swarm-halfday.yml
index 7de7776a..da596410 100644
--- a/slides/swarm-halfday.yml
+++ b/slides/swarm-halfday.yml
@@ -41,6 +41,7 @@ chapters:
   #- swarm/btp-manual.md
   #- swarm/swarmready.md
   - swarm/compose2swarm.md
+  - swarm/cicd.md
   - swarm/updatingservices.md
   #- swarm/rollingupdates.md
   #- swarm/healthchecks.md
diff --git a/slides/swarm-selfpaced.yml b/slides/swarm-selfpaced.yml
index d38a6cb7..2a34a2fd 100644
--- a/slides/swarm-selfpaced.yml
+++ b/slides/swarm-selfpaced.yml
@@ -42,6 +42,7 @@ chapters:
   - swarm/btp-manual.md
   - swarm/swarmready.md
   - swarm/compose2swarm.md
+  - swarm/cicd.md
   - |
     name: part-2
 
diff --git a/slides/swarm/cicd.md b/slides/swarm/cicd.md
new file mode 100644
index 00000000..2199a7a4
--- /dev/null
+++ b/slides/swarm/cicd.md
@@ -0,0 +1,37 @@
+name: cicd
+
+# CI/CD for Docker and orchestration
+
+A quick note about continuous integration and deployment
+
+- This lab won't have you building out CI/CD pipelines
+
+- We're cheating a bit by building images on server hosts and not in CI tool
+
+- Docker and orchestration works with all the CI and deployment tools
+
+---
+
+## CI/CD general process 
+
+- Have your CI build your images, run tests *in them*, then push to registry
+
+- If you security scan, do it then on your images after tests but before push
+
+- Optionally, have CI do continuous deployment if build/test/push is successful
+
+- CD tool would SSH into nodes, or use docker cli against remote engine
+
+- If supported, it could use docker engine TCP API (swarm API is built-in)
+
+- Docker KBase [Development Pipeline Best Practices](https://success.docker.com/article/dev-pipeline)
+
+- Docker KBase [Continuous Integration with Docker Hub](https://success.docker.com/article/continuous-integration-with-docker-hub)
+
+- Docker KBase [Building a Docker Secure Supply Chain](https://success.docker.com/article/secure-supply-chain)
+
+---
+
+class: pic
+
+![CI-CD with Docker](images/ci-cd-with-docker.png)