►
From YouTube: 2023-02-07 Rook Community Meeting
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
recording
has
started,
and
this
is
the
February
7th
2023
Rook
community
meeting.
Let's
hop
on
into
upcoming
milestones
and
releases,
we
do
not
have
anything
planned
for
1.9,
so
we'll
go
ahead
and
skip
over
that
I.
Believe
then
1.10.11
I
think
we
were
maybe
talking
about
this
in
the
last
community
meeting.
B
Yeah
I
don't
know
if
this,
if
there's
anything
in
there
to
discuss
the
surgeon,
it
would
just
be
the
release
on
Cadence
like
we're
over
we're
close
to
three
weeks
already,
but
the,
and
we
would
have
right
I,
think
we
discussed
last
time
today,
potentially
releasing.
B
But
the
thing
is:
we've
got
some
CI
issues
going
on
right
now,
where
there's
there's
an
update
to
the
GitHub
actions,
that's
breaking
our
osds
on
PVCs,
so
a
bunch
of
our
Canary
tests
are
failing.
B
Soturu
and
Siobhan
have
been
looking
into
those
issues
and
hoping
we
can
get
it
resolved
in
the
next
couple
days.
But
it's
already
been.
You
know
the
last
week
they've
been
looking
at
it
so
anyway,
we
just
don't
know
if
the
some
of
the
CI
is
broken.
B
A
Travis
is
the
point:
is
that
update
to
the
GitHub
actions?
Is
that
something?
That's
like
you
know
within
the
get
up,
GitHub
actions
internals
or
is
that
like,
if
any
of,
like
the
you
know,
like
modules,
that
you
have
that
we
that
we
load
and
reuse
in
the
in
the
workflow
or
like?
Is
it
something
out
of
our
control,
or
you
know
a
version
that
we
consciously
are
updating.
B
B
A
B
A
For
1.10
either
so
if
we
put
it
in
both
I
would
say
you
know
and
then
can
I.
Oh
wait.
Maybe
on
the
board
itself,
yeah
right
here
there
we
go
yeah.
A
When
we
look
at
the
board,
what's
what's
going
on
exactly
okay,
so
good
update
on
that
and
then
want
to
flow
right
on
into
1.11
progress
in
which
you
know
we
are
working
towards
getting
the
first
release
candidate
beta
out,
February,
15th
and
then
a
week
later,
getting
the
full
1.11
out
on
the
21st.
So
two
weeks
basically
left
on
that.
A
Fair
enough
all
right,
what
else
do
we
want
to
bring
up
then
for
1.11,
since
that
is
the
next.
A
Bigger
release
going
out
any
any
things
that
we
need
to
block
things
on
or
get
some
updates
on.
Yeah.
B
Maybe
I'll
just
go
over
the
other
things
in
the
block
here
at
least
call
them
just
for
what's
in
progress
here,
I,
don't
think
any
of
the
others
are
real
risk.
Besides
the
one
we
talked
about
already,
but
there's
like
we
need
to
make
sure
we
update
our
Min
version
because
we
support
the
last
six
versions
of
kubernetes.
B
B
The
shabbon
was
working
on
that
we've
got
Seth
exporter,
I,
think
a
meeting
or
two
ago
we
talked
or
just
brought
that
up,
but
yep,
it's
a
new
stuff
demon
that
we
need
to
to
run
so
that
that
PR
is
getting
ready
for
merge.
Now
it's
really
just
the
CI
isn't
passing
because
of
the
known
issues
and
then
the
last
one
there
is
a
supporting
mirroring
across
clusters
with
overlapping
networks.
B
So
Santosh
has
basically
has
a
prototype
working
end
to
end.
So
we
just
need
you're
just
cleaning
up
that
PR
and
should
be
ready
to
go
soon
and
otherwise
I
mean
there's
still
some
things
that
will
certainly
come
into
the
release
and
anything
that's
blocking
the
release.
I
just
want
to
make
sure
that
this
blocking
of
these
columns.
So
if
there's
others,
anybody
would
like
to
propose
or
bring
up,
but
let's
just
you
know,
be
great
to
get
those
in
that
column.
A
Yeah,
Blaine
or
Alex
any
suggestions
from
you
all
on
anything
else
that
is
critical
for
the
release.
A
Is
there
I?
Is
there
recent
progress
on
on
this
oldie
but
goodie
one
for
early
four
digit
one.
B
Scroll
at
the
bottom
I'm
trying
to
remember
what
the
latest
was.
We.
B
Oh,
it
was
assigned
to
shabbat,
Shabbat
was
going
to
start
looking
at
it.
That
was
three
weeks
ago.
That's
right
and
we've
got
a
potential
design
up
a
couple
comments
proposed,
oh
here,
but
it
yeah.
The
priority
keeps
we
need
to
help
the
priority
to
get
to.
It
really
is
what
it
comes
down
to.
Jerome
keeps
having
CIA
or
other
issues
come
up
to
look
into
got
it
so
yeah,
not
great.
A
All
right
all
righty,
then
so,
if
that's
everything
for
1.11,
then
we'll
continue
like
the
this.
The
CI
stuff
seems
to
be
the
most
pressing
issue,
because
you
know
we'll
be
able
to
really
be
able
to
release
without
that
and
then
some
other
features
and
work.
That's
going
on
to
be
included
in
release,
and
hopefully
we
can
Target
next
week
for
the
release
candidate,
the
Beta
release.
We
get
some
some
testing
and
some
big
time
on
that
one
and
get
in
two
weeks
out
the
the
1.11
release.
A
B
Yep,
just
last
night
got
an
email
that
the
submission
for
the
maintainer
track
was
accepted,
so
yep
we're
good
to
go.
No
big,
surprise
there,
but.
A
Any
news
on
like
the
booth
as
well
or.
B
So
the
oh
I
signed
up
for
the
the
kiosk
for
a
half
day
and
then
also
there's
PR
support
that
we
signed
up
for
we
can
get
I
get
some
announcements
out
or
other
other
info
for
people
attending
did
not
sign
up
for
the.
B
B
A
B
B
A
Then
really
exciting
update.
Did
anybody
else
here
on
the
call
get
a
an
individual
talk
accepted.
B
E
E
A
Yeah,
it's
a
really
good
point
too
Anthony.
That
is,
that
is
totally
that
that's
the
way
that
was
done
in
Barcelona,
and
that
was
really
really
cool,
I
think
because
it
was
kind
of
like
a
like
a
co-located
event,
zero
day,
event,
sort
of
style
there.
The
only
thing
I
didn't
like
about
cephlacon
at
in
Barcelona
is
that
I
on
the
cab
ride
over
to
the
venue
to
go
to
Silicon
I
lost
my
cell
phone
in
the
cab,
and
so
it
was
like
first
day
in
Barcelona
with
no
no
cell
phone
I
was
like.
D
E
A
C
A
Exciting,
that's
gonna
be
awesome.
All
right
now,
I
didn't
catch.
It,
though,
are
the
like
cfps
open
for
that
or
talks
already
is.
E
C
E
Submit
something
of
remember
correct,
oh
yeah,
here,
oh
no
well!
Well,.
E
E
D
B
D
D
D
Would
wish
that
they
had
that
that
had
been
rescheduled
in.
A
I'm
gonna
change.
My
screen
share
here
to
my
other
Chrome
profile.
A
There
we
go
so
you
should
be
back
at
the
agenda
dock
here
and
then
here,
I'm
an
editor,
so
I
can
go
ahead
and
start
doing
stuff
then
we'll
get.
The
cfp
is
open
with
submissions
there
we
go
and
what's
date,
what's
the
deadline
here
deadline
deadline
deadline
closes
on
okay,
so
five
days
left,
it
looks
like
yeah.
E
I'll
just
look
into
submitting
something
and
well
as
programming
course
being
a
sponsor
as
well.
There
will
try
to
spare
at
The
Rook
laugh
itself
column
as
well.
I.
E
A
Right
so
Travis
do
you
want
to
give
us
an
update
then
on
the
data
on
kubernetes
on
the
dock.
B
Yeah
sounds
good,
so
yesterday
I
had
a
call
with
someone
from
Daton
kubernetes
Bart.
This
is.
B
And
it
was
just
yeah
a
really
good
intro
to
what
are
we?
What
can
we
accomplish?
What
you
know,
what
are
our
goals
with
the
data
on
kubernetes
community
and
so
I
mean
to
recap
we're
officially
joining
as
a
community
sponsor
doesn't
cost
us
anything
but
yeah.
It's
just
good
Community
coverage
so
it'll
help.
B
So
their
goal
really
is
to
bring
the
community
together
help
people
find
the
right
people
to
talk
to
talk
about
use
cases,
discuss
challenges,
I
mean
everything
related
to
storage.
They
want
to
facilitate
Community
discussion;
they
don't
want
to
get
caught
up
with
products
or
product
pitches
like
data
yeah.
They
they
don't
want
to
do
that
they
just
want.
What
does
the
community
need
for
storage
and
they'll
facilitate
that
they
will
be
having
a
meet
up
in
Amsterdam
Tuesday
evening
of
that
so
yeah?
A
B
Said
it'd
be
pretty
casual
and
just
an
opportunity
to
work
could
have
a
brief
presentation
and
but
just
facilitate
discussion
more
than
anything,
and
that
would
be
work
would
be
one
of
many
people
who
might
just
talk
for
or
discuss
for
a
few
minutes
and
introduce
ourselves
yeah.
They
said,
like
5,
30
p.m,
on
that
Tuesday
is
an
evening
event
and
otherwise
I
mean
they
they're.
They
want
to
set
up
like
monthly
calls
for
people
interested
in
Rook.
It's
you
know
at
first
I
was
wondering.
B
Well,
is
this
kind
of
like
what
we
should
be
doing
in
the
community
meeting,
but
I
think
it
makes
a
lot
of
sense
to
just
you
know,
they're
going
to
help
facilitate
it
and
the
whole
point
of
what
they
want.
Is:
let's
discuss
scenarios
around
data
and
help
answer
people's
questions
about
what
they're
trying
to
do
in
our
community
meeting?
You
know
we're
talking
about
project
specific
features
and
things
I.
Think
it's
just
more
detailed
than
what
Community
discussion
is
the
goal
of
that.
B
So
so
and
I
think
this
really
is
a
gap
we've
had
in
the
work
project
like
having
a
place
for
people
to
really
get
it
together
and
discuss
what
they're
trying
to
do
so
anyway.
I
think
it's
all
good
I
think
you
know
they
they're
happy
to
have
multiple
people,
maintainers
come
and
participate
and
non-maintainers
just
users
who
who
know
how
to
use
rook
and
have
solved
problems,
so
they
can
get
real
world
people
talking
out
about
how
they're
using
it
yeah.
So
it's
just
just
all
goodness,
I
think
yeah.
A
B
A
A
I
could
also
imagine
there
being
like
a
you
know,
happy
hour,
like
after
sort
of
thing
for
everyone,
that's
gone
to
be
getting
together
in
casual
setting
too
so
I.
Imagine
there
could
be
a
conflict
here,
true
yeah
casual
stuff
yep.
So
this
sounds
like
something
then
like
when
we
have
the
details
about
it
and
stuff
to
promote,
to
you
know
the
Rook
user
base
to
the
community
to
let
them
know
where
it
is
when
it
is
all
that
sort
of
stuff.
B
Yep
so
I'll
be
reaching
out
to
people
to
see
who
all
is
interested
in
getting
into
those
discussions
with
data
on
kubernetes
community
books,
because
I
I
can't
do
that.
All
myself.
It's
we
need
lots
of
community
people
to
members
to
participate
there
and
maintenance.
So
yep
I'll
share
more
details
when
that's
what
that's
up
or
when.
A
Sounds
good
Travis
thanks
for
following
up
on
that
and
getting
us.
You
know
to
be
integrated
into
that
community
all
right.
So
that's
all
of
the
issues
that
were
part
of
the
agenda
docs.
Does
anybody
have
further
issues
that
they
want
to
bring
up
or
discuss
now,
foreign.
A
Well,
if
not,
then
we
can
go
ahead
and
adjourn
for
the
week
here
and
then
on.
The
next
community
meeting
is
when
the
release
is
scheduled,
so
we'll
definitely
be
active
on
slack
and
GitHub.
In
the
meantime,
until
the
next
community
meeting
working
towards
the
1.11
release,
all
right
thanks,
everybody
all
right.
Thank.