►
From YouTube: Kubernetes 1.17 Release Team Meeting 20191111
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
Good
morning,
everyone
this
is
week
eight
of
the
kubernetes
117
release.
It
is
November
11
in
the
United
States.
It
is
Veterans
Day.
At
this
point,
I
would
like
to
think
all
members
on
this
team
who
have
been
serving
in
the
United
States
Armed
Forces
for
their
service,
and
my
sincere
hope
that
we
as
a
society
take
care
of
the
humans
who
serve
in
these
roles.
I
also
would
like
to
remember
everyone
that
we
are
under
the
kubernetes
could
have
conduct
and
to
treat
each
other
with
excellence.
A
Please
put
your
name
in
the
attendance
sheet
and
I
forgot
to
introduce
myself.
I
am
going
to
be
R
Sanger,
your
release
lead.
Do
we
have
a
note-taker
for
today,
I.
C
C
B
With
me,
okay,
so
hi,
it's
great
to
be
back.
Our
current
status
is
yellow
attending
a
little
bit
to
orange,
but
I
decided
not
to
put
red
because
compared
to
the
past
couple
of
weeks,
we
have
been
having
a
great
improvement
and
I
want
to
really
thank
our
team
because
they
have
been
working
very,
very
hard.
Trying
to
reach
out
to
the
right.
B
People
and
I
also
want
to
thank
the
people
that
might
not
be
in
this
meeting,
but
I
part
of
the
coronaries
family
and
I
have
seen
a
great
improvement
and
the
response
rate
and
how
not
only
day
they
address
the
issues
or
they
they
not
only
acknowledge
the
issues,
but
they
address
them.
They
have
been
very
good
at
it,
perhaps
because
it's
cute
comment,
but
we
have
had
great
response.
So
as
a
result,
open
god
unmastered
blocking
everything
is
good.
We
have
nine
passings
explaining,
which
is
a
huge
improvement
on
mustering
forming.
B
We
have
13
passing
a
flaking
and
two
failing
there's
just
one
that
I
am
a
bit
concerned
about.
That
is
the
windows
side.
We
have
reported
it,
but
it's
failing
really
bad.
So
we'll
we'll
keep
an
eye
on
it
and
try
to
solve
it
as
soon
as
possible,
but
I
mean,
as
I
said,
it's
still
an
important
and
we're
making
some
progress.
Then,
on
the
release
miscellaneous
we
have
six
passing
into
flaking
and
the
only
reason
we're
not
green
is
because
we
have
one
failing
and
blocking,
and
it's
sort
of
it
has
a
story.
B
It
has
a
history
because
it
has
been
reported,
but
I
believe
that
at
first
he
was
just
flaking.
Then
it
was
okay,
and
today
it
starts
failing
again
and,
as
I
said,
it
has
been
reported.
But
since
it
just
literally
started
failing
today
number
eleven,
we
will
have
to
follow
up
to
see
what
it
what
is
going
on
because
he
was
reading
before
other
than
that
six
flaking,
six
passing
and
I'm
the
important
inside
everything
looks
good
good
I
mean
we
have
tracked
off
everything
so
far.
So
that's
like
the
conclusion.
B
A
B
A
A
A
D
Bug
triage,
we
have,
let's
see
open
non-test
issues.
We
are
at
30,
that's
down
from
13
priority
critical
urgent
is
it
for
that
has
remained
since
Oscars
priority
important
soon
issues,
15,
that's
down
from
one
PRS
for
open.
We
are
at
41
that
is
down
from
that
is
to
sue
me
41
down,
13,
I,
already
critical,
urgent.
That's
that
one!
That's
down
from
2
priority
important,
soon,
pr's,
it's
20
to
down
from
6.
Finally,
the
open
KK
issues
that
includes
tests
and
flakes
is
40
that
is
down
4.
We
have
for
urgent
critics.
Accuse
me.
D
I
also
meant
to
say
that
we
are
in
yellow
status
notice.
We
have
four
critical
urgent
issues.
+1
PR-
and
we
haven't
heard
back
about
the
timeline
from
the
author,
and
but
we
know
it's
under
active
development
and
it's
unclear
if
they're
gonna
make
this
milestone,
we
have
done
direct
and
indirect
pings
about
half
of
the
remaining
issues
and
PRS
are
under
active
development
about
one
fourth
of
those
sure
that
they're
going
to
make
the
milestone.
The
rest
that
are
non-responsive
will
be
moved
out
of
this
milestone
tomorrow.
That's
it
from
bug
triage.
A
D
What
we're
doing
is
we're
pinging
them
directly
our
students.
What
we're
doing
is
we're
putting
a
note
in
the
PR
or
the
issue
tagging
the
people
we're
waiting
a
bit
then
we're
slacking
them
DM
and
then
we're
saying:
okay,
we're
giving
them.
You
know
two
weeks
or
one
week
and
now
we're
coming
up
against
the
milestone,
we're
so
we're
saying
like
Tuesday.
If
we
don't
hear
anything,
we'll
try
one
more
round
and
then
we're
just
gonna
move
it
out,
because
it's
unresponsive,
most
people
have
been
responsive,
but
there's
a
few
go
out.
Okay,.
A
I
I'm,
just
and
maybe
maybe
and
maybe
not
up
to
date
on
this
but
I
was
under
the
impression
that,
while
after
code
freeze
enhancements
don't
get
worked
on
unless
they
are
under
an
exception,
buzz
will
definitely
still
get
fixed.
So
that's
why
I'm
wondering
if
we're
the,
why
I'm
wondering
if
removing
all
of
the
117
bugs
out
tomorrow.
F
G
H
Everyone
so
coming
from
the
status
from
dogs,
we
are
LOV,
we
already
crossed
our
deadline,
so
we
are.
We
have
two
enhancements
like
still
in
the
unknown
state.
So
still
we
didn't
hear
from
them.
Yet
so
and
we
are
working
on
our
second
deadline
for
November
15th
on
making
sure
the
dogs
are
ready
for
the
review.
H
A
H
A
All
right,
let's
mute,
do
we
have
any
questions
for
ducks.
A
Yeah
awesome
thanks
vineeth
I'll
round
up
back
with
you
about
those
those
issues
and
the
milestone
removal.
Thank
you.
So
much.
Let's
see
you
next
release
notes
with
Chris.
E
I
No
big
update
for
us
this
weekend
are
today
still
poking
people
every
now
and
then
about
the
known
issues,
but
we
don't
have
to
worry
about
that
for
a
little
while
so
get
as
fancy
about
that
this
week,
so
yeh.
Otherwise,
everything
is
good.
I
met
with
David
from
comms
today
about
the
release
theme,
so
we're
happy
with
how
things
are
there,
but
I'll?
Let
him
speak
more
to
that.
Otherwise,
she
sums
up
awesome.
K
A
I
I
have
I,
have
a
theory
and
I
have
a
suggestion.
The
theory
is
that
CN
CF
is
scrambling
about
Cube
comment:
the
contributor
summit.
The
suggestion
is
that,
let's
see
I,
don't
think
yeah.
The
suggestion
is
that
you
get
in
touch
with
Chris
short,
who
works
for
the
CN
CF
and
is
extremely
helpful,
and
if
you
tell
him
I
sent
you
he
should
be
able
to
poke
the
right
people.
He
has
poked
him
for
me
before.
Okay.
K
A
So
that's
that's
all
I'm
saying,
but
but
he
should
get
back
to
you
at
least
tomorrow.
K
A
Sounds
like
that
sounds
like
that's
an
awesome
strategy.
I
like
it,
because
because
that
way
everyone
will
remember
us
as
a
stability
release
and
then
next
year
they
would
like
yeah
it's.
If
that's
just
what
it
is,
and
then
you
don't
have
to
make
any
decisions
so
good.
This
is
why
you're
doing
coms.
K
A
Yeah-
and
let
me
know
if
I
can
help
with
that
further
I'll,
let
you
know
I'll
get
you
I'll
get
you
in
touch
with
Chris
cool
Stephen
is
not
here.
He
said,
I'm,
not
sure.
If
that
is
true,
because
you
cannot
quote
the
Stephen,
but
he
said
there
was
no
particular
updates
upcoming
cuts.
Our
beta
2
scheduled
on
November
18th,
which
is
next
week,
do
we
have
any
in
there
just
lead
updates.
A
No
update
from
me
awesome
thanks
so
much
my
only
update
is
that
code
freezes
this
week,
so
that
will
remain
the
update
for
the
next
well
for
the
next
one
meeting
on
Wednesday,
and
so
yes,
code
freeze
is
coming
up.
Everyone
is
well
aware
of
that.
I
must
Teamster
all
that
doesn't
really
need
mentioning
I
haven't
heard
from
six
scaleability,
possibly
because
Maria
went
and
talked
to
them,
but
as
far
I
know
we're
in
reasonably
good
shape
there
and
then
anything
else.
A
Life
cycle
active:
what
is
that
I've
never
seen
that
before
that's
crazy
Oh
or
he
did
that?
Okay.
G
A
F
G
A
Thank
you
I'm
living
up
right
here.
That's
on
me,
awesome,
I'm,
so
glad
we're
walking
this
documented.
This
feels
really
good
at
getting
things
done,
documented
criteria
by
which
we
decide
that
a
failure
is
tolerable,
okay,
lots
of
action,
and
we
have
an
updated
PR,
all
right,
very
cool.
Where
is
that
PR.
A
Cool
in
progress
document
reason
for
inclusion
of
really
stalking
jobs.
I'm
just
gonna
hold
these
up
working.
A
So
much
for
you,
honey,
I,
work
on
this.
This
is
this
is
you
are
so
well
positioned
to
do
this
work,
but
also,
thank
you
so
much
this.
This
is
so
helpful.
We
have
this
one
tracking
specially
this
is.
This
is
Bobby
I,
think.
A
A
L
Just
given
update
old
aware
at
the
bottom,
I
guess,
a
big
area
of
work
right
now
is
okay,
getting
a
getting
some
synthetic,
a
cluster
to
run
CI
jobs
on
OpenStack.
So
technically
we
already
have
a.
We
already
have
real
clusters
running
in
twenties
with
GCE
and
an
ADA.
Would
you
pay
an
AWS?
It
seems
and
wide
right
now.
L
The
only
tricky
thing
is
an
operating
the
open,
a
OpenStack
conformance,
so
it
uses
a
I
forget
the
name
of
the
exclusive
like
local,
a
local
queue
up,
which
is
a
which
does
in
the
which
doesn't
technically
create
a
real
cluster.
So
we
could
close
this
issue
because
that's
a
that
could
be
getting
a
getting
up
in
stock
to
do.
Multi
node
test
on
a
real
cluster,
that's
more
of
a
long-term
thing,
or
we
could
just
keep
this
one
for
tracking
a
okay.
A
L
H
A
A
A
E
A
A
A
Really,
what
is
happening?
Oh
it's
already
in
the
backlog.
Hooray,
let's
see,
we
are
working
on
this.
However,
so
do
you
want
it
to
do
or
do
you
want
to
do
it
and
do
I
have
in
progress,
I?
Think.
I
A
Fantastic,
really:
cool;
okay.
We
need
to
okay
patch
on
these
schedule
updates.
That's!
These
are
all
pull
requests
so
I'm,
assuming
that
we
are
going
to
add
these
to
review
in
progress.
A
A
There
we
go
okay,
awesome
and
then
hatch,
release
schedule,
update,
okay,
I'll
need
to
take
a
look
at
that.
Probably
just
looks
like
we've
been
poking
the
schedule
in
awesome.
Those
are
some
of
the
things
that
I
will
follow
up
on.
Presently
you
stop
share.
The
other
things
I
need
to
do
is
get
back
to
David
about
comes
and.
A
Right
great,
so
that
was
the
fastest
void,
walkthrough
ever,
which
is
probably
evidenced
by
the
fact
that
we
have
been
working
really
hard
on
them
or
at
least
made
significant
progress.
So
a
thanks
team.
You
are
all
doing
awesome,
work
and
I
will
unless
there's
any
other
comments,
concerns
questions.
I
will
let
you
all
get
on
with
your
day.