doc(*): strike references to publisher

Author: Kent Rancourt

docs/src/contributing/triaging-issues.md

@@ -49,7 +49,6 @@ security     | Security-related issues such as TLS encryption, network segregati
 - docs
 - kubernetes
 - logger
-- publisher
 - registry
 - router
 - store (Ceph)

docs/src/roadmap/release-checklist.md

@@ -38,7 +38,6 @@ $ ./contrib/bumpver/bumpver -f A.B.C A.B.D \
     docs/reference/api-v1.7.rst \
     docs/troubleshooting_deis/index.rst \
     logger/image/Dockerfile \
-    publisher/image/Dockerfile \
     registry/Dockerfile \
     router/Dockerfile \
     store/base/Dockerfile \

docs/src/understanding-deis/architecture.md

@@ -40,9 +40,6 @@ HTTP API. They can also interact with the [builder][] via `git push`.
 The Data Plane is where [containers][] (in blue) are run on behalf of end-users.
 
 The platform scheduler is in charge of placing containers on hosts in the data plane.
-Deis also requires a few lightweight components on these hosts:
-
- * [publisher][] - publishes end-user containers to the [router][]
 
 ## Router Mesh
 
@@ -74,7 +71,6 @@ See [Isolating the Planes][isolating-planes] for further details.
 [database]: components.md#database
 [isolating-planes]: ../managing-deis/isolating-the-planes.md
 [logger]: components.md#logger
-[publisher]: components.md#publisher
 [registry]: components.md#registry
 [router]: components.md#router
 [store]: components.md#store

docs/src/understanding-deis/components.md

@@ -40,11 +40,6 @@ Image data is stored by [Store][].
 The logger component is a syslog server that collects logs from across the platform.
 This data can then be queried by the [Controller][].
 
-## Publisher
-
-The publisher component is a microservice written in Go that publishes
-containers to etcd so they can be exposed by the platform [router][].
-
 ## Router
 
 The router component uses [Nginx][] to route traffic to application containers.