►
From YouTube: 2022-10-18 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
October
18th
2022
Rook
community
meeting.
So
let's
jump
on
into
our
Milestone
checkup
and
let's
see
check
in
on
everything
here,
I
have
a
little
confused
myself
right
now
about
when
specifically
last
releases
are
done.
So
let's
click
on
this
here,
real
quick
check,
the
dates
12
days
ago,
so
that
would
be
since
the
last
community
meeting
right.
Yes,.
B
B
A
B
A
That
makes
sense
all
right
sweet,
so
we
got
that
one
out
and
that
one
the
1.9.12
was
released
and
then
now
there's
nothing
currently
planned
for
further
1.9
releases.
Unless
another
particular
fix
comes
up,
then
correct,
yeah,
yeah,
all
right,
let's
check
in
then
on
1.10.3
and
give
ourselves
a
quick
pressure.
I
feel
like
that
was
the
same
day.
So
you
know
we
obviously
got
that
same
Helm
fix
in
there.
A
The
memory
limits
in
there
for
osds
and
then
another
set
of
fixes,
though
obviously
since
we're
not
10,
is
the
most
recent
release.
So
we're
getting
a
lot
more
things
in
there.
So
any
highlights
to
call
out
here
Travis.
B
Oh,
let's
see
I
mean
we
had
the
new
3.7.1
CSI
driver,
just
I,
don't
know
yeah,
just
a
bunch
of
other
small
fixes.
A
Yeah
all
right,
so
then
you
know
with
our
typical
Cadence
of
every
two
weeks
or
so
then
we
have
another
1.10.4
release.
That's
planned
for
just
two
days
from
now
on
Thursday
of
this
week.
Let's
take
a
quick
look
at
the
project
board
to
see,
what's
might
be
included
in
that
or
what's
still
pending,
to
make
it
in.
B
Yeah
I,
don't
think
anything's
blocking
that
release.
That
would
just
be
our
Cadence
release
for
sure.
I've
tried
to
clean
up
I've
spent
a
few
minutes
before
this
cleaning
up
the
board
a
bit
I've
got
a
few
things
that
would
be
nice
to
have
still
in
1.10,
but
yeah
I'm,
not
sure
we'll
have
any
of
those
by
this
Thursday
at
least
so
sorry
shabanzo.
Looking
at
that
one
in
progress
there,
but
we'll
we'll
see
on
that.
One.
A
All
right
anybody
else
want
to
call
anything
out
for
the
next
1.10
patch
release.
That's
coming
up
on
Thursday.
A
All
right,
okay,
so
we'll
follow
up
this
week
to
get
that
one
out
on
Thursday
and
then
1.11
I
think
we're
still
pretty
early
in
the
cycle.
There
we're
talking
about
mid-January
so
after
the
holidays
and
into
next
year,
which
would
be
the
release
scheduled
release
on
that
so
very
early
with
just
a
set
a
couple
of
a
handful
of
issues
that
were
you
know,
put
into
this
Milestone
or
things
that
we're
planning
on
focusing
on,
but
nothing
quite
really
done
yet.
A
B
Yeah,
mainly
the
issues
in
the
board
right
now,
I
just
moved
from
1.10,
which
was
obvious,
the
ones
that
were
obviously
not
going
to
happen
1.10.
So
please
aren't
really
committed
or
yeah.
They
just
got
moved.
So
we
really
need
to
think
about
what
do
we
really
want
in
1.11?
Oh
I
haven't
updated
the
road
map,
yet
I
need
to
do
that
and
think
about.
What's
you
know,
what
are
we
gonna
do
shoot
for
in
1.11.
now
the
operator
SDK
updated
the
big
one.
B
The
coupon
is
working
on
now,
I,
don't
know
if
we
even
have
an
issue
on
this
board.
For
that
yet
so
I
know
there's
oh
wait,
yeah.
It
is.
C
B
D
I
think
it
will
be
I
think
it
will
be
a
little
impact
on
their
is
regarding
a
tight
twist
structure
and
also
but
yeah.
We
will
see
later.
B
A
Would
that
would
that
be
any
like
any
possible
changes
in
the
functionality
of
the
operator?
Is
it
more
of
the
packaging
and
installation
and
upgrade
you
know,
process
or
path.
B
D
No
I
think
this
is
mostly
the
packaging
and
upgradation
yeah.
Apart
from
that
activity,
changes
currently
I
cannot
think
of,
and
that
also
be
my
can
handle,
but
yeah.
It
is
mostly
the
packaging.
B
A
Cool
sounds
good,
sounds
good,
okay,
and
so
nothing
too
much
else
going
on
in
1.11
to
bring
up
or
talk
about.
But
I've
got
a
few
months
until
the
tentative
scheduled
time
frame
for
the
release
of
mid-January
so
plenty
of
time
to
be
working
on
the
focus
areas
and
high
level
objectives
in
this
Milestone
and
then
to
deliver
and
execute
on
them
as
well
all
right,
so
we
can
go
ahead
and
start
moving
on
into
the
community
topics
section.
So
parth.
A
You
added
a
a
discussion
agenda
topic
here
about
using
two
two
dot,
XY
versions
for
for
the
book
releases,
and
it
looks
like
Travis
already
answered
that
with
exactly
my
same
mentality
as
well.
Is
that
you
know
sticking
to
the
the
the
meanings
of
semantic
versioning
and
as
long
as
nothing
is
you
know,
changing
breaking
changes
or
you
know
major
functionality.
Overhauls
I,
I
also,
don't
see
a
need
to
bump
to
you
know
to
a
major
version
bump
foreign.
E
Yeah,
it's
more
of
a
curiosity.
I
would
say
just
like
I
see
like
different
versions
coming
for
some
different
projects,
but
yeah.
It
makes
sense
to
like
continue
how
kubernetes
versions
are
releasing
so
yeah
I
guess
we
can
keep
it
like
that.
A
Yeah
and
then
pretty
much
all
the
projects
I've
seen
within
like
the
cloud
native
space
that
have
done
a
version
bump
to
a
version
two
they're
they're
almost
exclusively
around
you
know
big.
You
know
re-architectures,
you
know
changing
the
protocol,
like
you
know,
major
functionality,
ranking
changes,
type
of
stuff
where
it's
a
very
conscious.
Okay,
now
I've
got
to
change
how
I'm,
using
this
thing
to
go
to
this
new
model
in
version
two,
so
it
is
very
much
a
semantic.
You
know
big
bump
there
so
yeah,
that's
that's
yeah.
A
B
Is
a
different
pattern
from
like
the
Seth
version,
because
the
Seth
major
version
changes
every
year
with
each
new
release
and
even
though
there's
not
really
freaking
changes,
but
yeah
I
think
the
following:
what
kubernetes
is
doing
for
release
versioning
and
following
and
only
changing
the
major?
If
there's
a
breaking
change?
That
makes
sense
too.
C
Right,
I,
I
think
also
it
makes
sense
to
keep
our
versions
aligned
with
our
like
API
versions.
C
So
were
we
to
go
to
a
drastically
new
model,
we
would
have
to
do
to
our
apis
as
well
as
a
V2
of
our
like
release,
numbers
I.
Think.
A
B
B
That's
just
in
final
review
for
taking,
basically
if
you've
lost
Quorum
and
you
want
to
restore
Quorum
just
to
a
single
mon,
just
Define,
a
single
good
model,
then
you
can
restore
it
to
just
that,
so
the
yeah,
so
the
the
crew
plug-in,
makes
that
really
nice
and
here's
a
link
to
it.
Almost
there,
okay
yep,
so
there's
a
link
and
it'll
just
be
it'll,
be
great,
so
that'll
be
the
first
kind
of
Disaster
Recovery
scenario
helped
by
the
the
crew
plugin
and
then
we
can
work
on
more
from
there.
B
A
A
Very
cool,
very
cool:
have
you
gotten
some
good
Cycles
on
taking
this
for
a
test
Spin
and
such
Travis?
Another.
B
Mini
Cube,
it's
working
well
right,
it'd
be
nice
to
have
some
validation
on
a
real
failure.
Let's
see
but
yeah
it
I
mean
the
scenario
is
tested
in
that
CI
granted
mini
Cube.
Maybe
I'll
try
it
on
a
a
full
clust
full-size
cluster
too,
but
just
to
confirm
but
yeah
I.
Think.
If
we,
the
idea
is
we
could
if
we
get
this
in
the
next
couple
of
days,
we
can
have
a
cruellies
this
week
also
and
then
it'll
be
available
for
someone
to
try
out
the
next
time
they
they
hit
that
Disaster
Recovery.
B
A
Be
nice
to
be
able
to
test
this
with.
You
know
multiple
distincts
and
nodes
within
the
cluster.
You
know,
as
opposed
to
the
as
you
called
out.
The
test
scenario
of
you
know:
mini
cube
with,
maybe
maybe
a
single
single
node
in
it.
A
Yeah
very
cool,
though
this
is
definitely
definitely
helpful
to
you-
know,
provide
more
Automation
and
streamline
stuff.
Hopefully
no
one
ever
has
to
use
it,
though
this
is
true.
A
Okay,
great
Travis,
thanks
for
that
update
now,
the
daily
test
run
is
now
green.
Once
again,.
B
Yes,
so
the
law
there
were
two
major
issues
we
had:
one
was
Seth
Maine
didn't
allow
us
to
detect
the
difference
between
reef
and
Quincy,
and
that
was
fixed
a
couple
weeks
ago.
So
those
tests
turned
green,
except
for
intermittent
issues
and
then
with
Siobhan's
fixed
for
rm64
to
clean
up
the
the
tests
when
they're
done
now
arm
is,
is
passing
too
so
we're
down
to
intermittent
values.
But
a
couple
days
ago
there
was
a
green
build.
So
it's
nice
to
see
that
again.
A
Definitely
is
are
the
intermittent
failures
of
those
like
long-standing
known
issues,
type
of
things,
Travis.
D
B
A
Cool
yeah,
great
effort,
though
Siobhan
for
for
getting
getting
that
that
one
that
said
test
fixed
thanks
for
doing
that.
C
A
B
And
it
opened
an
issue
I
think
we
just
need
to
update
our
references
to
pick
up
some
some
recent
fix
because
of
all
the
reports
as
it's
fixed
in
some
newer
version
of
that
go
module.
So
probably
a
simple
thing.
A
Okay,
good
good
now
with
this
Travis
like
what's
the
scope
of,
like
you,
know,
a
release
to
fix
this,
is
this
something
we
just
fixed
and
and
mean
and
then
and
then
get
out
in
the
next?
You
know
next
next
scheduled
release
or
backboard
this
or
what's
your
take
on
that.
B
Yeah
I
think
just
getting
a
fix
in
and
releasing
on,
Thursday
and
fixing
it
with
1.10
will
be
sufficient.
I,
don't
feel
like
it's
urgent
to
get
into
a
backboard.
I
didn't
see
anything
that
indicated
it's
a
real
security
issue
for
us.
Just
that
it's
it's
good
to
keep
the
scan
clean,
but
no
known,
attack
surface.
That
I
could
find.
A
B
A
Cool
all
right
and
then
yes,
so
then
this
agent
item
we
did
talk
last
meeting
about
you
know
our
our
release,
Cadence
process
Etc,
so
Travis
you
you
did
then
follow
up.
I
saw
to
get
that
get
that
documented.
B
B
A
B
C
A
Yep,
okay:
this
is
good.
This
is
a
good
policy
to
kind
of
capture
and
be
clear
about
what
we're
doing
all
right.
Okay,
so
that
looks
like
the
end
of
the
topics
that
are
on
the
agenda
here:
I'll
open
up
the
floor
for
any
other
topics
that
folks
wanted
to
bring
up.
That
did
not
make
it
to
the
agenda
itself.