Skip to content

TELCODOCS-1453: Adding SNO post-install config for OLM #68117

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
merged 1 commit into from
Nov 28, 2023
Merged

TELCODOCS-1453: Adding SNO post-install config for OLM #68117

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
15 changes: 15 additions & 0 deletions modules/ztp-sno-du-reducing-resource-usage-with-olm-pprof.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
// Module included in the following assemblies:
//
// * scalability_and_performance/ztp_far_edge/ztp-reference-cluster-configuration-for-vdu.adoc

:_mod-docs-content-type: CONCEPT
[id="ztp-sno-du-reducing-resource-usage-with-olm-pprof_{context}"]
= Operator Lifecycle Manager

{sno-caps} clusters that run distributed unit workloads require consistent access to CPU resources. Operator Lifecycle Manager (OLM) collects performance data from Operators at regular intervals, resulting in an increase in CPU utilisation. The following `ConfigMap` custom resource (CR) disables the collection of Operator performance data by OLM.

.Recommended cluster OLM configuration (`ReduceOLMFootprint.yaml`)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(ReduceOLMFootprint.yaml) is this required?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes - it links to a file in a recommend cluster spec container

[source,yaml]
----
include::snippets/ztp_ReduceOLMFootprint.yaml[]
----
2 changes: 2 additions & 0 deletions ...y_and_performance/ztp_far_edge/ztp-reference-cluster-configuration-for-vdu.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -88,6 +88,8 @@ include::modules/ztp-sno-du-removing-the-console-operator.adoc[leveloffset=+2]

include::modules/ztp-sno-du-reducing-resource-usage-with-cluster-monitoring.adoc[leveloffset=+2]

include::modules/ztp-sno-du-reducing-resource-usage-with-olm-pprof.adoc[leveloffset=+2]

include::modules/ztp-sno-du-configuring-lvms.adoc[leveloffset=+2]

include::modules/ztp-sno-du-disabling-network-diagnostics.adoc[leveloffset=+2]
Expand Down
9 changes: 9 additions & 0 deletions snippets/ztp_ReduceOLMFootprint.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
apiVersion: v1
kind: ConfigMap
metadata:
name: collect-profiles-config
namespace: openshift-operator-lifecycle-manager
data:
pprof-config.yaml: |
disabled: True

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

extra space??

Copy link
Contributor Author

@rohennes rohennes Nov 28, 2023 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's generally best practice to leave a space at the end of a file. Snippets perhaps are a bit different but doesn't really make much difference in the output 🤷‍♂️