►
From YouTube: Secrets Store CSI Community Meeting - 2020-11-12
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
Okay,
welcome
today
is
november
12th
2020,
and
this
is
our
csi
secret
store
community
call.
A
All
right
and
with
that
said,
let's
go
ahead
and
jump
into
it.
So
we
got
a
couple
of
items
here
and
I'm
assuming
these
are
yours.
You
want
to
discuss
initial,
we'll
start
off
the
driver.
B
C
C
C
The
driver
was
interpreting
that
as
like
authoritative
for
using
the
paths
on
the
host
file
system
to
write
files
and
to
read
files
from
so.
We
added
a
bunch
of
validation.
C
To
fix
that,
or
at
least
try
to
mitigate
that,
and
then
I
think,
going
forward,
there's
probably
some
work
still
on
like
the
types
of
permissions
that
we
recommend
giving
out
to
to
users
of
the
driver,
which
should
be
don't
want
to
modify
the
status
part
of
the
resource.
D
C
D
B
C
Yeah,
just
one
third,
our
main
form
of
communication
is
like
this
meeting
and
in
the
slack
channel
right.
A
A
All
right
so
to
do
this
is
to
do
a
psa
on
the
latest
driver,
great
yeah.
That
makes
I'm
sorry
go
ahead.
Anything.
A
Okay,
all
right
I'll,
just
get
notes
here
all
right.
Next
up
we
have
the
doc
for
the
secret
store,
csi
driver
membership
go
ahead
and
bring
that
up.
B
Yeah
I'm
so
there
have
been
a
lot
of
folks
helping
out
in
the
community
actively
reviewing
peers
and
also
contributing
in
terms
of
fixes
and
features.
So
I
wanted
to
draft
a
doc
on
what
is
the
criteria
that
we
want
to
have
for
promoting
members
to
reviewers
and
then
gradually
to
approach.
B
A
Great
yeah,
so
if
you
have
any
feedback
on
the
dock,
if
there's
anything
that
you
want
to
be
considered
as
part
of
the
criteria,
please
go
ahead
and
make
your
notes
and
and
our
edits
anish.
When
would
we
like
to
have
this
doc
kind
of
be
signed
off
on
as
far
as
what
we
believe
to
validate
the
person
as
a
maintainer,
slash
owner.
B
If
everyone
can
go
through
it
and
add
comments
to
it,
if
they're,
okay
with
it,
then
I
think
we're
good
and
then
the
next
step
would
be
to
also
have
this
published
in
our
the
secrets
to
csi
driver
repo,
so
that
new
contributors
know
what
is
the
criteria
that
we
use
for
promoting
to
the
reviewers
and
approvers,
and
then
we
can
just
basically,
we
want
this
published
in
github,
so
that
users
can
actually
see
it
when
they
come
to
contribute
and
then.
A
Perfect,
okay,
so
how
about
we?
Just
maybe
just
by
next
meeting
so
again,
two
weeks
we
can
just
sign
off
on
this
and
then
yeah
we'll
also
broadcast
this
on
this
slack
channel
as
well.
So
you
can
get
yeah
another
psa
on
this
too.
A
All
right,
let's
see
now,
I
think
this
is
the
last
on
the
agenda,
so
the
stable
milestone
created
in
driver
based
on
last
week's
community
call.
B
Yeah
so
last
week
we
went
over
the
gas
table
criteria
dock
we
reviewed
each
and
every
individual
topics
that
we
had
listed
in
there
and
based
on
that,
this
is
the
initial
stable
milestone
that
I've
created.
So
I
wanted
to
post
it
here
so
that
folks
can
review.
B
It
also
add
new
issues
that
we
think
we
missed
out,
and
I
think
the
next
step,
similar
to
what
we
discussed
on
the
last
call,
was
if
we
can
start
picking
up
issues
and
then
assigning
it
and
then
going
over
it
and
trying
to
finish
it
up,
then
it'll
be
really
great.
B
And
arita
also
added
a
comment
to
review
the
production
readiness
questionnaire,
so
I
think
that'll
be
a
good
thing
to
do
so.
I
think
that's
to
do
that.
We
want
to
do
so.
We
basically
want
to
review
the
questionnaire
and
also
add
that
the
ga,
stable
doc
and
also
add
a
reference
to
the
ga,
stable
doc
in
the
secrets
to
csi
driver
repo.
B
A
Yeah
yeah,
it
makes
sense
any
comments
to
that.
Anyone
have
any
thoughts.
A
Okay,
perfect,
okay,
so
I
think
that
finishes
us
for
the
items
that
were
on
the
agenda.
Is
there
anything
anyone
else
wish
to
discuss
and
or
comment
on.
B
And
there's
just
another
provider
specific
fix
that
we
have
all
been
coordinating
and
working
on.
So
I
there's
actually
a
outstanding
pr
for
hashicorp
vault
to
update
to
the
latest
version
to
add
the
e2e
test.
So
I
think
that's
pending.
So
we
probably
need
to
review
that
later,
but
I
just
wanted
to
check
in
with
tom
about
the
grpc
changes
for
the
world
plug-in.
I
know
we
discussed
about
it
last
week,
so
just
checking
in
to
see
if
you
need
any
help
and.
E
Thanks
yeah,
I
I'm
afraid
I
don't
have
a
solid
timeline
but
yeah.
That
is
right
at
the
top
of
the
csi
to-do
list.
For
us,
the
yeah,
the
test.
Pr,
I
think,
is
pretty
much
ready
to
go.
I
was
just
taking
a
moment
to
go
and
update
all
of
the
examples
to
the
post,
0.0.5
interface
change
for
the
cids
that
we've
got
in
that
provider.
B
E
Yeah,
there's
there's
a
note
in
the
readme.
I
think
there's
a
note
in
the
release
as
well.
It's
it's
actually
we've
been
testing
an
old
version
of
the
provider
on
the
on
the
driver,
repo
for
a
while,
because
the
tests
haven't
been
updated
for
zero
zero
five,
which
is
where
the
braking
change
was
introduced
and
yeah
generally,
I
think
that's.
E
Working
out
a
good
way
to
to
make
sure
that
we're
testing
the
latest
version
of
the
providers
in
the
driver,
e2e
tests
without
having
to
raise
a
pr
every
time
would
be,
would
be
worthwhile.
It's
it's
probably
the
the
the
existing.
C
E
For
replacing
the
batch
tests
with
the
gingko
is
probably
way
too
big
to
consider
that,
along
with
it
as
well
but
yeah,
it
would
be
nice
to
to
solve
that
problem
because
yeah
we've
just
been
testing
a
static
tag
in
the
e3
tests
for
quite
a
while.
Now.
B
Yeah,
I
think
the
other
ones
also
having
e2e
tests
on
the
provider.
Repos
like
I
mean
today,
the
way
we're
doing
it
is
for
breaking
changes
on
the
provider.
We
usually
have
integration
tests
in
the
provider
that
let
us
know
that
this
change
is
actually
not
going
to
work
with
this
particular
driver
version,
or
do
we
need
a
latest
version
and
then
we
basically
just
communicate
that
as
a
kit
of
issue
and
then
because
there
is
a
version
compatibility
matrix.
E
Yeah,
okay,
that
makes
sense
we
can.
We
can
get
some
yeah
e2e
tests
going
on
the
provider.
In
that
case,.
D
I'm
sorry
just
to
recap
on
the
0.06
braking
changes.
I
don't
actually
remember
if
that's
being
propagated
to
the
driver,
it's
e
to
e,
so.
E
And
it
wasn't
actually
zero
zero
six
that
made
the
breaking
change:
zero
zero.
Six,
mostly
just
had
the
the
security
patch
in
it
zero
zero
five
was
the
breaking
change
just
for
the
notes.
A
B
All
right
all
right,
I
I
have
a
pr
for
the
dogs,
it's
an
initial
move
to
the
docs
framework.
So
if
you
click
on
that,
you
can
actually
scroll
down.
We
have
already
set
up
the
netlife
account.
So
there's
a
preview
available,
I'm
just
trying
to
add
more
details
to
it.
But
if
you
scroll
all
the
way
down,
yeah,
oh
you're,
not
logged
in.
C
B
Yeah,
so
this
is
basically
the
preview,
so
every
time
we
make
changes
to
docs
it'll
show
up
in
the
pr
and
right
now
it's
a
very
basic
framework.
B
A
Yep-
and
this
is
using
this-
is
the
doxie
theme
for
hugo
right
finish.
B
No,
this
is
a
different
one.
Actually.
A
Yeah
yeah,
I
think
we
probably
just
want
to
add
the
dots
on
how
to
to
update
this
all
right,
pretty
simple,
okay,
great
all,
right,
I
think
we
are
at
the
end
of
the
road
on
the
agenda
items.
One
thing
I
want
to
discuss
is
in
two
weeks:
what
would
normally
be
our
scheduled
time
on
the
26th?
A
B
A
A
C
A
Get
consensus
there
perfect
all
right,
so
our
next
schedule
meeting
will
be
thursday
december
3rd
and
thank
you
rita
for
doing
the
inline
note
taking
so
we're
good
there
all
right.
If
that
is
it
no
other
comments
or
anything
to
discuss
we'll
go
ahead
and
in
the
meeting.
A
Okay,
we
will
see
you
guys
see
everyone
december
3rd.
Thank.