Skip to content

Commit 14b5a97

Browse files
committed
Document olm-deployer and fix secret/listener-operator memory docs
1 parent 7c25d43 commit 14b5a97

1 file changed

Lines changed: 12 additions & 1 deletion

File tree

modules/ROOT/pages/kubernetes/openshift.adoc

Lines changed: 12 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,10 @@ SDP operators are certified for the OpenShift platform and can be installed from
77

88
IMPORTANT: OpenShift installations with FIPS mode enabled are not supported. This is because neither the SDP operators, nor the supported Apache products are FIPS-compliant.
99

10+
IMPORTANT: The operators deployed via olm might have higher memory requests (and limits) compared to our helm-charts, as we have seen typical production OpenShift clusters being larger than typical non-Openshift clusters.
11+
The reason is that memory usage of some of our operators scales with the number of objects in your Kubernetes cluster.
12+
However, you can fine-tune the memory of your operators using the documentation below, so this note is only about the default resources!
13+
1014
== Customizing operator installations
1115

1216
As described in the https://github.com/operator-framework/operator-lifecycle-manager/blob/master/doc/design/subscription-config.md[Openshift Subscription documentation{external-link-icon}^] you can configure the deployed operators.
@@ -53,7 +57,14 @@ spec:
5357
value: kafka-namespace
5458
----
5559

56-
IMPORTANT: The described configuration mechanism currently does not work for secret and listener-operator due to restrictions on deploying DaemonSets.
60+
=== secret and listener-operator
61+
62+
Most operators are deployed using a Deployment, which olm allows to tweak the resources for.
63+
secret and listener-operator use a DaemonSet instead, which can not be deployed and tweaked by olm.
64+
Because of this limitation of olm, we deploy a Deployment called the "olm-deployer", which in turn deploys the relevant Kubernetes resources, including the DaemonSet.
65+
As we can't influence the deployed resources via olm, the olm-deployer takes **it's own** resource requests and applies them to all containers on the DaemonSets.
66+
67+
This allows you to customize the resources of the DaemonSet in the same way as for the other operators - but doesn't allow individual resources for each container.
5768

5869
== Security context constraints
5970

0 commit comments

Comments
 (0)