►
From YouTube: SRE Team Introduction at GitLab - Team Structure
Description
An introduction to the Infrastructure team division and main responsibilities at GitLab.
Official Team Structure documentation: https://about.gitlab.com/handbook/engineering/infrastructure/team/
More about Infrastructure at GitLab: https://about.gitlab.com/handbook/engineering/infrastructure/
A
A
A
A
A
So
you
know
there's
a
deployment
it
could
be
blocked
by
either
misconfiguration,
maybe
in
the
code,
maybe
something
on
the
code
side
of
things,
which
is
the
infrastructure
team
shouldn't
really
be
handling
that
particular
problem,
like
the
developers,
should
take
care
of
that
we'll
also
get
to
who
is
responsible
for
coordinating
that.
But
the
core
infrastructure
team,
which
is
the
the
reliability
team,
is
responsible
for
the
infrastructure
side
of
things
more
than
anything
else
and
they're
also
participating
in
a
on
call
rotation,
which
is
the
other
sub
team.
A
The
scalability
and
the
delivery
don't
really
participate
in
that
one
called
it
doesn't
mean
that
they
don't
attend.
The
incident
calls
when
there's
something
urgent.
Actually,
in
fact,
I've
always
found
someone
from
the
delivery
team
in
the
incident
room
like
it's.
It's
like
a
standard
thing,
it's
like
they're,
always
there.
Sometimes
it
feels
like,
even
if
they're
not
really
affected
as
a
delivery
sub
team,
they
are
still
attending
and
helping
and
and
they're
always
there
as
of
their
own
call.
A
You
know
so
they're
not
officially
participating
but
they're
heavily
involved
on
their
own
call
rotation.
So
that's
the
reliability
team.
Oh
by
the
way,
the
reliability
team
is
divided
into
three
sub
teams,
as
well
according
to
their
different
focus
and
functionalities.
But
we're
not
going
to
talk
about
that
for
the
moment.
Let's
just
focus
on
the
next
team,
which
is
the
delivery
team,
so
the
delivery
team
is
responsible
for
delivering
the
releases
every
month
for
getlab.com,
so
they
coordinate
all
the
functionalities
that
are
going
to
come
out.
A
A
A
Some
of
our
instances
that
are
running
on
an
older
infrastructure
to
a
newer
infrastructure,
which
I
find
quite
quite
quite
interesting
topic.
So,
if
you're
about,
if
you
are
interested
about
kubernetes-
and
you
maybe
have
some
experience
or
want
to
get
more
experience
about
kubernetes,
the
delivery
team
is
where
you
want
to
look
at.
You
want
to
look
at
their
work
because
they
are
the
ones
that
are
doing
the
migration
from
the
older
infrastructure
to
the
new
infrastructure
which
is
based
on
kubernetes.
A
A
Well,
you
can
tell
from
that
sentence
that
I
haven't
really
dealt
heavily
with
them
during
my
internship
and
I
I
think
the
reason
is
because
they
are
working
more
as
sync
they're,
not
as
involved
in
the
incidents
as
the
delivery
and
the
reliability
teams.
That's
what
I've
noticed
from
the
few
incidents
that
I've
attended,
so
I
might
be
wrong,
but
that's
my
observation.
A
So
they
have
this
focus
on
bigger
infrastructures
and
how-
and
I
think
also
it's
not
it's
not
just
about
the
infrastructure
side
of
things-
things
that
they're
planning.
I
think
it's
also
more
about
the
code
sides
of
things
so
they're
also
planning
how
the
code
is
going
to
scale
as
gitlab.com
scaling.
So
it's
not
just
the
infrastructure.
Actually,
it's
more
about
the
code,
the
database
and
other
parts
of
the
services
that
work
together
to
eventually
grow
as
fast
as
as
the
company
is
growing.
A
A
Details
regarding
each
of
these
themes,
I
haven't
really
thought
about
what
details
I'm
going
to
talk
about
yet,
but
I
do
have
some
things
that
might
be
interesting
to
say
about
each
of
these
themes,
so
I'm
going
to
make
three
videos
for
each
of
the
teams.
I
think
I
might
not
actually
do
it
for
each
of
the
teams.
A
I
think
I
might
skip
it
for
the
scalability
team,
given
that
I
don't
really
have
much
of
experience
with
them,
so
I
guess
it's
going
to
be
just
the
delivery
and
the
reliability,
which
is
interesting
because
they
have
sub
teams,
as
I
mentioned
earlier,
so
yeah
stay
tuned
for
another
video.
Thank
you
for
watching.