►
From YouTube: End User Lounge: Salt Security
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
Awesome
welcome
to
the
cncf
end
user
lounge,
where
we
explore
how
technologies
cloud
native
technologies
are
adopted
by
end
user
organizations
across
different
industries
and
sectors.
The
cncf
end
user
community
is
formed
of
more
than
160
vendor
neutral
companies
that
are
used
to
open.
They
use
open
source
software
to
deliver
their
products.
I'm
abu
bakr,
dick
angel,
a
cncf
ambassador
and
today
with
me,
is
the
team
from
social
security
who
will
be
talking
with
us
about
their
journey
in
the
cloud
native
ecosystem.
A
In
these
live
streams,
we
bring
end
user
members
to
showcase
how
their
organizations
navigate
the
cloud-native
ecosystem
to
build
and
distribute
their
services
and
products
join
us
every
fourth
thursday
at
9
00
a.m.
Pacific
time
this
is
an
official
live
stream
of
the
cncf
and
our
search
is
subject
to
the
cncf
code
of
conduct.
Please
do
not
add
anything
to
the
chart
or
questions
that
will
be
in
violation
of
the
code
of
conduct
basically
be
respectful
to
everyone,
and
especially
fellow
participants,
and
also
the
presenters
when
sharing
your
opinions.
A
If
you
have
any
questions,
you
can
add
them
to
the
chats
of
this
video
and
make
sure
to
ask
any
question,
maybe
related
to
the
topic
or
any
other
thing
that
you
want
to
learn
from
the
folks
from
social
security.
Now
before
we
dive
into
the
questions,
eli,
omri
and
val
could
be
briefly
introduce
yourselves.
B
Sure
hi
hi
everyone,
my
name,
is
ellie.
I'm
a
platform
team
lead
in
solid
security
here
with
me
on
wii
guide
I'll.
Let
them
introduce
themselves
now
and.
D
A
Oh
nice
seems
we
have
all
the
people
powering
all
the
machines
background
here.
So
I
know
assault
is
all
about
security.
So,
but
can
you
share
with
us
more
about
your
company
and
what
you
do
and
how
you
did
awesome
what
you
do.
B
Yes,
so
salt
salt's
about
five
years
old,
we
started
off
with
kubernetes
on
the
get-go.
Now
we
have
around
40
micro
services
today
in
production
with
multiple
clusters.
I
think
I'll
be
able
to
elaborate
on
that
a
little
more
we're
very
like
we
use
a
lot
of
tools
and
and
products
from
from
around
the
cncf
landscape.
We
love
the
cncf
and
the
community.
B
It's
been
helping
us
a
lot
lately
and
recently.
In
the
past
two
years,
we've
dived
into
the
whole
service
mesh
journey
we've
written
a
we've
written
a
blog
post,
a
great
blog
post
that
was
recently
published
on
the
cncf
blog
around.
You
know
our
journey
with
grpc
and
you
know,
and
service
match
and
low
bouncing
around
kubernetes
and
a
lot
of
fun
stuff
like
that,
we'll
be
happy
to
share
with
everyone
but
yeah.
It's
been
really
great.
A
Awesome.
Okay,
so
can
you
like
walk
us
through
what
your
infrastructure
setup
is
like
and
what
are
the
that
there
are
some
visuals
and
the
gears
that
run
everything
in
the
background.
D
You
want
to
take
that,
so
we
are
multi-cloud.
We
use
several
cloud
providers.
Mostly
most
of
our
services
are
in
aws.
We
use
kubernetes
for
all
of
our
microservices.
D
A
D
Well,
basically,
from
the
early
days
in
social
security,
we've
started
to
use
kubernetes,
I
mean
the
simplicity,
the
flexibility
it
allows
us
to
manage
and
make
sure
our
service
is
highly
available
and
we
can
maintain
it
and
make
sure
to
revert
if
needed,
definitely
to
guarantee
our
customers.
The
best
service
possible.
A
Thank
you
awesome
yeah,
and
you
mentioned
the
other
time
about
blockbusters.
I
went
through
it
and
in
it
you
described
how
you
used
jr's
pcx
extensively,
and
can
you
shed
more
light
about
your
usage
of
jr
pc
and
any
other
tools
in
your
arsenal
that
you
use
outside
cloud
native
tools
that
you
use
aside
from
grpc.
B
Yeah
john
and
we
handles
that
another.
Well,
maybe
you
can
tell
us
more
about
why
we
chose
grpc.
C
Sure
so
we
were
using
to
now
as
as
familiar
with
all
with
all
my
microservice
architecture.
Then
systems
services
need
to
speak
to
each
other
right,
so
you
have
many
many
ways
to
do
so
and
lately
we
were
using
direct
communication
between
the
services.
Sometimes,
and
sometimes
we
were
using
more
of
I
think
kind
of
communication
on
top
of
message
skills.
So
we
used
kafka.
We
tried
to
evaluate
a
few
other
stuff,
but
in
terms
of
synchronous
communication
we
were
using
we're
using
the
akka
framework.
C
In
order
to
speak
between
services.
We
had
we
had
some
issues
with
backwards
compatibility.
So
while
we
were
changing
apis
between
the
services,
sometimes
we
had.
We
had
to
cope
with
with
api
changes,
breaking
api
changes,
and
then
we
started
the
process
of
finding
alternatives.
C
So
one
of
the
the
first
things
we
we
knew,
existed
and
and
always
wanted
to
kind
of
evaluate,
was
was
grpc.
C
C
And
then,
since
jpc
is,
is
working
on
http
2
we've
had
a
problem
there
because,
as
as
load
balancing
is,
is
very.
C
Like
familiar
to
kubernetes
kubernetes,
does
it
for
you
using
the
service
resource,
for
example,
in
http
2,
the
store
is
a
little
different.
The
connections
are
sticky
and
what?
What
made
us
realize
that,
if
we,
if
we
will
not
find
a
solution
to
this
load,
balancing
problem,
we
might
have
some
some
scaling
issues
and
then
we
started
researching
around
this
one
and
I
think
I'm
going
to
pass
it
to
ellie,
because
this
was
a
very
interesting
research.
He
he's
done.
C
B
B
Stalinquity
was
one
of
the
tools
that
was
available
for
us.
We
tried
it
out.
It
was
trivial.
We
ended
up
not
only
solving
our
low
balancing
issue,
but
we
also
gained
a
lot.
It
was
very
easy
to
maintain,
but
also
we
were
able
to
just
you
know,
look
at
everything
that
is
going
on
between
the
services
in
in
no
way
that
was
available
to
us
before
we're
able
to
see
all
the
traffic
between
services
we're
able
to
see
which
excessive
calls
would
be
made
from
one
service
to
another
right.
B
So
if
you
had
one
service
like
bombing
another
service
with
with
requests,
we
could
see
that
live
heading.
On
top
of
that
is
the
whole
security
topic
which
we
were
just
completely
overlooking,
and
today
we
have.
We
have
encryption
going
between
our
services,
so
specifically
mtls.
Our
services
are
encrypted.
B
The
communication
is
equipped
in
end-to-end.
Both
sides
also
thanks
to
linkerid,
so
that
really
changed
the
way
that
we
kind
of
work
with
with
our
services
and-
and
it
kind
of
it,
integrates
very
well
with
kubernetes
right.
So
we
have
like
I
mentioned.
We
have
like
multi
multi-cloud
setup.
We
have
it
both
on
aws
and
all
azure.
It
just
works
works
the
same
on
both
clouds,
which
really
enables
us
to
be
very
like
flexible.
B
Now
we
test
it,
we
run
it,
and
another
interesting
thing
is
that
it's
not
only
for
production,
so
we
found
that
it's
very
it's
very
helpful
when
you're,
also
developing
so
before
we
reach
production.
We
we're
also
using
linker
d,
for
example,
as
a
surface
mesh,
to
just
kind
of
find
those
problems
ahead
of
time.
But
before
we
reach
production,
our
developers
can
go
on
and
see
all
the
anomalies
and
traffic
that
you
can
see
between
the
services
and
then
kind
of
mitigate
them
even
before
we
reach
production.
B
So
it
was
really
was
really
a
great
experience
for
us.
So
far,.
A
Yeah,
that's
awesome
and
before
we
continue
with
the
rest
of
the
question,
I
know
as
an
end
user
community,
a
company
sharing
stories
about
how
you
use
these
technologies,
not
just
hearing
from
the
vendors,
it's
very
crucial
for
the
community,
because
people
want
to
learn
from
the
lessons
and
the
mystics
that
that
others
have
made.
Did
you
at?
Did
you
get
to
attend
kubecon,
the
last
coupon
that
happened
in
any
or
the
eu?
One.
B
A
B
Yeah
we
did,
we
actually
submitted
it.
Oh
nice
yeah
we're
yeah,
so
we're
hoping
even
to
come
to
within
the
speakers
as
well.
A
Nice,
nice
I'll,
definitely
be
looking
towards
some
of
the
lessons
you
learned.
I
took
my
cts
recently
I
passed
thank
god,
so
it's
always
interesting
to
learn
how
others
are
exploring
things
on
the
collaborative
ecosystem
and
also
especially
when
it
comes
to
security,
because
with
all
the
supply
chain
issues
and
everything
happening,
we
definitely
need
to
know
more
about
how
we
all
secure
our
things.
A
So
now,
on
the
topic
of
security,
what
are
the
trends
you
are
observing
in
the
cognitive
industry
that
you
think
should
be
taken
seriously
when
it
comes
to
security.
B
Well,
I
think,
I
think,
aside
from
service
measure
alone,
which
is
also
gaining
a
lot
of
popularity,
so
the
concept
of
I
think
chaos
engineering
is
most
is
most
interesting
to
us.
The
ability
to
kind
of
fail
services
and
infrastructure
on
purpose
and
doing
it
so
easily.
You
know
kind
of
like
a
built-in
way
of
configuring.
B
C
Yeah
thanks,
so
we
are,
we
are
taking
a
look
at
the
oppa
as
well,
along
with
some
new
feature
of
of
linker
d
that
was
introduced
recently
regarding
policies
between
workloads
into
the
cluster.
C
So
as
as
as
we
grow
our
cluster
and
have
more
workloads,
we
would
have
to
to
make
it
organized
in
a
way
that
well,
they
call
they
call
kubernetes
today
is
the
os
of
the
cloud
right.
So
so,
when
you
run
when
you
run
so
many
so
many
stuff,
so
many
workloads
on
kubernetes,
sometimes
it
tends
to
be
quite
quite
a
mess
to
manage.
C
So
we're
taking
a
look
into
this
in
the
security
aspect,
especially
to
make
sure
that
only
the
workloads
who
need
to
actually
be
able
to
speak
to
each
other
can
do
so.
In
addition
to
storm
tools.
Well,
all
of
us
still
have
a
little
back
hurt
from
the
from
the
recent
vlog
for
jr
problems
right
yeah.
I.
A
C
Ellie
had
many
many
long
nights.
C
C
We
will
probably
know
it
before.
Others
will
know
it.
We
have
a
very,
very
intense
system
that
scans
our
containers
before
they
ever
leave
our
our
dev
machines
and
we
are
using
some
some
open
source
utilities,
along
with
with
some
vendors,
to
help
us
do
so
so
tools
like
gripe
and
snick,
for
example,
and
other
tools
from
anchor
that
we
are
evaluating
as
well,
which
is
super
important.
There
are
two.
C
There
are
two
main
vectors
here
in
addition
to
not
be
able
to
push
an
infected
image,
sometimes
like
we
saw
with
log4j,
the
image
was
already
there
deployed
on
the
production
of
probably
everyone,
and
then
the
the
the
zero
day
or
the
vulnerability
was,
was
found
when
the
image
was
already
there.
So
so
it's
a
very
important
thing
to
note
that
sometimes
you
will
not
introduce
the
vulnerability
when
you
add
something
new,
but
but
many
times
you
will
find
a
vulnerability
in
something
you
already
have
deployed
onto
your
customers,
production
environments.
A
B
Yeah,
I
also
I
thought
also
I
wanted
to
mention.
D
Yeah
not
only
like,
as
our
scale
grows,
so
we
are
looking
for
the
most
efficient
ways
to
manage
our
clusters
and
secure
as
well.
So
we
are
getting
into
the
gitops
topologies.
We
are
implementing
gita
ops
for
us
to
securely
manage
and
have
the
least
privileges
way
of
managing
our
remote
clusters.
So
that's
something
we're
also
starting
demanding.
A
A
My
next
question
I
think
you've
covered
most
of
it
already.
2020
was
a
huge
challenge
for
everyone
in
the
industry
you
already
mentioned
lock4g
there
were
solar
winds.
There
was
quite
a
lot
of
supply
chain
security
issues
and
other
things
that
were
happening
as
a
company
salt
lake,
probably
not
for
your
client.
What
other
challenges
was
thrown?
Did
2021
or
2020,
throw
at
you
that
really
shook
the
company,
but
you
were
able
to
scale
through
it.
B
So
I
think
you
know,
being
a
security
company
puts
us
a
little
bit.
You
know
on
a
very
high
high
bar,
really
can't
allow
any
any.
You
know
it
falls
there,
but
aside
from
security,
I
think
our
biggest
challenge
today
is
our
scale
so
being
able
to
to
kind
of
scale
fast
and
doing
that
and
with
with
the
minimal
team.
B
So
you
know,
god
has
a
fairly
small
team,
which
does
pretty
much
everything
we're
looking
at
adding
other
escrow
ease,
really
looking
at
observability
and
reliability
as
as
the
kind
of
bit
too
big
things
that
are
are
ahead
of
us
so
being
able
to
to
leverage
kind
of
technologies
that
would
allow
us
to
first
of
all
sleep
better.
You
know
be
able
to
kind
of
be
on
top
of
those
things
you
know
before
they
happen.
B
These
are
kind
of
the
things
that
are,
you
know
we're
looking
into,
but
also
when
we're
deploying
things
we'd
like
to
be
able
to
kind
of
test
those
things
out
before
they
reach
production.
So
counter
redeployments
is
really
that
the
next
big
thing
for
us
in
terms
of
deployment
integrating
that
into
our
githubs
and
cicd
environment,
and
you
know,
kind
of
pushing
a
new
version
of
some
kind
of
deployment
and
splitting
the
traffic.
B
You
know
trying
it
a
little
bit
seeing
if
it
works,
then
rolling
back
automatically
would
really
do
a
lot
for
us.
I
think
those
are
kind
of
the
big
topics.
Yeah
all
right.
A
Yeah
awesome
definitely
getting
better.
Sleep
is
the
most
major
motivation
for
almost
all
of
us,
especially
when
the
industry
always
keeps
throwing
new
things
once
when
you
think
you
are
done
with
one
another.
One
comes
up,
yeah
right,
definitely
yeah
yeah.
So
I
think
my
next
question
goes
to
ralph.
You
already
mentioned
that
you
do
multi-cloud.
Do
you
also
do
multi-tenants?
A
How
do
you
distribute
the
workloads
between
your
clusters,
since
you
have
multi-cloud
already,
and
what
challenges
does
this
using
multi-cloud
bring
to
you
and
multi-tenants?
If
you
do
multi-tenants.
D
We
don't
do
multi-tenant
at
the
moment
and
that's
most
certainly
something
we
are
heading
towards.
I
think
the
most
challenging
thing
about
running
like
a
multi-cloud
is
managing
it,
not
only
in
terms
of
like
deployments,
but
you
know
having
the
right
scale
having
the
right
resources.
D
Your
monitoring
is
now
needs
to
support
like
multiple
clusters.
So,
instead
of
like
a
single
child,
you
now
have
like
a
bunch
of
childs
you
need
to
take
care
of,
but
with
tools
of
observability
like
datadog,
we
use
jaeger
as
well.
D
We
find
ourselves
managing
it
the
right
way,
instead
of
like
running
after
each
cluster
making
sure
you
know
it
has
the
right
resources
it
operates.
Normally
we
usually
set
our
monitoring
to
notify
us
when
something
goes
bad
and
learn
from
like
from
past
incidents,
so
we'll
be
more
reactive
than
running
after
managing
each
cloud
provider,
and
I
think
another
challenge
is
cloud
provider
issues.
I
mean
it's
not
that
rare,
but
cloud
providers
does
have
issues,
and
so
that
can
also
affect
your
operations.
D
C
So
like
like
as
a
message
to
the
community,
everyone
have,
or
at
least
most
people
should
have
a
redundancies
right
like
if
we
are
mostly
deployed
in
our
example
in
aws,
and
then
we
have.
We
have
another
cloud
provider
there,
as
as
the
resiliency
provider
in
case
something
goes
wrong
test
it.
Okay,
it's
not
enough
to
have
it
ready
for
the
day
right.
We
need
to
test
it,
because
if
you
don't
test
it
on
the
day,
you
need
it
like
it
might
not
work.
C
So
this
this
resembles
with
what
with
what
ellie
said
before
we
are
going
to
to
introduce
in
2022
of
chaos,
engineering
this.
This
can
be
one
one
of
the
one
of
the
kind
of
things
we
will
want
to
test
as
fast
as
possible,
automatically
not
only
having
a
way
to
do
it
manually,
but
automatically
it
happens.
A
lot
services
go
down,
it's
normal.
This
is
the
the
way
the
cloud
acts
right
when,
when
things
get
super
complicated,
they
tend
to
break
sometimes
so
yeah
so
test
test.
Your
emergency
protocols.
A
A
A
You
know,
no
matter
how
big
your
service
provider,
these
things
can
go
wrong
so
and
you've
been
able
to
prepare
is
a
very
crucial
thing
that,
as
a
company,
one
definitely
needs
to
make
sure
that
in
case
things
go
wrong.
There's
always
something
that
to
keep
the
service
running
because
nobody
wants
to
lose
money
when
things
go
wrong.
A
D
C
D
A
A
D
D
I
think
it's
not
only
in
the
phase
of
the
it's,
not
only
in
the
face
of
the
testing,
but
also
once
deployed
to
production.
I
think
there's
a
challenge
to
monitor
it
properly,
once
the
feature
is
released,
monitoring
or
having
the
right
visibility
of
on
the
feature
will
allow
you
to
better
understand
how
it
behaves
throughout
time.
I
mean
it
doesn't
necessarily
mean
that
the
moment
you
release
a
feature,
it's
it
will
work
properly
for
good.
You
need
to
have
proper
visibility
and
monitoring
throughout
time
to
detect,
like
future
fixes
issues.
A
Yeah,
that's
awesome,
but
in
all
of
this
that
we've
been
talking
about.
What
do
you
think
is
next
in
terms
of
cloud
native
at
social
security.
B
Well,
I
think
well
so
far,
the
the
tools
that
we've
we've
learned
that
are
available
are,
you
know,
are
really
there's
a
there's,
a
lot
of
there's
a
lot
of
abundance
of
utilities
and
products.
Every
day
we
look,
you
know
we
go
on,
we
don't
see
ncf,
you
know,
we
see
the
kind
of
landscape,
we
see
new
and
new
tools.
We
have
a
backlog,
things
that
we
wanna,
we
wanna
go
through,
so
you
know
so
far.
I
think
it's
very
it's
something
that
we
can't
cover
like
so
many
projects.
B
You
know
we
have.
We
have
a
lot
of
plans
and
and
not
a
lot
of
not
enough
time
to
to
kind
of
try
things
out.
I
think
the
tools
that
are
available
today
are
kind
of
filling
up
our
backlog,
and
we
have
things
to
look
at.
I
think
mostly
around
around
kubernetes.
You
know
things
that
are
kind
of
supplements
to
kubernetes
in
monitoring.
Are
those
I
can't
think
of
specific
projects
that
we
haven't
listed?
We
haven't
spoken
about
that.
A
Yeah
awesome,
sorry,
I
clicked
on
your
own
thing
on
my
system,
yeah
awesome
and,
I
think
yeah.
I
think
you
are
only
work
on
the
platform
right,
so
I
think
you'll
be
able
to
talk
more
about
developer
experience.
You
know
with
introducing
all
these
new
technologies
and
bringing
in
all
these
upgrades
and
new
improvements
to
your
cluster.
A
C
Yeah,
so
so
yeah,
it's
it's
a
really
really
big
thing
where
we
are
trying
our
best
to
allow
our
developers
to
not
only
be
able
to
use
this
stuff,
but
also
to
understand
this
stuff,
because
when
something
breaks
in
a
company
like
salt,
we
are
recruiting
all
the
time,
and
we
are.
We
are
scaling
not
only
in
our
workloads
but
but
also
in
our
in
our
human
resources.
C
So
you
you,
you
would
want
to
be
able
to
to
introduce
new
developers
to
the
system
and
also
when
you're,
introducing
new
technology.
You
would
want
your
existing
developers
to
be
able
to
to
use
it
properly,
but
not
less
important,
like
I
said
to
understand
it,
because
if
they
don't
understand
it,
then
then
we
will.
C
We
will
be
the
bottleneck
right
in
solving
everything,
because
everyone
will
come
to
us,
so
our
our
development
environment,
since
they
are,
it
became
quite
a
challenge
to
to
run
it
on
a
local
dev
computer.
C
Also,
if,
if
you
remember
one
of
the
one
of
the
12
factor,
app
recommendations
or
or
standards
is
to
to
make
the
developer
work
on
an
environment
that
is
as
close
as
possible
to
production
right.
C
So
this
is.
This
is
how
we
do
it
this
cluster
or
clusters.
We
we
use
telepresence
to
connect
to
them.
So
telepresence
is
a
is
a
really
cool
project
and,
and
their
latest
version
is,
is
very
nice.
We
are
using
it
extensively
and
this
way
when,
when
a
developer
is
working
on
on
one
of
our
many
services,
he
can.
C
He
can
instrument
only
this
service
on
his
local
machine
and
have
this
service
talk
to
the
rest
of
the
of
the
cluster
as
if
he
was
sitting
inside
the
cluster.
So
this
is
a
project
we've
graduated
a
while
ago.
People
are
using
it
they're,
loving
it,
and
it
also
helps
us
to
save
on
some
costs,
because,
rather
than
having
one
giant
cluster
that
the
developers
are
are
fighting
over
right,
we
have.
C
We
have
many
small
name
spaces
for
which
we
we
pay
less,
and
the
developers
are
not
waiting
in
line
to
test
their
stuff.
On
the
cluster.
B
You
know
dennis
request,
as
if
you
know
like
we
said
as
if
he
was
in
the
cluster,
so
one
of
the
services
conduct
directly
to
the
pods
and
varieties
which
gives
you
like
a
feeling
that
you're
you're
inside
a
cluster
you
can
actually
develop
inside
it,
which
really
solves
a
lot
of
problems.
You
have,
for
you
know.
A
Yeah,
that's
really
awesome
and
yeah.
It's
been
interesting.
Some
of
your
experiences
and
some
of
the
insights
you've
been
sharing.
I
know.
Definitely
our
community
will
appreciate
this
kind
of
content,
but
as
an
end
user
community.
You
know
the
cncf
landscape
is
like
this
landmine
of
new
things
always
coming
up
on
new
technology.
Sometimes,
if
you
go
there
today,
tomorrow,
you
go
back
you're
like
oh.
This
thing
has
expanded.
There
are
new
things
here.
C
Yeah
so
so,
as
you
said,
the
the
cncf
landscape
is
an
awesome
awesome
website.
We
learn
a
lot
by
by
by
polling
it
like
every
few
days
and
and
so
far
the
community
was
amazing.
We
didn't
have
any
pro
any
project
that
we
we
needed,
some
community
involvement
and
we
didn't
find
the
people
or
or
the
people
were
not
responsive.
C
So
we
really
think
the
cncf
made
made
a
great
community
which
is
supportive
and
and
very
fun
to
be
involved
in
so
on.
Our
on
our
experience
like,
for
example,
the
process
we've
had
with
with
the
link
rd
community,
which
was
was
very
fun.
We
had
some
questions.
C
We
approached
them
in
in
their
slack
and
we
developed
some
kind
of
a
really
warm
and
nice
relationship
in
which
we
we
are
hosted
in
their
in
their
community
calls
and
talking
about
the
features
we
use
and
and
educating
other
people
of
the
of
the
community
so
yeah.
This
was
our
our
experience.
It
was.
It
was
very
nice.
A
Yeah,
that's
really
awesome,
you
know.
One
of
the
great
things
about
the
collaborative
community
is
you're,
always
welcome,
and
you
you
get
that
welcome
feeling
where
you
from
even
assets,
someone
that's
completely
new
to
the
ecosystem.
It's
easy
for
you
to
learn
new
things
and
also
learn
from
the
experiences
of
others
yeah,
and
I
also
noticed
something
in
your
background
only
that
I
guess
that
was
fun
and
probably
a
good
event.
A
C
Yeah
and
and
this
gopher
is
from
from
gopher
con
tel
aviv
right
before
coffee
hit,
it
wasn't.
B
A
B
I
think
we
mentioned
it,
but
I
think
a
service
mesh
interface
is
something
that
we
really
really
want
to
see,
evolve
and
and
in
the
coming
months
we
really
hope
you
know
these
are
kind
of
pushed
forward.
You
know
with
istio
and
and
linker
d
and
all
you
know
dashboards
like
yali,
so
that's
something
we
really
would
like
to
contribute
and
see
how
it
evolves.
That's
kind
of
the
big
thing
that
we're
hoping
to
see-
and
I
think
that's
it
most
of
it.
A
Yeah
awesome,
thank
you
very
much
ellie
and
omri
and
gal.
Also,
thank
you
very
much
for
joining
us
today
and
it's
really
been
an
enlightening
session.
I
personally
like
a
lot.
I've
been
delving
more
into
communities,
security
lately
and
hearing
some
of
the
challenges
and
lessons
you've
learned
it's
it's.
It's
kind
of
resonates
with
a
lot
of
things.
I've
been
delving
into
and
it's
awesome
to
see
people
doing
most
of
it
in
the
in
real
life.
Now.
A
Thank
you
very
much
everyone
for
joining
the
latest
episode
of
the
cloud
native
end
user
lounge.
It
was
great
to
have
the
team
from
social
security
talking
to
us
about
their
usage
of
cloud
active
ecosystem
and
the
security
landscape
of
cognitive
as
a
whole.
We
also
really
loved
the
the
flow
in
which
the
questions
and
some
of
the
awesome
new
information
that
they
shared
with
us.
We
bring
you
the
latest
cloud
native
end
user
series
on
the
fourth
thursday
of
the
month
at
9.
00
am
pacific
time.
A
Don't
forget
to
also
join
us
for
kubecon
cloud
native.com
here
in
may.
Hopefully,
you
you'll
probably
hear
the
team
from
social
security
sharing
more
about
the
experiences
at
the
conference.
Hopefully
we
are
able
to
meet
in
spain,
definitely
I'll
be
going
to
spain.
Maybe
at
least
I
get
to
travel
to
a
conference
in
real
life,
yeah,
yeah
and.
B
A
Yeah
exactly-
and
you
also
hear
a
lot
of
latest
things
from
the
cloud
native
community
and
if
you
also
like
to
showcase
your
usage
of
your
cloud
native
tools
as
an
end
user,
join
the
end
user
community
with
more
details
on
cncf.io,
slash
enduser.
Thank
you
very
much
for
joining
us
today
and
see
you
next
time.