►
From YouTube: 2022-05-31 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
may
31st
2022
rook
community
meeting.
So
let's
dive
on
into
our
milestones
yeah,
I
don't
think
we
have
anything
driving
a
1.8.10
patch
release.
A
It
looks
like
there's
nothing
in
the
board.
That's
that's
actively
being
reviewed
or
worked
on.
Is
there
anything
in
the
done
column?
Travis?
That's
would
be
driving
a
a
10
patch
or
we're
kind
of
holding.
B
On
that,
I
meant
to
look
on
that.
I
I
feel
like
something
merged
a
week
or
two
ago.
That
would
be
useful
to
go
ahead
and
get
in
the
release.
Just
it
probably
will
be
our
final
8.1.8
release
and
just
say:
yep.
Here's,
the
latest,
there's
a
couple
of
fixes,
I
think,
probably
next
week
we
could
just
do
it
at
the
same
time
as
the
next
1.9
or
these
two
that's
what
I
was
thinking,
but
I
wanted
to
double
check
here.
A
Okay,
so
just
do
it
yeah,
do
it
like
coordinated
with
do
a
patch
for
one
at
eight,
at
the
same
time
as
a
1.9
patch
yeah.
A
Yep,
do
you
want
to
take
a
look
at
the
done
column
here
and
see
if
anything,
jogs
your
memory
on
something
that
would
be
priority.
B
I'm
looking
at
the
commit
history
now
for
1.8:
let's
see
okay,
so
we
did
have.
I
mean
beside
besides
the
docks,
so
we
had.
We
had
to
disable
the
docks
in
the
1.8
branch
because
of
the
new
docks
redesign
design
and
we
didn't
want
to
re
back
port
all
of
that
work
right.
Okay,
so
we
just
disabled
that.
But
since
that
branch
is
pretty
much
done,
we
can
live
with
it
or
do
manual
updates
to
that
branch.
B
That
was
the
idea.
Oh
sub,
back
ported
one
last
week
that
was
about
an
osd,
broken
argument.
I
don't
think
that
would
affect
hardly
anyone,
though.
So
again,
it's
not
urgent,
but
I
feel
like
well.
Maybe
this
would
be
useful.
The
telemetry
so
we're
getting
telemetry
enabled
in
rook
and
yeah
we've
discussed.
That
did
we.
A
Okay,
cool
that
makes
total
sense
to
me
very
reasonable,
okay
and
so
yeah
1.9.5
would
be
coming
up
as
well
along
with
1.88.10.
So
let's
take
a
quick
look
at
the
board
there
and
see
if
there's
any
major
things
to
discuss
or
progress
on
on
items
that
we'd
want
to
be
included
in
that
patch
release.
B
B
That
was
included
in
the
release
for
those
that
default
deployment
version,
but
I
think
otherwise
that
was
just
the
periodic
release.
A
Yeah,
it
feels
pretty
decent.
It
doesn't
seem
like
it's
too,
on
fire,
okay,
yep
and
then
yeah.
We
have
links
to
the
previous
patch
releases
here
as
well,
along
with
when
they're
released.
I
think
that's
that's
a
nice
addition.
We've
made
to
the
agenda
recently
cool
okay,
now
yeah
and
it's
all
right.
So
then
anything
else
on
upcoming
releases
any.
Is
it
too
early
to
start
talking
about
1.10
or
plans
for
that
travis
or
means.
B
A
I
don't
like
uppercase
these
perversions
yeah
and
it's
a
change.
It
normally
really
bugs
me
too.
So
thanks
for
being
yeah,
totally
fair,
okay,
great
so
yeah
any
comments
or
questions
from
folks
on
the
call,
then
about
milestones
and
releases
before
we
move
on.
A
All
right,
let's
move
on
into
the
community
topics
and
questions
kubecon,
valencia,
retrospective
yeah.
I
think
that
yeah
alexander-
and
I
were
there
in
person
in
valencia-
is
anybody
else
here
in
the
call
in
valencia
also.
B
So
yeah,
I
was
definitely
going
to
comment
on
that
so
and
basically
so
blaine
and
I
were
on
that
call-
and
we
were
looking
for
questions
to
answer
and
there
was
a
place
where
we
had
a
couple
comments
for
people
asking
for
questions,
but
we
did
not
see
any
questions
come
in
and
we
neither
were
able
to
get
live
audio
from.
We
didn't
hear
anything
and
we
couldn't
figure
out
how
to
get
our
own
live
audio.
After
the
end,
when
we
had
five
minutes
time
for
q,
a
right
so.
A
B
A
B
We
were,
there
was
an
audio
check
in
the
tool,
and
that
worked
fine,
but
it's
like
there
was
yeah
something
totally
failed.
There.
A
Weird
yeah,
I
wonder
if
that's
like
a
kind
of
a
lapse
in
in
previous
years,
because
you
know
the
last
few
were
virtual
only
so
they
had
like
the
entire
staff
on
the
virtual
platform,
and
you
know
doing
making
sure
that
everything
was
ready
and
connected
and
all
that
jazz
then,
for
this
here
influence
yeah.
It
seemed
like
that
was
you
know.
The
virtual
component
of
it
was
more
of
an
afterthought.
A
That
was
not
the
primary
thing
at
all:
a
lot
of
people
that
were
there
in
attendance
kind
of
forgot
about
the
virtual
part
too.
I
think
so.
It's
it.
B
A
I
did
yeah,
I
ran
into
her.
A
Oh
really,
oh
nice,
that's
cool
yeah!
I
saw
her.
I
went
to
a
maintainer
circle.
Discussion
circle
event
on
site
during
valencia.
That
was
quite
good.
You
know
talking
about,
like
you
know,
managing
projects
and
and
contributing
and
helping
community
grow
and
stuff
like
that,
and
a
lot
of
people
from
upstream
kubernetes
were
there
and
amy
amy
was
there
as
part
of
like
moderating
it
and
running
that
that
event
there?
So
I
I
ran
into
amy
briefly.
A
Cool
yeah,
so
hopefully
travis
that
you
know
we
can
be
in
person
for
the
detroit
keep
going
so
the
next
north
north
america
one
and
then
you
can
get.
We
can
give
our
maintainer
track
session
there
live
and
in
person
and
deal
with
that.
There.
A
Yeah
for
sure,
alexander,
any
any
comments
or
feedback
from
from
you
and
then
mike
also
on
the
the
booth.
The
project
pavilion.
C
I
don't
think
so
it's
to
be
honest.
It
like
the
rook
and
a
few
other
booths,
weren't
necessarily
as
visited
as
other
ones
like
flux
and
well,
even
I
think
crosstalk
but
well
we're
starting
to
say
smallest,
like
a
bit
anticipated.
That's
where
yeah
a.
C
Yeah,
no,
nothing
really
bad,
I
think
maybe,
regarding
like
a
whole
event.
It's
like,
I
think,
for
some
like
the
first
one
or
two
days
where,
like
the
sponsor
showcase,
was
often,
I
think
I
always
had
to
walk
like
a
mile
to
get
some
water
from
the
fountain
somewhere.
C
C
C
B
A
Okay,
yeah
cool-
we
have
really,
it
was
definitely
a
cool
experience
and
being
a
person
was
great
and
seeing
some
talks
and
connecting
with
people,
so
that
was
that
was
great,
and
hopefully
we
can.
We
can
do
even
more
of
that
in
in
in
detroit
detroit
yay
all
right
sweet,
so
anything
so
blaine's,
not
here
travis.
Do
you
want
to
address
his
agenda
item.
B
B
So
we've
already
got
this
deprecation
notice
on
the
cassandra
docks
for
their
that
operator,
so
that
basically
blaine
has
this
pr
linked
there,
which
does
the
same
thing
for
nfs
operator
to
make
it
more
visible
that
that's
deprecated,
there's
just
no
community
support
for
it
and
so
that
pr's
ready
to
merge
we're
just
waiting
for
the
community
meeting
to
go
ahead
and
merge
that,
and
you
know,
unless
somebody
objects
to
it
or
wants
to
step
up
for
maintainership
of
it.
Basically.
B
Always
sad
to
see
old
code
say
goodbye,
but
anyway
that's
what
it
is.
Yep
cool
all
right-
and
I
mean
there
is
nfs
support
inside
the
with
the
separa
seth
operator
yeah.
So
I
guess
that's
what
makes
me
feel
better.
In
that
case
at
least
it's
not
like
the
future
totally
gone.
That's
just
a
different
operator.
A
C
I'm
not
sure
if
you've
had
a
chance
to
look
at
it,
jarrod
so
yeah.
So
these
are
the
new.
This
is
the
new
design
for
the
documentation.
It
has
a
search.
It
even
has
a
like
a
night
mode.
Let's
call
it
night
mode
if
you
yeah,
for
if
or
if
you
need
to
administrate
a
rook
surf
cluster
night
at
night,
yeah,
that's
it's
there.
Now.
C
I
think
the
like
the
biggest
part
is
done
now,
it's
more
or
less
looking
into
rewriting
sections
of
the
documentation
to
like,
for
example,
the
installation
part
making
sure
that
it's
well
more
up-to-date
and
maybe
even
pointing
to
like
hey,
please
use
helm
and
like
basically
making
the
helm,
installation
a
first-class
citizen
so
to
say
and
yeah
so
there
only
those
restructures
or
like
rewrites,
more
or
less
would
be
a
thing
that
would
now
more
and
more
come
in.
C
A
A
A
Comes
up
with
like
volume,
or
something
like
that?
Oh
yeah,
look
at
that
like
the
high
level
pages
and
then
like,
like
you,
know,
previews
of
those
and
that
there's
more
on
them.
That's
pretty!
That's
pretty
cool!
I
like
that.
A
lot.
C
Maybe
just
as
a
sorry
for
all
the
issues
we
had
after
having
it
merged,
but
at
least
like
after
cubicle
I
was
a
bit
well.
It
was
a
bit
flat,
you
know,
but
you
know
having
an
in-person
event
was
something
not
new,
but
you
know
that's
scary.
B
C
C
Now
looks
great
in
most
parts
if
it's
like,
maybe
as
an
additional
point,
if
you
have
a
link
which
is
to
like
https
github.com
rook
rook,
during
building
the
documentation
for
release
branch,
it
will
automatically
replace
the
master
or
like
the
brand
it
is
on
or
whether
it
is
in
the
ul,
with
the
release
1.9
brand,
for
example.
So
if
you,
for
example,
hover
over
the
object,
open
shift,
yellow
link
there
yep
it's
release
1.9,
so
it's
automatically
replaced
during
the
build
which
is
cool.
C
A
C
A
B
A
B
C
Look
into
the
well
issue,
I
think
you
could
even
really
call
it.
That
is
that
sometimes
the
website
is
linking
to
rook.github.io
instead
of
just
rook.o
and
basically,
as
far
as
I
know,
right
now,
the
fix
would
be
to
remove
the
aws
stuff
or
whatever
is
going
on
there
in
front
of
it.
Not
sure
if
you
know
more
about
that
jerry,
but
there
seems
to
be
some
well
weird
caching
going
on
we're
like
so
well.
C
B
A
Like
click
around
on
some
of
this
stuff,
or
I.
B
A
C
C
Be
changing
the
dns
record
to
just
point
to
github
directly
or
something
or
seeing
like
where
it
netlifes
well
doing
some
caching
or
something
I
guess,
because
if
we
would
adjust
the
dns
record
to
just
get
up
to
like
the
rook.get.io
github
pages
would
be
able
to
host
like
the
normal
rook.
I
o,
basically
for
it
on
its
own
and
like
that's
where
the
rook.guitar
is
somewhere
coming
from
yeah.
C
A
C
A
C
Yeah,
I
think
it's
happening
somewhere
in
in
like
the
build
logic
for
the
web
for
the
documentation,
because
the
github
pages
doesn't
have
like
the
you
should
be
on
rook.io
cname
file
or
whatever
you
want
to
call
it,
and
I
have
to.
I
think
that
that
might
be
where,
like
the
build
system
or
like
the
documentation,
versioning
build
system
is
automatically
picking
it
up,
maybe
and
in
the
end
as
it
smallest,
let's
try,
cleaning
it
up
and
either
github
pages
are
like
yeah.
Well,
that
is
simply
easier.
There.
A
Yeah
yeah,
let
us
know
what
you
find
alex
or
if
you
need
like
any
eyes
on
something
to
when
you're
investigating
into
that.
C
A
Cool
you
talked
to
the
instruct
folks
alex.
C
Yeah
they
seem
to
be
offering
like
hands-on
labs,
which
well
seems
interesting
wait.
It's
basically
like
I
think
catacota
is
similar
to
it
where
you
have
like
a
terminal,
and
you
have
instructions
where
it's
like.
Hey
now,
run
cube,
ctrl
create
or
something
and
so
on,
and
they
seem
to
be
able
to
do
something
like
this.
Obviously,
we
would
need
to
create
the
actual
courses
or
well
tutorials,
whatever
you
want
to
call
it
for
that,
but
yeah,
so
it
might
be
at
least
worth
checking
out.
C
So
I
would
probably
just
go
ahead
and
check
them
out
again
and
see
how
easy
it
would
be
to
create
these
courses
or
whatever,
but
this
might
also
be
just
a
thing
to
go,
hands
and
hands
and
hands
with
the
training
videos
which
travis
is
going
to
mention
as
a
next
point
that
we
basically
get
like
the
hands,
the
training,
videos
and
then
like
hands-on
labs,
where
basically,
it's
like
a
kubernetes
cluster
that
gets
spent
up
spin
up
for
them.
We
can
even
attach
additional
disks
and
all
and
so
yeah
I'll.
C
I
have
to
further
check
it
out.
Just
wanted
to
bring
it
up
in
general
if
anyone
has
had
experience
with
that
yet
and
yeah.
B
A
What
sort
of
like
plans
do
they
have
alex
for,
like
you
know,
open
source
community
cncf
projects?
Is
it
like
something
that
they
host
like
like
a
partnership
or
like?
Does
it
like
a
product
that
they,
you
know
want
to
sell
to
to
us.
C
So,
at
least
from
what
was
written
by
well
barry
from
instruct
here
we
go.
Instruct
has
an
open
source
package
of
one
thousand
hours
of
free
consumption
per
year
is
the
something
for
rubraceff
basically,
so
it
might
be
something
I
don't
know
if
they
are
already
working
in
some
capacity
with
the
scenes
they
have,
but
yeah
well,
yeah.
C
Over
a
year,
this
might
be
depending
on
how
many
people
would
use
it
might
not
be
and
like
too
much
but
as
I'd
like,
I
would
check
check
it
out,
see
how
easy
it
is
to
work
with
that,
because,
like
hands-on
labs,
where
people
don't
need
to
sit
on
like
a
mini
cube
or
something
for
us
on
their
own
might
be
well
cool.
For
like
the
getting
started
guide
as
well,
including
like
the
training,
videos,
yeah.
A
Yeah
I
I
could
definitely
see
the
value
of
the
experience
there.
I
might.
I
am
hesitant
to
take
a
dependency
on
something
that
you
know
might
not
be.
B
A
Fit
scaling
or
needs
scaling
wise
stuff,
like
that,
that's
my
initial
hesitation
on
it:
it's
not
the
experience
but
the
taking
dependency
on
on
a
product.
Basically.
C
A
Yeah
travis:
let's:
let's,
let's
dovetail
that
into
the
q
by
example.com
training.
Videos
is
that.
Do
you
want
to
get
into
that
and
see
how
that
might
be
related
here?
Yeah.
B
Yeah,
so
the
that
kubecon,
a
number
of
new
learning
paths
on
that
site
were
announced,
rook
being
one
of
them.
So
if
you
click
on
that
link
there,
that
should
take
you
to
so
I've
got
basically,
I
created
four
different
videos
of
getting
started
with
brooke
and
they've
been
posted
and
they're
publicly
available.
Now,
as
of
the
last
few
weeks,
oh
cool
and
yeah,
so
the
I
mean
I
don't
need
to
be
the
only
one-
that's
posting
there.
B
So
if
other
people
want
to
create
videos,
the
ideas
are
just
you
know,
quick
tutorials
pick
a
topic
and
a
three
to
five
minute.
Video
is
ideal,
I
think,
is
what
they're
looking
for,
and
I've
got
a
list
of
like
20
topics
that
I'd
like
to
get
to
and
just
keep
adding
content
to
this.
B
B
A
Did
you
have
we
have
we
like
disseminated
this
much
to
our
community,
like
you
know,
like
blog
posts,
or
you
know,
on
slack
or
twitter
or
things
like
that,
to
promote
it
a
little
bit.
B
I
posted
it
in
slack
two
or
three
weeks
ago,
but
yeah.
I
need
to
tweet
it
at
least
and
keep
mentioning
it.
Yeah.
A
Yeah,
that
would
be,
that
would
make
total
sense.
I
think
that's
totally
reasonable
for
this,
as,
like
you
know
as
another
resource
that
we
that
we
share
folks
to
be
able
to
get
educated
and
learn
and
be
introduced
to
the
project.
I
think
this
is
great.
We
should
feel
free
to
promote
that
a
little
bit
more
than
you
have
so
far
right
right.
B
A
B
B
What's
a
you
know,
the
difference
between
a
rook
cluster
and
a
non-red
cluster
in
the
cef
telemetry
reports,
and
then
we'll
see
what
version
the
root
clusters
are
installed
and
what
version
of
seth
and
all
sorts
of
stuff
the
theft
team
is
already
you're
collecting
like
about
osds
and
mons
and
all
the
demons,
how
many
pools
and
whatnot,
but
then
also
yeah,
so
that
list
of
metrics
you
got
there,
that's
where
they're
mostly
defined,
what's
implemented
so
far,
basically
or
mostly
different
versions
like
kubernetes
version,
csi
and
rook
version,
and
then
a
bunch
of
cluster
cr
settings
now
to
get
this
data.
B
It
currently
requires
a
toolbox
command
to
go.
Enable
the
telemetry,
so
the
next
kind
of
next
step
is
well.
Let's
make
it
easier
for
people
to
enable
this
so
that
we
get
more
people
enabling
it
and
get
the
word
about
out
about
hey
we'd
love
it.
If
you
enable
cleventry,
it
will
always
be
off
by
default.
But
if
you
don't
mind,
we'd
love
to
have
you
report
it.
So
we
can
see
what
clusters
are
out
there.
B
What
features
are
being
used
and
at
the
same
time
stripping
all
of
the
cluster
identifying
information
and
we
never
report
anything
that's
sensitive
and
whatnot
cool,
but
that's
kind
of
the
overview
there
yeah.
So
we've
been
chatting
with
the
sephora
team
folks
who
were
working
on
the
telemetry
blaine,
and
I
have
and
excited
to
have
this
in
place,
because
we
really
haven't
known
what's
out
there
in
the
wild
for
as
far
as
rook
upstream,
except
when
we
do
a
a
survey
which
has
been
at
least
a
couple
years
right
since
you
did
it
last
year,.
A
Yeah
yeah,
yeah
and
it'll
definitely
be
helpful
to
streamline
the
opt-in
or
enabling
or
turning
it
on
functionality,
so
the
toolbox
command,
you'll
you'll,
definitely
end
up
with
we'll
end
up
with
a
you
know.
It's
the
subset
of
a
representative
example
right
so
being
able
to
streamline
that
I'd
definitely
agree
with.
A
A
All
right
cool,
so
yeah
we
can
go
ahead
and
adjourn
here
and
then
yeah.
We've
got
the
upcoming
1.8.10
in
1.9.5
pax
releases
and
just
getting
started
on
1.10
with
roadmap
roadmap
merged
yeah.
So
and
then
oh
yeah,
quick
reminder
that
there
is
the
cfp
for
kubecon
north
america
is
it
closes
on
friday?
I
think
friday,
like
friday,
midnight
type
of
thing.
So
if
you
want
to
get
a
proposal
in
for
kubecon
north
america,
this
is
the
week
to
do
it.