►
From YouTube: 2021-10-05 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
the
recording
has
started-
and
this
is
the
october
5th
2021
rook
community
meeting.
So
let's
dive
on
into
our
milestones
here
and
go
through
the
agenda,
it
doesn't
look
like
we're
necessarily
strictly
planning
on
another
patch
release
for
a
1.6.
A
So
we
can
open
the
board
here
briefly
and
see
if
there's
anything
there,
but
I'm
anticipating
not
if
we're
not
expecting
even
a
release
unless
if
it
comes
up,
there's
nothing
in
the
boxing
release,
column.
B
Exactly
yeah,
I
don't
think,
there's
anything
significant
or
that
I
recall
fixing
for
1.6
in
the
last
bit,
so
if
needed,
we
can
release
in
a
couple
weeks,
which
would
be
a
month
cadence
at
this
point,
so
we'll
see
what
comes
up
but
nothing.
Currently,
I
think.
A
Yeah
that
sounds
good
and
then
everything
comes
up.
We
can't
deal
with
that
and
we
have
the
ability
to
do
a
patch,
no
problem.
So
let's
take
a
look
at
1.7,
which
we
do
have
an
upcoming
release
for
we'll
do
1.7.5
later
on
this
week.
Let's
take
a
look,
see
the
board
there
and
talk
about
what
will
be
in
that
patch
and
what's
left
perhaps
too.
B
So
we
just
need
to
initialize
the
pool
right
after
we
create
a
pool,
and
that
will
work
around
this
issue
until
it's
it's
fixed
in
the
next
self-release
so
anyway,
hopefully
we'll
have
that
out.
I
got
a
pingless
csi
team
and
see
if
I
thought
they
were
working
on
it,
rekshith
from
csi,
so
yep.
Otherwise
it's
pretty
much
just
nothing
blocking
but
trying
to
get
fixes
moved
through
as
usual,
and
I
don't
have
anything
else
to
report
specifically
around
1.7
anybody.
A
Release
of
1.7
this
week
and
we
will
move
on
to
1.8
then
which
we
are
working,
there's
still
somewhat
early
in
the
cycle
there
and
working
towards
the
release
in
in
early
december.
A
So
let's
break
up
that
project
board
and
go
ahead
and
talk
about
things
that
maybe
are
we
want
to
call
out
here
as
obstacles
or
risks
or
big?
Oh
no,
I
messed
up
my
zoom
here
there
we
go,
I'm
back
on
my
screen,
yeah
obstacles,
risks
or
big
accomplishments
that
we
already
want
to
call
out.
B
Yeah,
I
didn't
get
a
chance
to
review
this
board
before
the
meeting,
but
I
think
so
I
mean
some
big
changes
we
have
coming,
or
we
talked
about
before,
like
to
remove
nautilus
support,
remove
the
flex
driver
update
the
minimum
version
to
kubernetes
1.16,
that's
supported
and
a
couple
of
those
have
already
been
merged.
I
think
not
the
nautilus
change.
We
can
probably
merge
pretty
soon
one
other
change.
B
A
B
B
C
So
travis
we
are
planning
to
hold
safe
nautilus
like
for
one
more
month,
so
because
of
the
same
reason
of
the
change
in
directive
layout
or
we
can
like
much
safe
nautilus
earlier,
like
not
wait.
One
month
or
two
months.
B
B
B
C
A
So
did
alex
show
for
his
topic
here
looks.
B
Like
we
don't
have
alex.
B
Yeah
he's
asking
about
the
operator
kit
and
if
it's
still
being
maintained
at
all,
should
it
be
archived
or
deprecated?
Well
so
yeah
this
I
looked
at
the
commit
history.
Briefly.
We
haven't
committed
to
it
for
over
two
years
now
and
feels
like
longer
than
that.
I
feel
like
forever.
Since
we've
used
it
so
yeah
we
might
want
to
consider
putting
in
read-only
mode
blaine.
You
have
a
comment.
There
don't
forget
to
check
for
all
usage
yeah.
B
A
To
check
for
references
across
like
you
know,
basically
all
all
repos,
like
you
know,
if,
like
somebody's
using
it
in
their
a
fork
or
something
like
that,
I
don't
know.
Okay,
I
feel
like
they'd,
be
able
to
at
least
at
least
like
in
search
or
something
like
that
and
search
for
like
the
import
path
across
all
of
github.
That
might
be
I
I.
A
A
lot
of
hits
or
anything,
but
that
might
be
nice
to
do
as
well.
B
B
A
A
All
right
so
zero
jenkins
you're
telling
me.
B
A
How
about
the
so?
We
have
a
backup
of
the
instance
there,
how
about
like,
but
we're
still
using
storage
in
that
account
right,
like
the
s3
buckets,
we're
still
putting
artifacts
and
it's
owned
by
that
account
right.
B
A
Yeah,
that
sounds
good,
but
this
is
great
definitely
a
milestone
to
no
longer
have
old,
jenkins
running
there.
These
chickens
served
as
well,
but
it's
time
to
come
and
now
we
can
move
on
and
live
a
new
life
jenkins
free.
A
Okay,
all
right
so
yeah,
so
the
new
control
plugin
that
we
have
here
so
bomb.
Do
you
want
to
kind
of
drop
the
conversation
here
about
getting
our
first
release
out
or
what's
left
for
that
yeah.
C
So
I
I
have
opened
the
issue
like
to
get
the
thoughts
on
having
first
release
of
this
tool,
because,
after
the
release,
I
will
use
the
the
zip
file
of
the
release
to
write
the
manifest
for
the
group
plugin
that
I
will
have
to
post
that
I
will
have
to
get
via
on
the
cube
index
repo.
So
I
have
opened
the
issue
like
if
you
can
open
the
issue.
Tab
click
on
that
and
the
first
one.
C
So
I
have
like
described
why
we
need
that
and
also
added
some
links
like,
which
is
what
example
manifest
look
like,
and
why
we
we
need
the
first
release
of
this
tool
or
to
make
more
progress.
And
what
are
steps
required
to
have
the
plugin
available
with
crew
just
wanted
to
get
thoughts
on
on
the
releasing.
C
D
Yeah,
I
think
I
think
my
only
like
consideration
for
releasing
the
crew
plugin
is
to
release
it
with
like
an
alpha
like
the
designation.
I
guess
for
for
lack
of
like
finding
a
better
word
just
so
that
it's
clear
that
we're
not
making
any
promise
to
like
keep
the
ai
or
keep
ai
to
keep
the
api
or,
like
user
commands
stable.
While
we
like
kind
of
develop
what
the
overall
structure
of
the
commands
are
going
to
be.
A
And
blaine,
I'm
not
super
up
to
date
on
like
any
specifics,
that
crew
might
need
for
semantic
versioning
so
like
I'm,
assuming,
though,
that
it
can
handle
any
any
well-formed
semantic
versions.
You
could
have
like
a
dash
alpha
in
the
in
the
senver
and
crew
would
still
be
able
to
install
and
upgrade
it
over
time,
and
things
like
that.
D
Yeah,
I
think
some
fur
v2
specifies
like
using
the
alpha
like
sub.
It's
not
subscript,
it's
a
yeah,
but
using
the
alpha
like
at
the
end
yeah,
it's
like
still
a
valid
semper
yeah.
They
talk
about
like
alpha
and
beta
versions.
B
B
B
D
Yeah,
I
don't
know
how,
like
I
mean,
we've
already
seen
that
rook
users
will
script
their
upgrades,
despite
the
upgrade
guide
like
having
slight
changes
between
releases.
So
I'd
rather
not
a
I'd
rather
not.
Have
us
assume
that
they're
not
going
to
use
it
for
scripting
when
I
think
they
almost
certainly
will.
B
A
Yeah
and
then
yeah.
Definitely
we
should
have
an
understanding
of
you
know
how
crew,
as
like
a
package,
manager,
tool,
sort
of
thing
handles
upgrades
or
you
know.
B
A
The
semantic
versioning
yeah
and
increasing
that
we're
doing
over
time
also
so
make
sure
that
it,
you
know
it
does
a
good
job
of
being
able
to
make
like
get
the
plugin
updated
to
the
latest
as
we're
continuing
to
make
changes
to
it.
So
people
don't
have
to
a
rough
rough
experience
with
that.
B
A
A
The
the
logic
there,
but
you
know
I
I
don't
myself-
have
an
understanding
of
how
crew
you
know
looks
at
the
manifest
and-
and
you
know,
retrieves
the
artifacts
from
where
the
man
effects
points
to
and
and
if
it
does
a
check
of.
Oh
this,
this
version
is
is
not
a
higher
version
than
the
last
one.
If
there's
any
funny
business
there,
you
know
we
should
kind
of
get
a
good
understanding
of
what
crew
does
from
a
metadata
perspective
to
you
know,
actually
go
and
do
the
upgrade.
A
The
update
itself
is
like
yeah,
switching
out
a
new
shell
script
for
an
old
one
or
whatever,
but
you
know
the
metadata
around
and
how
crew
manages
that
as
a
package
manager
is,
is
good
to
understand.
A
Yeah,
but
getting
this
out
you
know
soon
and
and
being
clear,
that's
alpha
is
totally
reasonable
to
me
getting
more
access
to
it.
B
A
All
right
and
then
somebody
have
another
another
agenda
item
here.
A
B
Oh
yeah,
I
mean
for
the
like
the
past
year,
we've
had
the
broken
fossil
license
and
I've
been
in
my
action
items
forever
and
I
thought,
if
we're
actually
going
to
get
something
done.
I
should
ask
your
mom
to
do
it
so
so
anyway,
yeah
he's
taking
a
look
at
that
and
we
just
need
to
get
access
to
this
license.
Now
that
cncf
said
amy
said
we
could
should
have
one
available
so
I'll
ping,
her
and
figure
that
out.
B
A
A
Okay,
great
yeah:
this
is
great.
I'm
really
really
really
happy
to
see
this
for
sure
all
right
anything
else
for
the
fairly
short
agenda
today.