►
From YouTube: Antrea Community Meeting 02/16/2021
Description
Antrea Community Meeting, February 16th 2021
A
So
welcome
everyone
today
is
wednesday
february
the
17th
or
tuesday
february
16th.
If
we
are
in
the
u.s-
and
this
is
the
entry
community
meeting
for
today-
unfortunately,
we
don't
have
any
topic
in
the
agenda,
so
it's
pretty
much.
The
whole
meeting
will
be
open
conversation.
A
All
right:
congratulations
for
the
the
many
new
releases,
especially
for
the
zero
13
release.
Okay,
great
and.
A
The
only
thing
that
I
wanted
to
maybe
ask
you
today
is:
this
is
probably
more
a
question
for
the
office
hours
meeting,
but
I
was
wondering
now
that
we
start
seeing
some
some
adoption
from
korea,
so
there
are
users
trying
trying
it
out
there
do
as
a
part
of
our
documentation.
A
I
was
looking
that
it's
kind
of
quite
good,
but
do
we
have
also
advanced
troubleshooting
documentation?
A
C
C
B
C
B
Just
gonna
say:
yeah,
probably
the
same
as
huge
engine
that
we
do
have
like
the
troubleshooting
document,
which
is
not
very
long,
but
it
does
have
some
valuable
information,
mostly
about
debugging.
The
apis
and
troubleshooting
open
v
switch,
and
I
think
we
have
pointers
to
nctl
and
the
different
commands
you
you
have
in
nctl
to
dump
flows,
for
example,
and
inspect
specific
flows
for
services.
I
mean
gendron's
working
on
services
right
now,
but
for
a
pods
and
and
so
on.
C
Yeah,
I
think
we
I'm
not
sure,
if
asking
some
documentation
like
wrong
book
wrong
book
like
documentary
for
that
one,
probably
we
don't
have,
because
what
we
have.
D
E
E
E
E
The
other
thing
at
the
close
of
the
troubleshooting
markdown
document.
Maybe
it
could
be
improved
by
just
a
suggestion
of
where
to
go
next.
You
know
it
tells
you
how
to
get
logs,
but
really
just
a
pointer
to
the
I.
I
would
think
that
the
place
you
should
recommend
people
go
would
be
the
slack
channel
and
then
maybe
the
community
meeting
or
something
like
that,
but
that
might
be
something
that
would
be
useful
to
put
at
the
end
of
the
troubleshooting.
A
Okay,
so,
following
up
on
on
what
the
on
what
stephen
just
brought
up,
I
noticed
that
the
same
document
is
accessible
both
from
untriado
tio,
documentation
and
from
you
know
the
the
gita
the
github
page,
but
is
it
exactly
the
same
document
or
are
we
maintaining
a
copy?
B
File,
but
it
is,
I
mean
it's
there's
a
single
source
of
truth,
which
is
a
markdown.
A
A
E
I'm
just
curious
that
you
mentioned
that
there
were.
We
do
have
growth
in
the
adoption
and
I'm
wondering
where
they're
coming
from
I've
seen
clues
that
maybe
people
are
looking
at
it
because
of
things
that
entry
it
does
that
other
cni's
don't
like
supporting
for
arm
and
windows.
But
do
we
have
any
other
niches
that
seem
to
be
attracting
users.
A
Unfortunately,
unfortunately,
I
don't
have
this
information,
maybe
anthony
johnson
can
answer.
I'm
just
answering.
You
know
reflecting
on
the
activity
that
we
see
on
github
and
on
slack,
but
maybe
maybe
andran
and
genji
will
never
an
answer
for
your
question.
B
I
mean,
as
as
you
said,
steven
actually
we
I
don't
know
if
you're
aware
of
that,
but
there's
been
some
activity
in
our
slack
channel
some
interactions
with
google
engineers
working
on
gke,
who
are
looking
into
using
gk
entria
in
in
gke
for
windows
support.
So
you
know
that
google
has
a
partnership
for
with
psyllium
for
for
curators
networking
for
linux
nodes
in
in
gke,
but
cdm
relies
on
ebpf
and
just
doesn't
support
windows
and
so
they've
been
investigating
using
entry.
B
B
B
B
I
think
that's,
that's
it
celebratory.
Do
you
think
there
is
any
yes.
A
I
don't
know
at
least
from
my
side.
I
don't
think
that
we
have
anything
else
that
we
need
to
cover.
I
will
probably
give
everyone
on
the
call
another
minute
to
see
if
they
have
any
other
topic
that
would
like
to
propose
otherwise,
for
today
this
could
be
an
extraordinarily
short
meeting.
E
E
B
Surprisingly,
the
miner
really
0.13
was
the
easiest
one
and
the
bug
fix
three.
These
were
the
most
painful
ones,
so
I
plan
to
work
on
the
process
to
cherry
pick,
bug
fixes
and
kind
of
like
try
to
automate
to
automate
bug
fix
releases
more,
but
it's
it's
easier
to
to
make
them
and
make
them
as
often
as
as.
D
D
I
have
a
quick
question
to
antonin,
I'm
not
sure
if
we
should
discuss
it
here,
though
I
just
want
to.
I
was
wondering
about
any
update
on
that.
Previously
we
heard
about
the
change
in
the
licensing
terms
from
from
kibana
site.
D
If
there
are
any
updates
regarding
how
whether,
when
to
make
any
changes
from
entry
outside.
B
Yeah,
that's
a
that's
a
good
point.
I
haven't
looked
into
it
since
there
was
a
blog
post
from
elastic
about
the
change
in
license.
I
know
there.
B
Some
communication
internally
at
vmware
about
some
recommendations
on
how
to
proceed,
and
actually
maybe
that's
something
that
stephen
has
some
context
on.
I
don't
know,
but
I
mean
my
position
is
still
that
I
don't
think
we
need
to
change
anything
because
of
how
we
use
elastic
and
the
fact
that
we
don't
distribute
it,
whether
it's
a
source,
distribution
or
a
binary
distribution.
E
Yeah
I
haven't
heard
any
update
coming
out
of
vmware
illegal
and,
of
course,
the
all
the
prospective
users
might
have
their
own
legal
departments.
That
would
need
to
evaluate
it.
It
and
I
also
didn't
go
attempt
to
read
the
actual
licensing.
You
know
there's
some
of
them,
like
the
other
one.
We
went
away
from
actually
had
a
really
aggressive
license
that
even
prohibited
giving
demos.
I
believe
I
don't
know
that
the
elastic
one
goes
that
far,
but
some
of
them
do.
D
E
D
B
D
A
A
Okay:
okay,
I
believe
that
we
don't
have
any
other
topic
for
today.
So
I
would
like
to
thank
everyone
for
attending
thanks
again,
congratulations
again
to
the
team
for
let
0.013
release
and
we
look
forward
to
see
soon
the
014
release
or
whatever,
which.
A
Yeah
I
said
014
or
whatever
it
might
be
called
and
yes,
we'll
then
need
to
have
a
big
virtual
party
once
the
one
that
release
comes
comes
out-
and
I
guess
that's
all
for
today.
So
thanks
everyone
for
attending
and
talk
to
you
in
two
weeks
time
where
we
will
go
back
to
the
usual
mondays
last
tuesday
timing.
So
thanks
again
and
have
a
good
one.