►
From YouTube: Developer Experience Office Hours: Deeper dive into the new Developer features in OpenShift 4.9
Description
Join OpenShift's Developer Experience experts for our regularly scheduled program filled with cloud native, Kubernetes, and OpenShift tips and tricks for developers.
Twitch: https://red.ht/twitch
#RedHat #OpenShift #Developers
A
A
A
A
Good
morning,
good
afternoon
good
evening
and
welcome
to
a
special
developer
experience
office
hour
here
on
red
hat
live
streaming,
I'm
joined
by
some
of
my
favorite
red
hatters
here,
especially
serena
from
the
future.
Who
is
here
to
talk
about
all
things
in
the
future,
so
I
will
remind
everybody,
I'm
chris
short,
a
host
of
red
hat
live
streaming,
and
this
show
talks
about
things
from
the
future.
So
if
you
try
to
do
this
on
your
cluster
now
and
you
call
support
for
help
could
be
a
problem.
A
B
Sure,
hey
everybody,
hope
everybody's
doing
well.
My
name
is
serena
nichols
coming
to
you
from
the
future
and
we're
going
to
be
talking
about
one
of
the
new
cool
features
which
will
be
available
in
49,
which
is
export
application
and
I'll
go
into
that
a
little
bit
more
after
we
have
a
couple
of
our
guests
introduce
themselves
so
I'll
pass
over
to
jay.
First.
C
D
As
you
can
see,
I
have
camera
issues
today,
so
bear
with
me
on
this
one
folks,
all
right,
but
very
happy
to
be
here,
as
you
can
tell,
I
found
a
camera
just
so
I
could
be
here,
so
I
am
going
to
be
showing
kind
of
what
how
to
export
applications.
This
was
something
that
was
really
interesting
to
me
because
I
love
the
whole
get
ops
approach
and
I
wanted
to
get
more
people
involved
with
it,
and
so
that's
why
you'll
see
what
you
do
today.
B
B
So
we
started
this
and,
like
ryan
mentioned
just
talking
about
collaboration
within
red
hat,
it's
pretty
cool.
We
started
talking
about
that.
We
need
this
type
of
feature
we
found
out
through
some
sources
that
somebody
in
his
cto
office
was
working
on
this
and
got
connected
with
ryan,
and
then
we've
got
our.
You
know,
ryan
connected
with
the
developer
console
group,
as
well
as
one
of
the
other
internal
teams
on
our
at
red
hat
and
have
been
able
to
produce
this
really
cool
feature.
B
I
also
did
want
to
talk
about
what
future
phases
of
this
might
lead
to
in
the
future
right,
so,
okay,
four,
nine
export
it
meaning
just
export
it
and
have
it
on
your
local
machine,
but
post
49
things
like
I
have
an
unmanaged
app,
which
is
not
yet
in
git
and
with
a
single
click,
I'm
able
to
export
and
push
it
to
my
git
repo,
which
would
be
super
cool
and
then
obviously
also
the
another
caveat
with
that
would
be.
We
don't
want
to
have
additional
off
needed
on
that
and
then
another
use
case
post.
B
That
would
be.
I
have
a
managed
app
which
is
running,
and
I
want
to
easily
disable
the
sync
and
be
able
to
modify
that
application
and
then
re-export
it
push
it
to
get
and
then
re-enable
the
sync.
So
how
do
we
interact
with
git
ops
in
the
future
right
and
how
we
fulfill
those
use
cases,
so
those
are
kind
of
where
we
think
this
this
feature
will
lead
us
to
in
the
future
future,
and
with
that
I
think
I'll
pass
it
over
to
ryan.
D
D
D
D
So
what
that's
going
to
do
is
it's
going
to
create
a
service
account
cluster
role,
cluster
role,
binding
job
and
pvc
and
you're
thinking
yourself.
There's
a
lot
of
objects
just
to
start
the
process
to
export,
but
we're
doing
this
with
the
concept
of
trying
to
keep
the
least
privileges,
and
so
what
we're
actually
doing
there.
This
time,
when
you
issue
the
export,
it's
going
to
read
what
your
username
is
at
the
time.
D
So
that
way,
it's
going
to
only
pull
the
objects
that
you're
allowed
to
see.
So
it's
going
to
create
a
cluster
role
based
on
your
user
account
and
assign
it
to
that
service
account.
The
job
is
then
going
to
use
that
service
account
and
only
allow
you
to
pull
things
that
you
have
access
to.
So
it
kind
of
gives
us
the
least
privileges
required
to
get
what
you
need
done
and
it
makes
it
so
you're
not
able
to
pull
secrets
or
anything
that
you're
not
actually
supposed
to
have
so
from
there.
D
You'll
see
that
that
cluster
and
across
the
rule,
binding
and
job
go
away.
When
the
job
reaches
success,
you
no
longer
need
that
privilege,
cluster
role
in
role
binding
and
so
that
service
account
transfers
over
to
a
deployment
and
that
pvc
is
used
again
and
a
service
and
router
created,
which
is
really
cool,
and
it
just
allows
you
to
one
click
download
your
whole
objects
that
we
extracted
from
the
environment.
D
So
the
tooling
itself,
as
you
hear
see
here,
that
the
upstream
repository
is
github's
primer
and
within
that
kubernetes.
Well,
the
openshift
kubernetes
job
that
runs
we're
using
crane
to
extract
the
objects
and
we're
using
crane
lib,
because
what
we
have
to
do
is
with
those
objects
once
they're
exported
they're
kind
of
ugly
like
they
have
fields
that
we
don't
want,
they
have
like
uid.
They
have
like
a
date
just
various
things
that
we
don't
really
want
to
transfer.
D
You
know
out
and
keep
so.
The
crane
lib
library
allows
us
to
manipulate
that
data
to
have
it
in
a
usable
format
that
we
could
take
to
another
cluster.
We
could
store
and
get
and
further
down
the
line
when
you
use
get
github's,
tooling,
they're,
not
fields
that
the
tool
is
going
to
obsess
over
you
know,
since
we
fixed
and
removed
you
know
certain
fields,
then
the
tooling
doesn't
see
that
that
needs
resolved.
C
C
C
So
you
can
see
option
like
export
application,
so
this
button
will
be
shown
only
if
the
operator
primer
operator
will
be
installed
which
will
be
available
in
the
operator
house
in
4.9.
So
once
you
have
installed
the
primer
operator,
you
will
see
an
option
for
export
application
if
user
have
access
create
access
in
this
namespace.
C
C
So
once
the
job
work
is
completed,
it
will
create
a
deployment
out
of
it
and
java
will
be
deleted.
So
let
me
go
back
to
topology
and
let's
try
to
visualize
this
whole
process.
So,
as
you
can
see,
job
is
up
and
running.
It
will
take
a
while
for
it
to
get
completed
and
if
you
try
to
click-
oh
it's
done
so
that
was
super
quick
for
this
particular
application.
C
C
You
should
be
seeing
press
three
and
you
have
the
all
the
required
resources
yaml
over
here,
like
image
stream
deployment
routes,
service,
etc.
Whatever
was
there
in
this
particular
name
space.
So
with
this
we
can
use
it
in
different
phases
with
get
ops
the
whole
flow
as
part
of
this
flow.
We
had
this
particular
piece
to
demonstrate
and
there
are
few
more
things
which
I
would
like
to
highlight
like
this
can
be
extracted
or
this
process
can
be
initiated
only
from
topology.
C
Now
the
topology
can
be
seen
in
the
dev
perspective
and
even
on
the
admin
perspective.
If
you
go
to
name
spaces
under
workloads,
you
should
be
able
to
see
the
same
option
again
over
here.
Export
application,
which
can
be
achieved,
and
another
thing
is
like
if
you
are
into
a
namespace
which
doesn't
have
any
workload
in
this
particular
case,
user
will
be
shown
with
export
application.
C
C
If
you
try
to
trigger
the
thing
that
is,
the
process
will
again
be
trigger
and
it
will
try
to
create
a
job
again
and
it
just
tries
to
export
again
with
whatever
state
it
is
in,
but
there
is
always
a
way
to
cancel
the
export
or
restart
it.
If
you
are
not
happy
with
that
reporting
progress
that
will
again
help
you
with
these
things
and.
C
B
C
C
So
these
are
the
scenarios
where
cancel
and
it's
report
can
be
useful
and,
as
you
can
see
again,
the
export
has
happened,
and
I
have
my
download
link
up
and
you
and
one
important
thing
you
don't
need
to
be
in
topology.
You
can
go
wherever
you
want
and
this
toast
will
also
be
sewn.
Even
if
you
close
your
browser
and
come
back
again
after
half
an
hour,
a
coffee
break
you'll
still
find
a
toast
over
there.
C
B
And
I
think
your
your
initial
export
went
very,
very
quick.
We
have
ryan.
I
know
that
we're
at
both
of
you.
I
know
you
guys
have
done
some
testing
before
when,
in
other
instances
etc,
and
as
far
as
like
how
long
that
process
might
take,
I'm
assuming
I
just
want
to
make
sure
that
we
allow
the
users
to
know
that
not
every
time
that
you
do
an
export,
it
will
take
within
30
seconds.
D
D
Do
I
have
access
to
ask
if
you
have
anything
for
me,
so
the
kind
of
the
nice
part
about
that
is
it's
two-sided
that
it
makes
it
kind
of
fast
that
if
I
don't
have
access
to
it,
it's
going
to
immediately
kick
me
down
to
the
next
step,
and
so
you
know
it's
really
dependent
on
how
much
you
have
in
there
as
well.
As
do
I
actually
have
access
to
this
whole
barrage
of
api
resources.
D
D
One
thing
that
I
wanted
to
kind
of
touch
on
as
well
is
that
the
oauth
that
we
showed
just
a
moment
ago
that
is
linked
to
your
namespace.
Only
so
if
you
are
a
member
of
another
namespace
and
you
don't
have
actually
access
to
this
test
project,
you're
not
going
to
get
in
you're
not
going
to
have
the
ability
to
get
in
and
that's
how
we're
kind
of
kind
of
stopping
people
from
accessing
it.
D
D
C
And
the
thing
was
trying
to
say
earlier
what
will
happen
once
we
have
our
export
there?
So
currently
we
have
downloaded
it,
so
there
will
be
different
phases
on
this.
This
whole
lifecycle
will
be
connected.
So
currently
we
are
doing
the
export.
The
next
thing
comes
is
the
import
flow,
so
this
download
can
directly
be
going
to
a
git
repo
in
future.
Once
we
have
the
github
cycle
in
place
to
handle
all
of
those
things
so
currently
few
things
you
have
to
do
manually,
yeah.
A
C
D
D
The
the
nice
thing
is
in
the
event
that
you
need
to
go
back.
We
have
the
ability
to
actually
tag
these
zip
files,
as
you
kind
of
see
down
in
the
bottom
left,
they're
tagged
by
month,
date
or
month,
day
a
year
and
then
hour
and
minute.
So
if
you
remember
to
click
the
export
button
frequently
while
you're
testing,
you
will
always
have
kind
of
a
point
in
time
to
to
make
your
way
back
to
that's.
C
D
So
why
don't
wait
for
simplicity
purpose?
Why
don't
we
just
go
into
the
openshift
console
and
delete
the
deployment?
The
only
reason
why
I'm
saying
that
is
because
the
image
backing
is
saved
in
the
registry
under
the
namespace
test,
I
believe
so.
If
we
were
true
try
to
bring
this
in,
we
would
have
to
to
rebuild
and
all
of
that,
okay.
C
D
D
The
only
thing
that
might
not
be
there
that
a
user
may
want
there
may
be
some,
I
guess
I'll
call
it
crud
fields
that
they
might
not
want
to
store
in
a
gear
posture
account,
like
I
said
earlier.
If
a
uad
is
not
scrubbed
out
of
a
field
by
the
crane
library,
that
would
be
the
only
thing,
but
anything
that
is
within
a
namespace
jay.
D
D
D
So,
for
example,
we
don't
really
want
to
record
the
pods
themselves
because
they're
part
of
deployments,
so
we
just
go
ahead
and
wipe
those
out
and
then
that
way,
when
you,
when
you
pull
out
the
download,
it's
not
actually
saved
but
serena.
Yes
from
your
original
question,
anything
that
is
in
the
name.
Space
is
pulled
down.
B
D
B
B
B
A
C
A
A
D
C
Sorry
so
yeah
I
mean
how
I
see
as
a
developer
myself
that
what,
in
what
scenario
could
be
useful
for
me
when
I
have
worked
on
something
or
created
lot
of
workloads
or
use
cases
depending
on
sbr
or
managed
services
or
serverless,
for
instance?
So
it
will
be
quick
export
for
me
to
take
you
to
another
cluster
or
maybe
sharing
with
some
of
my
colleagues
who
have
access
to
the
same
name
space
or
want
to
recreate
that
so
as
a
developer.
I
could
even
find
this
useful
when
we're
working
on
some
issues.
C
Yeah
a
customer
found
some
issue
in
some
particular
name
space
and
they
can
just
save
the
export
without
secrets.
I
mean
the
thing,
but
we
need
to
recreate
the
issue.
So
that's
another
use
case
of
it,
which
I
think,
which
will
be
very
useful,
but
that's
not
the
important
one
important
one
is
able
to
manage
your
unmanaged
state
which
serena
told
in
the
beginning.
D
You
can
then
press
the
the
button
export
your
stuff
and
then
bring
it
on
to
a
real
cluster,
and
so
you
know,
I
think,
kind
of
the
portability
as
well
as
kind
of
giving
the
developer
space
to
work
and
then
know
that
they're
going
to
extract
everything
that
they
need
and
have
a
successful
running
application.
After
the
fact.
I
think
it's
definitely
something
that's
useful
for
them.
A
A
Hey
check
this
out
right
like
and
hand
it
over
to
somebody
else,
so
they
can
test
it
in
their
cluster
and
add
on
to
it
and
then
export
it,
and
then
you
know
save
it.
You
know
upstream
in
their
repos
and
then
deploy
it.
However,
they
see
that
could
be
a
very
handy.
I
don't
know
what
do
you
call
that
outer
loop,
serene
right
inner
outer
both.
E
B
A
D
D
You
know
very
minimal
things
are
being
scrubbed
and
you
can
actually
see
those
within
their
repository
under
plug-ins,
but
yeah.
Just
very
minimal
things,
and
the
nice
thing
about
this
is
too
is
that
we
want
to
get
to
the
point
in
the
future
that
between
the
confederate
crane
group
and
us
we're
sharing
plug-ins
back
and
forth
to
just
kind
of
provide
a
user
experience
for
upstream
and
for
openshift
experience
as
well.