From 14b5a97f41fee23a0c06892dd72b56924ea118a7 Mon Sep 17 00:00:00 2001 From: Sebastian Bernauer Date: Wed, 5 Aug 2026 11:27:45 +0200 Subject: [PATCH 1/2] Document olm-deployer and fix secret/listener-operator memory docs --- modules/ROOT/pages/kubernetes/openshift.adoc | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/modules/ROOT/pages/kubernetes/openshift.adoc b/modules/ROOT/pages/kubernetes/openshift.adoc index c4ec84711..41a34c03e 100644 --- a/modules/ROOT/pages/kubernetes/openshift.adoc +++ b/modules/ROOT/pages/kubernetes/openshift.adoc @@ -7,6 +7,10 @@ SDP operators are certified for the OpenShift platform and can be installed from 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. +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. +The reason is that memory usage of some of our operators scales with the number of objects in your Kubernetes cluster. +However, you can fine-tune the memory of your operators using the documentation below, so this note is only about the default resources! + == Customizing operator installations 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: value: kafka-namespace ---- -IMPORTANT: The described configuration mechanism currently does not work for secret and listener-operator due to restrictions on deploying DaemonSets. +=== secret and listener-operator + +Most operators are deployed using a Deployment, which olm allows to tweak the resources for. +secret and listener-operator use a DaemonSet instead, which can not be deployed and tweaked by olm. +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. +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. + +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. == Security context constraints From caaed28feb19f0c885d452c8922ed4831c0ee0ca Mon Sep 17 00:00:00 2001 From: Sebastian Bernauer Date: Wed, 5 Aug 2026 13:00:29 +0200 Subject: [PATCH 2/2] Apply suggestions from code review Co-authored-by: Razvan-Daniel Mihai <84674+razvan@users.noreply.github.com> --- modules/ROOT/pages/kubernetes/openshift.adoc | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/modules/ROOT/pages/kubernetes/openshift.adoc b/modules/ROOT/pages/kubernetes/openshift.adoc index 41a34c03e..83e31f36b 100644 --- a/modules/ROOT/pages/kubernetes/openshift.adoc +++ b/modules/ROOT/pages/kubernetes/openshift.adoc @@ -7,9 +7,9 @@ SDP operators are certified for the OpenShift platform and can be installed from 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. -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. +IMPORTANT: The operators deployed with 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. The reason is that memory usage of some of our operators scales with the number of objects in your Kubernetes cluster. -However, you can fine-tune the memory of your operators using the documentation below, so this note is only about the default resources! +However, you can fine-tune the operator memory requirements using a custom Subscription object as described below, so this note is only about the default resources! == Customizing operator installations @@ -59,10 +59,8 @@ spec: === secret and listener-operator -Most operators are deployed using a Deployment, which olm allows to tweak the resources for. -secret and listener-operator use a DaemonSet instead, which can not be deployed and tweaked by olm. -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. -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. +The secret and listener operator are not deployed by OLM directly but rather by a helper tool called `olm-deployer`. This tool is needed to work around some OLM limitations that prevent it from directly installing these operators. +In this case, `olm-deployer` takes **it's own** resource requests and applies them to all containers on the `DaemonSets` of these operators.. 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.