►
From YouTube: Ask an OpenShift Admin (Ep 53): Updates and upgrades
Description
What happens in an OpenShift update vs. an upgrade? Changes with Red Hat OpenShift Container Platform can happen regularly, so we deploy a new version, which can be a bit scary because no one wants to push changes to an environment that might break stuff. This week on Ask an OpenShift Admin, we answer questions about when and what happens in an update vs an upgrade, pets vs cattle clusters and why we still need upgrade paths, the process of upgrading between minor versions, and we'll look at how you can visualize Red Hat's recommended updates with the Red Hat OpenShift Container Platform Update Graph. So join us to take a look at when and how OpenShift upgrades are necessary and some best practices for getting ready for those updates.
Want to learn more?
https://cloud.redhat.com/blog/ask-an-openshift-admin-office-hour-updates-and-upgrades?c_cid=7013a000002qG16AAE
Follow us:
Andrew Sullivan , https://twitter.com/practicalandrew
Jonathan Rickard, https://twitter.com/jrocktx1
Subscribe to Red Hat's YouTube channel: https://www.youtube.com/redhat/?sub_confirmation=1
About OpenShift:
Red Hat OpenShift is an open source container application platform based on the Kubernetes container orchestrator for enterprise application development and deployment.
Openshift.com https://red.ht/33Fh6uV
OpenShift on github https://github.com/openshift/
OpenShift on redhat.com https://red.ht/2o4ccDk
#RedHat #OpenShift #ContainerPlatform
A
B
Hello
and
welcome
to
this
week's
ask
an
open
shift.
Admin
live
stream.
This
is
our
first
stream
of
2022
and
happy
new
year.
Johnny,
hey
happy
new
year
yeah.
It's
it's
good
to
see
your
lovely
face,
stephanie
as
well
behind
the
scenes.
I
know
all
of
our
viewers.
Don't
don't
get
to
see
her,
but
before
and
after
you
and
I
do-
and
it
was,
it
was
great
to
to
finally
kick
things
off.
B
Indeed,
indeed
so
yeah
we,
we
had
a
conversation
back
before
the
holidays,
where
we
did
our
last
stream
of
2021
what
almost
a
month
ago-
and
we
were
both
like
well
taking
pto
like
in
two
days
and
then
we
come
back-
and
you
know
maybe
we
shouldn't
do
one
the
first
week
of
january,
because
there's
basically
no
time
in
between
so
apologies.
If
anybody
was
expecting
a
stream
last
week,
we
we
took
it
a
little
easy.
B
We
got
a
little
more
organized
if
you
will
and
we're
ready
to
go
for
this
year.
That's
right
refreshed
ready
to
go
yeah
yeah
as
as
it
were,
you
know
as
much
as
you
can
be
in
these
rather
interesting
times.
If
you
will
so,
I
hope
everybody
had
a
safe
holiday,
most
importantly,
and
hopefully,
folks
are
rested
and
relaxed.
B
B
Yeah
so
hello,
everyone,
hello
to
our
audience.
Thank
you
for
joining
us
today.
We
really
appreciate
you
being
here
so
the
ask
an
openshift
admin.
Livestream
is
a
part
of
the
office
hours
series
of
live
streams
here
on
red
hat,
live
streaming.
I
know
I
just
said:
live
stream
like
four
times
there,
so
what
that
means
is
that
we
are
here
to
answer
any
and
all
questions
that
you
happen
to
have
about
openshifts,
we'll
do
our
best
to
answer
those
here
on
the
stream.
B
We
also
have
a
blog
that
follows
up
each
one
of
these
three
and
I'm.
Following
up
on
getting
all
of
those
published
coming
up,
we
had
a
huge
backlog
on
the
blog
going
into
the
holidays
and
everything
so
yeah.
Normally
a
change
freeze,
I
I
hope
so
a
lot
of
times
it.
That
seems
to
be
50
50
in
my
experience,
like
some
organizations
have
a
freeze
kind
of
the
towards,
at
least
in
the
us
here,
right
towards
the
end,
the
entire
end
of
the
year,
because
it's
the
holiday
shopping
season.
B
It's
also
particularly
for
healthcare
companies.
It's
open
enrollment,
so
you
know
they
don't
want
to
have
all
of
that
stuff,
potentially
impacting
business.
So
and
then,
on
the
other
hand,
you
have
you
know
just
normal.
You
know
the
government
still
functions
and
still
does
its
thing
up
until
the
holidays
actually
happen.
And
then
you
know
people
are
gone.
So
it's
an
opportunity
for
the
it
folks
to
do
their
stuff,
so
yeah
anytime.
Anything,
that's
on
y'all's,
mind.
B
B
That
being
said,
we
do
have
a
topic
with
each
each
stream
that
we
do.
We
have
a
topic
that
we
use
to
kind
of
focus
or
or
center.
You
know
on
things
in
the
absence
of
your
questions,
if
you
will
but
of
course
don't
let
that
limit
your
imagination,
anything,
that's
that's
on
your
minds.
You
can
bring
up
regardless
of
what
the
topic
happens
to
be
so,
let's
see
johnny,
I'm
gonna,
I'm
gonna,
distract
you
for
a
minute.
Did
you
have
a
good
holiday?
Did
you
do
anything
exciting.
A
Nothing
exciting
no,
but
I
did
have
a
good
holiday.
You
know
like
we,
my
my
wife
goes
crazy.
You
know
she's
from
the
midwest,
and
so
like
christmas
is
like
the
the
holiday
of
holidays,
and
so
she
goes
all
out,
and
so
you
know
the
house
was
all
insane
and
it
was
good.
We
just
had
a
good
nice
like
quiet
christmas.
How
about
you.
B
Yeah
same
my
wife,
so
when
I
was
a
kid
we
always
traveled,
we
always
went
to
my
grandparents
every
year
and
my
wife
from
the
time
that
we
had
kids
she's
been
very
staunch,
very
adamant
about.
We
will
always
do
christmas
here
at
our
house
so
that
that's
always
been
kind
of
a
nice
and
relaxing
thing,
but
I
I
think
I
inherited
a
new
hobby
or
I've.
B
I've
been
told
I
am
acquiring
a
new
hobby,
so
one
of
my
one
of
my
good
friends,
former
co-worker
he
does
christmas
lights
like
goes
all
out
all
over
his
house
and
does
the
coordinated
light
shows
and
all
that
other
stuff,
oh
yeah.
So
this
was
the
first
time
in
two
years
that
we'd
seen
his
display
and
since
the
last
time
he
has
switched
to
all
individually
addressable
leds.
B
B
I
was
talking
with
somebody
like
as
soon
as
he
put
stuff
away
he's
planning
for
the
following
year
because,
like
there's
a
whole
group
of
people
here
in
the
rtp
area,
so
they'll
do
like
group
buys
of
individual
leds
and
then
he
builds
the
displays
and
solders.
The
led
like
it's
just
it's
a
crazy
amount
of
work.
A
B
B
B
If
you
have
not
updated
your
clusters,
I
would
strongly
encourage
you
to
do
that.
So
there
is
a
what's
the
word,
I'm
looking
for
here,
cve
page,
that
is
available
for
that
I'll
have
to
dig
up
the
link.
I
forgot
to
link
it
in
our
notes
document.
So
there
is
a
cve
page
that
goes
through
and
talks
about
how
it
impacts
every
version
of
openshift,
as
well
as
open
shift
components
like
the
logging
components
and
when
each
one
of
those
is
patched,
I
see
somebody
asking
about.
B
B
So
if,
if
you're
talking
about
openshift,
I
always
encourage
folks
to
look
at
learn.openshift.com,
that's
a
good
place
to
start.
You
can
also
go
to
depending
on.
If
you
want
to
learn
more
about
the
application
side,
the
developers
landing
spot
so
developers.redhead.com
they
have
a
lot
of
good
stuff
of
you
know:
hey.
How
do
I
deploy
an
application,
whether
it's
tyrell
or
to
open
shift.
B
B
B
B
B
Never,
no!
Please
update
system
permissions
yeah.
I
will
anyway,
so
I
just
posted
a
link
to
the
to
the
security
bulletin
for
that
cve
as
it
relates.
If
you
scroll
down
through
there
you'll
see
the
updates
for
affected
products,
you
can
see
everything
that's
in
there,
including
openshift4.
You
can
see
the
hive
container
so
interesting
note
here,
so
I
did
some
research
after
our
last
stream,
where
we
talked
about
this.
B
So
if
you
look
in
that
security
bulletin
for
red
hat,
openshift
4
the
first
item
in
the
middle
column,
the
component
that's
affected,
it
says,
is
hive
container.
That
is
not
related
to
hive
the
system
that
you
know.
We
talked
about
hive
when
we
were
talking
about
labs
and
you
know
kind
of
non-production
clusters,
so
red
hat
hive
or
open
shift
hive
is
a
way
of
deploying
clusters
programmatically
using
basically
kubernetes
constructs.
B
The
hive
container
that
this
is
referring
to
is
a
part
of
apache
hive.
Apache
hive
is
the
component.
That's
used
for
telemetry
reporting
within
openshift,
so
all
of
the
all
of
the
data
that
is
collected
and
then
sent
up
to
you
know
insights
as
well
as
console.redhat.com,
and
all
of
that,
so
that
that's
what
that's
referring
to.
So
if
you
saw-
and
there
was
some
confusion
even
amongst
myself
and
that's
why
I
started
to
really
dig
in
there
was
a
lot
of
folks
that
were
saying
you
know.
B
Oh,
you
just
need
to
update
the
logging
component
and
if
you
don't
have
openshift
logging
deployed,
then
you
should
be
fine
and
then
we
released
a
set
of
errata.
That
was,
you
know,
update
to
the
latest
openshift
version.
You
know
openshift
4.8.,
whatever
it
was
at
the
time
and
folks
were
confused
as
to
well.
B
Do
I
need
to
update
the
whole
openshift
cluster
in
order
to
mitigate
and
it
turns
out
yes,
because
that's
how
we
do
that
update
to
the
apache
hive
telemetry
reporting
component
inside
of
there,
and
the
reason
for
that
is
because
it
is
that
that
service,
that
component
is
controlled
by
the
cluster
version
operator,
and
that
was
part
of
what
spawned
today's
topic
of
you
know.
What
is
controlled
by
a
cluster
update
or
cluster
upgrade,
and
when
does
it?
When
does
it
affect
one
versus
the
other
right?
B
B
If
I'm
on
premises,
on
the
other
hand,
so
maybe
I'm
using
vsphere
upi,
I
have
a
couple
of
different
options
so,
for
example,
with
on-prem
vsphere
upi
I
can
power
off
those
nodes
and
then
resize
them,
and
that
applies
for
both
control,
plane
and
compute
nodes.
I
can
resize
them
and
then
power
them
back
on
and
allow
them
to
rejoin
the
cluster.
B
B
So
one
thing
to
note
is
that
technically
you
can
go
in
with,
for
example,
vsphere
or
rev
or
any
of
the
other
hypervisors
and
do
a
hot
add
right,
so
I
can
go
into
vsphere.
I
can
say
I
want
to
change
you
from
you
know:
12
cpus
to
16,
cpus
or
32
gigs
of
ram
to
64
or
whatever,
and
if
you
go
and
look
at
the
operating
system,
if
you
look
at
core
os,
it
will
report
the
appropriate
amount
right.
It's
just
rel
rel
has
supported
hot
ad
for
ages.
B
I
I
don't
know
how
long
the
problem
is.
Kublet
doesn't
recognize
that
those
resources
have
been
added
until
kublit
is
restarted,
so
the
usefulness
of
that
is
somewhat
limited.
If
I
have
a
static
pod
configuration
right.
So
what
I
mean
by
that
is
I've.
I've
deployed
workload
across
my
node
and
you
know:
there's
there's
10
pods
and
one
of
those
pods
is
consuming
90
of
the
resources.
Let
me
add,
you
know
a
bunch
more
resources
so
that
running
workload
would
technically
be
able
to
consume
those
additional
work.
B
B
So
the
usefulness
is
a
little
bit
limited
in
that
respect,
but
it
is
possible
to
do
hot.
Add
support
is
well.
I
don't
think
it
breaks
support
if
there's
issues
with
that,
it's
not
something
we
test.
As
far
as
I
know
so
I
I
don't
know
that
I
don't
know
how
helpful
we
would
we
would
support
would
be
johnny
any
any
thoughts.
A
B
Yeah-
and
there
is
it's
not
known-
and
I
I
can't
I
keep
trying
to
share
my
window
and
it's
not
working
I'll,
my
own
faults
for
not
testing
beforehand,
so
there
is
in
the
documentation.
You
can
explicitly
tell
it
which
nodes
to
scale
down.
So
if
you
go
in
you
know,
I've
got
my
machine
set.
I
edit
that
machine
set
to
change
the
say:
it's
aws
change
the
instance
type
and
then
scale
that
machine
set
up.
B
B
A
And
I
don't
know
if
we
talked
about
this
before,
but
that's
probably
my
favorite
feature
of
openshift4
is
the
machine
sets
like
that?
That's
you
know
back
in
the
day,
openshift
three
trying
to
add
nodes
to
the
cluster
and
that's
like
just
you
know,
crap
shoot.
You
didn't
know
if
it
was
gonna
work.
So
that's
I
love.
The
machine
sets
yeah.
B
I
I'm
with
you.
Operators
to
me
are
really
big,
though,
because
to
me
the
most
frustrating
thing
about
openshift
3
was
always
the
ansible
playbooks
yeah,
and
I
I
don't
know
about
others,
but
it
never
worked
right.
The
first
time
so
like
oh,
I
need
this.
You
know
I
need
to
add
a
new
node
to
the
cluster
okay.
Well,
let
me
run
the
playbook
and
something
failed.
Let
me
run
it
again
and
something
failed.
Let
me
run
it
again.
B
B
So
yeah
I
I
really
like-
and
it
was
a
huge
mindset
shift
for
me.
You
know
I
joined
red
hat
a
little
over
three
years
ago
and
you
know
3.11
was
out
at
that
point
in
time
and
I
don't
know
what
just
happened.
I'm
going
to
hit
cancel
sorry.
My
browser
just
came
up
and
was
like
hey.
You
need
to
reload
this
site,
but
no
so
I'm
gonna
not
do
that.
So
I
don't
lose
my
session
here
with
the
stream
but
yeah.
B
So
you
know
the
operators,
it
was
a
huge
mindset
shift
when
I
first
came
on
and
we
you
know
I
I
first
started
right
as
we
were
doing
the
initial
pre-release
testing
with
4.0,
which
I
never
saw
the
light
of
day.
4.1
was
the
first
ga
release-
and
I
I
remember
sitting
here
in
the
raleigh
tower
and
being
in
the
train,
the
trainer
training
yeah
during
the
trainer
training
and
like
we're
going
through-
and
you
know
learning
about
this.
You
know
wildly
different
paradigm
and
I'm
trying
to
change
things.
B
The
way
that
I
was
used
to
in
open
shift.
3
of
you
know
just
modifying
the
object
and
it'll,
and
you
know
then
the
operator
would
come
in
and
remove
my
my
edits
and
it's
oh,
what
is
going
on
here?
Why
are
you
doing
this
and
yeah
so
yeah?
It's,
I
have
to
say
once
I
got
used
to
it.
It's
been
really
really
nice.
You
know,
updates
and
upgrades
perfect
example.
A
Yeah
yeah,
we
we
had
an
issue
with
one
of
our
customers
where
we
were
trying
to
modify
dns
and
so
we're
like.
Oh,
let's
just
go
change,
resolve.com
no
big
deal,
and
so
we
would
change
it.
And
then
you
know
they
start
cycling
through
because
the
operator
picks
up.
It
says:
hey
you're
wrong,
so
it
goes
through
its
loop
and
it
starts
applying
yeah.
It's
pretty
awesome.
B
So,
let's
see
I
have
a
question
regarding
operators
and
how
they
work
with
kubernetes
after
creating
a
controller
using
the
operator
sdk
and
deploying
what
is
actually
happening
under
the
hood.
Let's
put
it
another
way,
how
does
kubernetes
know
that
it
has
a
new
controller
and
I
extend
the
functionality
using
the
api
extension
api.
B
So,
essentially,
an
operator
is
when
you
deploy
an
operator.
When
you
create
an
operator,
it
is
roughly
two
things,
so
the
first
one
is
using
custom
resource
definitions
right,
so
you
are
telling
kubernetes
hey,
create
this
new
api
namespace
or
this
new
api
endpoint,
and
when
you
get
a
request
for
that,
send
it
over
to
here,
and
that
here
is
the
second
part,
which
is
that
controller.
B
B
So
the
operator
is
when
I
say
you
know,
hey,
create
me
and
say:
I'm
gonna,
I'm
gonna
create
a
new
api
endpoint,
for
you
know
the
object.
Johnny
you
know
anytime.
I
want
to
interact
with.
I
need
a
new
johnny,
I'm
just
going
to
create
a
new
object
of
type
johnny
and
it
sends
it
over
to
the
controller
and
the
controller
does
something
with
it
that
something
could
be
as
simple
as
create
a
new
deployment.
B
B
B
It
basically
all
comes
around
to
being
the
same
set
of
things
right,
pods
that
are
deployed
via
something
like
a
you
know:
either
standalone
individual,
pods
or
via
deployment,
or
you
know,
a
replica
set,
config
maps
secrets,
it's
just
sometimes
they're
abstracted
by
things
like
an
operator
and
the
operand,
the
those
object
instances.
So
I
think
openshift
virtualization
is
another
good
example
of
that
right.
When
I
create
a
vm
right,
I'm
creating
an
object
in
the
api
named
virtual
machine,
and
that
is
nothing
more
than
the
definition
of
a
vm.
It's
not
creating
anything.
B
At
that
point.
When
I
go
to
power
on
that
vm,
the
operator
is
actually
creating
a
pod
and
it's
one
of
the.
I
think
it's
a
ver
launcher
pod
for
man.
I
think
it's
a
very
launcher
pod
and
that
pod
is
the
actual
running
vm
right.
So
it's
one
of
those
like
depending
on
how
you
do
it,
and
you
know
what
your
actual
goal
is.
It
could
be
many
different
things.
A
B
B
So
if
you
are
doing
google
or
duckduckgo
or
bing
or
whatever
your
search
engine
of
choice,
is
if
you're
searching
for
things
in
the
openshift
documentation,
you
may
have
noticed
historically
you'll
get
random
versions
for
things
like
you
search
for
you
know,
say
it's
a
persistent
volume
claim
and
for
a
long
time
I
think
it
was
like
the
openshift
3.4
documentation.
That
was
the
first,
the
first
hit
that
came
up
so
obviously
not
terribly.
You
know.
B
Maybe
pvcs
haven't
changed
that
much
since
then
I
would
argue
they
have
pretty
significantly
changed
since
then,
but
it's
also
very
confusing.
You
know,
especially
in
the
days
of
you,
know,
openshift
4.789,
to
get
documentation.
That's
three
plus
years
old,
four
years
old,
not
not
terribly
helpful,
so
the
docs
team
has
been
working
with
our
web
team
and
the
seo
folks
and
all
that
of
making
concerted
efforts
to
kind
of
de-index
an
end-of-life
old
documentation.
B
B
I
will
share
a
secret
or
a
tip
of
you
can
go
in
with
modern
browsers.
So
I
know
this
works
with
chrome
and
firefox
for
sure
I
haven't
tried
it
with
safari,
but
and
along
with
all
the
chromium,
derivatives
and
everything,
but
you
can
go
in
and
you
can
create
a
custom
search
engine
or
a
search
string.
B
So
if
you,
if
you've
ever
used
duckduckgo,
they
have
the
concept
of
they
call
them
the.
What
are
they
called
like?
You
can
do,
exclamation
g,
like
bang
g
and
then
your
search
term
and
it'll
search.
Google
or
you
can
do
you
know
bang
b
and
it'll,
search,
bing
and
stuff
like
that.
So
you
can
create
a
custom
search
term,
so
you
can
do
like
and
what
I
do
is
create
an
ocp.
So
I
do
ocp
space
and
then
my
term,
and
it
will
automatically
search
the
openshift
documentation.
B
So
it
would
be
the
same
as
doing
in
your
search
window.
You
know
search
term
and
then
space
site,
colon
http,
docs.openshift.com,
so
I'll
I'll
yeah.
Thank
you
for
letting
me
know.
Stephanie
there's
something
on
the
back
end,
going
on
with
the
sharing
so
we'll
get
that
fixed
for
next
week,
but
so
yeah.
I
will
share
that
process.
I've
got
it
in
a
gist
somewhere.
B
B
B
What
I
heard
was
it
was
related
to
log
for
shell,
so
oh
man
whoops,
oh,
they
just
disabled
it
to
prevent
issues.
Oh
okay,
gotcha
yeah,
so
I
I
use
that
all
the
time,
because
I
you
know
type
in
search
term
and
then
limit
it
to
just
openshift,
limited
to
just
kcs
articles
and
go
from
there
all
right.
Today's
topic
updates
and
upgrades-
and
I
said
before
you
know
earlier
that
you
know
we
had
I
I
had
started
considering
this
topic
previously
just
to
talk
about.
B
A
B
Question
about
that
so
that
that
kind
of
cemented
you
know
yes,
this
we're
going
to
make
this
a
topic
and
we're
going
to
talk
about
it,
even
though
it
is
arguably
something
that
we
talk
about.
You
know
kind
of
all
the
time
right.
It
seems
like
every
week
we're
talking
about.
What's
the
newest
release
or
the
release
status
or
upgrade
status,
you
know
from
version
x
to
version
y
or
whatever
it
happens.
A
Yeah
so
the
the
question
was,
it
actually
came
from
carl
mosca,
mosca
mosca,
but
yeah
he
he
reached
out,
and
he
asked
you
know
with
today's
operator
framework
and
the
way
that
the
clusters
are
deployed.
Why
are
we
still?
Why
do
we
still
have
pet
pet
clusters
instead
of
like
cattle
clusters
right?
So
why
aren't
we
instead
of
doing
these
massive
instead
of
doing
updates
right
from
four
nine
to
four
nine
one
to
four
nine,
four,
whatever?
A
You
know
the
major
really
so
it's
like
4.9
or
you
know
the
minor
release
rather,
and
you
know
a
lot
of
it
also
comes
down
to
you
know,
at
least
in
my
experience
has
been
resources.
You
know
so
we've
been
talking
about.
You
know
you
get
a
vpc
and
you're
very
restricted
within
that
vpc
of
what
you
can
build
and
what
you
can't
build
and
stuff
like
that,
and
so
you're
limited
to
the
number
of
hosts
that
you
can
have,
and
so
it
comes
down
to
just
a
resource
constraint.
A
B
I
don't
know
about
that.
It's
funny,
you
know
when
you
brought
up
that
question.
It
was
one
of
those
like
I
can
see
it
both
ways
of
particularly
if
you're
bought
in
on
the
whole.
You
know
12
factor,
cloud
native
application
thing.
You
know
yeah
the
underlying
infrastructure
is
disposable.
Why
should
I
care
about
it?
On
the
other
hand,
particularly
for
us
admins,
you
know
we,
we
love
our
clusters,
we
we
want
to
take
care
of
them,
we
want
to,
and
we
don't
do
it
intentionally.
B
B
You
know
no,
no
amount
of
you
know
us
deploying
new
clusters
and-
and
you
know,
pointing
to
them
and
saying
go
use
this
instead
is
going
to
have
any
effect.
If
the
application
team
says
sorry,
I
can't-
and
you
know
there
was
a
there-
was
a
question
yesterday.
What
was
it
and
and
somebody
somebody
asked
a
question
and
now
I'm
trying
to
remember
what
it
was
and
and
like
the
first
response
was,
why
would
you
want
to
do
this
and
there
was
the
the
the
person
responded?
B
Well,
we
have
containers
that
are
a
single
point
of
failure
and
you
know
if
oh
it
was
doing,
live
kernel
patching.
So
what
oracle
used
to
call
oh
gosh,
what
was
that
thing?
Where
you
could
you
can
patch
the
kernel
without
restarting
the
host?
You
know
so
they
were
asking
if
coreos
supports
that,
and
you
know
the
the
the
first
question
was
well.
Why
would
you
want
to
use
that
right?
B
B
A
Yeah
we
we
see
a
lot
of
times,
especially
in
like
when
I
was
in
consulting
where
you
know
we
do
these
things
called
container
adoption
journeys.
You
know
where
you
go
out
and,
like
you
go
out,
and
you
essentially
you
know
from
from
soup
to
you
know,
start
to
finish.
We
teach
people
how
to
use
build
containers,
use
container
platforms
and
stuff
like
that,
and
we
generally
recommend
that
we
have
like
a
dev
test
prod.
You
know
so
that
way
you
can
promote
between,
but
it's
it's
so
application
specific.
A
B
B
There's
no
panic!
Quite
like
the
panic
of
oh
no,
I
just
broke
something
on
the
accident,
which
is
yeah.
I
I
distinctly
remember.
It's
been
gosh
close
to
15
years
now,
since
I
was
a
very
junior,
vmware
admin
and
accidentally
unmounted,
the
nfs
data
store
and
watched
as
all
of
my
vms
were
disappearing,
and
I
didn't
know
why
and
it's
one
of
those
like
you
have
that
sinking.
B
A
B
So
let
me
catch
up
on
chat
here.
So
waleed
we
had
issues
with
upgrading
vcf
the
vmware
cloud
foundation
as
the
heart
via
virtual
hardware
version
for
the
vms
was
version
15..
Well,
the
qa
environment
was
14.
yeah.
So
I
think
it
was.
I
don't
remember
precisely
when
it
was
we
did
recently.
Maybe
it
was
with
4.9,
but
we
did
recently
change
the
default
version
of
virtual
hardware
from
13
to
15..
B
The
reason
for
that
is
because,
with
csi
we
have
to
use
at
least
virtual
hardware
version,
15.
and
csi
will
become
mandatory
in
the
future.
Remember
the
entry
drivers
are
being
for
lack
of
a
better
term
ejected
from
kubernetes
and
csi
requires
that
hardware
version
15
or
later,
along
with
the
static
uid,
which
that
was
already
set
so
yeah.
B
B
Continuing
your
comment
there,
while
leads
management,
does
not
want
us
to
update
as
frequently
what
we
say
to
traditional
management
regarding
update
policy,
and
why
would
you
advise
frequent
updates
now
that
releases
are
three
a
year
and
not
talking
minor
ones
yeah?
So
this
is
one
of
those.
It's
a
it's
an
eternal
and
constant
debate.
I
say
that
knowing
that
and
and
seeing
internally
requests
for
you
know
from
customers
of
hey,
we
know
that
openshift
3011
support
ends.
B
B
So,
even
if
you're,
you
know
and
and
completely
unsupported,
you
know,
or
out
of
it,
doesn't
get
any
feature
capability
updates.
Anything
like
that.
You
know
so
it's
it's
basically,
security
updates
that
are
happening
so
that
to
me
that's
one
of
those
like
we
know
that
customers
are
going
to
ask
for
that.
You
know.
We
know
that
customers
want
to
slow
down
the
pace
of
of
updates,
which
is
one
of
the
reasons
why
I
think
kubernetes
went
to
the
three
instead
of
four
annual
releases.
B
So
my
response
to
that
is,
it
is
a
you
have
to
weigh
risk
versus
benefit
so
going
within
minor
versions,
so
minor
version
being
the
second
number
so
4.6
to
4.7
to
4.8,
I
think,
is
largely
dependent
on
because
you
have
an
18-month
window
to
do
it
now.
You
know
how
comfortable
or
when
is
the
best
opportun
opportunity
to
go
between
those
so
4.8
to
4.10
right
type
of
thing.
B
B
So
update
is
what
I
usually
refer
to
as
a
z,
stream
update
and
upgrade
is
more
like
a
minor
version
update,
so
zstream,
4.8
or
4.9.8
to
4.9.12.
upgrade
would
be
4.8.
whatever
to
4.9
dot
whatever
so
from
a
process
procedure
standpoint
it's
effectively
the
same.
So
let's
take
a
step
back
or
maybe
a
step
down
in
the
process.
All
it's
always
triggered
by
a
cluster
version
operator
update.
So
the
cvo
has
a
huge,
manifest
or
actually
it's
a
list
of
manifests.
B
That
is
all
of
the
yaml
objects,
representing
all
of
the
things
that
make
up
openshift,
and
that
includes
you
know
things
like
deploy
olm
deploy.
You
know,
olm
now
deploy
this
operator
operator
and
now
deploy
this
operand
and
that
operand
could
be
dns,
for
example,
so
the
cvo
is
kind
of
that
source
of
authority.
B
Some
z
stream
updates
or
even
major
updates
upgrades.
Sorry
a
why
release
4.8
to
4.9
upgrade
that
can
be
the
some
things
will
stay
the
same
right.
So,
for
example,
maybe
it's
I'm
going
to
pick
on.
Logging
logging
is
one
of
the
decoupled
features,
so
the
version
may
stay
the
same.
If
you
go
from
4.8
to
4.9,
even
though
other
components
are
being
updated,
but
it
can
also
be
larger
than
you
would
expect.
B
So,
for
example,
I
think
it
was
4.7
one
of
the
4.7
z
streams,
core
os
rebased
from
like
rel
4
8.3
to
8.4,
or
something
like
that
might
have
been
4.6
and
8.28.3.
I
I
don't
remember
precisely,
but
you
know
it
was
in
a
z
stream
that
we
rebased
coreos.
You
know
from
8.3
to
8.4.
You
know
some
people
would
consider
that
to
be
a
pretty
significant
update.
I
tend
to
think
of
coreos
as
an
appliance.
So
theoretically
it
shouldn't
matter
but
yeah,
so
the
scope
can
vary.
B
B
Significant
api
changes,
some
of
the
most
significant
and
recent
memory,
so
yeah
that
that
is
usually
you
know.
In
my
perspective,
my
anecdotal
experience.
It's
the
kubernetes
versions
that
trigger
the
the
4.8
4.9
4.10
4.11
updates.
I
don't
think
that
was
always
true.
I
think
there
was
one
of
the
3.
something
releases
where
that
wasn't
true,
because
if
the
the
3.x
releases
were
a
little
less
in
sync,
with
the
kubernetes
releases
from
what
I
remember,
but
I
may
be
misremembering
just
checking
catching
up
on
chat
here.
B
Thank
you,
stephanie,
for
linking
the
ultimate
guide
to
updates
we'll
leads
does
not
mention
incentives.
Clearly,
like
lcd
data,
defrag
yeah.
Unfortunately,
the
best
way
to
find
and
understand
those
those
type
level
of
changes
is
to
review
the
release,
notes
yeah,
it's
tedious
and
kind
of
a
pain.
You
know,
I
guess,
if
you're
a
better,
you
know,
reading
learner
versus
listening
learner.
B
I
I
would
say
that
that's
probably
only
really
important
to
a
pretty
small
number
of
folks
a
pretty
small
number
of
clusters,
because
it
only
has
a
large
effect
or
you
were
only
impacted
if
you
had
very
large
clusters
to
the
point
where
the
normal
defrag
process
just
wasn't
able
to
catch
up,
keep
up.
So
previously
the
defrag
happened.
Every
time
you
did
a
reboot
now
it
happens
on
a
schedule,
regardless
of
whether
reboot
happens.
B
So
you
know
I
I
don't
know
whether
you
know
that
never
impacted
me,
but
I
do
you
know
I.
I
know
that
others
were
impacted,
so
you
kind
of
have
to
gauge
based
off
of
that.
That's
why
we
use
vsan
requires
a
higher
vm
version.
Yeah
vsan's,
it's
a
good
solution.
I
was
just
evaluating
deploying
it
in
our
lab
the
other
day.
I
didn't
know
that
it
had
a
vm
version
requirement,
though
it's
been
a
long
time
since
I
used
vsan.
B
So
does
the
cluster
upgrade
time
vary
per
number
of
nodes?
Yes,
so
not
as
much
as
before,
and
I
don't
remember
what
version
it
happened
in.
We
talked
about
it
here
on
the
stream.
So
it
used
to
be
that
every
change
was
sequential.
We
would
affect
one
node
at
a
time,
so
they
did
in
one
of
the
more
recent
releases.
B
B
I'm
going
off
the
top
of
my
head,
so
yeah,
so
in
the
mcp,
the
machine
config
pool
you
have
a
setting
called
max
unavailable
and
I'm
going
to
link
is
so.
This
link
is
to
the
api
documentation,
so
by
default
it
is
set
to
one.
So
what
that
means
is
that
unless
it's
configured
otherwise
with
each
machine,
config
pool
it
will
only
affect,
or
only
one
node
at
a
time
can
be
unavailable
or
or
not
available
for
for
workload.
B
So,
depending
on
your
applications,
depending
on
a
number
of
other
things,
you
can
maybe
increase
that
you
know.
Maybe
you
can
go
up
to
you,
know
two
or
five
or
ten
nodes
inside
of
that
machine,
config
pool
that
can
be
affected
at
any
time.
You
can
also
use
a
percentage
on
that,
so
you
know
use
10
percent
or
20
or
whatever
that
happens
to
be
so
this
does
so,
even
if
you
set
that.
B
B
I
was
unaware
of
the
schedule
one
today
well
he'd
happy
to
have
you
join,
I
feel
like
it's
been
a
while
since,
since
I
saw
you
on
here,
so
I'm
very
happy
to
see
you
again
yep,
so
you
decide
how
many
nodes
can
be
down
at
the
time
at
the
same
time.
Think
you
are
hope,
nine
again,
either
a
static
number
or
a
percentage
based
on
how
how
large
that
pool
is.
B
B
B
How
did
the
oh
jp
did?
How
did
the
southern
maryland
stuff
ham
turn
out?
I
lobbied
my
wife
endlessly
to
try
and
get
it
done.
She
was
not
a
fan.
She
was
not
on
board.
I
even
tried
to
get
her
parents
on
board
my
my
in-laws.
It
unfortunately
did
not
happen
so
now,
I'm
I'm
trying
to
see
if
I
can
do
it
on
a
smaller
scale
for
easter,
we
did
end
up
going
with
a
honey
ham
so
that
we
got
from
costco
or
something
so.
A
B
B
I
think
that
will
I
think
that
will
work
our
hope,
9.
so
effectively
you
can.
What
our
hope
9
is
is
saying
is
with
any
openshift
release,
regardless
of
whether
it's
one
of
the
even
numbered
eos
versions
or
not.
You
can
basically
pause,
updates
or
pause
changes
to
a
machine,
config
pool,
so
you
could
manually
pause
that
machine
config,
pool,
update
the
control
plane
and
then
resume
those
updates.
B
So
I
think
that
will
work.
I've
honestly
never
tried
that
and
the
result
would
be
they
can.
When
that
machine,
config
pool
comes
out
of
its
frozen
status,
it
would
say:
oh
I'm,
I'm
on
4.7
the
cluster's
on
4.9.
I
just
need
to
apply
one
one
set
of
updates,
so
that
is
functionality
that
is
fully
supported
with
4.8
and
later
with
the
eos
releases.
B
So
starting
with
4.8,
you
can
go
to
4.10
with
that
leap
process.
That's
what
I'm
going
to
call
it
or
accelerated
update
process,
but
that
only
applies
for
compute
nodes.
The
control
plane
nodes
would
still
need
to
go
sequentially,
4.8,
4.9
4.10,
and
then
you
would
be
able
to
do
the
same
thing:
4.10
to
4.12
12
to
14.
B
B
B
I've
got
some
notes
here.
I
kind
of
the
three
different
ways
to
update
a
cluster
to
trigger
an
update
so
using
the
web
console
using
the
cli
and
using
get
ops.
So
I'll
include
that
in
the
blog
post
that
way,
you
can
see
an
example
of
how
to
do
each
one
of
those
git
ops
is
usually
the
one
that
most
folks
are
the
least
familiar
with,
but
yeah
you
can
actually
do
a.
If
you
do
oc
git
cluster
version.
B
You
can
see
the
cluster
object
there
and
effectively
you're,
just
updating
that
whether
you're
changing
the
channel
so
say
go
from
stable4.8
to
stable
4.9
or
the
specific
release
that
you
want
to
use.
You
can
update
that
object
and
that
will
trigger
a
cluster
update
and
you
can
do
that
with
get
ops
as
well
as
the
cli,
so
yeah
kind
of
jumping
back
just
slightly
other
basic
troubleshooting
steps,
johnny
anything
that
came
to
mind
for
you.
There.
A
The
big
one
for
me
is
check
the
logs.
You
know
I
mean,
like
you
know,
if
you're
and
if
you
have
the
ability
to
go,
look
at
the
console
make
sure
it's
not
stuck
in
a
reboot
or
something
like
that.
Make
sure
that,
like
there's
something
you
know
something
dumb,
not
happening,
you
know
and
if
you
can
go
and
like
force
the
reboot
and
kind
of
get
it
to
kick
back
off
that
that
might
be
worth
doing.
A
B
Yeah
I'll
say
that
in
my
in
my
lab,
I
I
have
forcefully
triggered
a
reboot,
I'm
tired
of
way
down
on
you,
I'm
just
going
to
reboot,
because
you
can
look
and
see.
If
so,
if
you're
waiting
on
node
reboots
to
happen,
you
know
that's
usually
the
longest
part,
because
it
will
go
into
a
cordon
and
drain
of
each
node.
That's
another
thing
that
you
can
use
to
kind
of
speed
up.
That
process
is
usually
the
longest
part,
particularly
with
virtual
machines.
The
longest
part
of
that
is
just
waiting
for
the
workload
to
drain.
B
So
if
you
know
that
your
application
is
tolerant
of
it
knock
on
wood,
you
know
it
didn't
yeah
coarsely
reboot
it
and
that
I
do
that
in
my
lab.
You
know
I
get
tired
of
waiting
for
things
to
drain
and
do
it.
You
know
in
production,
maybe
wait
for
it
to
drain
or
talk
to
the
developers.
Talk
to
the
app
team
and
say:
hey
can.
Can
you
do
this?
You
know
figure
out
what's
happening
here,
why
this
is
taking
so
long
and
fix
your
application
type
of
thing,
yeah,
it's
and
vms.
B
You
know
vm's
reboot.
So
fast
that
that's
usually
a
pretty
minor
part
of
the
whole
thing:
oh
yeah
yeah,
so
you
can,
if
you're
waiting
on
that.
So
the
way
that
you
see
that
is
look
for
the
node
that
has
been
you
know
coordinated.
It's
marked
as
non-schedulable,
but
hasn't
rebooted
yet,
and
you
can
basically
go
and
look
specifically
at
the
pods.
So
I
usually
just
do
a
simple
grep.
A
B
A
B
B
So
basically,
what
that
means
is
historically
if
any
deployment
type
any
feature
function.
Capability
on
any
platform
is
qualifies
as
a
an
upgrade
blocking
or
as
an
upgrade
blocker.
We
block
that
upgrade
for
everyone.
So
maybe
it's
you
know
something
that
is
specific
to
you
know
only
vsphere
deployments.
Well,
if
you're
deployed
to
azure,
aws
or
anywhere
else,
you
know
you
we're
still
blocked.
B
So
what
they're
working
on
is
effectively
one
making
that
more
granular
so
that
you
can
see
you
know,
oh
I'm
not
using
vsphere.
I
can
go
ahead
and
update
my
cluster
and
I
think
I
I
think
don't
hold
me
to
it
that
you
can
still
or
even
after
that
you'll
still
be
able
to
say.
Oh,
I
see
it's
vsphere,
but
it's
a
vsphere
thing
that
doesn't
affect
me.
So
I
still
want
to.
You
know
trigger
that
update.
You
know
it's
something
that
only
affects
say:
vsphere
6.7,
but
I'm
on
7.0,
so
I'm
okay.
B
A
B
B
B
So
I
know
we've
shown
this
a
number
of
times.
I
always
like
to
remind
folks
of
this
just
as
a
it's
a
really
handy
tool
to
have
available,
so
it
shows
you
basically
you
go
in
and
say
I'm
using
this
version,
and
I
want
to
go
to
this
version
and
it
will
show
you
the
exact
path
that
you
take
and
it
will
even
provide
the
commands
that
you
can
use
to
do
that
upgrade.
B
So
I
always
like
to
remind
people
that
it's
out
there,
because
you
know
it
can
be
confusing
right
to
I'm
on
4.7
dot,
something
today.
How
do
I
get
to
4.9
dot
whatever?
The
latest
is,
however,
do
note
that
sometimes
you'll
see
some
weird
scenarios,
so,
for
example,
if
you
were
to
look
at
it
might
have,
finally,
the
the
upgrade
edge
might
finally
be
there.
But
if
you
go
to
like
so
are
you
on
stable,
4.8,
yep
so
switch
over
to
the
update
path
view?
B
24.,
okay,
so
sometimes
what
happens
and
we
can't.
Strangely,
you
must
be
on
fedora,
it's
not
showing
the
drop
downs
in
the
share.
Oh
overall
yeah.
I
have
that
issue
when
I
do
screen
recordings
on
fedora
anyways.
So
sometimes
what
happens
is
you
will
end
up
with
a
a
z
stream
for
an
earlier
version
that
is
from
a
core
os
perspective,
ahead
of
the
z
stream
from
a
later
y
release?
B
B
I'm
just
making
that
up.
I
don't
know
what
it
actually
was.
So
you
know
when
you
looked,
it
would
say
if
you're
currently
on
4.7
at
40,
you
have
no
upgrade
path,
and
essentially
the
solution
to
that
is
to
just
wait.
If
you
want
to
stick
to
stable
channels,
you
know
and
wait
wait
for
say
it
was
4.8.24
to
match
or
be
ahead,
wait
for
that
one
to
get
promoted,
and
then
you
would
be
able
to
do
that
update
or
if
you
are
comfortable.
You
can
use
the
fast
channel.
B
So
we've
talked
about
again
talked
about
it
before
the
fast
channel
is
fully
supported.
When
a
release
is
in
the
fast
channel,
it
is
generally
available.
It
is
fully
supported.
You
can
pick
up
the
phone
you
can
call
support.
You
can
absolutely
get
help
with
that.
So,
if
you-
and
if
you
go
to
fast
so
let's
say
the
scenarios
just
describing
is
true-
you
went
to
4.7.40
for
whatever
reason.
Oh
no,
I
need
to
go
to
4.8.24
right
now.
It's
only
in
fast.
That
is
a
fully
supported,
ga
release.
B
You
can
go
there
in
a
week
or
two
or
however
long
win
4.8.24
then
moves
from
fast
into
stable.
You
can
then
switch
your
channel
back
to
stable
and
then
you
can
stick
with
the
stable
releases
from
there
on
out
and
there's
that
doesn't
change,
support
status
that
doesn't
invalidate
your
support
or
anything
like
that.
B
Candidate
releases
are
unsupported,
but
you
can-
and
we
had
this
question-
come
up
not
too
long
ago
of
my
customer
didn't
realize
it
they
were,
they
had
selected
the
candidate
channel
and
then
they
updated
to
the
very
latest
release,
and
you
know
what
did
they
do
now
and
it
was
one
of
those
well,
hopefully
that
release
gets
promoted
to
fast
and
then
they
can.
You
know
then
they'll
be
supported,
because
it's
at
that
point
of
ga
release.
If
not
it's
so,
let's
say
it
was.
B
You
know,
I'm
gonna
use
fictitious
numbers,
so
they
were
on
candidate,
they
went
to
4.9.78
and
that
one
never
made
it
into
fast.
It
never
got
promoted
to
ga,
but
4.9.79
got
released
so
in
candidate
channel
update
to
4.99
and
then
switch
to
fast
channel
which
has
with
4.8.79
and
then
it
would
be.
Then
you
would
stick
with
it
type
of
thing.
So
for
production
environment
we
must
be
at
n
minus
one
or
minus
two
which
do
you
think
is
always
stable.
B
B
B
Usually
the
biggest
concern
is:
what
are
the
changes
that
happened
going
from
one
release
to
the
next,
the
longer
that
a
release
has
been
out
there,
the
more
and
the
better
awareness
there
is
around
what
those
things
are.
This
is
a
big
thing
with
the
4.8
to
4.9
release.
It's
not
that
4.9
was
unstable.
There's
been
no.
As
far
as
I
know,
no
stability
issues,
you
know
with
4.9.
B
B
The
each
each
release
is
intended
to
be
equally
stable,
as
as
all
of
the
others,
so
it
really
comes
down
to
certain
things.
That
being
said
most
of
the
time.
So
as
far
as
I
know,
security
updates
and
all
that
other
stuff
are
always
back
ported
but
sometimes
feature
you
know
fixes
you
have
to
go
forward
to
get
those,
so
it
may
be,
like
you
know,
hey
I'm
using
I'm.
B
A
No,
I
I
think
that
yeah,
you,
you
nailed
it
like.
I,
you
know
it's.
It
comes
down
to
just
what
you
need,
and
you
know
like,
especially
on
the
y
streams.
You
know
if,
if
there's
a
future
coming
out
that
you
need
obviously
upgrade
to
it.
If
there's
something
breaking
like
an
api
extension,
that's
being
deprecated,
obviously
don't
upgrade.
You
know
it,
but
it's
it's!
A
It's
good
to
read
the
release,
notes
it's
good
to
stay
up
to
date
with
like
what's
coming
out
in
the
cluster,
because
absolutely
with
every
release,
we're
going
with
the
new
version
of
kubernetes
as
well.
So
you
know
like
they're,
going
to
be
deprecating
things
upstream
and
we're
going
to
have
to
do
the
same.
So
it's
something
that
you
just
you
know
we
just
have
to
keep
track
of.
B
Well,
I
don't
know
if
you
heard
that,
but
that
was
my
doorbell,
which
means
that
my
my
timer
has
expired.
So
thank
you,
everybody
for
joining
us
this
week.
We
really
do
appreciate
you
attending.
I
know
it's
been
a
little
while,
since
we
had
a
stream,
so
thank
you
very
much
to
our
audience,
really
love
your
interactivity
today
really
love
the
questions.
Please
don't
hesitate
to
follow
up
stephanie.
Thank
you
for
flashing,
our
contact
information.
B
You
can
always
reach
me
via
email
at
any
time,
andrew.sullivan
redhat.com
and
then
keep
an
eye
out
for
those
post
stream
blogs.
They
usually
come
out
the
same
week,
sometimes
the
week
after,
but
we're
getting
all
of
those
taken
care
of.
So
thank
you
again,
johnny
really
good
to
see
you
stephanie.
Thank
you
for
all
your
help.
On
the
on
the
back
end
and
have
a
great
and
safe
week,
everybody.