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

Merge pull request #27161 from openshift-cherrypick-robot/cherry-pick-27158-to-enterprise-4.7

Browse Source 
[enterprise-4.7] Lowercase CRD
This commit is contained in:
Alex Dellapenta
2020-11-06 12:40:19 -07:00
committed by GitHub
parent 7972e3d186 e0ead4ec56
commit 6f6ffe0b15
2 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
modules/olm-operator-framework.adoc
View File

@@ -21,8 +21,8 @@ role-based access control (RBAC) of Operators in a cluster. Deployed by default
in {product-title} {product-version}.
Operator Registry::
The Operator Registry stores ClusterServiceVersions (CSVs) and Custom Resource
Definitions (CRDs) for creation in a cluster and stores Operator metadata about
The Operator Registry stores ClusterServiceVersions (CSVs) and custom resource
definitions (CRDs) for creation in a cluster and stores Operator metadata about
packages and channels. It runs in a Kubernetes or OpenShift cluster to provide
this Operator catalog data to OLM.

2
modules/olm-why-use-operators.adoc
View File

@@ -24,7 +24,7 @@ providers.
Why manage your app with Kubernetes APIs and `kubectl` tooling?::
These APIs are feature rich, have clients for all platforms and plug into the
cluster’s access control/auditing. An Operator uses the Kubernetes' extension
mechanism, Custom Resource Definitions (CRDs), so your custom object,
mechanism, custom resource definitions (CRDs), so your custom object,
link:https://marketplace.redhat.com/en-us/products/mongodb-enterprise-advanced-from-ibm[for
example `MongoDB`], looks and acts just like the built-in, native Kubernetes
objects.