►
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
A
A
B
Hi,
so
I
introduce
myself
briefly,
I'm
a
site,
reliability
engineer
at
rstudio
at
our
studio,
we're
looking
to
we're
building
out
a
a
cloud
ide
platform
for
data
scientists
and
we're
obviously
doing
so
with
as
many
cloud-native
technologies
as
possible.
I'm
looking
to
add
more
all
the
time.
C
Hi,
terry
hi,
everyone,
my
name,
is
andrea
garbuzzera,
I'm
an
engineer
and
co-founder
at
old
keys.
Altkeys
is
a
company
that
is
offering
authorization
as
a
service
in
the
cloud
I
used
to
be
an
embedded
engineer
for
more
than
a
decade
and
then
outkeys
was
my
opportunity
to
turn
into
cloud
native
aware
technologies.
C
Cloud
native
technologies
as
the
future:
that's
the
reason
why
we
joined
cncf
as
end
user
and
that's
one
of
the
reason
why
hamir
participated
at
this
radar
team.
A
A
C
Okay,
when
we
started
with
this
radar
team
task,
we
had
to
choose
a
topic.
Many
many
of
them
were
quite
interesting,
but
we
ended
up
choosing
a
secret
management,
especially
because
yeah
from
my
point
of
view
and
from
my
company
point
of
view,
security
is
is
a
focus
in
our
business.
C
C
Many
of
them
are
exposed,
and
whenever
you
have
to
coordinate
all
these
services,
you
need
to
deal
with
how
each
of
them
authenticate,
with
each
other,
so
secrets
are
at
the
base
of
this
of
these
mechanisms
and
as
soon
as
a
company
needs
to
automate
its
operation
process,
it
needs
to
deal
with
how
to
store
secrets
secrets.
Management
is
basically
the
set
of
techniques
that
are
used
for
keeping
those
secrets
safe,
usually
by
storing
them
somehow
encrypt
encrypted
somewhere
but
yeah.
C
We
we
choose
to
to
focus
our
radar
on
this
topic,
because
it's
not
that
easy,
as
it
can
appear
at
first
glance.
So,
that's
that's,
basically
why
we,
we
we
at
this,
this
this
decision
to
do
to
focus
on
secrets
management
for
for
the
raider
for
this
this
month,
rather.
A
Okay,
awesome
all
right,
so
still
a
reminder
for
what
this
technology
radar
looks
like.
So
the
goal
with
the
technology
radar
was
to
survey
the
end
user
community
and
ask
the
people
as
a
community.
What
do
you
currently
use
and
recommend
internally
for
your
own
company
and
there
are
three
main
options
so
adopt,
meaning
we
clearly
recommend
it:
we've
run
it.
We've
used
it
for
a
long
time
and
it's
pretty
stable,
pretty
mature
trial,
meaning
we've
used
it
with
some
success.
A
So
if
you
have
a
need
for
this,
then
you
should
be
looking
at
this
tool
or
assess,
meaning
we've
tried
it
out.
We
think
it's
promising.
Maybe
it
doesn't
cover
every
use
case,
or
maybe
it's
not
quite
mature
yet,
but
you
should
consider
it
anyway
and
then
there
was
a
fourth
option
that
people
could
choose
which
was
hold
hold,
meaning
we
don't
use
this
solution
anymore.
B
Sure
so
I
I
think
my
expectations
were
potentially
a
little
naive
in
that
I,
in
looking
at
the
space
of
secrets
management,
I
mainly
expected
organizations
to
be
using
the
the
offerings
by
the
public
cloud
that
they
were
already
in
it's.
It's
obviously
a
much
easier,
a
much
easier
choice
to
adopt
just
essentially
a
separate
set
of
apis
from
the
same
public
cloud
that
you're
already
using.
B
If
you
are
embedded
in
a
public
cloud,
if
you're
using
a
single
public
cloud,
it's
kind
of
a
an
easy
choice,
or
at
least
in
my
view
it
it
seems
like
a
very
easy
choice
to
just
adopt
it.
You
know
a
new
small
piece,
a
new
small
service
that
is
that
is
offered
by
those
clouds.
B
In
in
some
way,
shape
or
form-
yes,
that's
at
least
one
of
the
ways
that
we
that
we
manage
secrets
definitely
is,
as
a
small
team,
it's
kind
of
an
easy
pickup
to
to
use
an
additional
service
from
a
public
cloud
than
to
you
know,
kind
of
build
out
our
own
in-house
tool
or
or
adopt
a
an
additional
tool
that
we
have
to
run.
Take
care
of,
maintain.
C
Speaking
for
myself,
I
really
expected
a
lot
of
fragmentation
in
this
kind
of
survey.
This
is
probably
coming
from
a
light
survey
that
we,
in
the
light,
investigation
that
we
did
in
the
past
for
for
our
company
on
the
topic,
so
I'm
not
really
surprised
that
we
had
very
spread
answers
and
many
many
tools
or
frameworks
that
have
been
named
by
by
the
people
participating
to
to
to
the
radar.
C
Another
expectation
was
that
in
in
this
very
fragmented
landscape,
we
could
have
found
anyway
some
direction
and
that
that's
what
we
ended
up
with.
We
will
see
later
yeah.
A
We
actually
had
a
lot
more
answers,
a
lot
more
solutions
than
this
as
andre.
You
were
saying
there
were
a
lot.
There
were
a
lot
of
different
frameworks
here
we
ended
up,
I
think,
cutting
off
here,
because
we
felt
like
there
wasn't
enough
data
to
really
justify.
A
B
There
were
definitely
more
of
aws,
discrete
secrets
like
services,
and
we
collapsed
them
in
part,
because
aws
has
made
the
choice
to
make
each
piece
of
secret
management
a
separate
service
in
their
in
their
public
cloud
offering
and-
and
it
definitely
skewed
the
the
results,
since
there
was
huge
numbers
of
adoption,
simply
by
virtue
of
it
not
what
anyone's
service
handles
each
of
the
each
of
the
parts
of
secrets,
management
that
that
a
typical
organization
may
want
to
use,
and
so
we
had
a
lot
of
results
where
a
single
company
was
using
all
of
the
aws
secrets,
services
and-
and
it
ended
up-
ended
up
kind
of
skewing.
A
C
More
than
commenting
on
how
this
happened
to
be
distinguished
between
adopt
and
trial
with
which
was
kind
of
a
discussion
in
terms
of
number
of
votes
to
to
consider
for
for
the
different
categories.
There's
there's
a
point
that
this
is
not
possible
to
see
from
this
table.
There's
there's
a
solution
that,
in
reality,
is
probably
in
a
heterogeneous
set
of
solutions,
which
is
everything
homegrown.
C
We
choose
not
to
represent
them
in
this
final
result
table
because
they
are
definitely
solutions
which
are
quite
different
from
each
other.
So
we
we
ended
up
after
a
discussion
between
the
team
that
it
was
necessary
to
to
investigate
further
if
we
wanted
to
expose
which-
which
of
these
technologies
were
kind
of
interesting
for
for
others
potentially.
C
But
when
you,
when
you
have
to
do
when
you
come
when
you
face
a
homemade
solution,
it's
usually
something
that
is
very
difficult
to
to
use
for
others,
because
they're
very,
usually
tailored
to
to
specific
situation.
C
B
I
can
definitely
add
to
that.
I
think,
as
we've
kind
of
alluded
to
a
handful
of
times,
there
was
a
really
long
tale
of
tools
that
were
used
here
and
that
were
reported
as
being
in
use.
And
so,
while
it's
pretty
obvious
from
the
votes
which
which
of
these
tools
made
sense
as
adopt
the
the
remaining
tool
sets,
were,
there
was
a
little.
There
was
a
little
less
obviousness
out
of
them,
mainly
because
the
the
tale
was
so
long,
and
there
were
so
many
votes
spread
across.
B
So
many
different
solutions
that
that
there
we
kind
of
had
to
use
a
bit
of
judgment
going
down
and
where
to
really
stop
in
this
list.
A
A
So
next
up,
I
want
to
ask
the
radar
team
from
looking
at
the
data
that
people
submitted
and
from
your
own
experience
and
what
you
were
expecting
going
into
this.
What
did
you
find
surprising
or
interesting
or
noteworthy
themes
to
point
out
so
steve
and
andrea
and
the
team
put
together
four
themes
for
us
and
I'd
like
us
to
talk
a
little
bit
about
those
now
the
first
one
is
vault
and
the
theme
is
that
vault
has
the
broadest
adoption
across
many
companies
and
many
industries
so
steve.
Why
don't
you
start.
B
Of
course,
so
I
can,
I
can
say
myself
and
a
handful
of
the
radar
members
were
were
very
surprised
at
the
the
the
fact
that
there
was
such
widespread
adoption
of
vault,
not
because
it's
not
an
extremely
useful
tool,
but
simply
because
it
has
a
pretty
high
cost
of
entry.
It's
a
it's
it's
operational
burden
is,
is
generally
much
larger
than
some
of
the
other.
Some
of
the
other
tools
on
this
list,
and
so
we
were.
B
I
personally
was
pretty
pretty
confused
to
see
this,
but
then,
when
we
start
one
we
once
we
started
talking
a
little
bit
deeper
about
it.
We
started
realizing
that
you
know
this
makes
this
actually
makes
a
lot
of
sense.
B
For
one
point
it
is,
it
has
an
extremely
strong
showing
because
it
does
a
lot
of
what
the
other
tools
do,
but
in
a
cloud
agnostic
way.
If
organization,
if
organizations
are
split
across
multiple
cloud
providers,
if
they
have
large
footprints
in
multiple
clouds
or
on-prem
vault
is
a
is
a
pretty,
is
a
pretty
great
tool
in
order
to
in
order
to
solve
that
problem,
because
it's
comprehensive
and
it
doesn't
require
any
more
lock.
B
Any
more
vendor
lock-in
in
a
particular
public
cloud
and
obviously
being
able
to
be
used
on-prem,
you
know
across
multiple
cloud
offerings
without
having
to
change
tactics.
We
also,
we
also
kind
of
came
through
with
this
idea
that
this
broader
adoption
really
kind
of
makes
sense
when
you
put
it
in
the
context
of
offering
it
as
an
alternative
to
an
in-house
solution,
rather
than
everyone
going
off
and
building
their
own
secrets
management
tool.
B
Vault
is
a
great
tool
for
that
is
very
comprehensive
and
is
able
to
kind
of
allow
people
to
to
simply
adopt
it
and
its
set
of
of
requirements,
and,
rather
than
having
to
you,
know,
go
off
and
write
a
write,
a
solution
for
each
new
secret
problem
that
they
have
so
that
can
definitely
lead
to
a
higher
adoption
rate
and
that's
great.
A
C
Yep,
as
steve
already
pointed
out
before
this,
this
was
something
that
we
expected
when
we
choose
the
the
topic
for
for
the
raider.
We
we
tried
to
to
reason
a
little
bit
around
the
motivation
for
this,
and,
of
course,
we
we
ended
up.
C
Considering
that
the
cloud
the
cloud
providers
native
solutions
are
usually
the
closest
to
to
the
user,
so
they're,
the
the
definitely
one
of
the
first
choices,
if
they
end
up
being
covering
the
needs
that
the
user
has,
they
are
probably
the
fastest
to
to
bring
up.
So
this
is
something
expected
anyway.
C
Part
of
the
choice
of
of
cloud
provider
yeah.
So
probably
we
ended
up
saying
that
there
are
two
different
type
of
organization:
those
that
are
split
across
different
cloud
providers
already
considered
the
lock-in
problem
in-depth
and
they
probably
ended
up
choosing
an
agnostic
tool
for
for
for
the
secret,
for
these
secret
management
needs
smaller
companies,
which
are
at
their
first
cloud
native
experiences,
are
more
likely
to
stick
with
the
solution
provided
by
by
their
their
their
cloud
providers.
C
Yeah,
that's
pretty
small.
We
we
are
sticking
with
the
solution
that
are
kind
of
naive
in
this.
This
in
this
scenario,
because
the
team
is
very
small,
so
secret
security
is
is-
is
mostly
managed
by
encrypted
repositories
encrypted
that
data
within
repositories.
C
We
are
not
yet
concerned
about
sharing
the
content
of
repositories
across
teams,
so
we
are
good
enough
for
now,
but
of
course,
we
are
looking
at
more
a
structured
solution
for
the
future,
because
the
problem
will
come
up
as
soon
as
the
team
grows
and,
and
we
have
the
need
to
give
different
visibility
to
to
secrets
to
different
different
teams.
So
it's
something
we
are
working
on,
so
the
radar
is
definitely
a
good
opportunity
to
to
figure
out
what
what
others
that
are
bigger
than
us
already
went
through.
A
B
So
on
this
radar,
we,
you
know,
we
noticed
it
popping
up
popping
up
a
lot
and-
and
it
was
definitely
surprising-
because
it's
relatively
new
and
it
it's
not
a
general
purpose
tool
or-
and
it
doesn't
have
like
a
general
purpose
solution
for
many
different
secret
aspects.
But
it
is
one
of
the
things
that
we
kind
of
that
we
kind
of
returned
from
this.
B
Is
that
because
it
has
really
tight
integration
with
kubernetes
it,
it
can
not
only
be
seen
as
an
easy,
quick
pick
up
for
those
who
are
already
using
kubernetes
when
it
comes
to
managing
certificates,
but
but
also
that
it
kind
of
leads
us
to
believe
that
certificate
management
is
a
really
high
concern,
it's
top
of
mind
for
those
who
are
adopting
kubernetes
and
so
that
certificate
manager
kind
of
comes
along
in,
even
though
it
is
relatively
new,
because
it's
because
it
solves
a
specific
problem
in
a
simple
way
for
those
that
are
using
kubernetes.
A
C
C
C
This
is
probably
something
that
can
come
up
in
the
future,
because
secrets
management
is
not
rocket.
Science,
it's
basically
encryption
and
good
practice
in
in
workflows.
C
So
it's
probably
something
that
is,
in
my
opinion-
and
I
guess
all
the
radar
team
also
said
something
like
this:
it's
going
to
converge
into
more
more
concrete
best
practices
for
the
future,
so
it's
an
ongoing
process.
It's
probably
something
that
is
it's.
It's
not
speedy
at
the
moment.
A
B
A
Okay,
excellent
and
then
just
one
final
question
to
you.
So
how
did
you
actually
find
the
experience
of
creating
this
radar.
B
First,
I
I
enjoyed
it.
I
thought
it
was.
B
It
was
an
interesting
process
to
go
through
it's
it's
interesting
to
see
that
amongst
cncf
community
members,
there
is
a
an
inherent
goal
not
to
reinvent
the
wheel
and
taking
through
that
kind
of
getting
a
chance
to
participate
in
the
radar
and
see
that
a
lot
of
a
lot
of
different
organizations
of
a
lot
of
different
sizes
are
are
implementing
solutions
around
the
same
topic
in
the
same
fashion
or
in
a
handful
of
the
same
fashions,
is
really
promising
and
and
being
able
to
participate
in
this
kind
of
and
perpetuate
that
notion
of
of
not
having
to
reinvent
the
wheel,
because
there
are
some
some
tools
that
are
ready
and
able
to
be
adopted
by
by
organizations
looking
to
solve
these
same
problems.
C
Yeah
I'm
sharing
steve's
thinking
and-
and
I
I
couldn't
have
said
it
better.
I
just
want
to
to
add
that
I
I'm
very
thankful
thankful
to
cncf
for
the
opportunity
to
participate
in
this
in
this
task
in
this
radar
team
task.
C
It
was
very
enjoyable
to
to
create
a
small
team
in
a
short
time
and
yeah
being
able
to
to
to
share
our
experience
and
and
at
the
same
time,
to
be
working
on
this
data
and
and
figuring
out
what
the
main
threads
were
and
and
the
main
themes
that
came
out
from
from
the
survey
so
really
great
experience
and
I'm
very
happy
to
to
be
part
of
it.
A
Steve
and
andrea
and
the
other
two
members
of
our
radar
team.
I
really
want
to
thank
you
for
your
time
and
and
putting
your
thoughts
and
effort
into
this.
It's
been
really
fun
to
work
with
both
of
you,
so
I
really
appreciate
it.
A
Last
but
not
least,
if
you
want
to
check
out
previous
editions
of
the
radar,
you
can
go
to
radar.cncf.io
so
far,
we've
had
three
additions
on
database
storage,
observability
and
continuous
delivery.
So
please
go
and
check
those
out
and
then,
if
you
want
to
get
involved,
we
want
to
really
reflect
what
people
care
about
what
the
wider
community
is
thinking
about.
A
So
if
you
want
to
help
decide
what
the
next
topic
for
the
next
radar
will
be,
you
can
go
to
cncf
dot,
io,
slash
tech
radar.
This
is
just
a
github
issue
where
you
can
put
in
something
that
you're
interested
in
you
can
vote
up
and
down,
and
the
next
radar
team
will
take
a
look
at
that
to
see
what
people
are
interested
in
hearing
about.
A
Please,
if
you
also
come
and
join
the
end
user
community,
if
you
are
currently
using
cloud
native,
you
can
contribute
towards
the
future
radars.
You
can
come
and
be
part
of
the
radar
team,
so
just
check
it
out,
cncf.io,
end
user
and
then
last
but
not
least,
I'm
always
looking
for
ways
to
make
this
more
valuable
and
usable
and
easy
to
understand.
A
So
if
you
have
any
feedback
about
how
we're
producing
the
radars
or
anything,
you'd
love
to
see
a
bit
more
of
a
bit
less
of
just
send
an
email
to
info
cncf,
dot,
io,
and
that
is
the
end
of
this
edition
of
the
radar.
So
once
again,
steve
and
andrea,
it's
been
a
pleasure
to
have
you
on
and
to
talk
to
you
today.
So
thank
you
so
much.
C
Thank
you
for
the
pleasure
of
mine.
Thank
you,
sherry
for
for
managing
this
team
and
helping
out
with
with
making
it
so
so
nicely
working
and,
to
I
say,
bye,
bye
to
everyone
and
stay
tuned
for
the
next
raiders.