►
Description
Last time we sat down to explore the Red Hat OpenShift Developer Sandbox with CodeReady Workspaces, and things didn't quite go as planned. But who really wants to turn a project on and have it work perfectly the first time? In this episode, let's take another run at the Developer Sandbox and get those Workspaces doing what we want. Join us as we take a look at what went wrong, how we can fix it, and we should now be able to get the Cool Store working.
Learn more at https://red.ht/leveluphour
A
B
A
Really
quick,
you
know
we
can't
fail
on
this
show
ever
right,
except
we
cannot
have
any
mistake:
no
mistakes,
no
mistakes,
so
yeah.
That's
kind
of
the
topic
of
the
show
this
morning
right
like
right
right,
we
kind
of
basically
the
last
stream
that
we
did
two
weeks
ago
was.
If
you
watch
american
football
was
the
equivalent
of
watching
both
football
teams
fumble
the
football
all
the
way
down
the
field.
A
B
Exactly
so,
first
and
foremost,
maya
culpa,
we
had
a
scheduling
snafu,
so
we
were
supposed
to
be
doing
podman
b3
today,
but
our
special
guest
stars
couldn't
make
it
today
at
kind
of
at
the
last
minute.
So
we
had
to
reschedule
so
you
should
have
seen
it
on
the
twitters
that
that
it
changed
around
a
little
bit,
however
yeah
or
the
calendar,
but
we
will
be
having
them
next
time.
So
we
will.
We
are
still
planning
on
doing
that
episode.
A
So
familiar,
if
you
want
to
talk
through
it,
you
can
go
ahead,
no
go
ahead.
If
you're
not
familiar,
you
know
every
show
we
have
a
topic,
but
you're
more
than
welcome
to
ask
any
kind
of
question
related
to
containers.
You
know
venus,
you
know
former
sysadmin
now
working
in
openshift
and
kubernetes
land.
You
know.
I
understand
that
that
transition
is
not
exactly
smooth.
Sometimes
right,
like
containers
are
kind
of
hard
to
conceptualize
at
first
and
then
orchestrating
them
is
even
more
difficult
at
times.
A
B
I
will
say,
like
my
big
thing,
is
and
a
little
bit
more
than
that
in
that,
hopefully,
to
convince
you
why
containers
will
make
your
life
better.
It's
not
just
another
technology.
You
have
to
learn
and
get
under
your
belt,
because
that's
the
way
the
industry
is
moving,
which
is
true,
but
also
that
they're
super
handy
and
that,
hopefully
you
will
find
that
to
be
a
positive
experience,
so
level
of
power,
and
so
I
have
my
handy
links,
which
you
know.
B
B
A
A
B
Exactly
you
know,
it'll
have
little
to
do
with
english
or
anything
like
that,
but
you
can
also
join
us
on
our
discord
and
that
I
think,
is
already
landed
in
the
restroom
or
in
the
chat
so
join
us.
There
there's
often
discussions.
You
know,
don't
limit
yourself
to
any
particular
channel
feel
free
to
say
stuff.
You
know
the
live
stream
channel,
obviously
is
live
streaming.
So
if.
A
B
B
One
of
my
colleagues
is
actually
who's
actually
sometimes
on
the
here
on
the
show
christian
is
unhappy
with
exactly
how
it
works
so
he's
making
some
changes,
hopefully
to
improve
it.
So
if
you
are
interested
in
you
know,
or
if
you're
using
that
or
use
blender
or
whatever
you
might
want
to
take
a
look,
we
are.
I
will
take
a
look
at
his
pull
request
imminently
and
then
we
can.
You
can
see
the
merge,
assuming
it's
a
good
one,
so
yeah.
A
B
A
B
B
Not,
but
basically
you
know
putting
a
quasi.
I
I
personally,
I
think,
putting
a
quasi-arbitrary
limit
on.
It
is
just
primarily
going
after
bad
actors.
Not
you
know
it's.
The
intent
is
not
to
tell
you
that
you
shouldn't
use
it
longer
than
30
days
and
specifically
the
reason
I'm
I'm
commenting
on
this
is
because,
in
whatever
it
was
that
I
was
watching
somebody
commented.
Is
that
enough
time
to
learn,
you
know,
did
you
open
shift
or
code
ready,
workspaces
or
whatever
I
don't
know?
B
A
B
A
B
B
All
right
so
a
few
things
that
I
learned
since
last
time
as
well,
as
you
know,
kind
of
doing
some
experimentation
yeah
some
more
thoughts,
whatever
let's
discuss
this
so
first
and
foremost.
Actually,
let
me
close
these
so
that
it's
less
likely
to
be
angry
with
me.
I
tend
to
have
a
lot
of
windows
open.
I
don't
know
if
you've
noticed.
A
B
Right
here
I
can
see
never
mind
one
thing:
gnome
did
a
few
years
ago,
which
is
basically
take
the
ability
of
putting
you
know
like
icons
on
your
desktop,
like
putting
you
know,
saves
or
whatever
you
can
still
turn
it
off
like.
You
can
still
do
it,
but
it
has
made
me
a
much
cleaner
person.
I
will
say
you
know
as
far.
B
Better
more
likely
to
take
notes
all
right
so
back
to
dev
sandbox,
so
you
get
into
sandbox.
By
going
to
developers.redhat.com,
you
sign
up
for
an
account,
then
you
click
the
big
button
that
says
developer
sandbox
and
it
launches
this
site.
If
you're
lucky,
the
sso
will
be
ssoe
and
you
will
just
get
logged
in.
A
A
Speaking
of
sres
meeting
with
someone
on
the
openshift
dedicated
team
yesterday
about
the
nsre
show
oh
the
channel,
so
that
is
in
the
works.
No
promises,
no
it's
future
stuff,
but
it's
in
the
works
and
we're
probably
gonna
have
some
sres
on
the
channel
talking
about
not
just
openshift,
of
course,
but
how
and
why
they
built
srs.
B
The
way
they
did
yeah
yeah-
I
I
will
say
it's
really:
it's
an
interesting
phenomenon
like
if
you,
if
you
haven't,
read
the
book
that
kind
of
started
it
all
from
it's.
Some
people
at
google
called
site
reliability,
engineering,
it's
a
quick,
read,
take
a
look,
also
the
phoenix
project
about
devops.
You
know
if
you
kind
of
read
both
of
those.
I
think
you
get
a
really
interesting
sense
of
the
change
in
the
philosophy
of
how
software
is
delivered.
A
B
B
And
facebook
and
a
bunch
of
those
other
companies
as
unicorns
a
lot-
I
don't
you
know,
there's
probably
some
underhanded
nastiness
to
that.
But
really
you
know
the
the
core
of
it
is
true,
which
is
that
they
are
really
unique,
but
that
doesn't
mean
we
can't
learn
from
them.
You
know,
and
so
yeah
so
yeah.
B
As
you
say,
remember:
you're,
not
google,
but
the
real
point
I
was
trying
to
get
to
there,
even
though
I'm
kind
of
long-winded
sometimes
is
I'm
shocked
by
the
amount
of
interest
amongst,
because
I
teach
a
course
over
at
a
university.
The
amount
of
interest
among
the
students
about
growing
up
to
be
an
sre,
which
I
think
is
really
interesting.
You
know,
and
so
actually
one
of
my
classes,
I'm
gonna,
have
a
guest
lecture
come
in
to
talk
about
what
it
means
to
be
an
asshari.
So
I.
B
Okay,
so
back
to
dev
sandbox,
it's
a
developer,
sandbox.
So,
first
and
foremost,
I
was
very
confused
by
okay.
So
when
you
work
with
openshift
there's
this
concept
of
projects,
alternately
called
namespaces,
where
basically
that's
kind
of
where
all
your
code
lives
for
a
given
that
the
the
word
is
so
hard
these
days,
but
so,
let's
say
given
application,
even
though
an
application
may
be
made
up
of
a
number
of
applications.
B
So
when
we
talk
about
like
the
cool
store,
for
example,
it's
actually
made
up
of
a
bunch
of
different
services
right.
It
has
a
web
front
end.
It
has
a
catalog
component.
It
has
an
inventory
component.
All
those
things
combine
to
build
an
application
so
as
a
way
to
to
corral
those
things
into
one
thing:
we
have
this
concept
of
a
namespace
or
a
project.
B
B
That's
actually
not,
I
mean
you
could
use
it,
but
it's
not
meant
to
be
used
and
that's
why.
I
don't
know
if
you
remember
from
the
last
episode,
but
I
was
surprised
because
when
I
came
into
it,
I
landed
in
langdon
dev,
because
I've
worked
with
some
organizations
where
they
called
the
unit
test
level
deployment
code,
and
so
I
assumed
that
it
was
essentially
unit
test
level
deployment.
B
B
You
should
see
you'll
see
it
land,
so
I
just
started
my
code
ready
workspace
and
look
at
that.
It's
coming
up
as
a
you
know,
a
thing
right
in
langdon
code
in
that
project
and
it's
not
something
I'm
going
to
mess
with
unless
I
get
really
excited
about
how
workspace
works
and
want
to
go
dig
around
in
it.
For
some
reason,
so
is
this.
B
Yeah,
I
think
I
I
don't
know
if
it's
for
this
show,
but
I
think
for
a
show.
It
might
be
interesting
to
talk
about
how
workspaces
works
as
an
application
on
openshift
and
I
and
to
be
clear
right,
there's
no
particular
particular
affinity
for
your
workspace
back
end
or
whatever
to
live
in
something
called
dash
code.
It's
just
this
is
how
dev
sandbox
was
set
up
and
part
of
why
I
got
confused
is
because
other
setups
I've
seen
it's
been
in
other
projects.
A
B
Yeah
so,
first
and
foremost
ignore
this
thing
that
I
have
just
spent
so
much
time
talking
about
so
your
stuff
should
go
in
dash
dev,
and
this
is
where
we
get
into
kind
of
more
traditional
deployment.
You
know
stories
or
whatever,
where
dev
is
kind
of
where
you
play
around
with
stuff
and
then
whatever
we
call
it
here
stage
stage
is
where
you
know
you
stage
it
right,
and
you
know
because
it's
beta,
because
it's
a
demo
all
that
stuff.
B
B
The
idea
here
is
stage
and
the
reason
we
have
at
least
two
is
because
one
of
the
things
that
you
should
be
or
might
want
to
be
experimenting
with,
is
the
transition
from
one
project
to
another
or
one.
Even
you
know,
obviously
not
in
this
scenario.
But
you
know,
one
of
the
things
you
want
to
be
thinking
about
is
how
you're
transitioning
your
applications
from
one
environment
to
another
environment,
be
it
on
the
same
cluster,
on
different
clusters,
etc.
B
So
that's
why-
or
at
least
you
know,
that's
why
these
two
different
projects
are
included,
not
so
much
the
idea
being
that
you
would
be
running
multiple
and
again,
I
struggle
with
the
word
application.
So
you
know
you
don't
want
to
be.
It
would
be
surprising
for
you
to
run.
You
know
the
cool
store,
and
you
know
your
what's
the
most
popular
software,
these
days
like
to
do
system,
you
know
like
like
the
idea
with
openshift
is
with
sandbox
right.
B
Is
that
you're
going
to
work
on
kind
of
one
application
here,
even
if
it's
made
up
of
37
different
services,
so
it's
kind
of
set
up
for
that
kind
of
scenario
doesn't
mean
you
can't
do
something
else,
I'm
just
saying
that
that's
like
the
philosophy
behind
it.
As
I've
often
said
on
the
show,
if
you
understand
the
philosophy
behind
software,
it
makes
it
much
easier
in
my
experience
makes
it
much
easier
to
grok.
B
You
know
your
choices
or
guess
what
what
to
do
next.
So
again,
relatively
long-winded
way
of
saying
these
are
what
these
projects
are
for,
and
so
you
know
play
around
with
it,
knowing
that
and
things
will
go
better
for
you
all
right
so
moving
on
from
there.
What
I
first
wanted
to
show
here
or
next
one
in
the
show,
I'm
going
to
actually
go
and
do
this
in
stage,
because
I
don't
have
anything
there,
as
I
just
got
done,
saying
yeah.
B
If
you
really
are
just
wanting
to
try
stuff
out-
and
you
want
to
just
play
around
a
little
bit,
you
know
pick
your
favorite
language
do
a
sample
and
you
will
get
your
application
deployed.
I
strongly
recommend
and
we've
talked
about.
I
think
we've
talked
about
this
on
the
show
there
it
is,
you
know,
go
watch
the
logs
go,
see
what's
actually
happening.
B
B
So
this
is
engaging
with
the
red
hat
catalog.
You
have
to
have
a
secret.
If
you
want
something,
that's
privileged
so
check
out
those
logs,
you
know
get
an
idea
of
what's
actually
happening.
You
know
so
there's
a
bunch
of
you
know
stuff
about
the
setup
and
the
python
thing
we're
not
really
gonna
go
through
it
too
deeply
today,
but,
as
you
can
see,
you
know
we
get
this
nice
sample.
It
has
come
up.
B
A
B
All
right,
so
so,
okay,
so
in
order
to
access
like
an
application
inside
of
openshift,
you
need
some
sort
of
what
you
know.
The
fancy
term
is
some
sort
of
ingress
into
open
shift
and
in
order
to
get
that
what
we
create
is
called
a
route.
Now,
when
I
created
that
sample
application,
it
included
a
bunch
of
nice
things
right,
it
included
the
obvious
code
bits
which
is
what
this
build
part
is
right.
B
This
is
one
of
the
things
that
I
most
appreciate
actually
about.
Kubernetes
and
openshift
is
that
by
almost
by
default,
the
expectation
is
that
you
put
a
layer
of
indirection
between
your
application
and
the
url
you
use
to
get
to
it.
Why
is
this
so
important
because
applications
change
and
when
applications
change
you
want
to
do
things
like
you
know,
have
some
of
your
sorry,
some
of
your
visitors,
continuing
to
hit
your
old
one
while
you
deploy
your
new
one
and
new
visitors
start
hitting
the
new
one
things
like
that.
B
So
there
are
lots
and
lots
of
scenarios
where,
having
that
layer
of
interaction
between
the
url
and
the
actual
application
is
a
lifesaver,
and
so
the
default
coming
up
with
that
layer
of
indirection,
even
though
to
a
lot
of
people,
I
think
the
reason
they
shy
away
from
it
is
they
feel
like
it's
over
engineering,
and
this
is
one
of
those
places
where
I
you
know.
While
I
tend
to
over
engineer,
I
strongly
recommend
you
know
kind
of
that
layer
of
indirection.
B
B
A
B
Okay,
so
that's
my
little
python
sample
application.
I
am
actually
just
gonna
delete
it
and
one
of
the
things.
This
is
something
that
I'm
trying
to
figure
out
how
to
file
a
bug
about
this,
because
I'm
not
sure
what
exactly
I'm
trying
to
say,
but
when
I
click
this
delete
here,
I
expect
to
immediately
be
able
to
go
and
create
the
thing
again
and
you
can't
a
lot
of
the
time.
So
when
I
delete
it,
what
I
want
to
do
is
then,
okay,
so
it's
deleting
it's
doing
its
little
cooking.
B
I
go
and
look
at
the
project
and
notice
a
couple
of
things.
For
example,
hey
look,
my
service
is
still
there,
so
arguably
my
service
is
still
there
and
you
know-
and
so
now
I
could
put
some
other
thing
behind
it.
I
could
keep
that
old
route
right,
because
I
think
the
route
was
there
too.
I
could
keep
the
old
route
and
the
service
and
put
something
else
behind
that.
So
there's
a
really
strong,
positive
argument
for
for
being
able
to
do
that.
B
The
thing
is,
if
I
go
into
the
topology
view
and
right
click
delete.
My
expectation,
I
think,
is
that
all
that
stuff
is
blown
away
and
that
I
can
immediately
like
recreate
it.
So
I
I
wonder
if
almost
we
need
another
option
in
the
menu.
That
is
something
like
really
really
destroy
it
right
versus
you
know
mostly
destroy
it.
A
B
So,
in
order
to
get
this
back
to
square
one
so
that
I
can
redeploy
that
same
python
sample
app,
I
need
to
actually
manually
remove
both
the
route
the
sample
and
then
I
think,
an
image
stream.
And
what
particularly
annoys
me
about
image
streams
is
that
they,
you
have
to
go
to
the
administrator
view
and
then
go
to
builds
and
then
image
streams
and
then
delete
it
here.
B
A
A
B
B
B
You
know
burning
down
the
box
right,
it's
kind
of
like
if
I
get
a
virtual
machine
in
my
enterprise
or
whatever,
as
a
junior
developer,
I'm
not
gonna
ever
delete
the
virtual
machine
right,
I'm
gonna,
I'm
gonna
keep
using
it.
I'm
gonna
keep
trying
to
fix
whatever's
wrong
with
it.
I
don't
know,
maybe
I'm
crazy,
okay,
so
going
back
a
little
bit,
so
I
flip
back
over
to
the
dev
one
just
because
I
I
put
a
couple
projects
in
here.
So
a
few
you
know
for
a
few
episodes.
B
A
B
A
B
B
Right
right,
so
all
right,
so
what
I
want
to
show
here
is
okay,
so
I
know
it's
cut
off
because
of
poor
naming
on
my
part,
but
so
I
was
because
I
was
experimenting.
I
gave
it
the
brilliant
name
of
exp
for
experimental
catalog
go,
and
so
that's
this
directory
here,
this
experimental,
and
so
this
is
a
go
application
that
oh,
we
do
have
a
corkus
app,
so
I
can
show
you
how
fast
it
is.
B
A
A
B
B
B
B
B
B
B
B
A
B
A
B
A
B
A
B
There
we
go
okay,
so
the
reason
I
was
commenting
on
it
primarily
is
because
if
I
do
remote
minus
v,
I
would
like
to
be
able
to
just
drop
this
in
there
right.
I
don't
you
know,
and
it's
easily
translatable
from
that
to
be
an
https
url,
because
then
I
don't
have
to
go
open
up
a
web
browser
and
go
find
out
what
the
hps
url
is,
because
I
have
no
idea
you
know.
B
Maybe
I
don't
maybe
there's
a
way
and
get
that
you
can
actually
tell
it
to
give
me
the
other
url,
but
that's
why
I
think
it'd
be
kind
of
nice
if
you
could
just
drop
an
ssh
one
in
there,
all
right
so
continuing
on
okay,
so
it
smartly
detected
that
this
is
a
go
project.
It
said:
okay,
I'm
gonna,
plop
that
on
top
of
this
version
of
go,
I
have
some
other
options,
but
I'm
going
to
take
the
one
eight
guest.
B
B
B
B
B
B
A
B
B
A
Can
also
think
I'm
crazy
when
it
comes
to
these
dev
sandboxes
right
since
they
are
in
beta
right
now,
I'm
not
like.
I
need
to
put
this
lightly
because
I
don't
want
to
insult
anybody
right
like
I'm,
not
expecting
full
perfectionality
and
perfection
right
now,
right,
like
I'm,
I'm
I'm
hoping
for
pods
to
come
up
deployments
to
work,
those
basic
core
kubernetes
services
or.
A
B
B
And
I
found
actually
a
cool
script
that
will
convert
your
bash
aliases
to
fish
functions.
Fitch
commands.
I
can't
remember
what
it's
called
and
put
them
in
the
right
place,
because
they
go
in
this
like
config
directory
and
all
this
stuff,
and
so
most
of
them
work.
But
there
are
some
of
them
that
I
need
to
go
figure
out
how
they
work,
but
yeah,
so
I've
been
slowly
trying
it
out.
I
just
haven't.
B
B
I
am
personally
deeply
offended.
I
do
know
that
both
service
mesh
and
serverless
are
very
high
on
the
list
for
things
that
should
land
or
that
we
want
to
land
really
soon.
That
said,
though,
if
you
go
to
learn.openshift
right,
that's
the
one
with
all
the
demos
you
can
go
and
experiment
with
serverless
in
there
directly,
because
those
like
the
the
setups
for
those
workshops
are
are
set
up
to
use.
Serverless
et
cetera,
so
you
can
play
with
it.
B
B
Okay,
so
this
so
this
is
where
I
was
struggling
with
the
dev
sandbox
kind
of
setup
versus
openshift
setup.
So
the
problem
here
is
that
this
application
is
set
up
to
be
pushed
into
open
shift,
not
kind
of
read
by
openshift,
and
this
is
a
thing
that
we
would
like
to
or
like.
I
would
like
to
kind
of
see
how
to
fix
it.
I'm
not
sure
if
the
problem
is
in
the
code
base
for
the
catalog
go
here
or
if
the
problem
is
kind
of
like
how
openshift
approaches
it.
B
B
I'm
afraid
this
is
actually
going
to
inject
code
yeah,
so
I
need
to
stop
this
one.
So
you
have
to
you
have
to
have
two
or
less
total
and
then
you
can
run
one
at
a
time
and
it's
pretty
easy
to
kind
of
go
back
and
forth.
It's
just
I'm
still
getting
used
to
what
the
numbers
are
now
did
we
have
good
comments
in
the
chat
while
I
was.
B
A
B
Well,
let's
say
user
installed,
operators
yeah
kind
of
in
any
way,
because
the
the
challenge
right
now
is
that,
for
at
least
this,
my
understanding
is
that
to
get
kind
of
a
user-scoped
operator
is
not
something
open
shift
does
very
well
at
this
point.
You
have
to
have
them
at
the
kind
of
cluster
level.
B
So
in
order
for
you
know,
openshift
like
the
dev
sandbox
to
be
able
to
offer
an
operator,
it
needs
to
be
able
to
install
at
the
user
level
rather
than
at
the
cluster
admin
level,
and
so
that's
what's
in
progress,
but
it's
a
problem
like
it's
not
just
a
problem
for
dev
sandbox,
so
it's
very
high
on
the
priority
list
like
this
is
something
we
really
want
to
see.
Hopefully
that
helps
so
yeah.
So
it's
not
that
the
like
it's
not
that
hub
isn't
available
per
se.
B
B
A
B
A
B
For
me
right
if
I
was
looking
at
red
hat-
and
I
said
oh
dev
sandbox-
has
this
problem:
what's
the
priority
of
that
right,
right,
yeah,
what
I'm
just
trying
to
elaborate
on
is
that
dev
sandbox
is
just
one
instance
of
this
problem.
It
is
a
it
is
a
problem
for
a
number
of
other
scenarios
as
well,
and
so,
as
a
result,
it's
pretty
high
priority,
specifically
with
actually
service
mesh
and
serverless.
B
So
you
may
even
see
a
solution
where
service
mesh
and
serverless
just
become
available
to
developers
in
dev
sandbox
without
you
mucking
with
the
operator
in
a
sense,
it'll,
just
kind
of
be
set
up.
Okay
moving
on
so
I
went
and
did
the
go
like
sample
in
code
ready
workspaces
and,
as
you
can
see,
I
have
like
a
go
application
here
right.
The
thing
is:
is
that
it's
just
like
a
go
application,
so
that's
actually
not
really
what
I
wanted
right.
B
Is
this
thing
called
a
dev
file
which,
if
you've
ever
worked,
especially
as
a
team
lead
for
a
software
development
team?
It
is
incredibly
difficult.
I
find
this
video
very
distracting.
Sorry,
it's
incredibly
difficult
to
onboard
new
people
onto
an
existing
software
project.
That's
been
going
on
for
a
long
time
and
one
of
the
reasons
you
know
obviously
there's
all
the
teaching
and
stuff
about
how
you
do
things,
but
there's
also.
B
The
reason
of
I
want
to
make
sure
they
have
the
exact
right
operating
system,
exact,
right
code
base,
exact
rate
patch
level,
et
cetera,
et
cetera,
so
that
we're
all
operating
from
the
same
exact
position.
You
know
whether
we
decide
to
continuously
integrate
patches
or
we
decide
to
delay
them
for
a
patch
day
or
whatever.
B
What
I
want
is
my
whole
team
to
be
operating
from
the
same
position
at
any
given
point
so
vagrant
if
you've
ever
used,
vagrant
try
to
solve
this,
or
it
does
solve
this
to
some
extent
for
many
years
now,
using
virtual
machines.
Basically,
you
have
this
thing
called
a
vagrant
file.
I
give
it
to
everyone
on
my
team:
they
click
vagrant
up
and
bang.
They
have
an
environment
that
looks
like
everybody
else
is
on
the
team
code,
ready
workspaces
with
this
dev
file
thing
which,
let's
see
if
I
can
find
it
actually.
B
I
know
it's
easily
accessible
here,
no
wrong
button.
It's
easily
accessible
here
this
dev
file
thing.
I
can
give
somebody
else,
this
dev
file
and
it
will
create
exactly
the
same
development
environment
and
on
top
of
that,
if
you're,
using
something
like
code
ready
workspaces
which
is
being
deployed
on
an
open
shift,
you
know
exactly
what
it
looks
like
because
it's
all
coming
from
the
same
open
shift.
It's
all
coming
from
the
same
operator,
which
is
then
in
turn
creating
the
exact
same
development
environment,
so
yeah
a
vagrant
vm
in
openshift.
A
A
B
B
B
Plug-In
where
I
can
say
give
me
a
vm
in
you
know
inside
openshift
I've.
Actually,
if,
if
you
like,
openshift
sorry,
if
you
like
vagrant,
I
have
experimented
a
bunch
with
their
container
tooling.
So
you
can
actually
say
you
know.
Instead
of
a
vagrant
vm,
you
can
have
a
vagrant
container
and
many
years
ago,
if
you've
ever
seen
the
container
development
kit,
the
original
version
of
that
actually
works
in
vagrant.
So
it's
entirely
in
vagrant
and
if
you
use
vagrant
all
the
time
and
you
use
it
with
rel
all
the
time.
B
I
also
wrote
a
plugin
for
vagrant
that
does
your
red
hat
registration
for
rel
automatically,
which
may
be
interesting
to
people
who
use
vagrant
and
rel
quite
a
lot,
and
I
have
since
discontinued
my
support
for
it.
But
it
was
popular
enough
in
the
community
that
it
has
now
grown
its
own
owners
who
now
maintain
and
do
a
good
job.
B
B
I
wanted
an
online
ide
which
I
could
experiment
with
this
online
ide.
So
that's
cool,
but
not
quite
what
I
was
looking
for
right.
What
we
were
looking
for
was.
I
want
an
online
ide
for
the
things
I'm
using
in
openshift.
If
that
makes
sense,
so
I'm
actually
going
to
go
back
here
and
destroy
this,
because
it's
not
what
I
want,
but
the
reason
I
bring
it
up
is,
you
know
like
like.
If
that's
your
goal,
it's
a
good
one
and
it's
just
you
have
to
do
it
kind
of
differently.
B
B
B
A
B
I
I
remember
using
it
when
it
was
primarily
targeted
as
as
for
like
web
developers
on
mac,
which
was
how
I
started
using
it
not
on
mac
or
as
a
web
developer,
but
but
that
was
when
I
started
using
it.
I
just
found
it
super
handy
to
be
able
to
pre-describe
config
management
for
developers
right.
Is
that
like?
Well,
I
it.
B
B
B
B
B
B
B
B
B
In
my
experience
right
like
I
did
a
bunch
of
java
work,
it's
really
performant
once
it's
going,
but
if
you
want
to
do
something
like
serverless,
where
you
want
it
to
be
able
to
scale
to
zero,
you
cannot
scale
it
to
zero.
You
have
to
you,
have
to
keep
one
at
least
one
hot
right
and
what
corkus
lets
you
do
is
have
one
that
is
zero
and
then
still
can
respond
to
a
request
in
a
reasonable
enough
time
frame,
even
though
it's
starting
up
the
entire
jvm.
A
B
B
B
B
A
B
Out
a
little
bit
and
so
points
4
600
for
nurendev,
very
nice,
very
nice,
netherlands
hackam
with
4
500.,
then
I
haven't
seen
a
lot
of
movement
from
noaa
friction
and
joe
fuzz
the
past
couple
of
episodes.
So
we
I'm
hoping
that
we'll
we'll
see
that
movement,
detective,
conan,
kudo
and
bacon
fork
definitely
up
and
coming,
and
let
me
throw
the
today's
points
into
the
chat.
Thank
you.
B
Yeah,
I
yeah,
I
know
a
lot
of
I.
I
know
a
number
of
you
are
working
on
that
yeah.
I
am
too
I'm
I'm
really
curious
how
that's
going
to
work
exactly.
I
haven't
really
experimented
with
it
at
all,
but
it's
something
it's
like
on
my
list
of
things
to
do.
It's
just
the
list
isn't
like
any
kind
of
reasonable
length,
so
yeah
but
currents
has
the
points.
Thank
you
all
so
much
for
coming
along.
We
we
are
so
close
so
close
to
giving
out.
B
You
know.
Extrinsic
rewards
for
the
points
rather
than
just
intrinsic.
We
are.
We
are
kind
of
waiting
on
legal
at
the
moment
as
you
do,
and
so
kona
kudo,
who
was
masquerading
as
the
eighth
doctor,
is
back
to
conan
kudo
and
thanks
all
for
joining
us.
I
think
I
wanted
to
kind
of,
I
think,
wrap
up
there
unless
anybody
else
had
any
more
questions.
B
Yeah
right
right
right,
but
you
know,
like
I
said
I
kind
of
wanted
to
give
a
little
bit
better
overview
of
dev
sandbox.
I
think
some
of
my
challenges
in
the
last
episode
were
related
to
these
things
that
I
think
like
at
least
for
me.
It's
a
little
bit
unintuitive
how
some
of
these
pieces
connect
together,
and
so
you
know.
Hopefully
this
episode
has
helped
you
intuit
it
better,
so
that
you
can
have
a
you
know,
a.
A
B
Positive
experience
than
we
did
the
the
first
time
we
took
a
swing
at
it,
but
it
is
super
powerful,
like
you,
can
you
really
can
do
a
lot
of
stuff?
You
know
you
can
use
tools
like
we
mentioned
in
the
chat.
You
can
use
tools
like
odo.
We
have
not
done
odo
on
the
show.
We
really
should.
You
know.
We've
only
done.
A
B
B
B
A
A
B
And
remember:
podman
v3,
we'll
be
talking
about
that
next
week
on
this
show
and
then
with
any
luck.
If
I
can
make
the
if
I
can
make
the
timing
work,
I'm
going
to
be
help
hosting
the
rel
show
in
a
few
weeks,
and
we
may
who
knows
maybe
there'll,
be
some
points
given
out
then
snap
right,
so
you
never.
Could
you
never
know
so
yeah?
I
just
I
have
a
conflict
that
I'm
trying
to
get
out
of.
Basically
at
this
point
to
try
to
be
able
to
host.