►
From YouTube: Developer Experience Office Hours: How do YOU develop on OpenShift - Two Developers Go Head to Head
Description
Join OpenShift's Developer Experience experts for our regularly scheduled program filled with cloud native, Kubernetes, and OpenShift tips and tricks for developers.
A
Good
morning,
good
afternoon,
good
evening,
wherever
you're
hailing
from
welcome
to
another
edition
of
our
developer
experience
office
hours
here
on
openshift
tv,
we
are
back
after
quite
the
hiatus
red
hat
summit
and
kubecon
have
been
a
blur
for
me,
as
I'm
sure
many
others,
but
we
are
back
to
our
normally
scheduled
fun
and
serena.
You
have
a
very
interesting
topic
on
tap
today.
I
I
find
this
fascinating.
Would
you
like
to
tell
us
a
little
bit
about
what
we're
talking
about
and
who's
here.
B
Yeah
definitely
thanks.
Chris,
hey
everybody
glad
to
be
back
so
today
we've
got
evan
and
use
who
are
two
members
of
red
hat
and,
interestingly
enough,
they
were
both
part
of
an
intricate
part
of
the
keynote
summit
demo
of
developing
different
pieces
and
through
that
process
we
found
out
that
there
was
different
ways
that
peop
that
developers
were
kind
of
developing
and
deploying
onto
openshift
and
testing.
So
we
thought
it
would
be
a
really
cool
series
for
to
you
know
for
one
of
our
developer
experience
office
hours.
C
Yeah
sure
I
hope
I
might
still
so:
hey
I'm
evan
chartis.
I
work
at
red
hat
on
the
managed
services
side
of
things.
So,
if
you're
watching
some
of
you
would
have
seen
this
launch
our
red
hat
openshift
streams
for
apache
kafka,
so
I
work
with
the
team
behind
that
and
our
managed
api
management
solution
and
what
I
do
is
I'm
a
technical
marketing
manager.
So
I
help
enable
our
field
and
I
get
to
make
fun
demos,
nice.
D
Yeah
hi,
my
name
is
ian
lawson,
I'm
a
domain
solution,
architect
specializing
in
openshift.
I've
been
at
open
red
hat
for
about
nine
years.
Now
I
basically
evangelize
about
openshift
and
how
good
it
is.
I'm
slightly
different
to
most
people
at
red
hat
and
I
used
to
work
for
a
living.
I
was
actually
a
software
developer
for
25
years,
which
is
one
of
the
reasons
why
we're
having
this
talk
today,
because
I'm
an
old-school
software
developer
who's
happening
to
do
new
school
software
development.
E
B
Here
is
the
question
for
everybody
and
you
should
be
able
to
have
multi-select.
How
do
you
develop
on
openshift
today?
So
are
you
pushing
to
get
to
get
with
no
web
hook
and
kick
off
a
build
in
openshift
yourself?
Are
you
pushing
to
get
with
a
web
hook,
so
the
build
automatically
kicked
off
in
openshift?
Are
you
building
locally
pushing
to
your
image
registry,
hopefully
quay
and
deploying
that
image
into
openshift?
B
B
B
E
B
Where,
where
the
numbers
are
right,
if
people
are
watching
the
recordings,
so
definitely
please
take
take
a
second
to
answer
that
question
and
then,
after
this
one,
what
we're
also
going
to
do
is
which
of
you
of
these?
Have
you
tried
to
date,
so
I
am
going
to
try
to
figure
out.
How
do
I
get
out
of
this
and
if
I'm
going
to
remember
how
to
do
that,.
B
E
B
A
B
Okay,
so
then,
let's
just
stick
with
that
initial
question,
which
is
how
do
you
develop
on
openshift
and
so
okay,
so
this
is
great.
We've
got
quite
quite
a
variety
here,
and
so
I'm
not
sure
who's
going
to
be
interested
in
demoing
first,
but
we
kind
of
have
it
set
up
where
you
guys
are
going
to
both
be
using
the
same
application.
B
A
C
C
Okay,
yeah
so
far,
the
demo
myself
and
ian
basically
put
together
an
application.
That's
fairly
straightforward,
it's
like
kind
of
like
a
hello
world
application.
So
if
you've
used
openshift
before
you've,
probably
seen
some
of
these,
and
this
one
is
basically
a
fork
of
one
of
those,
it's
a
node
one,
but
I've
added
in
a
build
step
because
I
really
like
typescript,
so
that
does
add
a
build
stack
which
some
people
don't
like,
but
I
like
to
type
safety.
So
that's
what
this
app
is
hello
world
of
typescript
on
openshift.
C
So
let's
see
how
I'm
going
to
deploy
it
so
I'll
give
a
quick
overview.
I
have
this
tone
locally
and
how
I
plan
to
deploy
it
first.
I
have
a
few
different
ways
actually,
but
the
main
one
I'm
going
to
show.
I
think
because
this
is
what
I
was
doing
at
summit
that
had
the
disconnect
between
me
and
me:
is
I'm
going
gonna
build
it
locally.
So
here
I
have
what's
called
an
s2i
script
in
my
folder
or
in
my
project,
and
all
that's
doing
is
using
sty.
C
So
that's
a
tool
that
red
hat
provides
and
it
stands
for
source
to
image
and
what
it
does
is
it
takes
your
source
code
and
you
give
it
a
builder
image.
So
in
this
case
I'm
giving
it
the
node.js
builder
image
and
it
will
transform
your
source
code
using
kind
of
best
practices
like
the
standard
procedure.
You'd
expect
with
most
of
the
runtimes
the
same.
C
It
does
the
same
thing
with
java
and
other
languages
too,
and
it's
going
to
transform
that
source
code
from
a
local
folder
into
a
container
image
using
docker
or
if
you
use,
I
guess,
build
and
pod
manage.
It
supports
those
two
I'm
guessing,
but
it
builds
that
container
image
on
my
local
machine
and
I'm
going
to
push
that
up
to
key.io
or
you
can
push
it
up
to
a
different
image
registry.
If
you
use
another
one
and
then
I'm
going
to
deploy
an
openshift,
so
I
guess
I'll
do.
C
B
C
I
have
an
open
shift
cluster
over
here
by
the
way
in
chrome,
so
I'm
just
going
to
deploy
it
into
this
dev
project
I
have
here.
This
is
a
free
cluster.
By
the
way
you
can
get
it
on.
This
is
the
sandbox.
This
is
the
sandbox
yeah.
I
love
it.
It's
so
cool
like
how
easy
it
is
to
get
these
clusters,
so
maybe.
B
C
Show
that
in
a
minute-
although
I'm
sure
you've
shown
it
before
on
the
channel
so
yeah,
let
me
dive
right
in
so
we're
gonna
run
this
script
and
you'd
see
it
build.
It
should
only
take
a
few
seconds
and
I'll
deploy
it
on
openshift.
So
I'm
on
my
terminal
right
now
and
the
script
I'm
going
to
do
s2i.sh
and
this
will
invoke
s2i
and
it's
really
quick.
Actually,
you
can
see
it's
already
after
copying,
my
source
over
to
the
build
container
that
it's
spun
up
in
the
background.
C
So
if
I
like
go
to
docker
ps,
it's
probably
going
to
say
yeah
there
you
go
so
I
have
this
container
spun
off
and
it's
building
my
source
code
and
it's
going
to
output
another
build
image
on
my
machine,
so
it
takes
a
few
seconds.
But
while
I
do
that,
maybe
I
should
put
the
link
to
source
the
image
in
the
chat
press.
Would
that
be
a
good
idea?
Yeah.
C
C
F
C
For
that,
it's
like
maven
mpn
pick
your
poison
right,
but
yeah,
so
that
that
installed
the
dependencies
and
it
ran
the
typescript
compiler
which
compiled
my
typescript
to
javascript
and
by
now.
If
I
do
a
docker
images
here
there,
you
go
right
so
taggedish
with
this
really
long
tag,
name
that
I've
given
it
which
is
io
and
then
my
username
and
the
openshift
example.
C
C
C
Myself,
so
if
I
refresh
here
key
to
lio,
you
can
see
a
few
seconds
ago,
the
latest
tag
was
updated,
which
is
awesome.
It's
ready
to
to
be
deployed
so
I'll
go
over
here
to
openshift,
and
I,
like
this
developer
view
for
doing
this
stuff,
because
we
do
that
nice
topology
when
you've
deployed
a
few
things,
so
you
can
see
that
now
so
I'll
do
an
add
and
I'm
going
to
choose
container
image,
and
I
know
it's
oh
wait.
I
can
just
copy
it
for
my
terminal.
C
If
I
can
type-
and
I
generally
actually
choose
to
plan
and
configure
this
stuff-
I
don't
know
why
it's
just
habit,
I
know
deployments
are
maybe
better
if
they're
newer,
I
think
they're
newer,
but
I'm
just
so
used
to
design
configs
and
how
to
do
the
rollout.
I
just
prefer
to
do
that
and
then
for
revving
I'll
make
sure
it's
using
https.
C
C
C
B
C
E
E
D
Yeah,
that's
good
yeah.
So
before
you
start
the
timer,
because
first
of
all
I
didn't
realize
there
was
going
to
be
a
timer
which
is
a
little
bit
of
a
pain,
a
very
quick
introduction
about
why
why
we
wanted
to
do
this
in
the
first
place
when
we
were
developing
on
summit,
I
was
just
using
the
openshift
side,
because
that's
what
I'm
used
to
you
know.
I've
been
using
openshift
for
so
long
and
I
really
love
the
openshift
user
interface.
You
know
it's,
it
rings
my
bells.
D
You
know
I'm
a
bit
of
a
pat
and
fly
addict,
but
I
was
very
surprised
that
all
the
other
developers
were
involved
with
summit
didn't
use
the
actual
openshift
to
do
their
builds.
They
were
doing
all
the
builds
locally.
They
were
using
docker.
You
know
the
same
way
that
evan
just
did
right.
I
don't
use
docker.
I
have
a
history
with
docker
which,
which
I
won't
go
into.
I.
D
Oh,
it's
not
so
much
that
I
I
love
my
mac
and
and
docker
doesn't
love
my
mac.
So
so
every
time
I
try
to
put
docker
on
my
mac,
they
just
didn't
get
on
like
a
house
on
fire.
I
think
it's
the
best
way
of
doing
it,
so
I
don't
run
containers
locally
and
if
I
want
to
do
builds,
which
I
had
to
do.
Some
builds
like
this
at
summit.
D
I've
got
a
virtual
machine,
running
fedora
and
I
use
pod
map
rather
than
docker
for
that,
but
for
things
with
the
applications
where
you
can
actually
build
within
openshift
itself,
all
those
things
that
evan
showed
you
in
terms
of
the
source
to
image
they're
all
wrapped
up
as
part
of
the
developer
experience
within
openshift
itself.
So
whilst
it's
nice
to
be
able
to
download
the
the
s2i
and
use
it
on
a
kind
of
local
machine,
I
like
to
run
my
builds
elsewhere.
D
But
what
I'm
going
to
do
is
I'm
going
to
do
exactly
what
evan
did,
but
I'm
going
to
do
it
all
through
the
user
interface,
oh
nice,
and
also
I'm
going
to
I'm
going
to
add
redis
just
just
because
it
just
goes.
Yeah
we're
all
friends
here.
We're
all
honest.
I
I
didn't
see
this
application
until
this
morning,
so
so
and
I've
never
built
it.
So
so
this
this.
B
C
C
A
D
Yeah
yeah,
I
say
it's
I'd
like
to
say
I'm
a
fanboy
of
openshift
so
and
people
people
who
know
me
know
that
I
am
a
fanboy
of
openshift
but
anyway,
so
I'm
going
to
do
it
from
scratch
within
the
user
interface
itself.
So
the
first
thing
I'm
going
to
do
is
I
don't
have
a
project.
So
I'm
not
sure
if
you're
going
to
start
the
timer,
but
I've
got
you
know,
I'm
going
to
start
a
product.
You
know
create
a
project.
D
Counts,
let's
call
the
hell
of
it
going
to
create
it.
If
I
pop
it
was
the
developer
viewpoint
same
topology,
we
had
before
I'm
going
to
do
it
from
not
the
container
image.
I
do
it
from
the
catalog.
Now
the
application
itself
is
based
around
node.
So
I'm
going
to
use
a
node.js
builder
image.
Okay,
create
the
application
I'm
going
to
choose
14.
Was
it
14
or
12?
You
built
it
with
evan.
I
did
a
12,
but
it
should
work
with
14.
G
D
Validates
I'll
choose
the
same
thing
deployment
config,
because
I'm
a
fan
of
deployment
config,
so
I
prefer
them
to
deployments,
given
application
name
I'll
call
it
demo
app
that's
for
the
application
grouping,
not
the
application
itself
and
we'll
call
it
test,
because
I
love
using
the
word
test,
create
a
root
yeah,
exactly
the
same
hit
create
so
how
this
is
different
to
the
way
that
evan
did.
It
is
that
this
is
actually
creating
another
pod
before
it
even
starts
to
do
the
application
deployment
itself.
That
pod
is
a
build.
D
So
all
the
things
you
saw
evan
do
on
his
command
line
on
his
local
machine
are
now
being
repeated,
but
they're
being
repeated
within
a
pod
within
openshift
itself.
So
I'm
using
openshift
resources
to
do
the
build
and
we
can
actually
look
at
the
the
build
going
while
it's
doing
it
and
you'll
see
exactly
the
same
kind
of
messages
that
you
saw
from
evans
side,
something
about
husky
it
contains.
It
complains
in
italy
about
how
soon
that's
the
only
thing
I
noticed
when
I
was
doing
a
build
earlier.
B
D
For
using
husky
and
all
those
kind
of
things
so
yeah,
so
what
it's
actually
doing
now
is
it's
downloading
the
image
that
the
base
image
on
which
it's
going
to
build?
So
it's
going
to
get
what
we
call
the
universal
base
image
universal
base
image
is
a
very
useful
tool.
It's
a
very
useful
base
image
that
we
produced
that's
designed
as
a
kind
of
small,
easy
way
to
actually
build
applications
on
top
of
it's
going
to
get
them.
D
It's
loading
them
into
integrated
registry
before
it
starts
to
do
the
build
when
it's
got
the
image
down,
when
the
image
is
actually
being
produced,
it'll
actually
start
to
do
the
binary
build
side
of
the
the
actual
application
itself
I'll
hit
resume
stream,
so
you
can
continue
to
watch
it.
It
will
bit
about
the
npm
stuff
and
someone
complained
about
npm
timing.
D
G
D
A
D
C
A
D
The
first
thing
is:
I've
forgot
to
press
the
open,
url
button,
but
the
second
one
is
evan
is
using
the
dedicated
sandbox.
This
new
sandbox
we've
got
which
people
can
raise,
which
is
fantastic.
It's
a
hosted
system.
It's
a
grunty
meaty
system.
Now
I'm
not
allowed
to
use
it.
I
am,
but
I'm
not
allowed
to
use
it
because
I'm
a
red
hat
employee.
D
So
I've
got
this
this
this
sort
of
lesser
cluster,
which
I've
run
up
on
aws,
which
I've
got
limit
ranges
which
means
that
all
the
pods
run
much
slower
and
those
kind
of
things
but
being
serious
for
a
second.
You
see
that
exactly
the
same
functionality,
but
I
didn't
have
to
fire
up
a
command
line.
I
didn't
have
to
do
as
much
typing,
which
you
know
when
you
reach
my
age.
D
D
A
A
D
D
Each
of
the
applications
can
express
environment
variables
into
all
the
other
pods,
but
they're
not
expressed
until
the
pod
is
restarted
because,
of
course,
the
environment
variables
part
the
container
part
of
the
container
spec
when
the
actual
pod
starts.
So
I'm
going
to
restart
this
now
it
should
pick
up
the
reddest
thing
and
again
this
is
going
to
fail.
D
I
was
going
to
do
the
kind
of
oh
dear.
It's
failed
that
kind
of
sort
of
wonderful
thing.
We
normally
do,
but
no
no,
no,
this.
This
will
fail.
But
I'll
tell
you
why
in
a
second
so
I'll,
do
it
the
old
school
way?
Let's
get
it
down
to
zero,
get
rid
of
the
resources
scale
it
back
up
and
theoretically,
it
should
start
up
and
have
the
reddish
database,
the
reddish
sort
of
back
end
storage.
So
it
can
actually
record
the
number
of
things
and
it's
immediately
failed
right.
D
A
lovely
good,
old-fashioned,
red,
wonderful
crash
loop
back
off
that
we're
aware
of
and
the
reason
it's
failed
is
that
redis
is
authenticated.
It
needs
a
password.
So,
even
though
the
actual
configuration
information,
the
connect
connectivity
information
is
expressed
automatically
into
the
deployment
we
haven't
got
that
piece
of
information
now
normally.
This
will
require
me
going
away
to
fire
up
the
command
line.
Looking
at
the
secrets,
changing
a
config
map,
doing
all
those
fiddly
things,
but
another
nice
feature
of
the
user
interface
is.
D
I
can
change
the
aspects
of
the
deployment
of
the
application
as
well
as
the
application
itself.
So
what
I'm
going
to
do
and
I'm
going
to
watch
evan
wins
because
I'm
probably
going
to
get
it
wrong.
Is
I'm
going
to
look
at
the
deployment?
Config
look
at
the
environment
and
I
say
I'm
going
to
get
it
wrong
because
I
got
it
wrong
earlier.
I
went
out
from
a
conflict
map
because
the
config
map
actually
for
reddit
contains
the
password.
D
C
D
This
is
this
is
what
this
is.
Another
thing
amazing
about
the
summit
development
teams,
because
everyone
on
the
development
team
is
at
least
30
years
younger
than
me
right,
and
so
so
I
come
from
an
old
school
where
I
you
know,
when
I
first
started
programming,
I
used
four
track
and
fortran
was
a
horrific
language
where
you
had
to
tab
and
space,
and
you
had
a
limit
of
six
letters
or
whatever
on
the
actual
variable
names.
D
When
I
started
in
java,
I
wrote
the
most
verbose
code
you've
ever
seen,
because
I
could,
I
wrote,
sort
of
five
pages
of
java.com.
You
know
because
it
was
just
wonderful
to
be
verbose,
and
yet
everyone
I've
dealt
with
on
the
summit
team,
was
writing
these
sort
of
four-letter
variable
names.
It's
like
come
on,
enjoy
your
typing
you're
allowed
to
do
it
well
I'll,
select
the
key
from
it.
Database
password
yeah
your
database
password
expressed
in
the
server
the
secret.
That's
part
of
the
redis
distribution
nice.
B
D
D
A
D
I
want
to
show
you
very
quickly
the
environment
variables
you
see
within
the
pod
itself,
so
what
has
happened
is
when
I've
added
another
application
into
the
namespace.
There
are
a
certain
number
of
environment
variables
that
are
automatically
propagated
into
the
environment
of
the
other
pods
that
are
running
so
when
I
actually
install
redis
you'll
see
if
I
do
an
environment
and
I
grip
redis,
I've
got
a
set
of
wonderful
connectivity,
information
for
that
redis
pod
and
that's
not
part
of
this
application.
D
D
D
D
E
D
B
D
B
E
D
C
F
C
It's
working
right,
perfect,
yes,
so
there's
two
other
things
I
want
to
show.
The
first
is
the
so
the
tooling
that
we
have
at
red
hat
for
different
runtimes
right.
So
red
hat
has
runtimes.
We
support.
As
you
can
see,
we
have
the
supported
container
images
that
myself
and
ian
used
right,
the
node.js
one,
but
we
have
those
for
different
runtimes
and
for
I
know
at
least
java
and
node
are
the
two
I
use
the
most
we
have
in
java.
C
We
have
the
thing
called
fabricate
and
you
can
use
that
to
deploy
your
java
apps
really
easily
from
using
maven
and
for
node.
We
have
the
same
thing,
so
I'm
going
to
show
that
real
quickly
here.
So
if
I
go
back
to
the
code
base
here
and
in
my
dependencies,
I
have
this
nodeshift
cli
installed.
So
this
is
the
node
equivalent
if
you're
familiar
with
fabricate
it's
kind
of
kind
of
similar
it
lets
you
do
some
neat
things
with
node
on
openshift,
so
yeah.
C
C
C
B
C
Nodeshift
does
the
same
thing
with
one
cli
command,
so
it's
another
nice
way
to
set
up
that
whole
workflow.
So
you
can
see
here
yeah,
it's
super
cool.
You
can
see
here
it
creates
the
image
stream
and
then
it's
uploading,
the
archive
of
my
local
directory,
which
has
my
source
code,
and
you
can
see
these
logs
look
really
similar
to
what
was
on
ian's
screen.
So
if
we
go
over
yeah,
it's
really
cool.
C
So
I
love
this
like
so
go
over
to
stage
here
in
my
other
name
space
and
I
go
to
bills
there
you
go
like
there's
a
build
created
a
few
seconds
ago
and
you
go
to
this
build
itself
and
you
can
see
it's
only
on
the
first
build.
Obviously,
because
I
just
created
it-
and
I
can
go
in
here
and
take
a
look
at
the
locks-
and
it's
just
working
like
that.
It's
so
easy
so
like
we
don't
just
have
ui
tools
to
do
that
either
we've
both
with
cli
and
ui.
C
So
when
you
move
or
graduate
to
say
wanting
to
do
this
from
a
programmatic
expected
perspective,
you
can
do
that
too.
Or,
of
course,
you
can
use
cubectl
and
oc
to
apply
yamo
if
you're
doing
that
in
your
ci
pipelines
too.
But
it's
it's
really
easy,
so
you'll
see
the
same
logs.
That
ian
was
on
about
where
he
kind
of
gives
warnings
about
some
of
my
dependencies,
because
this
this
is
an
old
template
that
I
have
from
a
while
ago,
but
it
will
finish
building
if
I
go
over
my
topology
view.
C
B
C
C
C
And
look
if
even
if
you
do
like
so
if
you're
familiar
with
node
tooling
you
this
nice
npx
cli,
so
that
will
call
my
local
copy
of
node
shift
in
my
node
modules
for
this
project,
and
you
can
see
it
has
tons
of
options
like
you
can
specify
your
ocp
creds
or
your
credentials
to
log
in.
But
you
can
also,
you
know
manage
if
it
uses
if
it
exposes
an
ssl
endpoint.
C
Instead
of
just
playing
https
or
playing
http,
you
can
specify
the
image
stream
all
sorts
of
stuff
and
also
you
know
the
pretty
display
name
so
the
namespace
yeah.
So
like
it's
really
powerful
too,
and
it
also
supports.
I
haven't
really
looked
into
this
one
yet,
but
you
can
create
a
node
shift
file
in
your
project.
I
think
it
reads
from
there.
So
if
you
want
to
make
customizations
to
your
deployment
config,
you
can
do
that.
So
it's
really
neat
like
you
can
put
in
custom
environment
variables
and
different
things
so
yeah.
C
It's
all
awesome.
The
runtime
scene,
like
the
noting
they're
doing
cool
stuff.
Did
you
have
a
team
like
porcus
team,
like
they've
all
these
cool,
similar
tools
that
really
make
it
nice
for
a
developer
when
they're
either
staying
in
local
or
going
to
dui
they
can
they
can?
You
know,
use
these
in
conjunction
like,
for
example,
just
really
quickly
if
I
was
using
node
shift,
for
example,
I
can
go
to
the
ui
here
and
I
have
to
confess
I
do
this
all
the
time.
C
So
I
go
to
the
edit
deployment
config
or
deployment,
and
I
go
to
this
yaml
view
and
I
copy
and
paste
this
all
the
time
as
a
template
for
my
yaml,
when
I
want
to
do
like
a
ci
deploy,
because
I
always
make.
I
don't
know
about
you
guys,
but
I
I
can't
write
yaml.
I
just
always
make
mistakes
I
never
know
like.
Should
I
put
a
you
know
just
space.
C
Yeah,
whereas
with
xml
or
json,
I'm
like
okay,
like
I
know
where
I
put
my
brackets
and
I
know
where
I
don't
put
my
brackets
but
with
yellow-
I
just
have
no
idea.
So
I
do
this
all
the
time
I
deploy
using
the
ui
like
bean
showed
or
I
use
nodeshift
or
maven,
and
then
I
copy
the
resources
and
then
I
recreate
the
project
with
those
in
the
future
in
ci.
So.
A
C
C
B
C
A
A
C
Awesome,
so
what
I'm
going
to
do
is
open
the
code
base
locally
here
and
I'm
just
going
to
make
like
a
trivial
change.
So
I'm
going
to
go
to
the
index
file
here,
so
I'm
using
handlebars
for
templating
and
we
have
a
rocket
ship
here,
which
is
a
very
cool
emoji.
But
let's
change
it
to
like
a
rock
star.
How
about
that?
Like
a
lady
rock
star
thing
right
here
there
you
go
right,
be
an
easy
change.
I'll
do
a
git
status.
C
C
So
yeah
feature
you
cooler,
avatar
your
emojis,
and
so
you
can
see
husky
here
that
we
were
getting
mad
at
is
being
really
good
to
me,
because
it's
formatting
my
code
and
keeping
it
consistent.
So
that's
why
I
like
possibly
a
lot
it
keeps
me
disciplined
and
keeps
my
code
like
format.
So
if
I'm
sloppy,
it
doesn't
get
checked
in
without
this
weird
formatting
issues.
So.
C
So
basically,
it's
a
it's
a
library
you
can
pull
in
from
npm,
just
probably
probably
equivalents
for
like
different
runtimes,
but
what
it
does
is
it
installs
git
hooks
in
your
project
and
you
can
link
them
to
scripts
in
your
package.json.
So,
for
example,
I'm
using
husky-
and
I
have
a
block
here
in
my
you
know,
my
palm
or
my
package
json
and
I
put
in
a
pre-commit
hook.
B
C
Basically,
what
it
does
is,
I'm
saying,
run
my
format,
script,
so
format,
my
files,
so
you
know
it's
javascript,
so
you
could
leave
out
semicolons
or
you
might
want
to
put
them
in
or
take
them
out
or
you
know
whatever.
So
it
runs
my
formatting
and
then
it
adds
those
updated
files
into
my
commission.
So
it's
really
nice
it.
Basically,
you
can
do
other
things
right.
You
can
force
it
to
run
unit
tests,
so
someone
can't
make
a
commission
unless
they
run
your
unit
tests
and
other
things
like
that.
So
yeah.
It's.
C
B
C
Wrong,
I
shouldn't
be
using
stage
the
way,
I'm
adding
the
files,
but
what's
really
cool
is
I'm
integrating
github
actions
in
this
project.
So
we
didn't
talk
about
ci
or
cd
much
yet,
but
I
have
a
workflow
here
that
uses
red
hat's
actions.
So
red
hat
has
these
really
cool
actions
on
github?
Where,
if
you
go
and
take
it
check
out
this
build,
I
have
a
source
to
image
action
so
to
source
the
image
I
was
doing
on
my
own
machine
or
myself
and
ian
both
did
on
openshift.
C
You
can
run
it
here
and
github
actions
too.
So
you
look
at
these
logs
they're
the
exact
same
logs,
because
it's
running
the
source
image
binary
on
github
actions
and
then,
after
that
I
can
use
the
push
to
key
or
quay
action.
So
it's
taking
the
built
images
from
github
or
if
you
get
of
action
pushing
into
my
repo
in
in
key.io.
C
So
I
didn't
do
a
build
manually
at
all
so
you've,
so
many
options
here
to
work
to
get
this
sy
into
your
workflow
right
awesome,
it's
really
cool
and
these
actions.
I
set
them
up
last
night
because
I've
seen
them
before
but
never
used
them,
and
I
was
like
it's
really
cool
to
finally
use
these
and
it's
so
easy
because
we
just
copy
a
snippet
from
the
action
documentation
that
the
red
hatters
have
built
and
it
just
worked.
Basically
it
was
so
easy.
C
So
if
I
go
over
to
key.io
now
and
refresh
you
can
see
a
few
seconds
ago,
my
latest
tag
got
updated
and
I
have
a
new
tag
here
for
that
specific
commit.
So
it's
so
easy
and
then,
if
I
want
to
just
redeploy
this,
I
can
go
over
to
my
dev
project,
because
I
have
my
dev
project
pointing
to
the
latest
tag
and
I
can
do
a
rollout
or
I
could
delete
the
pod
as
well.
C
A
C
A
C
D
D
D
There
were
things
I
had
to
break
out
of
the
interface
to
do
and
when
you're
actually
trying
to
code
something
very
quickly
when
you're
trying
to
get
something
done
very
very
quickly.
You
don't
want
to
be
shifting
around
you
want
to
have
a
nice
single
focus,
you'll,
be
able
to
focus
on
your
code,
focus
on
what
you're
doing,
and
I
find
it's
much
easier
to
sit
with
just
a
single
web
page
open
and
I
can
go,
and
I
can
see
what's
going
on,
find
the
problems
was
that
the
rock
star.
C
D
Especially
in
the
latest
couple
of
releases
of
openshift,
the
there's
been
a
huge
amount
of
functionality
added
that
makes
the
developers
lives
easier.
I've
come
I've,
had
lots
of
conversations
with
serena
in
the
past
about
you
know
the
kind
of
workflow,
because,
oddly
enough,
most
of
us
cheat,
you
know,
most
of
us
will
develop
online,
we'll
develop
locally,
we'll
go
and
build
the
images
the
same
way
that
everyone
was
doing,
and
I
think
people
need
to
be
aware.
You
don't
have
to
do
that
anymore.
D
Now,
you
can
do
everything
you
can
dive
right
down,
for
example
the
stuff
that
evan's
showing
right
now
literally
before
this
just
before
this
stream.
One
of
the
reasons
why
I'm
mildly
confused
is,
I
was
dealing
with
a
problem
the
customer
had
and-
and
we
were
just
diving
straight
into
the
animal
literally
straight
into
the
animal-
to
find
the
problems
and
it
was
like
fix.
The
animal
fix,
the
animal
fix,
the
handle.
E
D
A
D
I've
seen
a
problem
when
I
was
working
on
summit,
and
I
can
talk
about
it
now,
because
it's
all
done
and
dusted
and
it
didn't
catch
fire
where
we
were.
We
would
find
a
problem.
We'd
have
to
jump
into
another
system,
jump
into
another
cluster
and
jump
into
another
system.
By
the
time
we
get
to
the
root
problem,
the
root
cause
of
the
problem
itself,
I've
forgotten
what
the
problem
was
there's
so
many.
C
A
D
D
B
Yeah,
I
think
too,
like
there's
different
ways
to
do
that
too.
Right,
we've
got
the
visually
guided
methodology
now
with
through
the
topology
view,
which
makes
a
lot
of
things.
Super
easy
and
evan
has
demoed
some
of
that
as
well
during
during
the
summit
keynote.
Where
he's
doing
for
for
the
for
the
binding
right
to
create
the
binding
and
stuff
like
that.
C
C
C
Like
I
oc
patch
commands
I've,
I've
messed
those
up
far
too
many
times
so
are
like
you
know
it
just
I
I
really
like
the
ui
just
from
doing
these
administrative
tasks
and
getting
started,
and
I
think
the
ui
just
it's
one
of
our
nicer
features
in
terms
of
just
as
a
developer,
getting
started
with
this
stuff,
making
it
feel
less
intimidating.
I
think,
for
sure,
is
really
nice.
B
And
a
couple
other
things
that
are
coming
in
the
future,
because
I
am
serena
in
the
future,
but
we
will
we
will
be
having
form-based
edits
for
deployments
and
deployment
configs
very
soon
and
then
possibly
the
release
after
form-based
edit
for
build
configs
so
again,
like
you're,
showing
that
jumping
right
into
yaml
but
like
if
you
prefer
a
form,
we're
trying
to
get
some
of
that
some
of
that
back
into
openshift4.x,
because
we
did
have
form
based
edits
in
three.
So
it's
another
thing
we're
trying
to
do
from
a
parody
perspective.
B
A
D
C
A
Type
does
a
pro
and
con
exist
for
most
of
the
recommended
new
projects
and
add
two
projects.
Could
you
that
that's
a
question
that's
being
asked
groov
cs?
Can
you
maybe
elaborate
on
that
like
a
cheat
sheet?
Okay,
yeah
yeah?
Do
we
have
any
cheat
sheets
about
deploying
to
openshift
or
anything
like
that?
I
feel
like
this
episode
could
spawn
a
few
so.
A
B
Do
have
some
quick
starts
that
are
limited,
yep
right
now
and
actually
the
quick
starts
if
you
go,
whoever
is
sharing
their
screen.
If
you
go
up
to
the
help
menu
on
the
top
and
the
first
item
under
there
should
be
quick
starts.
So
there
are
a
number
of
quick
starts
that
are
are
there
by
default,
and
the
really
cool
thing
about
quick
starts
in
4.7.
B
B
When
we
get
to
4.8
you're
going
to
be
able
to
see
that
on
that
that
aid
on
the
ad
page,
the
cluster
admin,
is
going
to
be
able
to
hide
pieces
that
they
don't
want
available
for
their
devs.
But
what
what
I
guess
it
would
be
interesting
to
have
a
conversation
from
a
red
hat
perspective
or
from
specific
developers
or
essays.
What
do
they
think
is
the
best
practice
that
is.
D
I
have
a
slight
problem
with
that
question,
because
this
is
one
of
the
things
I
talk.
A
lot
to
customers
about
openshift
is
a
box
of
technical
lego
and
one
of
the
wonderful
things
about
openshift
is
that
if
you
want
to
do
something,
there's
probably
four
or
five
ways
you
can
do
it.
We
don't
we
don't
push
methodologies,
we
don't
push
opinionation
on
people
when
they're
using
openshift,
it's
designed
to
cater
for
other
people
or
what
other
ways
of
doing
it.
I
get
asked
all
the
time.
What's
the
best
practice
for
this.
C
C
D
A
B
D
A
A
E
D
B
To
say:
hey,
based
on
what
we
just
showed
now
what
we've
talked
about?
What
method
do
you
prefer
and
just
to
get
an
idea
based
on
after
we,
we
talked
and
showed
everybody.
So,
let's
see
if
I
can
actually
find
the
screen
that
I
want
to
share
there.
It
is
let's
try
to
do
a
presents
here,
and
I
think
we
only
have
two
minutes
left
anyways
chris,
but
maybe
we
can
get
people.
B
C
B
B
Yeah
yeah,
so
I
want
to
thank
both
evan
and
uth
for
coming.
This
is
really
great.
I'm
glad
you
guys
joined
us
and
glad
we
were
able
to
bring
this
to
the
to
the
community
to
share
some
of
the
work
that
you
guys
are
doing
and
in
ways
that
you're
accomplishing
things.
So
thanks
very
much
for
your
time.
A
C
C
E
C
A
That's
awesome,
so
everyone
is
saying:
awesome
show
good
session
ian.
There
was
a
special
shout
out
for
you
great
great
to
be
here,
you're,
so
funny
ian.
That
was
from
somebody
named
linux
studio.
So
maybe
you
know
them.
I
don't
know.
Maybe
that
was
a
plant
maybe,
but
as
always,
thank
you
all
for
joining
us
and
we
really
appreciate
it.
A
If
you
want
to
see
more
of
us
on
a
regular
basis,
please
subscribe
to
our
streaming
calendar,
which,
if
my
mouse
would
work,
I
could
open
that
window
and
type
in
the
shortcode
there
we
go
and
you
can
catch
us
every
week.
Doing
stuff
like
this
every
day,
almost
doing
stuff
like
this,
if
you
so
desire,
so
please
tune
in
at
the
next
available
opportunity,
and
you
know
let
us
know
what
you
want
to
see.
You
can
always
email
me
at
short,
redhat.com,
and
you
know
your
show.