1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 21:46:22 +01:00

Updating 4.5 versions from 4.5.0 to 4.5.2

This commit is contained in:
Andrea Hoffer
2020-07-15 09:09:46 -04:00
parent 6bf7571db9
commit db4fdd300f
14 changed files with 113 additions and 113 deletions

View File

@@ -47,7 +47,7 @@ The Metering Operator is shown as 4.5. For example:
+
----
Metering
4.5.0-202005202015 provided by Red Hat, Inc
4.5.0-202007012112.p0 provided by Red Hat, Inc
----
.Verification
@@ -72,8 +72,8 @@ $ oc get csv | grep metering
In the following example, the 4.5 Metering Operator upgrade is successful and replaces the 4.4 metering installation:
+
----
NAME DISPLAY VERSION REPLACES PHASE
metering-operator.4.5.0-202006161654 Metering 4.5.0-202006161654 metering-operator.4.4.0-202005252114 Succeeded
NAME DISPLAY VERSION REPLACES PHASE
metering-operator.4.5.0-202007012112.p0 Metering 4.5.0-202007012112.p0 metering-operator.4.4.0-202005252114 Succeeded
----
--

View File

@@ -45,8 +45,8 @@ Manage various aspects of the {product-title} release process, such as viewing i
.Example: Generate a changelog between two releases and save to `changelog.md`
----
$ oc adm release info --changelog=/tmp/git \
quay.io/openshift-release-dev/ocp-release:4.5.0-rc.7 \
quay.io/openshift-release-dev/ocp-release:4.5.0 \
quay.io/openshift-release-dev/ocp-release:4.5.0-rc.7-x86_64 \
quay.io/openshift-release-dev/ocp-release:4.5.4-x86_64 \
> changelog.md
----

View File

@@ -157,15 +157,15 @@ oc get csv --all-namespaces
----
+
----
NAMESPACE NAME DISPLAY VERSION REPLACES PHASE
default elasticsearch-operator.4.5.0-202006160135 Elasticsearch Operator 4.5.0-202006160135 Succeeded
kube-node-lease elasticsearch-operator.4.5.0-202006160135 Elasticsearch Operator 4.5.0-202006160135 Succeeded
kube-public elasticsearch-operator.4.5.0-202006160135 Elasticsearch Operator 4.5.0-202006160135 Succeeded
kube-system elasticsearch-operator.4.5.0-202006160135 Elasticsearch Operator 4.5.0-202006160135 Succeeded
openshift-apiserver-operator elasticsearch-operator.4.5.0-202006160135 Elasticsearch Operator 4.5.0-202006160135 Succeeded
openshift-apiserver elasticsearch-operator.4.5.0-202006160135 Elasticsearch Operator 4.5.0-202006160135 Succeeded
openshift-authentication-operator elasticsearch-operator.4.5.0-202006160135 Elasticsearch Operator 4.5.0-202006160135 Succeeded
openshift-authentication elasticsearch-operator.4.5.0-202006160135 Elasticsearch Operator 4.5.0-202006160135 Succeeded
NAMESPACE NAME DISPLAY VERSION REPLACES PHASE
default elasticsearch-operator.4.5.0-202007012112.p0 Elasticsearch Operator 4.5.0-202007012112.p0 Succeeded
kube-node-lease elasticsearch-operator.4.5.0-202007012112.p0 Elasticsearch Operator 4.5.0-202007012112.p0 Succeeded
kube-public elasticsearch-operator.4.5.0-202007012112.p0 Elasticsearch Operator 4.5.0-202007012112.p0 Succeeded
kube-system elasticsearch-operator.4.5.0-202007012112.p0 Elasticsearch Operator 4.5.0-202007012112.p0 Succeeded
openshift-apiserver-operator elasticsearch-operator.4.5.0-202007012112.p0 Elasticsearch Operator 4.5.0-202007012112.p0 Succeeded
openshift-apiserver elasticsearch-operator.4.5.0-202007012112.p0 Elasticsearch Operator 4.5.0-202007012112.p0 Succeeded
openshift-authentication-operator elasticsearch-operator.4.5.0-202007012112.p0 Elasticsearch Operator 4.5.0-202007012112.p0 Succeeded
openshift-authentication elasticsearch-operator.4.5.0-202007012112.p0 Elasticsearch Operator 4.5.0-202007012112.p0 Succeeded
...
----
+
@@ -244,7 +244,7 @@ oc get csv -n openshift-logging
----
NAMESPACE NAME DISPLAY VERSION REPLACES PHASE
...
openshift-logging clusterlogging.4.5.0-202006160135 Cluster Logging 4.5.0-202006160135 Succeeded
openshift-logging clusterlogging.4.5.0-202007012112.p0 Cluster Logging 4.5.0-202007012112.p0 Succeeded
...
----
@@ -355,7 +355,7 @@ However, an unmanaged deployment does not receive updates until cluster logging
<5> Specify the number of Elasticsearch nodes. See the note that follows this list.
<6> Enter the name of an existing StorageClass for Elasticsearch storage. For best performance, specify a StorageClass that allocates block storage.
<7> Settings for configuring Kibana. Using the CR, you can scale Kibana for redundancy and configure the CPU and memory for your Kibana pods. For more information, see *Configuring Kibana*.
<8> Settings for configuring the Curator schedule. Curator is used to remove data that is in the Elasticsearch index format prior to {product-title} 4.5 and will be removed in a later release.
<8> Settings for configuring the Curator schedule. Curator is used to remove data that is in the Elasticsearch index format prior to {product-title} 4.5 and will be removed in a later release.
<9> Settings for configuring Fluentd. Using the CR, you can configure Fluentd CPU and memory limits. For more information, see *Configuring Fluentd*.
+
[NOTE]

View File

@@ -52,7 +52,7 @@ The Elasticsearch Operator is shown as 4.5. For example:
+
----
Elasticsearch Operator
4.5.0-202005201915 provided
4.5.0-202007012112.p0 provided
by Red Hat, Inc
----
+
@@ -76,7 +76,7 @@ The Cluster Logging Operator is shown as 4.5. For example:
+
----
Cluster Logging
4.5.0-202005201915 provided
4.5.0-202007012112.p0 provided
by Red Hat, Inc
----
+

View File

@@ -11,7 +11,7 @@ To see the current version that your cluster is on, type:
$ oc get clusterversion
NAME    VERSION   AVAILABLE PROGRESSING SINCE STATUS
version 4.5.0-0.0 True      False       10h   Cluster version is 4.5.0-0.0
version 4.5.4 True      False       10h   Cluster version is 4.5.4
----
Each release version is represented by a set of images. To see basic release information and a list of those images, type:

View File

@@ -6,7 +6,7 @@
[id="installation-azure-regions_{context}"]
= Supported Azure regions
The installation program dynamically generates the list of available Microsoft Azure regions based on your subscription. The following Azure regions were tested and validated in {product-title} version 4.5.0:
The installation program dynamically generates the list of available Microsoft Azure regions based on your subscription. The following Azure regions were tested and validated in {product-title} version 4.5.4:
* australiacentral (Australia Central)
* australiaeast (Australia East)

View File

@@ -32,36 +32,36 @@ cluster on infrastructure that you provide.
$ watch -n5 oc get clusteroperators
NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE
authentication 4.5.0 True False False 7m56s
cloud-credential 4.5.0 True False False 31m
cluster-autoscaler 4.5.0 True False False 16m
console 4.5.0 True False False 10m
csi-snapshot-controller 4.5.0 True False False 16m
dns 4.5.0 True False False 22m
etcd 4.5.0 False False False 25s
image-registry 4.5.0 True False False 16m
ingress 4.5.0 True False False 16m
insights 4.5.0 True False False 17m
kube-apiserver 4.5.0 True False False 19m
kube-controller-manager 4.5.0 True False False 20m
kube-scheduler 4.5.0 True False False 20m
kube-storage-version-migrator 4.5.0 True False False 16m
machine-api 4.5.0 True False False 22m
machine-config 4.5.0 True False False 22m
marketplace 4.5.0 True False False 16m
monitoring 4.5.0 True False False 10m
network 4.5.0 True False False 23m
node-tuning 4.5.0 True False False 23m
openshift-apiserver 4.5.0 True False False 17m
openshift-controller-manager 4.5.0 True False False 15m
openshift-samples 4.5.0 True False False 16m
operator-lifecycle-manager 4.5.0 True False False 22m
operator-lifecycle-manager-catalog 4.5.0 True False False 22m
operator-lifecycle-manager-packageserver 4.5.0 True False False 18m
service-ca 4.5.0 True False False 23m
service-catalog-apiserver 4.5.0 True False False 23m
service-catalog-controller-manager 4.5.0 True False False 23m
storage 4.5.0 True False False 17m
authentication 4.5.4 True False False 7m56s
cloud-credential 4.5.4 True False False 31m
cluster-autoscaler 4.5.4 True False False 16m
console 4.5.4 True False False 10m
csi-snapshot-controller 4.5.4 True False False 16m
dns 4.5.4 True False False 22m
etcd 4.5.4 False False False 25s
image-registry 4.5.4 True False False 16m
ingress 4.5.4 True False False 16m
insights 4.5.4 True False False 17m
kube-apiserver 4.5.4 True False False 19m
kube-controller-manager 4.5.4 True False False 20m
kube-scheduler 4.5.4 True False False 20m
kube-storage-version-migrator 4.5.4 True False False 16m
machine-api 4.5.4 True False False 22m
machine-config 4.5.4 True False False 22m
marketplace 4.5.4 True False False 16m
monitoring 4.5.4 True False False 10m
network 4.5.4 True False False 23m
node-tuning 4.5.4 True False False 23m
openshift-apiserver 4.5.4 True False False 17m
openshift-controller-manager 4.5.4 True False False 15m
openshift-samples 4.5.4 True False False 16m
operator-lifecycle-manager 4.5.4 True False False 22m
operator-lifecycle-manager-catalog 4.5.4 True False False 22m
operator-lifecycle-manager-packageserver 4.5.4 True False False 18m
service-ca 4.5.4 True False False 23m
service-catalog-apiserver 4.5.4 True False False 23m
service-catalog-controller-manager 4.5.4 True False False 23m
storage 4.5.4 True False False 17m
----
+
When all of the cluster Operators are `AVAILABLE`, you can complete the installation.

View File

@@ -40,7 +40,7 @@ The Ignition config files that the installation program generates contain certif
----
$ oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version False True 24m Working towards 4.5.0-0: 99% complete
version False True 24m Working towards 4.5.4: 99% complete
----
.. Run the following command to view the Operators managed on the control plane by
@@ -49,36 +49,36 @@ the Cluster Version Operator (CVO):
----
$ oc get clusteroperators
NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE
authentication 4.5.0 True False False 7m56s
cloud-credential 4.5.0 True False False 31m
cluster-autoscaler 4.5.0 True False False 16m
console 4.5.0 True False False 10m
csi-snapshot-controller 4.5.0 True False False 16m
dns 4.5.0 True False False 22m
etcd 4.5.0 False False False 25s
image-registry 4.5.0 True False False 16m
ingress 4.5.0 True False False 16m
insights 4.5.0 True False False 17m
kube-apiserver 4.5.0 True False False 19m
kube-controller-manager 4.5.0 True False False 20m
kube-scheduler 4.5.0 True False False 20m
kube-storage-version-migrator 4.5.0 True False False 16m
machine-api 4.5.0 True False False 22m
machine-config 4.5.0 True False False 22m
marketplace 4.5.0 True False False 16m
monitoring 4.5.0 True False False 10m
network 4.5.0 True False False 23m
node-tuning 4.5.0 True False False 23m
openshift-apiserver 4.5.0 True False False 17m
openshift-controller-manager 4.5.0 True False False 15m
openshift-samples 4.5.0 True False False 16m
operator-lifecycle-manager 4.5.0 True False False 22m
operator-lifecycle-manager-catalog 4.5.0 True False False 22m
operator-lifecycle-manager-packageserver 4.5.0 True False False 18m
service-ca 4.5.0 True False False 23m
service-catalog-apiserver 4.5.0 True False False 23m
service-catalog-controller-manager 4.5.0 True False False 23m
storage 4.5.0 True False False 17m
authentication 4.5.4 True False False 7m56s
cloud-credential 4.5.4 True False False 31m
cluster-autoscaler 4.5.4 True False False 16m
console 4.5.4 True False False 10m
csi-snapshot-controller 4.5.4 True False False 16m
dns 4.5.4 True False False 22m
etcd 4.5.4 False False False 25s
image-registry 4.5.4 True False False 16m
ingress 4.5.4 True False False 16m
insights 4.5.4 True False False 17m
kube-apiserver 4.5.4 True False False 19m
kube-controller-manager 4.5.4 True False False 20m
kube-scheduler 4.5.4 True False False 20m
kube-storage-version-migrator 4.5.4 True False False 16m
machine-api 4.5.4 True False False 22m
machine-config 4.5.4 True False False 22m
marketplace 4.5.4 True False False 16m
monitoring 4.5.4 True False False 10m
network 4.5.4 True False False 23m
node-tuning 4.5.4 True False False 23m
openshift-apiserver 4.5.4 True False False 17m
openshift-controller-manager 4.5.4 True False False 15m
openshift-samples 4.5.4 True False False 16m
operator-lifecycle-manager 4.5.4 True False False 22m
operator-lifecycle-manager-catalog 4.5.4 True False False 22m
operator-lifecycle-manager-packageserver 4.5.4 True False False 18m
service-ca 4.5.4 True False False 23m
service-catalog-apiserver 4.5.4 True False False 23m
service-catalog-controller-manager 4.5.4 True False False 23m
storage 4.5.4 True False False 17m
----
.. Run the following command to view your cluster Pods:

View File

@@ -42,7 +42,7 @@ $ export ARCHITECTURE=<server_architecture> <7>
$ REMOVABLE_MEDIA_PATH=<path> <8>
----
<1> For `<release_version>`, specify the tag that corresponds to the version of {product-title} to
install, such as `4.5.0`.
install, such as `4.5.4`.
<2> For `<local_registry_host_name>`, specify the registry domain name for your mirror
repository, and for `<local_registry_host_port>`, specify the port that it
serves content on.

View File

@@ -26,31 +26,31 @@ Operators so that they all become available.
$ watch -n5 oc get clusteroperators
NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE
authentication 4.5.0 True False False 69s
cloud-credential 4.5.0 True False False 12m
cluster-autoscaler 4.5.0 True False False 11m
console 4.5.0 True False False 46s
dns 4.5.0 True False False 11m
image-registry 4.5.0 True False False 5m26s
ingress 4.5.0 True False False 5m36s
kube-apiserver 4.5.0 True False False 8m53s
kube-controller-manager 4.5.0 True False False 7m24s
kube-scheduler 4.5.0 True False False 12m
machine-api 4.5.0 True False False 12m
machine-config 4.5.0 True False False 7m36s
marketplace 4.5.0 True False False 7m54m
monitoring 4.5.0 True False False 7h54s
network 4.5.0 True False False 5m9s
node-tuning 4.5.0 True False False 11m
openshift-apiserver 4.5.0 True False False 11m
openshift-controller-manager 4.5.0 True False False 5m943s
openshift-samples 4.5.0 True False False 3m55s
operator-lifecycle-manager 4.5.0 True False False 11m
operator-lifecycle-manager-catalog 4.5.0 True False False 11m
service-ca 4.5.0 True False False 11m
service-catalog-apiserver 4.5.0 True False False 5m26s
service-catalog-controller-manager 4.5.0 True False False 5m25s
storage 4.5.0 True False False 5m30s
authentication 4.5.4 True False False 69s
cloud-credential 4.5.4 True False False 12m
cluster-autoscaler 4.5.4 True False False 11m
console 4.5.4 True False False 46s
dns 4.5.4 True False False 11m
image-registry 4.5.4 True False False 5m26s
ingress 4.5.4 True False False 5m36s
kube-apiserver 4.5.4 True False False 8m53s
kube-controller-manager 4.5.4 True False False 7m24s
kube-scheduler 4.5.4 True False False 12m
machine-api 4.5.4 True False False 12m
machine-config 4.5.4 True False False 7m36s
marketplace 4.5.4 True False False 7m54m
monitoring 4.5.4 True False False 7h54s
network 4.5.4 True False False 5m9s
node-tuning 4.5.4 True False False 11m
openshift-apiserver 4.5.4 True False False 11m
openshift-controller-manager 4.5.4 True False False 5m943s
openshift-samples 4.5.4 True False False 3m55s
operator-lifecycle-manager 4.5.4 True False False 11m
operator-lifecycle-manager-catalog 4.5.4 True False False 11m
service-ca 4.5.4 True False False 11m
service-catalog-apiserver 4.5.4 True False False 5m26s
service-catalog-controller-manager 4.5.4 True False False 5m25s
storage 4.5.4 True False False 5m30s
----
. Configure the Operators that are not available.

View File

@@ -27,7 +27,7 @@ network-operator 1/1 1 1 56m
$ oc get clusteroperator/network
NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE
network 4.5.0 True False False 50m
network 4.5.4 True False False 50m
----
The following fields provide information about the status of the operator:
`AVAILABLE`, `PROGRESSING`, and `DEGRADED`. The `AVAILABLE` field is `True` when

View File

@@ -23,7 +23,7 @@ $ RELEASE_NAME='ocp-release' # <6>
$ ARCHITECTURE=<server_architecture> # <7>
$ REMOVABLE_MEDIA_PATH=<path> <8>
----
<1> For `<release_version>`, specify the tag that corresponds to the version of {product-title} to which you want to upgrade, such as `4.5.0`.
<1> For `<release_version>`, specify the tag that corresponds to the version of {product-title} to which you want to upgrade, such as `4.5.4`.
<2> For `<local_registry_host_name>`, specify the registry domain name for your mirror
repository, and for `<local_registry_host_port>`, specify the port that it
serves content on.

View File

@@ -28,7 +28,7 @@ known as `oc`, that matches the version for your updated version.
$ oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.5.0 True False 158m Cluster version is 4.5.0
version 4.5.4 True False 158m Cluster version is 4.5.4
----
. Review the current update channel information and confirm that your channel
@@ -89,7 +89,7 @@ $ oc get clusterversion -o json|jq ".items[0].spec"
"desiredUpdate": {
"force": false,
"image": "quay.io/openshift-release-dev/ocp-release@sha256:9c5f0df8b192a0d7b46cd5f6a4da2289c155fd5302dec7954f8f06c878160b8b",
"version": "4.5.0" <1>
"version": "4.5.4" <1>
},
"upstream": "https://api.openshift.com/api/upgrades_info/v1/graph"
}
@@ -143,5 +143,5 @@ updated to the new version:
$ oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.5.0 True False 2m Cluster version is 4.5.0
version 4.5.4 True False 2m Cluster version is 4.5.4
----

View File

@@ -20,7 +20,7 @@ endif::[]
If updates are available, you can update your cluster from the web console.
You can find information about available {product-title} advisories and updates
link:https://access.redhat.com/downloads/content/290/ver=4.5/rhel---7/4.5.1/x86_64/product-errata[in the errata section]
link:https://access.redhat.com/downloads/content/290/ver=4.5/rhel---7/4.5.4/x86_64/product-errata[in the errata section]
of the Customer Portal.
////
update link to 4.4 when available