►
From YouTube: 2021-12-14 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
so
the
recording
has
started-
and
this
is
the
december
14th
2021
rook
community
meeting.
Thank
you
travis
for
covering,
while
I
have
not
been
able
to
attend
with
some
conflicts
and
vacations
recently,
but
here
we
are
to
get
started
today
on
the
14th,
typically
typically
travis.
Typically,
we
start
with
the
milestone
checkups.
So
we
have
a
couple
of
releases
that
we
are
planning
to
do
later
on
this
week.
First
of
all,
another
patch
release
to
get
to
double
digits
here
on
1.7.
A
B
This
might
be
our
last
bi-weekly
release.
Well
I
mean
it
won't
help
that
we
have
the
holidays
coming
up
anyway,
but
let's
get
the
dot
10
out
and
yeah
the
one
critical.
What
I'm
remembering
is
that
the
on
newer,
let's
see
on
kubernetes
1.22,
a
few
people
were
hitting
an
issue
with
the
osd
prepared
jobs
not
being
able
to
run
on
certain
nodes
that
their
name
is
just
the
right
length
and
had
just
the
right
characters
in
it
with
dots
or
dashes
to
where
kubernetes
1-22
failed
because
of
a
bug
in
kubernetes.
A
B
A
And
then
we
could
talk
about
the
first
pass
released
in
for
1.8,
since
that
release
was
fairly
recent,
so
was.
A
C
B
B
B
We
have
had
a
few
issues
open
on
the
1.8
release,
with
some
of
the
big
changes
we
had.
There
were
a
couple
of
regressions
and
I
tried
to
fill
in
the
blocking
release.
Column
make
sure
it's
up
to
date,
so
we
can
get
a
patch
release
out
on
thursday.
Is
the
target
with
those
fixed
those
critical
fixes
in
there?
B
Let's
see
just
to
look
through
there,
so
there
there
was
a
pretty
big
artifact
or
our
effect,
our
back
our
refactor
or
move
around.
That
blane
did
related
to
the
helm,
charts
and
generation
of
common.yaml
from
the
helm
charts,
and
so
that
we
missed
something
in
there.
So
the
let's
see
so
the
service
monitors
there.
B
Weren't
were
failing,
and
there
was
also,
I
think
that
was
related
also
to
the
next
issue
there,
with
permission
denied
on
the
watch
active
sidecar,
so
that
one
affects,
if
you
have
multiple
managers
running
the
multiple
managers
fail,
so
the
work
around
there
is
people
need
to
use
one
manager
until
he
gets
picked
out.
B
And
then
teeny
was
removed
from
our
containers,
so
the
direct
mount
toolbox,
the
ammo
example
just
hadn't
been
updated
and
then,
let's
see
oh
really
unrelated
to
the
1.8
release,
was
the
seven
with
us
16.2.7
release
and
that
came
out
on
wednesday
just
the
day
before
our
rook
release.
B
So
it
it
looked
like
it
was
the
same
sort
of
timeline,
but
that
upgrade
for
ceph
has
an
issue
that
we
need
to
work
around
in
rook
where,
before
we
upgrade
the
monitors,
we
need
to
set
this
mds
skip
sanity
check
and
then
after
the
mods
are
upgraded.
Then
we
re-enable
that
so
I've
got
a
pr
in
progress
for
that
one
and
just
need
to
finish
that
up
today,
but
I
think
yeah
we've
got
fixes
in
progress
for
all
of
these
and
I
think
we'll
be
good
for
thursday.
A
B
A
Any
other
ones
that
are
like
in
progress
here,
perhaps
that
would
be
opportunistically
included
in
the
thursday
release
or
focus
intentionally
focused
on
the
blocking
release.
B
Well,
in
the
review
in
progress,
there's,
let's
see
not
the
first
one,
so
the
second
one
in
that
list
for
dealing
with
pools
and
defaulting
yeah,
yeah,
okay,
there's
kind
of
a
big
change,
really
a
feature
that
I
would
have
preferred
to
get
in
the
minor
release
itself,
but
I
think
it's
important
enough,
we'll
just
get
it
into
the
dot
one
release.
So
this
feature
is
really
the
ability
to
configure
the
default.
B
Are
built-in
cell
pools
so
there's
two
of
them?
There's
the
device
health
metrics
cool
which
ceph
just
creates
automatically
for
us,
and
it's
used
internally
for
actually,
I
don't
even
know
what
all
health
metrics
set
puts
in
there,
but
it
is
created
by
default
and
that
we've
had
no
way
to
configure
it.
B
You
just
had
to
use
the
it
would
use
the
default
replication
and
there
was
you
had
to
go
to
the
toolbox
to
configure
it
so,
the
way
now
to
configure
it
will
be
create
a
set
block,
full
cr
with
that
that
name
in
it,
and
then
we
will
go
and
configure
it
now.
The
the
tricky
part
here
really
was
why
you
couldn't
create
the
blackpool
cr
for
it
before
is
that
the
name
has
underscores
in
it,
and
the
kubernetes
resource
name
does
not
allow
underscores
or
dots.
B
B
A
Awesome
anybody.
A
Yeah
anybody
else
like
seven
blaine,
are
here
now.
Anybody
else
want
to
add
anything
for
1.8
that
won
the
first
patch
this
week.
D
Not
much,
I
think,
we're
on
track.
I
just
need
to
test
one
thing
for
watch
active
on
openshift,
I'm
like
100
sure
it's
gonna
work
on
openshift,
but
yeah.
Well,
I
guess,
did
you
say
100
well,
yeah
99.
Maybe
I
guess
so
yeah,
I'm
just
just
like
just
strapping
the
cluster
and
I'll
test
that
out
shortly
and
that
should
be
in
time
for
for
the
release.
A
Okay
and
then,
as
mentioned,
we
added
a
link
to
the
blog
post
here
in
the
community
meeting
agenda
for
1.8.
So
if
you
haven't
gotten
a
chance
to
read
all
the
features
and
effort
and
progress
that
went
into
1.8,
it
is
available
in
that
blog
post.
There.
B
A
B
B
C
C
C
B
C
C
So
that's,
I
guess
some
of
the
confusion
there,
but
yeah.
I
think
we
can
probably
given
that
the
user
hasn't
responded,
but
since
they're
effectively
the
same
with
just
a
different
default
setting
move
forward
with
the
first
one
I
suggested-
and
I
did
add
that
user
as
a
co-author
on
the
on
the
commit.
So
I
I
hope
that
is
acceptable
for
them.
C
I
also
see
from
the
chat
we
have
a.
We
have
a
question
from
user
abdulilah,
I'm
not
sure
if
I'm
pronouncing
that
correctly,
but
should
we
should
we
answer
that
or
are
there
questions
here.
B
B
I
said
that
so
one
dot
I
mean
we
want
to
get
1.8.1
now
there
are
a
few
critical
fixes
that
will
need
to
be
in
there,
but
other
than
that.
It's
yeah.
It's
really
a
personal
preference.
If
you
want
to
go
with
1.7
since
it's
it's
kind
of
stabilized
for
longer
or
one
I'd
say
1.8.1
for
new
deployments,
that
would
be
my
recommendation
but
other
thoughts
on
it.
C
A
A
That
in
the
entertain,
the
document
as
well
cool,
okay,
we'll
keep
moderating
the
chat
to
see
if
more
questions
come
up.
That's
definitely
useful
to
get
those
addressed
during
this
meeting
here.
Okay,
so
quick
note,
then
that
the
next
meeting
here
two
weeks
from
now
will
be
cancelled
due
to
holiday
period.
I
think
a
lot
of
people
will
be
offline,
so
we
will
just
skip
next
week,
and
it's
already
mentioned
here
in
the
agenda
doc
as
well,
and
we
will
pick
it
back
up
in
the
new
year.
A
So
yeah
everybody-
I
hope
everyone
has
a
happy
holiday
season
and
yep
we'll
see
everyone
in
the
new
year
there
all
right.
So
there
was
a
discussion
around
the
old
rook
dev
mailing
list
there
and
it's
a
value
or
a
lack
thereof.
A
The
one
thing
I
wanted
to
add
to
it
that
may
not
have
been
discussed
before
is
that
that
is
what
is
used
currently
for
a
community
meeting
calendar
appointment
being
you
know
added.
So
when
you
join
the
rook
dev
mailing
list,
google
group,
I
guess,
is
a
better
way
to
describe
it.
Then
you
automatically
get
the
community
meeting
calendar
appointment
added
to
your
calendar
as
well,
so.
A
Before,
in
the
conversation
around,
you
know
deleting
or
disabling
this,
this
old
group,
but
that
is
something
to
consider.
B
A
It
yeah,
I
I
don't
bring
it
up
as
like.
A
This
is
critical
and
you
know
it
must
be
protected
because
because
of
that,
but
is
something
to
consider
if
we
continue
to,
I
mean
it
seems
like
most
of
the
time
the
attendance
this
meeting
is,
you
know
like
a
core
crew
and
then
folks
come
in
as
needed,
and
so,
if
they're,
seeing
that
from
you
know
from
slack
or
if
we're
maybe
posting
it
on
twitter
also
could
be
effective
for
not
doing
that,
then
that
could
be,
you
know,
probably
reaching
an
audience
more
effectively
than
membership
in
rook
dev.
Google
group.
B
Exactly
yeah,
I
just
think,
there's
other
ways:
people
can
join,
but
yeah
we've
got
a
couple
who
have
joined
beyond
the
quarter
crew
today,
just
curious
for
your
input.
If,
if
you
care,
if
we
close
that
rook
dev
google
group.
A
B
In
honor,
sorry,
on
a
related
note
jared,
even
we
have
two
other
mailing
lists
too.
There's
the
rook
info
for
cncf
and
there's
the
the
rook
security
email
list.
So
I
mean
we
definitely
need
the
rook
security
email
list.
In
case
someone
wants
to
report
something,
but
even
the
rook
info
mailing
list
is
well,
it's
pretty
much
only
for
spam
right
now.
So
should
we
even
close
that
one
or
is
there
some
other
use
that
we
need
to
keep
it
open
right?
A
I
it
would
be
good
to
confirm
with
amy,
maybe
of
like
did
I
have
a
requirement
around
a
project
you
know
must
have
a
certain
set
of
mailing
lists
within
the
cncf
mailing
list
framework
there
yeah
the
security
one
I
agree
is
absolutely
it's
part
of
our
security
disclosure
framework
and
policy.
So
we
have
to
keep
that
one.
That's
that's
a
must,
but
the
info
one
is
is
of
questionable
value.
Also
so
yeah,
let's,
let's
stick
up
with
enemy
and
see.
If
we
can
remove
that.
B
B
But
I
think
we
agree
we'll
go
ahead
and
close.
The
rook
deb
mailing
list
consider
the
cncf
info
on
foreclosure,
but
maybe
just
remove
well,
I
mean
remove
the
dev
mailing
list
from
the
github.
I
think
that's
the
only
reference
to
it
and
then
we'll
can
we
mark
it
as
archived
or
or
just
close
it.
I'm
not
sure
how
that
works.
A
Yeah,
I
I
think
it
I
I
don't
know
I
can
look
at
the
google
group
settings
and
see
what
sort
of
functionality
it
exposes
for
deprecating
obsoleting,
closing
archiving
whatever
it
is
I'll
see
what
they
have
available
and
then
the
I
just
wanted
to
like
do.
A
real
quick
brainstorm
also
is
is
that
mailing
list,
or
that
google
group
used
for
gating
access
to
any
other
resources
we
can
think
of.
A
D
Yeah,
can
we
so
depending
on
like
if
we
can
archive
or
archive
it?
I
think
it's
great
if
we
can
leave
a
message
to
and
an
archive
or
send
out
an
email
saying
that
we're
closing
the
mailing
list
so
that
if
we
archive
it,
then
we
we
see
the
late
like.
The
latest
message
was
like:
okay,
hey.
We
are
just
moving
over
to
github
discussions,
for
example.
I
think
that'd
be
great
too
so
then
we
move
out.
Whoever
has
subscribed
to
that
meeting
is
we
just
send,
send
some
sort
of
a
shutdown
notice.
A
A
All
right
cool
sounds
good
and
then
so
I
could
follow
up
on
that.
Then.
Just
to
make
sure
all
that
happens,
and
I
can.
B
A
B
I'll
be
mean
yes,
yeah
seriously,.
A
Okay,
cool
all
right
again,
take
a
note
for
that.
Okay,
so
that's
everything
that
was
on
the
agenda
here.
Did
people
have
other
topics
that
they
wanted
to
bring
up.
A
I'll
take
one
more
look
at
the
chat.
Also,
it
doesn't
look
like
any
more
new
messages
there,
so
yeah.
Okay,
then
that
should
be
everything
from
for
today's
meeting
and
we'll
hope.
Everyone
has
a
happy
holiday
season
and
we'll
see
everyone
in
the
new
year
and
then
in
the
meantime,
on
on
slack
and
places
that
are
not
rook
dev
google
group.
E
A
E
I
didn't
want
to
interrupt.
I
don't
really
have
a
question,
but
I
mean,
since
we
have
a
couple
of
more
minutes,
so
I
thought
that
was
a
good
chance
to
kind
of
get
to
know
their
community
more.
I
was
looking
into
that
issue
about
adding
support
for
like
key
rotation
for
encryption
and
and
I
I
sent
a
br
thanks
sebastian
and
for
the
quick
feedback
on
that.
E
So
I
just
want
to
make
sure
that
you
know
I'm
familiar
with
what
would
be
the
next
steps
and
just
kind
of
getting
more
to
know
the
process
and
and
things
like
that,
yeah.
D
Yeah
thanks
for
submitting
it
was
a
really
good
write-up
and
I
I
know
I
have
to
do
a
second
round
of
review
just
to
address
your
some
of
your
comments
too,
but
yeah
overall,
it
looks
looks
good
thanks
for
yeah,
okay,
so.
D
Just
keep
on
discussing
a
little
bit
just
to
kind
of
finalize
what
we
want
to
do
and
then,
if
you're,
if
you,
if
you
want,
you
can
just
start
the
implementation,
I
guess.
E
Okay,
do
you
want
maybe
a
more
detailed
like
design,
diver,
a
design,
doc
or
something
like.
E
Or
or
maybe
just
kind
of
start,
where
I'm
kind
of
prototyping,
so
I
I'm
new
to
both
through
concept.
So
just.
D
Kind
of
I
guess
yeah
we're
not
like,
I
think
we
like
having
designs,
but
it
doesn't
have
to
be
like
super
thorough,
with
all
the
details
and
just
like
with
the
api
examples,
and
things
like
this.
There
are
things
we
also
like
to
talk
over.
B
D
And
code,
as
opposed
to
just
like
setting
everything
in
stone
in
as
a
markdown
document,
so
we
just
we're
just
trying
to
find
the
right
balance
and
I
think
that's
the
right
balance
for
us,
where
we,
we
have
a
good
design
overview
document
where
we
know
where
we're
going
and
then
we
just
like.
D
E
All
right
sounds
great,
we'll
follow
up
on
that
then
yeah.
A
A
Right
on
right
on
okay
cool,
then
I
think
that
probably
wraps
everything
up
then
so.
Yes,
thanks
everybody
good
to
see
everybody
today
and
we'll
see
each
other
online.
Then.