openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 21:46:22 +01:00
Code Issues Releases Activity

Trivial: Typos in OLM doc

Browse Source 
Fixes for typos I noticed while reading the [OLM workflow &
architecture](https://docs.openshift.com/container-platform/4.4/operators/understanding_olm/olm-understanding-olm.html) doc
This commit is contained in:
Eric Fried
2020-05-08 11:20:24 -05:00
committed by Alex Dellapenta
parent e2d50115c7
commit 712235e600
2 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
modules/olm-architecture.adoc
View File

@@ -8,8 +8,8 @@
The Operator Lifecycle Manager is composed of two Operators: the OLM Operator
and the Catalog Operator.
Each of these Operators are responsible for managing the CRDs that are the basis
for the OLM framework:
Each of these Operators is responsible for managing the Custom Resource
Definitions (CRDs) that are the basis for the OLM framework:
.CRDs managed by OLM and Catalog Operators
[cols="2a,1a,1a,8a",options="header"]
@@ -44,7 +44,7 @@ upgrade a CSV.
|Used to group multiple namespaces and prepare them for use by an Operator.
|===
Each of these Operators are also responsible for creating resources:
Each of these Operators is also responsible for creating resources:
.Resources created by OLM and Catalog Operators
[options="header"]
@@ -73,7 +73,7 @@ cluster.
The OLM Operator is not concerned with the creation of the required resources;
users can choose to manually create these resources using the CLI, or users can
choose to create these resources using the Catalog Operator. This separation of
concern enables users incremental buy-in in terms of how much of the OLM
concern allows users incremental buy-in in terms of how much of the OLM
framework they choose to leverage for their application.
While the OLM Operator is often configured to watch all namespaces, it can also
@@ -98,7 +98,7 @@ required resources they specify. It is also responsible for watching
CatalogSources for updates to packages in channels and upgrading them
(optionally automatically) to the latest available versions.
A user that wishes to track a package in a channel creates a Subscription
A user who wishes to track a package in a channel creates a Subscription
resource configuring the desired package, channel, and the CatalogSource from
which to pull updates. When updates are found, an appropriate InstallPlan is
written into the namespace on behalf of the user.

2
modules/olm-upgrades.adoc
View File

@@ -5,7 +5,7 @@
[id="olm-upgrades_{context}"]
= Operator installation and upgrade workflow in OLM
In the Operator Lifecycle Manager (OLM) ecosystem, the following resource are
In the Operator Lifecycle Manager (OLM) ecosystem, the following resources are
used to resolve Operator installations and upgrades:
* ClusterServiceVersion (CSV)