►
From YouTube: 2021-08-11 GitLab.com k8s migration EMEA
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
Good
morning,
how
are
you
I
am
fine?
How
are
you
I'm
doing?
Okay,
how
much
time
do
you
have
today
before
you
end
your
day,.
B
B
B
B
B
A
Yeah,
I
think,
for
for
the
communities
migrations.
In
most
cases,
we
have
most
of
the
interesting
information
the
readiness
reviews
anyway
and
not
in
the
run
books
yeah.
Then,
let's
stay
consistent
for
that,
even
if
I
would
like
to
have
it
the
other
way
around.
But
at
least
we
know
where
to
look
for
so
realistically.
B
B
The
writing
is
review.
I've
got
a
chef
update
that
I
would
like
for
you
to
look
at
that's
specific
to
the
get
lab
hd
proxy
cookbook,
because
what
graeme
has
created
looks
legit
during
my
local
testing.
It
appears
to
work
as
desired.
B
A
Yeah,
just
ping
me
in
those
amazon.
A
For
the
readiness
review
by
the
way,
amy
made
the
suggestion
today
to
mention
and
the
how
do
we
call
this
meeting?
What
was
the
dna.
A
Meeting,
but
that
I
mentioned
that
we
are,
you
know,
progressing
forward
with
that
migration
and
that
people
should
be
careful
when
they
do
chef
changes
to
port
them
back
to
kubernetes,
as
you
will
end
up
with
divergence,
and
so
this
there
maybe
can
reinforce
that
in
the
americas
session
of
that
meeting.
I
could
do
that
and
I
didn't
link
the
radius
review
and
this
because
yesterday
you
said
it's
not
ready
for
general
review
yet
so.
A
C
One
thing
that
would
be
good
to
share
in
the
reliability
meeting
scarbeck
was
one
of
the
big
change
and
the
reason
like
I'd
like
us
to
have
a
readiness
review
in
some
state
before
we
move
to
canary
is
the
nginx
removal
so
just
to
try
and
have
as
many
people
as
possible
aware
that
that's
happening
so
that
when
we
do
move,
if
any
incidents
do
happen,
people
have
like
a
few
fewer
steps
of
what's
happening.
C
So
that's
the
other
big
bit
that
would
be
helpful
to
to
highlight
for
people.
C
C
So
something
we
have
a
good
plan
for
the
readiness
review
and
so
from
my
side
like,
I
think,
if
we're
happy
with
the
the
chef's
changes
and
we
have
a
draft
readiness
review
available,
so
people
know
about
nginx
and
they
know
that
this
is
coming.
Then
at
that
point,
I'm
happy
for
us
to
move
to
canary.
B
Yeah
so
assuming
henry
doesn't
have
any
further
feedback.
What
I'll
do
is
get
it
merged
and
then,
during
today's
dna
meeting
I'll
ask
for
volunteers.
If
no
volunteers
people
are
going
to
get
voluntold
and
I'll,
follow
our
guidelines
and
sign
out
issues
for
various
people,
and
I
think
at
that
point
tomorrow,
thursday,
already
maybe
I'll,
pursue
the
change
review
or
the
change
issue
to
push
canary
into
place.
C
Super
sounds
great,
sounds
great.
It
could
be
one
depending
on
who
the
eoc
is
and
depending
on
how
busy
they
are
might
be
one
we
could
consider
pairing,
so
they
can
see
it
happen,
but
it
obviously
depends
on
when
and
what
else
is
happening.
C
C
A
This
is
going
to
be
interesting
because
tomorrow
I
am
also
planning
to
do
the
production
rollback
test,
so
you
have
some
interesting
stuff
going
on
with
production,
but
this
should
happen
in
in
my
early
afternoon.
So
I
think
before
you
are
starting
with
your
work.
C
B
So
how
about
this
instead
alternative
the
readiness
review
again
pending
your
feedback
is
ready.
So
if
that's
what's
keeping
us
from
moving
to
canary
what,
if
I
just
work
a
longer
day
and
therefore
we're
pushing
stuff
into
canary
later
in
the
day,
lower
traffic
and
there's
not
going
to
be
a
deploys
because
well,
I
could
work
with
robert
it's
necessary
because
I
know
he
does
work
later
than
I
do,
but
at
least
at
that
point
graham,
is
not
going
to
be
doing
a
deploy
either.
C
That
could
be
an
option
yeah
that
could
be.
B
I
could
pair
with
some
members
of
the
eoc
at
that
point
too.
Just
so
they
see
what.
C
C
To
pose
it
right,
because
I
think
that
would
be
great,
because
I
know
a
lot
of
people
want
to
see
the
stuff
it's
hard
to
get
like
you
know.
We
don't
get
super
many
people
in
this
demo,
because
it's
always
a
bit
of
a
tiny
snapshot
of
what
we're
doing
and
they're
busy
doing
other
stuff,
but
yeah.
That
could
be
a
super
one.
B
The
chef,
mr
because
the
chef
part
is
geared
towards
helping
us
move
to
production
in
a
more
easier
fashion
and
the
right
industry
view
is
what's
currently
blocking
us
from
moving
canary
traffic.
A
C
Awesome
sounds
like
a
good
plan,
so
other
other
things
we
want
to
go
through
in
this
demo.
B
Demo,
wise,
I
don't
have
anything
to
really
demo,
I'm
surprised
it's
wednesday
already
almost
as
a
price.
It's
a
whopping
90
degrees
outside.
So
I
wouldn't
want
to
step
out
there.
C
Not
the
same,
it's
definitely
not
that
in
london,
okay!
Well,
how
about
it
sounds
like
we've
got
a
good
plan
right.
It
sounds
like
henry
could
definitely
give
it
some
time
to
read
through
this
readiness
review,
scumbag
ruben,
I'm
sure
you
both
also
have
plenty
of
other
things.
So
how
about
we
end
this
early,
get
some
time
back
now
and
then
discover
it.
C
Like
you
know,
if
you
do
manage,
I
mean
the
reliability
meeting
is
recorded
anyway,
so
you
know
if
we,
if
we
do
manage
to
switch
over
during
canary,
we
can
just
also
add
that
meeting
onto
our
kate's
workloads,
our
kate's
demo
playlist
whatever
it's
called
and
link
it
back
into
this
as
well.
So
we
don't
have
just
demo
twice.
B
Yeah,
okay,
I
think
the
final
thing
I
kind
of
want
to
make
sure
henry
is
aware
of:
is
the
change
request
that
graham
put
together?
I
need
to
make
a
few
changes
because
it
looks
like
a
lot
of
the
links
he
logged
or
put
together
is
pointed
towards
the
main
stage,
but
since
we're
only
touching
canary,
I
want
to
make
sure
that
we're
looking
at
canary
log
details
and
metrics.
So
I
might
ask
you
to
just
do
a
quick
second
run
through
of
that
cr.
I
think
you
already
looked
at
it
once.
A
C
Awesome
great
okay
sounds
like
a
good
plan.
Let's
see
how
we
go
awesome
all
right.
Thanks
very
much.
Everyone
speak
to
you.