►
Description
Meeting of Kubernetes Storage Special-Interest-Group (SIG) Object Bucket API Review - 24 September 2020
Meeting Notes/Agenda: -
Find out more about the Storage SIG here: https://github.com/kubernetes/community/tree/master/sig-storage
A
B
So,
on
monday
we
talked
about
what
the
next
steps
are,
so
the
next
major
milestone
is
getting
to
alpha
on
the
way
to
alpha
we
will.
We
will
get
to
a
point
where
the
product
is
just
good
enough
for
people
to
start
trying
out.
I've
just
called
that
as
mvp
before
alpha.
B
While
mvp
is
in
progress,
we
will
have
to
work
on
the
api,
get
it
reviewed,
get
it
accepted
and
whatever
changes
that
are
brought
back
as
feedback
from
the
review
will
have
to
factor
into
the
mvp
development.
So
those
two
will
go
hand
in
hand,
but
even
before
that
we
can,
we
can
do
a
very
simple
demo,
the
demo
I
wanted
it
to
I.
I
wanted
to
be
a
a
development
milestone
rather
than
a
demo.
B
What
I
mean
by
that
is
when,
when,
when
we
reach
a
certain
stage,
that
is,
that
is
when
we
do
the
demo,
the
the
code
and
the
the
quality
of
code
and
whatever
features
we've
written.
I
I
want
it
to
be.
Essentially
you
know
production
quality
rather
than
just
trying
to
prototype
the
features
required
to
show
the
demo.
B
So
we're
not
setting
a
hard
deadline
for
the
demo,
we're
rather
setting
it
as
a
as
that
point,
when
we
reach
this
simple
set
of
functionality
in
terms
of
development
so
and
and
the
reason
I've
chosen,
the
demo
this
way
is
so
that
all
the
different
components
in
in
the
architecture
that
we've
come
up
with
we'll
have
to
integrate
and
and
work
for
this
demo
to
work.
B
So
we
were
estimating
something
like
three
weeks,
maybe
four
weeks
to
get
there
and
in
terms
of
what's
needed
to
be
developed
for
this,
we
needed
a
set
of
shared
components.
Obviously,
the
api
needed
to
be
defined,
and
we've
built
a
shared
controller
library
for
the
bucket
star
apis.
B
So
this
is
a
set
of
tasks
that
are
required
for
making
that
happen.
That
demo,
as
of
monday,
we
had
completed
the
tasks
that
are
shown
in
green,
so
we
had.
We
had
a
part
of
the
system
working
and
across
all
three
components,
and
as
of
today,
we
made
even
more
progress.
We
made
a
bug
fix
in
our
shared
control
library.
We
have
krish
who's
working
on
the
node
adapter
has
made
progress
in
terms
of
putting
the
buckets
into
the
pods.
B
B
It
need
not
be
a
vendor's
official
provisioner,
but
it
needs
to
be
good
enough,
so
that
people
can
anyone
can
start
trying
it
out
and
testing
it
out
in
their
own
environment
with
their
own
credentials
say
if
it's
amazon
s3,
they
should
be
able
to
just
plug
in
their
credentials,
and
you
know
be
able
to
create
buckets
and
delete
buckets
using
this
provisioner.
B
So
I'm
I'm
using
this
meeting
as
a
platform
to
ask
anyone
on
this
call
if,
if
you'd
be
available
to
contribute
to
this
project,
you're
you're
welcome,
please
reach
out
to
me
on
slack
or
on
through
the
google
groups
and
and
I'll
be
able
to
have
I'll,
be
happy
to
onboard
you.
B
So
as
we
as
we
start
building
this
create
bucket
workflow.
B
B
B
Anonymous
access
mode,
which
is
a
set
of
default
acls
on
the
bucket
itself,
does
not
associate
with
any
particular
user
and
a
bucket
context,
which
is
a
catch-all
for
every
other
configuration
that
goes
into
a
bucket
or
creation
of
a
bucket.
So
I
we
were
looking
through.
All
the
options
supported
in
the
different
cloud
providers,
so
region
is
is
is
a
common
field
that
is
supported
by
all
object,
search,
vendors.
B
Now
so
far,
we've
been
thinking
of
passing
region
as
a
field
in
the
bucket
context
now
similar
to
region.
There
are
some
fields
that
are
that
are
actually
common,
like
object,
lock
in
aws
s3
has
an
equivalent
in
gcs
called
event
base
hold.
Both
of
them
hold
the
object
for
a
particular
amount
of
time
before
it
can
be
deleted.
B
So
it
seems
like
there
are
certain
options
like
these
that
are
that
are
common
across
different
cloud
providers.
There
are
different
object,
storage
members,
so.
C
This
is
true
for
cloud
providers,
but
but
part
of
the
target
of
this
is
on-prem
object-
storage
providers-
it's
not
clear
to
me
that
region
necessarily
is
portable
to
on-prem.
B
C
B
So
so
the
first
question
I
have
is:
we
need
to
come
up
with
some
name
so
for
these.
B
For
these,
for
these
options
that
go
into
the
create
bucket
call
one,
I
want
to
figure
out
if,
if
we
should
make
them
kubernetes
like
if
we
should
start
having
a
list
of
known
annotations
or
known
keys
for
these
and
have
provisioners
support
these
options
or
not,
for
instance,
or
should
we
just
leave
it
to
the
provisionals
to
define
their
own
keys
for
whatever
they
support
and
and
as
far
as
we're
concerned,
it's
all
opaque.
B
D
B
E
So
the
way
that,
on
the
csi
side,
we
try
to
make
these
decisions
is
if
a
kubernetes
component
needs
to
be
aware
of
a
specific
field,
then
we
pull
it
out
into
a
first
class
field,
otherwise
we'll
leave
it
as
an
opaque
parameter.
B
So
yeah
we
don't
so
let
so
an
opaque
parameter
would
be
a
provisional
defined
thing
like
that.
Right,
like
what's
shown
right:
okay,
okay,
that
makes
sense
yeah.
So
that
was
that
was
the
main
question
that
that
I
had
in
mind
other
than
this.
Actually.
E
And
sorry,
I
just
want
to
clarify
when
I
mean
opaque
parameter,
I
mean
there's
like
the
set
of
parameters
that
are
passed
in
from
storage
class,
on
create
volume
right
where
they're
not
officially
defined,
keys
and
values.
It's
just
invisible
to
kubernetes
and
csi.
Only
the
provisioner
and
the
user,
who
sets
them
are
aware
of
what
the
keys
mean
right,
visible,
but
not
interpreted
right
right.
B
That's
the
word
I
was
looking
for
interpreted
okay,
so
so
so
as
we
go
through
this
actually,
so
I
wanted
to
kind
of
ask
jeff,
oh
so,
actually
before
I
do
that
on
the
cap
front,
I
believe
there
is
a
there's.
A
deadline
of
next
this
friday
or
next
friday,
for
the
freeze
feature
freeze
is
that
right.
B
Okay-
and
I
I
noticed
there
were
some
some
comments,
your
left
side,
we
can
address
them
today,
right
away.
F
Okay
sounds
good
yeah,
so
give
us
doing
I'm
real,
tough
time
kind
of
answering
your
questions,
and
I
know
we
still
have
questions
from
guy
or
comments
on
cap
and
appreciate
the
review
and
I'm
in
the
process
of
responding
to
a
lot
of
your
point
sought,
including
some
thumbs
up
on
things
that
we
missed
perfect.
Thank
you.
F
B
B
B
Cap
and
and
and
try
and
address
the
open
questions
in
the
interest
of
you
know
speeding
up
the
the
review
process.
I
want
to
start
looking
at
the
comments
that
are
left
and
what
hasn't
been
addressed
so
far.
B
So
jeff
there
was
a
question
yesterday
right
that
you
brought
up
someone
messaged
you
directly
on
slack.
Could
you
maybe
explain
that
we'll
start
with
that,
one.
G
F
Sorry,
I
was
muted,
yes,
is
kyle,
batter
or
baiter
on
this
call.
Let
me
just
look
quick.
F
No,
I
don't
see
him
okay,
so
he
he
messaged
me
reading
the
kep
there's
a
section
toward
the
end
called
dynamic
provisioning
and
inside
there
there's
a
use
case
andrew
which
I
believe
we
tried
to
capture
from
you.
So
let
me
let
me
find
the
line
in
the
cap
sid.
Can
you
go
on
to
something
else's
and
I'll
get
the
line
so
that
we
can
be
on
the
same
page?
Oh.
F
Great
yeah
and
it's
the
second
bullet.
I
think
no
third
bullet
sorry.
So
it's
the
third
bullet,
so
kyle
brought
was
looking
at
that
third
bullet,
and
this
is
what
he
wrote.
He
said.
Even
if
there's
no
conflict,
I
know
a
user's
access,
key
name
and
a
bucket
they've
created
and
or
no
they
have
access,
including
buckets
I
create
and
enable
for
cross
sharing.
F
I
can
now
get
their
secret
key,
so
that
was
his
comment
to
me
and
I
I
passed
that
on
to
the
folks
doing
the
coding-
and
I
I
have
to
admit
I
haven't
given
it
any
deep
thought,
though
I
just
wanted
to
let
sid
know
about
it,
so
I
guess
said
you're
opening
it
up
for
discussion
and
yeah.
I
can
repeat
that
comment
if
I
would
got
garbled
up
at
all.
B
C
C
B
Question
yeah
makes
sense.
I
think
it
answers
that
I
we,
the
answer
is,
it
is
the
issues
is,
I
would,
I
would
say
something
like
this
is
this
is
the
design
of
the
system
and
it's
it's
not
really
an
issue
he's
concerned.
B
Okay,
I'm
not
gonna
be
able
to
find
it
here.
Okay,
so
you
asked
missing
bucket
access
the
cluster
scope,
part
of
bar-
and
this.
B
B
B
So
so
today,
I
wanted
to
make
sure
that
people
get
a
chance
to
go
through
the
cap
before
the
freeze
next
week
and
and
also
leave
your
comments
reviews.
So
so
we
can.
We
can
prioritize
this
and
move
forward
to
the
next
step.
It
looks
like
the
comments
right
now
from
saad
are
fairly
straightforward,
andrew
others,
you
know,
andrew
especially
you
you've
been
a
very
active
part
of
this
development.
B
Your
review
would
be
much
appreciated,
so
if
you
can
take
some
time
to
go
through
the
cap
and
leave
your
feedback,
that
would
be
great
and
ben,
oh
and
ben
as
well.
Yes
for
everyone
really,
I
I
called
out
andrew
specifically,
because
he
hasn't
been
in
the
meetings
lately,
and
I
wanted
to
make
sure
that
you
know,
because
all
these
weeks
have
been
calling
on
everyone.
I
want
to
make
sure
he's
also
on
board.
B
Yeah,
so
yes,
we
can.
We
can
address
these
comments
quickly.
We
are
prioritizing,
you
know,
addressing
comments
on
the
cab
and
getting
it
to
a
position
where
you
know
it
looks
good
and
can
be
merged
so
yeah.
So
please
take
some
time
to
review
it.
That's
all
from
my
side
today.
H
Can
you
hear
me
yeah
yeah?
This
has
been
I.
I
do
look
forward
to
reviewing
this.
It's
just
that.
I
I
don't
see
that
happening
between
now
and
the
deadline
like
for
me.
It's
probably
going
to
be
later
I'll,
get
to
do
a
really
deep
review
and
as
part
of
that
I'll
like
implement
it
and
have
a
you
know,
working
implementation
to
play
with
it's
hard
for
me
to
do
a
review.
If
I'm
not
like
also
writing
code
yeah.
So
I
I
apologize.
B
Okay,
in
that
case,
we'll
move
forward,
and-
and
you
know,
if,
if
you
feel
like
anything,
needs
to
be
changed,
we
can
always
address
it
after.
E
Yeah,
the
good
thing
is
that
this
is
provisional
and
we're
talking
about
a
proof
of
concept
implementation
here
and
before
we
go
to
alpha
we're
going
to
have
a
more
thorough
api
review
and
and
design
reviews.
So.
F
Right
and
we'll
you
know
in
the
implementation
like
is
expected,
we
will
likely
find
that
we
have
to
tweak
things
here
and
there
and
and
so
yeah
getting
ben's
review
later
in
the
cycle
is
better
than
not
at
all.
So
we'll
definitely
appreciate
it
when
it
comes
in.
B
Unless
someone
else
wants
to
bring
up
something,
we
can,
we
can
finish
the
meeting
now
we'll
be
go
back
and
work
on
the
cap.
F
F
E
I
think,
from
my
perspective,
that's
fine.
I
I'll
leave
that
decision
up
to
you
as
the
leads
of
this.
Whatever
cadence
works
best
for
you,
let
me
know
I
can
adjust
the
calendar,
invite
for
you.
F
Okay,
we
can.
We
can
talk
about
it
amongst
ourselves
too.
If
anyone
wants
to
chime
in
with
their
opinion
on
it,
especially
the
regulars
I'm
seeing
ben
david
aaron
sod,
shing,
jawa,
joey.
Sorry,
you
guys,
I
see
your
names
constantly
in
the
guy
in
the
participants
list.
So
if
you
have
an
opinion
on
it,
go
ahead
and
chime
in.