From 92c73e7830bef5d3c590d72e216effe833714253 Mon Sep 17 00:00:00 2001 From: Ondrej Chromy Date: Tue, 23 Sep 2025 11:28:38 +0200 Subject: [PATCH] [RHDEVDOCS-6472] Confirm SNO support for Pipelines fix commit no1 fix commit no2 fix commit no3 fix commit no4 fix commit no5 --- install_config/installing-pipelines.adoc | 4 ++++ modules/op-sno-support-reference.adoc | 27 ++++++++++++++++++++++++ 2 files changed, 31 insertions(+) create mode 100644 modules/op-sno-support-reference.adoc diff --git a/install_config/installing-pipelines.adoc b/install_config/installing-pipelines.adoc index 3dc7b7f572e3..d8d9c0ab7ebb 100644 --- a/install_config/installing-pipelines.adoc +++ b/install_config/installing-pipelines.adoc @@ -35,6 +35,10 @@ include::modules/op-installing-pipelines-operator-using-the-cli.adoc[leveloffset include::modules/op-pipelines-operator-in-restricted-environment.adoc[leveloffset=+1] +// {pipelines-title} single node OpenShift (SNO) support + +include::modules/op-sno-support-reference.adoc[leveloffset=+1] + [role="_additional-resources"] == Additional resources diff --git a/modules/op-sno-support-reference.adoc b/modules/op-sno-support-reference.adoc new file mode 100644 index 000000000000..86c901fc1ab3 --- /dev/null +++ b/modules/op-sno-support-reference.adoc @@ -0,0 +1,27 @@ +// This module is included in the following assemblies: +// * install_config/.adoc + +:_mod-docs-content-type: REFERENCE +[id="op-sno-support-reference_{context}"] += {pipelines-shortname} on Single Node OpenShift (SNO) + +You can run {pipelines-shortname} on a single-node cluster, making it suitable for small-scale deployments, testing, and development. All components and workloads share the same machine, simplifying setup and management. + +.Minimum requirements +For a Single Node OpenShift (SNO) cluster on `libvirt` UPI, the minimum hardware requirements are: + +* 12 vCPUs +* 64 GB RAM +* 240 GB disk space + +You must ensure your cluster meets these requirements before deploying {pipelines-shortname}. + +.Supported components +All {pipelines-shortname} components are fully supported on SNO. + +.Limitations +There are no specific limitations for {pipelines-shortname} on SNO beyond the following inherent constraints of a single-node cluster: + +* Scalability: Limited by node resources, for example by CPU or memory. +* Fault Tolerance: No redundancy. If the node fails, all workloads stop. +* Concurrency: Limited parallelism due to resource constraints.