►
Description
Join OpenShift's Developer Experience experts for our regularly scheduled program filled with cloud native, Kubernetes, and OpenShift tips and tricks for developers.
A
B
A
C
C
I
had
a
super
softball
question
for
us
to
to
throw
back
and
forth
today.
If
you
have
better
questions
than
this,
please
drop
them
into
chat.
We
would
love
to
hear
what
you
are
dealing
with
and
try
to
give
you
more
specific
advice,
but
I'm
going
to
start
it
off
with
two
topics
that
I
wanted
to
touch
on
today.
One
is
a
general
question
of
why
containers,
and
also
why
not?
C
What's
the
what's,
the
appropriate
balancing
point
for
developers
to
derive
some
type
of
meaning
and
value
right
and
then
also
I
was
gonna
do
a
demo.
I
have
an
environment
that
I
have
already
done
a
little
bit
of
prep
work
to
set
this
environment
up,
but
it's
ready
to
go
and
we
can
do
a
live
migration
from
openshift
for
something
to
whatever's
available
and
we'd
have
to
go
check.
C
The
check
the
list
of
available
upgrades
to
find
out
what
specifically
is
available
now,
I
know
brian
last
week
talked
about
the
process
he
went
through
of
switching
to
a
different
channel
and
then
initiating
the
upgrade.
So
I
might
try
to
kick
that
off.
That
will
probably
take
a
while.
So
while
we're
working
on
it,
we'd
love
to
hear
your
thoughts
and
questions.
C
B
C
D
B
A
A
A
512
megabyte
limitation
on
pretty
much
everybody
unless
you're
an
enterprise
customer
and
then
there's
only
certain
file
types
that
they're
caching
now
and
cubecal2
was
obviously
not
one
of
them
right
right,
yeah
5g
for
five
gigs
for
enterprise
customers.
I
think
so
yeah
like
even
this
as
an
enterprise
customer,
would
have
been
a
problem
for
me.
So
it's
pretty
wild
right,
but
I
mean
I
can
drop
a
link
to
this.
Isn't
about
me.
This
is
not
the
about
me
show.
This
is
about
the
all
show.
A
A
B
I
mean
I
say
that
you
know
it.
It
is
still,
you
know
relevant,
and
you
know
interesting
for
our
audience
and
our
perspective
at
least.
I
think
it
is
because
you
know
developers
we're
working
on
things.
We
might
have
projects
and
random
little
things
that
we
have
deployed
or
whatnot.
You
know,
and
it's
important
to
you
know,
think
about
those,
not
all
the
time.
You
know
you're
thinking.
Oh
hey,
the
I'm
expecting
my
caching
provider
to
cache
these
files,
but
there's
there's
a
disconnect
or
there's
issues.
So
I
think
that
you
know
that
is.
E
A
C
A
Yes,
I
just
relaunched
it
from
hiatus:
adjusting
oh
adjusting
to
life.
It
was
on
hiatus
for
a
few
weeks
adjusting
to
life
in
the
new
covid
coronavirus
world,
so
yeah.
If
you're
not
following
me
on
twitter,
I
highly
recommend
that,
because
I
will
talk
about
the
channel
on
twitter
and
you'll,
get
email
or
not
email,
but
notifications
about
when
slides,
go
out
and
things
like
that
too.
So
you'll
get
a
lot
of
tech
news.
You'll
get
a
lot
of.
A
A
C
I'm
gonna
go
through
a
sh,
quick
see
how
far
I
can
make
it
before
I
hit
a
wall
here.
So
this
is
a
fresh
cluster.
I
created
this
last
night
skipped
over
the
actual
setup
piece.
So
if,
if
aws
bites,
you
in
the
wallet-
I
don't
know
talk
to
chris
but
oops,
let's
see
if
I
can
get
this
log
in
right,
open,
yeah,.
A
See
so
there's
a
question
chat,
any
update
on
when
the
nsxt
ncp
support
will
be
provided
with
openshift
installer
ipi.
I
don't
even
know
what
nsxt
ncp
is.
So
that
might
be
that's.
Definitely
my
team
question.
Oh
the
reply
function
is
different.
Today,
cool
twitch
updated
some
stuff.
I
will
ask
that
question
in
my
team
chat
and
let
you
know
tajaro
to
your
hero.
However,
you
say
your
screen
name.
D
A
A
C
C
C
Yeah
yeah.
Well,
I
know
I
have
pending
updates
already
available
on
stable
here
in
the
update
stack,
so
it
says,
updates
available.
I
was
just
wondering
how
how
weird
should
I
try
to
get
with
this?
I
could
try
to
do
the
stable
upgrade
and
it
looks
like
I'm
currently
on
openshift
4.4.8,
I'm
not
exactly
sure,
based
on
this,
I'm
a
little
bit
hesitant
to
click
this
update
button
and
do.
A
C
Let's,
let's
I'll
start
with
this
one,
so
I'll
start
with
stable,
but
this
is
definitely
something
that
if
you
wanted
newer,
more
bleeding
edge
code,
you
could
definitely
switch
to
this
release
candidate.
If
you
wanted
something
really
fresh
like
particularly
if
you
were
doing
service
integration,
work
and
you're
building
an
operator
that
is,
you
know,
some
data
supporting
a
database.
I'd
probably
be
testing
against
this
candidate
stream.
C
You
may
encounter
more
errors
in
the
candidate
stream,
but
you'll
get
the
newer
code
and
that's
probably
what
you
should
be
testing
against
if
you're
a
system
integrator
so
I'll
start
with
stable
and
I'll
hit
the
upgrade
button.
Aha-
and
here
it
goes-
here's
the
the
question
box,
so
it
looks
like
we
can
roll
up
to
4.4.16.
C
if
I
successfully
migrate
to
4.4.16.
This
is
the
the
valid
window
of
ranges
that
I
can
migrate
between.
So
I've
got
a
lot
of
flexibility
here,
but
I
can't
just
go
from
4.4.8
to
kind
of
anything
in
the
world.
I
may
need
some
precursor
information
in
order
to
successfully
roll
to
4.5,
so
it's
possible
that
once
I
get
to
4.4.16,
5
will
show
up
as
an
option,
but
I
haven't
played
around
a
whole
lot
with
this
brian.
What
do
you
think
should
I
go
with
four
four?
Sixteen.
B
Yeah
yeah
yeah
do
the
4.4.16,
so
the
the
the
things
that
are
in
this
list
are
things
that
have
been,
or
they
should
have
been
validly
successfully
upgraded.
You
know
from
4.4.8
to
which
version
is
on
that
list,
so
the
4.4.8
version
doesn't
have
a
six
or
it
has
a
you
know.
One
click
upgrade
path
or
whatever
a
4.5.
B
C
B
C
Cd
is
one
of
the
first
things
you're
going
to
you
got
to
update
the
database
central
database
at
first.
Another
thing:
that's
going
to
get
updated
very
early
on
is
the
api
server.
It
looks
like
that
one
hasn't
rolled
yet,
but
that
one
is
going
to
need
new
information
on
how
to
perform
a
controller
manager
as
well.
C
These
two
are
going
to
work
together
in
order
to
perform
rolling
updates
of
kubernetes
itself
and,
if
you're
rolling
to
a
new
api,
it
may
not
have
a
hundred
percent
knowledge
of
what
you're
rolling
forward
to
you
may
need
a
short
amount
of
downtime
on
the
api.
While
you
do
that
swap,
but
it's
hopefully
designed
to
be
a
distributed
system
that
tolerates
small
amounts
of
downtime.
B
Yeah,
yeah,
yeah,
and,
and-
and
this
makes
it
this
makes
it
easy
you
don't
have
to
you
know
you
don't
have
to
you-
know
necessarily
update
each
thing
increment
it
like
it
handles
that,
and
you
could
see
those
updates
happen
as
they're
going
without
affecting
what's
going
on
on
the
system,
so
stuff's
still
working
one
of
the
other
things
that
that
was
neat
too.
That
I
thought
was
interesting
is,
if
you
go
into
the
the
admin
view
you
could.
D
B
C
B
Yeah
each
one
of
those
is
a
a
node,
that's
running
it
could
be
a
master
or
worker
that
that
your
cluster
is
working
on
right.
But
if
you
click
into
one
of
those,
you
could
see
the
red
hat
core
os
version
under
details.
After
you
know
some
of
the
graphs
of
the
metrics
it's
down
on
the
that
page,
you
can
see
that.
B
The
specific
os
image-
and
you
know
these
updates-
might
not
you
know-
have
an
update
to
the
actual
os
image,
but
if
they
do
that
gets
also
upgraded
and
those
nodes
get
rebooted
as
things
go
along
and
you
as
the
person
using
the
cluster,
wouldn't
you
know
know
because
those
upgrades
are
happening.
You
know
staged
one
by
one
and
it's
not
going
to
affect
your
application
running
in
production
or
wherever
it's
going.
C
Yeah
it
looks
like
this
three
minutes
ago,
this
kublet
just
came
back
online,
indicating
that
this
node's
ready
to
get
more
work
and
yeah
graphs,
look
pretty
good.
We
could
see
if
you
were
an
operations
person,
if
you
needed
more
specifics
about
how
that
workload
is
being
managed
or
whether
it's
being
managed
effectively
whether
it
has
memory
leaks
or
other
things.
C
A
One
and
this
could
be
a
rob,
zumke
question,
so
all
these
all
the
upgrade
information
and
tooling
is,
is
it
only
contained
in
one
image
and
from
that
image
all
the
other
images
are
downloaded.
I
believe
this
how
it
works.
It's
one
image
that
fires
off
a
bunch
of
operators
that
fires
off.
You
know
it's,
it's
triggering
a
ton
of
operators,
so
all
those
operator
images
are
being
updated
and
firing.
So
the
actual
mechanics
of
that
will
lead-
I
don't
know,
do
either
of
you
know.
C
That
might
be
a
reboot
for
that
particular
step,
but
once
that
new
kubelet
is
in
there,
it
knows
how
to
run
just
about
any
kubernetes
workload.
Assuming
that
the
api
server
says
hey,
it's
you
wake
up.
It's
your
time
to
go
to
work
right.
It
needs
an
api
server
to
give
it
that
notice
and
we
don't
have
the
next
gen
api
server.
Yet
so
you
manually
get
a
new
kublet.
Somehow
openshift
does
this
using
the
machine,
config
operators
and
that'll
roll
our
base
level
machines.
C
C
B
But
important
to
know
the
upgrade
process
handles
all
of
that,
so
yeah
as
as
the
person
working
at
the
cluster,
all
you
do
is
click
the
upgrade
button.
It's
doing
everything
and
then
you
know
incrementally
doing
you
know
one
upgrade
piece.
Then
the
next
then
the
next.
That
needs
to
get
done
to
upgrade
everything.
C
Yeah
yep,
so,
oh,
let's
see
I
gotta,
let
me
jump
out
of
the
way
again.
It
looks
like
I
have
a
warning
here
and
I'm
going
to
click
in
and
see
looks
like
controller
managers
and
schedulers.
Those
are
the
two
things
I
was
saying
were
kind
of
vitally
important
automatic
image
pruning
is
not
an.
I
don't
know.
If
this
warning
is
super
relevant
to
me,
alerts
are
not
configured
to
be
sent
to
a
notification.
C
Oh
sure,
yeah
yeah
you'd
have
something
more
more
powerful,
so
you're
not
trying
to
swallow
all
that
information
on
your
own.
You
got
to
filter
it
through
something
first,
but
this
whole
system,
even
with
these
two
warnings
system,
never
went
down
system,
is
still
reporting
its
status
appropriately
and
it's
able
to
say
oh
wow,
I
got
stuck,
and
here
I'm
at
and
and
I'm
gonna
keep
working
until
I
get
either
to
the
result
you
want.
Oh
there
we
go
control.
D
C
A
C
Image
pruning
image
pruning,
I
think,
is
more
of
an
optimization
step.
If
you
have
a
very,
very
new
cluster
one
of
the
things
you
want
to
do
in
order
to
make
sure
that
cluster
is
fast,
is
pre-populate
images
onto
every
node
in
the
system
that
is
going
to
need
to
use
those
images.
So
if
you
have
node.js
builds
that
are
running
that'll
take
a
lot
longer
if
the
worker
worker
node,
where
the
build
is
being
performed.
If
it
doesn't
have
the
node.js
image,
it's
going
to
have
to
wait,
do
a
pull.
C
You
know,
pull
down
a
couple
hundred
megs.
It
doesn't
take
that
long,
but
it
can
be
maybe
like
a
10
20
second
delay
in
your
build
process,
and
at
that
point
the
node.js
image
will
get
cached
on
that
one
machine
you
run
another,
build
your
build,
might
run
on
any
any
node
in
the
cluster.
You
may
have
to
pay
that
same
time
penalty
again,
so
an
optimization
technique
is
pre-populating
all
those
images
onto
every
machine
where
they
will
be
needed.
C
On
the
other
hand,
the
result
of
the
build-
maybe
maybe
you
can
clean
up
that
image
after
a
while
there
is
a
certain
amount
of
image,
pruning
and
image
cleanup.
That
does
need
to
happen,
but
that's
kind
of
more
day,
two
like
usually
my
first
concern,
is
making
sure
developers
can
work
and
and
that
their
builds
will
run
after
I
get
that
crossed
off,
then
I
can
work.
You
know
work
on
cleanup
and
and
kind
of
shining
things
up.
A
C
C
C
C
D
C
C
So
there's
a
the
image
streams
and
the
images
these
are
going
to
be
things
that
are
there's
a
image
registry
that
every
openshift
cluster
comes
with.
If
you
were
using
google
container
image,
they
would
encourage
you
to
use
a
centralized
or
a
hosted
container
registry,
specifically
gcr
or
google
container
registry.
C
As
long
as
they're,
relatively
close
together,
the
wider
out
the
more
spread
out
your
kubernetes
cluster
is
the
harder
it's
going
to
be
to
synchronize
things,
but
if
the
machines
are
all
relatively
tight
synchronization
and
you
have
a
centralized
image
registry
like
openshift,
includes
then
you're
you're
good.
I
think
we
give
you
the
default
docker
registry
as
a
as
a
starting
point
is.
A
C
C
B
You
could
look,
you
could
look,
there's
a
couple
of
things
and
I
know
that
you
know
quay
koi,
dot,
io
and
quay
enterprise
are
a
thing
and
you
could
have
quay
enterprise
running
on
openshift
and
use
that
as
your
image
registry.
But
that
is
not
what
you
get
by
default.
You
get
one
that
is
included
with
the
openshift.
B
Just
the
open
shift
image
registry
and
you
could
look,
you
could
go
under
the
the
projects
and
look
at
the
openshift
image
registry
project
if
you're
admin
on
that
cluster,
which
you
should
be
the
other
two
things
that
I
wanted
to
to
mention,
is
there's
a
search
on
the
administrator
view
under
home.
So
just
look
under
the
phone.
C
C
It
looks
like
it's
70..
What
did
it
say?
Administrator
get
back
to
my
overview
check
the
cluster
settings,
so
78
percent
complete
to
get
this
upgrade
to
4
416
done
and
then
at
that
point
I'll,
be
able
to
check
and
see
if
we
can
roll
to
4-5
but
coming
along
pretty.
Well,
I
mean
it's
it's
I
can
try
deploying
a
basic
project
and
we
can
test
to
make
sure
that
it's
fully
operational,
even
while
its
head
is
being
slowly
replaced
with
new
information.
C
C
A
A
B
C
C
C
Of
everything
yeah
I
need
a
better
way
of
sharing
screens
looks
like
we've
got
at
least
some
progress
on
this.
I'm
gonna
check
back
in
on
the
administrator
side
and
see
what
how
we're
doing
with
the
cluster
settings
still
78.
Okay.
Well,
let's
see,
let's
see
if
we
get
there
before
the
end
of
the
the
yeah.
I
think
part
of
this
is
for
me
is
excellent,
because
I
never
want
to
have
to
deal
with
managing
the
cluster
upgrading
the
cluster.
C
B
Yeah
I
mean
I
agree,
so
it
lets
me
focus
on
what
I'm
building
versus
the
infrastructure
component
right.
So
I
I
I
just
get
the
openshift
cluster
kubernetes
cluster
set
up
running
and
I
could
focus
on
what
I'm
doing
and
I
don't
have
to
think
about.
Oh,
I
I
need
storage.
I
just
need
to
you
know,
create
a
pv
and
a
pvc,
and
I
I
get
storage
for
example
right.
I
don't
need
to
think
about
how
to
connect
all
that
stuff
together.
C
So
it
looks
like,
even
though
I
wasn't
able
to
load
the
the
ui
during
the
demo,
this
thing
still
ran
the
build
things
are
still
happening
in
the
background.
Without
my
knowledge,
I
don't
need
to
know,
I
don't
need
to
care.
Hopefully
the
the
system
provides
a
productive
work
environment
for
people
who
are
interested
in
having
a
productive
work
environment.
C
C
A
C
D
C
C
C
Yeah
yeah,
whatever
your
pipeline
is,
you
could
definitely
mix
in
claire
to
get
some
visibility
and
that
usually
is
going
to
rely
on
you
using
your
workloads
need
to
be
built
from
some
type
of
image
that
has
a
cve
reporting
against
it.
So
I
think
alpine
linux
is
now
on
the
list
of
base
images
container
images
you
can
use
that
does
get
cves
reported
against
it.
Oh.
D
C
So
alpine's
now
a
viable
option
as
far
as
at
least
visibility
of
security
alerts.
Other
things
that
I
would
highly
recommend,
there's
a
universal
base,
images
or
ubi
sounds
like
universal
basic
income,
and
maybe
you
can
convert
it
into
money.
I
don't
know,
but
ubi
gives
you
kind
of
a
rel
or
a
rpm
based
base
image
or
or
at
least
something
that
reporting
wise
is
very
consistent
with
rel
fedora.
B
So
yeah
serena
serena
mentioned
there's
a
couple
options
too.
So
quay.I
o
you
could
use
that's
a
software
as
a
service
and
you
can
pay
for
it,
get
some
advent
advanced
features,
but
by
default
you
get
security
scanning
there
and
you
could
have
openshift
pool
from
quay.io.
Like
you
mentioned,
there's
also
the
container
security
operator
which
you
can
install
and
it
will
give
you
some
details
with
just
the
standard
open
shift
image
registry.
B
B
It's
scanning
the
image
registry,
that's
on
openshift
and
it'll
pass
some
of
that
information
to
openshift
so
that
you
could
see.
What's
going
on
security-wise
in
the
openshift
console
blackduck
comes
to
mind,
there's
other
vendors
out
there
that
work
with
us
quite
a
bit.
So
there's
many
options.
The
one
that
serena
mentioned,
though,
is
the
the
container
security
operator,
and
I
have
that
on
my
screen
I'll
I'll
post
the
link
into
the
chat
you
can
install
that
on
the
operator
hub,
that's
built
into
openshift.
C
Yeah,
that's
that's
a
great
suggestion.
Brian
thanks.
The
the
hub
is
always
a
good
place
to
to
turn
to
for
partner
vendor
solutions,
especially
if
you
want
a
second
opinion.
Other
than
just
red
hat's
advice.
Take
a
look
at
what
the
rest
of
the
community
is
doing
and
what
people
are
doing
outside
the
openshift
space
as
well.
We're
trying
to
make
sure
everyone
has
the
tools
they
need
to
do
their
best.
C
Let's
see,
do
one
more
check
in
here
on
whoops.
Let
me
get
another
check
in
on
how
our
cluster
is
doing
looks
like
we
still
got
a
little
bit
more
work,
we're
still
at
83
percent.
It
looks
like
only
one
major
piece
is
still
waiting.
There's
a
machine
config
with
four
four
eight
other
than
that.
It
looks
like
we're
just
about
completely
rolled
to
4.4.16,
so
we're
basic.
Basically
there.
It's
probably
just
rolling
worker
nodes
at
this
point.
A
D
C
C
A
A
A
C
A
Like
go
ahead
and
get
your
cluster
spun
up
and
let
it
upgrade
itself
and
let
you
work
around
along
with
it
right
like
if
you
have
them
built
in
a
consistently.
You
know
if
you
have
your
applications
built
in
a
cloud-native
way.
That'll,
you
know
take
advantage
of
you
know
multiple
pods
or
you
know
not
lock
themselves
down
to
one
node,
particularly
somehow
you
know
through
through
annotations
or
labels
yeah.
Your
application
should
just
move
itself
right
around,
along
with
the
upgrade
to
just
keep
itself
running.
C
A
A
B
Always
I
did,
I
did
network
security
for
a
little
bit
and
it's
always
about
layered
security
protocol
yeah.
You
need
you
need
that
right,
because
there's
there's
different
ways
to
do
many
different
things.
They
pick
up
on
different
signatures.
They
pick
up
on
different
things,
so
you
need
to
stack
the
deck
in
your
favor
if
you're
really
trying
to
be
secure
to
put
it,
you
know
ultra
simple
and
you
need
multiple
layers
in
your
security
approach,
so
scanning
container
images
and
exactly
what
you're
saying
there's
multiple
different
ways
to
do
that.
A
I
don't
want
to
say,
like
only
rely
like
it's
safe,
to
rely
only
on
clear
right
like
because
I
feel
like
claire
is
robust,
but
claire
is
not
going
to
be
like
a
quick,
speedy
thing
that
you
need
right
like
if
you're
like
all
right,
I'm
just
gonna
try
and
kick
the
tires
on
this
image.
Like
is
this
even
sane
to
run
this
in
production
yeah
running
truly
against?
It
makes
total
sense,
and
then
maybe
you
discover
you
know
later
on
down
the
chain
that
oh,
this
actually
has
a
cv.
A
C
When
open
shift
recognizes
that
a
new
base
image
has
become
available,
it
can
automatically
trigger
a
new
build
to
basically
restitch
the
application
code
on
top
of
an
upgraded
base
image
and
then
do
a
rolling
upgrade
out
to
deployment.
So
you,
without
even
involving
your
developers,
you
can
go
from
this
morning.
I
had
a
hundred
percent
of
my
node.js
workloads
were
vulnerable.
C
I
found
the
issue
I
did
one
docker
push
and
the
cluster
was
like.
Oh
new
base
layers,
awesome,
I'm
going
to
rebuild
and
redeploy
and
get
you
back
to
where
you
need
to
be
so.
Some
of
the
work
can
be
kind
of
that
simple,
using
a
system
like
open
shift,
but
that's
really
kind
of
relies
on
a
whole
lot
of
coordination
between
you
know:
you're,
sharing
the
same
cluster
with
your
team
of
developers.
C
B
C
D
C
On
google's
cloud
or
anyone
else's
cloud,
the
idea
is
easy
controls.
So
you
don't
have
to
manage
the
complexity
on
your
own,
although
in
the
case
where
you
have
to
have
data
locality
or
machines
that
are
local,
maybe
you're
stuck
with
managing
the
complexity
on
your
own.
If
you'd,
rather
not
geez,
we've
got.
We've
got
the
tools,
regardless
of
what
cloud
bare
metal
a
hosted
doesn't
matter,
you
got
machines,
we'll
make
them
productive
machines,
hopefully
yeah.
Hopefully,.
C
Think
that
is
about
it.
I
was
gonna,
throw
out
a
update
for
folks,
a
small
small
minor
update.
I
pushed
some
changes
to
kubernetes
by
example.com
small
changes.
I
think
mostly
the
diy
page
now
has
links
back
to
learn.openshift.com
with
the
openshift44
environment
instead
of
4.2,
all
right
so
small
upgrade.
But
if
you
have
any
suggestions,
ideas
things
that
you
would
like
to
see
on
kubernetes
by
example.com,
please
file
an
issue.
C
C
C
A
C
A
See
you
there,
maybe
yeah
75
bucks
right
like
that's,
not
bad.
If
you
need
financial
assistance
for
some
reason
and
you
want
to
like
still
go
to
cubecon
and
75,
bucks
is
like
something
that
your
company
won't
cover
or
you
can't
handle
feel
free
to
reach
out
to
me.
There's
no
shame!
I
will
get
you
a
ticket
okay
seriously,
if
the
financial
means
are
just
not
there
for
you
right
now,
I
completely
understand,
and
I
will
help
you
out
yeah,
that's
not
me
giving
dollars
away.