►
From YouTube: Ask an OpenShift Admin (Ep 56): Edge Validated Patterns
Description
What is an edge validated pattern, and how can it simplify your deployment experience? Of course, edge computing takes more than just the right platform. But with so many options, it can be a puzzle to assemble the tech stack that’s uniquely right for you - that’s where validated patterns can help.
This episode looks at Red Hat Edge’s validated patterns and some of the detailed deployments created for different edge use cases. These pre-defined edge computing configurations can simplify the deployment experience, use automation to create a lifecycle that ensures they continue to work as new versions of the dependent products are released, and help you stand up your edge architecture faster. So please bring your questions and join us to learn more about edge computing and Red Hat validated patterns.
Learn more: https://www.redhat.com/en/products/edge/validated-patterns
https://www.redhat.com/en/blog/validated-pattern-industrial-edge-v20
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
C
Hello
and
welcome
to
this
week's
ask
an
open
shift.
Administrator
office
hour
live
stream.
That
is
a
mouthful
that
I
have
to
like
concentrate
on
every
week.
Johnny.
How
many
times
have
I
worked
that
100
of
the
time?
What's
the
napoleon
dynamite
right,
sixty
percent
of
the
time
it
works
all
the
time,
every.
C
A
C
Yeah,
you
know
it's
it's
a
great
day
to
turn
eight.
I
guess
so
today
is
something
that
I
think
johnny's
been
looking
forward
to
for,
at
least
since
we
put
it
on
the
schedule
about
a
month
ago,
and
it's
it's
something
that
is
interesting
to
me
as
I
learn
more
and
more
about
it.
So
you
know
johnny
what
what
are
we
talking
about
today.
A
Yeah
so
today
anthony
and
I
are
and
we'll
introduce
anthony
here
in
a
bit
but
anthony-
and
I
are
going
to
talk
about
the
validated
patterns
that
our
engineering
group
is
working
on,
and
you
know
we're
really
excited
about
what
we're
doing.
I
think
we've
we've
seen
a
lot
of
great
output
from
our
team
and
yeah.
There's
a
lot
of
excitement
building
around
it.
C
Yeah,
I
I
am
too
because
there's
let's
just
say
I
have,
I
have
questions
right.
You
know
johnny,
you
know
my
background
right,
administrator
and
all
that
other
stuff
right.
We
we
focus
a
lot
on.
You
know
what
we
used
to
call
reference
architectures.
So
I
I'm
excited
I'm
interested
to
find
out.
You
know
what
all
of
that
means
from
a
validated
platform
pattern.
I
keep
wanting
to
say
platform.
I
think
I've
said
validated
platform
probably
more
times
than
I
have
pattern,
and
I
don't
know
why
anyways
it
just
makes
sense.
C
I
get
it
yeah,
so
I'm
excited
to
learn
what
that
means
for,
for
you
all
for
our
audience.
So
with
that
being
said,
this
is
one
of
our
office
hours
series
of
live
streams.
So
what
that
means
here
on
red
hat
live
streaming
is
that
we
are
here
to
answer
your
questions
so
just
like,
if
you
ever
had
a
manager
or
a
professor
who,
you
know,
had
open
office
hours
where
you
could
come
in
and
talk
about
or
discuss
anything
that
you
need
to
discuss.
C
We
can't
improve
your
grades,
but
we
can
certainly
help
answer
some
questions
about
openshift.
So,
regardless
of
what
today's
topic
happens
to
be
you're,
more
than
welcome
to
ask
any
of
those
questions
in
chat,
regardless
of
which
platform
you're
you
happen
to
be
watching
us
on,
they
all
get
rebroadcast
and
integrated.
So
we
can
see
both
youtube
channels,
twitch,
all
that
other
stuff
here
in
our
interface.
So
please
don't
hesitate
to
to
ask
those
questions,
so
we
will
before
we
get
into
today's
topic.
C
We
will
have
our
what
I'm
going
to
call
a
reoccurring
segment,
which
is
the
top
of
mind
topics.
Let
me
bring
up
my
notes
document
here.
So
the
first
thing
before
I
forget
and-
and
I
want
to
make
sure
to
get
it
out
of
the
way.
So
if
you
are
not
aware
so
from
a
stream
perspective
next
week
we
will
have
frank
baldwin
and
the
oh
gosh.
What
is
it
the
performance
add-on
operator
on
the
stream?
C
So
if
you're
interested
in
performance
add-on
operator
right
how
to
kind
of
maximize
the
performance
of
your
nodes
for
things
like
dpdk?
Actually,
it's
dptk
supported.
I
don't
remember
definitely
sriov
right
all
that
other
stuff
be
sure
to
join
us
next
week.
For
that
we'll
be
talking
about
a
myriad
of
other
things
as
well,
so
be
sure
to
get
subscribed,
and
if
you
don't
subscribe
on
one
of
the
channels,
I
would
definitely
encourage
you
to
go
to
red.ht
livestream.
C
There's
a
google
calendar
embedded
in
that
page
that
you
can
subscribe
to,
and
it
has
all
of
the
streams
that
are
inside
of
there
so
next
week,
we'll
be
doing
performance
add-on
operator
the
week
after
that
the
16th
is.
We
will
not
be
streaming
this
stream
instead
during
our
time
slot.
Actually
it's
starting
a
little
bit
earlier.
I
think
it
starts
at
10
a.m
and
goes
until
11
30
a.m.
C
Eastern
is
the
what's
new
in
open
shift
4.10,
so
that
is
the
product
management
team's
opportunity
to
basically
give
you
all
all
of
the
details
of
what's
happening
inside
of
4.10
and
then
johnny,
and
I
typically
follow
those
up
with
another
episode
where
we
focus
on
some
of
the
things
and
dive
a
little
bit
deeper
into
those
for
things
that
we
think
are
interesting
to
you.
So
if
you
have
the
opportunity
to
watch
that
long
stream,
great
maybe
take
some
notes,
suggest
some
things
that
you
want
to
learn
more
about
to
us.
A
Yeah,
the
roadmap
is
a
great
way
to
get
an
idea
of
like
what's
on
the
horizon,
you
know
so
that
way.
You
know,
there's
always
a
feature
that
somebody's
looking
for
that.
You
know
you
may
not
know
that's
you
know
even
thought
of
right
now.
So
take
the
time
go
out
there
and
look
at
it.
I'm
really
happy
that
we
open
that
up
to
everybody
to
see
it.
You
know
so
it's
exciting
and
yeah
go
find
out
what
what
openshift
is
doing
to
make
make
your
lives
easier.
C
C
C
So
this
is
something
we
briefly
mentioned
it
a
while
ago,
effectively
what
it
is
and
if
we
scroll
down
in
the
page
here,
so
you
can
see
that
this
is
a
command
line
that
will
go
and
effectively
deploy
a
single
node
instance
of
quay
that
you
can
then
use
to
mirror
images.
So
this
is
really
helpful
for
disconnected
installs
or
you
know,
even
if
you're
pseudo-connected
right,
where
you're
you
don't
want
to
have
your
images
pulled
directly
from
the
internet,
you
want
to
cache
them
locally,
so
super
useful
for
that.
C
It's
a
very
quick
and
easy
way
to
get
a
registry
up
and
running
inside
of
your
infrastructure
and,
of
course,
it's
clay,
so
it's
super
powerful
to
to
to
boot.
But
if
we
scroll
all
the
way
down
here,
a
couple
of
things
to
note
so
the
mirror
registry
can
be
downloaded
at
no
additional
cost.
From
the
downloads
page,
so
it
is
included
with
openshift.
C
It
is
supported
as
a
part
of
openshift
just
be
aware
that
it
is
not
and
you
you
are
not
intended
to
use
it
as
a
replacement
for
the
internal
registry
or
a
replacement
for
a
standalone
like
full-on
quay
registry
instance
for
all
of
your
applications
and
stuff.
It's
specifically
targeted
at
you
know,
mirroring
open
shift
images
for
deploying
clusters
and
stuff,
like
that.
A
C
C
C
So
I
talked
with
a
bunch
of
different
folks,
product
management,
engineering,
et
cetera,
as
a
follow-up
to
that
one
of
the
things
that
came
out
of
that
and
if
we
scroll
all
the
way
down,
I
won't
say
it
was
just
me:
it
was
field
folks
and
account
teams
and
all
of
that
working
with
with
them
as
well
in
the
red
hat
security
bulletin.
Oh,
I
forgot
to
publish
this
link.
C
They
added
this
question
for
what
is
the
impact
to
openshift,
so
the
abbreviated
version
of
that
is
essentially
the
the
exploit
is
a
quote-unquote
local
exploit
man.
I
cannot
talk
today.
I
cannot
say
my
p's
is
a
in
a
local
exploit.
So
what
that
means
is
that
effectively
for
someone
to
take
advantage
of
it?
They
would
need
to
have
you
know,
root
access
or
the
ability
to
log
into
the
host
anyways
with
openshift,
that's
limited
to
the
core
user,
and
if
you
can
log
in
with
the
core
user.
C
C
C
So
while
yes,
openshift
and
red
hat
enterprise
linux
coreos
core
os
is,
is
vulnerable,
it
is
mitigated
somewhat
by
some
other
circumstances.
That
being
said,
they
are
working
on
a
fix.
I
don't
know
the
precise
version
of
openshift
that
it'll
be
in
because
it
depends
on
release
cycles
and
how
they
do
all
that
stuff.
C
So
hypothetically
and
I'm
sure
anybody
who's
watched,
the
stream
long
term
knows
of
like
let's
say
next
monday
is
you
know,
4.8.,
I
don't
know
703
that
might
not
get
promoted
into
fast
or
stable.
It
might
stay
in
candidate
for
other
reasons,
so
it
could
be.
You
know
the
next
version
704
that
would
be
the
one
that
gets
promoted
into
stable.
So
it's
hard
to
say
on
this
day
with
this
version
you
will
have
access
to
fixes
for
that.
Rather,
we
just
have
to
wait
for
those
promotions
to
happen.
C
All
right
tiger
can
raspberry
pi
running
microshift,
be
a
worker
node
for
normal
openshift
cluster.
I
don't
believe
so,
but
we'll
check
with
the
microchip
folks
when
they,
when
they
join
us,
I'll,
collect
your
questions
on
that
tiger
and
we'll
put
them
in
the
notes
document
that
we
use,
so
we
can
be
sure
to
address
them
when
they
join
us
and
tiger.
I
know
you're
a
red
hatter,
so
you
can
also
send
me
messages
internally
if
you'd
like,
since
you
mentioned
4.10
curious
to
know
what
the
release
date
is.
C
So
we
don't.
Let
me
rephrase
that
andrew
doesn't
ever
discuss
specific
dates
because
they're
always
prone
to
change,
as
in
like
I
have
seen
a
openshift
release
slip
hours
like
two
hours
from
the
originally
intended
shipping
time
and
it
slipped
by
two
weeks
in
that
instance.
So
we
are
expecting
it
to
ship
soon.
I
would
say
ideally
in
q1,
so
calendar
q1,
so
you
can
kind
of
project
that
out,
but
remember
that
times
are
always
subject
to
to
change
depending
on
whether
or
not
they
find
any
last-minute
bugs
and
stuff
like
that.
C
C
Words
are
hard
today,
so
part
two
was
released
earlier
this
week
or
maybe
friday
last
week,
which
for
me
it
was
a
lot
of
fun,
not
the
least
of
which,
because,
like
this
flyover
in
the
introduction,
it
says
raleigh
in
like
2014,
and
it
actually
has
the
old
logo
here
on
the
building,
and
then
I
think,
the
next
scene.
It
cuts
to
yeah
red
hat
tower,
and
now
we
have
the
new
logo.
C
C
I
was
actually
at
the
very
first
cncf
meeting
in
new
york
city
when
they
had
it
at
the
times
building.
So
it
was
super
fun
and
super
interesting
to
see
the
very
beginning,
or
I
guess
that
was
just
after
the
very
beginning
of
kubernetes
and
of
course
red
hat
was
very
involved
from
from
the
very
beginning.
So.
A
C
Even
talk
about
it,
we
should
talk
to
your
manager.
I
know
yeah
sachin.
It
was
good
to
see
clayton
yeah
clayton,
so
clayton
actually
lives
here
in
raleigh.
I
think
so.
We've
at
my
previous
employer,
we
did
a
podcast
and
we
actually
had
him
on
at
one
point
we
haven't
had
him
on
here,
though,
maybe
we
should
do
that.
Johnny.
A
C
That'd
be
awesome
last
but
not
least,
one
that
this
is
kind
of
late
breaking
news.
If
you
will
so
they
just
did
the
re
the
press
release
for
this.
I
don't
think
it's
even
like
it's
public,
but
it
hasn't
actually
been
linked
from
the
press
releases
page.
Let's
check
real,
quick
yeah,
so
it's
not
even
on
the
press
releases
page,
but
it
has
been
released
and
that
is
so
red
hat
open
shift.
Platform
plus
entitlements
now
include
openshift
data
foundation
essentials.
C
So
essentially,
this
is
a,
I
won't
say,
an
add-on,
but
basically
it's
in
addition
to
that
entitlement.
No
additional
cost
where
you
can
go
in
and
add
odf
essentials,
which
entitles
you
to.
I
think
it's
256
terabytes
of
capacity
inside
of
there.
So
if
you're
using
openshift
platform
plus
entitlements
today,
you
can
now
deploy
odf,
you
can
take
advantage
of
that
shared
storage
rate.
The
local
storage
on
your
hosts
for
all
of
your
pvc
needs
up
to
256
terabytes.
A
That's
that's
really
good
news
and,
if
you're
not
if
you're
not
familiar
with
the
platform
plus,
it
comes
with
a
lot
of
the
the
big
things
that
red
hat
wants
you
to
use
right,
acm,
I
think
acs
is
in
there
now
odf,
that's
really
great.
So
I
think
that
it
simplifies
the
the
subscription
purchasing
and
all
that
and
helps
people
get
up
and
running
without
worrying
about
you
know,
licensing
or
whatever
yeah.
C
Yeah,
it's
I
know
our
or
my
team
there's
several
folks
who
are
working
on
like
environments
and
stuff
like
that
for
red
hatters
to
be
able
to
get
hands-on
with
all
of
the
products,
all
the
things
in
openshift
platform
plus.
So
that
will
be
an
easier
on-boarding
thing
so
for
any
red
hatters
who
are
watching
very
soon.
We'll
have
those
environments
available
to
you,
I'm
just
looking.
I
don't
think
that
my
links
are
coming
through.
I'm
pasting
them
onto
youtube
the
openshift
youtube
channel,
but
I'm
not.
C
A
For
sure,
but
real,
quick,
I'm
going
to
answer
sasha's
question
the
inclusion
it's
to
make
it's
to
simplify
the
the
purchasing
of
subscriptions.
Really
it's
it's
so
that
you
don't
have
to
worry
about
buying
like
eight
different
skus
for
the
the
products
that
you
want
to
use.
It
helps
give
you
a
single
skew
to
order
to
get
what
you
want
right
in
like
a
single
shot,
so
it
helps
simplify
that
that
workflow,
that's
really
most
likely
why
they're
doing
it
but
yeah
validated
patterns.
A
B
Manager
in
the
office
of
the
cto
focused
on
edge
and
these
validated
patterns,
so
our
validated
patterns
initiative
started
about
a
year
and
a
half
ago,
and
we've
been
working
towards
bringing
up
a
number
of
use
cases
into
the
library,
I'm
extremely
happy
to
have
johnny
on
the
team.
I've
been
with
red
hat
for
about
five
years
now,
but
it
this
is
a
fantastic
initiative
to
showcase
real
world
solutions,
or
at
least
the
framework
for
those
solutions
into
a
reproducible
architecture,
and
the
framework
is,
is
what
we're
working
on.
C
You
know
that
sounds
an
awful
lot
like
a
reference
architecture,
so
we
have
reference
architectures
things
that
we
actually
call
reference
architectures
from
our
partners,
I'll
dig
up
the
blog
post,
there's
a
blog
post
that
has
a
whole
list
of
those
from
primarily
our
hardware
partners,
and
we
have
portfolio
architectures
right.
There's
a
is
I
I
don't
know
if
they're
publicly
accessible,
but
certainly
red
hatters
are
aware
of
the
portfolio
architecture
team
and
then
we
have
validated
patterns.
So
can
you
describe
what
the
difference
between
those
is
like?
C
A
So
a
reference
architecture
is
it's
essentially
just
a
a
architecture
that
you
would
use
to
product
to
make
your
environment
your
production,
ready
right,
it's
something
that
we
say:
hey,
here's
the
best
best
practices
to
get
your
your
solution
in
place.
You
know
in
a
production
environment
a
validated
pattern.
Is
it
takes
that
reference
architecture
and
it
essentially
runs
it.
You
know
it.
We
we
build
the
framework.
A
The
github
stream
work
around
that
that
reference
architecture,
so
we're
building
out
the
argo
applications,
we're
building
helm,
charts
and
we're
building
all
of
the
automation
through
a
git
ops
framework
for
that
reference
architecture,
and
then
we're
also
running
it
through
a
ci
pipeline
right.
So
a
reference
architecture
is
a
moment.
I
actually
got
this
from
anthony
earlier.
It's
it's
a
point
in
time,
snap
of
that
design
right
and
the
the
red
hat
validated
pattern.
Is
it's
a
life
cycle
of
that
reference
architecture?
A
So
you
know
you
get
you
get
the
whole
get
ops
framework
and
then
you've
got
a
ci
pipeline,
that's
kind
of
like
controlling
that
life
cycle.
So
when
you
go
from
4.8
to
4.9
or
4.9.4
to
4.9.700
or
whatever
right,
it's
running
through
the
ci
pipeline
and
on
the
other
end
comes
out.
This
validated
pattern
that
you
know
that
you
can
take
from
one
environment
to
another.
A
You
know
obviously
you'd
have
to
the
key
here
is
you'd
have
to
have
your
own
open
shift
cluster,
and
then
you
would
just
take
your
your
80
legos
and
then
you'd
have
your
20
right
and
you'd
bolt
that
in
to
our
validated
pattern,
and
that's
really
what
you
get
at
the
end.
So
I
think
that's.
The
biggest
difference
is
that
reference
architecture
is
a
point
in
time
and
the
validated
pattern
is
the
life
cycle
of
that
reference
architecture
from
you
know
from
now,
until
it's
dead.
A
Yeah,
so
what
we
do
is
we
there's
a
ci
aspect
or
there's
a
a
qe
aspect
to
our
team,
and
so
once
we've
got
it
in
git
and
we've
said
hey
thumbs
up.
It
runs
through
the
the
qe
team,
they
run
it
through
a
ci
pipeline,
and
then
you
know
once
that
comes
out.
That's
that's!
Really
the
the
8
000
foot
view
of
the
oversimplified
process
right
we
build
it,
maintain
we
build
it,
deploy
it,
send
it
over
to
qe
qe.
A
C
So
I'm
I
don't
know
the
answer
to
this,
so
I'm
I
usually
you
know.
What's
the
thing
about
being
a
lawyer
and
never
ask
a
question,
you
don't
know
the
answer
to
I
I
I
know
you're
on.
You
know
you
and
the
team
you're
on
the
engineering
side
yep,
and
I
hear
you
mentioning
you
know
ci
and
qe,
and
all
that
does
that
mean
that
these
are
supported
like
if
you
deploy
using
this
pattern.
It
is
a
supported
pattern.
A
I
I'm
gonna
defer
to
anthony
on
that
question.
The
products
themselves
are
supported,
yeah,
the
red
hat
products
themselves
are
supported,
but
as
far
as
the
pattern
right
there
there
is
an
aspect
of
it
that
that
is
it's
community
right.
It's
a
it's
a
community
project,
so
you
know
it
kind
of
comes
with
those
those
you
know,
restraints
or
whatever
constraints.
If
you
want
to
call
it
that,
like
it's,
you
know
when
we
can't
you
know
but
anthony
I'll.
Let
you
I'll
let
you
answer
that
better.
B
I'm
not
sure
if
it's
better
in
this
case
there's
an
aspect
of
validation
and
that's
what
we're,
including
in
here
when
you
had
asked
earlier.
What's
the
difference
between
all
these
different
offerings,
a
lot
of
the
things
are
the
same,
ultimately
they're,
just
a
reference
of
a
solution
when
we're
looking
at
our
side.
B
If
you
have
a
problem
with
openshift
inside
a
pattern
inside
a
validated
pattern,
openshift
support
will
will
take
the
call.
So
you
shouldn't
worry
that
you're
not
going
to
get
support
on
this,
we're
doing
the
ci
testing
to
try
to
forestall
some
issues
coming
your
way
when
going
from
openshift
4.9
to
4.10,
as
you
upgrade,
the
stack
as
well
as
all
the
minor
components
and
the
things
that
don't
always
get
tested
are
connecting
from
kafka
to
through
the
api
chain
to
all
the
different
services
in
these
patterns.
B
So
that's
what
we're
trying
to
to
do
within
this
validation
stage?
Will
it
be
supported
all
the
the
products
inside
a
validated
pattern?
Right
now
are
all
red
hat
products,
because
we're
only
delivering
as
johnny
said,
80
of
the
solution,
the
top
20
is
going
to
be
partners
system.
Integrators
consultants
and
the
hardware
is
obviously
not
red
hat
either,
so
we're
relying
on
external
forces
to
surround
the
validated
patterns
to
make
them
work
for
any
customer.
B
C
A
Right
and
a
good
example
of
that
right
is
when
the
apis
were.
The
api
extensions
were
deprecating
right,
so
we
would
have
caught
that.
A
really
great
example
actually
is.
Last
week
open
shift
get
offs.
The
operator
went
out
1.4.0
and
within
I'd
say
minutes
of
the
release.
We
identified
quickly
that
there
was
a
parameter
that
was
removed
from
the
crd
right,
and
so
we,
our
team,
like
three
out
of
the
five
engineers
on
our
team,
caught
it
within
like
10
minutes
right,
and
we
reported
that
submitted
the
juror
ticket
and
all
that
stuff.
A
So
I
mean
like
it,
I'm
not
saying
everything's
gonna.
Be
that
quickly
a
turnaround,
but
that's
you
know
same
day,
maybe
next
day
we're
gonna
catch
that
stuff
pretty
quickly
and
find
out
before
the
entire
world
finds
out.
You
know
right
on
their
face
that
you
know
something
broke
and
they
can't
explain
why,
and
so
I
think
that
that's
really
a
lot
of
the
value.
The
un.
The
unspoken
value
that
you're
going
to
get
from
a
validated
pattern
is.
C
So
or
when
asked
a
question
here
and
I'm
going
to
expand
on
a
little
bit
and
I
think
we'll
answer
it
kind
of
in
the
flow,
and
that
is
you
know
what
is
what?
What
is
that
validation
process?
What
does
that?
Look
like
from
kind
of
inception
to
delivery
and
or
one
specific
question
is,
you
know,
is
performance
benchmarking,
a
part
of
that
performance.
A
Benchmarking,
I
do
not
think
on
the
medical
diagnosis.
Specifically,
it's
definitely
not
part
of
it.
There
might
be
some
of
it
built
into
the
industrial
edge
pattern,
but
I
I,
if
it's
not
part
of
the
original
architecture,
then
you
know
it's
probably
not
gonna,
be
part
of
the
initial
pattern
build
out,
but
from
the
way
it
goes
from
inception
to
deployment
and
anthony.
A
You
know
please
chime
in
q
and
q
or
qn
if
there's
something
else
that,
like
I'm
missing
on
that,
but
from
inception
to
to
production,
really
it's
like
we,
we
get
this
reference
architecture
or
this
poc
that
was
delivered
to
a
customer
or
a
solution,
and
we
we
take
that
and
then
we
we
decouple.
You
know
if
it's
written
in
ansible
or
if
it's
written
in
shell
or
if
it's
you
know,
there's
like
this
hodgepodge
of
you
know
both
right.
C
A
Correct
that
we're
not
we're
not
in
the
business
of
telling
you
how
to
build
your
cluster
right
like
if
you
need
odf
right,
there's
restrictions
that
come
with
odf
right.
You
have
to
have
x
amount
of
compute.
You
have
to
have
you
know.
Odf
is
a
big
operator,
so
you
know
you
have
to
have
a
lot
of
cpu
and
a
lot
of
ram.
Obviously
a
lot
of
disks
and
stuff
like
that.
A
So
there
there
are
those
aspects
where,
like
you
said,
you
have
to
be
ready,
your
environment
has
to
be
ready,
and
then
we
just
lay
down
the
pipeline
on
top
of
that,
and
then
it
goes
and
we
do
get
into
that
a
little
bit.
I
it's
more
of
a
high
level
from
an
application
standpoint,
but
not
necessarily
on
the
openshift
side,
from
an
architecture
but,
like
I
said
it
doesn't
matter
as
long
as
you
have
the
resources
that
you
need
to
run
that
workload,
we
don't
care.
C
Got
it
so
kind
of
to
to
ortwin's
question
circling
back
and
answering
that
indirectly,
it's
the
performance
is
whatever
you
configure
the
cluster
to
be
right,
and-
and
you
know
you
mentioned
the
medical
imaging
one.
You
know
you
mentioned
the
edge
validated
pattern
so
I'll
pick
on
the
medical
imaging
for
a
moment
right.
I
would
suspect
that
your
cluster,
you
know
deployment,
is
going
to
look
very
different
if
you're
doing
one
image
an
hour
versus
you
know,
100
000
images
an
hour
right.
So
basically
the
the
patterns
team
doesn't
addre.
C
A
C
A
A
Install
and-
and
this
pattern
in
particular,
is
the
medical
diagnosis,
and
so
it
uses
a
combination
of
odf
grafana,
there's
a
bunch
of
operators
that
get
deployed,
but
it's
also
right
now
a
combination
of
helm
and
argo
and
then
there's
a
little
bit
of
ansible
for
some
of
the
imperative
commands
which
we're
running
on
or
we're
working
on
completely
converting
into
openshift
jobs.
So
that
way,
it's
completely
declarative
and
we
don't
have
any
imperative
things
going
on.
A
C
How
does
a
an
architecture
or
an
implementation?
I
guess
right,
so
how
does
it
become
a
validated
pattern?
Does
that
mean
that
a
customer
has
adopted
it?
Does
that
mean
that
you
know
we're
for
lack
of
a
better
term
like
inventing
this
as
an
example
of
how
to
do
something?
I'm
curious
about
the
kind
of
before
johnny
starts
work
on
this.
How
did
it
come
to
be.
B
B
C
And
I'm
I'm
afraid
to
ask
this
because
I
know
you
know
there's
never
enough.
You
know
humans
behind
the
scenes
to
execute,
but
is
there
like
how
many
validated
patterns
are
there
and
kind
of
the
follow-on
to
that?
Is
you
know,
hey
I'm
a
customer.
I
did
something
that
I
think
is
really
cool.
Can
I
submit
that
as
a
validated
pattern
to
your
team.
B
Anyone
can
put
a
pattern
on
we're,
also
working
with
partners
to
be
able
to
deploy
our
patterns
and
their
third-party
solutions
at
the
same
time,
in
the
same
get
ops,
workflow
so
we'll
we
can
talk
about
all
of
this
there's
lots
of
areas
to
get
into.
I
want
to
make
sure
that
we
have
time
for
johnny's
presentation.
A
You
know,
operators
that
start
popping
up
and
once
they
do
I'll
kick
over
to
to
argo
and
then
we'll
look
at
argo
from
the
application
side.
So
that
way
we
can
kind
of
see
it
going
through,
but
it
open,
openshift
data
foundation
takes
so
long
to
come
up
because
nuba
has
to
come
up
and
it
has
to
do
some
validations
and
then
you
know
the
ocs
operator.
It
actually
doesn't
complete
until
everything
completes
so
and
by
the
way
the
cool
part
about
this
is
we've
just
been
sitting
there.
A
Shooting
the
breeze
and
all
I
typed
was
make
install
right
so
that
that's
something
to
remember
when
we
talk
about
simplicity
and
ease
of
use
right,
I
type
to
make
insole
and
we're
getting
all
of
these
operators
popping
up
automatically.
You
know
all
the
routes
are
being
created,
all
the
things
that
we
need
to
make
this
application
operational.
A
It's
all
automated.
You
know
so
then,
now
what
this
means
is
when
you
come
in
and
you
have
a
cluster
or
when
we
come
in
and
you
have
a
cluster
and
you
take
this
framework,
you
take
your
20
or
your
25
percent
and
you're
the
last
mile
right,
you
plug
you,
plug
your
notes
and
bolts
into
this
framework,
and
now
you've
got
a
full
solution
that
has
meaningful
impact
to
your
organization.
A
You
know-
and
I
think
that
that's
where
you
know
at
least
for
me
when
I
get
excited,
that's
what
I'm
I'm
I'm
getting
amped
up
thinking
about
this
right,
because
I
was
in
consulting
for
five
years
and
there's
so
many
times
that
we've
deployed
openshift
from
311.
You
know
I
mean
I
mean
three,
four,
three,
three
to
four
ten.
You
know
what
I
mean
where
or
four
nine
rather
and
for
just
people
can't
you
know
they
get
overwhelmed
and
you
know
they.
A
A
I
got
this,
you
know
what
I
mean
and
then
now
they've
deployed
something
and
it's
meaningful.
It
shows
value
back
to
them
and
back
to
their
organization,
and
then
it
helps
them
have
that
base
layer
that
now
they
can
build
on.
It
gives
them
like
a
legit
framework
that
they
can
like
truly
build
on
and
then
be
part
of
a
community
that
they
can
distribute
back
to
and
then
everybody
can
build
on
it.
You
know
what
I
mean,
so
I
mean
it's
just
this.
A
C
Yeah-
and
I
was
just
looking
at
so-
I
posted
a
link
to
the
hybrid
cloud
patterns,
dot,
io
and
there's,
there's
hyphens
between
hybrid
and
cloud
and
cloud
and
patterns.
So
I
was
looking
at
the
site
and
there's
you
know
basically
documentation
around
each
one
of
these,
including
there's
a
very
nice
architecture,
diagram,
logical,
diagrams
and
and
all
of
this
other
stuff
that
go
into
a
lot
of
detail
inside
of
here,
and
I
do
see
kind
of
what
we
were
talking
about
before.
C
There's
cluster
sizing
suggestions
around
like
different
platforms
that
it's
been
tested
on
and
different,
like
node
counts
and
node,
saw
instance
sizes,
instant
types
rather
so
yeah,
I'm
I
I
was
cognizant
of
this
website.
I
had
not
actually
looked
at
it
in
depth
and
there
is
just
a
wealth
of
information
here.
A
B
A
A
Standpoint.
We're
gonna,
run
just
scale
up
a
pod
and
what
that's
going
to
do
is
it's
going
to
sync
images:
x-ray
images
from
an
s3
bucket
via
nuba.
You
know
because
it's
s3,
but
it's
really.
It's
like
noob,
backed
from
odf,
and
it's
going
to
push
it
through
an
amq
pipeline
and
then
so
amq
and
then
serverless
and
all
that
stuff
is
gonna
happen
and
then
it's
gonna
display,
like
the
the
pictures
of
the
x-ray.
A
A
It's
using
x-rays
right
for
to
to
check
for
pneumonia
or
to
detect
pneumonia
rather,
but
this
is
just
one
sample
right
like
there's,
there's
other
ones
where
you'll
be
able
to
take
a
hopefully
a
ct,
scan
or
x-rays
of
something
else
and
be
able
to
detect.
You
know
other
anomalies
within
the
within
the
body,
so
it'll
it'll
help
take
some
of
the
human
errors.
Out
of
you
know,
x-ray
visualization
or
x-ray
reporting-
and
you
know,
make
some
of
these
medical
diagnoses,
the
medical
diagnosis,
much
easier
right
and
and
much
more
accurate.
C
And
it
just
out
of
curiosity
the
validated
platform
or
pattern
rather,
and
I
really
gotta
stop
saying
platform
the
validated
pattern
it
doesn't
have
to
be
used
with
the
specific
application.
Rather,
it's
kind
of
you
know
yes,
we're
showing
it
and
it's
tested
and
validated
using
this
application,
but
really
it's
all
the
parts
and
pieces
that
go
into
that
and
you
know
it
could
be
a
different
application.
That's
doing
maybe
something
similar.
You
know
using
the
same
same
bits.
A
Yeah
100,
so
the
idea
is
that
it's
legos
right,
like
it's
modular,
so
each
one
of
these
things
right.
You
have
your
acm,
that's
one
component
of
it.
You
have
odf,
that's
another
component.
You
know
the
20
in
this
regard
would
be
like
the
image
generator
and
the
image
server
and
demo
right
where
everything
else
is
a
red
hat
product,
and
so
you
know
that
those
three
things
there
might
actually
be
four.
A
I
just
I
might
be
misremembering,
but
like
those
three
or
four
things
right,
that's
gonna
be
that
20
25
that
you're
bolting
on
right,
you're!
That's
that's
our!
That's
our
nuts
and
bolts
that
we're
putting
into
this
pattern
to
make
it.
You
know
meaningful
to
us
right,
yeah,
but
everything
else.
It's
modular,
they're
built
to
be
individual,
repos
and
so
they're,
reusable
they're
composable,
like
that.
It's
it's
all
the
all
the
good
stuff
about
automation
and
open
shift
and
get
off
kind
of,
like
all
wrapped
into
one.
A
C
C
C
So
essentially
what
you
would
have
to
do
is
if
you're
using
openshift
sdn
day
two,
you
could
use
something
like
nmstate
operator,
which
is
tech
preview
right
now
to
to
reconfigure
that
interface.
So
go
from
a
single
interface
to
a
bond
or
something
like
that.
If
you're
using
ovn
kubernetes,
then
you
can't
do
that.
It
won't
allow
you
to
basically
break
if
you
change
that
first
interface,
so
ipi
would
not
be
ideal
there
yeah.
I
don't.
C
I
don't
think
if
you
have
two
network
adapters
that
are
on
the
same
network
and
both
have
an
ip
address.
I
don't
think
that
would
work,
because
etcd
is
configured
for
a
specific
ip
address
for
each
one
of
the
nodes
and
it
will
it
would
take
whichever
one
comes
up.
First,
so
jenny.
I
know
you're
you're
watching
your
argo
there.
I
don't
know
if
you
had
any
thoughts
on
that.
A
C
A
All
right
we're
really
only
waiting
for
the
ocs
operator
to
essentially
do
its
health
check,
but
one
thing
I
just
wanted
to
kind
of
to
key
in
on
here
is
yeah,
I'm
just
going
to
click
on.
You
know
kafka
whatever,
but
the
cool
part
about
argo,
if
you're
not
familiar
with
argo,
is
that
it
literally
gives
you
a
visual
representation
of
you
know
the
resources
that
are
deployed
in
your
cluster.
You
know
so
like
this
kafka
application.
This
is
our
argo
application
right.
A
It's
it's
deploying
a
kafka
resource,
the
kafka
topic,
the
routes
and
then
each
one
of
those
is
pointing
to
a
service
which
is
pointed
to
a
pod
or
whatever
you
know.
I
mean
there's
just
all
this
cool
stuff.
That's
happening
like
to
me.
This
is
probably
like
you
know,
coming
from
you
know,
being
an
infrastructure
guy
and
then
trying
to
help,
deploy,
applications
and
stuff
like
that.
This
is
probably
the
coolest
thing
ever
to
see
like
when
it
just
starts
like
popping
stuff
out.
It's
just
amazing.
C
A
Is
it
is,
and
if
you
like
automation-
and
you
like-
I
think,
a
lot
of
people
like
automation,
you
know
what
I
mean,
but
I
think
a
lot
of
people
love
visualization
and
I
you
know,
there's
a
lot
of
things
that
you
don't
really
get
out
of
that
from
like
normal
writing,
ansible
core
or
writing
a
shell
script.
Right,
like
you
might
put
some.
You
know
some
green
feedback
where
you're
like
oh,
okay
or
red,
stops
or
whatever,
whatever
you
know,
all
that
old
school
stuff,
but
like
with
ansible
tower.
A
You
can
do
workflows
and
then
get
that
nice
visual
representation
of
your
workflow
going
through,
and
I
think
that
that
was
a
big
hit,
and
I
think
that
with
this
and
argo
this
is
just
awesome
to
see
and
it's
cool
to
see
it
just
like
spider
web
out
to
all
the
resources
and
like
really
help
people
understand
just
how.
How
awesome
this
thing
is:
it's
not
just
an
app
right.
It's
an
app
with
all
of
its
buddies.
A
C
A
C
That
kind
of
makes
sense
you
know,
because
each
application
is
going
to
be
different
and
have
different
requirements.
You
know
we've
talked
about
this
before
here
on
the
stream.
You
know
with
each
one
being
different.
It
means
that
there's
going
to
be
different
methods
of
recovery.
You
know
each
storage
provider
is
going
to
have
a
different
method
of
replicating
storage
or
protecting
storage,
so
on
and
so
forth.
So
speaking
of
which,
for
anybody
in
the
audience
odf
is
a
topic.
I
know
we
talked
about
it
some
with
annette.
C
A
A
C
C
C
B
Ci
so
that
it's
being
tested-
but
there
are
changes
happening
in
that
common
framework,
so
that
we
can
add
in
vault
or
sealed
secrets
over
time
and
they'll
be
back
ported
into
the
older
patterns
or
the
validated
patterns
to
to
bring
them
up
to
speed
over
time.
But
we're
trying
to
do
things
in
a
more
methodical
way
so
that
we're
not
just
constantly
being
updating
and
and
causing
disruption
at
customer
sites.
If
they
just
decide
to
deploy
these.
C
You're
you're
kind
of
you
know
flirting
with
the
edge
of
something
there,
which
is
I
really
really
like
and
that's.
I
know
you
know
most
people
don't
see
this,
but
internally,
because
I
I
you
know,
I'm
I'm
adjacent
to
the
openshift
product
management
team.
Like
we
see
your
team
driving
a
lot
of
road
map
stuff,
that's
happening
across
openshift
and
to
me
it's
really
cool
that
you're.
Creating
these
things
that
are
effectively
to
to
you
know
quote
the
name.
It's
a
validated
like.
C
Yes,
you
can
do
this
and
checking
and
making
sure
and
finding
all
of
those
little
errors
and
all
of
these
little
incompatibilities
and
inconsistencies
that
you
know
normally
we
would
have
to
rely
on.
You
know.
Unfortunately,
we'd
have
to
wait
until
a
customer
tries
to
do
it
right
and
now
you
all
are
finding
those
way
earlier
in
the
process
so
that
that's
really
cool
to
me.
B
C
B
Not
just
individual
product
solutions
as
much
as
they
are
incorporated,
we're
looking
at
what
the
business
value
is
for
a
customer
to
deploy
this
from
a
hospital's
perspective,
to
reduce
the
number
of
doctors
that
they
need
to
see
a
patient's
x-ray,
because
they
can
do
some
ai
on
that
x-ray
and
see
what
the
likelihood
that
they
have
pneumonia
or
sepsis
or
other
diseases
associated
with
it.
So
there's
some
really
cool
stuff
here.
C
That's
a
that's
a
really
interesting
way
that
you
put
it
of
you.
You
are
effectively
a
customer,
for
all
intents
and
purposes,
and
very
much
to
your
points.
You
know
the
product
management
team
as
a
whole.
You
know
they.
They
quote
unquote
own
openshift
and
all
of
the
features
and
functions
on
top,
but
ultimately
each
one
of
them
is
only
responsible
for
a
small
piece
and
even
me,
as
a
tech
marketing,
you
know
person,
I
only
own
are
responsible
for
a
couple
of
those
pieces.
C
So
it's
hard
to
see
it's
hard
to
get
that
you
know
basically
confirmation
validation
again
across
you
know
the
big
large
swath
of
all
of
the
things
that
are
happening
inside
of
there.
So
yeah,
I'm.
You
know
I
I
make
no
secret
about
it
internally
or
externally.
I
love
the
work
you
all
are
doing
and
not
just
y'all,
but
also
the
the
portfolio
architecture,
team,
right
and
all
that
other
stuff,
and
that's
certainly
not
to
discredit
the
work
that
our
partners
do
with
reference
architectures
or
anything
like
that.
But
it's
super
valuable.
B
A
About
a
thousand
on
demo,
so
I
mean
like
my
my
luck
with
demos.
Live
has
been
outstanding,
so
yeah,
so
what's
going
on
is
like
there's
a
job,
that's
running
in
the
back
background,
and
it's
essentially
doing
like
this
initialization
and
there
there
might
have
been
like
a
little
bit
of
a
race
condition,
so
I'm
trying
to
reset
it
to
get
this
thing
up.
But
if
you
look
at
the
output
on
on
here
this,
this
is
the
the
visual
representation
of
of
like
the
pipeline.
A
That's
going
on,
so
you
can't
really
see
it,
which
kind
of
sucks
but
like
right
right
in
the
middle
of
the
screen
under
the
wrist
distribution.
That
would
be
the
images
that
are
being
processed
first,
that
are
normal
versus
with
pneumonia
or
whatever,
and
then
over
on
the
far
right
would
be
where
the
the
x-ray
itself
would
be
presented.
You
know,
and
then
these
images
it
just
shows
the
the
images
that
are
going
through.
B
C
A
It's
going
to
go
out.
It's
going
to
install
ocs
or
od
open
openshift
data
foundations.
It's
going
to
install
amq
streams,
it's
going
to
configure
all
of
those
it's
going
to
create
the
kafka
resources
and
you
know,
then
it's
going
to
go
through
the
openshift
server
list
and
it's
going
to
create
those
jobs
or
those
those
functions.
So
servos
can
do
its
thing
and
then,
at
the
end,
you're
going
to
have
this
this
tool.
That
is
usable,
you
know,
and
it's
going
to
provide
value.
C
So
so
terence
highlights
something
here.
You
know
it's
a
great
teaching
tool
tool
to
show
off
best
practices
with
deploying
complex
applications
and
anthony.
You
had
used
the
phrase
best
practices
before
as
well.
So
is
that
a
part
of
the
deliverable
like
is
there
you
know
if
we
go
and
browse
through
the
websites?
B
B
It
is
still
a
point
in
time
review
from
our
architects
and
the
engineers
and
people
within
red
hat
to
say
is
this
the
way
I
want
to
deploy
it
if
something
was
to
change
in
one
of
our
patterns
and
we're
no
longer
able
to
use
the
api
as
as
defined
we
may
have
to
change
things?
Does
that
mean
that
the
best
practices
changed,
maybe
on
how
you
solve
this
problem,
because
this
is
the
only
way
to
do
it,
but
there
are
also
alternatives
using
amq
or
apache.
B
C
C
So
g
kumar
a
little
off
topic,
but
when
is
the
next
release
of
3.11?
The
last
one
is
december
8th,
I
don't
know
so
off
the
top
of
my
head.
My
initial
response
is
that
3.11
is
in
maintenance
phase,
so
I
would
expect
that
it
will
only
be
releasing
when
there's
things
like
security
issues
and
and
bugs
and
stuff
like
that.
So
I
also
want
to
highlight
johnny.
I
know
you're
still
bouncing
different
things
inside
of
there.
C
C
If
you
have
any
questions,
comments,
concerns
issues,
please
go
ahead
and
get
those
into
the
chat
we'll
address
those
as
they
come
in.
You're
also
welcome
to
reach
out
to
to
me
at
any
point
in
time.
You
can
reach
me
via
email,
andrew.sullivan
at
redhat.com.
You
can
also
reach
out
on
social
media.
So,
if
you've
seen
me
chatting
there
on
twitch
practical
andrew
is
my
twitter
handle
as
well,
so
you
can
of
course
reach
out
on
there.
C
A
C
So,
with
our
last
couple
of
minutes
here
I'll
again
throw
out
a
reminder
and
a
plug
for
two
weeks
from
today,
we
will
have
the
what's
new
in
openshift
4.10
session
with
the
product
management
team,
so
we
will
not
be
having
the
ask
an
openshift
admin
live
stream.
That
being
said,
I,
along
with
several
of
the
other
folks
here
on
red
hat,
live
streaming,
will
be
on
that
stream
and
we
will
be
here
to
answer
questions.
So
if
you
have
any
questions
about,
you
know,
features
functionality
that
type
of
stuff.
C
C
So
definitely,
if
you
are
interested
in
a
lot
of
the
things
happening,
4.10-
and
I
have
to
say,
4.10-
is
a
there's
a
lot
of
stuff
going
on
in
there
ranging
from
you
know,
metal
lb
has
some
stuff
going
on.
I
know
there's
a
lot
of
stuff
happening
with
the
scheduler
and
kind
of
other
low
lane
components
right
things
that
I
tend
to
interact
with
openshift
virtualization
4.10,
which
is
not
a
part
of
the
openshift
4.10
release
it's
a
decoupled,
but
they
usually
follow
within
a
few
days
or
maybe
a
week.
C
They've
got
a
bunch
of
stuff.
That's
coming
out
in
there.
So
4.10
is
going
to
be
exciting.
Csi
providers
there's
a
number
of
csi
providers
that'll
that
are
going
to
be
affected
in
there
so
yeah
it's.
I
would
definitely
encourage
anybody
and
everybody
to
at
least
check
out
one
of
the
recaps
that
you'll
find
around
what's
new
in
4.10,
because
it's
there's
a
bunch
of
stuff
there
yeah
so
johnny
any
any
progress.
A
A
C
We'll
we'll
have
to
talk
to
christian
see,
if
maybe
we
can
get
one
of
the
argo
argo
shirt
sent
to
you
all
right,
awesome
so
to
our
audience.
Thank
you
so
much
for
joining
us
today.
We
really
appreciate
it
again
if
there's
any
questions,
anything
that
you
that
comes
to
mind
after
you're
viewing
this,
I
know
that
we
get
a
lot
of
views
on
the
various
youtube
twitch.
You
know
people
watching
not
live,
feel
free
to
reach
out
to
us
via
email
or
social
media,
anthony
so
much
it.
C
C
A
We
have
a
good
time
with
it,
so
you
know
like
I'm
glad
it
went
down,
because
you
know
stuff
does
always
go
wrong,
especially
when
it
feels
like
I'm
driving.
But
you
know
it
just
goes
to
show
that
you
know
like
there's
just
little
things
that
you
can
tweak
and
then
once
we
get
it
perfect,
it'll
be
in
this
tool
and
it'll
it'll
be
perfect.
All
the
time.
A
All
right
anthony
thank
you.
Lesser
martin
mckelley,
the
validated
patterns
team,
everybody.
You
know,
michael
st
john,
thank
you
guys
for
showing
up
and
and
supporting
the
chat
and
answering
some
questions
too.
So
those
guys
are
rock
stars.
I
I
just
get
to
hang
out
with
them
so
glad
that
they
were
here
and
glad
that
you
know
it
mostly
went
well.