Skip to content

Commit 49b902f

Browse files
authored
Merge pull request #63218 from skopacz1/OSDOCS-5912
OSDOCS-5912: OSUS architecture recommendations
2 parents ad50906 + 29da6c2 commit 49b902f

File tree

1 file changed

+8
-0
lines changed

1 file changed

+8
-0
lines changed

modules/disconnected-osus-overview.adoc

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,4 +11,12 @@ The OpenShift Update Service (OSUS) provides update recommendations to {product-
1111

1212
However, clusters in a disconnected environment cannot access these public APIs to retrieve update information. To have a similar update experience in a disconnected environment, you can install and configure the OpenShift Update Service locally so that it is available within the disconnected environment.
1313

14+
A single OSUS instance is capable of serving recommendations to thousands of clusters.
15+
OSUS can be scaled horizontally to cater to more clusters by changing the replica value.
16+
So for most disconnected use cases, one OSUS instance is enough.
17+
For example, Red Hat hosts just one OSUS instance for the entire fleet of connected clusters.
18+
19+
If you want to keep update recommendations separate in different environments, you can run one OSUS instance for each environment.
20+
For example, in a case where you have separate test and stage environments, you might not want a cluster in a stage environment to receive update recommendations to version A if that version has not been tested in the test environment yet.
21+
1422
The following sections describe how to install a local OSUS instance and configure it to provide update recommendations to a cluster.

0 commit comments

Comments
 (0)