Skip to content

Commit 84923fe

Browse files
authored
Merge pull request #60212 from adellape/mv_colocation
2 parents e5dee17 + f4fbdde commit 84923fe

10 files changed

+46
-15
lines changed

_topic_maps/_topic_map.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1664,6 +1664,8 @@ Topics:
16641664
File: olm-understanding-dependency-resolution
16651665
- Name: Operator groups
16661666
File: olm-understanding-operatorgroups
1667+
- Name: Multitenancy and Operator colocation
1668+
File: olm-colocation
16671669
- Name: Operator conditions
16681670
File: olm-operatorconditions
16691671
- Name: Metrics

modules/olm-colocation-namespaces.adoc

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,6 @@
11
// Module included in the following assemblies:
22
//
3-
// * operators/understanding/olm/olm-understanding-dependency-resolution.adoc
4-
// * operators/understanding/olm-multitenancy.adoc
3+
// * operators/understanding/olm/olm-colocation.adoc
54

65
:_content-type: CONCEPT
76
[id="olm-colocation-namespaces_{context}"]

modules/olm-installing-global-namespaces.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@
66
[id="olm-installing-global-namespaces_{context}"]
77
= Installing global Operators in custom namespaces
88

9-
When installing Operators with the {product-title} web console, the default behavior installs Operators that support the *All namespaces* install mode into the default `openshift-operators` global namespace. This can cause issues related to shared install plans and update policies between all Operators in the namespace. For more details on these limitations, see "Colocation of Operators in a namespace".
9+
When installing Operators with the {product-title} web console, the default behavior installs Operators that support the *All namespaces* install mode into the default `openshift-operators` global namespace. This can cause issues related to shared install plans and update policies between all Operators in the namespace. For more details on these limitations, see "Multitenancy and Operator colocation".
1010

1111
As a cluster administrator, you can bypass this default behavior manually by creating a custom global namespace and using that namespace to install your individual or scoped set of Operators and their dependencies.
1212

operators/admin/olm-adding-operators-to-cluster.adoc

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,11 @@ toc::[]
1111

1212
Using Operator Lifecycle Manager (OLM), cluster administrators can install OLM-based Operators to an {product-title} cluster.
1313

14+
[NOTE]
15+
====
16+
For information on how OLM handles updates for installed Operators colocated in the same namespace, as well as an alternative method for installing Operators with custom global Operator groups, see xref:../../operators/understanding/olm/olm-colocation.adoc#olm-colocation[Multitenancy and Operator colocation].
17+
====
18+
1419
ifdef::openshift-origin[]
1520
[id="olm-adding-operators-to-a-cluster-prereqs"]
1621
== Prerequisites
@@ -21,6 +26,9 @@ If you have the pull secret, add the `redhat-operators` catalog to the `Operator
2126
endif::[]
2227
2328
include::modules/olm-installing-operators-from-operatorhub.adoc[leveloffset=+1]
29+
[role="_additional-resources"]
30+
.Additional resources
31+
2432
* xref:../../operators/understanding/olm-understanding-operatorhub.adoc#olm-understanding-operatorhub[Understanding OperatorHub]
2533
2634
include::modules/olm-installing-from-operatorhub-using-web-console.adoc[leveloffset=+1]
@@ -67,7 +75,7 @@ When you initiate the Operator installation, if the Operator has dependencies, t
6775
[role="_additional-resources"]
6876
.Additional resources
6977
70-
* xref:../../operators/understanding/olm/olm-understanding-dependency-resolution.adoc#olm-colocation-namespaces_olm-understanding-dependency-resolution[Colocation of Operators in a namespace]
78+
* xref:../../operators/understanding/olm/olm-colocation.adoc#olm-colocation[Multitenancy and Operator colocation]
7179
7280
include::modules/olm-pod-placement.adoc[leveloffset=+1]
7381

operators/admin/olm-upgrading-operators.adoc

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,11 @@ toc::[]
88

99
As a cluster administrator, you can update Operators that have been previously installed using Operator Lifecycle Manager (OLM) on your {product-title} cluster.
1010

11+
[NOTE]
12+
====
13+
For information on how OLM handles updates for installed Operators colocated in the same namespace, as well as an alternative method for installing Operators with custom global Operator groups, see xref:../../operators/understanding/olm/olm-colocation.adoc#olm-colocation[Multitenancy and Operator colocation].
14+
====
15+
1116
include::modules/olm-preparing-upgrade.adoc[leveloffset=+1]
1217
include::modules/olm-changing-update-channel.adoc[leveloffset=+1]
1318
include::modules/olm-approving-pending-upgrade.adoc[leveloffset=+1]

operators/understanding/olm-multitenancy.adoc

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,6 @@ Consider the following scenarios to determine which Operator installation workfl
1313
[role="_additional-resources"]
1414
.Additional resources
1515
* xref:../../operators/understanding/olm-common-terms.adoc#olm-common-terms-multitenancy_olm-common-terms[Common terms: Multitenant]
16-
* xref:../../operators/understanding/olm/olm-understanding-dependency-resolution.adoc#olm-colocation-namespaces_olm-understanding-dependency-resolution[Colocation of Operators in a namespace]
1716
* xref:../../operators/understanding/olm/olm-understanding-operatorgroups.adoc#olm-operatorgroups-limitations[Limitations for multitenant Operator management]
1817
1918
include::modules/olm-default-install-behavior.adoc[leveloffset=+1]
@@ -28,4 +27,11 @@ include::modules/olm-multitenancy-solution.adoc[leveloffset=+1]
2827
.Additional resources
2928
* xref:../../operators/admin/olm-adding-operators-to-cluster.adoc#olm-preparing-operators-multitenant_olm-adding-operators-to-a-cluster[Preparing for multiple instances of an Operator for multitenant clusters]
3029
* xref:../../operators/admin/olm-creating-policy.adoc#olm-creating-policy[Allowing non-cluster administrators to install Operators]
31-
* xref:../../operators/admin/olm-managing-custom-catalogs.adoc#olm-restricted-networks-operatorhub_olm-managing-custom-catalogs[Disabling the default OperatorHub catalog sources]
30+
* xref:../../operators/admin/olm-managing-custom-catalogs.adoc#olm-restricted-networks-operatorhub_olm-managing-custom-catalogs[Disabling the default OperatorHub catalog sources]
31+
32+
[id="olm-colocation_{context}"]
33+
== Operator colocation and Operator groups
34+
35+
Operator Lifecycle Manager (OLM) handles OLM-managed Operators that are installed in the same namespace, meaning their `Subscription` resources are colocated in the same namespace, as related Operators. Even if they are not actually related, OLM considers their states, such as their version and update policy, when any one of them is updated.
36+
37+
For more information on Operator colocation and using Operator groups effectively, see xref:../../operators/understanding/olm/olm-colocation.adoc#olm-colocation[Operator Lifecycle Manager (OLM) -> Multitenancy and Operator colocation].
Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
:_content-type: ASSEMBLY
2+
[id="olm-colocation"]
3+
= Multitenancy and Operator colocation
4+
include::_attributes/common-attributes.adoc[]
5+
:context: olm-colocation
6+
7+
toc::[]
8+
9+
This guide outlines multitenancy and Operator colocation in Operator Lifecycle Manager (OLM).
10+
11+
include::modules/olm-colocation-namespaces.adoc[leveloffset=+1]
12+
[role="_additional-resources"]
13+
.Additional resources
14+
15+
* xref:../../../operators/admin/olm-adding-operators-to-cluster.adoc#olm-installing-global-namespaces_olm-adding-operators-to-a-cluster[Installing global Operators in custom namespaces]
16+
* xref:../../../operators/understanding/olm-multitenancy.adoc#olm-multitenancy[Operators in multitenant clusters]

operators/understanding/olm/olm-understanding-dependency-resolution.adoc

Lines changed: 1 addition & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -32,10 +32,4 @@ include::modules/olm-dependencies-best-practices.adoc[leveloffset=+1]
3232
* Kubernetes documentation: link:https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api_changes.md#readme[Changing the API]
3333
3434
include::modules/olm-dependencies-caveats.adoc[leveloffset=+1]
35-
include::modules/olm-dependency-resolution-examples.adoc[leveloffset=+1]
36-
include::modules/olm-colocation-namespaces.adoc[leveloffset=+1]
37-
[role="_additional-resources"]
38-
.Additional resources
39-
40-
* xref:../../../operators/admin/olm-adding-operators-to-cluster.adoc#olm-installing-global-namespaces_olm-adding-operators-to-a-cluster[Installing global Operators in custom namespaces]
41-
* xref:../../../operators/understanding/olm-multitenancy.adoc#olm-multitenancy[Operators in multitenant clusters]
35+
include::modules/olm-dependency-resolution-examples.adoc[leveloffset=+1]

operators/understanding/olm/olm-understanding-olm.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -30,15 +30,15 @@ include::modules/olm-subscription.adoc[leveloffset=+2]
3030
[role="_additional-resources"]
3131
.Additional resources
3232

33-
* xref:../../../operators/understanding/olm/olm-understanding-dependency-resolution.adoc#olm-colocation-namespaces_olm-understanding-dependency-resolution[Colocation of Operators in a namespace]
33+
* xref:../../../operators/understanding/olm/olm-colocation.adoc#olm-colocation[Multitenancy and Operator colocation]
3434
* xref:../../../operators/admin/olm-status.adoc#olm-status-viewing-cli_olm-status[Viewing Operator subscription status by using the CLI]
3535
3636
include::modules/olm-installplan.adoc[leveloffset=+2]
3737

3838
[role="_additional-resources"]
3939
.Additional resources
4040

41-
* xref:../../../operators/understanding/olm/olm-understanding-dependency-resolution.adoc#olm-colocation-namespaces_olm-understanding-dependency-resolution[Colocation of Operators in a namespace]
41+
* xref:../../../operators/understanding/olm/olm-colocation.adoc#olm-colocation[Multitenancy and Operator colocation]
4242
* xref:../../../operators/admin/olm-creating-policy.adoc#olm-creating-policy[Allowing non-cluster administrators to install Operators]
4343
4444
include::modules/olm-operatorgroups-about.adoc[leveloffset=+2]

operators/understanding/olm/olm-understanding-operatorgroups.adoc

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -21,6 +21,7 @@ include::modules/olm-operatorgroups-limitations.adoc[leveloffset=+1]
2121
[role="_additional-resources"]
2222
.Additional resources
2323
24+
* xref:../../../operators/understanding/olm/olm-colocation.adoc#olm-colocation[Operator Lifecycle Manager (OLM) -> Multitenancy and Operator colocation].
2425
* xref:../../../operators/understanding/olm-multitenancy.adoc#olm-multitenancy[Operators in multitenant clusters]
2526
* xref:../../../operators/admin/olm-creating-policy.adoc#olm-creating-policy[Allowing non-cluster administrators to install Operators]
2627

0 commit comments

Comments
 (0)