►
From YouTube: 2021-09-21 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
september
21st
2021
rook
community
meeting,
and
so
we
can
dive
on
into
our
milestone.
Checkups
and
we've
got
a
1.6.10
scheduled
for
later
this
week,
along
with
another
patch
for
1.7,
which
will
be
1.7.4.
A
A
Right
any
highlights
there
for
pressing
things
to
get
out
in
1.6.10
or
is
more
more
regular,
routine.
B
A
The
solid
done
column
too,
by
the
way,
93
items
and
then
done
column
there
for
all
of
1.6.
That's
pretty
that's
pretty
nice.
A
Yeah,
that's
right
so
1.7.4,
then,
on
the
same
day,
on
thursday,
typically,
there
looks
like
it
has
more
things
potentially
waiting
to
get
in
still
and
make
it.
B
Well
and
those,
I
think
nothing
is
really
in
the
blocking
release
there.
So
those
some
of
those
pr's
are
kind
of
bigger
things
in
progress,
so
we'll
see
if
any
of
those
actually
make
it
into
the
the
thursday
release.
A
B
B
Yeah,
it's
a
just
a
really
well
wait
before
you
do
that
real
quick!
Actually,
that's
right!
I'm
trying
to
remember!
We
don't
need
it
in
1.7.
I
don't
think,
but
the
same
time,
if
it's
almost
ready
since
it's
an
additive
feature,
I
think
we
could
get
it
in
now
if
it's
pretty
soon
just
to
get
early
feedback
instead
of
waiting
all
the
way
until
december,
where
we
get
it
out
in
1.8.
B
C
Definitely
the
only
issue
with
that
is,
I
think,
as
you
said,
it's
as
you
saw
it's
an
enormous
pr
which
has
which
requires
rebase
now,
and
I
think,
once
we
rebase
and
then
eventually
merge,
then
the
back
port
will
be
even
harder
because
it's
going
to
be
a
ton
tons
of
complex
too,
not
sure
if
it
can
make
it
yeah
yeah.
B
A
B
A
C
B
C
C
Think
of
I
think
there
is
also
I
have
one
pr
to
fix
the
ci
failure,
which
we
don't
see
in
one
seven
yet,
but
I
I
think
I'd
like
to
have
it
in
one
seven
anyways
we
have
a
flappy
rgw
multi-site,
so
I
just
added
it
yeah
yeah.
It
did
this
one.
C
A
All
right,
then,
I
guess
we
can
go
ahead
with
those
items
identified
and
knowing
what
we
want
to
get
in
there.
For
the
thursday
release.
We
can
kind
of
take
a
look
at
progress
on
1.8,
which,
as
a
reminder,
we're
looking
for
the
release
being
scheduled
for
around
the
first
week
of
december
to
start
cutting
cutting
releases,
release
branches,
get
the
beta
out
there
get
feedback
and
target
december
8th
for
an
actual
release.
B
A
A
Of
stuff
either,
but
I
replied
to
the
survey
and
signed
up
cool
all
right,
some
big
1.8
stuff.
Any
any
risks
to
call
out
here
or
things
are
locked
on
or
anything
like
that.
B
Yeah,
I
don't
know
if
there's
a
lot
to
talk
about,
I
mean
in
previous
meetings.
We
pointed
out
that,
while
we're
removing
nautilus
support,
we're
changing
our
minimum
kubernetes
version
to
1.16.,
it
will
be
supported,
so
we
can
get
rid
of
the
v1
beta1
crds.
That's
the
main
motivation
for
that
update.
B
I
mean
1.15
is
pretty
old
at
this
point,
so
I
think
we've
given
people
lots
of
time
for
that
and
then
the
flex
driver
being
removed
is
the
other
big
one
and
the
tool
is
still
in
progress
as
we
got
a
demo
less
last
meeting
so
jared.
If
you
ever
need
a
recording
to
watch,
you
can
see
the
demo
on
the
flex
tool,
migration
to
csi,
oh
nice
and
yep.
So
that's
in
progress
still
did
you.
A
A
B
A
Okay,
any
other
items
of
note,
then,
besides
those
those
big
ones,.
C
Yeah,
I'm
not
sure
if
cozy
is
going
to
make
it,
we
should
probably
open
one
nine
already
to
move
some
of
this
stuff
out.
C
Yeah,
I
think
jeff
and
told
me
he's
gonna
follow
up
on
it
next
week
has
some
of
the
design
has
changed?
I
think
so,
I'm
not
sure.
So
I
guess
next
week
we
will
know
a
bit
more,
but
I'm
not
really
expecting
this
to
land
in
one
eight
anyways.
A
In
the
cycle
for
1.8
yep
progress
is
being
made,
though
all
right,
so
we
can
then
I
think,
move
along
to
the
community
topics
section
and
we,
I
know,
we've
made
a
lot
of
progress
over
the
last
months.
Let's
say
on
getting
rid
of
our
dependency
on
jenkins.
We've
got
some
releases
that
have
run
without
that
that
behemoth
as
well
too
travis
from
your
perspective,
are
we
we
about
there.
B
Yeah,
so
we've
got
the
github
actions
working
in
the
1.6
branch
from
a
month
ago,
and
so
our
latest
1.6
1.7
branches
are
all
in
actions.
The
new
nfs
and
cassandra
repos
are
all
running
on
their
reactions
and
the
release.
Almost
two
weeks
ago
already
173
was
from
those
branches.
It's
all
working.
I
don't
see
any
reason
at
this
point
to
keep
jenkins
running.
B
A
A
The
background
you
know
watching
prs
and
spinning
up,
you
know,
builds
and
stuff
on
its
own,
but
it's
just
not
doing
anything
or
is
it
you
know
not
even
connected
to
or
watching
updates
on
repos
anymore.
B
Let's
see
they
shouldn't
be
building
anymore,
because
the
there's
no
more
jenkins
file
in
master
or
1.7.
C
C
C
A
Is
there
is
there
any
conflict
or
anything
with
like
in
1.6
the
chicken
chicken
file
is
still
there,
you
merged
fixed
in
1.6,
does
jenkins,
try
to
run
and
then
push
pub,
build
and
publish
artifacts
in
addition
to
the
github
actions.
Also,
is
there
a
conflict
there.
B
A
B
A
A
Time
to
gracefully
thank
it
for
all
its
hard
work
and
shut
her
down.
B
A
A
B
A
Yeah,
multiple
years
of
of
the
work
there
jenkins-
you
did
us
well,
but
yeah,
get
up.
Actions
is
just
a
really
good
product.
B
A
B
B
A
All
right,
okay,
so
I
know
there's
been
a
ton
of
work
on
getting
you
know,
nfs
and
cassandra
out
into
their
own
repositories
and
really
good
work
on
driving.
That
blaine
did
wanna.
Give
us
an
update
on
all
that
stuff.
B
A
C
D
B
Yeah
so
going
forward,
release
schedules
will
be
completely
independent.
Contributions
will
be
independent
and
they're
on
repos,
we'll
just
be
all
goodness.
A
More
possible
yeah,
definitely
and
so
likely.
Then
we
we,
if
there's
not
changes,
there's.
No,
you
know
effort
going
into
cassandra
or
nfs
and
for
the
1.7
there
would
not
we
don't
we.
We
would
expect
1.704
to
be
a
voxef,
only
release,
probably
right.
C
A
Yup,
that
sounds
that
sounds
great.
All
right.
Do
you
want
to
move
ahead
to
moving
the
example
folders
topic
here.
C
Beyond
I
go
for
it
yeah
I
mean
I
think
it's
a
natural
follow-up,
after
blaine's
and
travis's
work
on
decoupling
and
separating
the
back
cans
onto
their
own
repos,
it's
just
just
think
to
get
a
cleaner
root
repo,
where
essentially
we
so
today
we
have
a
directory
called
cluster
where
you
have
to
go
in
and
then
you
get
examples
then
kubernetes,
then
ceph
we're
just
proposing
to
simplify
all
of
that
and
rename
this
to
deploy,
which
essentially
means
deploying
and
then
inside
the
deploy
directory.
C
Then
you
have
examples,
and
then
you
have
olm
so
yeah.
This
is
essentially
what
the
change
is
about
is
yeah,
just
renaming
directories
for
clarity.
B
A
B
B
And
maybe
the
so
I
like
the
example,
the
idea
of
moving
the
examples
folder
up
and
the
question
to
see.
If
there's
concern
about
it
is
renaming
the
root
cluster
folder
to
deploy,
which
I
do
agree
deploy,
makes
a
lot
of
sense.
I've
just
been
trying
to
decide
is
it?
Is
it
worth
the
change
in
name
because
people
might
have
a
hard
time.
A
B
A
Yeah
one
of
the
things
that
comes
up
is,
I
you
know
in
the
documentation.
We'd
have
you
know,
control,
apply,
dash,
f
and
then
the
right
path
for
it
with
updated.
You
know
in
releases
where,
in
the
tree,
this
change
has
happened,
but
I
would
not
be
surprised
if
there's
you
know
scripts
or
you
know,
people's
own
handwritten
notes
or
whatever
that
are
out
there
in
the
ecosystem
that
have,
you
know,
commands
for
applying
things
that
use
the
old
pass
that
we
have.
D
Exactly
yeah,
I
I
as
a
kind
of
like
continuation
of
that
I
I
think
it
was
probably
about
a
year
ago
I
was
like
chatting
with
someone
on
slack
or
like
there
was
a
github
issue
where
someone
had
a
like
an
issue
on
upgrade
because
they
had
scripted
the
upgrade
where,
like
we,
we
always
have
upgrade
docks.
It's
like
do
these
things
in
order
to
upgrade
and
so
effectively
like
they
just
weren't
reading
the
upgrade
docks
and
we're
therefore
running
them
to
upgrade
issues.
D
B
C
D
Yeah,
I
think,
having
a
good
release.
Note
yeah,
honestly,
I
think
changing
from
cluster
to
deploy
is
another
way
because
the
when
the
whole
root
directory
changes.
That
means
any
scripting
anyone
has
done
on.
It
is
going
to
change
and
it's
going
to
break
and
like
as
soon
as
that
breaks,
then
they
will
realize
that
other
things
have
changed
as
well
and
we'll
have
to
like
update
scripts
if
they
have
them
or
otherwise.
D
B
C
B
A
All
right
sounds
good,
then
we
can
move
forward
with
that
and
then
the
sub
you
added
this
just
recently
here,
yeah.
C
B
B
Remove
it,
we
can
remove
the
the
slack
one
and
the
jenkins
one.
Basically.
A
B
B
B
C
B
B
A
Is
that
the
recommendation
they
made
to
use
snick
snick
whatever
it
is,.
B
A
A
That's
really
interesting
if,
if
there's
licenses
for
all
cncf
projects,
that
might
be
something
nice
to
be
able
to
get
the
benefit
of
that
yeah.
A
B
A
Awesome
all
right,
so
I
think
that's
everything
we
had
on
the
agenda
here.
Anything
else
that
folks
wanted
to
bring
up
here.
The
floor
is
open.
C
A
C
A
Yeah
yeah,
if
you
want
to
follow
up,
maybe
on
slack
then
spum.
If
you
have
something
else
there
we
can,
we
can
keep
that
conversation.
A
D
B
Like
travis
addressed
the.
B
A
And
I
think
this
is
what
may
have
been
logging
out
logging
back
in
or
changing
the
microphones
there
not.
B
C
B
A
Cool
all
right,
awesome
all
right,
then
I
think
that's
everything
here
on
the
agenda
and
so
yeah
great
good
to
see
everybody
thanks
for
everybody
for
joining
and
we'll
see
you
all
on
slack.