►
From YouTube: Kuma Community Call - January 20, 2021
Description
Kuma hosts official monthly community calls where users and contributors can discuss about any topic and demonstrate use-cases. Interested? You can register for the next Community Call: https://bit.ly/3A46EdD
B
A
We
don't
have
much
today.
I
have
just
added
this
upcoming
106
release,
which
we
were
planning
actually
for
today.
It
should
have
been
happening
at
this
very
moment,
but
we
saw
a
couple
of
last
minutes
pr's
coming,
so
we'll
probably
try
to
do
it
tomorrow,
this
time
or
maybe
sometime
early
on
friday,
we'll
see
how
things
are
going,
but.
A
A
Other
than
that,
because
I
was,
I
was
actually
going
to
the
to
the
pr's
that
were
merged
since
105,
and
I
noticed
a
lot
of
community
prs
like
community
members
prs,
which
was,
which
is
which
is
great.
Actually
I
mean
I
I
I
was.
I
don't
think
that
we
had
that
that
kind
of
the
diverse
set
of
contributors
in
any
of
our
previous
releases.
This
probably
is
the
first
one
that
you
have.
A
A
A
And
thanks
thanks
to
being
proactive
on
the
on
the
contributing
side,
because
I
you
know,
as
with
a
lot
of
the
open
source
projects,
people
are
kind
of
mostly
coming
with
the
demands
pointing
fingers
at
other
products
and
projects
and
saying,
but
you
can
do
this
with
this
other
with
this
other
project.
So
thanks
for
kind
of
approaching
us
directly
with
with
pr
that's,
that's
actually
rare,
but
but
it's
a
great
great
show
of
of
support
for
the
project.
Thanks.
A
Okay:
okay,
that's
that's
good!
Let
us
let
us
know
on
the
on
the
chart
or
even
here
now
in
the
next
course.
If
there
are,
if
there
are
any
any
any
gaps
for
you
for
that
option,
for
the
integration
with
your
rest
of
the
system,
we
are
pretty
much
open.
I
don't
know
if
you,
if
you
have
seen
marco,
he
has
been
sharing
marco.
A
B
A
B
A
E
A
A
C
Yeah,
so
fips140-2
is
a
an
ist
standard
around
encryption.
Typically,
this
is
a
requirement
around
govcloud
distributions
or
cloud
installations
of
software,
so
relativity
operates
in
both
commercial
cloud
setting
and
also
in
govcloud,
and
we
have
a
basically
one
of
our
sponsoring.
Agencies
does
have
a
requirement
for
us
to
leverage
encryption
modules
that
are
fips,
140-2
approved
so
envoy,
proxy
itself
does
impl
does
have
support
for
fips
140-2.
C
C
C
Okay
yeah,
so
the
the
the
standard
envoy
distribution
uses,
boring
ssl
and
it
does
have
a
fips
approved
version.
So
I
have
done
the
research
on
that
and
what
I'm
curious
about
is
if,
in
the
future,
kuma
could
support
building
envoy
with
that
enabled
and
then
support
the
ability
to
select
the
cipher
suites
for
the
mesh.
C
Basically
that's
so
if,
if
we're
able
to
meet
those
requirements,
you
also
have
to
worry
around.
You
have
to
deal
with
your
how
your
certificates
are
actually
generated,
but
that's
something
that
we
could
as
a
consumer
on
our
own,
generate
our
own
ca
certificates
using
our
own
fips
fips,
approved
modules,
so
that
it's
not
something
that
envoy
would
necessarily
have
to
support.
Well,
sorry,
kuma
would
have
to
support
the
generation
part.
C
So
if
it's,
what
we
would
like
to
see
is
if
it
would
be
possible
to
have
that
option
for
the
kuma
distribution
to
support
the
fips,
approved,
fips,
enabled
version
of
envoy
and
then
be
able
to
select
the
different
tls
ciphers.
That
are
that
we
would
need
for
that,
are
fips
approved,
and
then
we
could
then
basically
have
a
fips
approved
kuma
distribution.
A
That
sounds
like
something
that
we
would
want
to
have.
I
mean
I
deliberately
opened
this
one
because
apparently
one
of
the
persons
that
were
part
of
this
project-
and
actually
I
was
in
my
previous
adventures-
I
have
been
part
of
some
similar
discussions
in
the
envoy,
so
I
mean
it's
like
it's.
It's
not
a
new
thing
to
us
and
this
person
is
also
part
of
our
team
in
a
way
now.
A
So
we
we,
we
are
can't
say
close
to
this
thing
about
open
ssl.
I
was
not
aware
about
boeing
ssl
versions.
I
knew
that
there
was
some
efforts,
at
least
like
maybe
a
year
and
a
half
ago,
to
actually
start
to
fight
against
fibs,
but
I'm
not
sure.
So
if
you
have
any
any
links,
any
any
pointers
where
we
can
find
this.
C
Yeah,
so
that's
the
documentation
from
envoy,
and
I
look
to
see
so
it's
the
latest
version
of
envoy,
which
I
know
you
guys
are
moving
towards
and
specifically
so.
This
goes
over
that
if
you
look
there's
a
link
further
that
if
you
want
to
read
about
like
what
it
takes
to
be
fips,
approved
the
security
policy
for
boring
crypto,
that's
the
actual
nist
document.
That
tells
it
like
that.
That's
how
it's
supported,
but
you
can
see
that
it's
it's
a
it's
a
command
line
flag
when
you're
building.
A
C
Yeah
a
big
thing
with
this
like
so
like
we,
we
currently
are
using
istio
and
I'm
more
more
than
like.
We
well
pretty
much
guaranteed
we're
moving
to
kuma
relativity.
Just
because
of
all
the
features
you
guys
already
have
in
the
simplicity
of
kuma
and
the
fips
requirements
have
been,
for
example,
with
istio.
There
was
a
request
in
february
of
2019,
and
there
it
seems
like
the
istio
community
is
not
moving
forward
with
that
at
all.
A
A
A
That
that
there
will
be
something
around
this
for
sure
in
the
in
the
releases
to
come,
I
don't
have
any
any
timeline
yet,
but
oh
yeah
definitely
totally
understand
considering
I
mean
like
even
before
this
this
discussion
here
we
were
like
looking
into
this
envoy
story
and
what
we
can
do
about
it,
but
now
that
you
bring
this
up
this
additional,
you
know
somehow
incentive
into
trying
to
figure
out,
because
you
know
android
builds
are
not
really
the
trivialist
thing.
Yeah.
C
So
I
looked
at
that
as
well,
because
I
figured
you
know,
that's
that's
more
added
complexity
for
you
guys
to
have
to
to
own
your
own
build
of
envoy.
So
I
did
look
into
that
as
well,
and
there's
an
issue
open
into
with
the
envoy
community
to
provide
a
docker
image
with
envoy
pre-built.
With
that
the
issue
I
went
ahead
and
added
it
as
well,
so
it's
this
is
what
I
found
so
far
around
that
so,
like
the
standard
get
envoy
website
to
get
it.
C
A
A
Trying
to
focus
our
efforts
on
things
that
would
be
more
meaningful
to
the
community
yeah
and,
to
be
frank
at
least,
I
was
not
aware
of
anyone
bringing
the
specific
envoy.
You
know
built
topics,
at
least
I
was
not
aware.
I
don't
know
if,
if
anyone
here
on
the
call
was
aware
of
anything
any
discussions
about
this.
E
E
Okay,
I
think
I
think
that
there
is
two
answers
to
this.
There
is
a
short
term
thing
we
can
do
or
you
can
do,
and
there
is
a
long-term
fix,
obviously
long
term.
You
know
we
bundle
envoy
with
with
kuma.
Therefore
we
could
be
bundling
it
in
such
a
way
that
this
is
already
enabled,
but
the
qmdp
process
when
it
starts
envoy.
E
It
just
looks
for
envoy
in
the
path
you
know
in
or
in
the
same
folder
as
where
the
comma
dp
binary
is
so
the
short
term
fix
is
you
can
go
ahead
and
recompile
envoy.
However,
you
like
and
add
it
to
the
path
before
you
start
qmdp,
it's
simple
as
that,
so
you
could
have
a
short-term
fix
that
would
allow
you
to
enable
this
feature
without
us
having
to
recompile
or
rebuild
envoy.
You
know
the
one
that
we
bundle.
C
E
C
E
C
E
E
Yes,
so
at
that
point
we
would
probably
want
to
understand
how
we
can
build.
You
know
we
would
probably
want
to
integrate
that
work
with
our
build
process
in
such
a
way
that
yeah
so
yeah
that
that
could
be
an
option.
So
we
can
learn
from
anything
that
you're
doing
around
this,
so
that
it
can
be
incorporated
into
our
own
build
process.
C
Yeah
gotcha
mean
we're
we're
we.
We
luckily
have
a
longer
timeline,
for
we
have
several
months
to
to
work
this
out.
So
would
this
be
better
just
to
like?
Do
you
guys?
Would
you
like
me
to
create
a
a
github
issue,
just
a
feature
request
for
you
to
track
it,
and
then
we
can.
You
can
determine
where
it
fits
in
your
priority
and
then
potentially
we
might
be
able
to
contribute
to
this
takuma.
C
Okay,
so
yeah
I'll
open
a
feature,
request
issue.
I'll
also
add
it
to
the
the
google
doc
you
guys
had
in
the
last
meeting
and
just
added
in
there
for
tracking
purposes,
and
then
you
know
we
can
continue
to
check
in
and
see.
You
know
if
it's
something
that,
depending
on
the
priorities,
you
know
for
what
you're
working
on.
If
we
can
contribute
this
and
do
that
it'd
be
great.
If
not,
you
know
we
can
maybe
work
together
on
it.
E
This
year
we
would
like
to
move
kuma
to
the
incubating
stage
of
cncf
and
as
part
of
that
process,
since
cf
you
know
wants
to
wants
to
know.
You
know
a
few
kind
of
you
know
commute
community
case
studies
on
on
how
people
are
using
it,
and
you
know
you
know
why
they're
using
cuba
and
in
what
capacity
and
so
on
and
so
forth,
would
you
be
interested
in
participating
in
the
due
diligence
that
cncf
does
in
order
to
help
kuma
move
to
incubating.