►
From YouTube: Introducing 5mp to Steren Giannini (Product Manager leading Google Cloud Run) - December 6th 2021
Description
Bartek and Sri from GitLab Incubation Engineering sync with Steren Giannini who leads the Cloud Run efforts at Google Cloud.
5mp is now Cloud Seed ⛅🌱 https://hello.cloudseed.app
Cloud Seed is an open-source program lead by GitLab Incubation Engineering in collaboration with Google Cloud.
Deploying web application (and related workloads) from GitLab to major cloud providers should be trivial.
Cloud Seed makes it ridiculously simple and intuitive to consume appropriate Google Cloud services within GitLab.
Topics:
00:00 Introductions: Incubation Engineering
01:06 Topics / agenda
01:35 Why 5mp exists
02:36 Target user groups
03:30 Simple, reliable and "boring"
04:40 Why GCP? Why Cloud Run?
06:27 Demos
14:30 Roadmap discussion
15:45 5mp through the Google Cloud lens
16:30 Collab opportunities and discussion
A
We
have
a
lot
of
support
in
internally
from
the
leadership
when
it
comes
to
product
leadership
or
engineering,
leadership
or
sales
leadership,
but
also
the
ceo
office
is
a
direct
stakeholder
in
all
of
these
projects.
So
we
get
a
lot
of
internal
visibility
and
support
and
yeah
we
like
to
work
in
the
gitlab
way,
so
just
open
source,
transparent
and
all
the
good
stuff
that
you
get
with
the
culture
just
moving
on.
A
This
is
the
agenda
for
today,
I'll
just
give
a
quick
introduction
of
what
five-minute
production
is
for
whom
we're
building
it
and
then
from
there.
We'll.
Also,
I'd
like
to
share
why
I
think
google
cloud
and
cloud
run
is
the
ideal
choice
for
what
we're
doing
and
we
see
the
roadmap,
we'll
see
a
few
demos
and
we'll
see
if
we
can
actually
work
together.
A
So
in
light
of
that
five
minute
production
delivers
simple,
reliable,
boring
web
application
deployments
which
have
seamless
integration
into
the
rest
of
the
devops
pipelines,
ecosystems,
workflows,
so
planning,
source
code
management,
security
monitoring?
All
of
that
is
like
bundled
right
in
and
we
give
them
a
self-service
package
that
they
can
use
for
whom
are
we
building
this?
A
A
It
really
should
be
trivial
and
ridiculously
simple
to
use,
and
let's
try
to
define
that
a
bit.
When
I
say
ridiculously
simple,
I
mean
one
click
authorization,
so
a
really
simple
way
to
set
up
the
deployment
credentials
or
when
I
say
one
click
config.
It
should
be
very
simple
to
deploy
or
to
set
up
the
pipelines
and
then,
through
these
setups,
make
it
really
simple
for
those
teams
to
consume
the
best
practices.
A
I
also
use
the
term
boring,
and
this
is
something
that
we
use
a
lot
internally
within
our
organization,
at
least
in
the
engineering
part.
Where
did
we
want
boring
solutions
and
boring,
not
in
the
sense
that
they
are
bad
or
inferior,
but
boring
in
the
sense?
Like
my
water
kettle,
I
fill
it
up
with
water.
I
turn
it
on
and
it
boils
the
water
for
me.
I
can
just
forget
about
it.
A
I
don't
have
to
worry
about
it,
so
boring
in
that
sense,
wherein
we
use
popular
and
established
tech
which
reduces
complexity
and
gives
us
speed,
and
that
brings
us
to
google
cloud
and
cloud
run
when
we
are
talking
about
web
application
deployments.
Gitlab
itself
is
not
an
infrastructure
for
right,
we
don't.
We
don't
offer
cloud
hosting
for
web
applications,
but
we
have
two
partners.
A
We
have
aws
and
we
have
gcp
and
we
work
with
them
a
lot
like
we
work
with
you
a
lot,
but
now
we
need
to
choose
between
them
and
the
criteria
that
I
said
for
myself
is
okay.
Out
of
these,
can
we
get
frictionless
generation
of
deployment
credentials
from
the
gitlab
web
interface
with
gcp?
It
is
possible.
You
have
a
pretty
solid
oauth,
2
and
iam
and
cloud
resource
manager
apis,
which
makes
the
generation
of
service
account
and
keys
pretty
straightforward
aws
to
the
best
of
my
knowledge
as
of
december
2021.
A
A
A
A
A
There
is
a
discussion
going
on
like:
where
should
this
menu
live,
should
it
be
under
infrastructure
or
some
other
section,
but
that's
that's
a
different
matter.
What
I
want
to
demo
is
that
there
is
this
section
out
here
which
takes
you
to
a
page
which
lists
my
service
accounts.
As
of
now,
I
can
follow
the
create
service
account
root.
It
takes
me
through
the
oauth
2
process.
B
Just
one
comment:
I
think
that
that
flow
works
great.
You
might
also
want
to
allow
the
manual
way
of
doing
things,
because
you
seem
to
be
granting
a
lot
of
permissions
in
that
earth
consent
screen,
and
I
know
for
some
customers
that
would
be
a
deal
breaker.
So
just
calling
out
that
that's
great
also
provide
the
fallback
for
people
who
want
to
be
more
restrictive
around
the
permissions.
A
Yeah
yeah-
that
is
a
very
good
point.
So
so
this
is
not
documented
right
now,
but
the
way
the
flow
ends
is
that
it
ends
with
revoking
the
oauth
rights,
so
the
customer
isn't
expected
to
grant
us
the
permissions
forever,
but
only
for
this
creation
process.
But
let
me
let
me
just
touch
upon
the
second
point
you
made
because
it's
so
valid.
A
The
second
little
bit
of
a
demo
is
one
click
config,
and
this
is
not
100
ready,
but
what
we
want
to
do
is
we
want
to
make
it
dead,
simple
for
the
user
to
include
a
pipeline
as
well.
So
let
me
get
that
up.
I
need
to
switch
my
branch
for
a
second
I'm
on
the
wrong
branch,
which
is
always
fun.
I
should
have
checked
this
before
my
call
began,
but
I'm
on
a
wrong
branch.
B
A
No,
that's
such
a
good
point.
It's
a
really
good
point
and
something
that
we
verified
in
the
beginning,
because
within
the
gitlab
autodevops
workflow
there
is
a
concept
of
a
review
application
wherein
we
have.
If
I
make
a
feature
branch,
I
just
want
to
spin
up
a
temporary
environment
where
I
can
check
that
out.
So
one
of
the
criterias
for
selecting
a
review
environment
was
to
verify
the
free
tier
for
cloud
run
and
I
believe
it's
a
fairly
generous
free
tier
right
now,
if
I'm
not
mistaken,
something
like
two
million
requests
a
month.
B
B
A
A
Also
just
I
switch
to
the
right
branch
and
I'm
able
to
manually
revoke
authorizations
as
well,
but
just
be
informed
that
this
would
be
part
of
the
automated
process.
So
what
happens
when
you
revoke
authorizations
is
pretty
straightforward.
Now
your
service
account
remains,
but
gitlab
application
is
no
longer
authorized
to
manage
your
cloud
resources.
So
if
I
was
to
create
another
service
account,
it
would
ask
me
to
authorize
again
so
so
this
is
part
of
the
process.
A
The
second
part
was
one
click
configuration
where
didn't.
We
have
this
tab
and
this
tab
shows
us
a
bunch
of
it
shows
us
two
gcp
managed
services.
Let
me
just
increase
the
font
size,
we
have
cloud
run
and
cloud
storage,
and
while
this
is
not
100
complete
pressing,
this
button
will
create
a
pipeline
for
the
end
user,
which
is
in
which
is
included
in
their
project
through
the
review
process.
So
it
will
be
included
in
their
project
and
once
reviewed
and
approved,
they
have
a
complete
pipeline.
A
That
looks
something
like
let
me
get
the
demo
up
for
you.
The
pipeline
will
look
something
like
this:
where
it's
going
to
build
run,
the
tests
run
all
the
security
scanners
and
then
based
on
which
environment
the
pipeline
is
running
for
or
which
branch
the
pipeline
is
running,
for
it
will
deploy
to
the
right
environment,
and
this
deployment
is
actually
the
cloud
run.
A
A
If
I
take
you
back
to
this
page
over
here,
you're
seeing
cloud
run
and
cloud
storage,
and
these
are
the
services
we
want
to
target
upfront,
so
cloud
run
for
web
applications,
cloud
storage
for
static
resources
and
over
time,
of
course,
a
typical
production
application
will
need
a
sql
database.
So
maybe
cloud
sql
comes
right
here,
or
maybe
they
need
some
sort
of
a
caching
service.
So
I
forget
the
name:
is
it
memory
store
or
whatever
the
gcp?
Caching
services?
A
A
A
A
Looking
forward
june
july
august,
I'm
thinking
firebase,
I'm
thinking
cloud
sql,
I'm
thinking
some
sort
of
caching
service
based
on
the
demand
that
we
have
from
our
users
so
depending
on
which
services
they
need
we're
going
to
prioritize
those
and
just
to
take
a
step
back.
I
want
to
define
five-minute
production
again
for
you,
but
from
this
time
I
want
to
use
a
lens
of
gcp.
So,
from
your
point
of
view,
what
is
this?
It
basically
enables
gcp
users
to
set
up
and
configure
service
accounts
right.
A
It
enables
gcp
users
to
configure
cloud
run
with
the
press
of
a
button,
and
the
roadmap
is
for
including
more
gcp
services
based
on
the
demand
of
our
users,
so
you
can
look
at
it
as
and
bartek
might
not
like
the
way
I
phrased
this,
but
you
can
see
this
as
a
gcp
plugin
being
built
natively
within
our
product.
So
this
is
one
way
to
look.
Look
at
this.
B
B
You
know,
I
don't
know
if
you
know,
but
if
you
open
claron,
you
can
either
give
a
container
or
you
can
connect
to
gitlab
and
github
and
bitbucket
and
and
once
you've
done
so,
you
know
we
will
set
up
the
ci
cd
pipeline
for
you
and
every
time
you
push
to
a
branch
it
will
deploy,
and
so
I
like
to
see
the
other
angle
of
this,
which
is
you
come
from
from
the
gitlab
angle,
and
and
now
you
are
looking
for.
Okay,
you
have
your
web
app.
You
are
looking
for
an
easy.
A
B
Think
that's
the
right
approach
and
you
know
the
the
experience
you
you
demoed
is
you
know
it
is.
It
is
definitely
in
the
spirit
of
of
claddon,
which
is
simple
one-click.
You
know,
convention
of
a
configuration,
so
I
assume
that
the
pipeline
that
you
show
you
are
going
to
pre-populate
it
on
behalf
of
the
user
and
the
user.
Can
then
customize
it.
So
that's
very
much
in
the
spirit
of
of
of
what
we
do
for
plato
and
which
is
setting
you
on
the
right
path,
but
allowing
you
to
customize.
B
That
would
that
would
allow
you
to
say
yeah
the
way
you
do.
It
is
good
or
oh.
No,
we
don't
recommend
you
to
do
it
that
way,
but
this
other
way
because,
as
I
said,
I
think
many
customers
won't
be
able
to
follow
that
flow,
because
the
the
os
screen
is
asking
them
basically
to
give
like
full
full
access
to
their
cloud
infrastructure.
So
we
should.
We
should
see
how
that
flow
could.
Maybe
this
works
great
for,
like
small
companies,
individual
developers,
but
that
will
not
work
for
a
big
enterprise.
A
A
In
terms
of
what
you
mentioned,
you
know,
pull
versus
first,
should
cloud
run,
pull
from
a
git
repo,
or
should
the
gitlab
platform
be
responsible
for
pushing
it's
fair.
I
I
come
from
a
commercial
background
where
I've
worked
with
a
lot
of
our
customers
and
what
triggered
this
concept
was
a
lot
of
customers
who
use
gitlab
ci
cd
for
all
of
their
pipelines.
A
So
the
use
case
was
that,
if
you're
a
large
enterprise,
let
the
id
team
just
give
you
a
you
know
a
constrained
gcp
account
where
you
can
only
do
cloud
run
with
all
the
limits
set
in
and
we
have
the
self-service
system
where
you
can
just
say.
Okay,
I
want
to
use
cloud
run
for
my
web
application
right
now,
maybe
six
months
from
now
when
we
have
to
go
live,
it
has
to
go
on
the
official
kubernetes
clusters,
but
for
now
I
can
quickly
develop
this.
A
That's
that's
the
user
base
that
we
want
to
go
after,
of
course,
when
it
comes
to
startups
or
small
organizations,
it's
a
different
user
base
altogether,
but
yeah.
I
think
it's
a
good
suggestion
that
we
can
get
a
review
done
from
both
the
gcp
security
team
and
and
my
security
team
over
here
and
find
the
best
way
forward.
B
Yeah
and
overall,
you
know,
I'm
excited
to
see
this
gitlab
partnership
expanding
in
a
way.
Gitlab
has
been
a
launch
partner
for
clarence
since
2019,
and
you
know
we
are
talking
with
different
people
around
how
to
bring
clutter
and
jobs
to
to
get
lab
runners,
but
this
would
be
yet
another
expansion
of
you
know
the
collaboration
between
google
cloud
and
gitlab
and
more
precisely
cloud
and
gitlab,
which
I
represent.
A
Yeah
sounds
good,
so
on
that
note
you
know
it'll
be
nice
to
one
of
my
items
here
in
the
slides
is
also
kind
of
a
recurring
sink.
I
don't
know
if
it
has
to
be
every
month
or
every
quarter,
but
I
think
you're
speaking
to
quite
a
few
people
in
our
organization,
we're
also
speaking
to
different
parts
of
google
cloud.
So
if
you
can
get
some
structure
around
this,
for
example,
you
just
mentioned
cloud
run
jobs.
A
B
A
Yeah
yeah
makes
sense
so
I'll
just
go
through
this
final
slide
and
just
get
your
thoughts
on
this
as
well.
So
I
just
listed
down
from
the
top
of
my
head
some
opportunities
and
having
this
sink
ever
so
often,
let's
say
every
quarter
or
every
month.
I
don't
know
what
the
ideal
timeline
is,
but
let's
just
keep
talking.
Let's
give,
let's
give
each
other
speaking
slots
in
each
other's
events,
especially
when
this
is
at
a
stage
where
end
users
can
consume.
Then
I
would
love
to
present
this
to
gcp
audience
and
vice
versa.
A
We
can
invite
you
to
to
the
events
that
that
we
run
as
well,
and
we
can,
you
know,
just
educate
our
joint
user
base
on
that
light.
Again,
I'm
not
the
right
person
for
this,
maybe
you're,
not
the
right
person
as
well,
but
I
would
love
to
look
at
your
marketing
calendar
for
2022
and
I'm
happy
to
share
ours
as
well.
B
Yeah
I
mean
on
that
one
I
think,
before
making
noise
about
it,
we
need.
You
know,
we
need
to
be
confident
that
this
is.
This
is
something
we
we,
that
is,
that
is
available
to
everyone
that
that
gitlab
plans
to
support,
and
once
we
are
there,
then
you
know
there
are
many
activities
we
can
do,
and
notably
I'm
thinking
about
google
cloud
next,
you
know
you
gitlab
was
already
mentioned.
You
know
at
launch
in
2019,
but
like
either.
B
We
can
think
about
a
dedicated
session
or
add
this
to
an
existing
session.
You
know
we
are
many
things
we
can
do
and-
and
you
know
when
it
comes
to
to
go
to
market,
we
can.
I
can
loop
in
more
folks
from
our
marketing
or
outbound
team,
but
but
I
think
my
my
main
question
is
today:
it
seems
to
be
a
proof
of
concept.
B
A
No,
that's
a
very
good
point,
I'm
glad
you
mentioned
it
so
this,
as
you
said,
noise
making
has
to
happen
once
this
is
more
than
just
a
proof
of
concept,
and
I'm
going
to
look
at
this.
This
timeline
over
here,
I'm
fairly
confident
by
you
know,
early
summer
or
late
spring.
This
would
be
both
available
in
self
managed
and
in
dot
com,
so
our
self
hosted
and
our
sas
users
will
have
access
to
this.
A
The
question
is:
how
do
we
want
to
roll
it
out,
so
we
can
be
very
defensive
about
it.
We
can
have
it
enabled
only
for
a
small
set
of
users
that
we
know
and
we
trust
or
we
can
go
crazy
about
it.
So
all
of
that,
I
think
that
depends
on
the
confidence
level
that
we
have
in
this
feature
set
at
that
point
of
time,
but
all
options
are
available.
Yeah.
B
B
So,
for
example,
when
you
have
something
potentially
under
a
low
list
for
gitlab.com
or
self
money
like
self-managed
gitlab
is
probably
not
managed
by
by
you,
but
by
the
customer
instead,
but
for
github.com,
for
example,
if
the
feature
can
be
like
accessed
via
analyst,
we
can
can
distribute
a
form
to
the
cloud
interested
tester,
so
they
can
fill
in
to
to
give
it
a
try.
And
once
we
got
us
a
few
rounds
of
testing,
we
can.
A
A
A
B
A
B
B
A
A
We
can
have
two
large
launch
events
so
to
speak,
one
for
the
sas
launch,
so
on.com
it's
available,
which
is
a
big
deal,
we'll
make
a
lot
of
noise
around
this,
and
I
believe
gcp
in
the
past
has
provided
credit
coupons
for
kubernetes,
so
for
the
gke
service
and
it'll
be
great.
If
you
can
do
something
like
that
to
get
more
of
our
dot
com
users
to
try
out
cloud
run
such
as
something
that
I
want
to
throw
at
you
in
the
past,
we've
done
it
with
gke.
A
B
I
will
have
to
follow
up
with,
or
marketing
and
an
add-on
team.
I
don't
want
to
promise
anything
yeah.
I
just
want
to
cover
that.
Contrary
to
kubernetes,
you
know,
clardon
is
really
pay
as
you
go
and,
as
you
mentioned
already,
has
a
pretty
generous
free
tier.
So
it
depends
what
our
goal
is.
If
our
goal
is
to
make
sure
that
people
trying
out
this
flow
can
try
it
without
charges.
B
That
will
be
true,
no
matter
what
like,
even
if
we
have
credits
or
not,
because
the
free
t
already
covers
the
the
trial
yeah
if
the
goal
is
actually
to
to
give
a
free,
a
credit
to
incentivize
the
use
of
this
feature
like
hey,
you
know
you
get,
you
get
a
coupon.
Basically,
then,
then
it's
a
different
goal,
and
in
that
case
I
I
agree
that
you
know
I
should
follow
up
with
what
we
can
do
internally.
A
A
B
Yeah
exactly
I
wanted
to
ask,
what's
your
because
you
mentioned
cloud
storage
and
cloud
run,
but
you
did
not
mention
cloud
sql,
because
cloud
storage
is
also
in
the
same
way.
It
has
a
free
tier,
and
if
you
don't
use
it,
you
don't
pay
well
as
long
as
you
don't
store
many
things
on
it,
yeah,
but
class
sql
indeed,
is
always
on
so
cloud
sql.
If
you
have
an
instance,
you
pay
for
it.
A
A
And
if
there
is
a
demand,
then
we
can
think
about
a
coupon
for
a
cloud
cloud
cloud
sql
at
that
point
of
time
but
yeah,
but
we
have
cloud
sql.
We
have
firebase,
we
have
the
redis
service,
so
all
of
that,
like
common
things
that
you
would
expect
a
website
to
use,
we
want
to
offer
that
so
in
theory,
you
should
be
able
to
run
a
production
website
using
just
this
feature
set.
B
B
So
indeed,
in
google
cloud
we
don't
have
a
pay-as-you-go
scale
to
zero
sql
compatible.
So
if,
if
one
of
the
requirement
is
to
be
sql
compatible
like
postgresql
and
we
do
not
have
a
something
that
scales
down
to
zero
yeah,
so
yeah
in
that
case,
customers
enabling
that
should
should
know
that
you
know
it
will
incur
charges
if
they
don't
use.
It.
A
A
The
next
thing
I
want
to
do
is
also
make
a
big
noise
when
we
are
going
to
ship
this
in
the
self-managed
product,
because,
as
you
probably
know,
a
bulk
of
majority
of
our
customers
are
self-managed
users,
and
these
are
large
federal
accounts,
large
enterprise
accounts
and
there's
a
large,
at
least
in
the
emea
benelux-
nordic
market-
that
I
that
I
am
familiar
with.
There
is
a
big
overlap
with
these
enterprise
customers
of
ours,
who
are
also
gcp
customers.
A
A
B
A
Yeah
yeah
and
I'm
sure
you
know
you
have
customer
success
teams
and
we
have
customer
success
teams
and
we
can
ask
them
to
look
through
their
records.
You
know
if
there
is
overlap,
let's
identify
them
and
if
the
account
is
significantly
large
enough,
we
can
run
some
sort
of
an
enablement
motion
just
for
those
accounts
so
that
we
both
win
so
so
in
terms
of
topics
on
my
slides.
This
is
it
really.
A
B
A
B
It's
just
that
I
I
don't
I'm
not
familiar
enough
with
the
latest
security
best
practice.
I
know
google
has
invested
a
lot
into
not
having
to
download
api
keys
or,
like
you
know,
service
account
keys.
So
I
there's
probably
some
something
to
to
be
aware
of
when
it
comes
to.
You
know,
generating
fml
credentials.
A
A
If
I'm
doing
machine
learning,
I
still
need
some
sort
of
web
interface
or,
if
I'm
doing
any,
like
almost
every
enterprise
task
or
every
computing
task
requires
some
kind
of
a
presence.
So
I
do
see
this
as
a
futuristic
project
where,
where
gitlab
users
can
pick
the
very
best
of
google
cloud's
offerings-
and
I
know
you
have
some
excellent
offerings
in
the
aiml
space
and
think
of
this
five-minute
production
right
now,
it's
focusing
on
web
applications.
So
right
now
it's
focusing
on
databases
and
we're
addressing
this
because
80
20
right.
A
A
So
yeah,
so
if
we
can
keep
talking
every
quarter,
I
think
this
will
get
pretty
exciting
over
time,
but
yeah,
that's
all
I
have.
I
don't
know
how
busy
the
two
of
you
are,
but
we
have
got
about
15
minutes
remaining
in
this
meeting.
If
anybody
has
anything
else
to
share,
maybe
some
action
items
going
forward.
A
A
B
A
B
A
It
could
know
well
to
be
very
honest.
This
is
already
getting
merged
into
the
master
branch
and
it's
getting
shipped.
So
if
your
customer
is
using
any
version
greater
than
14.4,
they
already
have
some
of
the
features.
So,
let's
say
in
february
or
march,
we're
ready.
Then
we
can
just
ask
this
customer
to
update
to
the
latest
instance.
It's
going
to
be
14.8
or
something
like
that.
They'd
be
ask
them
to
update
to
a
specific
version,
and
then
they
can
enable
this
locally
on
their
instance
as
well.
A
B
A
No,
I
I
really
valued
your
inputs
regarding
iem
that
might
be
critical
depending
on
the
sensitivity
of
of
our
customers
and,
of
course,
your
offer
for
trusted
testing.
That
is,
that
is
perfect.
Thank
you
so
much
what
I
will
do,
just
just
a
future
task
for
me,
is
to
reach
out
to
you
sometime
in
january
or
february
or
march.
I
don't
know
exactly
when,
but
around
that
time
early
next
year
and
hopefully
show
you
progress
and
plan
out
more
concrete
steps
that
we
take
at
that
point,.