►
Description
Kubernetes Storage Special-Interest-Group (SIG) Object Bucket API Review Meeting - 28 January 2021
Meeting Notes/Agenda: -
Find out more about the Storage SIG here: https://github.com/kubernetes/community/tree/master/sig-storage
B
Okay,
thank
you.
So
our
cap
review
deadline
is
coming
up
very
shortly.
It's
next
friday
and
we've
been
working
hard
to
make
sure
that
everything
is
in
place
for
that
review.
B
So
the
first
thing
that
we
need
to
get
in
place
is
the
actual
cap
itself,
I'll
start
with
that,
and
then
we'll
go
into
the
other
developments
that
have
been
happening.
So
I'm
going
to
open
up
the
cap
kubernetes
enhancements
all
right,
so
here
jeff
made
a
pull
request
recently.
C
B
B
If
I
change
my
name
yeah,
I
mean
he
got
your
name
wrong:
okay,
okay,
so
so
this
this
skip
currently
after
this
update,
reflects
the
developments
we've
made
in
terms
of
the
api
changes
in
terms
of
the
changes
to
the
spec,
the
grpc
spec,
and
also
the
any
other
technical
changes
that
we
made
throughout
the
course
of
the
last
two
months
or
so
after
the
initial
cap
was
approved.
B
So
the
grpc
change
for
protocol
is
here.
Yes,
the
protocol
structure,
just
an
explanation
of
protocol
and
also
we
were
adding
parameters.
B
B
B
Yeah
yeah
makes
sense
yeah,
so
we
will
mark
it
as
implementable
and
send
it
through
a
round
of
review.
So
if
and
should
this
be
merged
before
asking
for
api
review
or
is
just
the
pull
request
enough.
A
B
Understood
and
and
this
time
we'll
have
to
so
so
I'm
trying
to
understand
the
process.
If
I
understand
correctly
this
time
before
the
fifth
we
should,
we
should
inform
an
api.
B
Okay,
okay,
understood,
so
is
it
possible
for
us
to
ping
an
api
reviewer
right
away,
since
we
have
we.
A
B
Yeah,
okay,
okay
yeah!
Maybe
she
need
and
sing
who
should
we
reach
out
to
her?
Does
shrini
all
already
know
that
srini.
A
So
you
can
there
is,
there
is
an
api
review.
There
is
a
label.
What
is
that
label?
They
need
api
review
or
something
at
that
label.
So
we
normally.
I
think
a
lot
of
our
caps
are
reviewed
by
tim,
so
you
can
try
him.
I
don't
know
if
he
has
the
bandwidth
to
review
this,
but
I
think
a
lot
of
our
caps
are
reviewed
by
him.
A
E
D
Yep
make
sense
yeah,
but
we
need
to
so
what
happens
to
the
cap.
That
is
already
emerged
right.
The
main
cap,
no.
A
But
if
it's
a,
if
it's
a
well,
he
can
see
that
right.
So
he
can
actually
expand
and
see
the
whole
thing
so
yeah.
So
I
think
he
will
have
to
review
it
before
this
one
becomes
implementable
right,
the
previous
one.
Obviously
it's
not
inventable.
B
B
Okay,
okay
yeah,
I
believe
jeff
is
busy
today
with
a
bunch
of
meetings
but
yeah
we'll
get
it
updated
as
soon
as
possible.
I
don't
think
we
can
add
the
label
just
as
it
is,
but
that's:
okay,
we'll
first
make
the
changes.
Let's.
B
Yeah,
do
you
want
me
to
send
a
link
to
this.
B
Okay
sounds
good,
okay,
so
so
that
is
on
track
and
you
know
we're
ready
to
respond
to
any
comments
that
come
up
and-
and
I
I
encourage
everyone
in
the
community
to
go
ahead
review.
It.
B
Jeff
is
so
jeff
is
very
old
school
he's
he's
still.
Gate
is
new
to
jeff,
so
so
he.
A
A
B
No,
that's!
No!
So
yes,
that's
the
thing
he's
new
last
time.
Actually
I
helped
him
push
his
comments.
He
had
a
different
id
called
yard.
Turkey,
not
jeff
man.
He
has
another
id.
Maybe.
B
A
F
He's
an
org,
not
not
a
user,
I
mean
he
it's
an
organization.
D
B
Yeah
I
mean
like
the
last
time
it
was
from
ya.
Turkey
yataki
is
a
part
of
you
know,
has
signed
the
cla
and,
and
we
made
the
pull
request
from
ya
turkey
from
one
arc
to
another:
okay
yeah.
So
it's
okay,
so
I'll
I'll
work
with
jeff
and
make
sure
that
this
is
done
properly.
Last
time
I
had
to
do
the
same
thing.
Is
it's
yeah?
It's
a
few
steps.
It's
not
a
problem!
Yeah!
It's
a
simple
thing.
I
think
he
missed
it.
That's
all!
B
Okay!
So,
coming
back
to
this.
B
All
right
so
current
priorities
we're
still
on
track,
we're
still
it's
still
the
same,
but
we're
moving
forward
for
sure
we
want
to
do
the
demo.
I
noticed
that
there
are
some
new
people
here
today,
so
I
want
to
explain
what
the
demo
is
about,
so
we
we
set
a
milestone
for
ourselves
that
once
the
cap
was
merged,
once
the
initial
enhancement
proposal
was
merged,
that
we
would
the
first
milestone
would
be
a
demo
of
the
most
basic
use
case
of
cozy
working
in
its
entirety.
B
End-To-End,
the
idea
behind
that
milestone
was
it
would
it
would
make
us
work
on
all
the
different
components,
the
project
and
also
the
integration,
in
addition
to
just
saying
we'll
do
a
demo
of
the
basic
functionality
working.
We
also
said
that
whatever
we
show
in
the
demo
is
going
to
be
a
code
that
has
been
tested
that
has
been
documented
and
you
know
as
close
to
production
quality
as
possible.
Those
are
the
words
we
used
again,
the
idea
being.
B
So
to
that
end,
I'll
quickly,
first
go
over
what
the
basic
use
cases
and
the
basic
use
case
is
because
you
will
create
a
bucket
in
response
to
user,
requesting
it
it'll
grant
access
to
that
bucket
for
a
workload
and
then
provision
this
bucket
for
a
part
and
the
part
can
use
it
and
write
and
read
data
from
it.
B
So
this
is
what
we
said.
The
demo
would
be
in
terms
of
the
progress
of
this
I'm
happy
to
say
we
have
we've.
We've
tested
this
integrated
and
tested
this,
and
for
with
the
sample
driver
that
you've
written,
which
is
a
min
io.
As
the
object
storage
provider.
We
have.
B
We
have
completed
the
development
stage,
so
we
have
those
three
use
cases
working
well.
Actually
there
is
a
new
new
development
that
happened
after
we
got
it
working.
We
had
to
make
a
change
to
the
grpc
spec
and
once
that
change
is
made,
we'll
update
the
code
to
start
using
the
new
spec.
B
But
I
would
say:
that's
that's
a
quick
step
and-
and
we
don't
expect
it
to
take
much
time
so
in
terms
of
development,
you
could
say
that
that
step
is
still
left,
but
even
without
it
we
have
things
working.
B
The
next
thing
is
obviously
deployment
should
not
be
something
only
a
few
of
us
know
or
some
select
people
who
have
actually
done
it
know,
but
deployment
should
work
out
of
the
box
and
everyone
should
be
able
to
start
testing
it
out.
So
again,
I'm
happy
to
say
that
we
have
that
working,
and
these
are
the
four
commands
on
the
right
hand,
side
that
that
you
need
to
issue
to
deploy
the
entire
project.
B
So
you
register
the
crds
by
before
that
all
of
the
commands
are
have
the
flag
dash
k,
so
cube,
ctl
create
dash
k,
k
stands
for
customize,
so
you
can
provide
a
customized
template
as
a
as
a
github
vanity
url
like
this.
B
So
if
there
is
a
customization
or
enamel
at
the
root
of
this
project,
then
it
would,
it
will
go
and
pull
that
and-
and
it
will,
you
know,
register
and
install
those,
the
customization
resources
that
are
present
there,
and
so
using
these
four
commands,
you
can
deploy
the
whole
project
with
the
sample
driver,
we're
working
on
a
deployment
dock
that
will
explain
how,
to
you
run
your
own
driver
and
different
architectures
of
running
it
building
in
different
name
spaces
and
all
that
for
the
basic
use
case,
though,
full
stack
deployment
is
in
place
for
the
demo,
people
can
try
it
out
in
terms
of
testing.
B
We
have
a
decent
amount
of
unit
tests
and
we
have
ca
in
place.
End-To-End
testing.
We
found
that
there
is
a
little
bit
of
waiting
involved
in
in
having
to
provision
resources
to
run
the
end-to-end
tests
and
also
there's
some
extra
development
effort
required,
which
we
think
might
be.
B
There
is
more
development
work
required
there
than
in
actually
developing
cozy,
as
it
is
right
now.
So
you
know
it
seemed
like
the
best
way
to
move
forward
here
was
to
manually.
Do
the
end-to-end,
testing
and
and
slowly
work
on
e3
tests
as
if
it's
another
development
milestone,
because
it
is,
it
is
a
quite
a
large
effort.
It's
not
it's,
not
a
quick
thing.
B
That's
going
to
involve
multiple
projects
coming
together.
So
final
thing
is
documentation,
so
we
have
a
spec
guide
in
place.
It's
the
second
point
on
the
right
in
terms
of
getting
started.
We
have
good
getting
started
guides
for
some
of
the
projects
and
janis
here
is
working
on
adding
that
for
the
rest
of
the
project.
So,
on
the
spec
repo,
we
have
a
getting
started
guide,
which
explains
what
the
project
does
a
quick
developer
guide
some
references
and
also
a
link
to
our
documentation.
B
Our
documentation
is
housed
under
the
api
repo.
Before
I
go
into
the
show
you
this
in
the
api
repo
again,
we
have
kind
of
a
readme
landing
page
kind
of
read
me,
which
again
has
information
of
what
the
project
does
and
a
quick.
I
think
we
should
remove
this
right
because
it's
still
alpha.
B
Yeah,
so
we
will
remove
that
because
in
alpha
we
can't
enforce
that
and
it
doesn't
make
sense
so
anyway.
So
again,
these
are
the
two
projects
that
have
the
getting
started
guide.
I
would
say
this
kind
of
read
me
and
we
have
a
other
larger
documentation
effort
all
housed
under
docs
folder
under
api.
B
It
goes
into
why
another
standard
and
a
bunch
of
useful
links,
like
user
guide
deployment
guide
how
to
write
a
driver.
I
believe
how
to
write
a
driver
is
going
to
be
one
of
the
most
important
pieces
of
documentation
that
we'll
need
in
the
near
term
and
then
the
next
one,
how
to
write,
make
your
application
cosy
compatible
is
going
to
be
another
key
documentation
in
the
long
term.
B
F
E
Writing
on
the
yeah
yeah,
but
yeah,
it's
I
think
the
coming
week.
It
would
be
my
first
contribution.
I
think,
we're
looking
forward
to
it.
B
Okay,
so
he
he
was
working
on
well
fixing
changing
this
to
the
word
api
and
also
the
deployment
guide.
I
think
he
has
a
pull
request
out
there,
but
he
said
he
was
working
on
it
further
yeah.
B
Yeah
so
so
yeah,
he
he's
gonna
talk
about
he's,
gonna
we're
gonna,
have
a
dock
explaining.
What
are
the
different
ways
to
deploy?
Tedious
is
an
is
a
sys
admin.
He
has
been
working
with
customize
and
deploying
deploying
it
in
various
scenarios
at
red
hat
and
now
at
his
new
startup.
B
So
you
know
he.
He
understands
the
different
scenarios
and
different
kind
of
in
the
most
important
things
that
that
needs
to
be
covered
from
admins
perspective.
So
so
he's
he's
helping
with
this
right
now
yeah.
So
that's
that's
where
we
are
in
terms
of
the
project,
any
questions
so
far.
E
So
sid,
I
have
a
question
so
for
the
commands,
with
the
first,
the
customized
commands
that
install
the
crds
in
the
beginning.
So
I
don't
know
if
it's
a
stupid
question
for
a
customized
noob,
but
it
asked
me
for
a
username
password
for
the
for
github.
When
I
execute
these
commands.
B
B
E
I
I
did
try
the
commands
from
cloning,
the
repo
and
applying
it
and
it
works,
but
yeah,
but
out
of
the
box.
It
asks
for
username
password,
interesting.
B
Probably
because
I
have
logged
in
in
my
github
environment,
I
never
saw
this.
This
is
a
public
repository.
E
A
D
B
Using
https
here,
I
think,
by
default
it
might
use
git
github.com
the
ssh.
B
However,
I
think
this
is
something
that
we
need
to
address,
though
adoption
has
to
be
super
simple,
where
people
can
just
just
you
know,
copy
and
paste,
and
it
should
just
work,
and
I
don't
believe
it's
a
lot
of
effort
to
get
there
from
where
we
are
right
now
so
yeah
yeah
we'll
try
different
combinations
and
see
how
to
get
this
working
yeah
all
right
so
so
these
are
the
main
things
I
wanted
to
discuss
today
and
I
wanted
to
keep
it
focused
on
the
on
the
cap.
B
I
don't
have
any
specific
technical
discussions
planned.
However,
if
you
have
anything
you
want
to
bring
up,
we
can
we
can
we
can.
We
can
do
that
right
now.
F
E
So
for
the
end-to-end
testing,
what
frameworks
are
you
thinking
of?
Because
it's
it's
a
big
problem?
The.
B
The
end-to-end
yeah,
so
shrini
can
talk
a
little
bit
more
about
it.
I
haven't
dived
into
the
details,
but
he
has
so
I'll.
F
B
D
Right
now
we
are
just
following
what
csi
is
doing
right.
I
mean
we
already
have
a
framework
in
place
in
communities,
kkk
report,
so.
E
What's
the
end
test,
pardon
and
and
test
what
was.
C
E
So
I
was
looking
at
the
kuba
test
because
I
prefer
I
mean
it
resonated
a
bit
more
with
me
to
have
it
in
you
know
in
in
python.
I
don't
know
I
like
the
semantics
more
of
this
project,
so
I'm
posting
it
there,
but
it
seems
that
they're
not
maintaining
very
well.
So
I
posted
on
the
on
the
channel
but
yeah,
so
it
it
assumes
that
you
have
already
a
cuba
ctl
context.
So
basically
you
need
to
bring
up
like
mini,
cube
and
install
all
these
things
so
yeah.
E
So
this
is
the
only
framework
that
I
tried
with,
but
with
a
for
end-to-end
but
yeah.
B
B
B
Okay,
so
I
want
to
address
two
things
right
now.
One
is
blaine
here,
hi
blaine,
so
you
asked:
what
is
the
behavior's
behavior
if
set
dash
o
is
run
without
an
arc
following
it?
Is
that
right.
G
I
I
found
that
the
documentation
actually
or
I
just
opened
up
bash
and
typed
it
in
it.
It
actually
displays
the
options
that
are
set.
I
just
didn't
know
if
that
was
like
a
typo
and
was
intended
to
set
an
option
or
not.
B
It's
supposed
to
be
eax.
This
is
what
we
wanted
to
have
exit
if
this
narrower
and
also
print
out
what
you're
doing
yeah.
This
is
something
I
wrote
on
this
on
this
slide.
This
is
not
something
that
we
had
as
a
script
before,
but
yeah.
B
Yeah,
of
course,
all
right
so
going
to
the
next
thing
so
shane
it
looks
like
tim
hawkins
responded,
I'm
very
impressed.
I
know
he's
very
busy.
I
just
I'm
impressed
because
he
found
the
time
so
quickly.
B
H
A
A
I
think
you
have
everything:
oh
did
you
you
can.
Maybe
I
think
you
should
probably
also
mention
those
repos
yeah
got
it
for
I
don't
know
if
you
want
to
show
him
your
slides,
maybe
that's
easier
for
him
to
get
an
overview.
If
you
have.
B
A
B
Yeah
yeah,
I
worked
with
them.
You
know
you
know
it
was
just
the
two
of
us
when
we
started
doing
the
cloud
provider
work
and
back
then
he
was
not
this
quick,
okay,
so
yeah
anyways.
I
think
it's
good
that
you
know
we're
doing
this
now,
because
we
have
information
in
this
spec.
In
the
read
me,
we
talk
about
what
it
is
yeah
yeah
earlier.
He
wouldn't
have
been
able
to
make
sense
of
it.
B
So
it's
good,
yeah
and
and
yeah
and,
like
you
said,
he'd,
be
able
to
look
at
the
whole
project
with
the
whole
file
right.
That
shouldn't
be
a
problem
actually
yeah.
A
He
should
know
how
to
read
the
whole
file
yeah
you
just
if
you
just
do
a
view.
You'll
see
the
whole
thing,
but
the
only
thing
then
you
cannot,
I
mean
I
guess
the
only
downside
is
because
it's
already
merged
yeah.
He.
C
A
H
A
D
B
Yeah,
this
is
important.
I
think
this
can
be
a
great
troll
account
in
the
future.
B
Anyway,
so
all
right,
so
so
it's
good
api
review
is
already
starting.
We
have
to
now
work
towards
the
demo
before
that
we
have
to
have
the
spec
pr
merged
so
shang.
We
have
made
the
updates
based
on
sad's
comments.
B
Yeah
it'll
be
good
if
you
leave
a
review
as
well:
yeah,
I'm
sure,
yeah
and,
and
once
this
is
merged,
we'll
go
make
the
changes
to
the
other
repositories
to
pull
this
version
and
right
after
that,
we
should
be
ready
for
the
demo.
B
Yeah
so
yeah
we
can.
We
can
end
the
meeting
early
today
because
I
wanted
to
keep
it
focused
on
the
cap.
On
monday,
though,
we
have
a
bunch
of
technical
issues
that
we
want
to
bring
up
and
we'll
continue
from
there.
C
D
Are
we
missing
anything
from
the
the
new
process
for
the
project
management,
yeah.
A
You
should
because
I
think
they
actually
respond
very
quickly.
You
basically
did
I
tell
you
how
to
do
it,
just
to
go
to
that
production,
and
this
channel
and
pin
those
three
people
saying:
hey
here's
the
cap.
We
are
trying
to
go
after.
Can
you
review
it?
They
are
very
quick,
so.
B
A
You
just
need
to
add
that
section.
B
Okay,
so
shin
did
you
get
all
of
it:
yeah
yeah,
okay.
So
this
is
not
something
that
you
set
on
the
pull
request.
That's
what
she's
saying
right,
I'm
saying
yeah!
That's
right!
I
mean.
A
B
Yeah
yeah:
let's
bring
jeff
as
well
to
update
this
and
right
after
we're
done
with
that,
let's
bring
the
slack
channel.
So
so
we
go
to
the
slack
channel
ping.
Someone
correct
me.