//Module included in the following assemblies:
//
// * microshift_running_apps/microshift_operators/microshift-operators-olm.adoc

:_mod-docs-content-type: CONCEPT
[id="microshift-olm-namespaces_{context}"]
= Namespace use in {microshift-short}

The `microshift-olm` RPM creates the three default namespaces: one for running OLM, and two for catalog and Operator installation. You can create additional namespaces as needed for your use case.

[id="microshift-olm-default-namespaces_{context}"]
== Default namespaces

The following table lists the default namespaces and a brief description of how each namespace works.

.Default namespaces created by OLM for {microshift-short}
[cols="2",%autowidth]
|===
|*Default Namespace*
|*Details*

|`openshift-operator-lifecycle-manager`
|The OLM package manager runs in this namespace.

|`openshift-marketplace`
|The global namespace. Empty by default. To make the catalog source to be available globally to users in all namespaces, set the `openshift-marketplace` namespace in the catalog-source YAML.

|`openshift-operators`
|The default namespace where Operators run in {microshift-short}. Operators that reference catalogs in the `openshift-operators` namespace must have the *AllNamespaces* watch scope.
|===

[id="microshift-olm-custom-namespace_{context}"]
== Custom namespaces
If you want to use a catalog and Operator together in a single namespace, then you must create a custom namespace. After you create the namespace, you must create the catalog in that namespace. All Operators running in the custom namespace must have the same single-namespace watch scope.