►
From YouTube: Secrets Store CSI Community Meeting - 2020-10-15
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
All
right
welcome.
It
is
october
15th,
welcome
to
the
csi
secret
store,
meeting
and
just
fyi
again,
not
just
not
that
it's
a
problem
on
this
call,
but
we
are
under
the
cncf
kodaconda
guideline
so
just
be
kind
to
each
other,
and
everyone
will
be
okay,
I'll
see
again
if
you're
new
feel
free
to
add
yourself
to
the
attendees
list.
So
we
know
you
showed
up.
A
And
with
that
we
will
go
ahead
and
kick
off
the
meeting.
I
will
moderate
and
we
have
rita
doing
some
note
taking
for
us
so
first
on
the
agenda.
This
is
anish
to
talk
about
the
secret
store,
csi
driver,
ga
stability.
B
Take
it
away
so
I've
started
a
dock
basically
to
go
over
the
criteria
for
graduating
the
driver
to
stable
and
also
the
criteria
for
different
providers
to
become
ga
and
stable.
B
A
It
is
there
a
call
to
action.
Do
do
we
need
other
eyes
on
this.
B
Yes,
so
we
need
me
more
folks
to
review
this
and
also
add
more
comments.
Whatever
we
are
missing
so
that
we
can
have
a
confined
list
and
then
we
can
start
working
through
that
to
working
through
all
the
items
in
the
list.
Basically
perfect:
okay,.
B
A
Yeah,
if
anyone
has
some
cycles,
when
are
we
hoping
to
move
forward
on
this
initiative?
Is
this
a
week
couple
weeks?
How
long
do
you
want
to
give
people
time
to
be
able
to
look
and
provide
comments
too?.
B
I
would
think
that,
probably
before
the
next
community
call,
if
you
can
get
folks
to
review
this
and
then
have
a
consensus
on
all
the
documented
features
and
also
all
the
improvements-
and
I
think
once
we
have
that
we
can
basically
translate
these
into
github
issues
and
then
start
picking
off
from
data
visions
and
working
on
those
battery.
A
Okay,
so
call
to
action
if
those
that
care,
if
you
can
just.
A
C
A
C
This
in
the
slack
channel,
to
give
more
people
a
signal
that
this
is
here
and
we're
looking
for
feedback
and
comments,
as
this
is
going
to
impact
users
and
all
the
providers.
C
One
thing
one
thing
that
would
be
super
helpful
is
you
know,
based
on
this
list,
is
there
anything
that
the
providers
think
the
driver
should
have,
but
is
not
here
currently
and,
as
you
can
sort
of
see
in
there
bear
it
in
there
is
there's
also
like
you
know,
a
bit
of
backward
compatibility
and
it
touches
a
little
bit
on
the
release
process.
Once
this
driver
goes
to
stable.
We
didn't
really
talk
about
that
here,
but
I
think
it
might.
C
C
And
and
we
need
to
have
that
kind
of
contract
as
we
go
to
stable,
so
I
think
this
is
a
really
good
start,
but
yeah
definitely
looking
for
more
more
feedback.
E
A
Should
we
have
a
do
we
want
to
use
next
community
call
to
kind
of
just
go
through
this,
so
should
we
have
that
as
an
agenda
item.
A
Yeah,
okay,
so
will
focus
on
this
stock
for
the
next
meeting,
which
will
be
on
the
22nd.
I
believe.
A
Okay,
initially
anything
else
to
add.
A
So
get
that
link
okay,
that's
it
for
the
main
stuff.
I
just
want
to
let
those
know,
specifically
those
that
are
consuming
the
azure
provider,
that
we
have
an
initiative,
we're
going
to
be
changing
kind
of
all
of
our
standard,
github
markdowns
over
to
what's
getting
popular,
which
is
you
know,
the
static
site
representation
so
we'll
be
using
the
hugo
static
site
generator
and
specifically
the
doxie
thing.
A
I
think
google
created
the
doxie
thing
for
hugo
and
the
kubernetes.I
o
site
actually
utilizes
that
thing
as
well,
so
so
just
heads
up
nothing
drastic
other
than
we're
just
trying
to
beautify
the
content
for
users
and
and
what's
nice
about
those
templates
is
it.
It
really
makes
the
interaction
from
users.
If
they're
reading
some
of
the
docs,
they
can
directly
kind
of
edit
it
and
get
prs
into
it.
So
it
really
involves
the
community
a
little
more
in
how
those
stocks
are
presented
out.
A
So
that's
it
so
yeah!
That's
it's
a
quick
one
today!
If
there's
no
agenda
items
I'll
leave
it
open.
If
anyone
has
anything
else
that
they
want
to
comment
on
and
or
discuss,.
B
Yeah
just
to
add
to
what
phil
already
has
for
the
csi
provider,
I'm
also
looking
at
doing
the
doing
something
similar
for
the
driver
as
well.
So
since
the
driver
is
part
of
community
six,
we
can
request
for
a
netlify
account
from
the
kubernetes
community.
A
Yeah,
if
you've
not
seen
this
I'll
just
go
out,
here's
an
example
of
what
we're
doing
with
our
azure
pod
identity.
So
we've
basically
again
just
taken
all
the
markdown
from
the
github
repo
and
put
it
in
this
kind
of
static
site.
So
again,
as
users
go
through
this,
you
know.
If
they've
got
a
question,
you
know
they
can
easily.
A
You
know
create
a
document
issue.
This
will
take
them
out
to
actually
do
a
pr
et
cetera.
Well,
I'm
not
logged
in
so
but
yeah
it
it.
Just
really,
you
know
get
feedback.
So
we
start
to
get
a
little
signal,
and
even
with
the
these
these
things
you
can
actually
do
some
google
analytics
as
well,
so
you
can
actually
see
kind
of
which,
which
pages
are
more
popular,
maybe
where
you
can
focus
some
time
on
ensuring
that
that
documentation
is
correct
for
users.
A
All
right,
so
that
is
it
anything
else
from
from
anyone.
This
will
be.
E
Niche
so
I'm
looking
to
add
kind
of
for
to
help
contributers,
adding
the
dev
container,
and
originally
it
was
going
to
be
a
pr
that
would
include
the
dev
container
debugging
support,
as
well
as
allowing
you
to
run
the
local
end-to-end
tests
within
the
dev
container,
and
I
think,
since
the
change
it
did
require
to
be
a
little
bit
more
large
of
a
rewrite.
So
in
this
case
I
think,
is
it
cool?
B
B
Yeah
also
there's
the
end-to-end
pr
in
the
driver.
B
C
D
Yes,
yeah,
I
just
wanted
to
see
the
do
the
test
pass
and
that
merged
and
then
I'll
add
some
more
integration
tests
and
send
some.
I
think
that's
about
it
for
like
adding
it
to
the
readme.
Are
there
any
other
things?
I
should
look
out
for
obviously
I'll.
Do
the
dot-com,
like
the
ga
stable
for
additional.
A
Okay,
I
think
that's
it
for
this
meeting
I'll
give
you
guys
back.