►
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:36 Recap
01:43 MR 01 - Merged
02:25 MR 02 - Merged
03:10 MR 03 - Open
04:46 Discussion around OIDC
06:38 What's next
A
A
In
the
last
quarter,
we
worked
on
the
theme
around
one
click
authentication,
wherein
service
account
generation
within
git
lab
was
a
super
smooth
process,
and
once
this
was
developed,
it
was
split
into
multiple
small,
merge,
requests
and
merged
into
get
lab
source
in
quarter.
Four.
What
we
have
done
so
far
is
we
have
got
a
functional
working
demo
of
deployment
to
cloud
run.
A
The
major
piece
of
work
that
remains
now
is
to
break
that
feature
branch
into
multiple,
smaller
merge
requests
and
merge
that
into
gitlab
source.
Once
this
gets
done
in
the
coming
weeks,
we
look
forward
to
fy23q1
where
we
will
work
on
a
preview
rollout
first
privately
and
then
to
a
larger
user
base.
A
A
This
was
a
fairly,
I
would
say,
small
merge
request
that
got
reviewed
and
merged
pretty
smooth.
So
I
would
like
to
thank
the
two
reviewers
cynthia
david
kim
and
tyler
rabos,
for
their
support
with
this,
mr
and
having
it
merged.
A
This
introduces
the
ui
elements
which
are
disabled,
and
this
will
basically
be
the
place
where
the
user
would
configure
their
merge
request
again
fairly
small
and
straightforward
merge
request
that
got
reviewed
and
merged
as
a
smooth
process.
So
I
would
like
to
thank
peyton
and
natalia
for
this
smooth,
merge
process.
A
The
final
mr77590
is
still
open.
This
is
a
merged
request
that
sets
the
protected
status
of
the
ci
virus
generated
for
the
service
account
and
the
protected
status
of
these
ci
variables
is
linked
to
the
environment
they
were
created.
For
so,
if
I
create
a
service
account
for
a
non-protected
environment,
then
the
ci
wires
are
not
protected,
whereas
if
I
create
the
ci
wires
for
a
protected
environment,
then
of
course
they
are
protected.
A
A
This
is
where
we
are
still
waiting
for
douglas
to
return
from
his
out
of
office.
He
was
out
of
office
for
a
few
days,
so
this
review
hasn't
been
merged
yet,
but
he'll
be
back
monday
and
we'll
go
through
the
changes
that
I
made
and
we'll
see
if
we
can
get
it
merged.
A
A
Both
these
discussions
were
around
workload,
identity,
federation.
I
wanted
to
understand
what
it
is
and
how
it
works
and
where
we
are
within
oidc
support
or
open
id
support,
or,
should
I
say,
open,
I
d
connect
support
within
gitlab
there's
an
epic,
and
this
should
be
there
at
some
point
once
it's
ready.
I
feel
that
seth
has
made
a
strong
case
for
this
to
be
implemented.
I
think
it
makes
sense
to
implement
it.
A
It
reduces
the
responsibility
of
our
software
in
holding
secrets
and
that's
a
good
thing,
and
the
key
element
for
me
was
to
ensure
that
we
do
not
compromise
on
the
one.
Click
authentication
and
one
click
on
configuration,
user
experience,
and
if
I
understood
what
set
said
properly,
it
seems
that
we
can
stick
with
the
existing
user
experience,
which
means
my
oauth
flow
will
configure
workload,
identity
federation
for
me
and
then,
once
the
gitlab
ci
runner
is
provided
with
the
jwt
token
for
ooidc,
we
will
be
able
to
use
it
for
five
minute
production
as
well.
A
A
The
agenda
for
what's
next
is
simple:
we
create
one
or
more,
mrs
to
get
the
configure
cloud
run
pipeline
working,
and
this
will
mean
that
we
are
ready
to
have
a
preview
rollout.
I
suspect
this
will
be
two,
mrs,
maybe
three.
The
other
step
is
to
work
on
the
existing
openmr
and
get
that
merged
as
well.
The
focus
would
be
just
performing
these
engineering
tasks
and
closing
the
quarter
strong.