From 1102a542eacbd3751fdc926a1227540fefd4f0af Mon Sep 17 00:00:00 2001 From: rfisher001 Date: Thu, 16 May 2024 12:23:46 +0000 Subject: [PATCH] =?UTF-8?q?[CI]=20Publish=20Documentation=20for=20cc87b07c?= =?UTF-8?q?0fb303184ed2d0d7084c4352d98ff7bf=20-=20cc87b07c0fb303184ed2d0d7?= =?UTF-8?q?084c4352d98ff7bf=20=F0=9F=9A=80?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- 4.12-4.14/API-Compatibility.html | 113 +++- 4.12-4.14/CNF-Upgrade-Prep.html | 110 +++- 4.12-4.14/OCP-upgrade-prep.html | 226 ++++++- 4.12-4.14/Upgrade-process-step-13.html | 465 +++++++++++++ 4.12-4.14/Upgrade-process-step-3.html | 456 +++++++++++++ 4.12-4.14/Upgrade-process-step-6.html | 458 +++++++++++++ 4.12-4.14/Upgrade-process-step-9.html | 623 ++++++++++++++++++ 4.12-4.14/Upgrade-process.html | 512 ++++++++++++++ .../_images/4.12to4.14-upgrade-graph.png | Bin 0 -> 71527 bytes 4.12-4.14/index.html | 110 +++- 4.12-4.14/introduction.html | 110 +++- sitemap.xml | 32 +- 12 files changed, 3184 insertions(+), 31 deletions(-) create mode 100644 4.12-4.14/Upgrade-process-step-13.html create mode 100644 4.12-4.14/Upgrade-process-step-3.html create mode 100644 4.12-4.14/Upgrade-process-step-6.html create mode 100644 4.12-4.14/Upgrade-process-step-9.html create mode 100644 4.12-4.14/Upgrade-process.html create mode 100644 4.12-4.14/_images/4.12to4.14-upgrade-graph.png diff --git a/4.12-4.14/API-Compatibility.html b/4.12-4.14/API-Compatibility.html index 22d265a..5e9ca4f 100644 --- a/4.12-4.14/API-Compatibility.html +++ b/4.12-4.14/API-Compatibility.html @@ -152,10 +152,118 @@

+
  • + Environment considerations +
    • +
  • + + Platform preparation + +
    • + + +
  • + + OCP Upgrade Process Flow + +
    • +
  • + + OCP Upgrade Process Flow - Continued - Step 3 +
  • - Applying MCPs + + OCP Upgrade Process Flow - Continued - Step 6 + +
    • +
  • + + OCP Upgrade Process Flow - Continued - Step 9 + +
    • +
  • + + OCP Upgrade Process Flow - Continued - Step 13 +
    • @@ -196,9 +304,6 @@

    Kubernetes Version Skew

    Support of specific API versions needs to be maintained by each cluster operator. With new releases of operators come new APIs. Therefore, the changes or skews in APIs need to be maintained. To a certain extent the APIs can be compatible across several releases of an operator. This list of operators and the releases that are compatible are at: https://kubernetes.io/releases/version-skew-policy

    -
    -

    The easiest way verify your application functionality will still work, is to make sure that you follow

    -
    diff --git a/4.12-4.14/CNF-Upgrade-Prep.html b/4.12-4.14/CNF-Upgrade-Prep.html index c4f3621..7c271b7 100644 --- a/4.12-4.14/CNF-Upgrade-Prep.html +++ b/4.12-4.14/CNF-Upgrade-Prep.html @@ -152,10 +152,118 @@

    +
  • + Environment considerations +
    • +
  • + + Platform preparation + +
    • + + +
  • + + OCP Upgrade Process Flow + +
    • +
  • + + OCP Upgrade Process Flow - Continued - Step 3 + +
    • +
  • + + OCP Upgrade Process Flow - Continued - Step 6 + +
    • +
  • + + OCP Upgrade Process Flow - Continued - Step 9 +
  • - Applying MCPs + + OCP Upgrade Process Flow - Continued - Step 13 +
    • diff --git a/4.12-4.14/OCP-upgrade-prep.html b/4.12-4.14/OCP-upgrade-prep.html index aa880c5..2c30064 100644 --- a/4.12-4.14/OCP-upgrade-prep.html +++ b/4.12-4.14/OCP-upgrade-prep.html @@ -6,7 +6,7 @@ OCP Upgrade Preparation :: LAB - Telco OCP Upgrade Lab - + @@ -152,10 +152,118 @@

    +
  • + Environment considerations +
    • +
  • + + Platform preparation + +
    • + + +
  • + + OCP Upgrade Process Flow + +
    • +
  • + + OCP Upgrade Process Flow - Continued - Step 3 +
  • - Applying MCPs + + OCP Upgrade Process Flow - Continued - Step 6 + +
    • +
  • + + OCP Upgrade Process Flow - Continued - Step 9 + +
    • +
  • + + OCP Upgrade Process Flow - Continued - Step 13 +
    • @@ -223,7 +331,7 @@

    OLM Operator compatibility

    -

    There is a set of Red Hat Operators that are NOT part of the cluster operators which are otherwise known as the OLM installed operators. To determine the compatibility of these OLM installed operators there is a great web based tool that can be used to determine which versions of OCP are compatible with specific releases of an Operator. This tool is meant to tell you if you need to upgrade an Operator after each Y-Stream upgrade or if you can wait until you have fully upgraded to the next EUS release. +

    There is a set of Red Hat Operators that are NOT part of the cluster operators which are otherwise known as the OLM installed operators. To determine the compatibility of these OLM installed operators there is a great web based tool that can be used to determine which versions of OCP are compatible with specific releases of an Operator. This tool is meant to tell you if you need to upgrade an Operator after each Y-Stream upgrade or if you can wait until you have fully upgraded to the next EUS release. In Step 9 under the “Upgrade Process Flow” section you will find additional information regarding what you need to do if an Operator needs to be upgraded after performing the first Y-Stream Control Plane upgrade.

    @@ -345,11 +453,11 @@ 

    # oc get no
 NAME                                           STATUS   ROLES    AGE   VERSION
-euschannel-ctlplane-0.test.corp   Ready    master   25d   v1.23.12+8a6bfe4
-euschannel-ctlplane-1.test.corp   Ready    master   25d   v1.23.12+8a6bfe4
-euschannel-ctlplane-2.test.corp   Ready    master   25d   v1.23.12+8a6bfe4
-euschannel-worker-0.test.corp     Ready    worker   25d   v1.23.12+8a6bfe4
-euschannel-worker-1.test.corp     Ready    worker   25d   v1.23.12+8a6bfe4
    +ctrl-plane-0 Ready control-plane,master 39d v1.25.10+28ed2d7 +ctrl-plane-1 Ready control-plane,master 39d v1.25.10+28ed2d7 +ctrl-plane-2 Ready control-plane,master 39d v1.25.10+28ed2d7 +worker-0 Ready worker 39d v1.25.10+28ed2d7 +worker-1 Ready worker 39d v1.25.10+28ed2d7

    @@ -390,8 +498,8 @@

    Labeling no

    -
    oc label node euschannel-worker-0.test.corp node-role.kubernetes.io/mcp-1=
-oc label node euschannel-worker-1.test.corp node-role.kubernetes.io/mcp-2=
    +
    oc label node worker-0 node-role.kubernetes.io/mcp-1=
+oc label node worker-1 node-role.kubernetes.io/mcp-2=
    @@ -410,11 +518,11 @@

    Labeling no 
    # oc get no
 NAME                                STATUS   ROLES          AGE   VERSION
-euschannel-ctlplane-0.test.corp   Ready    master         25d   v1.23.12+8a6bfe4
-euschannel-ctlplane-1.test.corp   Ready    master         25d   v1.23.12+8a6bfe4
-euschannel-ctlplane-2.test.corp   Ready    master         25d   v1.23.12+8a6bfe4
-euschannel-worker-0.test.corp     Ready    mcp-1,worker   25d   v1.23.12+8a6bfe4
-euschannel-worker-1.test.corp     Ready    mcp-2,worker   25d   v1.23.12+8a6bfe4
    +ctrl-plane-0 Ready control-plane,master 39d v1.25.10+28ed2d7 +ctrl-plane-1 Ready control-plane,master 39d v1.25.10+28ed2d7 +ctrl-plane-2 Ready control-plane,master 39d v1.25.10+28ed2d7 +worker-0 Ready mcp-1,worker 39d v1.25.10+28ed2d7 +worker-1 Ready mcp-2,worker 39d v1.25.10+28ed2d7

    @@ -519,9 +627,95 @@

    Monitor MCP for +
    +

    Environment considerations

    +
    +
    +

    In Telecommunications environments most of the clusters are kept in an “air gapped” or disconnected network. Therefore, you will need to update your offline image repository. When choosing which images to include, please review the OCP API Compatibility Policy section to make sure the cluster will be able to upgrade to the new version of OCP. Setting up and managing an offline image repository is currently out of scope at this time but will be added at a later date.

    +
    +
    +
    +
    +

    Platform preparation

    +
    +
    +

    This section should be used as a basic set of checks and verifications to make sure that your cluster is ready for an upgrade.

    +
    +
    +

    Basic cluster checks

    +
    +

    First you will need to verify that there are no issues with failed pods within the cluster that will stop the upgrade. A very easy first check is to run:

    +
    +
    +
    +
    [cnf@utility ~]$ oc get po -A | egrep -vi 'complete|running'
+NAMESPACE         NAME       READY   STATUS      RESTARTS        AGE
+[cnf@utility ~]$
    +
    +
    +
    + + + + + +
    + + +You may need to run this twice if there are pods that are in pending state as they may just have moved around due to normal operating conditions of the cluster. +
    +
    +
    +

    If there are problems with pods, please review the troubleshooting documentation to determine what the issue is with the pod(s).

    +
    +
    +

    Next verify that all nodes within the cluster are available:

    +
    +
    +
    +
    jcl@utility ~]$ oc get no
+NAME           STATUS   ROLES                  AGE   VERSION
+ctrl-plane-0   Ready    control-plane,master   32d   v1.25.14+a52e8df
+ctrl-plane-1   Ready    control-plane,master   32d   v1.25.14+a52e8df
+ctrl-plane-2   Ready    control-plane,master   32d   v1.25.14+a52e8df
+worker-0       Ready    mcp-1,worker           32d   v1.25.14+a52e8df
+worker-1       Ready    mcp-2,worker           32d   v1.25.14+a52e8df
    +
    +
    +
    +

    Verify that all baremetal nodes are fully provisioned and ready in the cluster. Here is an example of a cluster that has a baremetal node that had an error while provisioning:

    +
    +
    +
    +
    cnf@utility ~]$ oc get bmh -n openshift-machine-api
+NAME           STATE       CONSUMER                   ONLINE   ERROR   AGE
+ctrl-plane-0   unmanaged   cnf-58879-master-0         true             33d
+ctrl-plane-1   unmanaged   cnf-58879-master-1         true             33d
+ctrl-plane-2   unmanaged   cnf-58879-master-2         true             33d
+worker-0       unmanaged   cnf-58879-worker-0-45879   true             33d
+worker-1       unmanaged   cnf-58879-worker-0-dszsh   true             33d
    +
    +
    +
    +

    Now verify that all cluster operators are ready:

    +
    +
    +
    +
    [cnf@utility ~]$ oc get co
+NAME                                       VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
+authentication                             4.12.45   True        False         False      17h
+baremetal                                  4.12.45   True        False         False      32d
+...
+service-ca                                 4.12.45   True        False         False      32d
+storage                                    4.12.45   True        False         False      32d
    +
    +
    +
    +
    +