►
From YouTube: Kubernetes 1.17 Release Team Meeting 20191205
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
A
A
Please
keep
telling
me
if
I
cut
out
hello
everybody.
This
is
week
11
of
the
kubernetes
117
valise,
it
is
Thursday
December
5th.
My
name
is
Guinevere
singer
and
I
will
be
hopefully
hosting
this
meeting
today,
barring
further
cutting
out
be
kind
to
each
other
and
observe
the
code
of
conduct.
Let's
hear
from
enhancements.
C
Perfect
timing,
because
I
had
like
a
coughing
fair
right
before
that,
so
bob
was
gonna
do
this,
but
he
had
a
meeting
pop
up
so
I'm
gonna
do
it.
Today
the
status
is
still
green.
We
haven't
had
any
real
changes
since
the
code
freeze,
it's
just
kind
of
coast
in
now,
so
the
stats
are
there
we're
tracking
22
things
for
alpha
for
beta
and
14
staple
all.
B
D
Well,
we're
green.
We
don't
have
a
lot
of
updates.
Actually
this
update
was
written
by
alina,
but
she
couldn't
join
us
today,
but
basically
there
is
nothing
blocking
right
now.
All
the
issues
that
are
currently
existing
have
been
currently
to
have
been
discussed
previously.
Sorry
in
other
meetings
here.
So
if
you
have
any
questions,
let
me
know,
but
everything
should
be
on
the
same
truck
I.
A
Have
an
update
for
those
who
aren't
part
of
that
discussion
on
I
believe
issue
number
eight:
five:
nine
zero
zero
that
one
was
removed
from
the
Maya
stone
yesterday,
because
it
appears
and
I'm
not
sure
why
not
percent
agree
with
this,
but
it
appears
that
I
can
I
can
go.
It's
sorry,
I
just
spoke
up.
I
can
go
and
find
a
little
bit
more
detail,
but
basically
the
plan
is
to
remove
that
test
entirely
and
there
is
currently
in
the
works.
There's
currently
work
being
done.
D
And
also
like
it
isn't
blocking
it
isn't
compromising
the
release
itself.
I
think
it's
just
making
noise
and
it
has
been
very
buggy
for
a
long
time
and
we
were
just
concerned
about
it.
But
since
it
is
not
under
release
itself,
it
might
be
with
some
configuration
stuff.
It
might
be
with
the
issue
itself
yeah.
But
you
know
so
long
didn't
read
it's
it's
not
under
kubernetes
side,
so
yeah,
that's
why
we
decided
to
remove
it.
Yeah.
A
E
So
this
is
Silvia
with
the
updates
for
bug
triage
and
just
looking
at
the
numbers,
The
Situation's
pretty
stable.
Since
yesterday
we
continue
to
have
status
green.
There
was
a
critical,
urgent
issue
for
a
failing
test
that
we
discussed
yesterday
and
that
has
been
closed
in
the
meantime
and
also
put
under
observation
by
CI
signal
as
a
precaution,
but
one
new,
critical,
urgent,
PR
popped
up,
and
it
this
was
added
to
the
milestone
today
or
yesterday.
E
F
So
that
one
specifically
is
looks
like
it's
critical
origin:
it's.
It
needs
a
test,
basically
to
make
sure
that
thing
doesn't
happen
again,
essentially
a
problem
with
the
service
cider.
If
the
service
cider
is
missing,
it
will
cause
the
API
server
to
fail.
So
that's
something
that
also
needs
to
be
cherry
picked
over
to
117,
so
I'm
going
to
be
watching
that
one
throughout
the
day.
A
All
right
cool,
let's
hope
that
gets
fixed-
is
there
anything
in
the
important
soon
boats
that
we
should
worry
about
for
this
release.
A
E
A
I
guess
we'll
have
to
see
if
we
want
to
this
this
one's
in
the
milestones.
F
A
F
A
Might
be
able
to
give
a
little
bit
of
update
on
docks,
we
have
been
running
into
a
COI
CLA
issue
with
the
overall
docks
PR,
because
someone
has
since
lost
their
company
CLA
on
the
email
that
that
commit
was
made.
This
is
a
commit.
This
is
a
docks
commit
consisting
of
I,
think
45
different
people.
Basically,
everybody
who
had
docks
change
is
committing
into
this
one.
Big
docks
PR
for
117
and
the
docks
team
is
currently
working
to
remove
that
commit
and
recommit
with
someone
who
has
a
CLA
signed
email
address.
G
Responses
from
four
to
are
okay,
with
the
way
things
are
right
now,
and
then
we
have
storage
and
API,
who
put
in
a
bunch
of
note
changes
since
this
morning,
so
Jordans
been
in
there
pending
some
of
the
API
updates
and
yeah,
so
I'll
ping,
the
other
ones
this
afternoon,
with
a
slightly
updated
note,
I'll
send
that
to
you
when
before
I
send
it
out
just
to
make
sure
the
language
is
appropriate,
that
things
are
progressing
just
hate
to
kind
of
move
everything
into
the
right
spots
and
should
be.
We
should
be
good
great.
B
G
H
We
are
slightly
shifting
to
a
yellow
a
little
bit
because
we
do
not
get
any
response
from
network
hope.
This
will
change
soon,
but
inside
of
that,
the
drafts
for
the
storage
blog
posts
are
available.
We
added
also
to
the
protocol,
and
hopefully
we
can
also
add
later
the
link
to
the
draft
for
the
cloud
provider.
A
Great,
thank
you.
How
have
you
tried
to
contact
network.
H
We
were
in
contact
always
like
with
elites
and
they've,
followed
us
to
remind
us
to
talk
with
some
of
their
people,
contributing
we
had
an
active
communication.
It's
a
lot
a
little
bit
down
over
Thanksgiving
and
since
yet
we
do
not
get
any
response.
So
we
start
talking
again
to
all
the
leads
and
trying
to
find
someone
who
can
help
us.
There.
A
A
H
Basically,
we
just
need
to
get
some
response
on
our
requests
and
I
mean
we
offer
them
to
help
writing
the
blog
post.
But
of
course
we
need
some
information.
A
Okay,
alright
I'll
tag
you
in
it:
hey
cool
release,
branch
management.
F
Hello,
hello,
so
basically
all
the
stuff
that
was
said
earlier
about
the
issues
and
the
bugs
we
were
on
truck.
But
now
some
things
are
floating
in,
so
that
API
server,
side,
er,
split
bug,
as
well
as
letting
in
the
add-on
resizer
I'm
gonna,
be
looking
through
the
issues
and
PRS
again
today,
right
after
this
meeting,
so
I
will
poke
people
who
need
poking.
A
B
A
A
A
A
Most
of
my
update
is
that
I
started
conversation
going
about
how
unresponsive
the
sick
of
chairs
have
been
during
this
release.
Cycle
I
have
seen
this
in
previous
release
cycles
as
being
a
team
member
as
well
the
amount
of
work
that
it
takes
to
find
a
problematic
pull
request,
find
the
person
who
owns
and
find
the
person
who's
supposed
to
review.
A
It
then
fight
their
correlating
slack
handle
and
then
DM
them
takes
so
much
time
that
by
the
time
you
have
the
DM
open,
you
forget
what
you
were
going
to
talk
to
them
about,
because
you've
gotten
distracted
by
the
jillion
other
release
team
related
issues.
So
anyway
long
story,
short
I,
open
an
issue
and
I
would
like
it.
If
you
all,
could
either
+1
some
comments
or
share
some
personal
experiences
of
this
happening
to
you.
A
We
want
to
make
sure
that
the
community
is
aware
that
this
is
a
community-wide
issue
and
it's
not
just
a
release
team
and
it's
not
just
a
contributor
experience.
This
is
a
problem
for
everyone,
including
the
people
who
aren't
responding
really.
So
it's
funny
because
the
issue
has
been
up
since
yesterday
afternoon
and
the
only
people
commenting
on
in
our
control
box
and
release.
Folks,
so
I
said.
F
F
A
I
The
only
thing
I
do
want
to
say
is:
for
the
most
part,
we
should
try
and
keep
discussion
regarding
this
issue
in
that
github
issue,
because
I
feel
like
this
is
going
to
be
a
very
sensitive,
slash,
heated
topic
and
it
should
all
be
in
one
place
like
I
know.
There's
discussion
happening
in
the
chairs
and
sig
leads
for
tech,
leads
channel
in
slack
and
I,
already
kind
of
want
to
wake
and
drive
that
back
to
the
air
shooter.
So
that's.
F
That
my
two
sons
for
it
yeah,
some
of
that
chat-
has
been
mirrored
into
the
issue
already,
but
yeah,
no
you're,
totally
right,
I
I,
don't
I!
Don't
expect
us
to
not
chat
about
this
on
pretty
much.
Every
cig
call
for
people
who
have
seen
this
issue
at
this
point
like
we're
going
to
talk
about
it
internally
as
well.
The.
A
F
And
please
I
would
say:
I
want
this
to
I.
Think
Gwen
said
it
very
nicely
in
the
issue
that,
like
we
want
to
drive
this
towards
positive
action
right,
we
don't
want
this
to
be
a
pile
up.
So
if
you
see
something
that
has
been
said
already,
don't
say
like
yes,
me
too,
or
what
like
the
+1
is
fine,
if
you
have
additional
things
to
add,
that's
fine
as
well
I'm
trying
to
make
this
a
I
mean
it's
hard
to
not
assign
blame
because
but
try
to
make
this
something,
that's
blameless.
F
A
The
opposite
of
what
we
want
all
right
great
with
that
I
think
well,
I
actually
have
a
question.
I,
don't
know
if
Jorge's
on
the
call
no
never
mind
I
will
not
be
making
the
call
tomorrow.
So
I
will
have
one
of
my
team.
Okay,.
F
A
A
A
B
E
F
Sort
by
sort
by
or
just
click
the
milestone
on
one
of
the
issues,
so
you
can
just
tackle
the
milestone.
One.
F
F
A
G
G
G
F
G
F
F
A
F
There
are
no
updates
on
the
issue.
There
are
multiple
there
like
a
thousand
issues
open
for
this
honestly,
so
yeah.
If
you
look
at
the
block
releases
on
block
releases
on
non-synthetic
clusters,
they're
a
bunch
of
things
there,
it's
kind
of
a
spider's
web
of
things,
but
yeah
moving
that
into
milestone
18
is
fine.
119
is
fine.
F
A
F
A
A
Landed
on
me
because
it's
it's
been
open
for
a
year,
that's
to
be
a
member
noticed
to
be
a
manager
who
gets
to
be
an
owner.
A
A
A
This
is
related.
This
is
honestly
the
same
issue.