►
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
A
A
B
I
have
a
list,
but
I
think
we
can
start
start
looking
at
the
projects.
First,
okay:
let's
do.
A
A
And
this
was
all
the
this
is
all
the
external
dependencies
for
moving
the
cloud
private
provider
out
of
tree.
Let's
take
a
quick
look
at
that.
B
Yeah
for
this
issue,
we
still
have
a
working
item
to
to
move
the
external
provider
out
of
tree.
B
Yeah
the
the
c
actually
like
the
csi
java
patch.
Actually
it's
already
it's
already
done
yeah
and
says:
let's
do
a
remaining
work
item
for
moving
the
credential
provider
out
of
three,
and
I
think
we
will
try
to
to
make
it
in
in
the
1.20.
A
And
look
at
that.
I
last
moved
it
to
1.19,
that's
february
yeah
in
february
yeah.
A
So
I
guess
this
is
another
one
that
needs
to
move
to
1.20
and
I'm
surprised.
Nobody
has
bugged
us
yeah.
A
B
Yeah
perfect
just
mentioned,
I
think
confirmation
is
that
he
will
put
some
time
to
to
implement
it
in
1.20.
A
B
B
B
A
B
For
the
csi
java
migration-
actually
it's
already
better
in
1.19
I
mean
for
disk.
Oh,
I
think
I
need
to
update
it.
Well,
this
actually
it's
already
better
in
for
disk,
actually,
it's
better
in
1.19
and
for
fire.
It's
still
alpha
in
1.19,
so
yeah
we're
going
to
plan
to
make
it
better
in
the
1.20
and
some
work
need
to
do.
The
main
work
is
the
the
ci
test.
I
mean
automatic
cr
test
that
needs
to
be
computed
for
the
fire
in
1.20
yeah.
B
Actually,
it's
not
a
critical
feature
of
bug,
it's
not
a
critical
feature,
I
think
so
yeah.
We
may
not
sure
whether
there's
a
volunteer
to
do
that.
A
A
B
Same
yeah,
we
can
make
it
as
the
mr.
A
Yeah
this
seems
reasonable,
okay,
open,
I
think,
there's
already
yeah.
There
is
a
pr.
This
is
the
beer.
B
The
formerly
is
actually
a
summary,
and
there
this
one
is
the
detailed
one.
A
A
Yeah,
I
know
that
initially
done
some
work
and
probably
pigfet
too
it'd
be
good
to
get
an
update
on
that.
So
I
guess
we'll
leave
it
where
it
is.
B
Has
the
external
credential
provider
implementation.
B
A
Okay,
so
let's
I
see
yeah
so
this.
A
If
it
does
this,
or
should
we
move,
remove
the
milestone
or
move
it
to
1.2,
there
is
no
1.21
to
add
it
to
right.
Maybe
we
did
we
did
this
minutes
ago.
A
Let's
leave
it
here
for
now,
we'll
we'll
track
it
over
time
and
see
how
it
goes.
Yeah,
that's
funny,
vm
list
this
issue,
pickfa
opened.
A
A
A
A
All
right,
let's,
let's
ask.
A
A
B
This
one
pamphlet
is
working
on
such
I
think
it
should
be
milestone.
Yeah.
A
A
So
we
were
just
looking
at
a
bunch
of
the
issues
that
had
that
were
on
the
project
board
and
also
ones
that
had
older
milestones
and
we
were
updating
things
and
it
looks
like
this
is
in
progress
and.
C
A
So
do
you
think
we
should
add
it
to
the
1.20
milestone.
A
C
No,
the
event
doesn't
detail
the
errors
yeah,
so
we
want
to
add
the
add,
the
router
errors
to
to
the
service
to
the
to
the
node
events.
C
I
think
someone
has
started
a
work
on
that
some
time
ago,
but
I
didn't
finish
that
work.
Let's
see
so,
we
may
need
a
line
lender
to
to
a
different.
A
C
C
A
Yeah,
let's
see
is
that.
C
Heart,
it
should
work.
A
C
And
another
feature
we
want
to
add
is:
is
support
multiple
standard
balancer
in
the
same
clutter,
I
I
didn't
create
an
issue
yet
we
we
need
to
prepare
a
design
proposal
and
we
also
want
designed
to
be
part
of
a
class.
A
C
B
Yeah,
I
think
the
summer
already
discussed
and
I
just
pasted
the
one
link
about
the
volume
volume
issue
and
yeah
it's
about
the
dangling
volume
mechanism
and
for
csi
driver.
It
does
not
exist.
So
I'm
planning
to
protect
that
code
for
the
entry
already
conjured.
The
code
is
in
tree.
I
will
put
that
code
to
the
csi
driver
and
also
do
some
implementation
for
our
csi
java,
mainly
for
audio
disk
driver.
C
B
We
should
target
fixing
for
1.2
guys,
I
think,
even
for
this
issue,
we
can
my
stone
yet
for
the
1.20.
C
Yeah
so
for
external
credential
provider,
I
think
we
may
also
either
enter
in
this
relate,
but
then
it
depends
on
the
plugin
itself
to
be
ready
right.
So
we
are
not
sure
whether
then,
would
be
ready
in
this
release
cycle.
A
So,
let's
I
guess
we'll
I'll
check
we'll
check
in
with.
C
Actually,
looking
for
him
folks
working
on
this
feature,.
B
B
C
A
I
would
love
to
go
through
it.
Is
it
the
general
under
the
kubernetes
sigs
cloud
provider,.
A
C
C
Okay,
so
if
you
think
something
I'm
missing
here,
we
could
add
them.
C
Yeah
just
search
everything
on
the
on
the
top
right.
C
One
thing
so
for
the
pi
I
I
mentioned
you
earlier
to
update
the
traffic.
Guys
is,
actually
they
are
not
modded
yet
so
could
you
have
online?
So
actually,
the
main
concern
from
a
team
is
that
some
club
providers,
specific
changes,
may
be
considered
as
features.
C
So
I
didn't
think
those
these
kinds
of
changes
are
unreasonable
to
terrific,
but
actually
it
is
required
for
ecas.
So,
for
example,
some
custom.
You
never
knew
features
from
new
api
version,
but
the
cloud
provider
is
here
in
all
the
api
version
so
when,
when
they
type
in
cloud
provider
would
be
broken.
C
You
actually
it
would
help
a
lot
if
we
could
accelerate
the
other
three
cloud
provider.
So
it's
just
the
tman.
A
Independence,
so
it's
tim's
comments
as
I
read
this,
I'm
imagining
something
a
little
more
explicit.
C
B
Actually,
we
we
already
did
the
nfl
support
for
the
identifier
and
blob,
and
recently
we
renamed
the
process
csi
java
to
props
inside
driver,
which
means
that
it
not
only
supported
broad
fields.
Functionality
also
supports
the
nfs
and
also
there's
some
community
work
to
make
the
to
support
nfs
on
windows
yeah,
it's
it's
actually
there's
already
a
pcr
and
I'm
also
reviewing
it
and
trying
it.
B
And
finally,
we
would
support
the
bob
rob
csi
driver
on
windows
use
using
nfs.
C
Is
amps?
It's
definitely
no.
B
C
I
mean
is
the
afs
afsg
now.
B
Actually
for
the
broadway
ledger,
files
are
still
in
preview
and
I
think
it's
it's
like
a
public
review,
but
still
need
to
register
by
the
customs
themselves.
B
Okay,
so
yeah,
I
want
to
j
and
we
will
also
see
our
future
in
the
future.
B
So
that's
my
side
for
the
for
the
for
the
props
fields-
and
I
did
this
because
I
got
updates
and
also
well,
I'm
also
working
on
some
other
in
the
other
csi
projects
like
the
smb,
like
the
nfx
csi
driver
yeah,
I'm
also
working
on
sets
yeah.
A
B
Currently,
there's
a
plan
that
we
will
move
all
the
e3
drivers
to
out
of
three,
not
only
the
cloud
provider
like
like.
I
did
this
kind
of
fire,
but
also
other
built-in
drivers
like
an
effects.
As
you
know
that
says
already
an
fs
driver
built-in
driver
in
kubernetes,
and
we
were
going
to
move
it
move
it
out
of
three.
So
I
I'm
asked
to
spend
some
effort
on
that.
B
I
think
I
need
to
make
it
just
to
become
a
maintainer
of
that
project
first
and
in
the
future.
Let's
see
what
we
can
do
like,
for
example,
for
the
nfs
support.
I
think
we
need
to
support
on
windows
2,
and
I
think
we
can
put
some
efforts
on
that
and
also
make
it
work
on
azure
yeah
first,
so
those
kind
of
projects
are
really
upstream
and
some
some
are
like,
for
example,
for
the
smb
and
the
nfs.
Most
users
are
not
value
users.
A
I
think
that'll
be
those
will
be
great
additions
for
sure
where,
where
are
you
tracking
that
work
or
is
there
some
place?
Well.
B
A
B
This
is
the
smb
system
java
and
for
the
smb.
Actually
it's
already
so
the
beta.
Now
I
just
enable
all
the
tests,
like
the
sanity
test,
integrating
test
end-to-end
tests
yeah
it
works.
It
also
works
on
windows.
So
I
also
add
the
windows
and
you
can
test
by
writing
the
azure
resources
and
for
the
nfs
driver,
yes
country,
it's
their
only
simple
test,
like
only
blue
test,
so
I'm
adding
some
I'm
now
adding
some
other
tests,
like
the
send
test
and
engine
test
to
dnfs
yeah.