►
From YouTube: Antrea Community Meeting 08/02/2021
Description
Antrea Community Meeting, August 2nd 2021
A
B
B
B
You
can
see
this
crd
in
the
screen
and
user
can
define
the
multicast
group
addresses
which
are
expected
to
be
supporting
a
cluster
and
they
use
a
part
selector
to
set
target
pods
which
are
expected
to
access
the
multicast
address
and
multicast
group
defining
the
cid
could
be
ipv4
ipv6
and
if
it's
ipv6
address,
the
video
gates
for
joe's
stack
should
be
named
for
the
cluster,
but
we
are
not
planning
to
support
ipv4
in
the
first
version.
Maybe
we'll
talk
this
later
and
here
I
want
to
explain.
B
B
So
for
the
entry
controller
part,
it's
really
simple:
let's
watch
the
multicast
crd
in
the
computer.
Switch
parts
are
involving
each
multi-pass
group
entry,
controller
leverage,
pass
letter
to
step
parts
and
write
a
part
information
back
to
cit
and
organize
the
result
by
nodes.
So
the
green
part
I
highlight
are
the
information
that
is
written
by
energy
controller.
B
B
B
B
The
matching
this
table
is
multicast
group
config.
In
crd.
The
flow
action
in
this
table
is
a
group
bucket
in
the
group.
A
bucket
in
the
group
includes
three
parts
and
you
can
see
the
last
line
and
the
first
is
up
to
package
to
end
and
three
gateway:
zero
and
the
support
for
forwarding
packets
to
make
some
external
and,
secondly,
you
can
see
at
a
transaction
normal
and
that
is
to
leverage
only
asthmatical
smoking,
snow
pin
capability
and
for
the
pocket
inside
ovs.
B
B
B
B
B
And
for
the
no
in
camp
mode
entry
engine
as
multicast
routing
entries
on
the
host
to
forward
the
traffic
between
entry
gateway,
0
and
the
transport
interface,
which
is
used
for
routing
traffic
across
nodes,
the
multicast
routing
entry
is
configured
once
when
entry
engine
find
a
different
node
joins
to
the
multicast
group.
The
first
time.
B
B
B
Because
ijmp
proxy
only
supports
igp
v1,
which
one
downstream
interfaces
and
the
rgmp
proxy
adds
multicast.
Not
only
if
igmp
membership
report
is
downstream
interfaces
and
ignore
the
upstream
interfaces,
so
this
might
cause
local
multicast
traffic,
my
able
to
center
external,
which
we
don't
want
to
also
with
we-
are
not
using
dynamic,
multicast
water
demon,
I'm
rotating
on
pimd,
and
we
want
to
try
to
config
static,
multicast
routing
table
using
c
go,
and
for
do
we
support
multicast
four
to
external
cancer.
B
B
B
C
C
C
We
have
enforce
the
multicast
traffic
to
go
through
the
network
policy
related
tables,
but
I
don't
think
we
have
enough
policy
rules
focusing
on
mud
catch
traffic,
so
I
just
mean
for
the
first
release:
mudcast
might
not
be
limited
by
network
policy,
but
if
or
not
so
we
want
to
support
network
policy
and
multicast
traffic.
I
think
it
is
an
open
issue
and
the
conclusion
might
have
some
impact
on
the
table
designed
for
multicast
and
the
third
is
for
the
3d
design.
C
C
C
Maybe
the
second
world
second
release
format
cast,
but
but
absolutely
not
in
the
first
release,
and
these
are
the
limitations
the
way
we
know
we
already
know
about
the
design,
and
then
I
want
to
have
some
discussions
about
about
all
the
issues.
Firstly,
is
about
crd
way.
We
want
to
know
if
namespace
selector
is
required
to
use
to
to
be
used
to
select
the
poles
in
the
zld.
C
A
Hey
waiting,
I
had
a
question
kind
of
regarding
pot
selection.
Have
we
considered
using
like
a
pod
annotation
instead
to
have
a
pod,
join
a
multicast
group?
I'm
asking
because
let's
say
I'm
someone
scheduling
pods
in
a
cluster.
Maybe
I
maybe
I
know
that
my
pods
need
to
join
a
specific
multicast
group
and
it's
easy
for
me
to
add
an
annotation
to
the
pod
to
let
them
join
the
multicast
group.
But
if
I
have
to
go,
find
the
crd
and
modify
it.
That
means
I
need
to
have
like
permissions
to
edit
the
crd.
C
C
C
D
D
E
E
C
E
C
E
A
Or
in
that
case,
annotation
makes
more
sense
right,
because
it's
not
as
big
of
a
change
in
a
way.
You
don't
need
to
change
the
crd
and
conceptually
it's
kind
of
like
more
similar
right,
because
it's
the
point
but
joining
the
group
either
through
an
annotation
or
by
sending
a
an
igmp
packet
that
you
can
capture
at
the
at
the
switch.
C
C
A
C
E
Yeah,
how
about
you
think
a
little
more
about
it?
I
mean
why
the
it's
it's
it's!
It's
significant
piece
of
theory
work
to
do
allotation
or
crd.
First,
if
it's
really,
I
mean
lots
of
user
will
work.
I
have
to
say,
let's
consider
how
to
discovery
from
the
beginning,
but
I
would
like
to
you
you
wanna
another
one
that
I
put
anything.
We
should
differentiate
the
debugging
information
and
the
the
the
involving
information
required
by
functionality.
E
C
C
C
D
E
C
E
E
D
E
E
A
E
E
C
A
C
E
I
don't
know
I
mean
if
you
ask
me,
of
course,
you
you
shouldn't,
make
a
decision
since
you
are
into
business.
But
if
you
ask
me,
I
have
to
do
the
income
first,
since
it's
because
it's
simplest
and
don't
require
many
chains
in
forwarding
pipeline,
and
it's
also
the
only
required
use
case
winner
and
then
we
can
do
in
calculator
he
first
met.
Then
I
probably
were
thinking
about
how
to
discovery.
C
E
C
E
E
E
C
E
C
E
C
Oh
disgusting
and
I
think
I
don't
have
other
alternatives
to
discuss.
I
want
to
to
share
another
point
about
the
madquest
resulting
entry
configuration.
I
remember
that
in
the
original
stride
genji
has
asked
us
if
we
could
support
the
any
thoughts
in
the
multicast.country
in
that
email.
I
have.
I
have
written
backsides
for
the
zero
address
is
positive
by
smc
route,
but
when
looking
to
the
linux
relating
multicast
routing
implementations,
I
found
that
we
can't
use
the
zero
address
to
use
that
anything.
C
C
C
I
don't
think
the
linux
one
last
turn
around
to
drop
it.
It
is
because
we
don't
have
any
added
any
unknown
external
address,
but
they
don't
know
the
external
addresses
from
the
configurations.
So
we
have
to
let
the
link
kernel
to
use
up
call
messages
for
using
upload
messages
to
us.
Two
letters
and
extra
add
additional
login
entries.
C
I
think
other
tools
is
using
the
practical
learning
and
they're
sure
to
show
learning
dramatic
identity
message,
team
message
of
some
other
massacre,
related
protocol
messages
and
learn
the
source
and
the
destination,
and
then
the
dotting
entry.
I
think
the
final
action
is
is
the
same.
The
difference
is
a
very
get
on
the
how
they
get
the
message.