►
From YouTube: Secrets Store CSI Community Meeting - 2022-02-17
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
Let's
record
all
right:
okay,
welcome.
Everyone
today
is
february
17
2022,
and
this
is
our
bi-weekly
csi
secret
store
meeting.
As
always,
this
meeting
is
governed
by
the
cncf,
so
the
code
of
conduct
applies
if
you're
not
familiar
with
all
the
terms
in
the
code
of
conduct.
Please
visit
our
repo
and
look
up
dakota
conda
markdown
file
for
information
with
that.
A
Let's
go
ahead
and
kick
it
off.
Let's
see
it
looks
like
we
got
a
pretty
pretty
light
agenda.
Is
that
right,
I'm
just
looking
not
much
is
happening
here,
some
tommy
and
then
some
stuff.
Let
me
just
go
through
I'll.
Kick
it
off,
because
I
want
to
just
go
through
the
doodle
results,
which
weren't
really
surprising,
we're
pretty
much
at
the
the
normal
times
that
we
do
have
the
meeting
I
haven't
voted.
A
I
I
could
be
a
tiebreaker
here,
but
I
think
consensus
here
is
everyone
that
participated
is
actually
okay
with
the
current
time.
We
could
push
it
back
in
an
hour.
I
would
love
to
hear
from
a
niche
or
anyone
else
on
the
west
coast
if
they
feel
like
that's
going
to
be
beneficial.
A
I'm
on
the
east
coast.
I
think
you
are
too
tommy
with
me,
so
I'm
flexible
with
either
one.
B
Yeah,
maybe
I
also
forgot
to
do
this,
so
maybe
we
push
it
a
bit
more
in
the
chat
for
another
week
or
something
in
case
anyone
else
just.
B
Missed
it,
but
yeah.
D
C
I
think
also
like
yeah.
I
think
me
and
delek
are
here,
but
we
are
also
okay
with
it
like
that's
why
I
think
we
said
if
we
want
to,
we
can
still
do
that.
So
if
the
consensus
is
at
the
end
of
it
like
after
waiting
a
week
still
we
want
to
keep
it
at
eight.
I
think
that's
totally
fine.
A
Okay,
all
right
yeah,
let's
you
know,
I
think,
for
the
the
the
normal
quorum
that
shows
up
here.
I
think
everyone's
okay
with
it.
You
know
if
we
start
getting
more
members
that
show
up.
We
can
revisit
this.
So
I
guess
you
know
my
vote
is
hey.
Let's
just
keep
everything
the
same
until
we
need
to
change
them.
You
know
if
we
get
any
community
feedback.
A
All
right
and
I'll
publish
that
out
onto
the
the
slack
just
to
let
everyone
know
all
right.
Let's
go
down,
we
got
tommy.
You
want
to
talk
about
some
foul
ownership.
B
Let
me
pull
this
up
for
myself
too,
about
writing
different
file
permissions,
but
we
run
the
the
driver
which
writes
the
files
as
root,
and
so
the
the
files
are
always
just
owned
by
root.
So
you
can
change
the
file
permissions,
but
it
can
may
not
be
that
useful
for
you,
because
yeah
the
ownership
is
still
rude.
B
So
I
think
this
might
be
a
good
issue
to
get
more
community
involvement
on
of
just
like
what
the
expected
behaviors,
especially
if
there's
like
username
spacing
where,
like
you
know,
the
user
in
one
pot
may
not
be
the
same
user
number
in
another
pod.
That
kind
of
thing,
so
I
just
wanted
to
call
it
out
see
if
anyone
wanted
to
work
on
it.
B
B
Yeah
like
when
they
mount
something
into
their
pod,
who
do
they
expect
it
like
to
be
the
file
owners
and
groups,
and
how
do
they
expect
to
control
that
and
yeah
just.
B
If
anyone
wants
to
pick
up
kind
of
like
solving
it
too,
I
think
it
would
probably
help
with
our
permissioning
issues.
A
And
yeah
again,
apologies.
I
got
locked
out
of
my
my
normal
zoom
account,
so
these
things
are
looking
a
little
different,
but
I
failed
to
ask
at
the
beginning
of
this
call.
I
see
we
do
have
a
couple
of
do
members
and
for
the
new
members.
What
we
typically
do
is
just
ask
you
to
just
introduce
yourself:
you
can
you
know
if
you
want
to
say
your
organization
etc,
and
then
you
know
kind
of
what
you're
you're
looking
for
or
you
know
what
you're
most
interested
in.
E
Oh
yeah
hi
everybody,
I'm
sean
hurley,
I'm
from
red
hat,
I'm
just
trying
to
join
some
cigs
that
I
found
were
interesting
and
just
listen
in
for
right
now.
I
don't
have
any
any
like
exact
thing
to
get
out
of
this
right
now,
but
this
one
seems
super
interesting
just
from
like
things
that
I
could
see
us
needing
it
for
so
I'm
just
trying
to
just
gain
as
much
knowledge
as
I
can
at
this
point.
D
Thanks
ben
well
welcome
to
the
community
meeting
yeah.
F
Hello,
hey
phil,
my
name
is
julie,
phil
and
I
are
colleagues
at
microsoft
and
I'm
actually
here
because
you
mentioned
this
meeting
is
happening
today
and
I
was
like
oh
these
are
these
meetings
are
here
and
forget
about
these
special
interest
groups
and
that
they're
that
open,
and
so
I
was
like.
Oh
let
me
just
join
and
see
what's
going
on
yeah.
So
my
background
is
more
actually
like
a
full
stack
engineer.
I
did
some
architecture
stuff
as
well,
and
so
it's
interesting
to
hear
how
people
are
using
new
technologies.
F
What
are
the
challenges
that
they
have
because
otherwise
I'm
stuck
in
my
own
little
world
and
all
my
experiences
and
you
know
which
add
up
to
prejudice
in
the
sense
that,
like
the
world
works
like
the
way,
I
know
it,
but
that's
not
always
the
case
yeah.
That's
my
long-winded
introduction.
At
the
end
of
a
day
based
in
munich,
germany.
A
All
right,
let's
go
back
and
I'll
just
check
to
see
if
we
got
any
other
thing
from
the
agenda.
I
guess
not,
though,.
C
Actually,
I
just
wanted
to
go
back
to
the
file
ownership,
one
right.
So,
okay,
I
think
the
first
thing
was:
we
talked
about
providers
making
it
configurable
for
the
individual
files,
that's
written
to
the
file
system,
but
on
the
slack
group
I
think
there
was
this
interesting
ask
about
using
the
security
context,
file
system
permissions
to
also
change
the
actual
permissions
for
the
file
system.
C
Like
I
don't
know
if
that
is
something
that
we
want
to
support
in
the
future,
but
I
mean
we
can
definitely
get
community
feedback,
but
I
think
we
need
to
be
really
cautious
if
we
want
to
do
that
with
security
context.
B
B
No,
that's
why
I
don't
want
to
make
any
changes
yet,
but
it
does
seem
like
this
could
be
a
an
issue
that
people
run
into
and
it
seems
worth
kind
of
tackling.
B
Yeah
it,
I
did
add
it
as
a
comment:
oh
yeah,
security
context.
Okay,
maybe
I
missed
the
chat
thread
in
the
slack,
but
yeah.
C
Okay,
yeah
and
then
also
like
not
on
the
agenda
but
yeah.
We
cut
an
rc
village
rc
image
last
week
and
then
we've
been
testing
that
out,
at
least
on
the
azure
provider.
Now
we've
ended
that
and
then
we've
been
testing
it.
So
one
we
found
one
bug
based
on
tests
that
were
failing
in
gcp
integration
with
the
rc
image.
C
A
Takes
us
to
all
the
agenda,
slash
discussion,
items
I'll
open
it
up.
If
anyone
has
any
questions
or
comments
or
anything
that
they
want
to
chat
about,
please
do
if
not,
we
can
give
you.
C
Okay,
the
first
one
I
actually
opened
it
as
a
follow-up
to
the
discussion
on
tommy's
pr.
So
basically
we
have
a
pr
out
there
which
tries
to
change
the
default
path
where
we
are
looking
for
sockets
for
the
provider
socket.
So
we
are
moving
from
xc
folder
to
var
run
and
then
I
think
we're
trying
to
do
that
in
a
backward,
compatible
way
for
consistency.
The
default
is
going
to
be
it's
equabities
and
then
additional
parts
we'll
check
is
var
run.
C
C
And
then
the
869
is
the
bug
that
we
talked
about.
We
found
an
rc
image,
so
we
have
a
fix
for
it
that
we're
looking.
We
will
be
merging
soon.
C
I
think
the
third
issue
is:
it
was
specific
to
the
vault
provider,
so
I
looked
at
their
and
then
basically
walt
always
returns
version
zero
for
every
secret,
so
that
might
be
a
provider
specific
issue.
So
we
can
move
that
issue
later
and
then
I
think
865
was.
I
was
just
curious.
What
the
community
thoughts
are
on
adding
prometheus
service
monitor
to
chat
like
I
think
I've
got
similar
asks
on
few
other
projects-
and
I
was
just
wondering-
is
this
something
that
we
want
to
add
in
our
hand
chat
in
the
future?
A
This
is
I'm
just
assuming
permitted,
so
is
this
scraping?
Are
we
emitting
any
particular
metrics
with
with
with
the
pods.
C
D
C
The
ask
here
is
it's:
we
also
do
this
as
part
of
himself
and
then,
like.
I
think
my
own
only
comment
was:
if
you
do
this,
then
we
need
to
keep
up
with
the
changes
for
service
monitor
in
our
head
chats
and
then
also
like.
If
there's
any
breaking
change,
we
have
to
update
guidance
and
all
that-
and
I
was
thinking
we
can
keep-
that
out
of
our
control.
A
Yeah
that
I
agree
with
that,
it
seems
like
there's
going
to
be
some
some
ongoing
maintenance
for
this
to
to
keep
working
right.
A
A
C
Yeah,
I
think
they
just
want
to
bundle
everything
within
a
single
chart,
so
when
they
install
it,
they
basically
get
all
the
components
required
for
metrics
and
the
driver
and
everything
installed.
So
they
don't
have
to
do
it
in
two
different
ways
like
I
think
it
works
well,
when
all
you're
really
doing
is
the
driver,
but
I
mean,
if
you're
using
the
service,
monitor,
maybe
like
for
other
components,
then
you
still
have
to
install
it
on
your
own
yeah,
yeah,
okay,.
A
Yeah,
let
me
let
me
I
I
don't
mind
I'll
kick
the
ties
with
this
experience.
I
just
I'm
curious.
Maybe
we
can
revisit
this
next
next
call
and
I
can
kind
of
say
you
know
what
I've
experienced.
C
A
Okay,
we'll
let's
go
ahead
and
that'll
conclude
our
meeting
today,
thanks
everyone
that
has
shown
up
next
meeting
will
be
in
two
weeks,
so
that's
gonna,
be
march
3rd
and
I'll
work
with
initial
get
this
video
out
and
post
it
on
the
youtube
channel
and
we'll
see
everyone
in
a
couple
of
weeks
awesome.
Thank
you.