►
From YouTube: k8s 1.16 - Week 2 - Release Team Meeting 20190708
Description
Release details: http://bit.ly/k8s116
A
All
right,
hello
and
welcome
to
week
two
of
1/16
kubernetes
release.
Today's
date
is
July.
The
8th
that
is
Monday
welcome
everybody.
This
is
our
second
release.
Meeting
for
116
today
is
going
to
be
a
lot
more
of
introductions
and
making
sure
that
everybody
knows
each
other
and
is
familiar
what
the
team
is
doing,
and
then
we
have
the
agenda.
I've
lazy
linked
the
agenda
in
the
chat
before
we
get
into
it
a
few
housekeeping
things.
Please
go
and
put
your
name
if
you're
in
attendance
here
on
the
attendees
section
for
today's
meeting.
A
A
This
meeting
is
being
recorded
and
will
be
posted
to
YouTube,
and
we
want
to
make
sure
that
everybody
follows
the
kubernetes
code
of
conduct,
which
says
please
treat
each
other
with
respect
in
your
words
and
your
conversations
so
I
would
ask
that
you
all
adhere
to
that.
Thank
you
very
much
and
finally,
if
I
can
get
a
note-taker,
because
it's
kind
of
hard
to
run
the
meeting
and
take
notes,
please
place
your
name
in
it.
You
get
the
prestigious.
A
Second
spot
in
the
agenda
as
the
notice,
the
note-taker
and
it
will
forever
be
filed
on
the
internet.
So
that
is
you
know.
Internet
points
abound,
okay,
so,
let's
get
into
it.
I
have
some
good
news
for
the
team.
Everybody
has
selected
their
shadows.
If
you
pop
over
and
take
a
look
at
the
release,
team
marked
down
dock
under
the
116
release,
I'm
lazy,
linking
it
there
for
everybody,
you
can
check
out
all
the
leads
and
the
shadows
for
the
team
and
their
associated
handles
about
slack
and
get
up.
A
A
A
One
more
thing
before
I
do
that
I
should
have
everybody
that
is
a
named
shadow
to
the
kubernetes
release
team
Google
Group,
which
means
they
should
have
the
calendar
invites,
and
you
may
also
notice
that
a
whole
bunch
of
additional
invites
and
milestones
and
116
came
out
last
week,
they're
just
placeholders
to
give
everybody
a
heads
up.
The
only
thing
I
haven't
added
to
the
calendar
and
invited
everybody
to
is
the
burn
downs.
So
just
keep
that
in
mind.
They'll
come
out
a
little
later
in
the
release,
but
over
to
introductions.
A
B
Absolutely
I've
already,
given
my
hello,
who
am
I
last
time
so
I'm
gonna
hand
it
over
I,
see
three
of
them
are
on
today.
Everybody
knows
Bob
killin,
mr.
bobby
tables.
He
is
in
the
midst
of
finishing
painting
his
house
he's
in
through
a
huge
move,
so
he
gets
the
checkbox
that
go
ahead
and
miss
today's
meeting,
but
I'll
pass
it
over
to
another.
Familiar
face.
That's
been
around
here,
which
is
Maria.
C
B
Good
choice
of
headphones
as
well
and
then
Eddie
is
well
from
Microsoft.
It
seems
were
we're
a
big
Microsoft
fanboy
team
over
here.
C
A
F
F
I
A
J
Think
two
days
gonna
make
it
today
so
I
guess
as
a
shadow,
I'll
go
first
and
then
I
think
there's
a
couple
other
people
on
here.
My
name
is
Seth.
I
worked
for
a
trailer
I'm,
a
site,
reliability
engineer
my
first
round
doing
stuff
for
the
kubernetes
release
team
and
really
excited
to
be
here.
K
M
Hi
I'm
Chris
I
did
the
DevOps
released,
sir
sorry
a
little
nervous
today,
first
time
in
in
this
thing,
it's
very
exciting
for
me,
so
I'm,
the
DevOps
team
leader
at
the
City
of
Ottawa
and
I
am
really
excited
to
help
participate
and
contribute
back
to
this
awesome
community.
So,
looking
forward
to
this
next
12
weeks,
thanks
for
having
me.
N
P
Q
A
Thank
You
Taylor
and
then
nice
new
haircut
get
a
good
a
lots
of
feedback
in
the
in
the
chat,
they're,
fantastic,
alright,
so
I
think
that
concludes
introductions.
If
anybody
is
on
the
call
and
want
to
introduce
themselves
feel
free
to
interrupt
we'd
love
to
get
to
know
you
all.
So.
Obviously,
that's
super
important
moving
on
in
the
agenda
here,
I'm
going
to
just
provide
an
update.
A
This
is
the
last
week
of
kind
of
more
administrative,
getting
everybody
set
up
and
make
sure
that
everybody's
got
the
invitations
and
the
right
access
to
things,
and
then
we
kind
of
move
into
the
the
general
agenda.
That's
from
the
template
at
the
top,
where
all
the
teams
give
their
updates.
So
I
just
want
to
make
sure
I'd
kind
of
added
everybody
to
the
Google
Group.
So
this
should
get
the
calendar
invites.
If
that's
not
the
case,
please
feel
free
to
ping
me
on
slack
and
we'll
make
sure
that
that
gets
fixed.
A
A
Next
upcoming
milestones,
I
see
the
the
agenda
getting
patted
out
here.
Thank
you,
Jeff
for
getting
those
notes
in
is
the
116
alpha
one
next
Tuesday
the
16th,
so
I
want
to
make
sure
that
the
release
engineering
team
is
ready,
willing
and
able
to
be
able
to
cut
the
first
alpha
release
next
week.
We
don't
have
yes
go
ahead:
Steven
yeah,
I'll
be
I'll,
be
cut
ed,
so
you'll
be
cutting
it
yelling
good,
yeah,
okay,
fantastic
all
right!
A
A
Okay,
I'm
gonna,
keep
going
I
might
do
the
project
board
at
the
end.
Let
me
just
keep
moving
through
this
handbook
updates
for
testing
for
a
role,
removal,
I've
kind
of
followed
the
thread
so
for
those
following
along
at
home.
At
the
end
of
1:15,
we
collapse
this
role
called
test
infra
and
some
of
the
responsibilities
of
that
role
that
weren't
automated
went
to
other
teams
now
I
think
everything's
been
updated,
but
that
issue
is
still
open.
R
So
it
was
testing
for
a
certain
foreign
call
itself,
so
within
cig
testing,
the
branch
manager
role,
which
is
now
part
of
the
release,
managers,
group,
sub-project,
thingy,
nabob
and
then
bug
triage.
We
actually
haven't
transferred
any
roles
in
to
bug
triage
any
duties
into
bug
triage,
but
that
might
change
as
I
sweep
the
handbooks
so
stay
tuned.
Okay,.
A
B
This
is
gonna
be
relatively
short
because
we're
just
now
kicking
off
the
cycle.
Well,
last
week,
I
sent
an
email
off
to
Kade
of
just
saying:
there's
a
call-out,
and
if
you
can
please
try
and
make
sure
that
you
take
care
of
your
your
issues
to
either
move
it
to
a
correct
milestone
or
to
make
sure
that
there
is
a
issue
that
has
been
created.
The
tracking
sheet,
as
you
can
see,
is
a
little
bit
of
a
different
link
going
on
to
it
this
time,
I
think
somebody
jumped
the
gun
and
took
the
bit
literal.
B
So
we
have
a
new
tracking
sheet
that
Bob
killin
had
sort
of
creating
a
little
bit
of
the
automation
around
behind
it,
so
we
can
actually
just
type
in
the
issue
number
and
it
will
pull
in
the
github
issue
name
to
do
it
as
well
he's
gonna
look
at
it,
then
helping
make
this
even
go
a
little
bit
further,
perhaps
filling
in
some
more
information.
But
again
this
is
one
step
in
a
right
direction
for
something
that
is
spreadsheet
madness
at
the
end
of
the
day.
B
So
after
this,
this
meeting
today,
I'll
be
meeting
with
the
rest
of
the
enhancement
team
kind
of
looking
over
really
what
it
is
that
we
need
to
tackle
for
closing
out
the
current
milestone,
looking
at
existing
issues
that
have
tracked
yes
and
track
no
labels
so
towards
the
end
of
this
week,
we'll
have
a
better
idea
of
really
how
many
issues
and
enhancements
we'll
be
tracking
for
this
release
cycle.
So.
R
B
A
B
R
R
You
may
see
there
what
I
want
to
do
is
kind
of
go
through
the
each
of
the
the
books
around
like
onboarding
and
clean
some
of
that
stuff
up
and
eventually
turn
that
into
like
an
onboarding
github
template
instead
right,
so
you
can
click
a
few
buttons
and
know
exactly
what
you
need
to
do
or
like
the
lead
can
use
that.
But
eventually
that
will
be
done.
Maybe
in
a
maybe
in
a
week
or
two.
R
The
next
thing
that
we
need
to
do
is
notify
all
of
the
people
who
were
not
selected
as
shadows,
so
that
will
be
happening.
Josh
has
an
email,
template
I
need
to
review
the
email
template,
maybe
pop
a
few
things
in
there
and
and
then
we're
gonna.
Send
that
out
so
expect
that
I
want
to
say
end
of
today
or,
if
not
sooner
well,
don't
expect
it
because
you're
all
selected
so
you're
here
and
blah
blah
blah
right
and
then
finally
do
you
do.
R
Finally,
I
worked
on
doing
an
update
to
the
release
team
lead
handbook
and
the
update
is
primarily
grammatical,
stuff
fixing
some
links,
anything
that
has
changed
in
the
process
at
some
point,
just
making
sure
that
we
capture
that
those
notes,
so
that
those
the
least
team
lead
gets
stuff
off
to
a
good
start.
So
nothing
too
crazy.
There
I've
linked
the
PR
for
that.
If
y'all
want
to
review
it
and
correct
me
on
certain
things,
but
outside
of
that
I
think
I'm
good
Joshy
got
stuff
I.
R
S
S
A
F
F
That's
really
important
important
point
that
I've
been
talking
with
with
a
lot
of
people
in
the
community,
see
I
see
you
know
a
signal
wise,
a
we're
gonna
be
streaming
as
I'm
about
to
do
a
ton
of
failures
by
impact
a
many
many
of
the
cigs
in
the
in
the
community.
So
if
you're
looking
for
a
place
to
contribute,
you
might
want
to
stick
around
take
a
look
at
all
the
issues
and
see
which
ones
you
find
interesting
with
that
in
mind
and
let's
get
started
so
first
off
project
bore
a
we're.
F
Gonna
do
our
best
during
the
early
in
the
release
cycle,
to
keep
a
tree
to
tree
a
and
keep
it
up
to
date
as
much
as
possible,
and
that's
gonna
be
the
center
of
all
di
signal
knowledge
now
master
blocking.
So
last
time,
I
checked.
There
was
one
test
failing
and
the
failure
is
related
to
being
able
to
add
or
delete
worker
notes
from
a
from
a
coaster
currently
that
one
that
one
had
has
had
no
response.
As
of
as
of
right
now,
who
will
work
this
week
to
a
two-headed
coin?
F
S
S
R
F
Yeah,
you
can
take
it.
My
the
attack
plan
from
CIC,
no
was
just
to
you
know,
go
to
their
you
go
to
the
issue
say
be:
what's
the
word
that
I'm
looking
for
a
yeah
just
it
just
we
just
work
a
little
bit
harder
on
the
conversation
side
a
so
they
to
make
sure
that
they
are
right
that
they
are
like
happening,
but
they
having
a
meeting
a
sounds
good.
It
won't
set
it
up
and
yeah.
S
I
think
what
last
really
showed
us
is
that,
if
those
are
the
long
link
has
failed,
we
can't
necessarily
see
all
of
the
reasons
why
they're
failing
and
in
the
issues
themselves,
the
sig
scalability
team
will
kind
of
deal
with
one
reason
at
a
time,
but
they
won't
necessarily
tell
us
if
there's
other
stuff,
that
they
don't
have
PR
for.
Yet,
if
you
follow
me,
yeah.
F
Yeah
yeah
absolutely,
and
so
that's
been.
Okay,
that's
been
that's,
probably
a
problem
since
I've
been
in
the
interval
listing
so
there's
a
super
interesting
they're
always
super
complicated
and
they
stay
on
top
of
them
from
same
top
of
them.
Synchronizing
between
six.
It's
always
been.
It's
always
been
an
issue.
I.
F
Yeah,
okay,
so
just
to
summarize
action
item
we'll
get
some
a
will
get
the
convert.
A
will
make
sure
that
there's
a
lot
more
conversation
between
between
our
team
and
six
scalability
other
than
that.
Just
to
summarize
mustard
walk
in
there
are
some
really
cool.
Cac
glossary
lifecycle,
this
railing,
which
are
not
able
to
add
all
the
lead
notes.
If
anybody
wants
to
take
a
look
at
them
and
work
with
sig
glossary
lifecycle.
F
Moving
on
from
that
one
muster
in
forming
a
lot
of
tests
and
a
lot
of
jobs
are
failing.
So
let
me
start
with
the
easy
ones
flakes
a.
We
will
keep
an
eye
on
most
of
the
flakes,
but
nothing
seems
part
took
a
particularly,
but
with
with
them
on
the
failing
jobs,
though
there
are
a
handful
of
there
are
actually
a
couple.
Sick
is
sick
storage,
test
away
the
having
film
for
the
last
couple
days
and
they
are
affecting
some
of
great
jobs.
F
There's
also
the
issue
79
74
0
in
the
95
tree
tree,
which
are
the
second
and
third
bullet
points
under
the
failing
test.
Those
are
also
a
really
interesting.
We
feel
we
figure
than
the
issues
were
to
solve
a
song
end
to
end
test
not
be
enough
improperly
from,
for
example,
we
have
one
in
which
a
cubic
thought
was
trying
to
create
a
deployment
with
an
API
group
that
was
helping
deprecated
a
hijacked,
see
a
signal.
F
We
actually
work
with
one
of
the
see
a
signal
with
one
a
with
come
in
with
a
contributor
who
applied
to
the
see
a
signal
wall,
and
we
had
a.
We
merge
a
couple
pairs,
but
does
seem
to
not
actually
fixed
it.
So
we
will
keep
on
investigating
to
see
what
the
underlying
solution
a
underlined
solution
will
be
for
those.
Besides
that
there's
also
a
far
away
there's
also
far
wall
test,
that's
been
showing
up
in
a
couple
down
grid
jobs
in
a
stream
informing.
F
It
might
possibly
have
something
to
do
with
a
some
work
that
6k
6
scalability
has
been
doing
in
which
they
are
quick,
am
I
having
a
haven't
got
in
the
entire
history,
on
the
work
that
they're
doing.
But
my
understanding
is
that
the
closer
side
they
are
being
closed
off
from
the
internet,
so
some
tests
actually
need
access
to
the
Internet
to
it
to
work
to
work
out.
F
We
need
to
do
a
little
bit
more
investigation
in
that
the
author
Edition,
for
this
release
cycle
is
that
we
are
going
to
start
telling
you
all
how
they
release
miscellaneous
jobs
are
doing
in
the
in
the
secret
list.
Dashboard
right
now,
a
there
are
two
jobs
spelling
in
that
one
periodic
packages
install
that
and
what
is
verified.
We
also
need
to
investigate,
what's
what's
wrong
with
the
what's
wrong
with
them,
create
an
issue
and
get
something
working.
F
R
A
L
Visit
a
shadow
introduction,
we
have
two
updates,
so
the
first
one
is
that
we
gave
the
release,
notes,
website
and
angular
8.1
update,
which
looks
fine
and
then
the
other
update
is.
We
have
an
open
pool
request
on
kubernetes
kubernetes,
which
adds
additional
documentation
to
each
plea
requests,
so
it
would
be
cool
if
we
could
get
this
into
the
master,
somehow
that
we
can
cross
link,
release,
notes
and
documentation
and
like
caps
and
stuff
like
that,.
A
A
A
So,
even
though
we're
talking
EU,
we
might
be
a
little
more
friendly
to
those
times
because
it's
the
middle
of
the
night
in
Australia,
whereas
the
middle
of
the
day
in
EU,
you
could
catch
them
at
the
end
of
the
day,
eastern
Australia
or
China.
So
what
what
were
your
points?
Sir
sure
I'd,
like
to
kind
of
solicit
your
feedback?
Given
that
you'd
have
some?
You
said
you
don't
wouldn't
like
to
do
a
meeting
and.
L
L
Have
this
we
have
Paul,
which
comes
from
the
Australian
time
zone,
Eastern
Australian
and
it's
not
far
away
from
the
US
West
Coast
time
zones
or
five
hours
approximately,
and
the
idea
was
to
schedule
the
meeting
by
weekly,
different
time
zones
that
sometimes
I
am
on
their
bad
time
zone
and
sometimes
other
guys
on
a
bad
time
zone
that
we
just
can
switch
to
recording
and
yeah.
Stick
to
that.
Okay.
A
A
I
just
don't
know,
it
would
be
interesting
to
know
how
much
India
we
would
catch
because
I
think
there's
at
least
three
or
four
people
from
India,
so
that
would
be
very
early
morning
their
time.
Unless
we
do
it,
you
know
6
or
7
p.m.
Pacific
which
I'm
interested
in
entertaining.
So
how
about
I?
How
about
I,
throw
a
throw
at
a
doodle
and
throw
out
some
time
zones
things
that
work
and
see
what
most
people
want
to
jump
on
and
then
we'll
just
go
from
there.
S
Gonna
say
yes:
I'm
gonna
suggest
two
meetings,
which
is
what
we've
had
in
some
cycles
rather
than
flipping
every
other
week,
just
because
I'm
all
for
having
an
India
friendly
meeting,
but
it's
largely
impossible
for
somebody
in
Eastern
Europe
to
attend.
I,
don't
know
if
we
have
anybody
in
the
list
who's
currently
in
in.
A
S
R
We
moved
quite
quickly
on
those
and
and
missed
little
things
like
like,
quoting
and
and
and
like
having
a
glob
outside
of
a
quote
and
different
things
like
that
short
version
is
so
Peter
Hannes
Peng,
Fay,
DIMMs
Liggett,
a
few.
A
bunch
of
people
like
work
to
bring
the
release
repo
back
into
a
good
state.
R
Ipr
de
revert
for
some
of
those
changes,
so
those
dashboards
should
start
to
clean
up
the
ones
that
we,
the
ones
that
you're
interested
in
investigating
the
two
failing
ones
release
verify
the
reason
that
release
verify
is
failing
right
now
is
release
verify
calls
a
week
verify
target
which
runs
a
verify.
Shell
check
script,
since
we've
pulled
all
of
the
shell
check
chain
out
of
kubernetes
release.
That
script
starts
to
fail
now,
so
we
need
to
have
a
I,
don't
know,
she'll
check,
failures,
thing
or
pull
the
the
verify.
R
R
So
periodic
packages
installed
Deb
exists
inside
of
kubernetes
cube,
ADM
repo,
so
under
tests
eat
it
a
ete
packages,
something
like
that
and
then
like
verify,
verify,
install
Deb's
or
something
right
that
that
test
has
been
failing
for
forever
right,
it's
more
specifically,
it's
been
failing
since
I
believe
the
beginning
of
the
1:14
release
cycle
and
the
reason
for
that
is
because,
again
yet
again,
a
change
to
kubernetes
release.
So
what
changed?
R
R
The
CSD
I
see
I
signal
stuff
before
and
I
was
incredibly
confused
about
how
all
the
stuff
works.
So
I
did
a
kind
of
analysis
of
all
of
that
and
wrote
up
a
github
issue
that
github
issue
is
linked
to
is
in
the
notes,
and
it's
like
it's
a
it's
like
a
really
really
really
long
right
up.
So,
if
anyone
who
is
not
familiar
with
testing
for
our
CI
signal
is
curious
about
some
of
that
stuff,
how
jobs
are
built,
how
they're
run
which
targets
they
affect
and
all
that
kind
of
stuff.
R
R
The
reason
that
they
were
failing
was
because
they
were
looking
for
something
that
that
kubernetes
release
is
responsible
for
publishing
right,
so
whether
it's,
whether
it's
making
sure
that
the
packages
exist
or
making
sure
that
the
making
sure
that
the
binaries
so
like
the
eBay
DM
jobs
were
failing,
because
the
cube
CTL
binaries
didn't
exist,
keep
CTL,
binaries
and
exists,
because
when
we
tried
to
publish
when
we
made
changes
to
the
shell
checking
stuff,
the
changes
to
the
shell
checking
stuff
affected.
The
scripts
that
publish
that
publish
are
staged.
R
The
binaries
to
our
GCS
buckets
once
we
undid
all
of
that
stuff.
They
started
to
clean
up
right.
So
you
would
have
seen
that
across,
like
somewhere
between
July,
1st
and
July
3rd,
or
something
that
signal
got
clean
around.
Then
all
of
the
issues
that
were
open
for
that
I've
closed
and
linked
back
to
that
analysis
that
I'm
that
I'm
still
kind
of
going
through.
R
So
the
the
short
version
is
be
very
careful
when
you're
making
changes
to
kubernetes
kubernetes
release
I'm
working
on
putting
tests
in
place
to
make
sure
that
the
that
it's
safer
for
us
to
make
changes
because
I
don't
think
that
the
right
answer
is
for
us
to
block
on
like
to
block
on
tests
when
we
can
be
fixing
things
and
moving
the
repo
forward.
The
the
second
part
is
other
release
engineering
stuff
right.
That's
that
you
should
look
out
for
that
may
cause.
Some
friction
in
the
repos
may
cause
additional
test
failures.
R
So
this
one
not
too
big
of
a
problem:
the
ability
to
build
and
build
the
Deb's
and
rpms
with
one
script
right
so
right
now.
It's
basically
kubernetes
release,
debian
debian,
jenkins,
SH
and
then
Jenkins
that
SH
will
spin
up
a
docker
container.
That
docker
container
will
run
a
build,
go
script
that
is
in
that
is
in
that
folder
and
that
will
spit
out
the
art,
the
the
Deb's
right
and
then
on
the
RPM
side.
R
It's
like
the
kerbin,
IDs
release,
RPM,
slash
bill,
dot
s
age
or
something
and
build
that
sh
is
our
docker
or
something,
and
then
that
one
is
part
of
like
theirs.
Then
there's
an
entry
script
and
the
entry
script
is
like
you
know,
take
some
arguments
right.
The
short
version
is,
there
are
two
different
ways
to
build:
Deb's
and
rpms
I
created
a
build
slash
package
in
docker
script,
which
basically
calls
out
to
the
respective
the
the
respective
places
where
those
scripts
are
built.
R
So
now
now
that
that
exists,
I
can
created
also
make
targets
for
those
so
that
we
can
pop
those
make
targets
into
the
jobs
that
run
that
stuff
right.
So
now
that
means
we
can
change
the
underlying
implementation
of
the
make
targets
without
having
to
also
change
the
CI
jobs
right,
which
means
we
can
move
a
little
quicker
in
terms
of
making
improvements
there
right.
The
second
one
is
verifying
that
the
Deb's
and
rpms
are
actually
published
right.
R
So
there
is
a
script
that
exists
again
in
the
kubernetes
cube,
ADM
repo
right
that
verifies
that
we
can
actually
that
we
have
actually
published
the
Deb's
and
rpms
right.
So
my
thought
is
that
it's
ridiculous
that
it's
in
qadian,
so
I
have
a
PR,
that's
linked
there
that
moves
that
script
into
kubernetes,
release,
hack,
verify
hack,
published
packages,
verify
published,
or
something
like
that
right.
That
script
is
also
wired
up
to
test
in
for
PRS
that
are
in
flight.
R
What
we
should
be
able
to
do,
then
I've
also
split
out
some
of
the
logic.
Basically,
what
it
was
doing
was
looking.
It
would
spin
up
a
debian
container
or
a
bunch
of
container
and
then
install
yum,
which
is
not
a
good
idea
and
and
do
a
check
for
the
things
that
do
a
check
for
each
of
the
packages
that
exist
in
the
repo
right.
That
is,
the
logic
has
been
split
out
so
that
you
can
do
now.
R
You
can
do
like
a
make
verified,
Deb's
and
make
verify
rpms
right,
so
those
will
run
as
two
separate
CI
jobs
and
we'll
get
more
signal
there.
They
will
go
on
to
the
I
believe
all
of
those
jobs
I
push
on
to
master
informing,
because
at
the
end
of
the
day
like
they
matter,
whether
or
not
we
can
cut
releases
as
we
go
through
the
criteria
for
what
master,
blocking
and
forming
miss
miscellaneous
and
I
don't
know,
maybe
I'll
create
another
dashboard.
R
That's
like
artifacts,
or
something
like
that,
so
that
we
were,
you
were
actually
like,
not
considering
it
to
be
miscellaneous,
but
more
like
this
is
important.
All
right,
you
know
like.
If
we
don't
do
like.
If
these
jobs
don't
work,
then
we
won't
be
able
to
release
kubernetes
right,
so
that
was
some
of
the
cleanup
I
did
over
the
last
week.
Some
of
it
is
still
in
progress
and
I've
been
talking
a
lot.
So
I'll
stop
talking.
You.
R
A
Okay,
so
I
think
in
summary,
because
there
was
a
lot
said
there,
release
engineering
team
team
is,
is
doing
their
best
to
improve
and
validate
kubernetes
releases
and
make
sure
that
they're
going
out
in
the
right
shape
right
form
and
we
also
creating
more
tests.
So
CI
signal
as
monitoring
the
release
set
of
tests
that
you're
now
taking
into
account
so
I
guess.
This
is
just
evidence
of
the
released
engineering
teams
coming
together
and
actually
moving
making
some
changes
all
right,
Thank,
You,
Steven,
a
quick
call
to
anybody
else.
A
Fantastic
Thank,
You,
vineeth,
okay
and
off
the
back
of
that
next
week,
we'll
be
going
to
the
traditional
template
where
each
team
provides
an
update
and
is
responsible
for
their
update.
So
I'll
go
ahead
and
put
the
templated
agender
in
for
next
week.
After
this
call,
so
leads,
shadows
show
up
with
any
items
for
your
associated
updates
and
any
things
that
we
need
to
discuss
as
part
of
those
updates.