►
From YouTube: GitHub Actions and OpenShift - John Bohannon (GitHub) John Duimovich (Red Hat) OpenShift Commons
Description
GitHub Actions and OpenShift - John Bohannon (GitHub) John Duimovich (Red Hat)
OpenShift Commons Briefing
hosted by Karena Angell (Red Hat)
The OpenShift Extension for GitHub Actions gives you the ability to create workflows to automate the deployment process to OpenShift. In this session, Github’s John Bohannon will give an overview of Github Actions, demonstrate how to use them in conjunction with OpenShift and answer questions from the audience.
A
Hello,
everyone
welcome
back
to
another
openshift
commons
briefing,
I'm
karina
angel
and
I
am
one
of
the
openshift
product
managers
and
we're
really
excited
to
have
john
bohannon
from
github
and
john
dumavich
here
from
red
hat,
to
talk
about
github
actions
and
openshift.
They
put
a
lot
of
work
into
this,
so
really
excited
to
have
them
here
to
demo
this
for
us
john.
Can
you
go
ahead
and
kick
it
off.
B
Yeah,
absolutely
thanks
karina,
so
everyone
welcome
to
this
introduction
of
how
to
use
openshift
and
github
actions.
I'm
one
of
the
johns
that's
going
to
be
presenting
today,
john
b.
We
also
have
a
john
d
from
red
hat,
so
here's
how
we're
going
to
spend
our
time
together
today,
we've
got
about
an
hour
together,
starting
off
at
really
the
ground
level
like
you've,
never
heard
of
github
actions.
B
Of
course
you
have
heard
of
openshift
and
we're
going
to
go
quickly
into
demos
and
then
q
a
so
be
sure
to
save
up
any
questions
you
have
for
the
end,
like
I
said,
I'm
john
bohannon,
I'm
in
github
partner
engineering
with
a
background
in
hardware
engineering
and
then
application
development
and
feel
free
to
reach
out.
After
the
talk
to
talk
about
partnering
about
github
platform,
apis
github
apps
can
have
actions
and
so
on.
D
I'm
the
experience
architect
for
outer
loop,
which
is
everything
in
ci
cd,
so
once
it
lands
in
git
and
gets
deployed,
I'm
responsible
for
what
that
experience
is
for
developer
tools
at
openshift,
and
you
can
see
some
of
my
history
there,
I'm
a
vm
developer,
but
I
always
plug
small
talk
because
you
gotta
go
where
the
heart
is
and
let's
get
this
show
going.
John.
B
That's
right:
okay,
great
so
we'll
start
with
github
actions.
If
you
haven't
heard
of
it,
it's
the
automation
system,
that's
built
into
github,
so
today
we're
gonna
mostly
concentrate
on
its
use
as
a
ci
provider,
but
you
can
use
github
actions
to
codify
any
workflow.
Just
a
few
points
on
this
slide.
It
is
the
number
one
ci
provider
on
github
which
we're
really
pleased
about.
After
just
a
year
or
two
of
after
launch.
B
Github
actions
comes
with
a
nice
secret
store
for
holding
things
like
deploy,
keys,
other
credentials
and
it's
community
and
partner
driven.
So
you
get
to
build
on
the
shoulders
of
giants
like
red
hat,
and
actually
I
like
that
you
don't
have
to
manage
any
compute
to
use
it
to
try
it
out.
You
can
just
head
to
the
actions
tab
of
any
of
your
repos
get
started
with
a
hosted,
runner
and
and
plug
away.
B
B
In
this
example,
workflow
is
just
like
greeting
new
newcomers
to
the
repository
with
a
message,
but
in
general
I
can
trigger
this
sequence
on
any
event
across
github
like
a
pull
request
or
a
commit,
or
an
issue
being
opened,
or
even
on
schedule
or
manually
from
a
button
press
so
super
flexible.
My
steps
can
be
verbose
and
written
right
into
the
workflow.
B
I
mentioned
that
github
actions
is
powered
by
the
community
and
by
partners
like
red
hat.
If
you're
someone
who
wants
to
write
an
action
and
give
back
to
the
community,
you
can
write
a
javascript
action.
You
can
write
an
entire
container
image
and
publish
either
one
to
github
marketplace
so
that,
like
56
million
develop
developers
can
potentially
discover
it.
It's
a
massive
audience,
a
really
flexible
way
to
get
into
open
source
and
to
provide
an
interface
to
your
tooling.
B
B
I'm
not
going
to
steal
too
much
more
of
john's
thunder,
but
we're
happy
to
announce
today
that
several
actually
red
hat
actions
are
available
for
free
in
the
red
hat
actions
organization
on
github
with
them
you
can
easily
use
builda
quay,
open
shift,
k
native
and
a
lot
more.
So
red
hat
also
maintains
a
starter
workflow.
That
will
that
you
can
find
when
setting
up
a
new
workflow
and
any
of
your
repositories,
but
in
like
this
is
outstanding
work
that
john's
team
has
done
and
so
who
better
to
demo
it
than
than
john
himself.
D
So,
let's
do
that!
Thank
you
very
much
for
that
intro,
short
and
sweet.
We
hope
everyone
likes
our
organization.
We
decided
to
go
and
not
do
many
charts
and
just
get
to
watching
me
run
a
demo,
so
that
might
be
that
might
be
a
bit
of
some
fun
and
games
because
it's
live.
We
decided
not
to
not
to
record
anything.
D
Our
our
strategy
here
is
to
enable
things
that
you
know
and
love
from
the
openshift
developer
tools,
ecosystem
things
like
build
s2i
other
things
are
quay,
repository
those
kinds
of
things
and
make
them
available
through
github
actions
and
github
workflows,
because
it's
it's
a
really
easy
way
to
consume
a
bunch
of
the
stuff
and
and
reuse
a
bunch
of
things
you
know
and
love
from
from
openshift.
So
you
can
see
even
things
like
our
early
release,
pod
man
and
those
kinds
of
stuff
things.
D
So
the
what
we
decided
to
do
today
is
a
few
demos.
The
first
one
is
quite
simple.
I
I
created
a
simple
app
called
it
simple,
app,
I'm
going
to
show
you
how
to
enable
this
using
github
actions,
workflows
the
default
openshift
workflow
and
the
the
developer
sandbox
okay.
So
basically,
what
we're
going
to
do
is
follow
these
four
easy
steps
which
is
easily
found
in
my
in
my
repo
I'm
going
to
get
a
sandbox
which
I
did
earlier
so
when
I
go
to
the
site,
I've
already
prepped
it.
D
It
doesn't
take
that
long,
but
I
didn't
want
you
guys
to
wait.
While
I
got
a
sandbox
but
a
sandbox
is
there
and
I
basically,
since
I
logged
in
earlier
it's
it's
still
logged
me
in
it's
going
to
take
me
to
my
openshift
cluster.
So
if
you
want
to
try
openshift
out,
this
is
a
a
really
great
way
to
to
get
started.
Okay,
then,
what
I'm
going
to
do
is.
Is
I'm
going
to
take
my
my
app
and
I'm
going
to
enable
it
to
run
this
and
basically
I'll?
D
Take
you
through
a
quick,
quick
view
here.
I
could
take
the
vs
code,
but
I'll
just
do
it
here.
It's
a
really
simple,
node,
app,
nothing
special!
It's
just
going
to
serve
up
some
pages.
I
have
pages
in
my
html
directory.
So
I'll
show
you
what
those
are
in
a
second,
I
have
a
very
basic
docker
file,
which
is
the
pretty
standard
one.
D
I
have
a
little
edition
here,
so
you
can
actually
show
what's
going
on
with
the
demo
that
it
is
a
live
demo
and
those
kinds
of
things
and
let's
just
get
to
get
to
business
here.
So
github
is
a
really
nice
place
to
sort
of
add
and
get
started
with
workflows.
You
can
set
up
your
own
or
you
can
go
down
here
and
take
our
ready
setup,
openshift
workflow,
which
I'm
going
to
do,
and
so
now
I'm
ready
to.
D
If
I
start
this
commit
I'm
going
to
have
a
workflow,
but
it's
not
going
to
work
yet
because,
before
you
actually
read
all
this
stuff,
so
maybe
developers
don't
read,
but
there's
a
few
things
you'll
have
to
read.
But
what
we
did
is
we
put
these
little
arrows
like
you're
at
the
lawyer's
office,
signing
documents
on
all
the
things
you
have
to
add
for
this
to
become
executable.
So
I
don't
know
where
your
username
is.
D
D
Those
are
things
that
you
wouldn't
randomly
type
in
the
clear
here
so
john
mentioned
earlier,
a
secrets,
thing
secrets
facility
to
manage
your
secrets,
so
you
could
do
something
like
put
a
deploy,
key
and
other
things
into
secure
storage
at
github
and
then
use
it
for
something
like
a
deployment.
So
that's
what
we're
going
to
do
and
I'll
show
you
how
we're
going
to
set
those
up
in
a
minute
I'm
going
to
send
this
over
to
and
the
reason
I'm
doing.
That
is
when
I
get
a
topology
viewer
or
sorry.
D
When
I
get
a
a
new
sandbox,
I
actually
get
three
name
spaces
to
have
code
and
stage
I'm
going
to
be
using
all
these
today,
but
my
dev
name
space
is
empty.
I
I
put
some
cool
future
demo
stuff
here.
So
you'll
see
some
of
that
stuff
coming
up,
but
right
now
I
chose
an
empty
one.
So
when
I
hit
the
topology
viewer,
there's
nothing
running
there.
So
if
everything
goes
to
plan-
and
I
find
my
workflow-
which
I'm
right
here-
this
will
end
up
here
in
between
dev.
C
D
Due
to
an
issue
that
we're
fixing
today,
I
have
to
go
back
to
1804,
but
that
should
be
fixed
in
our
in
our
update
to
the
build,
and
I
think
that's
it-
I've
decided
8080.
I
don't
want
to
change
the
port,
I'm
not
going
to
change
my
app
name
or
tag,
and
I
can
take
you
through
a
quick
flyby
of
this
of
this
workflow.
D
So
first
things.
First,
it's
it's
using
some
features
like
setting
up
outputs
so
that
I
can,
when
I
run
this
workflow
I'll,
get
a
really
nice
output
to
tell
me
where
to
find
the
app,
but
I
just
deployed,
because
I
always
find
that
very
interesting.
You
get
a
bunch
of
automation,
but
you
can't
find
where
your
app
does.
If
you
use
this
and
start
the
commit
and
just
start
running
stuff,
we'll
warn
you
that
your
secrets
aren't
set,
so
you
don't
have
to
debug
the
thing.
It'll
tell
you
what
to
do
so.
D
So
I'm
not
going
to
wait
much
longer,
I'm
just
going
to
actually
I'm
going
to
do
one
more
thing.
First
of
all
before
I
do
this
and
I
waste
your
time
watching
the
registry
password
and
token
I'm
going
to
go
over
here
to
the
settings.
So
the
settings
has
a
place
on
the
right
hand,
side
for
secrets.
I
don't
have
any
secrets.
This
is
going
to
be
a
problem
here
because
it's
my
first
time
enabling
it.
D
D
I'm
I'm
ui
adverse
in
some
cases
I
like
to
automate,
so
I
actually
wrote
my
own
set
secret
script
and
lo
and
behold
it's
going
to
go
and
I'm
already
logged
into
openshift
here.
So
it's
going
to
query
my
openshift
credentials
and
things
like
that
in
this
case,
getting
my
login
token
and
it's
getting
my
server
using
some
oc
commands.
D
It's
also
grabbing
my
conveniently
environment
variable
docker
password,
so
you
guys
don't
get
to
see
me
type
it
and
if
I
go
back
here
and
I
refresh
my
window,
you'll
notice
that
I
just
set
the
server
token
and
registry
password
okay.
So
instead
of
me
typing
those
manually
and
pasting,
all
that
stuff
like
I
would
have
had
to
type
in
two
passwords.
So
for
demos,
that's
not
the
greatest
thing
to
be
youtubing,
so
I
did
it
with
with
a
script.
D
I
have
to
wait
very
long.
My
open
shift
initial
workflow
is
now
running.
So
what
it's
going
to
do
is
it's
just
going
to
build
and
deploy
to
openshift.
Then
if
I
decide
to
decide
to
watch
this
run,
it
doesn't
take
very
long
to
be
honest.
It
it's
already
done
the
tag.
It's
doing
a
build.
It's
it's
dipping
along
quite
quite
quickly
here
and
as
soon
as
the
build
is
done.
We'll
we'll
see
a
push
to
the
registry.
B
C
B
D
Yeah,
it
is
secure
and
I'll
I'll
show
you
the
way.
I
did
this
you'll
notice
that
I'm
using
the
github
secret
setter.
Okay
in
this
is
the
github
command
line.
So
it's
a
convenient
thing.
If
you
haven't
seen
it,
I
recommend
downloading
it.
If
you
use
a
lot
of
github
kind
of
things,
you
can
set
your
secret,
but
there
is
no
corresponding
get
secret.
So
if
you
forget
it
and
or
don't
know
what
it
is,
this
is
not
a
place
to
get
it
back.
D
C
D
D
Anyways
this
is
the
cli,
so
this
should
be
deployed,
and
lo
and
behold
there's
my
app
it's
starting.
It's
not
quite
running
yet.
If
I
click
on
it,
it's
containers
still
creating.
So
it's
going
to
download
the
container
and
run
this
doesn't
take
very
long
and
as
soon
as
since
the
donut
fills
we
should
be.
We
should
be
ready
to
show
you
the
app
now.
This
app
is
a
simple
app,
which
was
designed
to
be
a
self
advertisement
for
this
demo
that
we're
doing
today,
it's
kind
of
recursive.
D
So
when
you
run
this
app
you
can
you
can
find
more
about
the
actions
I
showed
you
earlier.
If
you
want
to
go
back
to
our
red
hat
action
site,
you
can
go
to
the
github
actions
site
as
well,
and,
of
course,
together
we're
super
awesome
and
it
tells
you
how
two
four
easy
steps
configure
the
same
thing
and
you
can
then
of
course,
link
to
the
simple
app,
which
is
where
I
was
doing
all
the
work.
So
the
whole
thing
is
is
quite
quite
simple.
C
A
D
And,
of
course,
we'll
see
another
build
running
in
in
a
few
minutes,
we'll
we'll
see
that
running
and
I
won't
make.
I
won't
make
you
wait
for
that,
but
you'll
see
it
took
about
two
minutes
and
won't
take
much
longer
this
time.
So
the
next
demo
I
was
going
to
do
was
something
a
little
more
complicated
people
ask
us
a
little
bit
about
this,
so
I'll
close
these
for
now,
actually
enough
to
watch
all
this
stuff
happen.
D
This
will
be
updated
in
the
background,
but
the
next
demo
I'm
going
to
show
you
is
I
earlier
today
I
took
our
spring
pet
clinic
demo
and
I
did
a
did
a
demo
release.
I
didn't
upgrade
the
database.
I
just
did
a
quick,
quick
demo,
so
there
is
a
there's.
No
database
currently
running
I'll
show
you
that
little
error
message,
but
this
shows
how
you
could
use
your
spring
application
in
deploy
to
to
to
openshift.
So
I'll.
Take
you
through
that
one.
It's
it's
available
on
our
in
our
red
hat
actions.
D
Org!
I
happen
to
have
a
fork
of
it
so
that
I
can
have
my
magical
set
secret
script,
that
I
can
easily
whip
through
demos.
So
that's
convenient,
and
basically
I
was
the
interesting
thing
here
is
there's
a
few
actions
I
want
to
show
one
is:
we've
decided
to
make
this
another
demo
showcase
for
how
to
use
existing
actions?
So
if
you
want
to
use
a
one
of
these
plain
old,
docker
builds
and
pusher
image.
D
You
can
peruse
your
way
through
here
and
show
exactly
how
you
would
do
that
in
this
case,
we're
actually
using
builder
for
building
with
a
docker
file
and
basically
do
a
essentially
a
build
of
your
image.
And
if
I
I'm
interested
in
s2i,
we
did
a
sample
workflow
there.
That
shows
you
how
to
do
an
s2i,
build
and
pick
the
correct
java
and
those
kinds
of
things.
So,
if
you're
really
interested
in
taking
your
spring
application
and
learning
to
build
it
and
learning
to
push
it
to
an
openshift
cluster.
D
D
D
C
D
Find
my
location
for
this
fine
thing:
you
know
it's
just
the
browser
is
slow
there.
We
go
all
right.
Let's
push
this
now
and
not
worry
about
it
too
much,
so
the
the
browser
or
sorry
the
vs
code.
Finally
determined
it
was
changed
so
demo,
so
I
just
did
that
and
pushed
it
quickly
and
you'll
notice
that,
because
I
have
three
different
workflows,
they'll
all
start
running
at
the
same
time.
So
I'm
going
to
burn
a
little
bit
of
my
my
github
time
here
and
the
one
I'm
really
worried
about.
D
Is
this
one
or
paying
attention
to
you'll
notice,
it's
built
in
a
bunch
of
different
steps,
so
these
first
compile
step,
which
is
then
a
precursor
for
the
build
and
push
to
quay
and
then
it'll
deploy
to
openshift.
So
if
we
go
back
to
our
demo
a
little
bit
we'll
you'll
notice
that
we've
built
it
based
on
this,
you
know
these
sep
separable
steps
and
the
the
steps
then
can
be
dependent
on
a
previous
step
using
the
id
of
the
steps.
D
You
can
have
that
that
workflow,
that
we
just
showed
here
running
as
a
as
a
sequence
of
dependent
steps.
Okay,
so
this
this
doesn't
actually
shouldn't
take
that
long
as
well
and
when
it
finally
finishes
while
we're
at
it.
Let's
go
back
to
this.
This
one
probably
finished
right,
see
together
we're
super
awesome
and
so
is
openshift
comments,
so
that
was
my
previous
demo.
So
we're
going
to
just
stop
with
the
simple
demo
you
can
play
around
with
it.
D
D
D
If,
for
for
demos
and
for
day-to-day
stuff,
I've
been
able
to
incorporate
workflows
into
just
my
regular
projects
and
then
loop
in
my
my
sandbox,
and
so
whenever
I
I
play
around,
I
can
always
have
a
running
copy
of
my
my
application.
So
this
is.
This
is
part
of
what
I
would
consider
leverage
the
cloud
for
a
developer's
use,
and
so
you
know,
while
ci
cd
is
typically
for
you
know
a
lot
of
folks,
consider
it
prod
or
pre-prod
something
you're
going
to
deploy.
D
I
also
consider
it
something
that
you
end
up
using
as
part
of
your
day-to-day
development.
If
you
want
to
see
something
a
little
more
realistic
as
part
of
what's
going
to
happen
when
you
do
finally
get
ready
to
to
start
using
a
real
cluster
in
in
your
development
and
testing
so
and
when
this
finally
runs
we'll
see
a
version
of
it.
Hopefully
I
just
I
just
took
oh,
am
I
going
to
be
that's
the
docker
build
one,
there's
s2i
and
now
the
one
we
actually
care
about
is
deploying.
C
D
D
I
have
two
so
I
have
this
one
which
is
coming
up
still,
and
I
have
this
one
which
is
up
so
this
is
the
demo
live
one,
and
if
I
go
back
to
this
viewer,
it's
starting
and
if
I
go
to
my
logs,
I
can
actually
see
it's
probably
still
bootstrapping
a
little
bit,
but
we
can
always
find
out
by
clicking
here
and
checking
it
and
there's
the
new
version.
So
the
reason
I
I
put
this
in
the
demo
today
was
you
know.
D
I
realized
we
had
a
discussion
yesterday,
but
demoing
ci
cd
can
kind
of
seem
not
as
exciting,
but
let's
talk
about
how
you
would
use
this
one
here
I
have
my
two
versions
of
the
app
running
side
by
side.
So
if
you
don't
incorporate,
in
my
view,
something
like
an
openshift
cluster
or
if
you're
developing
kubernetes
something
like
a
test
environment,
where
you
can
run
things
like
side
by
side,
I
can
actually
then
have
testers
or
even
just
developers
go.
What
did
the
old
one?
Look
like?
Oh
look
and
go
to.
D
This
is
a
copy
of
the
new
one.
Oh
look,
that's
different
and-
and
I
can
then
run
them
side
by
side
when
you
do
this
locally
on
your
local
desktop,
you,
which
you
can
do
you're
ending
up
managing
ports
and
you're
into
changing
your
scripts
to
have
multiple
copies,
and
then
there
you
go.
You
can't
run
the
same
copy
out
of
the
same
directory.
You
got
to
check
it
out
multiple
times,
it's
all
sorts
of
stuff.
D
You
end
up
doing
manually,
while
here
there's
a
lot
of
things
that
just
are
kind
of
a
natural
way
to
do
in
the
cloud.
So
I
wanted
to
point
that
out
and
if
you're
considering
kind
of
using
some
of
the
stuff,
considering
incorporating
these
kind
of
new
ways
to
validate
your
applications.
And
I
found
that
github
actions
was
a
really
easy
way
to
do
this.
Because
it's
all
part
of
my
code
base
and
I
could
just
push
and
go.
C
D
D
So
this
one
is
is:
what's
called
an
application
called
graftuitis
it's
hard
to
pronounce,
because
it's
a
play
on
gratuitous
graphics,
it's
the
name
of
the
application
and
what
it
does
is
it's
it's.
It's
designed
to
show
how
you
can
build
slightly
more
complex
applications,
and
so
this
exact
this
actually
existed
before
and
when
I
started
to
github
actions,
work
last
fall.
We
decided
to
to
see
see
where
we
could
take
it
and
what
we
could
do
with
it.
This
one's
interesting
it
has
three
different
programming.
D
Languages
for
a
single
service
called
go
one
for
go
one
for
node
and
one
for
quarkus
in
java.
It's
got
a
front,
end
load,
balancer
that
I
inserted
for
for
convenience
and
it's
got
a
an
nginx
for
all
the
html
stuff,
and
so,
in
this
particular
case,
that's
this
application
here.
Actually,
let
me
show
you
the
application.
D
A
little
bit
applications
actually
running,
and
you
can
now
you'll
probably
figure
out
why
it's
called
gratuitous,
because
it's
using
gratuitous
graphics,
these
charts
mean
almost
nothing
because
they're,
basically
benchmarking
the
app
itself,
so
it
really
doesn't-
and
it
just
shows
you
some
intergalactic
numbers
flying
by
and
those
kinds
of
things
you
can
play
with.
You
know
a
number
of
requests
and
stuff
for
performance
and
other
testing,
which
we
can
actually
demonstrate
lots
of
interesting
things
on
the
cluster
like
scaling
and
other
things.
D
However,
today
I'm
just
going
to
demonstrate
a
a
change
it's
going
to
be
applied
dynamically
and
how
the
github
actions
that
we
put
together
work
to
make
all
of
this
stuff
happen.
So
I'm
gonna
go
down
here.
First,
I've
been
using
it
already.
So
I'll
show
you
what
I
did
one
this
morning.
You
can
probably
guess
when
I
show
you
the
last
few
action
runs.
What
I
did
to
set
up
that's
a
hint
yellow-
let's
close
some
of
these,
so
that
we're
not
going
to
get
buried
in
windows.
D
Now,
because
I
have
one
here
and
as
you
can
probably
guess,
yellow
refers
to
the
color
of
the
go
implementation
in
the
in
the
cluster,
which
you
can.
You
can
also
see
here.
You
can
see
the
yellow,
but
you
can
see
that
this
is
the
application,
and
this
is
nice
because
you
can
demo.
If
I
decide
to
go
for
two
pods
you
can,
you
can
demonstrate
that
eventually,
you'll
see,
there's
three
pods
instead
of
two
pods
you'll,
eventually
see
a
third
slice
once
it
once
it
scales.
D
D
Anyone
want
to
pick
a
color
in
this
case
just
to
I'm
going
to
first.
Do
the
change
I'm
going
to
take
you
through
how
this
particular
workflow
works
and
then
some
of
the
things
we
have
to
do
and
and
show
you
some
other
features
in
github
that
we
were
able
to
find.
So.
The
first
thing
I'm
going
to
do
is
to
my
go
application.
Instead
of
yellow.
C
D
D
Lo
and
behold
so
there's
the
three
node
sort
of
three
go
instances
I
earlier
scaled
up.
So
if
we
were,
if
we
were
running
auto
scale
and
other
things,
you
would
see
this
happen
automatically
when
we
push
it,
but
that's
not
what
we're
doing
today
we're
just
going
to
show
some
ci
and
cd
the
action
workflow
I
just
or
the
workflow
I
just
fired
off-
was
my
commit
for
pink
and
so
what's
going
to
happen,
is
this
workflow
is
going
to
just
do
us
very
similar?
D
D
This
here,
so
you
can
watch,
look
at
that.
There's
a
slice
disappearing
on
you
maybe
and
look
we've
already
built
and
deployed
the
pink
and
you
can
see
the
yellow
is
going
to
disappear
as
the
as
the
deployment
disappears
and
then
the
pink
start
to
start
to
get
the
two
deployments
and
I'm
going
to
show
you
how
all
of
that
kind
of
works.
So
it's
it's
gratuitous
graphics,
so
you
can
actually
watch
something
and
I
can
talk
to
changes
and
you
can
actually
visually
see
them
without
without
me,
going
hey
look.
D
But
I
want
to
show
you
a
few
of
the
interesting
things
that
we
did
here,
although
I
did
want
to
point
out
a
few
a
few
interesting
things.
One
is
I
I
regularly
normally
have
my
get
offs
repo
separate
from
my
dev
repo,
but
for
convenience.
I
made
a
mono
repo
for
this
demo
and
I
put
everything
in
one,
so
I
put
all
of
the
gear
ups
deployment
yamls
in
one
spot
and
I
put
all
of
my
services
in
one
spot
but
12
factor.
D
The
problem,
when
I
put
it
all
into
one
is:
I
was
building
five
images,
even
if
none
of
them
needed
to
be
changed.
So
I
added
a
facility
to
compute
the
changes,
which
is
your
basic
script,
using
a
diff
and
some
repping,
nothing
spectacular!
You
can
see
it.
The
there
is
a
get
a
bunch
of
github
actions
that
do
properly
detect
changes,
so
you
could
write
an
incremental
builder.
D
I
I
didn't
do
this
because
I
also
use
this
to
incrementally
build
locally,
and
I
I
was
using
this
script
already
to
go
and
diff
on
my
local
machine
and
I
use
the
same
script
on
github.
If
I
was
doing
just
a
github
diff,
I
would
use
the
github
action
and
I
can
actually
show
you
where
that
was
we
have.
D
We
use
it
in
a
bunch
of
our
red
hat
actions
as
a
way
to
determine
what
to
build
for
our
our
demos
and
for
our
actions,
and
so
I
selectively.
This
is
a
feature
I
can
selectively
run
steps.
So
when
so
just
to
map
it
back
to
what
you
saw
earlier.
You'll
see.
Some
of
these
steps
have
a
little
didn't
run.
They
didn't
run
because
they
didn't
need
to
run.
D
D
So
that's
a
that's,
unfortunately,
this
interestingly
long
thing.
Actually
that's
not
the
interesting
long
thing.
There's
a
patched!
That's
this
interesting
long
thing
that
will
patch
the
images
with
their
new
names.
So
so,
basically
this
is
an
all-in-one
script.
So
I
bring
this
up,
so
you
can
go
and
look
at
it
and
figure
things
out,
but
at
the
very
end
I
interact
with
github
itself
using
an
action
that
I
I
found
a
a
fellow
named
peter
evans,
who
does
quite
a
few
interesting
github
actions
and
after
my
pink
was
deployed.
D
Which
should
be
here
what's
happened.
Well,
the
previous
one
was
yellow
and
the
current
one
was
pink
well.
How
does
that
actually
work
in
a
in
a
git,
ops,
workflow?
I
need
to
change
my
repo,
so
what
I
did
is
incorporate
into
my
workflow
a
fairly
basic.
It's
not
super
fancy
action
to
send
myself
a
pull
request
and
that
action
will
then,
of
course,
send
one
and
the.
D
Let
me
see
where
I
am
here
so
there's
there's
the
commit
and
you
can
see
that
I
patch
the
old
image
to
the
new
image
and
then,
if
I'm
happy
with
that
deployment
now,
if
I
was
doing
a
b
roll
forward,
all
those
kinds
of
things
there
should
be
some
automation,
but
I'm
showing
this
demo
manually.
If
I'm
happy
with
this,
I
can
just
take
it
and
since
it's
all
ready
to
go,
I
can
merge
it
happy
happiness.
Is
me
and-
and
I
can
delete
the
branch
too,
because
I
don't
really.
C
D
Local
deployment-
I
should
see
the
old
one
here,
but
if
I
will
pull
back
to
get
myself
in
sync,
I
see
it
changed.
Hopefully
you
spotted
that
to
the
new
tag.
So
this
is
me
running
a
full
end
to
end
ci
cd
out
of
github,
just
for
myself,
with
the
full
get
ops
kind
of
workflow
to
determine
what
gets
released
and
I
can
go
back
to
any
previous
release
and
and
and
it's
all
tagged
through
these-
these
pull
requests.
D
D
So
those
are
the
demos
we
were
going
to
basically
run
through
today
and
I
was
going
to
just
end
with
a
couple
of
things
and
then
go
back
to
some
charts,
and
then
we
can
go
to
the
questions
we'll
have
plenty
of
time.
I
hope
if
there's
any
good
questions
we'll
see
I
wanted
to,
I
want
to
point
out
stuff.
D
We
haven't
demoed
and
then
we'll
talk
about
a
little
bit
today
we
build
also,
if
you
want
to
run
for
openshift
users
who
may
want
to
run
a
an
action
or
workflow
on
their
own
self-hosted
cluster
on
their
own
cluster.
They
can
install
these
pre-built
images.
There's
a
there's,
a
there's,
an
installer
here
for
this
there's
a
openshift
action
runner
chart.
So
this
chart
here
is
a
helm
chart
which
will
allow
you
to
install
and
run
any
runner
on
your
local
cluster.
D
So
if
you
want
to
do
some
of
this
stuff
and
for
some
reason
you
feel
it's
something
you'd
like
to
run
on
your
cluster
now
in
some
cases,
maybe
you
don't
want
to
do
the
build
on
your
cluster,
but
you
might
want
to
do
some
testing
on
your
cluster,
which
is
already
pre-configured.
This
is
a
perfect
way
for
you
to
get
github
to
launch
and
execute
on
your
cluster.
The
nice
part
about
this
particular
case
you
could
you
can
you
can
also
the
nice
part
about
this
particular
case
is.
D
I
can
also
use
this
with
other
open
shift
or
red
hat
tools
like
code
ready
containers
which
runs
on
my
desktop
it'll
wait
for
work
from
github
and
I
could
be
doing
things
like
running
testing
and
other
things.
So,
if
you're
interested
in
this
workflow,
I
I
encourage
you
to
go
and
look
at
the
runner
chart.
D
There
is
it's
pretty
it's
pretty
nice
and
if
you
want
your
cluster
as
part
of
your
your
own
personal
cluster
or
something
as
part
of
your
your
dev
cycle,
that's
a
great
way
to
do
it
and
it's
and
it
works
with
things
like
our
crc
on
the
desktop
the
other
stuff.
I
wanted
to
point
out.
If
you
we
didn't
demo
today
but
is,
is
a
great
way
to
learn.
We
have
k
native
integration,
and
so
we
we've
done
some
action.
D
Okay,
so
I
encourage
you
to
go
and
and
and
see
some
of
this
stuff,
you
may
not
be
able
to
use
the
k
native
with
the
sandbox
yet,
but
if
you
have
a
cluster
that
can
run
open
shift,
serverless
you
should
be
able
to.
You
should
be
able
to
try
this
one
out
and
get
yourself
get
yourself
going
the
spring
pet
clinic.
Of
course,
this
is
where
I
forked
mine
to
to
show
you
the
demo
today.
D
I
didn't
really
do
a
lot
of
work
other
than
than
you
know,
forking
it
and
filling
in
some
secrets
in
a
little
script,
a
bunch
of
direct
actions
for
talking
to
openshift
and
there's
one
more.
I
really
want
to
talk
about
here
as
soon
as
I
scrolled
past
it
that
put
some
a
little
bit
of
thought
into
it.
This
one
here
so
github
comes
with
a
large
set
of
pre-installed
binaries
in
their
github
hosted
runners,
which
are
really
convenient
because
you
have
to
install
them.
It's
instant.
D
This
is
a
way
to
do
it
and
it's
a
standard
way.
You
don't
have
to
go
around
figure
out
where
the
downloads
are.
So
it's
a
really
convenient
way,
because
I
have
this
myself
where
I
need
version
x
and
I
just
don't
know
where
to
find
it.
I
go
to
rummage
around
the
mirrors
and
those
kinds
of
things
to
find
it.
In
theory,
you
know
in
the
real
world
or
in
an
ideal
world,
you
wouldn't
need
to
be
versions
dependent,
but
in
the
real
world,
you're
often
tied
to
versions.
D
So
we
have
this
model
where
you
can
install
the
correct
lineup
and
we
optimize.
So
if
github
has
the
correct
binary
that
you're
asking
for
it's
a
no-op
for
instance,
but
if
it
ever,
if,
if
it
ever
moves-
and
you
were-
and
you
wanted
to
ensure
that
your
versions
to
that
version,
then
you
can
actually
use
this
and
you
can.
You
can
find
one
or
more
command
lines,
and
this
is
our
strategy
for
ensuring
that
any
command
line
that
you
can
get
from
red
hat
through,
for
example,
the
command
line
tool,
installer.
D
D
C
D
With
that,
I
think
we're
done,
except
for
this
cool,
so
I
did
want
to
go
through
this
just
quickly
and
then
questions.
I
think
we
did
our
timing
just
right,
john.
So
this
is
our
roadmap
with
vague
near-term
midterm,
long-term
meanings.
I
do
want
to
point
out
if
you've
watched
me
scroll
through
all
this
stuff,
we've
pretty
much
completed
everything
in
the
near
term
and
we're
going
to
move
on
to
the
midterm.
D
Our
near-term
goals
were
basic
authentication
deployment,
cli
installer,
which
I
just
showed
you
cli,
that
are
specific
to
build,
k,
native
and
all
in
the
marketplace.
So
very,
very
much
a
bootstrapping.
We
have
a
single
user
runner
which
you
can
install
via
that
helm
chart,
so
that's
there
and
we're
working
still.
D
This
is
coming
at
some
point
fairly
soon
on
an
a
single
user
bot
that
you
can
install
on
your
openshift
cluster
and
that
will
manage
those
secrets
for
you
that
I
was
so
instead
of
you
having
to
type
in
you
know
my
version
of
this
which
queries
the
server
I'm
going
to
and
queries
the
server.
For
the
token,
it's
going
to
do
it
for
you,
and
you
won't
have
to
bother
with
all
that,
so
we're
trying
to
make
that
user
experience.
Oops
very
simple.
D
D
Again,
I
had
to
manage
these
secrets
and
other
things
we
wouldn't
mind,
making
it
a
lot,
a
lot,
smoother
experience
to
get
a
sandbox
and
work
with
github,
so
hopefully
in
a
future
demo.
You
won't
watch
me
click
around
a
lot,
you'll
see
just
smooth,
you
know
getting
stuff
built
and
deployed
and
then
of
course,
the
longer
term.
You
know
execution
on
pipelines
on
openshift
pipelines.
D
So
if
you
want
to
want
to
actually
leverage
the
openshift
cluster,
be
configured
for
security
or
be
configured
for
larger
things,
larger
heaps
larger
memory
than
might
be
available
on
github,
although
github
is
very
generous
with
their
seven
gig.
That's
pretty
much
big
enough
for
anything.
However,
there
are
things
that
do
exceed
that
and
then
some
other
ui
things.
D
D
A
D
A
D
Is
that
correct
and
I'll
answer
I'll
answer,
the
red
hat
one,
which
is
you
go
to
the
red
hat
actions
org,
where
the
link
is
that
I've
been
demoing
and
create
a
create,
a
new
issue
of
what
you
want
as
a
feature
and
we'll
prioritize
it
in
our
planning,
which
is
done
in
a
project
on
that
on
that
organization?
So
if
you
have
a
feature
request-
or
you
want
to
anything
that
you
want
to
talk
to
us
about,
we
hang
out
on
github
as
you'd
expect.
B
C
A
C
D
D
There
was
a
vpn
feature,
we're
looking
at
what
it
would
take
for
you
to
enable
a
tunnel
from
github
back
to
your
private
cluster,
but
only
for
you
which
would
then
it
then
lets
you
treat
your
private
clusters
just
like
just
like
something
on
the
public
internet,
but
it
wouldn't
go
through.
You
know
that
doesn't
need
a
public
dns,
the.
So
that's
the
that's.
The
sort
of
the
the
downside
of
having
sort
of
stuff
behind
the
firewall.
There's
two
use
cases
that
we've
seen.
D
However,
one
is
a
lot
of
customers
who
have
github
enterprise
they're
on
the
correct
side
of
the
firewall
when
they
run
actions
or
when
they,
if
they're,
having
actions
running
a
github
enterprise,
so
they're
on
the
correct
side
of
the
firewall.
So
a
bunch
of
this
stuff
will
still
work
in
an
enterprise
kind
of
context
and
then
the
the
last
point.
I
want
to
make
is
things
like?
The
github
runners
are
a
outward
connect
model.
C
D
C
A
D
Yeah,
that's
it's
that's
one
of
the
bigger
bigger
problems.
We
see
it
for
even
things
like
web
hooks,
for
example,
so
you
see
redirectors
to
go
from
and
then
of
course
you
have
ssl
issues
because
you
don't
want
github
needs
a
secure
connection
to
post
web
hooks.
It's
the
same
essential
problem
of
having
a
public
service
talk
to
private
behind
the
firewall
networks.
D
D
B
Yeah,
I
know
we
have
a
mixed
audience
today,
so
I
just
wanted
to
point
out
that
there
are
a
few
different
variants
of
github
there's
like
the
github.com
version.
That's
free
to
use
there.
There
are
different
paid
tiers
of
that
as
well,
including
an
enterprise
cloud
and
github
actions
is
available
on
all
those
and
also
the
on-premise
github
enterprise
server.
So
it's
worth
trying
out
in
that
context,
too.
D
Yeah
so
yeah,
so
if
you,
if
you
have
general
enterprise
with
actions-
and
you
want
to
try
our
actions,
one
of
the
things
that
we
we're
trying
to
ensure
is
that
we
work
transparently
with
enterprise
and
github.com
the
public
sas.
The
only
real
difference
is
the
api
endpoints.
So
you
have
to
you
know.
Sorry,
the
only
the
major
difference
is
the
api
endpoint.
So
everything
should
work
as
long
as
you're
considerate
of
the
environment.
That's
it's
being
run
in.
D
B
D
B
Yeah
and
there's
a
detail
there
that
if
you're
on
github
enterprise
server
you're
not
going
to
be
able
to
reach
out
to
public
actions
like
red
hats
out
of
the
box,
you
need
to
enable
a
feature
called
github
connect
and
you
can
google
the
documentation
for
that.
I
can't
do
two
things
at
once,
or
I
would
do
that
too.
But
github
connect
will
allow
you
to
say
you
know
red
hat
action,
slash
you
know,
oc,
installer
and
and
use
those.
A
B
B
C
D
So
I
can.
I
can
comment
a
little
bit
on
that
from
our
roadmap
perspective.
So
github
app
has
a
very
nice
way
to
give
you
fine
grain
control
access
to
your
github
repository
or
organizations.
You
could
have
an
app
that
says.
I
just
need
repo
access
or
I
just
need
access
to
workflows.
So
it's
essentially
a
way
to
create
bots
for
yourself
to
do
things
autonomously
and
so,
and
the
install
experience
is
quite
easy.
D
What
did
I
forget
to
set,
because
you
should
have
seen
these
demos
the
early
days,
I'd
forget
to
set
the
secret
and
then,
after
should
do
it
twice
and
you'd
watch
me
debug
for
a
while,
so
automate
all
of
that.
So
the
experience
is
very
smooth
in
using
the
two
together,
but
only
with
the
rights
that
are
needed,
as
opposed
to
a
full
oauth
token,
which
is
pretending
to
be
you
and
only
you
which
has
unlimited
power.
D
B
B
You
know
your
enterprise
instance
and
they
can
also
take
or
they
can
be
permitted
to
act
as
the
user,
so
you
can
send
a
github
app
user
through
the
oauth
flow
and
do
the
normal
oauth
dance
and
and
do
something
that
pretty
much
everybody
is
familiar
with,
but
it's
a
flexible
model.
I
encourage
you
to
check
it
out.
A
A
B
I
can't
speak
to
the
plans,
the
the
build
scripts
that
we
use
to
to
make
those
vms
are
available.
I
just
sent
a
link
to
the
virtual
action
virtual
environments,
repository
where
all
that
happens,
but
I
don't
think
the
the
image
itself
is
available
right
now.
I
want
to
say
it's
for
licensing
reasons
of
the
software,
that's
included,
but
I'm
not
sure
on
that.
A
D
It's
nice
to
hear
we.
We
actually
met
yesterday
to
talk
about
the
kinds
of
messaging
and
demo
kind
of
stuff.
So
it
was
it's
good
to
hear
that
the
discussion
was
useful
for
everybody
and
but
yeah.
If
you
see
us
on
see
us
on
our
our
red
hat
actions
github.
So
if
you
need
to
know
things
or
want
to
know
things,
if
you
can
always,
of
course,
I
work
at
red
hat.
D
So
if
you're
from
red
hat
you
just
you
can
you
can
find
me,
I'm
sure,
but
I'm
pretty
pretty
easily
accessible.
So
anything
you
need
to
know.
I
can
certainly
find
find
out
stuff
for
you
if
you,
if
you
want
so,
but
thanks
for
the
feedback
on
the
on
the
demos,
we're
trying
to
make
them
kind
of
useful
and
not
just
watch
me
run
something.