►
Description
Are your Operators ready for the release of Kubernetes 1.22? It's a good idea to double-check because several APIs that have previously been marked as deprecated will be removed and are no longer available in 1.22. To help us cover this change Rob Szumski, Senior Manager, Openshift Product Management, joins us to discuss the details and ensure we avoid removed API versions. We'll also look at the steps needed to upgrade to newer APIs because Operators projects using these APIs versions will not work on Kubernetes 1.22 or any cluster vendor using Kubernetes version 1.22, such as OpenShift 4.9+.
About Ask an OpenShift Admin:
Do you have questions? We want to answer them! Every Wednesday at 11am ET, hosts Andrew Sullivan and Chris Short sit down to answer your questions about Red Hat OpenShift.
Follow us:
Andrew Sullivan https://twitter.com/practicalandrew
Chris Short https://twitter.com/chrisshort
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
A
A
A
Good
morning,
good
afternoon
good
evening
and
welcome
to
another
ask
an
open
shift
admin
I
am
chris
short
host
of
the
most
of
red
hat
live
streaming.
I
am
joined
by
the
one
and
only
andrew
sullivan,
as
well
as
some
other
red
hatters
who,
yes,
sir,
may
or
may
not
be
visible
right
now,
so
feel
free
to
ask
us
questions
about
anything,
openshift
related
right
or
red
hat
related.
For
that
matter.
We
can
get
you
the
right
answers
feel
free
to
email.
Me
short
at
redhat.com.
A
B
B
All
one
word
and
chris
is
at
chris
short
on
twitter
and,
of
course,
you
can
reach
out
via
email,
although
we
usually
don't
respond
to
email
while
we're
on
stream,
because
yeah
too
much
too
much
multitasking
is
hard,
so
yeah
feel
free,
regardless
of
which
platform
you're
watching
us
on
whether
it's
one
of
the
youtube
channels
or
twitch.
If
you
chat
with
us,
we
it
gets
rebroadcast
across
all
of
them
and
we'll
see
it
and
we'll
do
our
best
to
respond.
B
So
today,
as
chris
mentioned
we're
here
to
talk
about
kubernetes
api
deprecations,
thank
you
for
posting
that
link
chris.
You
got
it
no
problem,
so
this
is
an
interesting
one
and
we've
talked
about
it
in
bits
and
pieces
over
the
last.
What
month
or
so,
we
we've
brought
this
up
and
talked
about
a
couple
of
different
aspects.
I
think
the
first
time
I
mentioned
this
was
in
the
what's
new
in
4.8,
when
we
talked
about
the
api
request,
counts.
C
B
D
Everyone
happy
to
be
here:
I'm
rob
sumski,
I'm
on
the
product
management
team
for
openshift.
I've
been
in
the
cube
space
for
quite
a
long
time.
I
deal
with
a
lot
of
things
being
built
on
top
of
kube
apis
and
so
api
deprecation
is
part
of
that,
but
talked
to
a
bunch
of
folks
in
like
the
operator
community
and
other
folks
building
on
top
of
the
openshift
platform.
So
yeah
happy
to
be
here
thanks.
B
C
B
D
A
E
C
A
E
B
B
B
So
I
think-
and
chris
maybe
you
know,
I
don't
know
how
many
streams
are
happening
next
week,
but
next
week
is
ansible
fest
and
I
I
have
the
privilege
of
being
one
of
the
subject
matter
experts.
So,
if
you're
registered
for
ansible
fest,
if
you
go
to
the
connect
tab,
there
is
a
brain
date
thing
and
you
can
go
and
register
for
brain
date.
I'm
going
to
call
them
appointments
not
to
make
it
awkward.
Yeah.
B
B
Then
openstack
summit,
maybe
one
of
the
events
in
austin,
was
when
I
first
heard
about
it,
but
so
yeah,
if
you're
attending
ansible
fest
by
all
means,
go
and
check
that
out,
there's
more
than
just
me,
of
course,
there's
a
lot
of
folks
right.
So
yeah,
not
not
just
me,
you
get
enough
of
me.
Maybe
maybe
talk
to
somebody
else.
Yeah.
A
B
Indeed-
and
I
think
all
of
that
is
on
the
streaming
calendar
as
well
and
should
be
yes,
I'm
going
to
trust
that
you've
posted
a
link
and
to
all
that
stuff.
If
folks,
don't
already
know
how
to
get
there,
so
the
next
one
that
I
want
to
talk
about
is
another
one
that
we've
been
talking
about
for
quite
a
while,
which
is
the
stable
upgrade
edge
for
openshift
4.7
to
4.8.
B
B
Fixed
a
virtual
hardware
yeah,
so
so
it's
funny
right.
It
felt
like,
and
I
don't
know
why
this
one
felt
like
it
took
longer
to
go
from.
You
know:
ga
release,
hey.
You
can
release
to
there's
a
stable
upgrade
edge,
but
engineering
actually
sent
out
a
really
interesting
email
where
they
were
highlighting
that
with
this
new
process,
which
we've
been
using
since
4.6,
this
upgrade
edge
was
right
in
line
with
the
others.
B
So
the
upgrade
promotion
happened
55
days
after
ga
and
included
over
120
bugs,
since
that
ga
right,
including
I
think
five
of
those
were
upgrade
blockers,
so
4.6-
was
promoted
to
stable
after
58
days
and
4.7
was
promoted
to
stable
after
50
days.
So
this
is
right
in
line
like
it
seemed
like
a
long
time,
at
least
to
me
I
felt
like
I
was
constantly
you
know.
Hearing
about
and
and
people
are
you
know
asking
regularly
about
when
it'll
be
available,
but
really
it's
the
system
is
working.
B
It's
working
the
way
we
want
it
to
and
the
way
that
we
intend
it
to
so
that
you
know
when
you
use
stable,
which
is
something
like
90
percent
of
clusters
use
the
stable
upgrade
channel.
When
you
use
stable,
you
can
be
confident
that
you're
not
going
to
encounter
any
any
edge
cases
or
anything
like
that.
D
D
You
know
something
needed
to
be
blocked
there,
and
so
we
did
it
to
protect
you
so
yeah,
but
so
trust
your
cluster
console
or
the
any
of
the
tools
we
have
to
visualize
that
graph,
because
when
they
say
it's,
okay,
it's
okay,
but
then
yeah.
We
need
folks
to
mix
in
some
of
their
development
environments
their
test
environments.
If
you've
got
like
a
a
scale,
testing
kind
of
environment,
throw
your
cluster
on
there
and
get
us
a
little
bit
of
feedback
on
that.
It
really
really
helps.
B
B
B
So
if
you
look
at
this
guy,
you
can
see
that
openshift
4
is
not
affected.
So
essentially,
congratulations.
We
don't
have
to
do
anything,
and
that
is
a
result
of.
As
you
can
see
here,
we
don't
support
logging
levels
higher
than
eight
and
the
vulnerability
only
affects
when
you
have
logging
levels
set
to
10
or
higher.
B
So
this
one
and
let
me
check
to
make
sure
that
we're
yeah
you're
posting
the
links,
yeah
yeah.
Thank
you.
So
this
one
is,
or
it
does
affect
openshift4
you'll
notice
that
we
don't
have
an
errata
or
a
release
date
here.
So
this
is
being
worked
in
the
background.
Once
that
becomes
available,
we
will
make
sure
to
make
it.
You
know
out
through
the
standard,
upgrade
update
mechanism
for
all
affected
versions.
One
thing
that
I
would
highly
recommend
is
somewhere
on
this
page.
There
is
a
follow
button.
B
B
You
can
also
go
over
to
the
bugzilla,
that's
associated
with
it
and
you
can
follow
the
bz
and
that
will
announce
that
will
let
you
know
when
there
happens
to
be
any
updates
or
changes
inside
of
there.
So
definitely
this
one
is
a
pretty
serious.
One.
Definitely
keep
an
eye
on
that
one
and
make
sure
that
you
are
updating
your
clusters
as
appropriate.
B
D
B
B
And
you
know
that
in
well
that,
in
in
combination
with
things
like
you
know
no
root,
we
we
force
no
root
containers.
You
know
we,
you
know
sccs
and
all
the
other
security
mechanisms
that
we
have
where's,
that
security
e-book.
I
always
like
to
post
that
one
oh
yeah,
I
should
have
had
that
link
candy.
I
should
have
that
like
as
a
short
command.
A
B
So,
while
you're
digging
on
that,
the
last
thing
that
I'll
touch
on
here
is
so
last
week
we
had
christian
on
christian,
talked
about
windows
hosts,
bring
your
own
windows
nodes
to
openshift
and
he
alluded
to.
It
would
be
released
as
generally
available,
soon
and
sure
enough
monday.
It
was
released
as
generally
available.
So
if
you
have
any
need
for
windows
nodes-
and
you
did
not-
or
you
don't
are
not
using
one
of
those
previous
platforms-
specifically
on-prem,
it
was
limited
to
vsphere
ipi.
D
D
A
B
B
I
don't
think
you
can
have
like.
You
can't
have
two
clusters
that
use
the
same
cluster
name
or
the.
If
you
and
it
sounds
like
you're
saying
here
like,
can
I
change
the
route
to
use
oauth.openshift.baseddomain
or
api
dash
in
base
domain?
I
don't
think
you
can
do
that
with
two
clusters,
simply
because
it
needs
some
way
to.
A
D
A
B
D
B
For
for
aws,
it
actually
works
and
is
supported
on
any
deployment
type
but
effectively.
What
this
does
is
when
you
create
a
route
it
uses
whatever
this
apps
domain
is
for
all
of
those
routes
and
that
domain
endpoint,
so
this
apps.acme.io
that
dns
endpoint
can
be
located
on
an
external
load
balancer
or
wherever
it
happens
to
be
so
that
could
be
one
option
where
that
would
get
weird
is
that
external
load,
balancer
would
still
need
to
understand,
like
app1.ac.apps.acme.io
needs
to
go
to
cluster
1.
B
Now
I'm
wondering
if
it
isn't
to
use
a
ingress
controller
from
one
of
our
partners,
so
think
like
an
f5
or
a
citrix
adc,
where
it's
able
to
reach
out
and
control
right,
the
the
operator
and
the
integration
is
able
to
reach
out
and
control
that
external
device.
That
may
be
the
most
robust
option
that
you
have.
A
B
On
chat
drop
that
link
real,
quick,
yeah
I'll,
put
the
link
to
this
apps
domain
inside
inside
there,
the
apps
domain.
Usually
this
comes
up
in
the
context
of
with
on-prem
ipi
when
folks
want
to
use
or
want
to
move
the
apps
star.apps
endpoint
off
of
the
virtual
ip,
the
vip
that's
managed
by
the
cluster
and
onto
an
external
load
balancer.
This
is
one
of
the
ways
that
you
can
do
that
awesome
without
yeah,
without
changing
significant
things.
Inside
of
the
cluster.
B
All
right,
I
will
stop
my
sharing
again
and
I
will
I'm
that's
all
I've
got.
I
think
I
don't
see
anything
else
in
my
notes
here
so
yeah.
Let's
talk
about
api
deprecations,
so
so
rob
you
know
we
we
chatted
about
this
beforehand.
I
think
you've
got
some
slides.
That
kind
of
talk
at
a
high
level
of
you
know
why
this
is
important,
why
it's
and
why
it
matters
to
us
and
what
it
affects.
B
So
I
definitely
want
to
make
sure
that
we
address
that
because
I
will
admit
you
know
this
is
the
the
ask
an
admin.
You
know
live
stream
and
we're
talking
about
apis
which
not
everybody.
You
know
some
people
are
like
what
that's
you
know
apis
or
developer
things.
Well,
no.
This
is
important
for
all
of
us
and
that's
why
we're
talking
about
it.
D
Yeah
so,
as
you
mentioned,
I
do
have
a
few
slides.
I
promise
they're
mostly
just
to
show
you
some
commands
that
are
hard
to
describe
verbally
and
some
screenshots,
so
we're
mostly
just
going
to
be
talking,
so
I
hope
I
didn't
scare
you
away
already
so
yeah,
let's
jump
into
it.
So
basically
in
kube
they
have
a
api,
deprecation
policy
and
they're
actually
very
generous
about
this.
D
So
let's
talk
about
a
few
of
the
popular
ones
that
are
getting
deprecated
and
what
deprecated
means
is
when
you
submit
objects
in
the
old
format,
the
deprecated
format,
they
will
either
just
straight
up,
not
work
and
your
cli
or
whatever
tool
you're
using
will
just
say.
I
don't
know
what
that
is,
or
in
some
cases
we
can
actually
do
an
upgrade
to
the
actual
like
transform
it
to
the
actual
api,
the
real
one
like
if
it
went
from
beta
to
stable
right.
So
sometimes
that
can
happen.
A
A
D
You
need
to
update
that
or
it's
not
gonna
work,
so
there's
that
side
of
it-
and
so
we've
got
a
very
rich
operator,
ecosystem
work
with
a
ton
of
partners,
building
some
really
cool
stuff,
running
databases,
machine
learning,
workloads
all
that
stuff
on
top
of
kube,
and
so,
if
under
the
hood
they're
using
one
of
these,
they
need
to
update
to
not
use
it.
And
again
this
should
have
happened.
D
You
know
over
many
many
months
and
releases
because
this
has
been
planned
for
a
while
the
main
one
that
you
need
to
care
about,
especially
in
operator
land,
is
the
custom
resource
definition
which
has
been
a
kind
of
v1
or
a
stable
api
for
a
while,
now
and
so
they're.
Finally,
removing
the
beta
version
of
that
and
chris,
as
you
mentioned,
so
the
spec
of
this
thing
did
not
change.
We
basically
said
hey.
The
beta
1
is
good,
let's
roll
it
on
up
and
make
it
official.
D
So
all
you
need
to
do
is
just
change
like
basically
get
rid
of
v1
beta1
on
that
some
of
the
other
ones
are
a
little
bit
more
invasive,
because
some
of
the
the
spec
actually
did
change
like
either
field
name
went
from
not
required
to
required
or
change
names,
and
that
kind
of
thing,
so
some
of
them
are
a
little
bit
more.
I
listed
only
four
of
them
here
there's.
D
To
put
mostly,
we
manage
the
tls
on
these
so
that
you
can
do
expose
some
metrics
and
other
things,
and
so
that's
where
those
get
a
little
bit
more
widely
used
in
our
tools
and
then
certificate
signing
requests
for
folks
that
have
built
automation
around
some
of
the
cert
management
in
cube.
You
know
openshift
kind
of
does
this
for
you
by
default
and
you
don't
really
have
to
mess
with
it
too
much.
B
D
So
I
think
the
the
first
lesson
is:
yes,
you
do
because
of
situations
like
this,
but
for
the
most
part,
that's
just
an
indicator
of
like
if
I'm
going
to
be
building
something
against
this.
How
how,
on
top
of
it
do
I
have
to
be,
if
you're,
building
against,
like
an
alpha
api,
it
could
mean
that
that
never
progresses
and
like
you're
building
on
something
that
might
just
immediately
be
removed
or,
like
everyone
will
stop
working
on
it
and
will
pursue
do
a
different.
So
I
think
there's
like
the
maturity
aspect
of
that.
D
D
So
you
as
an
end
user.
It's
pretty
easy
if
you've
got
like
a
get
ops,
repo
and
you've
just
got
your
yamls
in
there
to
just
do
a
regex
or
whatever
and
change
stuff
and
da
da
da
you're
good,
where
it
gets
harder
is
us
on
providing
the
platform
side.
We
we
do
a
bunch
of
upgrades
and
manage
you,
know,
deprecating
and
enabling
these
new
apis
on
your
behalf.
D
So
if
you're,
just
using
openshift
you're
good
to
go
now,
if
you're
a
content
producer-
and
you
maybe
say
you
support
a
hundred
or
a
thousand
customers
that
are
using
an
alpha
api,
oh
you
gotta
have
a
plan
there
for
how
to
get
that
from
alpha
to
beta.
You
know
in
an
automated
fashion,
unless
you
want
to
like
really
just
disrupt
your
customers.
So
that's
where
you.
B
B
B
D
It
kind
of
depends:
we
have
a
few
situations
where
changing
around
some
of
the
apis
is
really
invasive,
and
so
we
have
actually,
we
do
fully
support
an
alpha
api,
but
when
we
get
those
from
upstream,
we
typically
would
follow
a
typical
alpha,
beta,
stable
and
not
support
the
alphas.
We
actually
usually
don't
enable
a
lot
of
the
upstream
apis
until
they
hit
beta,
so
you
usually
won't
find
one
of
those
in
an
openshift
cluster
unless
you've
specifically
toggled
on,
like
a
feature
flag
or
something
like
that,
got
it.
D
Good,
so
that
was
kind
of
the
overview.
I've
got
a
few
kind
of
like
commands
and
screenshots.
So
we
talked
about
content
producers,
but
there's
also
just
admins
that
are
running
clusters,
and
you
probably
just
want
to
check
to
see
hey
my
users
on
this
cluster.
What
have
they
installed?
What
are
they
actually
doing?
D
D
You
can
also
check
for
any
of
this
and
more
with
our
operator,
sdk
cli.
You
can
validate
what
we
call
bundle,
which
is
a
bunch
of
the
metadata
about
the
apis.
You
use
and
say
hey
validate
this
against
cube122
and
it
will
go.
You
know,
give
you
some
output
for
things
that
you're
either
using
or
not
using,
and
what
you
need
to
do
there.
D
We've
got
a
bunch
of
cooler
tools
for
live
cluster
usage,
so
this
is
think
operators.
It's
more
about
clustered
content
right.
It's,
like
other
part
parties
producing
stuff
that
you're,
probably
just
using,
but
what
about
live
stuff.
I've
got
somebody!
That's
got
some
jenkins
job.
That's
you
know
using
the
cube
api
or
something
like
that.
So
in
openshift
we
have
two
different
things
you
can
do.
D
D
Yeah
trying
to
make
this
really
easy
for
like
this
to
kind
of
be
self-service
too,
so
you
know
you
as
an
admin
made
people
say
hey.
This
is
my.
I
just
provide
like
a
multi-tenant
cluster.
This
is
my
tenant's
problems.
Okay,
great
well
they've
got
a
self-service
api
to
go
figure
out
what's
happening,
and
you
can
also
use
that
same
api
to,
like
you
know,
really
get
after
somebody
if
you've,
given
them
a
lot
of
time
to
migrate.
D
B
B
D
Yeah
great
question:
so
yes
in
openshift,
we
do
in
upstream
kubernetes.
There
is
not
a
facility
for
this.
So
specifically,
especially
in
our
operator
ecosystem
openshift
will
notice
that
hey
you're,
using
an
operator
that
maybe
is
just
not
even
present
the
partner,
has
marked
that
it
isn't
available
in
the
next
version
of
openshift.
Yet,
and
so
we
can
say,
hey,
you
probably
don't
want
to
upgrade,
because
you
probably
care
about
what
that
operator
is
doing
or
the
api
has
changed
between
this
operator
versus
that
one.
D
And
you
know
there
might
be
a
change
required
there
or
you
need
to
upgrade
the
operator
before
you
go
to
the
new
version.
Usually
like
our
operator,
authors
will
write
things
so
that
they
work
across
like
openshift,
four,
seven,
four,
eight
and
four
nine,
and
so
then
you
can
upgrade
to
the
new
version,
one
for
eight
before
you
then
jump
to
four
nine,
that
type
of
thing,
but
we've
got
kind
of
warnings
and
like
walk-throughs,
for
all
of
this.
D
D
And
so
I
forget,
I
think
I
I've
been
using
a
single
deployment
yaml
for
my
personal
website
on
a
cube
cluster
for
like
a
really
long
time-
and
I
wrote
it
like
literally
like
four
years
ago,
five
years
ago
and
never
updated
it
and
finally
the
it
stopped
working
when
I
needed
it,
I
made
a
change
and
wanted
to
redeploy
it
and
openshift.
I
think
it
was
like
the
either
the
alpha
or
maybe
the
beta
of
the
deployment
object
itself
and
it
was
like.
D
I
don't
know
what
this
is
anymore,
but
what's
cool?
Is
my
website
kept
running
because
openshift
had
automatically
dragged
that
thing
forward
through
all
the
api
changes,
because
it
had
that
logic
built
into
it?
So
I
I
needed
to
update
my
yaml
before
I
could
apply
it
again
but
like
it
never
stopped
running,
and
you
know
because
openshift
carried
it
forward,
which
is
kind
of
cool.
B
A
B
Yeah-
and
so
I
also
I
want
to
highlight
that
we
also
talked
about
this
in
one
of
our
streams,
I'm
going
to
try
and
find
which
one
that
was
it
was
relatively
recent
anyways,
so
we
talked
about
it
in
more
depth
in
one
of
the
stream.
One
of
the
recent
streams
chris
will
find
the
link
for
that
and
post
it
in
there.
So
I
want
to
highlight
a
couple
of
things,
so
an
etcd
backup
is.
It
includes
everything
that
is
an
sct.
B
So
what's
an
cd,
it
is
the
state,
the
expected
state
and
the
desired
state
of
the
entire
cluster,
and
that
includes
not
just
things
like
hey.
I
need
this
deployment
to
be
created
and
it
needs
to
have
three
replicas
and
it
needs.
You
know
I
need
this
service.
It
also
includes
things
like.
I
expect
there
to
be
a
node
named.
B
B
Yeah
and
when
we
had
who
was
it,
I
think
it
was
a
nons
on
when
we
we
had
a
stream
dedicated
to
scd
when
we
talked
to
anons.
You
know
his
thing
is,
and
I
talked
to
one
of
the
support
people
as
well.
You
know,
scd
backups
are
great
when
you
lose
a
control,
plane,
node
or
two
or
three,
but
the
rest
of
the
cluster
is
still
there
so
that
you
can
bring
back
that
control
plane
with
a
minimal
amount
of
fuss.
B
So
scd
backup's
not
the
greatest
strategy
in
in
all
scenarios,
but
are
a
possibility
in
some
scenarios.
Just
be
cognizant
of
that.
So
what's
the
real
answer
here,
so
there's
a
number
of
partners
that
have
capabilities
here
I
want
to
say:
trilio
comes
to
mind,
veeam,
there's
a
handful
of
others.
You
can
look
on
the
the
catalog
or
on
the
marketplace
to
find
all
of
those.
B
D
Yeah
get
ops
is
great
for
that.
It's
something
that
we
do
use
on
this
cluster,
where
a
bunch
of
our
product
manager
all
share
this
same
thing,
and
so,
if
you
want
to
onboard
an
app
yeah,
you
go
through
get
you
make
a
pull
request
and
all
that
so
we
use
openshift,
get
ops
and
argo
cd
to
make
that
happen,
but
yeah,
it's
perfect
for
especially
oh
go,
deploy
this
on
five
clusters
or
like
I
want
to
give
this
to
somebody
to
run
on
their
local,
kubernetes
and
docker,
or
something
like
that.
C
A
A
D
D
One
cool
thing
about
this
is
you
can
see
every
instance
of
basically
every
api
that
you
have
on
here
and
so
I've
got
some
operators
installed,
so
we've
got
tons
and
tons
and
tons
of
these
things.
But
let's
go
just
like
search
for
like
let's
say,
pods
right:
let's
go
find
just
like
the
v1
pods
api,
which
is
right
here,
because
we
should
have
some
decent
amount
of
usage
of
this.
D
It
looks
like
our
prometheus
that
we
use
for
openshift
monitoring
is
doing
400,
some
watches,
which
makes
sense
it's
looking
at
all
the
state
and
the
scrape
targets
and
all
that
stuff.
So
you
know
that
makes
sense
and
you
can
keep
on
going
down
and
down
and
down.
We
can
see
here.
Oh
this
one
is
actually
a
kubelet.
D
Is
doing
something
here,
so
you
can
see
that
it's
doing
a
number
of
different
deletes
gets
like
I
mean
it
needs
to
run
the
pods
and
delete
the
pods
and
all
that,
so
that
makes
a
ton
of
sense
as
well
and
just
keep
going
on
and
on
and
on.
So
that's
how
this
is
useful,
even
if
you
just
are
just
trying
to
see
who's
using
one
of
your
apis
for
knees.
D
This
is
not
like
necessarily
like
an
auditing
mechanism
like
I
think
you
could
maybe
use
it
for
that,
but,
like
the
audit
log
is
going
to
be
a
better
thing
for
that.
So
let's
go
back
here
and
we'll
look
at
I'm
trying
to
think
so.
We've
got
web
hooks
is
one
of
our
api,
so
you
can
see
here
that
we've
got
the
v1
and
then
we've
got
the
v1
beta
1..
So
this
is
the
one
that's
deprecated.
D
This
is
the
one
that's
in
use,
and
so
we
can
go
see
how
much
this
one
is
being
used
here.
So
it
looks
like
not
a
lot
of
usage
on
this
one.
Actually
so
you
can
see,
some
of
these
nodes
are
not
doing
any
usage
so,
but
we've
just
got
them
listed
out
here
and
so
great
we're
not
using
this
one.
It's
going
to
be
removed
in
one
two
two
and
our
request
count
is
zero.
D
D
D
So,
okay,
so
we
got
a
few
of
these,
so
cube.
State
metrics
is
doing
some
watches
and
did
one
list
of
this,
and
so
what's
interesting
about
this
is
this
will
get
picked
up
since
this
is
a
part
kube
state
metrics
is
part
of
openshift.
This
will
get
picked
up
when
you
upgrade
from
four
eight
to
four.
Nine
is
we'll
upgrade
this
one
for
you,
so
that
one
is
not
to
worry
about,
but
if
it
was
anything
the
non-openshift
in
here,
then
you
really
start
to
care
about
that.
B
B
D
Because
it
might
be
oh,
we
actually
have
a
pre-release
version
of
that
out
if
you'd
like
to
test
it
or
whatever,
like
because
one
of
the
interesting
things
about
you
know
we're
kind
of
talking
about
openshift
here,
but
this
is
a
kubernetes
problem.
So
if
you,
if
you
have
a
partner
that
supports
all
kinds
of
cubes,
they
all
have
to
deal
with,
this
openshift
happens
to
ship
kubernetes
releases
on
a
pretty
consistent
basis.
D
Basically
one
release
after
they
come
out
upstream.
So
you
know
roughly
about
a
quarter
later,
and
so
we
usually
see
this
first
before
other
folks,
and
so
it
might
be
partners
hearing
this
for
the
first
time,
possibly
because
of
openshift
users.
But
then
it's
going
to
be
other
managed
service
users.
Once
you
know
pick
your
next
favorite
distro
that
updates,
then
all
these
requests
start
flooding
in.
So
it
does
help
to
engage
your
part
and
maybe
even
help
them
test
out
they're
already
working
on.
B
Yeah,
I
think
it's
important
to
highlight
what
you
said
there
at
the
beginning,
which
is
this
isn't
an
open
shift
thing.
This
is
a
kubernetes
thing,
so
it
really.
This
is
affecting
everyone.
It
just
so
happens
that
we're
making
a
a
big
deal
out
of
it
quote.
Unquote,
because
you
know
we
are
relatively.
B
D
The
last
thing
I
want
to
show
is
one
of
those
alerts.
If
we
can
go
see
so
we've
got
you
can
see.
I've
got
a
bunch
of
instances
of
this
firing
one
two
three
four,
because
we're
using
some
apis
that
are
being
removed
and
so
for
each
instance
of
this
that's
firing.
You
can
actually
go
look
at
some
of
the
information
about
what
exactly
it
is,
and
then,
if
that
usage
did
tail
off
because
oh
hey,
I'm
gonna,
do
a
deploy
tomorrow
morning.
That's
gonna
fix
this.
D
D
Yeah,
so
that
that's
a
console
customization
that
again
is
run
through
the
actual
get
ops
pipeline
that
it's
even
telling
you
about.
So
you
know
you
can
customize
it
with
a
yaml
object,
and
so
one
of
the
things
that
we,
when
new
pms
want
to
get
familiar
with
the
process,
we
say:
hey,
go
change
the
color
of
that
banner.
It
used
to
be
blue.
Now
it's
purple.
Somebody
else
might
make
it
green
and
that's
a
way
for
you
to
see
how
the
process
works,
and
you
know
30
seconds
later,
banner's
different.
So.
A
D
Yeah,
so
it's
probably
not
like
a
a
special
or
a
different
process.
It's
just
that
you're
like
compressing
a
bunch
of
changes
into
like
one
like
big
event,
because
you're
going
to
go
probably
from
one
eus
to
another.
Eus
and
eus
stands
for
the
extended
update
support.
So
this
is
just
a
longer
period
of
support
than
we
typically
support
a
release
and
that's
to
give
folks
more
predictability.
D
D
Basically,
what
you're
doing
is
these
alerts
specifically
actually
mentioned
the
eus
so
that
you
can
get
a
heads
up
on
planning
for
this
as
part
of
that
eus
upgrade,
because
probably
what
you're
going
to
do
is
you're
going
to
upgrade
openshift,
but
you're
also
going
to
upgrade
all
the
software
that's
running.
On
top,
that's
the
actual.
You
know
good
stuff
that
meets
your
business
goals.
D
So
in
the
case
of
like
that
cruise
ship,
you
might
have
some
like
the
apps,
where
you,
like,
you
know,
order
your
food
and,
like
all
that
new
versions
of
that
need
to
update
these
apis
if
they're
using
them
and
if
you've
got
vendor
software.
That
also
comes
on
top.
You
need
to
make
sure
that
vendor
has
also
updated
their
software,
and
so
these
alerts
just
help.
D
You
try
to
get
on
that
kind
of
spectrum
of
thinking,
because
you
typically
most
folks
when
they
do
an
eus
upgrade,
they
don't
have
a
lot
of
wiggle
room
and
they
just
really
need
to
have
it
planned
out
very
well
because,
especially
if
the
cruise
ship
needs
to
leave
it's
going
to
leave
port.
You
know
after
like
it's
three
months
or
whatever,
if
it's
downtime,
while
they
upgrade
the
machinery
and
stuff.
So
you
got
to
get
it
done
in
that
three
months.
E
One
one
thing
that
I
think
that
is
very
nice
about
these
alerts
is
like
it's
possible.
The
admin
prevents
problems
like
when
you
upgrade
to
the
cluster
right.
So
if
I
have
a
lot
of
operator
installation,
no
matter,
if
it's
from
the
partners,
I
can
go
there
and
checky
if
he
diverts
my
installation
is
using
the
deprecated
apis,
because
if
he
is
using
enjoyable,
the
cluster
for
far
nine,
it
will
not
work
right.
So
it's
a
very
nice
point.
It's
a
very
nice
feature
to
to
help
me
help
the
items
check
that
right.
D
Yeah
and
our
eus
cadence
does
just
happen
to
roughly
match
the
upstream
api
deprecation
periods.
So,
if
you
think
about,
if
it's
four
releases
upstream
and
we're
going
to
go
to
three
releases
a
year,
we
actually
have
more
overlap
there
and
in
some
cases
we
actually
we
don't
plan
on
extending
our
own
support
for
things
that
have
been
deprecated
upstream,
but
we
have
done
that
for
certain
situations.
D
A
A
C
D
B
Yeah
we
we
had
a
stream
on
olm
not
too
long
ago
as
well
so
cool.
I
will
find
that
as
well
yeah,
you
you
have.
I
we
each
have
different
things
up
which
works
out
well,
but
I
don't
have
the
list
of
so
I'm
just
kind
of
reviewing
the
the
set
of
things
that
I
had
kind
of
pre-staged
or
or
the
different
questions
that
I
had
thought
about
coming
into
this.
D
D
It's
really
look
at
what
the
upstream
is
doing,
and
you
know
we'll
talk
about
this
stuff
on
the
openshift
blog
as
well,
and
you
know
we're
obviously
tracking
that
stuff
very
closely,
but
I
think
that's
where
you're
going
to
start
to
see.
You
know
if
you
really
want
to
be
really
bleeding
edge,
like
the
change
about
pod
security
policies
and
its
deprecation
was
talked
about
inside
of
the
you
know,
the
working
group
long
long
before
it
actually
became
an
official
policy.
D
A
B
B
B
There
we
go
blocked,
upgrade
yeah,
so
if
you
watch
these
errata,
it
will
tell
you
when
the
edges
get
blocked
and
it
will
tell
you
exactly
why
they're
blocked
and
all
that
other
stuff
I
know
historically
for
anybody
who's
watched
the
stream
before
I
tend
to
use
the
cincinnati
graph
data
repo,
which
is
kind
of
low
in
the
weeds.
If
you
will,
this
is
the
kind
of
official
way
that
they
publish
those.
B
So
you
may
want
to
subscribe
to
those.
If
you
don't
already,
I
know
I
think,
as
employees
we
get
subscribed
to
all
of
the
alerts
all
of
the
time,
so
they
get
routed
to
devnull
for
me,
but
so
this
is
a
great
way
to
keep
updated
with
what's
going
on
there
and
then
they
do
eventually.
Many
of
these
make
their
way
into
the
release
notes.
B
So
if
we
go
back
to
the
docs
here
and
release
notes,
and
then
you
got
to
come
like
all
the
way
down
to
the
bottom,
you
can
see
all
the
way
down
here.
It
talks
about
all
the
things
that
have
been
going
on
inside
of
there
so
to
camilla's
point.
The
release
notes
are
a
phenomenal
way
to
understand.
What's
going
on,
like
you
can
see
here,
I
think
we
might
have
talked
about
this
on
stream.
I
don't
remember,
but,
like
the
minimum
storage
requirement
decreased
from
120
gigabytes
to
100
gigabytes.
E
D
D
Yeah,
and
so
we
talk
about
deprecations-
that
of
kind
of
the
non-api
variety
like
we're
talking
about
api
contracts
here
but
like
even
when,
like
certain
features
or
technologies,
we
don't
see
a
future
for
them
in
openshift.
We
will
tell
you
that
ahead
of
time,
so
that
you
can
plan
accordingly
and
there's
a
whole
section
for
that,
as
well
as
well
as
then,
all
of
our
our
tech,
previews
and
other
things
for
what's
new,
and
what
do
you
want
to
try
out?
All
of
that
is
in
here.
C
D
B
D
I
believe
there
are,
I
don't
know
if
they're
gonna
wait
to
go
live
until
like
you
really
really
need
to
do
something
about
it.
Like
I,
don't
know
how
much
buffer
room
we
give
you
there.
So
I
don't
know
if
they're
live
right
now,
but
they
do
exist
and
may
either
go
live
if
they're
not
closer
to
the
four
nine
release.
B
B
So
if
you
are
deploying
or
if
you're,
using
acm
advanced
cluster
manager-
and
you
have
your
clusters
connected
into
that-
you
create
a
cluster
pool
and
you
click
the
button
that
says
deploy
submariner
and
it
does
it
all
for
you.
It's
super
neat
and
thank
you
rhope9
for
linking
the
documentation
there.
A
I
think
I
can
take
this
one.
Can
you
explain
what
deprecation
actually
means?
It
means
at
a
point
in
the
future.
This
feature
will
go
away
and
that
feature
could
be
right,
like
the
beta
version
of
the
api
being
bumped
up
to
stable
or
like
an
alpha
version,
just
not
getting
adoption
and
fading
out
that's
kind
of
how
that
works.
Yeah.
You
know
the
official
kubernetes
definition
of
deprecation.
I
can
look
that
up,
but
I
mean
that's
the
layman's
term
stuff.
D
Yeah
and
it's
it's
kind
of
communicating
an
intent
in
the
future,
so
you're
saying
right:
this
is
deprecated
now
so
probably
don't
invest
in
it
or
upgrade
whatever,
and
then
it
will
be
removed
at
some
point,
and
so
the
reason
we're
here
today
is
because
we've
reached
that
point.
This
stuff
is
actually
getting
removed.
Right.
A
D
I
think
we
there
was
like
a
if
these
things
either
don't
progress
to
stable
by
x
time
period.
They
need
to
be
removed
or
just
dropping
a
bunch
of
cruft,
which
I
think
is
mostly
what
this
is
is
like
look.
These
things
have
been
in
here
for
years
at
this
point
like,
let's
just
finally
get
rid
of
them,
but
on
that
one
of
the
links
that
you
posted
about
the
removals
as
you
can
see
the
things
that
are
deprecated
in
the
versions
that
they're
going
to
be
removed.
D
A
E
I
think
one
thing
nice
is
it's
likely
to
admit
right:
they
let
they
know
it's
like
if
they
have
a
lot
of
operators
installed
in
the
cluster,
were
they?
Oh
everything
is
working
now,
but
if
the
epigraphy
449,
for
example,
where
this
apis
doesn't
check
cc
anymore,
and
they
have
the
operators
versus
installation
that
they
are
using
these
apis,
then
this
operation
will
not
work.
A
B
B
B
E
B
Yeah,
so
for
our
audience,
please
don't
hesitate
to
reach
out
at
any
point
in
time.
If
you
have
any
questions
about
today's
topic,
if
you
have
any
questions
about
really
anything
else
related
to
openshift
and
and
using
openshift,
so
you're
welcome
to
contact
me
on
social
media
at
practicalandrew
I'll,
throw
chris
under
the
bus
at
chris
short
on
twitter.
You
can
also
reach
us
via
email.
We
post
our
email
addresses
in
chat,
but
just
reiterate
I
am
andrew.sullivan
at
redhat.com
and
chris
is
short
rehadhat.com.
B
If
we
can't
find
the
answers,
we
are
always
happy
to
track
down
and
harass
the
right
people.
So
don't
don't
be
afraid
to
ask
us
about
anything
and
everything,
and
with
that
being
said,
we
will
see
you
in
two
weeks.
Remember
next
week
is
ansible
fest,
so
be
sure
to
join
those
again
sign
up
for
brain
dates.
If
you
want
to
have
one-on-one
with
smes
around
many
things,
not
just
openshift
around
ansible
awesome.