►
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.
A
Our
mission
is
to
make
non-kubernetes
deployments
trivial
for
a
gitlab
user,
which
means
you
take
your
web
application
and
you
have
it
deployed
on
major
cloud
providers
with
minimum
fuss.
A
We
finished
building
the
initial
prototype
back
in
january
2021,
which
proved
that
this
could
be
done
using
the
gitlab
ecosystem
of
pipelines,
scripting
and
state
management
of
the
infrastructure
now
reach
out
the
journey
ahead
in
the
monthly
direction.
Update
I'll
share
with
you,
the
immediate
focus
for
the
next
few
weeks.
A
The
benefits
is
that
we
get
to
serve
a
pool
of
existing
review,
app
users
and
capture
their
feedback,
which
means
we
can
ship
quickly
and
ship
small
and
we
get
to
test
with
them
capture
their
feedback
and
get
the
details
right.
A
A
A
We
will
try
to
automate
this
process
as
much
as
possible,
can't
make
any
problem
in
any
promises,
but
I
think
it
should
be.
It
should
be
feasible,
so
we'll
give
it
a
honest
shot
of
trying
to
achieve
that.
Similarly,
the
next
item
is
one
click.
Config
again,
if
you
go
back
to
the
original
five-minute
production
project,
we
required
you
to
include
manually
include
lines
inside
your
gitlab
ci
aml
pipeline
definition.
A
Can
we
automate
this?
There
is
an
example
with
where,
in
the
secure
conflict
page.
A
A
Finally,
the
five
minute
review
app
pipeline
itself.
We
will
strip
down
the
original
five-minute
production
pipeline,
especially
on
the
infrastructure
side.
We
will
strip
it
down
so
that
we
can
support
review
applications,
so
the
five-minute
production
original
pipeline
or
the
infrastructure
setup
creates
things
like
vpcs
and
subnets
and
drought
tables
and
provides
a
managed
email
service
and
a
lot
more
things
that
we
don't
need
for
review
applications.
A
So
we
try
to
strip
it
out
and
give
a
really
bare
bones
environment
that
is
perfect,
but
also
lightweight
for
for
supporting
review
applications
when
it
comes
to
long-term
direction
and
focus.
The
first
thing
we
want
to
do
is
research
and
identify
popular
gcp
and
aws
services
used
among
gitlab
customers.
A
Coming
to
this
week's
updates,
most
of
my
time
has
been,
has
been
spent
on
these
onboarding
and
career
mobility
tasks
and
familiarizing
myself
with
the
code
base
and
the
documentation
around
it.
However,
I
was
able
to
build
two
front-end
prototypes,
the
first
one
for
group
level,
authentication
and
the
second
one
for
project
level
config.
So
let's
have
a
look
at
them.
A
Let's
just
have
a
quick
look
setting
the
context:
you
are
a
maintainer
of
a
group
and
you
want
to
provide
cloud
credentials
for
all
projects
within
that
group
so
that
they
can
deploy
review
apps
to
this
particular
cloud.
A
So,
as
the
group
maintainer
you
navigate
to
your
group
and
you
go
to
settings
ci
cd,
this
is
where
you
would
normally
manage
your
pipelines.
So
you
have
settings
for
auto
devops
for
runners
for
variables
and
the
likes
you
already
have
these
over.
Here.
You
can
notice
two
new
editions.
Two
new
sections
over
here
review
apps
for
aws
and
review
apps
on
google
cloud.
A
Clicking
on
this
button
will
open
a
new
browser,
pop-up
window
tab,
and
it
will
take
you
to
the
cloud
console
where
you
can
perform
your
auth
and
whatever
other
tasks
need
to
be
performed,
get
performed
at
the
end
of
the
process.
What
should
happen
is
gcp
or
aws
credentials
get
created
and
automatically
stored
in
variables
over
here.
So
the
end
of
the
process
would
be
that
you
click
you
go
to
the
cloud
console
and
when
you
finish
the
process,
you
will
see
the
variables
showing
up
over
here.
A
So
the
context
here
is
that
you're
a
maintainer
of
the
project,
and
you
want
to
enable
review
apps
for
your
particular
project
and
you
can
assume
that
credentials
already
have
been
set
up
either
as
group
ci,
cd
variables
or
as
project
cicd
variables.
The
first
thing
you
would
do
is
navigate
to
your
project.
A
A
A
A
A
A
It
is
important
to
get
the
feature
flags
done
first,
because
it
will
just
smoothen
the
development
process.
After
that
I
can
create
once
the
feature
flags
are
there.
I
can
create
small,
mrs
and
merge
them
into
the
main
code
base
without
any
unintended
side
effects,
so
that
will
be
the
focus
for
the
days
and
weeks
ahead,
and
that's
all
for
this
update
hope
you
liked
what
you
saw
have
a
great
weekend
and
see
you
next
time.