►
Description
In this session we will explore how organizations can become more productive, efficient, and effective by improving their DevOps strategy. We will discuss how we can change the way Development, Security, and Ops teams collaborate and build software and walk through a demo showing the day in the life of a developer including a walk through of the pipeline and how to deploy an application to OpenShift.
A
All
right,
we
are,
we
are
live.
We
are
live
here
today.
This
is
the
open
shift.
Commons
briefings
operator
hours,
and
today
we
have
some
very
special
guests
here
from
git
lab,
so
we've
got
darren,
darren
eastman,
he's
a
senior
product
manager,
hey
darren.
How
are
you
and
then,
and
then
we've
got
pete
rahman
who's,
the
federal
solutions,
architect
and
we've
been
talking
this
morning,
while
we've
been
getting
ready
to
getting
ready
to
get
going
about
is
winter
in
fact
over
and
can
we
put
the
snowblowers
away
and
so
forth?
A
D
A
C
C
So
this
is
this
is
my
third
year
here,
so
I
I
feel,
like
I've
got
a
little
bit
of
time
under
my
belt
and
as
well.
My
focus
being
on
the
channel
team
working
with
red
hat
has
been
on
openshift
for
the
past
few
months
or
actually
longer
than
that.
My
participation
has
been
writing
a
lot
of
documentation.
C
C
A
B
A
B
So
I
joined
gitlab
in
september
of
2019,
specifically
as
a
product
manager
for
github
runner,
which,
which
we
will
be
chatting
about
today.
Git
fat
burner
is
a
high
level,
is
the
is
the
engine
that
makes
kitab
ci
work.
What
makes
me
an
expert,
I
guess
I've
been
an
entrenches
here
at
get
that
for
just
you
know.
You
know
a
year
and
a
half
now
and
working
in
all
things,
runner,
which
is
a
very
interesting
space,
because
we
get
to
touch
a
number
of
different
technologies
such
as
openshift.
B
I've
been
working
with
the
red
hand,
openshift
team.
Now
I
think,
very
closely
on
getting
the
run
operator
going,
maybe
for
the
past
six
or
eight
months,
and
so
I
wouldn't
say
I'm
an
expert,
but
I
certainly
put
up
from
a
lot
of
our
customers
and
users
in
terms
of
the
features
and
capabilities
that
they're
looking
for,
and
so
if
that
makes
me.
A
A
Okay,
well,
I
I
would
imagine
that
your
your
managers
and
your
managers
managers
wouldn't
have
wouldn't
have
signed
you
up
to
be
our
victim
for
the
show
here
today.
If
you
folks,
weren't,
pretty
pretty
comfortable
with
that
so
git
lab
we've
been
working
with
your
team
to
get
your
operator
built,
tested
and
certified
for
open
shift.
B
A
B
That's
a
great
question
and
that's
kind
of
the
beauty
of
of
gitlab
and
gitlab
runner.
So
in
terms
of
git
lab
runner
itself,
you
know
with
different
choices
as
a
gitlab
user
or
customer,
it's
kind
of
just
stepping
back.
You
can
subscribe
to
our
gitlab
sas
offering.
So
if
you,
you
know
your
security
requirements
are
compliant
compliance
requirements
allow
for
it.
You
can
just
basically
subscribe
to
gitlab
stats.
You
don't
actually
have
to
install
an
on-premise
version
of
git
lab
or
get
that
runner.
B
But,
as
you
well
know,
as
everyone
is
probably
in
the
call
well
knows
they
have
different
security
and
compliance
and
setup
requirements.
So
with
that
we
have
the
flexibility
of
being
able
to
install
both
gitlab
and
the
github
runner
on-prem
in
the
cloud,
different
platforms
of
choice
and
so
on
and
so
forth.
A
Okay,
so
present
company
excluded
with
you
and
pete,
tell
me
what
business
problems
git
lab
solves
for
customers,
meaning
like
at
a
very
high
level.
You
know
how
do
people
survive
without
gitlab?
What
you
know,
what
what
is
what
does
it?
Do
I
mean
if
someone
said
to
me:
hey
great
red,
you
know
awesome,
so
you
work
at
red
hat.
What
does
red
hat?
Do
I
would
say
you
know?
A
Well
you
know
we
we
made,
you
know
the
first
enterprise
commercially
supportable
linux
distribution,
which
helped
our
customers
migrate
off
of
proprietary
spark
solaris
platforms
years
ago
and
then
through
acquisitions
and
and
technology
development
we've.
You
know,
we've
built
openstack
distributions
which
help
customers
in
the
telco
space-
and
you
know
these
days,
ansible
and
management,
and
and
certainly
openshift
as
a
kubernetes
orchestration
platform.
A
B
That's
a
great
question:
in
the
simplest
term,
I'm
going
to
use
something
that
I
sell
for
one
of
our
cfo's
cheddar.
He
had,
in
its
simplest
terms,
get
that
helps
teams,
collaborate
on
software
development
and
project
management
in
its
very
simplest
terms,
right,
it's
you
basically
give
that
as
a
the
one
platform,
the
one
tooling
of
choice
for
doing
software
development.
So
it's
an
enabler
of
innovation.
If
you
kind
of
think
back,
michael
to
maybe
10
15
20
years
ago,.
D
B
Develop
software
back,
then,
is
completely
different
from
how
we
develop
software
now
and
our
expectations
in
terms
of
users
as
well
as
our
executives.
In
terms
of
how
fast
we
should
innovate,
how
fast
we
should
deliver
new
features
to
market
has
completely
changed,
and
so
github
is
that
one
software
platform
that
is
revolutionizing
how
you
think
about
developing
software.
So,
instead
of
having
multiple
point
solutions
for
project
management
for
software
configuration
management
for
security
testing
for
ci
cd,
you
have
everything
in
one
platform,
one
platform
and
one
collaboration
tool.
B
A
So
if
people
either
on
facebook
or
youtube,
have
questions
for
pete
or
darren,
please
put
it
into
the
the
chat
box
and
our
producers
will
make
sure
that
those
questions
get
picked
up
and
brought
over
here,
and
we
can
get
those
addressed
and
the
same
thing
for
those
of
you
who
are
on
the
bridge
here.
Please
drop
your
questions
into
chat.
C
A
C
A
You
know,
because
you
guys
are
one
of
our
marquee
customers
and
you
guys
are
so
interesting.
We
wanted
to
make
sure
that
you
had
an
opportunity
to
be
here.
You
know
and-
and
you
know
talk
about
your
technology
here
on
our
show
when
we
get
done.
If
you
guys
wanted
I'd
like
to
send
you
some
of
these
shirts
and
you
can
use
them
on
your
on
your
on
your
your
zoom
conferences
and
so
forth,
and
maybe
even
one
for
your
manager
pete,
you
know
if
I
hear
he's
a
big
t-shirt
fan
anyways.
C
C
C
C
And
again
make
sure
that
we're
in
the
right
name
space
go
ahead
and
install
it,
and
so
basically
what
this
is
doing
is
it's
installing
the
operator
as
a
prerequisite
for
us
to
actually
install
the
runner
in
a
little
bit.
So
once
we
have
this
operator
installed,
let's
just
go
ahead
and
take
a
peek
at
it.
Real
fast
make
sure
everything's
out
there
we'll
go
into
installed
operators,
we
see
it.
There
switch
over
to
the
developer
view
and
we
can
see
that
the
operator
is
there,
so
everything's,
fine
and
dandy.
C
So
what
we're
going
to
do
now
is
we're
going
to
jump
into
the
get
lab
side
of
the
house
and
we're
going
to
actually
start
creating
a
project
and
you're
going
to
see
once
we
jump
over
there
that
you
know
there's
many
ways
to
start
a
project:
we're
going
to
go
ahead
with
importing
a
project
which
again
many
ways
to
import
projects
with
into
gitlab
we're
going
to
do
a
repo
by
url.
So
this
is
an
existing
project.
C
So
now
that
we've
got
the
project
set
up
it's
time
for
us
to
go
ahead
and
start
building-
and
this
is
where
the
fun
stuff
starts.
This
is
where
we
start
building
the
the
runners
actually
installing
them
so
by
default.
Gitlab
allows
you
to
utilize
shared
runners
throughout
an
instance
of
gitlab,
we're
not
going
to
use
that
for
right
now,
so
I'm
going
to
go
ahead
and
disable
that
and
what
we
are
going
to
do
is
make
use
of
the
area.
C
The
section
that
allows
us
to
create
a
runner
manually,
because
you
know,
like
I
said
runners
in
the
server
instance-
are
two
different
pieces
of
software.
Generally
speaking,
you're
going
to
run
the
runner
on
a
different
virtual
machine
or
different
piece
of
hardware
just
to
keep
that
utilization
off
the
server.
C
So
we're
going
to
grab
this
token
and
what
I
did
is
I
actually
cut
and
pasted
it
into
a
command
that
we're
going
to
use
in
a
little
bit
and
first
we're
going
to
switch
over
to
the
to
the
correct
project
and
excuse
my
slow
typing.
That's
one
thing
that
I
was
never
fantastic
at
and
to
save
you,
the
pain
of
watching
me
type
along
command.
I
went
ahead
and
cut
copied
this
next
command
and
you'll
see
at
the
very
end
of
this
command.
C
That
is
the
token
that
I
just
grabbed
from
the
gitlab
side.
So
again,
this
is
what
associates
the
runner
that's
going
to
be
on
openshift
to
my
specific
project.
Now
runners
can
be
done
at
different
levels.
You
know
group
level
at
the
instance
level,
but
what
I'm
creating
right
now
is
a
runner
specific
to
my
project,
and
so
that
was
the
secret
that
we've
done
and
and
we're
going
to
create
a
crd
file
here,
which
I
already
did
beforehand,
so
you
wouldn't
have
to
watch
me
actually
type.
This.
C
C
Now,
with
that
said,
if
I
pop
over
to
the
the
openshift
side,
you're
gonna
see
that
we're
spinning
up
a
runner
as
we
speak.
So
not
only
is
this,
you
know
it's
taking
the
crd
file
that
we
used
it's
building
the
runner
based
on
that
and
it's
also
registering
it
with
gitlab.
So
so
it's
it's
basically
reaching
out
to
the
gitlab
instance,
basically
straight
to
the
product
or
on
project
and
registering
it
with
that
project.
So
now,
if
I
jump
over
to
the
developer
viewer
fast,
you
can
see.
We've
got
our
operator.
C
We've
got
our
runner
spun
up,
so
it
looks
like
we're
pretty
good
from
the
open
shift
side.
Let's
check
the
the
get
lab
side
as
well
and,
like
I
said
so,
we
basically
registered
that
runner
with
gitlab.
So
now,
when
you
go
to
available
specific
runners,
you
can
see
that
there's
a
brand
new
runner
there,
that's
the
one
that
I
just
created,
I'm
not
going
to
use
tags
in
this
demo,
so
I'm
gonna
un
or
check
that
box,
and
I
also
kind
of
like
to
track.
C
C
So
when
you
start
talking
about
pipelines,
you're
going
to
see
that
there's
stages
and
jobs-
and-
and
this
is
what
defines
those
stages
it
defines
what's
in
a
stage-
it
defines
a
job-
it
defines
what's
in
the
job
when
the
job's
going
to
be
run,
how
it's
going
to
be
run.
What
images
it's
using
you
can
see
here,
there's
scripting
commands
there.
You
see
a
series
of
oc
commands
in
here,
so
this
is
and
I'll
come
back
to
this
in
a
little
bit.
C
And
this
is
the
pipeline
that
that
ci
yaml
file
built
right,
so
you
got
the
four
stages
that
go
across
the
from
left
to
right
and
then
you've
got
the
jobs
within
each
stage.
Now,
if
you
were
to
you
know,
this
is
a
very
simplistic
pipeline.
If
you
were
to
add
things
like
security
scanning
license
scanning,
you
would
basically
use
that
ci
ci
yaml
file
that
I
showed
you
and
build
it.
C
Those
parts
into
these
stages
right,
you
might
create
a
new
stage
called
scanning,
or
something
like
that,
where
you
add
these
other
stages
into
your
pipeline,
so
that
that
way,
it's
run
each
time
that
you
run
through,
therefore
giving
you
that
ability
to
run
all
the
scans
that
you
need
to
run
each
time.
You'll
see
that
I
did
set
this
up
to
be
a
manual
deploy
just
because
I
like
to
have
that
manual
step
before
I
actually
deploy
anything
out
into
production
and
what
it's
doing
right
now.
C
C
And
what's
going
to
happen
is
basically
it's
going
to
bring
up
our
tanuki
tanuki
tech
portal
that
we
utilize
for
our
fictitious
work
that
we
do
at
our
fictitious
company
all
right?
Let's
go
ahead
and
fire
it
up
see
if
it
works
so
there
it
is
so
we've
got
our
portal.
Everything
looks
fantastic,
but
there's
a
problem
again.
I've
told
you
my
typing
skills
aren't
great.
C
So
what
we
do
is
we
use
these
things
called
issues
right.
So
we
go
into
our
issue
tracker.
We
have
our
issue
boards
and
this
allows
us
to
open
up
issues.
An
issue
is
something
like
you
know:
opening
up
a
feature,
enhancement
request
or
a
bug
fix
or
something
along
those
lines,
and
that's.
This
is
where
we
manage
those.
So
you
know
maybe
a
tester
is
inputting
this
or
somebody
from
a
project
team.
C
So
we're
going
to
go
ahead
and
open
up
an
issue,
and
you
know
related
to
this
problem
that
we
found
on
the
website
we'll
submit
an
issue.
The
issue
and
excuse
me
immediately
to
the
right
hand,
side
you'll,
see
that
there's
various
things
that
I
can
do,
I'm
basically
assigning
to
this
to
myself.
Just
because
that's
who's
gonna
fix
it,
but
you
know.
Basically,
this
can
be
an
assignee
to
a
person
or
persons,
multiple
people,
you
know
that
might
be
actually
working
on
this
problem.
C
You
can
do
other
things
like
assigning
it
to
epic
milestone,
work
on
time,
tracking,
give
it
a
due
date.
We're
also
going
to
work
with
labels
here.
So
these
are
customized
customizable
labels
I'll
give
it
a
critical
status
so
that
that
way,
you
know
you
can
keep
your
issues
labeled
and
organized
in
that
way.
So,
diving
actually
into
the
issue.
We
can
see
a
little
bit
more
about
the
you
know
the
meat
of
the
problem,
and
this
is
where
you
get
a
little
bit
descriptive.
C
C
What
you
didn't
see
me
do
was
I
got
a
screenshot
of
that
problem
on
the
previous
screen
and
with
the
portal,
and
what
we
can
do
is
basically
take
that
screenshot
and
literally
just
drag
and
drop
it
into
the
issue
which
allows
us
to
have
a
you
know
that
picture
you
know
pictures
worth
a
thousand
words
sort
of
a
thing.
So
let's
go
ahead
and
look
at
the
preview
there.
It
is
so
that
way.
Whoever
gets
this
issue
will
understand
a
little
bit
better.
C
What
what
to
look
for
and
what
the
fix-
and
that
said
so.
This
is
a
starting
point
for
whoever
put
in
the
issue
and
that's
that
collaboration
now
begins
from
that
issue,
but
then,
now
that
I'm
going
to
start
to
work
on
it,
I'm
going
to
go
ahead
and
create
a
merge
request.
The
merge
request
is
where
everything
all
the
magic
really
starts
to
happen
here.
All
the
work
really
begins.
You're
going
to
see
things
like
commits
and
changes
and
some
other
info
in
there.
C
What
we're
doing
right
now
is
we're
building
out
a
a
separate
branch
for
us
to
actually
work
on.
So
you
know
we
don't
want
to
be
working
on
master,
impacting
production
in
any
way,
so
get
lab
in
the
background
is
actually
spinning
up
a
separate
bubble.
If
you
will
for
us
to
do
all
of
our
testing
and
viewing
of
the
application.
C
So
once
we
do
this
merge
it's
going
to
close
out
the
issue
and
everything
will
be
done
so
that
person
that's
working
on
it
can
move
on
to
the
next
to
the
next
job,
and
you
know,
like
I
said
this-
this
merge
request
is
going
to
be
a
record
of
all
the
collaboration
that
occurs
throughout
this
change.
So
you
can
see
here
that
we're
actually
get
labs
automatically
kicked
off
a
process
in
the
background
to
create
a
new
branch.
C
Again,
a
sandbox
that
we
can
do
our
work
without
impacting
any
production,
and
you
know
it'll
also
make
use
of
an
approval
process
for
us
to
to
put
the
changes
into
production,
but
for
now
now
that
we've
got
that
ready
for
us
to
start
working.
Let's
start
working
now,
obviously
you
know
most
people
might
use
their
own
local.
C
Applications
to
do
the
web
work
or
do
the
programming
work
so
here
we're
using
it
gitlab's
very
capable
web
ide,
which
comes
as
a
part
of
the
product.
So
you
know
basically
allows
me
to
do
the
work,
let's
say
from
even
an
ipad.
You
know,
while
I'm
on
the
road,
so
in
case
you
can't
get
to
your
local
ide,
which
is
really
nice.
Once
we
make
the
change,
we
go
to
a
split
screen
and
the
spritz
this
the
split
screen
allows
us
to.
C
So
again,
you
know,
gitlab
is,
is
very
good
at
automating
the
process
and
making
things
quicker
and
what
you're
going
to
see
here.
If
you
look
on
the
very
bottom
left
corner
there,
you're
going
to
see
us
kick
off
a
new
pipeline
there,
it
goes
we'll
jump
into
that
pipeline.
Real
fast
and
so
what's
happening
here
is
we're
running
another
pipeline
again.
This
is
these
pipelines
are
customizable
to
do
whatever
you
need
to
do
whatever
scripts
you
need
to
do
whatever
scans
you
need
to
do.
C
This
is
a
very
simplistic
one
and
we're
what
we're
doing
is
deploying
the
application
back
into
its
own
bubble.
So
you
know
we're
not
going
to
production
at
this
point,
but
we
are
taking
the
changes
that
we've
made
and
deploying
that
into
our
our
bubble
right
now
for
testing-
and
this
is
a
big
advantage-
you
know,
particularly
if,
if
you're
gonna
have
approvers,
you
know
approving
before
this
application
goes
live
so
going
back
into
the
to
the
merge
request.
C
You
know
this
is
I
I
told
you
this
is
where
you
know
the
rubber
hits
the
road
sort
of
a
thing.
This
is
if
I
was
an
approver,
I
would
come
in
here
and
I'd
have
these
various
things,
various
information
for
me
to
look
at
such
as
the
commits
that
it
occurred
right.
So
you
only
saw
me:
do
one
commit,
so
it's
literally
just
that
one
commit
at
the
time
you
see
the
pipelines
and
the
great
part
about
this.
Is
you
know
if
there's
any
part
of
the
pipeline
that
didn't
complete?
C
We
can
hover
over
things,
and
you
know
drill
down
on
things
and
see
what
failed,
how
it
failed,
why
it
failed.
We
can
get
into
the
raw
output
to
really
start
figuring
out
what
happened
in
this
case.
You
can
see
that
my
great
programming
skills
went
straight
through
with
no
problems.
You
can
also
see
the
changes
that
were
made
so
again.
You
know
this
is
great
from
approver
standpoint
if
they
want
to
see
all
those
bits
of
information.
C
As
you
know,
in
terms
of
the
actual
approvers
themselves,
it
can
be
a
single
approver,
multiple
approvers.
It
could
be
a
group
of
people
and
maybe
let's
say
you
know,
seven
out
of
ten
people
need
to
approve
this
before
it
goes
through
sort
of
a
thing,
so
just
a
way
to
keep
an
eye
on
the
project,
and
you
know
keep
that
authority
in
check.
In
this
case,
though,
I'm
not
using
any
approvers.
C
In
real
life
scenarios,
you
would
see
more
pipelines
more
commits
and
a
lot
more
activity
in
terms
of
collaboration.
Here,
we've
kicked
off
another
pipeline,
so
this
is
again
you
know
going
back
to
the
ci
yaml
file.
You
know
we're
basically
using
that
file
just
to
refresh
your
memories
to
build
out
that
pipeline
and
it's
you
know
it's
a
critical
piece
in
the
sense
that
again,
if
you
wanted
to
add
your
security
scans,
your
license
scans
or
you
know,
modify
the
jobs
to
do
certain
things.
C
You
know
this
is
how
you
do
it
and
where
you
would
do
it,
you
can
see
in
the
very
bottom
there
you
see,
when
is
manual,
for
instance,
that
you
know
that
could
be
switched
to
automatic
or
just
remote,
remote
or
removed
out
to
allow
the
the
process
to
go
all
the
way
through
without
that
manual
step
that
I
added
in
it's
a
sanity
thing
for
me.
I
just
like
to
be
able
to
push
the
the
manual
button
right
there
as
needed.
C
C
You
can
see
that
the
merge
requests
are
gone,
the
one
is
closed
out
and
that
in
turn,
if
we
go
into
our
issue
boards,
you
can
see
it's.
The
issue
is
no
longer
open,
so
we
keep
everything
integrated
with
each
other.
So
that
way
you
know
project
from
a
project
management,
standpoint,
everything's,
nice
and
clean
and
we'll
head
back
to
openshift
and
we'll
check
to
see
how
our
application
is
doing.
C
C
Yeah,
I
I
don't
have
a
an
open
shift
instance
available
to
me
at
the
time
we
are
building
that,
but
just
to
recap,
kind
of
you
know
what
we
did
there
is.
You
know
we
started
off
in
openshift
we
created
a
namespace,
then
we
added
the
operator
in
we
popped
over
to
gitlab.
We
created
a
new
project
and
from
there
we
we
created
the
new
runner
put
that
into
openshift.
C
We
then
were
able
to
provision
our
first
version
of
the
application
out
to
openshift.
Once
we
did
that
you
know,
then
that's
where
we
kind
of
went
through
the
entire
software
development
life
cycle
within
a
single
application.
Where
you
know
we
saw
there
was
a
problem.
We
opened
up
an
issue.
We
went
immediately
into
the
merge
request
to
work
on
that
problem
where
we
did
all
sorts
of
you
know,
security
scanning
license
scanning
and
all
the
you
know
the
tests
that
we
need
to
run
on
those
things.
C
A
A
D
A
B
C
Yeah,
so
we
definitely
do
we
have
many
deployment
options
available,
so
obviously
the
various
linux
instances,
but
you
know
as
well
as
you
know,
we
have
sas
available
as
well,
so
you
can
use
gitlab.com,
you
can
use
deploy
gitlab
out
in
aws,
gcp
openshift.
Obviously
so
we've
got
every
option
as
well
as
a
standalone
option
too.
So
I'm
in
the
federal
space.
So
the
majority
of
what
I
see
is
really
standalone
instances
so
yeah.
C
So
we
definitely
have
that
ability,
and
you
know
one
of
the
things
that
I
wanted
to
point
out
to
you.
You
know
you
were
saying
earlier
that
git
lab
you
know
we
were
talking
a
lot
about
openshift.
I
kind
of
want
to
point
that
as
a
very
big
benefit
of
gitlab.
So
as
a
standalone
product,
we
are,
you
know
fantastic.
We
cover
the
entire
life
cycle,
but
in
reality,
though,
we
need
to
be
able
to
integrate
with
other
products
and
integrate
well
with
other
products.
C
So
you
were
saying
you
know
hey
if
you're
talking
about
open
shift.
This
open
shift
that
well,
that
was
actually
by
design,
because
you
know
we
do
integrate
very
well
with
a
lot
of
products
and
and
openshift
is
definitely
one
we're
very
big.
Your
red
hat's,
very
big
to
us
we're
a
very
big
partner
of
you,
and
you
know
we
want
to
make
it
clear
that
you
know
we
integrate
well
with
other
products.
A
B
It
makes
me
that
good,
but
I
think
that's
kind
of
people
on
what
pete
just
said
right.
Gitlab's
vision
is
to
develop
this
platform.
Where,
again,
you
have
one
platform
for
your
entire
software
development
lifecycle.
The
reality
of
the
computing
industry
is,
we've
got
multiple
types
of
computing
platforms.
Right
have
openshift
on-prem
that
have
openshift
in
the
crowd
right,
different
public
cloud
providers,
ibm,
mainframes
and
so
on,
and
so
we
have
to
meet
those
customers.
B
Our
users,
where
they're
at
so
the
gitlab
run
on
openshift,
basically
just
enables
that
on
openshift
you're
asking
the
question
of
pete
earlier
in
terms
of
other
platforms
that
we
support
the
runner,
for
example,
you
can
currently
today
you
can
host
a
runner,
that's
ci
engine
for
gitlab
on
an
ibm,
z,
mainframe.
You
can
host
it
on
the
public
cloud
platform,
so
it
doesn't
really
necessarily
make
it
better.
A
A
A
A
So
if
we
have
any
more
interesting
questions
that
people
want
to
ask,
don't
be
shy,
pop
them
into
chat
and
we'll
make
sure
we
get
you
your
very
own,
get
lab
red
hat.
Can
you
see
my
screen
shirt?
I'm
gonna
stop
sharing
now
and
we're
gonna
go
back
to
the
question
and
by
the
way,
greg
wire
shoot
me
an
email,
it's
just.
It's
just
wait:
redhat.com
w-a-I-t-e
at
redhat.com
and
hopefully
you're
in
north
america.
A
I
don't
think
we're
gonna
be
shipping
these.
These
are
limited
edition,
2021
shirts,
by
the
way,
we'll
do
another
one
for
2022,
but
send
me
your
mailing
address
and
we'll
get
a
shirt
off
to
you
and
anyone
else.
Okay,
greg
wire
will
roll
residual
files
on
the
runner
be
cleared
between
jobs,
or
do
you
have
to
ensure
everything
is
removed
in
the
ci
script?
I
I
was
going
to
ask
the
very
same
question,
but
I'm
glad
that
that
he
did.
B
Yeah
the
answer
is
yes,
so
the
answer
to
the
question
is
yes.
We
also
have
a
feature
that
we're
currently
working
on
in
a
next
release.
To
also
do
some
additional
cleanup
of
the
pods
on
openshift,
also,
specifically
the
run-up
parts
and
openshift,
but
at
a
high
level,
the
greatest
question.
The
answer
is:
yes,
those
residual
files
will
be
cleaned
up,
will
be
cleaned
up.
B
A
Anyway,
so
we
were
talking
about
the
the
the
runner
was
certified,
not
that
long
ago,
what
about
what
about
the
server?
And
how
does
that?
So,
if
a
customer
is
running
openshift
in
their
environment
right,
whether
it's
in
public
cloud,
multi-cloud,
on-premise,
whatever
they
can,
they
can
use
the
op
the
the
runner
operator.
A
B
B
Gitlab.Com
and
what's
interesting
in
pete's
demo,
he
was
then
connecting
to
a
runner
operator
plus
runner
that
he
installed
on
an
openshift
environment.
So
you
can
imagine
as
a
user
or
customer
that
could
be
your
own
openshift
environment.
So
the
relationship
is
always.
You
have
a
gitlab
server
somewhere
if
either
gitlab
sas
or
a
gitlab
server
that
you
install
yourself
and
you
associate
a
gitlab
server
with
a
runner.
So
that's
the
relationship.
B
So
today,
though,
as
you
you're
quite
rightly
pointing
out
michael
the
runner
operator
and
the
runner
is
available
to
be
installed
on
openshift
gitlab
server
is
going
to
be
coming
soon.
I
believe
pete
we
are
targeting,
maybe
13.11,
which
is
our
april
release,
so
that
folks,
that
may
not
be
able
to
use
gitlab's,
ask
and
can
leverage
the
github
server
and
openshift.
C
Yeah,
that's
correct
and
that's
something
that
I've
been
pushing
for
very
hard,
so
I'm
very
excited
to
see
that.
But
yes,
you
are
right
darren!
So
michael
this
in
this
just
a
specific
demo,
it
was
a
sas
instance
of
get
lab
out
in
internet
land
and
the
interesting
part
is
the
the
openshift
server
in
this
instance
is
behind
a
firewall.
I
installed
the
the
gitlab
runner
on
that
instance
of
openshift
and
the
way
that
the
runner
works
is
it
actually
pulls
the
gitlab
server
right.
C
So
it's
an
outbound
communication
to
the
sas
instance
of
gitlab
to
you
know,
see
if
there's
any
jobs
awaiting
if
there
is
it,
gets
the
information
and
runs
that
job,
and
then
it
was
able
to
push
that
workload
over
to
my
openshift
instance
in
this
instance.
So
I
I
I
guess
the
answer
to
your
question.
Is
you
know
it's
it's
very
configurable
in
the
way
that
you
want
to
set
up
your
environment.
You
know
as
long
as
there's
communication
paths.
C
A
Do
you
see
that
that
there's
a
different
set
of
roles
and
requirements
in
the
federal
space?
I
mean
that
this
may
be
a
stupid
question,
but
are
they
more
on
premise
due
to
security
concerns
about
where
their
jobs
are
running
in
the
federal
space?
Or
does
everyone
just
trust
the
the
interweb
these
days.
C
So
this
is
more
of
a
yeah,
it's
a
preference
things,
I
guess
kind
of
so
to
speak,
where
they're
keeping
it
on
premise
in
order
for
them
to
go
anywhere
sas
that
needs
to
be
fed
ramped
in
order
for
them
to
be
allowed
to
use
that
service.
So
I'm
not
sitting
here
saying
that
they
do
not
use
online
services
or
sas
services.
A
A
B
Yeah,
it's
a
great
question.
Thank
you.
I
need
to
double
check
exactly
how
we're
developing
the
current
version
of
the
gitlab
server
for
openshift.
I
believe
that
the
nu
id
requirement
should
be
in
there,
but
I'll
need
to
double
check
that
so
miko.
I
I'll
grab
your
information
from
michael
as
well,
and
maybe
I'll
connect
with
you
offline.
Just
to
make
sure
that
I
answer
the
question
accurately
in
terms
of
are
we
taking
care
of
the
nu
id
pieces?
C
And
if
I
could
one
other
thing,
I'd
like
to
add
is
at
gitlab
we
try
to
be
as
transparent
as
possible
and
when
I
say
that
I'm
referring
to
our
product,
for
instance,
you
have
the
ability
to
go
out
to
gitlab.com
and
actually
search
for
this
for
the
issues
in
in
which
we're
working
on
these.
So
you
might
see
featuring
requests
or
enhancement
requests
out
there.
So
my
urge
to
you
is,
you
know,
go
out
there
and
do
a
search
for
any
uid
and
see
what
the
the
product
learned
status
is.
C
C
B
A
B
It's
a
deep,
open
chef
question
there
very
specific
rules
in
openshift
or
in
regards
using
new
id
and
that's
kind
of
the
key.
That's
really
it's
really
a
red
hat
open
shift
thing
in
terms
of
the
sort
of
the
annuity
requirements
and
not
mean
to
go
like
too
deep
into
it,
but
that
that's
leaving
it
at
a
very
high
level.
B
B
D
D
B
Oh
so
you're
talking
about
github
actions,
okay!
Well,
no,
it's
definitely
two
different
products.
Products
in
this
case
I
mean
github
actions,
is
how
git
hub
has
implemented
ci
cd
on
the
github
platform
and
so
two
different
product
streets.
At
this
point,
to
be
quite
honest,
things
are
simply
to
answer
that.
A
Two
different
products
from
two
different
companies-
exactly
yeah,
but
presumably
customers
have
a
a
a
mix
of
just
about
everything
out
there.
So
you
know
I
might
ask
the
question
then
you
know
I
don't
know
you
tell
me,
but
you
know,
if
there's
and
we're
talking
about
large
customers,
whether
it's
in
the
federal
space
or
financial
services,
presumably
there's
different
groups
with
inside
different
companies
that
are
using
different
devops
platforms.
So
you
probably
see
some
customers,
yes
or
no,
that
have
git
lab,
github
and
or
others.
Yes,.
B
Yeah
absolutely
you're,
gonna
find
and
stepping
back
that's
the
goal
of
github
right
is
that
if
the
idea
is
and
what
we're
seeing
with
other
companies
that
have
adopted
git
lab
in
total,
is
that
because
you
now
have
a
single
tool
chain,
you
no
longer
have
the
need
to
say,
maintain
a
jenkins
or
maintain
something
else
to
do.
Your
devops
maintain
a
different
tool
for
project
management,
but
you're
right,
you'll
go
into
an
existing
organization
today
and
team.
A
C
A
B
Github
actions
is
good,
github's
implementation
of
cicd,
it's
similar
to
runners.
I
think
they
actually
call
their
runner
a
github
agent
and
I
think
they're
using
the
same
software
that
microsoft
azure
is
using.
So
they
call
that
an
agent,
whereas
github
actions,
I
think,
is
what
they're
referring
to
or
the
technology
they
use
to
refer
that
three
foot
to
their
ci
to
ci
cd
offering
so
I
think,
yeah,
but
I
think
the
more
accurate
sort
of
apple's
apple's
comparison
is
the
github
agent
and
the
get
lab
runner.
A
B
I'm
going
to
try
to
pass
this
question
so
can
we
optimize
our
products
build
time
or
availability
for
multiple
projects?
I
guess
sebastian,
you
can
keep
us
honest
here
sebastian
on
youtube.
Are
you
basically
trying
to
get
to
a
state
where
you're
only
deploying
a
runner
when
you
need
to?
If
that
is
the
core
question,
the
answer
is
currently
not.
You've
had
a
speaker
showing
in
this
demo.
You
would
want
to
install
your
runner
on
openshift.
First,
because,
what's
happening
is
the
runner
is
pulling
gitlab
for
an
available
job?
B
You
can
certainly
optimize
your
project's
build
times
and
there's
certainly
certainly
different
strategies
to
do
that.
So
I
think,
generally
speaking,
yes,
I
think
we
can
certainly
delve
into
your
use
case
a
bit
more
kind
of
tease
out
exactly
kind
of
what
you're
trying
to
solve
for
in
terms
of
the
availability
by
multiple
projects.
Piece
of
this.
A
Okay,
sebastian,
hopefully
that
answers
your
question
and
by
the
way,
if
it
doesn't
we're,
really
accessible,
people
like
you
can
send
me
an
email
again,
it's
just
wade.
Redhat.Com
you
want
to
get
in
touch
with
darren.
You
want
to
get
in
touch
with
with
pete
or
or
anybody
else
like
we're.
We're
really
easy
to
work
with,
and
so
you
know
don't
think
that
this
is.
You
know
this
is
the
last
chance
to
to
get
any
questions
answered
from
us.
Mikey
was
mikey
wanted
to
know
what
runners
are
supported.
B
Just
basically
get
in
this
case,
it's
just
one
gitlab
runner
at
a
really
high
level.
You
have
just
the
one
gitlab
runner
software
itself
and
within
the
github
runner
software
binary.
We
support
either
a
multiple
target
deployment
environments
or
be
multiple
executive
times.
So,
in
the
case
of
openshift,
we
are
leveraging
our
communities
executor
and,
of
course
we
are
packaging
it
up
with
the
operator
in
terms
of
the
install
process
and
the
management
process.
So
it's
just
one
runner,
multiple
environments,.
A
Okay
and
I'm
gonna,
I'm
gonna
continue
to
read
the
questions,
because
the
other
people
watching
on
youtube
and
facebook
won't
know
what
the
question
is.
So
we've
got,
we've
got
a
couple
more
here,
I'm
gonna,
I'm
gonna,
allow
I'm
gonna
allow
pete
to
pronounce
this
person's
name.
You
can
take
it.
You
can
take
a
stab
at
that
one
and
why
don't
you
read
that
question
off?
It's
probably
up
your
alley.
C
Rap
scallion
reeves,
I
think,
is
there
a
marketplace
where
I
can
find
pre-made,
gitlab,
ci
emil
files
for
common
projects,
ie,
rebuilding
and
deploying
node.js
apps.
So
the
answer
is
yes,
but
it's
not
specifically
in
marketplace.
It's
actually
within
gitlab.
So
one
of
the
things
you
can
do
so,
if
you're
already
a
user
of
gitlab
and
if
you're
not
you
can
go
to
gitlab.com
and
sign
up
for
a
free
account
and
start
using
it.
C
But
my
suggestion
there
is
once
you
go
into
the
repo
you
can
opt
to
create
a
new
file,
and
when
you
do
that
you
could
opt
to
use
a
template
and
from
the
templates
you
can,
we
basically
have
a
large.
I
don't
even
know
what
the
number
is:
a
series
of
pre-made
gitlab,
ci
yaml
files
in
various
languages,
all
ready
for
you
to
go.
So
the
answer
is
yes
from
within
gitlab,
I'm
not
positive.
D
A
A
B
So
the
answer
is
go
and
the
answer
is
yes,
we
use
the
operator
sdk
for
building
it
in
terms
of
what's
the
most
difficult
part,
I
can
answer
that.
I
I
personally,
this
is
darren,
can't
answer
that
question
all
right,
but
you
can
certainly
ask
that
question
of
the
developers
that
actually
did
the
coding
work,
and
so
I
will
just
drop
in
the
chat
window
the
link
to
that
project.
Oh,
they
just
feel
free
to
create
an
issue
in
there
and
ask
that
question.
B
A
A
So
I'm
not
going
to
read
these
canned
questions
at
all,
but
I
did
want
to
ask
you
about
you
know:
what's
next
in
the
next
major
release
of
coming
up
for
git
lab
and
that
ties
in
really
well
with
with
preston's
question
that
just
came
in
you
know
for
the
upcoming
gitlab
server.
Will
it
install
operate
as
a
different
user
than
root,
and
maybe
you
can
kind
of
darren
tie
that
in
with
like?
What's
coming
in
your
in
your
releases,
you
know
the
major
releases
for
your
products.
B
Okay,
so
in
terms
of
the
gitlab
server
itself,
I'm
the
product
manager
for
github
server,
so
I'm
preston.
I
want
to
point
you
to
the
link
that
we
posted
earlier
on
that
takes
you
to
the
the
epic
for
the
gitlab
server
on
openshift,
go
ahead
and
raise
that
question
in
the
epic
in
terms
of
the
route
requirements
or
any
other
folks
that
are
listed
in
the
call
requirements
around
nuid
and
the
product
management
team
and
development
team
working
on
gitlab
civil
response
to
that,
michael
in
terms
of
the
runner.
B
What's
coming
in
our
major
release,
we've
got
a
bunch
of
things
coming
in
our
major
in
our
major
release,
just
14.
for
the
runner
specific
to
openshift,
we're
doing
things
related
to
pot
cleanup
and
then
some
additional
work
related
to
managing
of
root
certificates,
but
yeah.
If
folks
are
interested
in
things
that
are
happening
specific
on
the
server
side.
Yeah.
Thank
you
preston
that
epic.
There
is
a
place
to
raise
those
questions.
The
product
management
team
will
respond
to
them.
A
C
A
C
B
Yeah
and
sebastian
the
thing
that
we
have
and
the
flexibility
as
people's
kind
of
showing
as
well
is
that
you
can
configure
the
runners
to
solve
different
your
your
your
sort
of
like
use
cases
in
terms
of
you
know,
project
sizes
and
and
large
questions,
business,
small
buckets
at
a
high
level.
Yes,
auto
scaling
is
definitely
there.
You
also
have
the
additional
flexibility
of
just
being
able
to
simply
to
register
different
runners
for
different
types
of
products.
So
maybe
you
have
a
runner
right.
B
That's
going
to
just
handle
the
last
project
bills
right
and
it
will.
It
will
handle
auto
scaling
on
your
openshift
cluster,
and
maybe
you
have
a
different
one
and
that's
going
to
handle.
Maybe
your
node.js
project
and
maybe
it's
in
a
separate
naming
space
or
something
like
that.
So
the
answer
is
at
a
high
level.
A
Okay,
we
are
out
of
time,
I'm
gonna,
I'm
gonna
grab
my
the
screen
share
here
and
if
anyone
again,
if
anyone
has
more
questions,
send
them
to
wait,
redhat.com
I'll
get
them
answered
or
if
you
guys
want
to
call
call
darren
and
pete
at
their
home
phone
we're
going
to
put
that
up
on
the
screen
here.
Right
now,.
C
A
Yeah,
so
this
was
your.
This
was
the
call
to
action
slide
that
you
got
that
your
marketing
folks
sent
over
to
me.
I
don't
know
if
I
go
page
view
whatever
anyways
people
can
can
be
a
part
of
their
pipeline
on
openshift
event.
That's
coming
up
on
april
29th
thanks
everyone
for
for
joining
today
and
pete
and
darren
thanks
so
much
for
coming
here
and
being
our
victims.