►
Description
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.
00:00 Intro
00:40 Why 5mp?
01:25 Why Cloud Run?
02:53 Demo: Until now
03:32 MR !75295
04:37 MR !75902
04:56 MR !75897
06:13 Next week
A
A
We
are
striving
to
be
a
boring
solution
and
boring
shouldn't
be
conflated
with
bad
or
inferior,
but
rather
it's
to
use
popular
and
established
tech
that
reduce
complexity
and
increase,
speed
and
stability.
It
should
be
reliable.
Like
my
electric
kettle,
I
fill
it
up
with
water.
I
turn
it
on
and
then
I
forget
about
it.
A
A
These
are
our
natural
partners,
but
how
do
we
decide
between
them?
The
criteria
is
number
one.
Is
it
frictionless
to
generate
deployment
credentials
from
the
gitlab
web
interface
with
gzp?
If
you
use
google
award
2
and
their
iam
apis,
it
is
possible,
as
of
december
2021,
with
aws.
It
is
not
possible
unless
we
use
an
ugly
hack.
A
A
Till
now,
we've
demonstrated
the
ability
to
create
service
accounts
from
within
the
gitlab
rails
web
application.
You
navigate
to
infrastructure,
google
cloud,
you
follow.
The
create
service
account
workflow,
which
takes
you
through
the
google
oauth
process
you
log
in
and
you
grant
permissions
and
then
you're
taken
to
the
create
service
account
form
where
you
select
your
gcp
project
and
the
environment.
A
A
A
I
would
like
to
name
a
few
people
who
helped
me
through
this,
and
I
would
say
the
two
key
players
were
andrew
fontaine
and
paul
slaughter.
I
believe
there
were
a
couple
of
back
end
approvals
as
well.
So
if
I
just
toggle
this,
you
will
see
all
the
back
end
approvers
and
the
key
back
in
the
proverb
was
krasimir,
but
because
most
of
the
work
done
here
was
related
to
front
end.
I
named
paul
and
andrew
as
the
main
reviewers
and
maintainers
who
helped
me
through
this
process,
and
this
got
merged.
A
A
Let
me
show
you
a
quick
demo,
so
here's
a
project
which
has
got
three
service
accounts
created
and
by
default
they've
gone
through
this
oauth
process.
They
have
this
auth
token
associated
in
the
session
and
it
times
out
after
a
certain
amount.
I
believe
it's
10
minutes,
but
we
want
to
give
the
user
complete
control
to
revoke
this
authorization.
So
button
has
been
introduced
inside
the
google
cloud
configuration
section
where
I
can
press
this
button
to
revoke
the
authorization.
A
Do
note
this
revokes
the
authorization,
but
it
does
not
invalidate
the
service
accounts
which
has
been
created.
Let
me
just
press.
The
button
goes
through.
The
process
gives
me
notification
that
the
token
has
been
revoked,
and
the
proof
of
this
is
that
when
I
try
to
create
a
service
account
again,
I
have
to
go
through
the
sign
in
process
the
what
process.
A
A
It's
not
functional
right
now,
but
I
think
I've
decided
on
this
ui
process,
because
this
ui
seems
scalable
when
we
have
to
support
more
services,
so
we
can
have
buttons
or
toggles
for
each
one
of
them,
and
this
has
been
inspired
by
what
we're
doing
in
security
compliance.
For
example,
if
I
go
to
configure
within
security-
and
I
click
enable
sas-
this
will
take
in
take
me
to
a
form
where
I
see
see
a
few
fields,
and
I
can
configure
my
sas
task
and
I
press
the
button
and
then
it
takes
me
to
well.
A
That's
the
experience
I
want
to
make
make
available
so
that
we
can
come
true
on
our
track
on
our
promise.
We
promise
them.
One
click
authentication
which
we
have
over
here,
with
the
create
service
account
and
with
the
deployment
button
over
here
we
want
to
promise
or
we
have
to
fulfill
the
promise
of
one
click
configuration.