diff --git a/_topic_maps/_topic_map_ms.yml b/_topic_maps/_topic_map_ms.yml
index ee680c4e48..498e8689e0 100644
--- a/_topic_maps/_topic_map_ms.yml
+++ b/_topic_maps/_topic_map_ms.yml
@@ -38,7 +38,7 @@ Topics:
 - Name: MicroShift 4.13 release notes
   File: microshift-4-13-release-notes
 ---
-Name: Getting Started
+Name: Getting started
 Dir: microshift_getting_started
 Distros: microshift
 Topics:
@@ -145,6 +145,13 @@ Topics:
   File: expanding-persistent-volumes-microshift
 - Name: Dynamic provisioning for MicroShift
   File: dynamic-provisioning-microshift
+---
+Name: Running applications
+Dir: microshift_running_apps
+Distros: microshift
+Topics:
+ - Name: Running applications
+   File: microshift-operators
 # ---
 # Name: Networking
 # Dir: networking
diff --git a/images/microshift_ovn_topology.png b/images/microshift_ovn_topology.png
new file mode 100644
index 0000000000..55db68eeed
Binary files /dev/null and b/images/microshift_ovn_topology.png differ
diff --git a/microshift_running_apps/_attributes b/microshift_running_apps/_attributes
new file mode 120000
index 0000000000..93957f0227
--- /dev/null
+++ b/microshift_running_apps/_attributes
@@ -0,0 +1 @@
+../_attributes
\ No newline at end of file
diff --git a/microshift_running_apps/images b/microshift_running_apps/images
new file mode 120000
index 0000000000..5e67573196
--- /dev/null
+++ b/microshift_running_apps/images
@@ -0,0 +1 @@
+../images
\ No newline at end of file
diff --git a/microshift_running_apps/microshift-operators.adoc b/microshift_running_apps/microshift-operators.adoc
new file mode 100644
index 0000000000..39e447ac79
--- /dev/null
+++ b/microshift_running_apps/microshift-operators.adoc
@@ -0,0 +1,13 @@
+:_content-type: ASSEMBLY
+[id="operators-with-microshift"]
+= Using Operators
+include::_attributes/attributes-microshift.adoc[]
+:context: operators-microshift
+
+toc::[]
+
+Operators integrate with Kubernetes APIs and CLI tools such as `kubectl` and `oc`. Operators provide the means to manage applications and their resources, such as deploying a database or message bus. To minimize the footprint of {product-title}, Operators are installed directly with manifests instead of through the Operator Lifecycle Manager (OLM).
+
+Operators offer a more granular configuration experience. You configure each component by modifying the API that the Operator exposes instead of modifying a global configuration file. {product-title} applications are generally deployed in static environments, but Operators are available for you to use.
+
+include::modules/microshift-deploying-operators.adoc[leveloffset=+1]
\ No newline at end of file
diff --git a/microshift_running_apps/modules b/microshift_running_apps/modules
new file mode 120000
index 0000000000..464b823aca
--- /dev/null
+++ b/microshift_running_apps/modules
@@ -0,0 +1 @@
+../modules
\ No newline at end of file
diff --git a/microshift_running_apps/snippets b/microshift_running_apps/snippets
new file mode 120000
index 0000000000..9d58b92e50
--- /dev/null
+++ b/microshift_running_apps/snippets
@@ -0,0 +1 @@
+../snippets/
\ No newline at end of file
diff --git a/modules/microshift-deploying-operators.adoc b/modules/microshift-deploying-operators.adoc
new file mode 100644
index 0000000000..3ba4dc2017
--- /dev/null
+++ b/modules/microshift-deploying-operators.adoc
@@ -0,0 +1,15 @@
+// Module included in the following assemblies:
+//
+// * microshift_operators/microshift-deploying-operators.adoc
+
+:_content-type: PROCEDURE
+[id="microshift-deploying-operators_{context}"]
+= Deploying Operators using manifests
+
+You can use Operators with {product-title} to create applications that monitor the running services in the cluster. Operators are designed specifically for your applications. These customized pieces of software running inside your cluster can be used to implement and automate common operations.
+
+//add examples
+
+//.Procedure
+//adding operators with manifests
+