►
From YouTube: 2022-10-04 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
4th
2022
Rook
community
meeting,
so
we
will
start
with
our
Milestones
as
usual.
1.8
that
doesn't
have
anything
going
on
that
I
am
aware
of,
or
needs
to
be,
going
on
no
further
patch
patches
coming
up
for
that.
So,
let's
move
on
head
on
to
1.9
branch,
so
1.9.11,
let's
see
when
was
that
release
that
was
exactly
a
week
ago,
yeah
exactly
you
want
to
get
us
caught
up
on
a
couple
of
the
main
things
for
that
Travis.
B
Let's
see
I
mean
yeah
one
911
caught
up
on
a
bunch
of
backwards,
a
lot
of
good
little
fixes,
let's
see
what's
worth
mentioning
here,
glancing
through
those
release,
nodes,
yeah,
I,
don't
know
what
a
big
ones
would
be
worth
mentioning
just
a
lot
of
a
lot
of
good
little
fixes.
B
But
you
know,
assuming
we
don't
have
any
big
blocking
issues
that
may
be
the
the
final
final
final
patch
release
for
1.9.
We
could
do
another
one
we'll
see
if
there's
a
need-
and
maybe
there
will
be-
and
that's
fine
but
there's
not
currently
anything
I.
Think
yeah
backboarded
since
that
released
to
1.9.
B
A
Completed
this
one's
closed
from
in
the
to
do,
column
looks
like
maybe
we
can
move
that
over.
Otherwise,
yes,.
A
All
right
so
1.10
we
do
have
an
expected
patch
release.
So
let's
look
at
1.10.2.
First
was
that
around
last
week
as
well
yeah
exactly
the
same.
B
Yeah,
a
lot
of
the
same
patches
I
think
we
were
pretty
aggressive
about
backboarding
them
to
both
yep
yep,
goodness
a
couple
additional
ones
that
would
have
been
a
one
that
had
been
like
picking
up
the
latest
CSI
driver,
I,
think
3.7.1.
A
B
I
guess
something
I
feel
like
might
be
worth
noting
is
at
least
my
memory
of
the
prior
few
releases
was
that
we
released
the
dotto
and
we
pretty
quickly
released
like
that.
2.3
.4,
like
on
like
a
weekly
Cadence
and
picked
up
some
fairly
big
bug,
fixes
I.
B
It
seems
to
me
that,
with
the
1.10
release,
I
think
we've
actually
been
keeping
like
the
Cadence
of
releases
that
we
usually
keep
when
something
is
pretty
stable,
so
I
think
our
1.10
release
like
started
off
at
a
pretty
good
place,
yeah,
which
is
nice
I,
don't
think
we
had
any
urgent
releases
needed
that.
So
it's
been
nice
and
stable
nice.
B
A
A
We
go
okay,
that
makes
more
sense
and
so
typical
Cadence,
then
okay,
all
right
and
then
any
of
the
issues
here
on
the
1.10
board
that
need
to
be
discussed.
B
A
A
Looking
good,
then
all
right,
then.
Finally,
then
we
can
move
on
to
1.11,
which
is
definitely
very
forward-looking,
since
it's
about
a
quarter
away
from
us
now.
So
we're
talking
about
2023
here.
The
project
board
here
is
probably
not
probably
an
early
planning
for
this.
So
it's
not
super
populated,
yet
either
yeah.
One
whole
issue
showing.
B
Right
so
we'll
make
an
effort
by
next
meeting
to
add
more
work
items
here,
move
on
to
some
feature
planning.
Instead
of
the
just
the
bug
fixes
and
backboarding
yeah
I
put
a
tentative
date.
There
is
January,
just
I
mean
we
could
move
it
up
to
December
just
before
the
the
holiday
break,
the
Christmas
break
and
everything,
but
the
reality
is
January
is
may
just
be
better
or
approves.
B
Unless,
if
somebody
wants
it
in
December,
we
could
shoot,
but
January
will
be
more
like
our
court,
we've
been
really
a
four-month
Cadence
I
think
kubernetes
is
more
on
a
four
month.
Yeah.
A
That's
what
they've
they
moved
to
as
well.
Yeah
and
I
have
no
problem
with
that
Cadence
either.
You
know,
if
there's
something
like
a
feature
that
comes
up
that
is,
you
know
highly
high
in
high
demand,
then
you
know
you
can
maybe
think
about
doing
it
for
holidays,
but
yeah
I
think
this
that
feature
planning
hasn't
really
done
yet,
and
it's
not
up.
It
doesn't
seem
like
there's
something
super
obvious
burning
on
our
minds
to
be
driving
the
an
accelerated
release
either.
B
Yeah
I
assume
we'll
be
you
know
doing
the
like
a
sort
of
final
at
least
one
week
of
like
this
is
our
breakfast
period.
You
know,
there's
a
Beta
release
and
then
a
ga
release,
yeah
I'm
gonna,
say
mid-January
is,
is
the
Target
in
my
mind
just
because
the
last
week
of
January
I've
planned
a
vacation
already
so
in
January
might
be
good.
B
A
A
All
right
and
just
checking
the
chat,
real,
quick
welcome,
sent
us
to
the
call
here
as
well.
It's
good
to
have
you
here.
A
Yeah
good
to
see
you
yeah,
let
us
know
if
you
have
any
questions
or
anything
that
you
wanted
to.
You
know,
get
get
into
or
discuss
while
we're
going
through
the
call
here
too
yeah.
B
I
was
thinking,
I
was
I,
would
start
looking
into
rook
and
you
know
start
fixing
some
of
some
small
bugs
if
there
are
and
yeah
let's
get
started
from
there.
B
And
we've
got
some
bugs
labeled
with
good
first
issue
label.
If
you
want
to
look
for
those
that
might
be
a
good
place
to
start.
Okay
cool
sounds
good.
A
All
righty,
so
I
don't
see
Alexander
here
and
he
wanted
to
talk
about
long-term
supports
stuff.
So
do
we?
Maybe
we
can
postpone
this
one
for
a
little
bit
more
and
put
it
at
the
bottom
of
the
agenda
and
then,
if
Alex
shows
up,
we
can
go
into
it
then,
or
we
can
kind
of
Drive
some
of
the
early
thinking
of
the
discussion
without
him
as
well.
B
A
A
B
All
right
yeah
for
this
one.
We
were
talking
in
the
member
cuddle
yesterday
about
the
disaster
recovery
and
what
we
can
do
to
improve
it,
because
this
this
whole
page
on
the
data
recovery.
It's
a
lot
of
very
manual
steps
and
they're,
not
I
mean
as
documentation.
It's
not
tested
regularly,
there's
not
in
the
CI,
so
we
really
want
to
a
focus
area
is
to
improve
and
automate
a
lot
of
these
steps.
B
So
it's
not
so
tedious,
so
the
crew
plug-in,
which
we've
been
putting
a
lot
of
it
into
recently,
especially
in
part
we
can
start
building
on
that
and
I'm
prototyping
this
week
on
restoring
monoporam
after
Quorum
is
lost
and
anyway
I
think
it'll
just
be
a
lot
of
goodness
be
nice
to
have
so
just
wanted
to
point
out
we're
putting
some
more
effort
into
that
area.
B
B
A
B
A
How
are
you
thinking
about
like
the
division
of
responsibility
between
like
the
plug-in
the
cube,
CTL
plugin?
And
you
know
the
Rook
operator
and
when
you
would
put
you
know
this
type
of
functionality
into
the
plug-in
versus
having
it
as
part
of
the
operator
functionality
and
exposing
it?
There.
B
Right
I
mean
the
I
guess
the
simplest
way
I
can
Define.
That
is,
the
operator
is
for
a
desired
State
and
the
tool
is
for
one-time
actions,
which
you
know
when
you're
doing
Disaster
Recovery
I
mean
you
desire
to
get
the
cluster
back
up
online,
but
it's
not
really
ongoing
desired
state
right.
It's
a
one-time.
B
Do
these
operations
and
then
you're
done,
and
you
don't
need
to
do
them
ever
again
until
the
next
disaster,
if
there's
one
but
operators
for
ongoing
reconciles,
where
we're
constantly
making
sure
we're
in
that
state
and
running
the
same
commands
over
and
over
with
you
know,
I
did
I
didn't
both
turn
into
I
can
never
say
that
word.
I
I
didn't
put
an
action.
A
B
A
Would
be
about
restoring
Quorum,
like
that's
the
disaster
recovery
task,
to
focus
on
first
for
automation,.
A
Okay,
Travis.
Do
you
want
to
update
us
on
something
exciting
for
red
hat
and
IBM
world.
B
Yep,
so
this
just
came
out
this
morning
in
the
news:
there's
a
press
release
from
IBM
about
it
and
as
soon
as
this
is
over
I'll
I'll
post
it
in
the
announcements
of
The
Rook
slack,
because
so
everybody
will
know
but
there's
so
those
of
us
employees
of
red,
hat
working
on
Seth
and
rook
and
and
pretty
much
all
of
that
related
to
storage
will
be
officially
moving
over
to
the
IBM
storage
business
units
will
become
it's
kind
of
the
acquisition
within
the
acquisition
right
right
now.
B
It's
already
acquired
by
ABM
a
few
years
ago.
Has
it
been
three
years
already,
but
now
and
we've
been
in
really
acting
independently
since
that
acquisition,
but
now
they're,
taking
the
whole
storage
unit,
moving
us
as
employees
over
to
IBM
storage,
which
will
give
us
I
think
a
lot
better
long-term
growth
perspectives
and
opportunities
for
the
story,
so
I'm
excited
about
it.
There's
a
and
the
so
From
rook's
perspective,
though
we
don't
expect
anything
to
change.
B
It's
still
Upstream
first,
our
email
addresses
will
change,
although
we'll
still
have
our
red
hat
email
addresses
for
a
while
or
forever
and.
B
A
Yeah
I
think
the
biggest
thing
by
far
is
that
you
know
the
statement
here
that
commitment
to
Upstream
Road
concept
Remains
the
Same
right
like
that
on
a
day-to-day.
B
A
Isn't
changing
anything,
that's
still
investing
in
it.
You
know
no
concerns
about
that.
I
think
that
that's
like
by
far
the
most
important
thing.
So
thanks
for
clarifying
that
Travis
and
and
sharing
that
with
us,
I
was
one
thing
I
was
curious
about
is
just
by
you
know
skimming
this
article
here.
Real
quick!
Is
that
what
exactly
does
the
red
hat
openshift
data
Foundation
cover
I'm
saying?
Is
it
will
remain
100
open
source?
What
what
all
projects
does
that
cover.
B
Yeah
odf
is
really
I
mean
mainly
there's
an
OCS
operator
which
provides
an
opinionated,
installer,
rook
and
stuff.
It's
really
it's
I,
think
of
it
as
Rook
plus
Seth
plus
there's
a
new
nuba
is
another
technology
in
there
around
the
storage
and
they've
been
adding
some
more
things
that
haven't
been
keeping
track
of
honestly,
but
those
are
the
main
things
that
I
think
of
it
as
and
it's
all
been
focused
on
running
an
open
shift
and
that's
been
our
only
product
offering
so
now
with
IBM.
B
A
Yeah
yeah
for
sure
and
then
like
use
it
to
the
word
foundation
here.
That's
is
that
not
the
same
as
foundation
in
the
sense
of
set
Foundation
Linux
Foundation,
Cloud
native
Computing
Foundation?
This
is
like
more
like
that's
the
product.
Yeah
yeah,
like
the
foundation
of
your
data
platform,
type
of
thing
right.
A
Confused
me,
a
little
bit
is
by
seeing
Foundation
there
and,
like
it
more
open
source.
I
was
like.
Oh,
what
projects
belong
to
that
Foundation?
That
could
that
confused
me?
That's
what
I
was
curious
about.
B
Yeah
the
product
used
to
be
called
openshift,
container
storage
and
six
months
ago,
or
something
they
renamed.
A
B
Okay,
I'll
have
to
I,
don't
see
it
yet,
but
okay
I'll
keep
looking
at
it.
B
I,
don't
know
I,
don't
see
it
there,
yet
all
painless
stuff
devs
that
we're
working
on
me
and
Josh.
B
A
Okay
and
then
I
don't
see
Alex
still,
but
yeah
we
can
kind
of
get
into
some
of
the
high
level
things
here
about
long-term
support.
Lts
stuff,
you
know
because
we
do,
we
do
have
like
a
working
process.
I
was
kind
of
surprised,
I
thought
we
had
that
written
down
the
general
approach
we
take
there,
but
is
that
just
kind
of
you
know
like
I'm,
not
ad
hoc,
but
just
gotta?
The
way
we
do
things
kind
of.
B
B
It's
probably
my
fault
more
than
anything
if
people
really
want
undocumented,
but
that
I've
not
put
it
my
my
intention
was
to
not
put
it
there
so
that
we
can
be
more
flexible
or
do
what's
best
for
the
community
in
any
given
moment
like
if
someone
really
needs
to
back
support,
something
or
just
to
walk
through
these
bullets
I
added
there,
so
we
I
mean
we
can
backboard
fixes
to.
As
far
as
people
need
to
that's
not
really
a
problem,
but
then
the
problem
really
is
maintaining
CI.
B
B
So
since
it's
difficult
to
maintain
the
CI
for
the
older
version,
that's
where
saying
we
support
long-term.
Some
given
Rook
releases
is
a
challenge.
So
if
people
want
to
build
their
theirselves,
they
can
do
that
for
any
branch.
It'll
backboard
it
anywhere.
But
that's
really,
my
concern
is
maintaining
a
CI
there's
a
cost
to
it
and
it's
not
unlimited
resources.
So
you
know
we
always
try
and
do
what
the
community
needs
and
honestly
I
don't
feel
like.
We've
had
requests
so
much
to
backport
things
beyond
the
last
two,
maybe
three
releases.
B
Whenever
people
hit
issues
with
the
older
clusters,
it's
configuration
or
environment
issues
once
they
work
through
it,
then
they
can
upgrade.
So
historically
at
least
we've
had
a
good
record
that
way
of
not
needing
to
do
old
releases.
A
Yeah,
you
know
I
I'm,
very
much.
You
know
in
support
of
having
an
explicit
policy
of
you
know
like
the
last
two,
like
the
current,
the
like
the
current
three
releases,
you
know
like
the
something
something
like
that
having
a
specific
number
to
it.
As
opposed
to
you
know,
oh
yeah,
we
can
go
back
and
do
one
dot
blah
blah.
You
know
that
like
backwards,
okay
and
then
we'll
try
to
get
their,
you
know,
CI
going
I.
Think
it
like
being
more
explicit
about
it
seems
seems
pretty
good
was
Alex
coming
at
this.
A
So
from
from,
like
you
know,
like
a
more
traditional
or
classic
like
LTS
type
of
thing,
where
you
know
you
have
LTS
releases
and
then
you've
got
ones
that
you
know
it
stays
supported
for
a
long
time,
but
then
you've
got
some
ones
there
that,
like
will
drop
out
more
quickly,
and
then
you
know
like
that
sort
of
thing
or.
B
A
B
A
Yeah,
maybe
yeah
it'd
be
good
if
he's
got
yeah
some
more
specific
direction
that
he
or
you
know,
pain,
points
that
he
wants
to
solve.
You
know
essentially
like
the
most
of
the
stuff
you're
bringing
up
here
Travis.
It
seems
reasonable
to
me.
A
I'd,
be
I'd,
be
more
like
fine,
also
like
going
going
to
a
more
specific,
explicit
policy,
so
not
like
just
like
keeping
it
flexible,
but
you
know
like
the
two
like
the
two
or
three
whatever
most
most
recent
releases
is
something
that's
that's
reasonable
to
be
explicit
about
a
policy
than
that
and
not
do
patches
or
maintain
older
ones,
and
that
is
something
that
would
be
okay
with
me.
Yeah.
B
B
A
A
You
Jared
yep
good,
seeing
all
y'all
and
good
luck
with
your
new
IBM
home
yeah
for
the
last
I
feel
like
I'm,
saying
after,
like
the
last
two
years
at
least
I'm.
Not
that
was
meaningful.