►
From YouTube: 2022-09-20 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
B
All
right
recording
has
started,
and
this
is
the
September
20th
2022
Rook
community
meeting
the
a
reminder
to
folks
that
the
agenda
Doc
is
open
for
everybody
to
continue
adding
things.
B
I
will
go
ahead
and
drop
a
link
to
the
agenda
doc
into
the
zoom
chat
right
now,
so
folks
can
directly
go
to
it
and
add
any
topics
of
discussion
that
they're
interested
in
otherwise,
let's
jump
on
into
Milestone
checkups,
so
I
just
took
a
quick
pass
through
the
various
release,
Milestone
boards
and
recent
releases-
and
you
know
there
has
not
been
a
recent
patch
release
since
the
last
community
meeting
for
1.8
or
1.9.
But
there
was
a
1.10
patch
release
since
the
last
community
meeting.
B
So
we
did
the
1.10.1
patch
release
on
September
9th.
That
was
just
a
few
days
after
last
community
meeting.
So
let's
hop
into
that
release
real
quick
here
and
let's
see,
if
there's
anything,
you
know
major
that
folks
wanted
to
call
out
as
part
of
a
part
of
this
release,
Alexander
or
Blaine
or
anything.
You
guys
want
to
call
out
for
this
1.10.1
patch
release.
A
Yeah
I
I
think
something
to
kind
of
note:
I
mean
it's
fairly
small,
but
the
warning
about
Helm
chart
upgrades
before
upgrading
to
kubernetes
1.25
is
I,
think
a
pretty
important
item
for
Helm
users
and
who
want
to
update
to
the
latest
kubernetes
version.
B
And
is
that
it
Blaine
was
that,
like
a
blocking
warning
that,
like
you,
it
would
fail
to
upgrade,
or
it's
just
hey
like
you're
upgrading
now,
and
you
really
also
need
to
be
doing
this
kubernetes
upgrade
too.
A
No,
it's
not
that
the
kubernetes
upgrade
is
required.
It's
that
the
the
helm
chart
needs
to
be
updated
before
upgrading,
just
kubernetes
1.25,
and
that
is
related
to
the
Pod
security
policies.
C
A
Removed
from
kubernetes
1
to
25.,
so
now
the
the
helm
charts
in
1.9.10
will
remove
PSPs.
If,
if
kubernetes
1.25
is,
is
a
part
of
it,
there.
B
Got
it
okay,
so
yeah
we
added
it
and
it's
like.
Is
this
the
docs
okay
got
it
yep,
definitely
important
to
call
out
for
folks
so
that
they
can
have
a
good
experience
when
they're
getting
on
on
that
release?
Yeah
okay
sounds
good.
B
Cool
okay
sounds
good,
so
then
let's
get
a
status
as
well,
so
yeah
so
with
a
typical
Cadence
I
would
expect
another
patch
release
for
1.10.2
to
be
later
on
this
week,
like
Thursday
or
so,
but
I
don't
know
if
that's
confirmed
or
if
we're
we're
planning
on
that.
But
that
would
be
the
typical
typical
Cadence
I
believe.
B
A
Week,
sorry,
yeah,
yeah,
yeah,
I,
think
I
think
that's
probably
likely
is
next
week.
I
think
the
1.10
release
has
actually
been
fairly
fairly
stable
overall,
especially
kind
of
comparing
to
some
of
the
the
previous
few
releases,
but
always
some
little
to
do's.
B
Yeah
in
1.10
project
boardview
do
not
have
anything
currently
in
the
blocking
release
column.
Is
there
anything
that's
already
in
the
done
column
that
you
know
we
would
be
giving
us
a
little
bit
of
incentive
or
motivation
to
be
getting
a
1.10.2
out
soon.
A
B
Okay
sounds
good
yep,
so
then
I
expect,
then
that
we'll
just
probably
follow
the
typical
Cadence,
then
of
getting
one
out
every
two
weeks
or
so
so
yeah,
nothing,
big,
that's
driving
a
1.10.2
patch
release
or
anything
that
we're
majorly
concerned
about
right
now,
great.
B
A
I
guess
that
would
be
Friday
yeah.
It
could
be
Friday
or
maybe
early
next
week.
Okay,
I
guess
I
can
always
do
it
too.
I
will
I'll
make
a
note
to
go
through
and
look
at
the
latest
commits
in
the
branch
to
see
if
there's
anything
that
should
push
us
too,
to
release.
B
All
right
sounds
good
Blaine.
Thank
you
for
following
up
on
that
yeah.
Let
me
make
a
note
online,
okay,
all
right
and
then
let's
go
ahead
and
I
guess
we
can
keep
on
moving
forward
to
the
community
topics
and
questions
since
we've
got
our
latest
Milestones
talked
about.
B
So
we
had
this
on
the
agenda
last
time
as
as
in
the
it
did
not
make
the
1.10
release,
but
I
would
love
to
hear
where
we
currently
are
with
this
effort
and
like
if
we're
stabilizing
on
the
CI
test
or
we're
still
running
into
failures,
what
the
what
the
next
steps
are
for.
It.
A
Is
issue
I'm
here
to
to
talk
about
this
a
little
bit.
C
Yeah,
so
we
tried
to
develop
like
doing
one
110.1
release,
but
we
could
not
have
the
fix
yet
and
we
and
we
are
not
able
to
you,
know,
get
the
right
place
to
fix
or
like.
We
are
not
aware
what
is
filling
the
CI,
because
there
are
only
two
commands
which
is
failing
to
run
with
the
client.through
cooperator.
C
Apart
from
that,
like
all
the
all,
the
commands
are
running
and
there
were
no
issues,
but
currently
we
decided
that
we
will
take
a
break
from
this
since,
like
we
spent
more
than
like
two
three
weeks
me
and
Travis
both
so
we
decided
that
we
will
take
a
one
week
or
two
week
break
from
this,
and
and
we
will
get
we'll,
we
will
Target
this
for
maybe
1.11
or
something
So
yeah.
Thank
you.
C
B
That
sounds
good
thanks
for
giving
us
that
update
on
and
thanks
for
your
continued
effort
on
it
as
well.
You
know,
obviously
there's
some
long
tails
to
to
follow
here
and
wrap
up
to
get
to
a
conclusion.
So
thanks
for
your
continued
effort
on
it,.
B
Right
so
yes,
and
then,
let's
hop
on
into
this
Steph
OSD
segfault
issue,
Let's
bring
this
up
on
the
screen
and
see
what
we
got
here.
A
Yeah
I
I,
don't
have
a
ton
of
deep
information
on
this
I,
unfortunately
think
no
one
has
a
ton
of
deep
information
on
it.
I
wanted
to
call
this
out.
This
is
an
issue
that
this
Upstream
user
has
has
seen
and
reported.
This
is
someone
that
is
there's
definitely
like
a
fairly
occasionally
active
on
The
Rook
in
the
Upstream
Community.
A
This
is
also
an
issue
that
Red
Hat
has
like
seen
or
or
we've
seen,
an
issue
that
seems
similar
to
it,
and
the
current
working
theory
is
that
it
may
relate
to
some
process
in
this
fosd
of
getting
confused
by
old
data
on
a
on
a
hard
disk
which
I
mean
I
really
should
should
not
be
happening
in
in
my
opinion,
so
there's
not
a
there's.
Not
a
lot
of
this
is
what's
causing
editor.
This
is
how
we're
going
to
fix
it,
but
just
this
is
something
that
we
are
aware
of.
A
B
And
blade,
so
is
this
something
that
the
Upstream
Seth
Community
is
is
looking
into
as
well,
or
is
it
only
reproduced
in
you
know,
Rook
scenarios
or.
A
A
Some
some
part
of
it
could
be
that
you
know
Rook
is
just
easier
to
like
tear
down
and
reinstall
than
than
set
Busters
sometimes
and
that
that
seems
to
be
the
one
of
the
related
factors
for
at
least
what
we've
been
seeing
in
one
of
the
downstream
issues
and
it
it
could
be
that
these
are
you
know
the
downstream
issue
and
this
issue
reported
are
are
not
related,
but
I.
Think
currently,
the
the
logs
that
we're
getting
from
the
OSD
are
similar
enough
that
that
it
seems
to
us
they
could
be
related.
A
I
wish
yeah
I
wish
I
had
more
definitive
answers
here.
I
I
just
wanted
to
make
sure
it's
something
we
call
out
as
something
that
we
are
investigating.
It's
just
progresses
sort
of
slow
and
confusing.
C
I
think
the
count
from
safety
is
also
looking
so
I
will
say.
Yes,
if
Safe
Community
is
also
keeping
eye
on
this
and
in
the
downstream
bc2
we
we
got
some
involvement
from
the
safety.
B
Got
it
okay,
sweet?
So
it's
yeah,
it's
not
clear
exactly!
You
know
how
what
the
root
cause
is
how
to
fix
this.
It's
you
know
we're
not
working
on
effects
already
to
deliver
it,
because
we're
still
investigating
the
nature
of
it,
trying
to
gather
more
information
as
well.
Okay,
yep,
that
makes
that
makes
sense
then,
and
I'll
go
ahead
and.
B
Oh
yeah
cool
cool
yeah.
So
then
do
you
want
to
go
ahead
and
start
start
jumping
into
that
one
then,
too.
C
Yeah,
so
thank
you.
We
don't
have
a
like
a
great
doc
documentation
of
the
crew
for
the
crew
plugin
and
for
the
each
commands
and
the
arguments
that
we
have.
So
we
decided
that
we
will
have
a
separate,
separate
dock
for
each
command
with
with
like
which
will
explain
what
is
like
supposed
to
be
working
with
that
command
and
what
argument
that
command
accepts
and
the
and
how
output
looks
so.
We
will
have
a
like
big,
big
document
of
like
each
command,
which
explained
like
most
of
the
things
so
yeah.
B
If
you
have
the
Jew
and
Travis
close
on
the
approach
to
take.
C
Yeah
so
I
and
I
said
like
offline
discussion,
and
so
we
decided
that
we'll
keep
the
separate
dock
in
group
plug
and
on
The
Rook
side.
Let
me
just
split
up
here
on
the
from
the
website
also
and
on
The
Rook
side.
We
will
link
plot
link,
but
we
will
have
like
through
documentation
according
to
the
requirement
of
the
topic.
So
let's
say:
if
someone
wants
to
like
pause
OSD
on
like
and
they
are,
they
are
looking
to
The
Rook
documentation,
not
the
group.
C
So
in
that
section
we'll
have
the
okay
I,
don't
have
the
permission
to
edit
the
talk,
but
I
I
will
suggest
that
clearly.
C
This
is
The
Rook
PR,
which
added
like,
which
adds
particular
command
section.
According
to
the
requirement
of
the
topic.
B
Foreign
got
it
so
then,
so
what
we'd
be
adding
to
the
Rook
docs
is
more
of
like
the
Practical
usage
of
the
crew
plug-in
okay,
for
like
scenario
based
of
hey,
we
want
to
accomplish
the
scenario
you
run
this
command
to
do
it
and
that's
kind
of
helps
document
it.
Okay,
that
makes
sense,
and
then
did
we
also
in
the
docs
for
the
the
plugin,
the
crew
plug-in.
B
Do
we
have
a
clear
pointer
to
The
Rook
docs
like
to
find
out
more
information
or
to
see
more
examples
of
this
plug-in,
go
to
The
Rook
docs?
Do
we
have
a
good,
an
Easy,
Link
or
pointer
to
The
Rook
docs?
There,
too,.
C
So
we
are
not
pointing
from
like
group
plugin
Loop
to
Loop
group
main.
We
are
pointing
Rook,
look
to
a
group
like
it.
So
we'll
have
all
the
document
here.
But
if,
like
user
is
in
a
group
documentation
and
they
want
to
look
more
on
the
crew
side
than
we
are
pointing
from
okay.
B
Okay
and
now
I
get
it
I,
think
that
makes
sense,
because
in
the
crew
plug-in
site,
that's
like
each
command
is
documented.
With
its,
you
know,
functionality
there
about
the
command
itself
and
then
the
Rook
tax
so
show
those
commands
and
then
get
more
information
by
going
to
the
plug
the
crew
plugin
like
area,
okay,
that
that
direction
makes
sense.
Okay,
great.
B
Sounds
good
okay,
so
then
that
is
the
end
of
the
items
that
were
on
the
agenda.
Were
there
other
agenda
items
that
folks
wanted
to
bring
up
that
had
not
yet
made
it
to
the
dock?.
B
Okay,
all
right,
if
there's
nothing
else,
then
we
can
go
ahead
and
adjourn,
I,
believe
and
then
we'll
keep
following
up
on.
You
know
offline
and
talk
syncing
with
Travis
as
well
to
CPS
opinions
on
a
1.10.2
release.
There,
typically
like
I'll,
lean
towards
just
doing
the
regular
Cadence,
but
we'll
stick
with
Travis,
see
if
there's
anything
more
pressing
or
if
he
has
another
opinion,
sounds
good
all
right,
well,
good
to
see
everybody
thanks
for
thanks
for
everyone
coming.