►
Description
Kubernetes Storage Special-Interest-Group (SIG) Object Bucket API Standup Meeting - 04 January 2021
Meeting Notes/Agenda: -
Find out more about the Storage SIG here: https://github.com/kubernetes/community/tree/master/sig-storage
A
B
Started
all
right.
Thank
you.
Let's
get
started.
Okay,
so
hi
sweeney
welcome
back
happy
new
year
happy
new
year
thanks!
Thank
you.
Thank
you!
So
all
right,
so
let's
go
over
everywhere
and
what
what
is
what
is
in
progress
and
what
needs
to
be
done
so
srini.
B
So
last
we
talked.
Were
you
still
are
the
proud
or
ss
changes
in.
C
A
Did
not
work
much
this
this
couple
of
weeks,
so
it's.
A
Yeah
yeah,
so
I
should
be
able
to
finish
that
off
the
product
search
changes,
so
there
are
like
a
few
pr's
that
are
outstanding
right
now.
For
me,.
B
Yeah,
so
what
were
you,
what
were
you
working
on
before
we
before
we
left
for
vacation?
Obviously,.
A
Yeah,
so
one
is
the
delete
handling
so
for
the
both
the
the
on.
E
A
So
and
then
the
other
thing
is
the
proud
sh
needs
to
be
finished
now
that
the
pr
for
ci
is
merged.
We
also
needed
to
finish
the
cloud.
E
A
File
one
person
manjunad
has
submitted
a
pr,
but
that's
not
what
I
expect.
So
I
reviewed
that
and
asked
him
to
make
changes.
We
still
need
to
do
the
same
cloud
yaml
file
for
the
for
the
other
projects
to
for
the
provisioner,
sidecar
and
I'll
I'll.
I
I
need
to
work
on
that
this
week,
so
two
pr's
that
I
can
push
today.
One
is
for
the
pro
and
the
other
one
is
for
the
delete,
but
the
other,
the
claudia
per
I'll
work
in
this
week.
So,
okay.
B
So
so
so
it
looks
like
this
person
wants
to
help.
Could
you
could
you
also,
you
know,
help
him
get
this
pr
right,
yeah.
B
Okay,
great
awesome,
all
right
so
right
now,
you're
focusing
on
so
now
that
in
the
central
controller,
which
listens
to
bucket
requests
and
bucket
access,
request
events
and
creates
the
bucket
and
bucket
access
objects,
you
said
you've
completed
the
work
on
or
you've
completed,
the
first
milestone
for
the
deletes
right.
A
A
A
B
E
A
I
think
he's
talking
about
update
streaming.
No,
when
I
I
create
a
br
with
the
finalizer
and
then
I
do
have
a
delete
on
the
br.
The
call
just
finishes
and
I
don't
see
the
br.
I
cannot
query
the
vr
anymore
no
update,
even
that
is
coming
with
my
big
client.
B
A
B
Right:
that's
that's
what
we're
really
testing
here
right,
right,
yeah,
so
yeah!
Let's
do
that!
Let's
we
shouldn't
have
to
test
the
controller
logic
here.
I
think
we
should
just
test
the
update
logic.
A
The
ete
test
for
that
anyways
so
yeah,
because
that
is
that
is
an
integration
point.
It
is
not
a
unit
testing,
correct,
yeah,
that's
what
I
realized,
but
it
just
didn't
fail.
I
was
trying
to
see
why
it
is
getting
deleted,
even
though
there
is
a
finalizer,
so
it
it.
Probably,
this
call
directly
goes
and
deletes
without
the
the
intermediate
api
server,
somebody
catching
the
finalizer.
So
that's
I
don't
know
exactly
how
it
works,
but
I
was
trying
to
figure
that
out.
Okay.
B
Yeah,
let
me
know
if
you
want
to
do
a
like
a
zoom
session.
We
can
go
over.
It
sounds
good
yeah,
all
right,
so
jeff
did
you.
Were
you
raising
a
concern?
Sorry,
if
I
spoke
over
you.
E
B
Then
so
we
don't
so
the
thing
is,
we
are
doing
unit
testing
here,
so
the
kubernetes
api
server
is
not
involved,
we're
using
a
fake
client
and
a
fake.
B
You
know
this
for
unit
testing,
so
the
second
thing
is
what,
if
I
understand
correctly,
what
srini
is
saying:
we're
not
trying
to
delete
the
object,
we're
listening
for
an
update
event,
but
then,
when
we,
when
we
go
through
the
wiring
and
try
and
understand
where
the
update
event
went,
we
found
that
the
object
itself
was
not
there
that
we
updated
so
srini
tried
to
put
a
finalizer
in
there,
hoping
that
that
would
prevent
the
object
from
going
away.
But
that's
not
what
happened
exactly.
B
A
fader
client
is
just
simply,
you
know
a
data
structure
like
a
map
holding
a
key
to
any
any
kubernetes
resource.
B
Yep,
okay,
okay,
so
that's
good
to
know
so
so
this
is,
is,
is
this
merged,
so
it's
in
progress.
A
B
Okay,
alright!
So
yes,
okay,
now
I'd
like
to
catch
up
with
rob,
hey
rob,
how's
it
going.
B
Good
to
hear
that,
so,
could
you
remind
me
what
you
were
working
on
before
we
went
on
holidays.
D
So
that
so
we
before
we
before
we
broke
for
holiday,
we
were
moving
all
of
the
sidecar
code
to
the
official
repo.
So.
F
D
I
talked
with-
I
mentioned
that
to
sajin
that
it
needs
to
be
reworked
to
to
be
in
the
main,
build
pipeline
in
the
in
the
sidecar,
as
opposed
to
in
its
own
subpac
subdirectory
right
with
its
own
set
of
dependencies
and
all
that
stuff.
This
thing
made.
D
G
Where
this
provisioner
will
live
like
I,
I
wouldn't.
D
It's
in
the
same
repo,
but
I
would
just
I
would
pull
everything
out
of
his
subdirectory
and
make
it
a
top
level.
You
know
a
subdirectory
under
command
for
the
command
bits
and
the
patent.
You
know
the
to
move
the
components
into
a
package
sample
provisioner
or
something
for
anything
that
it
would
need
in
the
package
directory,
and
I
think
that
should
be
it
and
then
once
you've
done
that
and
added
the
either
added
build
targets
or
added
sample
provisioner
as
a
thing
to
build
in
the
make
file.
B
D
B
Yeah
yeah,
that's
true:
we
want
to
design
it
like
this
project
like
just
like
how
kubernetes
itself
is
so.
Kubernetes
has
multiple
binaries
and
the
different
binaries
are
not.
You
know
like
cubelet
and
queue
controller
manager.
All
the
different
binaries
are
put
under
the
command
package
or
command
folder
cmd
folder.
B
Well,
I'll
I'll
have
a
call
with
you
and
I'll
show
you
I'll
walk
with
you
through
it.
B
Yeah
no
problem
so
sergeant
you
were
working
on
this
right.
This
is
the
last
thing
you
were
working
on
or
were
you
working
on
past?
You
know.
G
Okay-
and
I
made
some
progress
there
and
it
worked
fine,
but
later
rob
informed
that
I
will
have
to
do
it
with
the
ktc
paper.
So
I
I
was
currently
doing
the
testing
for
that,
I'm
not
sure.
G
Okay,
could
you
I
I
earlier
I
tested
with
our
depreciated
deprecated
repo
and
later
I
talked
to
rob
and
he
told
me
to
use
kubernetes
repo,
like
it's
the
updated
one.
B
Oh,
I
see
I
see
so
you
were
integrating
with
the
unofficial
repos
and
since
we've
stopped
using
that
rob
asked
you
to
start
using
this
one,
correct
yeah
and
when
you
say
integration
you
mean
you
are
testing
the
full
workflow
with
this
driver.
Correct
yeah,
understood,
understood,
okay,
sounds
good
yeah.
Let's
have
a
call
later
and
let's
go
over
both
of
those
things.
B
H
So
before
the
holiday
started,
I
finished
up
moving
all
the
csi
adapter
code
over
to
the
official
repost,
and
now
I'm
just
working
on
making
some
of
the
changes
that
we
discussed
prior.
Let
me
open
up
my
notes.
H
I
think
the
main
idea
was
just
to
add
the
finalizers
onto
the
bucket
access.
That
was
one
item
right
and
the
other
thing
was
for.
H
I
mean
like
so
we
discussed
how
like
we
wanted
the
secrets
to
be
structured
in
different
folders
right
right
right
right.
I
see
what
you
mean.
B
B
Got
it?
Okay,
let
me
let
me
assign
this
to
crush.
B
B
F
B
C
B
B
Okay,
it's
fine,
then
yeah
yeah,
so
we
got
yeah
yeah.
B
Perfect,
I
see
yeah
and
did
we
did
we
capture
it?
Okay,
we
had
it
here.
We
had
the
description
here.
D
B
Okay,
so
maybe
on
yeah,
this
is
good,
maybe
on
on
thursday,
we'll
we'll
bring
this
up
again
and
make
sure
everyone
in
the
community
also
understands.
Did
we
bring
it
up?
Last
time
last
before
we
broke
for
holidays,
I
don't
think
so.
D
B
Yeah
yeah,
I
think
I
mentioned
that
I'll
bring
it
up
this
time
or
something
so
yeah,
let's
I'll
bring
this
up
on
thursday
yeah.
This
is.
This
is
an
important
part
of
how
you
know
the
whole
life
cycle
of
the
different
objects
work.
So
so
I
think
everyone
should
participate
in
this
and
share
their
thoughts
as
well.
So
yeah,
I
don't.
I
don't
I'm
not
prepared
to
bring
this
up
today
and
I
don't
think
we
have
the
time
even.
B
The
so
we've
gone
over
control
we've
gone
over
side
car
we've
gone
over
the
csi
adapter,
the
api
and
spec.
There
are
no
changes
needed
now,
so
repository
wise,
I
think
we're
good.
There
is
one
other
effort
that
you
know
I've
been
bringing
up
and
it's
very
important,
which
is
a
documentation
right
now.
B
As
someone
who
is
newly
coming
into
the
project,
we've
definitely
improved
in
the
onboarding
experience,
but
if
someone
were
to
come
into
the
project
wanting
to
just
try
it
out
see
what
progress
has
been
made
or
see
how
they
should
start
writing
a
driver
for
cosy
there
is.
There
is
not
enough
information
for
them
so,
along
with
all
the
development
effort
that
is
going
on,
I
think
it's
really
important
that
we
start
focusing
on
documentation.
B
So
there
was
one
person,
summers
matthews
who
was
helping
out.
I
encourage
others
here
as
well,
who
can
spend
some
time
and
you
know,
help
everyone
who
wants
to
start
trying
out
cozy
by
contributing
to
our
documentation
here.
That
would
be
highly
appreciated.
B
B
Issues,
that's
it
from
me.
That's
all
this
is
this
is
so
one
more
thing
that.
B
So
I
looked
through
the
pier,
so
so
the
last
view
that
was
made
by
nicolas
I
reviewed,
and
I
believe
I
merged
it.
I
don't
think
I
have
any
open
ones.
Okay,
so
nicholas
sorry,
I
should
have
also
asked
you.
So
what
are
you
working
on
like
right?
After
the
the
changes
to
the
customized
templates?
B
What
is
the
next
thing
you're
focusing
on?
I
believe,
you're
already
looking
at
something.
C
Nothing
right
now.
I've
been
off
for
like
two
whole
weeks
and
I
need
to
catch
up
again
and
see
how
things
I
also
see
at
what
my
primary
job
duties
are
yeah,
so
I
can
get
back
to
cozy
as
well
understood.
Okay,.
B
Yeah,
okay,
yeah,
as
I
think
I
think
this
is
a
good
start.
This
was
you
know
I
wanted
today
to
be
a
catch-up
session.
I
think
I
have
a
good
idea
of
where
we
are
at
this
point.
So
again
the
the
main
goal
we
are
going
towards.
I
didn't
prepare
slides
for
today,
but
the
main
goal
we're
going
towards
is
our
demo,
where
we
have
a
proper
working
driver
and
the
various
components
integrated
properly.
B
B
Time
all
right,
so,
let's
meet
again
on
thursday,
we'll
talk
about
finalizers
and
we'll
also
discuss
the.