Skip to content

Commit 077ccc9

Browse files
committed
BZ#1995435: Change the update server
Fixes: BZ1995435 Added a section on how to change the upstream for both the cases: CLI and web console. Signed-off-by: Servesha Dudhgaonkar <[email protected]>
1 parent 2a3e925 commit 077ccc9

File tree

5 files changed

+61
-0
lines changed

5 files changed

+61
-0
lines changed
Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * updating/updating-cluster-cli.adoc
4+
// * updating/updating-cluster-rhel-compute.adoc
5+
6+
[id="update-changing-update-server-cli_{context}"]
7+
= Changing the update server by using the CLI
8+
9+
Changing the update server is optional. If you have an OpenShift Update Service (OSUS) installed and configured locally, you must set the URL for the server as the `upstream` to use the local server during updates. The default value for `upstream` is `\https://api.openshift.com/api/upgrades_info/v1/graph`.
10+
11+
.Procedure
12+
13+
* Change the `upstream` parameter value in the cluster version:
14+
+
15+
[source,terminal]
16+
----
17+
$ oc patch clusterversion/version --patch '{"spec":{"upstream":"<update-server-url>"}}' --type=merge
18+
----
19+
The `<update-server-url>` variable specifies the URL for the update server.
20+
+
21+
.Example output
22+
+
23+
[source,terminal]
24+
----
25+
clusterversion.config.openshift.io/version patched
26+
----
Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * updating/updating-cluster.adoc
4+
5+
[id="update-changing-update-server-web_{context}"]
6+
= Changing the update server by using the web console
7+
8+
Changing the update server is optional. If you have an OpenShift Update Service (OSUS) installed and configured locally, you must set the URL for the server as the `upstream` to use the local server during updates.
9+
10+
.Procedure
11+
12+
. Navigate to *Administration* -> *Cluster Settings*, click *version*.
13+
. Click the *YAML* tab and then edit the `upstream` parameter value:
14+
+
15+
.Example output
16+
+
17+
[source,yaml]
18+
----
19+
...
20+
spec:
21+
clusterID: db93436d-7b05-42cc-b856-43e11ad2d31a
22+
upstream: '<update-server-url>' <1>
23+
...
24+
----
25+
<1> The `<update-server-url>` variable specifies the URL for the update server.
26+
+
27+
The default `upstream` is `\https://api.openshift.com/api/upgrades_info/v1/graph`.
28+
29+
. Click *Save*.

updating/updating-cluster-between-minor.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -44,3 +44,5 @@ include::modules/update-using-custom-machine-config-pools-canary.adoc[leveloffse
4444
If you want to use the canary rollout update process, see xref:../updating/update-using-custom-machine-config-pools.adoc#update-using-custom-machine-config-pools[Performing a canary rollout update].
4545

4646
include::modules/update-upgrading-web.adoc[leveloffset=+1]
47+
48+
include::modules/update-changing-update-server-web.adoc[leveloffset=+1]

updating/updating-cluster-cli.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -35,3 +35,5 @@ include::modules/update-service-overview.adoc[leveloffset=+1]
3535
include::modules/understanding-upgrade-channels.adoc[leveloffset=+1]
3636

3737
include::modules/update-upgrading-cli.adoc[leveloffset=+1]
38+
39+
include::modules/update-changing-update-server-cli.adoc[leveloffset=+1]

updating/updating-cluster.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -28,4 +28,6 @@ include::modules/update-service-overview.adoc[leveloffset=+1]
2828

2929
include::modules/understanding-upgrade-channels.adoc[leveloffset=+1]
3030

31+
include::modules/update-changing-update-server-web.adoc[leveloffset=+1]
32+
3133
include::modules/update-upgrading-web.adoc[leveloffset=+1]

0 commit comments

Comments
 (0)