►
From YouTube: KubeCon EU Office Hour: OpenShift 4.7 Q&A
Description
Learn about features in the latest version of OpenShift, or just bring your general OpenShift operations and deployment questions. The OpenShift Developer Advocate experts are here for you.
A
Good
morning,
good
afternoon,
good
evening,
wherever
you're
hailing
from
welcome
to
a
special
kubecon
eu
office
hour,
this
office
hour
will
be
discussing
openshift47
and
addressing
any
questions
you
may
have
about
the
platform
itself
and
you
know
anything
else
that
comes
up
along
the
way.
So
let's
do
a
round
of
intros
I'm
chris
short,
I'm
the
executive
producer
of
this
thing
called
open
shift.
Tv,
josh,
burkus,
yeah,.
B
C
I
always
thank
you.
Thank
you
for
the
extended
introduction,
I'm
ryan
jarvan
and
you
could
find
me
most
places,
usually
muted
in
the
first
minute
or
two
of
the
chat
but
ryan
j
on
and
yeah
I'll
hand
it
off
to
jason
dobies
on
our
team.
We're
all
developer
advocates
on
the
openshift
team,
mostly
on
this
call,
so
welcome
hit
us
up
with
your
questions.
We'll
keep
an
eye
on
chat.
D
Yeah,
the
rest
of
us
are
all
on
the
same
team.
So
in
terms
of
introduction
I'll
just
say,
let's
do
developer
stuff.
My
favorite
language
is
python.
Although
I've
been
doing
a
lot
more
qarcus
related
stuff
been
spending,
obviously
a
lot
of
time
with
openshift
in
the
past
four
years.
Working
with
this
team
and
of
course,
I'm
getting
a
phone
call
so
we'll
hand
it
over
to
brian.
E
F
Hey
yeah,
I'm
brian
tannis,
I
am
also
a
developer
advocate
focused
on
openshift.
I
mostly
focus
on
some
of
the
platform
tools
like
things
like
serverless
and
techton,
and
things
that
could
kind
of
make
your
life
as
a
developer
a
little
bit
easier.
Well,
I
guess
maybe
or
complex,
depending
on
how
you
look
at
it.
F
You
know
there
are
some
things
that
that
do
make
it
a
little
bit
easier,
but
I
do
focus
on
those
and
I'm
sure
we'll
get
into
some
of
those
details
on
here
with
some
q,
a
my
favorite
language
like
jay's
same
thing
would
be
python.
I've
recently
been
learning
a
little
bit
about
elixir
kind
of
curious
about
erlang
and
how
that's
going-
and
you
know
some
of
the
different
pieces
of
where
that's
used-
I
think
it's
kind
of
interesting
it's
distributed
built
in
so
it's
kind
of.
F
G
Yeah,
hey:
hey,
happy
to
stay
still
here.
My
name
is
natalia
vinto.
I'm
a
developer
part
of
this
team
of
developer
advocate
for
openshift.
My
focus,
I'm,
I
think
I'm
I'm
a
java
developer
and
I'm
also
a
devops.
So
this
is
me
and
my
expertise
is
within
openshift
and
all
the
votes
so
cicd
gear
ups.
Of
course
we
talked
about
it
before
so
happy
to
jump
here
in
the
call
with
my
team
talking
about
obviously
for
developers.
B
E
B
C
Faked
myself
out
there
yeah
developer
sandbox
is
one
of
our
newer
offerings.
I
it
looks
like
there's
a
link
in
chat
that
chris
got
for
you
and
yeah.
It's
a
definitely
a
easy
way
to
get
your
hands
on
a
free,
open
shift
environment.
There
is
a
limited
time
trial.
I
think
it's
30
days
now,
yeah
yeah,
we
just
updated
it
to
give
you
a
little
extra
time
and
once
the
30
days
is
up,
you
can
sign,
you
can
click
through
and
get
another
sandbox,
usually
there.
C
It
may
be
that,
30
days
later,
we
have
a
limited
capacity
limitations,
so
you
might
not
get
one
right
away,
but
usually
click
on
one.
You
get
one
immediately,
so
pretty
easy
setup.
A
couple
caveats
I
should
point
out
since
we're
the
developer
advocate
team
and
we
want
to
give
you
the
straight.
No
bs,
here's
here's
the
trade-offs.
C
The
the
caveats
on
this
sandbox.
Are
you
do
not
get
admin
access?
So
if
you
had
operators
that
you
were
hoping
to
install
that's
not
an
option
on
the
sandbox,
you
can
still
go
in
and
download
code
ready
containers
and
set
that
up
on
a
system
with
plenty
of
ram
and
cpu
and
go
to
town
with
that.
You'll
have
full
admin
access
there,
so
plenty
of
options
to
get
started
with
openshift,
if
you're,
if
you're
new
to
it
and
I'm
assuming
folks
on
that
are
joining.
C
B
C
C
It
doesn't
have
a
whole
lot
of
step-by-step
introductions
on
how
to
interact
with
that
playground
area,
but
you
could
definitely
go
through
4.7.
Yeah
4.7
doesn't
give
you
a
lot
of
details
on
how
to
go
through
the
the
4.7,
but
you
can
go
straight
to
the
docks
and
I'll
put
a
link
to
the
4.7
docs.
Pretty
much
do
just
about
whatever
you
like
from
the
official
docs.
F
If
you're
not
familiar,
there
is
the
whole
concept
of
learn.openshift.com.
Just
you
know
we
we
have
recently
added
openshift
4.7,
which
is
the
latest
release,
show
of
open
shift
and
all
of
that,
but
on
learn.openshift.com
we
have
a
set
of
scenarios
and
tutorials
and
things
that
you
could
use
to.
You
know
help
bolster
your
kubernetes
and
you
know
open
shift
knowledge,
so
we
have
some,
you
know
getting
started
with
what
is
a
container.
We
have
some
things
about
openshift.
F
You
know
some
of
the
beginner
type
things
like
this
is
what
a
pod
is.
This
is
how
you
would
expose
a
service,
so
those
types
of
things
are
there.
There
are
also
tutorials
for
more
intermediate
concepts
of
the
tools
that
you
know.
Ryan
was
saying
that
you
wouldn't
necessarily
be
able
to
access
on
that
developer.
Sandbox
like
openshift
pipelines,
which
is
techton
that
we
have
some
news
around
that
which
we'll
talk
about
here
in
a
second
that
we
also
have
some
tutorials
around
get
ops.
B
C
C
C
So
if
you're,
within
a
certain
project
scope
or
for
upstream
folks
in
kubernetes,
if
you're
working
in
a
certain
name
space
and
you
boot
up
a
terminal
in
that
namespace,
it
should
already
have
your
kubectl
and
oc
credentials
already
initialized
and
set
up
to
have
you
work
within
that
namespace
and
everything.
So
it's
it's
really
nice!
I'm
setting
up
a
new
laboratory
workshop
lab.
That's
going
to
use
that
terminal!
Quite
a
bit!
Nice.
D
I'll
do
a
bit
before
someone
steals
mine,
so
two
days
ago
I
guess
we
announced
ga
for
openshift
pipelines.
This
is
something
that
I
I
did
a
demo.
I
guess
two
months
ago
and
I
was
asked
to
put
together
this
kind
of
just
developer
experience
on
openshift.
So
I
had
this
four
container
application
spanning
a
bunch
of
different
languages
and
one
of
the
things
I'm
like
well
it'd
be
kind
of
cool.
D
If
part
one
of
these
containers
was
built
by
pipelines,
because
I
did
one
new
odo,
I
did
one
using
just
a
general
source
to
I
and
there
was
a
couple
different
lessons
going
on,
but
I
was
like
all
right
cool.
This
is
my
chance
to
play
with
pipelines
and
once
I
got
things
working
and
saw
the-
and
I
should
say
I
probably
stressed
that
incorrectly
once
I
got
multiple
pieces
working
and
you
could
see
it
in
the
ui
with
that
pipeline
and
it's
showing
the
progression
and
the
parallel
tasks.
D
It
was
a
really
cool
feeling
and
and
how
easy
it
was
once
I
got
the
initial
setup
in
place
to
just
add
new
steps
and
new
steps,
and
then
I,
admittedly
and
intentionally
over
engineered
it,
because
it
was
for
demo
purposes.
So
I
did
across
three
tasks.
What
could
have
been
one?
So
what
should
have
just
been
stuff
goes
in,
and
this
stuff
comes
out
like
no,
no
we're
gonna
blow
this
out
to
like
12
different
tasks,
but
it
looked
really
cool
and
I
was
impressed.
D
I've
been
impressed
for
months
now,
seeing
the
early
ux
markups
for
what
the
pipelines
were
going
to
look
like
in
the
gui.
I
understood
the
abstraction
but
finally
sitting
down
and
putting
my
hands
on
it
being
like
okay.
This
is
going
to
be
this
particular
task.
I'm
going
to
use
this
one
and
this
one's
gonna
be
custom
and
it
all
just
fell
into
place
and
it
just
started
to
kind
of
click
and
then,
like
I
said
once
I
got
the
kind
of
initial
two
or
three
pieces
in
then
it
was
easy.
D
I'm
not
gonna
lie.
I've
never
been
particularly
interested
in
setting
that
stuff
up.
I've
used
jenkins,
to
the
extent
that
I
was
a
developer
and
I
would
watch
jenkins,
turn
red
and
then
yell
at
someone,
and
it
was
typically
me
turning
it
red
anyway,
so
actually
having
set
one
up.
Yes,
exactly
we've
all
this
is
the
developer
talk.
We
were
talking
about
breaking
the
build,
we're
doing
something
wrong
so
actually
setting
one
up
and
kind
of
putting
the
thought
into
these.
A
C
D
Yeah
and
there's
so
much
between
what's
in
the
developer
perspective,
or
does
that
live
in
whatever
in
the
web
ui,
I
should
say:
leave
it.
That
way
is
a
really
really
neat
ui
using
the
tectonic
command
line
worked.
I
can't
remember
what
I
did
for
each
of
it.
It
was
just
kind
of
throwing
stuff
out
and
poking
around
with
it,
but
the
tecton
cli
works
tkn.
F
Like
yeah,
we
have
a
task
like
that.
Task
is
going
to
do
something
and
there's
steps
you
know
and
to
run
that
task.
You
have
a
task.
Yeah
like
these
are
specifics
for
pipelines,
but
those
are
things
that
make
sense,
and
the
developer
console
on
the
openshift
web
console
makes
it
easy
to
go
and
build
like
you're
saying,
build
that
whole
step
right,
which
is
cool.
D
D
This
is
really
cool
that
I
started
with
a
vanilla,
cluster
and
then
navigated
to
operator
hub
and
obviously
not
showing
any
of
this,
but
if
you've
ever
poked
around
open
shift
or
seen
any
of
our
demos,
you've
seen
a
fair
amount
of
this,
and
then
it
was
this
kind
of
customize,
your
your
cluster.
After
that,
so
I
was
like.
Oh,
I
want
serverless
I'm
going
to
hit
install
on
that.
Oh
I
want
python,
so
I'm
going
to
hit
install
on
that.
D
The
pipeline
ones
is
particularly
interesting
because
you
hit
install
and
as
I
was
talking
over
it,
the
pipelines
menu
appears
in
the
left
and
it's
a
really
cool
like
makes
for
a
great
demo,
because
you're
like
tada,
we
magically
have
pipeline
stuff
at
the
end
of
the
day.
That's
how
it
works.
It's
not
like
a
demo
smoke
and
mirrors
thing,
but
that
that
notion
of
I
have
this
base
cluster
and
it's
just
click,
click,
click
and
kind
of
customize.
It
with
all
these
add-on
features
is
really
cool.
D
G
C
In
the
the
hold
ups
there
from
a
developer
perspective
platform
services
are
things
that
you
can't
install
as
a
developer.
Usually
you
need
admin
credentials,
but
I
think
the
really
powerful
thing
is.
I
can
install
this
cluster
on
any
cloud
and
not
have
to
rely
on
platform
services
that
are
not
cncf
sanctioned
platform
services.
G
Cloud
agree:
no,
no
locking
no
at
least
there's
no
specific
place,
locking
you
can.
This
is
all
open
source
software.
Of
course,
in
the
openshift
version
we
support
a
certain
version.
We
packed
the
support
to
the
version,
but
it's
all
open
source
all
upstream
and
it's
all
operator
hub.
So
in
this
case
it's
really
no
locking
and
you
can
install
in
in
any
place
that
you
want.
D
Let
me
jump
in
quickly
because
I
don't
know
how
commenting
works
with
the
restream
bot,
but
some
of
youtube's
asking
me:
how
long
can
we
use
the
dev
sandbox?
So
it's
30
days
and
someone
correct
me
if
the
policy
has
changed,
but
after
that
the
cluster
goes
away,
but
you
can
get
another
one,
I'm
seeing
not
so
they
haven't
changed
that
policy.
So
you
sign
in
with
your
red
hat
developer.
Account
that's
free!
You
get
your
cluster
for
30
days
and
then
again
you
have
to
make
sure
you
back
up
anything
after
that.
D
There's
no
kind
of
extension,
which
is,
let's
call
it
what
it
is
intentional
because
back
in
the
old
days
of
I
got
open
shift
2,
I
guess
we
had
this
hosting
and
people
would
use
it
to
host
their
wordpress
logs
kind
of
indefinitely,
and
I
know
because
I
was
one
of
those
people
well
yeah.
I
was
on
the
team
and
it
was
a
spectacular
abuse
and
I
kind
of
miss
it.
You
think,
as
an
employee.
I
would
get
access
to
that.
But
now.
D
And
then
you
can
renew
it
as
many
times
as
you
want
just
keeping
in
mind
that
it's
not
an
extension,
so
you're
going
to
have
to
make
sure
anything.
You
have
out
there
that
you
may
want
to
save
some
resources
or
anything
like
that,
if
you're
not
using
proper
git
ops,
where
you've
already
stored
that
stuff
in
version
control
and
recreate
it.
Otherwise
it's
going
to
end
up
getting
knocked
out
on
you.
D
G
Yeah,
you
know
this,
you
know
this
github's
integration
is
really
really
cool
with
argo
cd.
I
think
this
is
gonna,
be
my
my
favorite
from
now
yeah
right
before
it
was
text
on
now.
Now
is
this
one?
It's
it's
still
cool
it's
too,
and
lots
of
work
in
progress.
Also
too
you
to
bring
the
same
experience
you
know
with
tekton.
We
have
this
tight
connection
with
the
web
console.
Really
we
we
have.
If
you
look
at
tekton
know,
tecton
has
also
a
dashboard
is
a
kind
of
standalone.
G
You
can
install
this
dashboard,
but
it's
not
that
in
advanced,
the
the
the
integration
of
tekton
inside
openshift
is
really
powerful
from
a
user
experience
perspective
in
the
dev
console
and
and
I'm
looking
forward
to
the
to
the
works
also
to
integrate.
This
key
tops
experience
in
the
web
console
because,
as
you
know,
the
web
console
is
also
programmable
is
extendable
via.
G
And
I
think
there
would
be
a
talk
at
summit
by
ryan
and
brian
and
jay
talking
about
how
to
customize
the
dev
console.
So
the
customization
comes
also
with
the
operator.
If
you
install
the,
for
instance,
the
quay
operator,
which
is
an
operator
for
having
a
registry
enterprise
registering
openshift,
you
will
have
this
adding
on
the
web
console.
If
you
install
a
pipeline,
you
are
more
adding,
and
so
this
is
a
very
powerful
and
cool,
and
I'm
looking
forward
for
today
tops
integration
to
the
web
console
which
are
coming.
C
Natalie
I
I
would
like
to
say
congratulations
on
your
efforts
on
launching
the
new
learn
topic
area.
We
have
a
new
learn.openshift,
slash
gitops,
that
natalie
did
a
lot
of
work
to
help
get
ready.
So
if
you're
interested
in
learning
more
about
argo
cd
and
get
ops
definitely
check
that
out
I'll
I'll
post.
A
link
in
in
chat
here,
nice
workout.
G
G
Most
of
the
content
comes
from
his
workshop
github's
workshop
and
also
our
colleague
devon
that
collaborated
on
making
this
scenario
so
we're
looking
forward
to
any
hints
or
feedback
suggestion
for
extending
this
github's
learning
path.
At
the
moment
we
do
getting
started
and
then
customize
and
sink
waves
and
hooks,
but
we
would
like
also
to
touch
base
the
new
kitops,
a
cli
called
cam,
which
is
able
to
bootstrap
either
the
pipeline
part
and
the
github
sport,
and
then
we
will
also
like
to
mention
and
covered
in
some
way.
G
E
C
B
G
Yes,
definitely
when
you
install
the
operator,
you
have
tacked
on
apis,
so
you
have
tekton
and
also
tacton
triggers.
So
when
you
install
the
operator,
it
comes
with
a
certain
version
of
the
tecton
core
and
tecton
triggers.
So
yes,
the
the
answer
is
yes
and
we
track
those
version
between
the
version
of
the
operator
and
measure
of
the
tecton
upstream
project
installed
by
the
operator.
G
A
B
B
A
A
G
Well,
this
is
you
know.
This
question
is
a
a
kind
of
architectural
question.
So
usually
the
use
case
is
having
one
single
central,
argo
cd,
that
control
multiple
cluster,
but
if
they
wanna
do
this
multi-tenant
approach,
that
is
definitely
possible
inside
the
same
openshift
cluster,
with
the
fine
grade
that
roll
binding
or
cluster
role
permission
in
multiple
cluster.
G
I
don't
know,
I'm
I'm
not
aware
of
any
work
on
that
and
I
don't
think
the
github,
so
the
key
tops
operator
is
bringing
argo
cd
with
openshift
airbag
and
all
the
permission
and
stuff
that
that
is
needed.
But
I
don't
think
that
we
will
add
more
in
in
terms
of
this
arc,
ocd
multi
tenancy.
So
I
think
it's
a
question
that
need
to
be
investigated
more
maybe
with
cmak
offline
or
in
chat
in
slack,
but
I
don't
think
there.
F
So
you're
saying
yeah
like
what
we
could
limit
access
to
like
who
accesses
it
with
our
back
rules,
but
as
far
as
like
having
multiple
instances
of
argo
cd
running
for
like
each
bu
or
whatever
you.
You
know
how
you
you
know,
designate
your
your
cluster
like
that.
We
don't
think
that
exists
or
we're
not
that
doesn't
exist.
F
F
G
G
That's
a
good
question:
you
know,
because
the
openshift
sdn
is
based
on
an
open
source
project
called
openmp
switch.
So
this
is
the
sdn.
The
implementation
of
the
software
defining
network
ovn
is
a
kind
of
in
our
implement.
That
is
a
kind
of
superset,
so
basically
ovn
in
openshift
use
still
open,
p
switch,
but
it's
a
kind
of
superset
that
can
talk.
Also
with
a
non-linux
implementation
like
in
windows,
you
can
use
ovn
and
under
the
hood
there
is
an
implementation.
G
In
our
case
is
a
open
v
switch
still,
so
the
the
difference
is
there?
Isn't
a
versus
so
open
shift?
Sdn
is
ovn
because
we
implement
in
this
way
ovn
and
openv
switch,
and
thanks
to
this
obn
we
can
also
have
a
a
terror
genius.
Computing
system
like
linux
and
windows,
host,
for
instance,
so
and
kubernetes,
is
using
ovn
for
a
superset
for
all
the
sdns.
So
this
is
the
not
the
difference
is
is
the
context
about
obn
and
openv
openshift
sdn.
A
G
Yeah-
and
I
think
jp
dade
mentioned
a
very
advanced
topic,
which
is
the
kind
of
channeling.
I
think
we're
going
beyond
the
developer
scope
here
yeah,
but
this
is
a
really
niche
information
which
is
a
vxlan
for
a
openshift
sdn,
so
openv
switch
and
geneve
tunnels
kind
of
tunneling
ip
tunneling
used
in
the
software
defining
network.
So
thanks
for
this
very
niche
information,
I
hope
all
the
developers.
I
appreciate
that.
A
B
F
A
B
C
A
C
To
regards
to
multi-tenancy
one
thing
we
upgraded
in
the
last
year,
or
so
has
been
our
support
for
helm,
charts
that
used
to
be
just
one
helm,
repo
for
the
whole
cluster,
and
now
you
can
do
multiple
helm,
repos
and
do
kind
of
a
multi-tenant
have
one
group
of
developers
that
are
using
a
particular
batch
of
helm
solutions
and
then
a
different
group.
That's
all
sharing
the
same
cluster,
so
you
don't
have
situations
where
every
developer
is
admin
on
their
own
cluster
and
then
you're
not
quite
sure
how
permissions
are
going
to
work.
C
G
Yeah,
what
about
the
github's
approach
right,
I
was
thinking
before
in
the
previous
show,
so
isn't
that
similar
to
git
flow?
If
you
recall
git
flow
right,
it's
a
methodology
of
developing
software
where
you
have
a
feature
branch
and
then
you
change
the
brain.
You
go,
you
do
the
hotfix
or
or
you
wrong
back.
G
You
go
in
the
master
branch
when
our
main
branch,
if
you
want
to
deploy
to
prod,
so
I
was
wondering
if
that
fits
also
the
the
this
new
key
tops,
because
the
key
tops
is
for
deploying
apps,
but
also
keeping
a
manifest
for
the
infrastructure.
So
can
we
kind
of
use
git
flow
in
githubs?
What
was
thinking,
what
do
you
think
about
it
and
if
you
ever
use
git
flow,
do
you
think
that
would
be
visible
here.
A
I
mean
it's
been
a
long
time
since
I
used
git
flow
but
like
git
flow.
I
believe,
if
I
remember
correctly,
is
the
process
through
which
things
get
committed.
That
would
then
spin
up.
You
know
an
argo
cd
instance
to
say:
go
reconcile
all
those
changes
against
a
cluster.
I
believe
they
can
work
in
tandem,
they're,
not
exclusive
right.
G
Yeah,
it's
kind
of
they
can
work
in
together
either
for
the
app
and
then
for
the
manifest
controlled
by
by
hit
up
so
by
argo.
In
this
case,
so
the
feature
branch
can
be
a
branch
where
you
can
create
a
feature
namespace
where
you
can
try
the
things
and
and
then
roll
back
roll
forward.
I
don't
know,
was
a
kind
of
idea.
I
was
thinking
if
those
two
words
can
talk
each
other
from
the
past
experience
with
git
flow
for
developing
gaps.
C
Perhaps
phased
roll
outs,
and
I
don't
know
whether
it
should
talk
to
helm,
charts
and
do
a
helm
chart
rollout
or
whether
I
should
be
using
k
native
services
to
do
a
rollout
or
whether
I
should
be
using
service
mesh
to
do
to
shape
traffic
around
and
achieve
a
rollout
right.
There's
multiple
different
ways
to
approach
the
solution
there
so
and
hard
to
know
what
people
are
going
to
expect.
A
Right
and
always
the
the
answer
is
use
the
method
that
works
best
for
you
right,
like
you
and
your
org
right,
you
have
to
come
to
a
consensus
there
around
methodologies
and
it
could
be
that
you
know
you
decide
to
go
with
git
flow
and
tecton,
and
you
know,
or
pipelines
and
off
you
go
and
that's
a
viable
solution.
You
know
there's
nothing
wrong
with
that.
F
I
mean
yeah
like
what
kind
of
granularity
of
like
you
know,
levers
and
tweaks.
Do
you
need
like
do
you
need
the
ability
to
you
know
automatically
scale,
this
application
based
on
services
that
are
coming
in,
like
like
it's
going
to
be
up
to
what
level
of
you
know,
tweaks
that
you
need
for
that
application,
and
you
know
what
you
need
so
exactly
like
hard
to
exactly
say:
it
depends
on
the
application
right.
G
A
G
Yeah
good
point
will
yeah
yeah.
I
think
we
need
to
consider
also
this
well
coming
on
the
for
that
seven
experience,
I
think
maybe
brian
can
say
more
about
it.
I
think
they
experience
the
user
experience
across
several
less
and
eventing
improved
a
lot.
It's
very
easy
to
create
an
application,
serverless
app
connecting
to
a
kafka
stream
and
react
to
some
events.
F
Yeah
yeah
so
too.
Well,
I
guess
to
finish
the
the
first
question.
To
begin
with
two
of
my
favorite
features,
I
guess
I
didn't
mention
that
would
be
the
serverless
updates
that
we
have
on
building
out
the
whole
eventing
stream.
So
we
have
been
adding
this
into
the
openshift
developer
portion
of
the
web
console.
You
know
incrementally
right,
so
openshift
serverless
came
out
serving
the
aspect
of
scaling
up
an
application
and
handling
the
giving
you
an
automatic
route,
and
things
like
that.
F
That
aspect
came
ga
generally
available
in
openshift
before
the
eventing
aspect
of
serverless
or
k
native
came
out,
so
openshift
serverless
uses
k-native,
and
the
surveying
aspect
came
first,
because
you
need
to
run
your
application
and
be
able
to
scale
that,
and
we
made
it
easy
to
be
able
to
build
out
a
serving
service
in
the
openshift
web
console.
The
only
difference
that
you
do
when
you
deploy
an
application.
Is
you
click
a
little
radio
button
that
says
I
want
this
deployed
as
serverless,
instead
of
as
a
traditional
kubernetes
deployment?
F
Very
easy
right
like
that's
what
I
would
expect
you
know
if
I'm
looking
at
the
web
console.
It's
very
simple,
like
I
don't
even
have
to
think
about
it.
This
is
now
a
serverless
service
that
then
allows
me
to
use
this
service
as
something
that
auto
scales
and
whatnot,
but
it
also
allows
me
to
hook
up
to
events
so
serverless
eventing,
which
enables
event
driven
development,
which
I
think
is
insanely
interesting
and
that's
probably
my
favorite
aspect
of
everything
that
comes
with
openshift
and
openshift.
F
You
know
latest
update
and
whatnot,
so
we
will
be
able
to
connect
to
kafka
and
be
able
to
hook
up
and
see
messages
come
to
our
application
and
maybe
wake
that
application
up.
If
we
get
a
kafka
message,
do
some
stuff
and
then
it'll
go
back
to
sleep
and
use
no
resources
right
so
like
eventing
event,
driven
development
enables
that
type
of
flow,
and
I
think
that
that
is
probably
the
most
interesting
aspect.
E
F
Other
thing
that
I
think
also
is
interesting,
which
I
know
we
talked
about
earlier.
Well,
we
didn't
talk
about
it,
but
in
the
stream
earlier
was
the
openshift
service
mesh
2.0
like
that
came
out
around
4.7.
It's
been,
there's
been
a
couple
updates
and
stuff
since
then,
but
they
changed
some
of
the
architecture
of
istio
and
made
it
a
little
bit
different.
F
Instead
of
going
from
microservices
and
split
up,
it's
all
together
and
one
more
monolith,
that's
easier
to
manage
for
these
particular
set
of
services
right,
so
they
went
a
little
too
far
and
they
kind
of
backed
it
down.
There's
also,
some
other
things
that
are
interesting.
Keoli
makes
it
easier
to
monitor
things
that
are
going
on
in
the
service
mesh
and
there's
a
lot
of
updates
there
that
make
it
easier.
Some
of
those
things
come
through
to
the
open
shelf
web
console
and
you
could
see
kind
of
hey
this
name.
F
Space
has
service
mesh
enabled
or
we
can
enable
it
easier
or
what
not
through
the
web
console
and
that's
included,
and
that's
pretty
awesome
and
interesting.
So
anyways
yeah
those
two
things
I
guess
would
be
my
main
event
driven
development.
It's
a
lot
easier
and
openshift.
Now,
instead
of
working
with
the
ammo,
I
could
work
with
that
web
console
and
then
yeah,
serverless
or
service
mesh.
Sorry,
the
updates
with
service
mesh.
D
Firefox
people
are
going
to
one
place
or
like
he
says
you
know
having
the
revisions
start
to
slowly
creep
in
and
you
see
like
you
jam
on
refresh
a
bunch
of
times
and
you
see
green
once
in
a
while,
and
then
you
just
kind
of
shift
the
ratios
and
all
of
a
sudden
that's
coming
through
a
lot
more.
It
makes
a
really
cool,
very
visual
demo,
not.
E
F
So
initially
it
was
handled
by
istio,
but
now
it
is.
It
starts
with
a
c
like,
but
I
can't
think
of
what
it
is.
Contour,
that's
what
it's
called
it's
contour,
okay,
so
it
still
uses
envoy
it's
istio's
using
envoy,
it's
just
a
more
simplified,
controlled
plane
and
yeah.
It's
using
cons
or
project
contour.
For
that.
A
D
You
create
a
new
one
of
those,
so
it's
a
yaml-based
resource
like
any
other,
and
that
contains
the
information
all
of
the
information
for
the
individual,
quickstart
so
being
able
to
just
write
that
yaml
file
get
it
deploy
and
then
your
quick
start
appears
in
there.
That's
actually
just
how
they're
written
in
the
first
place.
There's
no
fancy
thing
that
we're
doing
to
inject
the
quick
starts
above
and
beyond.
Just
writing
those
and
then
packaging
them
in
some
way.
D
The
other
thing
is
that
we're
still
we're
working,
in
particular
with
that
team,
to
enhance
it
going
forward.
So
what
you're
seeing
today
is
definitely
not
the
end
state
we're
looking
to
add
things
like
these
pre
and
post
steps.
So,
as
you
come
into
your
quick
start,
is
it
going
to
set
an
initial
state
on
top
of
your
cluster
or
something
like
that
grouping
mechanisms?
You'll
say
these
five
belong
to
a
particular
path,
or
something
like
that,
which
is
a
very
long
answer
to.
Can
you
write
your
own
yeah?
D
We
actually
expect
companies
and
users
are
going
to
say
hey.
This
is
training
material
or
for
our
new
employees,
or
this
is
the
kind
of
thing
you'd
want
to
use
to
bootstrap
a
project
or
something
like
that.
There's
a
number
of
reasons
why
companies
would
want
to
use
them
outside
of
what
we
would
do
from
a
teaching
and
advocacy
type
perspective
right.
Ryan
sandy
check
me
don't
speak
on
any
of
that.
C
No,
no,
that
sounds
totally
correct.
These
quick
starts
will
show
up
as
a
card
or
a
tile
in
the
open
shift
dashboard
when
you
go
to
create
new
content
and
if
you
were
as
a
organization
very
opinionated
on
how
people
should
do
their
rollouts,
whether
they
should
use
istio
or
not,
you
could
potentially
type
all
that
information
into
a
quick
start
and
then
tell
people
prescriptively,
here's
what
you
need
to
click
on
next.
C
You
could
even
highlight
different
ui
components
and
say
head
on
over
to
the
developer
perspective,
and
there
you'll
find
all
of
your
developer
folk.
You
know
kind
of
direct
them
down
a
guided
path.
So
yeah
quick
starts
are
a
new
feature,
great
opportunity
for
helping
encourage
folks
to
take
the
correct
next
steps.
Kubernetes
can
have
a
lot
of
terminology
and
a
lot
of
things
to
learn
so
helping
people
have
kind
of
guided.
Next
steps
is
potentially
a
huge
help
for
them.
F
So
the
quick
start,
or
can
only
be
it's
just
steps
of
how
to
do
something
and
then
the
person
has
to
go
through
and
you
know
go,
do
them
to
follow
the
thing
like
we
it
it
won't,
do
any
automation
or
whatnot
on
the
cluster.
So
if
you
want,
you
know
them
to
create
a
namespace
or
whatnot,
they
have
to
go
physically,
create
it
right.
D
Yeah
but
keep
in
mind,
though
there
are
ways
to
reference,
or
at
least
they're
coming,
there's
the
intention
of
having
it
be
able
to
flip
around
the
ui
for
you,
so
click
here
to
start
the
create
namespace
process
and
it'll
bring
you
into
that
ui.
This
is
the
intention,
I'm
not
quite
sure
whether
that
is
there
today
and
let
me
ask
the
follow-up
question.
We
hope
that
someday
we
see
quick
start
features,
as
catacota
has
funny.
D
D
I
don't
think
it
necessarily
needs
to
map
one
to
one
where
you
know.
I
I
think
one
of
the
most
dangerous
things
you
can
say
is
like
we've
always
done
it
this
way-
and
I
think
you
know
not
necessarily
saying
well,
this
exists
in
catacode.
It
needs
to
exist
in
quickstart,
but
us
being
able
to
come
in
and
say
hey.
D
These
are
the
types
of
things
we've
done,
and
these
are
the
types
of
problems
we've
had
to
solve
is
influencing
that
further
direction
so
non-committal
to
say
we're
not
going
to
see
the
exact
or
not
being
able
to
say
we're
going
to
see
the
exact
same
features
or
parody
or
anything
like
that.
But
the
intention
is
to
be
able
to
do
the
same
sorts
of
things
we
do
with
quickstart
in
terms
of
depth
in
terms
of
just
teachability
like
if
that's
what
we
do.
Is
this
advocacy
role.
F
A
C
Have
that
installed
on
any
cluster,
really
that's
going
to
be
available
as
part
of
the
getting
started
experience
on
code
ready
containers.
So
if
you
get
code,
ready,
containers
or
even
sandbox,
you
should
be
able
to
see
some
of
those
quick
start
tiles
that
red
hat
has
pre-populated
in
there,
but
yeah.
That's,
definitely
something
you
can
customize
and
give
specific,
getting
started
information
to
folks
in
your
users
of
your
clusters
for
sure.
A
And
there's
a
question
here:
I'm
asking
christian
in
our
slack
about
sss,
oauth
or
yeah
sso
auth.
I
don't
know
why
that's
so
hard
for
me
to
say,
but
it
is
so.
I
will
get
back
to
you
on
that
about
the
web
terminal
operator.
Is
there
a
per
developer
storage
solution
like
a
user
home
directory
allowing
each
dev
to
have
its
own
settings
command
history?
Whatever
it's
a
good
question.
C
C
A
A
G
C
C
Go
ahead,
learn.openshift
has
some
some
content.
There,
I've
updated
the
the
content
to
4.6
openshift4.6,
so
you
should
see
some
relatively
recent
pipelines
content.
If
you
find
books
on
techton
from
anyone
else
in
the
cloud
native
space,
it
ought
to
apply.
You'll
just
have
a
nicer
ui.
If
you
show
up
and
visit
the
openshift
console.
A
D
Cheat
sheets
will
be
on
developers.redhat.com
got
it.
I
don't
know
why.
I
said
that
so
like
without
making
it
a
sales
pitch.
So
the
cheat
sheet
sami
is
referring
to
developer.redhead.com
has
an
entire
section
of
cheat
sheets
scrolling
through
right
now,
there's
kubernetes.
I
know
I've
written
one
on
build,
there's
one
on
podman
that
I
I
don't
know
if
one
already
exists
today,
but
if
not
it's
definitely
something.
We
can
write
those.
D
B
E
B
So
so
thanks
everybody
for
joining
us.
I
posted
some
links
in
the
chat
because
we're
going
to
have
a
whole
bunch
more
office
hours
this
coupon
week
also
for
people
who
participated
in
the
session.
You
can
claim
your
openshift
for
sure,
and
so
I
pasted
that
link
in
there
and
thank
you
so
much
for
joining
us
and
answering
everybody's
open
shift
questions.
A
Yeah
been
really
great,
I'm
glad
to
have
this
one
like
in
the
can
ready
to
be
refreshed,
and
you
know
shared
with
everybody
at
any
given
moment
so
yeah.
This
is
already
available
on
youtube.
If
you're
not
aware
of
the
open
shift,
youtube
page
is
here,
let
me
type
in
the
archive
shortcut
and
that's.
You
can
literally
learn
everything
we've
done
for
the
past
year
and
one
day
live
streaming
from
that
link
right.
There
really.
A
Just
one
all
right
folks,
thank
you
so
much
audience.
Thank
you
so
much
for
attending.
Thank
you
everybody
here.
I
greatly
appreciate
all
of
you
and
we
are
going
to
sign
off
for
the
day
here
on
openshift
tv
and
josh
is
going
to
go,
take
a
nap
or
whatever
josh
does
take
it
easy
out.
There
stay
safe
and
we'll
see
you
tomorrow.