►
From YouTube: 2021-03-15 Multi-Large Working Group Weekly
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
B
Yeah,
this
is
a
quick
status
update
based
on
one
of
the
next
steps
or
follow-ups
from
last
week,
we're
going
to
utilize
this
epic
of
epics
to
track
the
overall
gitlab.com
racial
migration
project.
So,
if
you're
curious
about
where
we
are,
you
can
use
that.
A
Any
questions.
A
Okay,
moving
on
to
what's
happening
next,
first
one
was
from
me:
dimity
will
try
that
issue
linked
here.
It
may
be
directed
to
another
key
after
the
initial
triage,
so
stay
tuned,
please,
my
question
to
amy
is:
how
soon
do
you
need
this?
This
one.
C
Yeah
so
it
looks
like
this
has
been
a
factor
in
some
recent
incidents,
so
I
mean
if
we
could
get
it
into
1311.
That
would
be
helpful.
I
know
that's
quite
soon,
though,
but
just
in
there.
I
think
we
haven't
had
a
lot
of
time
to
dig
into
it
further,
but
if
it
could
be
picked
up
soon,
that'd
be
great.
A
D
A
Okay,
thank
you
joshua
to
your
next
item.
B
Yeah
amy,
you
pinged
me
on
a
couple
m's
for
also
maybe
not
the
cause,
but
could
have
helped
some
of
the
incidents.
Last
week
we
got
these
prioritized
for
13
11.,
so
update
there.
C
And
then
we've
been
working
out
most
of
last
week
we
spent
delivery
working
out
tasks
and
the
order
we
need
to
go
through
them
to
safely
deploy
a
duplicate
registry
setup
which
is
sort
of
desired,
set
up
for
the
gradual
migration.
C
C
Cool
so
yeah
thanks
so
much
for
everyone,
who's
helped
move
blockers
recently.
This
is
the
main
one
I've
highlighted,
which
I
think
to
answer
your
question
josh.
I
think
it
would
be
good
to
keep
it
moving
forward.
I
don't
think
it's,
let's
drop
absolutely
everything
to
solve
it
today,
but
if,
in
the
next
few
days
we
could
make
sure
that's
still
moving
that'd
be
super.
A
B
This
is
me,
my
name
there
just
a
little
highlight
here
since
this
this
I
was
looking
at
the
scope
multi-large,
and
that
includes
running
giddily
in
kubernetes.
B
One
item
is
that
we
have
found
with
some
customers
at
least,
and
not
everyone
is
that
giddily
currently
just
not
run
very
well
at
memory
consumed
environments.
So
if
you
have
like
memory
limits
on
pods,
it
can
have
a
bad
time.
So
there's
an
issue
open.
Initially
there
we're
kind
of
lacking
hard
data,
but
I
wanted
to
surface.
B
This
item
for
the
working
group,
because
we
might
want
to
try
to
parallel
process
this
one
with
the
getaway
team.
So
we
don't
end
up
having
this
be
a
long
pole
in
the
tent
to
move
italy
at
some
point
in
time,
so
sort
of
an
early
warning
that
we
know
of
that.
There
are
some
gremlins
lurking
here,
and
the
question
is
whether
we
want
to
try
and
how
proactive
do
you
want
to
be.
A
We
don't
have
any
representative
from
guillotine.
Maybe
I
show
you
why
cga
and
cj
and
mark
wood
to
this
working
group.
A
Thank
you
other
questions.
E
Yeah,
this
is
just
a
follow-up
on
the
earlier
comment.
Does
this
effect
need
to
be
confidential?
Is
there
a
reason
that
it
is
confidential.
B
Challenge
you
might
have
is
that
you
can't
you
can't
have
nine
confidential
ethics
referencing
confidential
setup.
It
becomes
this
like
weird
dependency
tree,
so
I'll,
try
and
look
into
this.
I
think
you
also
can't
currently,
oh
you
can
now
you
can
change
the
confidential
ethics.
That's
recent!
So
cool
I'll
check
in
it's
a
it's
a
great
question.
I
don't
know
I'll
find
out.
D
E
Also,
it's
it's
in
the
gitlab
board
group
and
I
think
we
still
can't
cross-link
to
the
get.com
group
from
a
gitlab,
org
epic
and
I
can
see
like
there's
a
mixture
of
issues
we're
going
to
link
to
from
gitlab.org
projects
and
then
probably
the
infrastructure
works
going
to
be
all
under
gitlab.com.
So
we
may.
C
I
think
we're
going
to
kind
of
link
them
in
as
in
the
description,
because
I
think
what
we
want
to
make
sure
is
we
don't
sort
of
lose
visibility
of
infrastructure,
so
in
data
stores,
there's
quite
a
nice
epic.
That
already
has
all
the
build
out
the
data
store
for
the
staging
tasks,
but
there's
not
much
visibility
if
you're
not
in
data
stores,
so
I
think
linking
them
in.
C
I
mean
yes,
ideally
having
something
where
we
could
have
an
epic
that
cross
links
across
all
of
these
repos
would
be
helpful,
but
I
don't
think
we
should
separate
them
away
from
this
parent.
C
B
And
there
are
some
epics
for
each
like
pre
and
staging
and
prod
and
so
on
and
so
like.
If
you
go
underneath
and
then
those
I
think,
do
nest
out,
there's
a
nice
description
under
pre
right
now,
since
we're
working
on
that,
if
you
click
on
it,
that
includes
a
whole
bunch
of
work
around
the
status.
I
think
also
data
stores
in
there.
It's
just.
B
It
also
includes
work
in
the
registry
and
helm,
chart
repository
projects,
and
so,
if
you're
going
to
have
six
dozen,
you
know
six
and
one
half
dozen,
the
other
around
someone
can't
join
the
epic
party.
Yeah
okay
cool
rather
rely,
I
think,
on
descriptions
as
opposed
to
like
rolling
them
up.
If
we
think
it's
me
like
90
in
front
and
like
10
product
like
doesn't
like
product
functionality,
we
can
move
it,
but
I.
E
D
A
Cool
we
reached
the
end
of
the
agenda,
any
other
topics.