My Oracle Support Banner

OCNE: Why Kubernetes update takes different number of hops in different environments? (Doc ID 2881925.1)

Last updated on APRIL 03, 2024

Applies to:

Oracle Cloud Native Environment (OCNE) - Version 1.3 and later
Linux x86-64

Goal

Why Kubernetes update takes different number of hops in different environments?

For Example:

OCC = Oracle Cloud at Customer
PCC = Oracle Private Cloud at Customer

On OCC, during Upgrade to OLCNE 1.2, that time Kubernetes version took 2 jumps: from current version 1.17.6 ==> 1.18.10 ==> 1.18.18

On PCC, during Upgrade to OLCNE 1.2, which took only 1 jump from. current version 1.17.9 ==> 1.18.18

Kubernetes version on OCC was on version 1.17.6 and on PCC was on version 1.17.9 before the update.

Is there any place where this upgrade path defined?
 

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Goal
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.