Skip to content

Document olm-deployer and fix secret/listener-operator memory docs #912

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
sbernauer merged 2 commits into from
Aug 5, 2026
Merged

Document olm-deployer and fix secret/listener-operator memory docs #912

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
14b5a97
Document olm-deployer and fix secret/listener-operator memory docs
sbernauer Aug 5, 2026
caaed28
Apply suggestions from code review
sbernauer Aug 5, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 10 additions & 1 deletion modules/ROOT/pages/kubernetes/openshift.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 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 operator memory requirements using a custom Subscription object as described 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.
Expand Down Expand Up @@ -53,7 +57,12 @@ 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

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.

== Security context constraints

Expand Down
Loading