►
From YouTube: 2023-06-13 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
June
13th
2023
Rook
community
meeting,
let's
jump
on
into
our
milestones
and
we
will
catch
up
with
everything
going
on
for
1.10.
We
still
do
not
have
a
planned
patch
release
for
that.
Nothing,
that's
important
that
we're
going
to
be
putting
out,
so
we
can
move
on
to
1.11..
A
Just
like
the
last
couple
of
community
meetings,
we've
basically
had
a
patch
release
for
the
1.11
branch
go
out
the
same
day
as
the
or
the
day
after
the
community
meeting.
So
this
is
almost
two
weeks
ago,
but
it
was
after
the
last
time
we
met
and
chatted.
So
let's
go
ahead
and
take
a
quick
look
there
at
the
release,
notes
for
1.11.7
and
see
what
all
was
in
there
and
what's
important
to
call
out.
B
A
Alrighty
and
then
with
the
regular
Cadence
here,
we'd
be
looking
to
do
another
patch
release
the
1.11.8
patch
release
later
on
this
week.
So
let's
take
a
look
at
the
1.11
board
and
see:
what's
in
progress,
doesn't
look
like
anything
is
currently
blocking
that
release.
So
that's
a
good
thing:
what
are
we
planning
on
getting
in
there
yep.
B
B
Yeah
one
in
the
review
column
has
been
in
review
for
a
while
I
guess.
We
should
I
think
we're
waiting
for
a
response
from
the
author
on
that
bill.
A
Well,
but
nothing
to
consider
nothing
to
consider
blocking
here.
Yeah
another
area,
yep,
all
right,
so
yeah
back
into
a
Thursday
Cadence
then
so
it
will
be
quite
the
full
two
weeks
for
the
to
discuss
the
batch
release.
Next
time
we
have
a
community
meeting
together,
all
right,
okay,
so
nothing
else
big
to
call
out
for
1.11,
so
we're
getting
closer
and
closer,
though
to
the
1.12
release,
looks
like
we're
under
a
month
now
for
that.
So
that's
where
the
you
know
more
more
of
our
Focus
would
be
going
to
so.
A
We
had
discussed
this
in
the
last
community
meeting
about
kind
of
trying
to
sync
up
with
the
release
of
stuff
so
that
we
have
that
available
before
we
do
our
1.12.
So
it
looks
like
Blaine
I
think
you
were
just
typing
this-
that
this
is
a
bit
of
news
about
Reef
being
delayed.
C
Yeah
they
were
having
troubles
with
the
container
build
portion
of
the
release
they
yeah.
This
F
Community
lost
the
member
who
is
doing
that
work
and
had
to
sort
of.
Oh,
we
develop
some
some
tribal
knowledge,
but
they
did
finally
release
that
RC
yesterday,
I
I
think
I
understand
that
might
affect
the
final
release
by
a
week
to
a
week
and
a
half
I
I,
don't
know
that
we
necessarily
have
to
adjust
for
that.
But.
B
A
So
that
so
that
we
don't
have,
though,
kind
of
specific
Clarity,
though
about
when
the
final,
so
the
RC
is
out
yes,
but
we
don't
then
know
if
the
final
build
will
be
out.
Maybe
we
think
it
would
be
delayed
in
a
similar
time
frame,
but
we
don't
know
for
sure.
Yet
right
is
that
right.
Blame.
C
Yeah,
my
my
understanding
of
their
process
is
that
they
release
an
RC.
Everything
is
like
frozen,
except
for
bug,
fixes
and
based
on
like
feedback
that
they
get
and
testing
that
they
are
doing
they
will
put
in
patches
for
a
final
release.
Potentially
there
could
be
another
RC,
so
I
think
it's
like
until
it's
as
stable
as
they
can
make
it
so
I
mean
in
the
worst
case
it
could
I
guess
be
indefinite,
but
likely
it.
It
would
still
be.
C
A
And
then
so,
let's
say
then
if
it
continues
to
get
if
it's
delayed
to
just
mid-july.
That
is
that
something
here
that
we
would
like
to
hold
the
1.12
release
until
that
happens
in
or
if
so,
if
that's
a
yes,
then
how,
if
it
gets
delayed
further,
would
we
continue
delaying
1.12
or
what's
kind
of
the
threshold
there
for
when
we
just
want
to
proceed,
is
1.12
anyways
first.
B
My
my
view
is
that
we
moved
it
up
to
July
5th
because
we
thought
Reef
would
be
out
in
June
if
it
ends
up
being
later,
though,
I
feel
like
delaying
until
maybe
mid-july,
it
may
make
sense
just
so.
We
can
try
and
release
around
the
same
time
as
Reef
if
it
ends
up
being
end
of
July
or
later
I
feel
like
well,
we'll
still,
let's
still
release
around
mid,
mid
July
or
end
of
July
at
the
latest
for
1.12
I.
C
I
I
agree
with
that.
We
yeah,
barring,
like
our
own
testing
of
the
RC
like
if
things
are
going
well
for
Rook,
with
the
exception
of
issues
that
are
clearly
staff
issues,
then
I
don't
see
any
reason
to
say
we
don't
support
Reef
as
long
as
the
RC
goes
well,.
C
B
It
was,
was
it
the
end
of
March
start
of
April,
something
like
that.
A
I
think
to
avoid
to
work
around
Travis's
PTO
as
well
I
think
Travis.
Do
you
you
have
time
off
like
right
after
the
Fourth
of
July
week?
Is
that
right,
remembering
that
incorrectly
yeah.
B
B
I,
looked
at
the
11.0
release,
it
was
February
27th.
So
what
does
that
mean?
So
it's
four
months
would
be
the
end
of
June.
So
early
July
I'd
still
be
with
around
our
four
month
goal.
C
B
A
Okay,
so
then
that
means
that
not
that
we
should
wait
for
Reef,
but
if
our
C
testing
goes
okay,
then
early
July
still
is
the
the
goal.
B
We
do
have
a
couple
other
features
that
we
really
want
to
get
released,
which
is
qazi
and
dealing
with
node
loss,
so
jiffin
and
Siobhan
working
on
those
but
I
mean
if
those
features
honestly
like
both
needed
more
time
than
maybe
we
bumped
to
the
end
of
July,
especially
if
reef
is
not
going
to
be
delayed.
But
I
don't
think
we
want
to
say
we're
ready
to
delay
that
yet.
A
Okay,
cool
thanks
for
helping
with
the
notes
there
Blaine
all
right
so.
E
A
Think
that's
we
got
that
kind
of
captured
there,
so
let's
go
ahead
and
look
at
the
the
project
board
to
see
what
all
is
there
and
important,
then
from
the
for
from
everything
within
the
Rook
side,
looks
like
we've
got
six
things
in
the
blocking
release.
Category
are
these
all
up
to
date
and
we
feel
we
feel
like
those
are
the
the
must-haves
for
the
release
still.
B
So
the
first
two
are
those
two
features:
I
just
mentioned
that
we'd
really
like
to
get
into
the
release
with
qazi
and
load
loss.
The
other
four
I
just
opened
yesterday,
I
think
just
to
track
the
standard,
bookkeeping
items
for
dealing
with
upgrades
the
upgrade
guide
right,
upgrade
tests,
yep,
and
also
on
that
note.
B
So
after
right,
after
I
opened
these
sheetal,
you
opened
a
couple
of
PRS
thanks
for
jumping
on
those.
Do
you
want
to
introduce
yourself.
D
So
yeah
I
have
been
looking
into
the
project
for
some
time
now
and
they
are
slowly
trying
to
contribute
wherever
I
can
and
previously
to
that.
I
was
working
on
to
the
cluster
project
and
currently
yeah
towards
little
bit
on
roadside.
Only
I'm
focusing
now.
C
B
Another
things
for
412
yeah,
those
are
the
just
the
ones
I've
been
blocking,
I'm,
not
sure
any
other
features
need
to
be
blocking
the
release.
I
think
the
rest
in
the
to-do
column
is
kind
of
things
that
moved
from
previous
release.
That
would
be
nice
to
have
when
we
can
most
some
of
them
need
owners.
C
A
Yep,
so
that's
good,
then
like
as
we're
closing
in
with
the
month
or
so
let
less
than
a
month.
Maybe
if
it's
early
July
that
you
know,
we've
got
these
identified,
at
least
of
the
you
know
the
process
that
we
need
to
get
accomplished
and
the
features
that
are
most
important.
So
that's
that's
definitely
good
to
have
these
here
cool,
okay,
then
anything
else
for
you
can
make
the
same
statement
here
to
Blaine
for
no
plus,
maybe
probably
more
so
actually.
A
All
right
so
I
think
then
Alex.
You
got
anything
else
for
1.12
that
you
wanted
to
mention
or
add
Buddy.
E
A
Right
so
let's
roll
on
into
the
community
topic
section
then
so
yeah
we've
got
some
updates.
It
looks
like
thin
for
the
cube
cuddle
plug-in
being
ported
over
to
go.
E
F
Oh
yes,
so
we
have
all
the
blocking
we
are
sent
and
thanks
everyone
for
doing
the
bug
blessing
and
all
so.
We
will
wait
for
a
day
or
two
more
or
more
bug
blessing.
If
we
get
some
more
issues,
we
will
fix
that.
Otherwise
we
are
planning
to
have
the
news
later
later.
This
week.
F
F
Yeah
yeah,
that's
it.
Currently.
The
release
process
is
very
fast
and
kind
of
Auto
mission,
but
for
the
new
release
with
go
link,
we
we
did
one
time
manual,
release
which
will
take
few
days
from
the
kubernetes
group
project
to
merge
that
new
release,
so
yeah
foreign.
B
A
Yep,
that's
great
yes,
thanks
everybody
for
who
is
bug
bashing
and
getting
that
quality
up
after
that
major
import
effort
and
then
Siobhan
thanks
again
for
for
driving
all
that
and
getting
it
to
a
state.
Now,
where
it'll
be,
you
know
more
maintainable,
more
extendable,
all
that
stuff.
F
A
All
right,
Alex,
your
new
architecture
diagram,
is
in
progress.
E
E
Yeah,
if
you
go
to
the
files
instead
of
the
comments,
we
can
it's
easier
to
see.
Yeah
yeah.
A
E
Well,
I
hope
all
of
them
are
good
well,.
E
If
there's
any
questions
or
it's
a
good
point
to
bring
up
route,
though
for
like
for
Blaine's
Point
like
maybe
to
just
chat
about
tear
right
now,
would
be
that,
like
a
detailed
one
that
you
have
created
a
mock-up
of
I
guess,
maybe
we
should
start
with
that.
E
I'm
amazed
on
what
you
can
do
with
Google
Slides
will
be
interesting
to
Port
it
over
to
draw
IO
but
well
and
as
as
I
wrote
in
a
comment
there
like
I,
think
it
makes
sense
to
just
have
a
second
graph
and
a
second
graph,
a
second
diagram,
to
show
the
more
details
for
you.
If
you
go
to
the
comments
now
generate
instead
of
the
files
at
the
bottom,
there's
a
comment
from
Blaine
somewhere:
where
is
it
there?
We
go
here,
the
Google
Doc
one.
E
Well,
it
worked
yeah
there
we
go
that
we
have
such
a
detailed
one
of
like
the
actual
flow,
as
I
put
it
in
my
comment
that
we
just
add
that
as
a
an
additional
diagram,
basically
of
like
hey,
this
is
the
flow.
It's
like
I,
don't
know
if
it
was
able
to
bring
it
across
in
my
column,
but
I
said
like
that,
so
to
say,
the
one
that
I
create
is
kind
of
like
modest.
E
This
is
these:
are
the
components
involved
and
like
roughly.
This
is
how
everything
kind
of
communicates
or
might
communicate,
and
your
diagram
with
the
flow
that
this
is
like
the
actual.
This
is
how
everything
flows.
Basically
so
I
would
try
recreating
this
one
in
trial,
otherwise
we'll
probably
just
end
up
with
export
as
PNG
in
Google
Slides,
which.
E
C
C
C
Yeah
I
guess
my
thought
is
like
maybe
maybe
we
could
focus
on
like
the
large
architecture
and
then
get
that
merged
and
then
do
like
additional
like.
C
As
well,
because,
like
being
like
okay,
here's
what
we
want
to
communicate
with,
you
know
talking
about
CSI
or
like
I
kind
of
think
of
this.
As
you
know,
what
is
what
is
the
data
path
or
data
fulfillment?
You
know
mechanism
look
like
in
Rook,
which
is
to
me
like
that
is
like
this.
Is
you
know
what
people
kind
of
are
more
likely
to
care
about
like
versus?
Like
here's,
you
know,
here's
the
connection
for
CSI,
like
that's
kind
of
like
a
CSI
diagram.
E
That's
the
thing
where
I'm
like
at
least
a
little
bit
split
with
like
not
necessarily
going
too
deep,
with
these
I
I,
think
or
maybe
as
I.
Try
to
like
put
it
into
a
comment
as
well.
It's
like,
on
the
one
hand,
I
get
that
you
know,
as
you
put
it
it's
too
deep
into
CSI,
which
might
not
necessarily
be
relevant
for
rogue
people,
but
in
the
end
at
least
how
I
kind
of
see
Rook.
To
summary,
more
more,
it's
like
a
we're,
deploying
CSI
like
we
again.
C
E
C
Mean
this
is
something
we
can
take
offline
as
well,
I
think,
possibly
the
intent
of
my
like
comment
and
like
wasn't
I,
don't
think
I
communicated
it
very
well
like
the
CSI
diagrams
that
I
see
there
are
feel
like
they're
somewhere
in
between
too
complicated
and
not
complicated
enough
so
like.
If
we're
going
for
overall
architecture,
then
I
think
just
having
like
you
know
what
we
deploy
as
CSI
deployments
is
good
and
then
like.
C
Seems
like
it's
a
rehash
of
some
CSI
architecture,
diagrams
that
I've
seen
before,
without
without
like
also
going
what
specifically
reconces
CSI
provides.
C
And
that's
I
mean
that's
definitely
open
to
interpretation.
That's
kind
of
this,
the
space
where
I
see
those
I
I
think
probably
just
having
like
hey.
Here's
like
where
the
CSI
pods
are
going
to
live,
based
on
how
Rick
sets
them
up
seems
like
a
good
amount
of
like
overview
compared
to
like
bringing
like
storage
classes
and
everything
into
it
and
EVS
versus
PVCs
and
like
where
API
calls
happen.
Like
that's.
B
B
If
I
worry
about
putting
too
much
detail
in
the
picture,
because
then
nobody
can
maintain
it.
Oh,
except
plane.
A
Well,
yeah
definitely
good
work.
An
effort
from
you
know.
Everybody
involved
in
this
with
you
know:
Blaine,
taking
a
stab
at
a
deeper
or
a
more.
You
know,
descriptive
diagram
from
your
perspective
and
through
Alex
continue
to
drive
the
pr
as
a
whole
and
stuff
so
yeah
thanks
for
both
of
that
guys.
A
Travis
you
want
to
give
us
a
quick
update
on
adopters.md.
This
was
merged
recently.
B
Yeah
so
last
time
we
talked
about
kind
of
marrying
what
was
done
with
crossplay
and
yeah.
It
was
definitely
a
great
pointer,
so
basically
it
a
lot
of
the
wording.
There
is
similar
to
what
cross-plane
does
and
it's
merged
the
I.
What
I
didn't
change?
B
With
this
description,
if
you
want
a
description
or
just
the
end
of
the
list,
if
you're,
if
you
don't
want
a
description,
so
that's
the
The,
Proposal
I
posted
in
the
announcements
channel
of
slack
and
I
was
going
to
Tweet
about
it
today
too.
If
anybody
has
thoughts
on
how
to
get
people
to
I,
guess
add
themselves
to
that
as
part
of
it
any
wording
around
the
Tweet,
you
think,
might
work
just
curious.
A
I
think
it's
also
an
ongoing
thing
to
Travis
that
you
know
one
tweet
will
maybe
attract
a
few
people,
but
then
you
know
doing
it
again
next
month
and
then.
A
Basis
is
probably
important,
but
then
also
making
a
plug
for
it
in
the
communicate
other
communication
channels
that
we
have
too,
like,
for
instance,
the
maintainer
track
talks
at
kubecon.
You
can
have
a
slide
at
the
end
of
you
know
about
like
we're
already
talking
about
ways
to
get
involved
and
stuff
like
that
and
having
a
you
know,
a
easy
link
to
or
a
reminder
to
join
the
adopters
file.
There
is
another
time
that
you
get
a
more
eyeballs
from
an
audience
on
it
as
well.
So
that's
another
idea.
A
Time,
yeah
exactly
exactly
so:
it'll
be
an
overtime
thing
for
sure.
Cool
cool,
awesome,
good
update
on
this
and
then
depending
about
PR's,
are
failing
whenever
they
touch
the
the
go
mod
in
some
files.
B
Yeah
so
Shaban
had
a
couple
fixes
for
the
bot
today
and
maybe
it's
working
now,
I
haven't
seen
my
email
for
the
last
couple
hours.
F
I
created
a
couple
of
years
that
that
helps
that
dependent,
build
dependent
bought
the
CI
to
pass,
but
even
after
that,
it
is
not.
It
is
not
committing
the
new
changes.
A
A
It
yeah
go
ahead
and
reopen
them
I'm
on
a
non-signed
in
account,
no
account
and.
A
All
right,
cool
yeah
thanks
for
the
continued
effort
on
that
then
to
try
to
work
through
those
issues.
A
F
A
A
Okay,
all
right
so
yeah
I
do
still
have
this
action
item
for
setting
up
slack
and
extended.
You
know
I
think
that
that's
still
not
really
necessarily
like
top
burning
burning
top
of
the
pile
for
me,
but
you
know
sometime
in
the
in
the
nearest
Future
that
I
will
get
to
that.