►
From YouTube: Antrea Community Meeting 03/11/2020
Description
Antrea Community Meeting, March 11th 2020
The hosts forgot to hit the recording button at the beginning of the meeting, so only a short part of it was recorded.
A
C
C
B
The
benefit
of
everyone
that
will
listen
to
the
brief
recording
of
this
meeting,
and
so
finally,
they
want
everyone
hour-long
recording
to
go
through
so
I
just
wanted
to
quickly
summarize
what
we
said
about
zero-five-zero
release
that
all
the
issues
that
are
currently
open
on
and
and
targeted
zero-five-zero
are
still
on
target.
The
most
pressing
issue
is
aware
that
we
need
more
code
reviews
on
the
prometheus
patches
and
on
this
aim
we
have
several
action
to
the
same.
We
have
several
action
items.
B
One
is
for
Kobe
to
squash
the
various
updates
that
email
on
his
PR.
That's
because
you
know
that
we
have
probably
a
few
tens
of
commits
there
and
having
a
single
commit
will
make
it
easier
to
review
some
in
anon.
In
total,
we
have
three
peers
to
review
for
the
Prometheus
work
320
to
325
and
446,
which
is
the
which
is
the
patch
that
you
are
the
four
unit
tests.
The
other
thing
that
is
worth
mentioning
is
that
issue
361
regarding
updating
the
beta
kubernetes.
Are
you
ready?
B
Node
selector
should
be
fix
it
by
4,
DS,
0,
5
0
release,
because
it
is
important
when
it
fixes
the
4
kubernetes
1.18
and
it's
scheduled
to
be
released
one
day
before
on
3
@
0,
5
0.
And
finally,
we
discussed
the
issue
the
last
issue
that
is
targeted
year
from
494
about
the
namespace
deletion.
This
issue
has
been
root
caused
by
Chan
and
you
we
need
to
assess
a
little
bit
our
weather.
B
Our
process
for
managing
API
versioning
is
compliant
with
kubernetes
api
versioning
strategy
in
order
to
avoid
in
the
futures
issues
like
this
like
this
at
the
moment,
this
is
not
an
extremely
big
deal,
because
we
are
not
yet
1.0.
We
are
still
in
the
early
stages,
but
as
we
get
more
and
more
adopters,
it
become
import
becomes
important
to
give
them
a
good
experience
upon
upgrade.
Ok,
so
I
I
summarized
pretty
much
everything
that
I
wrote
down
in
the
notes
for
the
zero-five-zero
release.
B
Alright,
I
think
that
of
viewers
of
our
meetings
will
probably
appreciate
a
shorter
recording.
Ok,
so
thanks
Cody
for
your
update
on
the
website,
and
it
seems
that
we
have
exhausted
the
items
in
our
agenda
for
today
for
today's
meeting.
So
is
there
anything
else
that
anyone
from
the
community
would
like
to
bring
up
for
discussion.
C
B
Fairly
open
to
change
the
changes
our
meeting
time,
what
whoo
my
curiosity's
these
are
we
conflicting
just
because
maybe
the
Calico
meeting
time
is
using
an
Amir
is
Amir
based
and
therefore
the
conflict
will
be
just
for
these
two
weeks
and
then
and
then
you
know
one
see
me
as
which
circulates
daylight
savings.
The
conflict
will
be
over
or
is
it
permanent?
Do
you
know
that
I.
B
Thinking
is
indeed
that
normally
this
was
happening
like
at
8:00
a.m.
Pacific
time
and
it
slipped
through
to
9:00
a.m.
just
because
maybe
you
know
the
bait,
the
time
zone
for
the
meeting
is
GMT
and
the
u.s.
switched
to
daylight
savings
over
the
weekend,
whereas
the
time
zone
for
this
meeting
for
our
meeting
is
instead
PST.
So
you
know
it
would
be
always
9:00
a.m.
for
9:00
a.m.
Pacific,
regardless
of
opening
of
GMT.
B
So
you
know
if
the
conflict
is
just
until
the
end
of
the
and
for
the
next
weeks
until
Europe
and
the
rest
of
the
world
with
which
to
daylight
saving
I
mean
the
rest
of
the
world
that
uses
they're,
not
saving,
then
I,
don't
know
if
it
makes
sense
to
reschedule
our
meeting.
I
mean
I
think
that's
something
that
we
can
easily
verify
on
the
Internet.
B
B
A
B
So
it
might
make
sense
for
us
to
consider
rescheduling.
We
can
choose
a
different
day
of
the
week
if
you
prefer
and
still
keep
it
at
9:00
a.m.
PST,
maybe
on
a
Tuesday
or
on
a
Tuesday.
We
need
to
verify
conflicts
with
other
community
meetings
in
the
kubernetes
in
the
kubernetes
space,
but
I
have
the
feeling
that
perhaps
using
a
different
day
may
be
easier
than
moving
in
the
meeting
one
hour
earlier
one
hour
later.
A
B
Okay,
with
that
I
mean
to
me,
6:00
p.m.
or
7:00
p.m.
and
doesn't
make
a
huge
difference,
food.
It
will
be
impossible
for
the
people
in
China
as
well,
so
it
doesn't
make
a
difference
for
them
as
well.
So
unless
there
is
another
conflict,
we
just
need
to
verify
whether
there
are
other
conflicts
with
the
upstream
community
meetings.
B
B
A
C
B
B
Anyway,
so
I
don't
think
there
is
a
any
other
thing
to
discuss
for
today
and
I'm
sure
I'm,
surely
sure
I'm
sure
that
you
don't
want
to
hear
about
football.
So
I
guess
that
we
will
tentatively
look
at
rescheduling
in
the
meeting
at
Wednesday
10:00
a.m.
we
will
need
to
look.
We
will
verify
the
kubernetes
community
calendar
to
verify
that
there
are
not
in
other
conflicts
and
if
there
are
no
conflicts,
we'll
move
the
meeting
does
that
work,
for
you
sounds
good
to
me
perfect,
all
right.