Skip to content

Commit bf53244

Browse files
committed
OSDOCS-4444: adding Running Apps book and operators content to MicroShift
1 parent bae1282 commit bf53244

File tree

8 files changed

+40
-1
lines changed

8 files changed

+40
-1
lines changed

_topic_maps/_topic_map_ms.yml

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ Topics:
3838
- Name: MicroShift 4.13 release notes
3939
File: microshift-4-13-release-notes
4040
---
41-
Name: Getting Started
41+
Name: Getting started
4242
Dir: microshift_getting_started
4343
Distros: microshift
4444
Topics:
@@ -145,6 +145,13 @@ Topics:
145145
File: expanding-persistent-volumes-microshift
146146
- Name: Dynamic provisioning for MicroShift
147147
File: dynamic-provisioning-microshift
148+
---
149+
Name: Running applications
150+
Dir: microshift_running_apps
151+
Distros: microshift
152+
Topics:
153+
- Name: Running applications
154+
File: microshift-operators
148155
# ---
149156
# Name: Networking
150157
# Dir: networking

images/microshift_ovn_topology.png

298 KB
Loading

microshift_running_apps/_attributes

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
../_attributes

microshift_running_apps/images

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
../images
Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
:_content-type: ASSEMBLY
2+
[id="operators-with-microshift"]
3+
= Using Operators
4+
include::_attributes/attributes-microshift.adoc[]
5+
:context: operators-microshift
6+
7+
toc::[]
8+
9+
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).
10+
11+
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.
12+
13+
include::modules/microshift-deploying-operators.adoc[leveloffset=+1]

microshift_running_apps/modules

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
../modules

microshift_running_apps/snippets

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
../snippets/
Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * microshift_operators/microshift-deploying-operators.adoc
4+
5+
:_content-type: PROCEDURE
6+
[id="microshift-deploying-operators_{context}"]
7+
= Deploying Operators using manifests
8+
9+
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.
10+
11+
//add examples
12+
13+
//.Procedure
14+
//adding operators with manifests
15+

0 commit comments

Comments
 (0)