►
From YouTube: Kubernetes 1.19 Release Team Meeting 20200615
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
B
Yeah,
hello,
everyone,
I'm,
Laura,
enhancements,
Shadow
and
I'm
standing
in
today
for
Nabarro
cookin,
the
joint,
so
our
our
overall
status
is
green.
When
it
comes
to
the
metrics,
nothing
has
changed
since
the
last
call.
We
have
total
of
44
enhancements
being
tracked
and
13
of
which
are
in
alpha
stage.
18
ou
are
in
beta
and
13
are
in
stable,
and
one
additional
thing
to
point
out
is
that
we've
received
for
exception,
requests
so
far
and
all
of
them
were
accepted
and
that's
that's
it
from.
Thank
you
awesome.
A
C
But
we
have
some
folks
looking
into
that,
so
not
too
worried
about
that
on
master
informing
on
the
main
thing.
That's
been
persisting
for
a
little
while
now
has
been
the
OpenStack
conformance.
Job
is
consistently
failing,
but
we're
able
to
get
into
into
contact
with
some
folks
on
that
team
and
they're
basically
just
need
to
change
their
configuration
to
be
able
to
run
their
tests
on
a
kubernetes
cluster
with
more
than
one
nodes.
So
we
can
do
the
scheduling
tests,
so
they
are
looking
into
that.
C
D
Everyone,
my
name,
is
John
skarbek,
I'm,
a
bug,
triage
shadow
for
this.
Our
release
chosen
the
color
yellow
for
the
most
part,
we're
doing
ok
with
the
external
time
line.
Then
we
still
have
plenty
of
time
to
comment
on
various
issues
that
are
still
creeping
in,
but
I
think
compared
to
118
we're
more
than
quadruple
the
number
of
open
issues
and
mr
or
pull
requests.
E
Hey
everyone,
a
curious
traveler
here,
dock
shadow.
We
are
currently
yellow
and
we're
reaching
out
and
telling
everyone
about
the
new
deadlines
and
following
up
with
that
and
that's
about
it,
happy
Monday.
A
F
F
A
G
H
Yeah,
hey
everyone.
Well,
we
are
still
green,
we're
still
aligning
also
on
the
future
blocks,
having
a
look
who
is
interested
in
writing
one
or
contribute
one
to
to
the
release
cycle
afterwards,
and
we
are
also
in
the
contact
with
CC
and
CF
to
outline
some
content
for
faeries
block,
where
we
threaten
should
next
week,
centered
first
draft,
but
do
it
was
a
stretched
time
which
we
have
for
this
recital
I
think
we
can
also
give
ourselves
a
little
bit
more
time
before
we
can
proceed
in
depth
with
the
CN
CF
folks.
C
I
J
Hey
I
was
just
literally
pressing,
send
on
rescheduling
the
all
shadows
meetings
from
two
weeks
ago,
so
they'll
be
on
for
this
week,
and
the
invites
for
that
should
have
gone
out
so
check
your
mail
for
messages
from
the
the
shadows,
Google
Group,
for
all
the
shadows
out
there
and
then
the
I
guess
the
the
continual
reminder.
If
shadows,
you
have
any
global
questions
for
the
overall
process
or
how
things
are
working
or
things
relative.
Your
particular
role
feel
free
to
reach
out
to
me
on
slack
or
email
or.
J
However,
you
are
able
to
get
in
touch
with
folks
that
you
prefer,
but
generally
around
and
that's
kind
of
what
I'm
here
for
answering
questions
and
helping
make
sure
that
things
are
going
smooth.
So
that's
pretty
much
if
right
now.
A
A
Really
sleet
update
a
little
note
from
Taylor.
This
is
regarding
shifting
the
dates.
I'll
drop,
the
link
in
chat
as
well.
If
you
could,
please
take
a
look
at
that
PR
and
just
give
a
look
over
the
dates
and
make
sure
everything
looks
good
to
you.
I
think
at
this
point
we're
sitting
pretty
good,
but
you
know
we'll
see
how
things
pan
out
six
scalability
updates.
A
A
K
K
K
So,
for
example,
there
were
a
lot
of
comments
on
be
kept
and
the
tooling
that
Jeremy's
working
on
so
I've
already
begun,
taking
some
notes
that
Bob
and
Jeremy
had
collected
and
adding
some
of
your
notes
from
the
the
prioritization
sessions
for
that
document
to
basically
start
shaping
up
a
roadmap
for
it,
and
then
we
could
use
similar
efforts
with
any
of
the
iodine
zone.
This
year,
a
signal
topic.
We
have
a
bunch
of
documentation
items
that
we
talked
about
over
the
sessions.
K
A
Then
there
have
been
a
lot
of
enhancements
issues
like
also
around
you
know
some
of
it
regarding
Jaime's
tooling,
but
some
of
that
might
happen
over
in
an
upcoming
enhancements
meeting,
and
we
can
send
that
you
know
when
that
meeting
is
scheduled.
We
can
send
it
the
list
to
you
if
people
want
to
hop
in
on
that
one.
A
K
Really
really
fun
I
mean
all
the
sessions
were
different.
Some
went
really
quickly.
Some
were
longer
like
more
more
comments,
more
back
and
forth
discussion,
but
every
one
of
them
was
very
enjoyable
and
I.
Just
really
appreciate
how
everybody
just
came
prepared
and
we're
eager
to
help
an
eager
to
contribute.
K
G
Sorry
I'm
the
person
who
comes
in
at
the
end
now
with
my
question
for
the
dates
PR
that
we're
waiting
for
it
to
be
merged
is
an
announcement.
Then
gonna
go
out
to
everybody
and
then
how
do
you
want
the
enhancements
team
to
deal
with
that
like?
Should
we
sort
of
ping
the
enhancements
that
are
open
and
working
to
code
stuffer,
or
do
we
just
say
anything
so
big?
It's
been
quicker,
I,
don't
know,
and.