►
From YouTube: 2023-05-16 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
recording
has
started,
and
this
is
the
May
16th
2023
Rook
community
meeting.
So,
let's
jump
on
into
our
latest
Milestones,
we
don't
have
an
upcoming
patch
release
for
the
1.10
branch.
Nothing
planned
on
that
one.
So
I,
don't
even
think,
there's
anything
to
look
at
that
on
the
project
board.
If
we've
got
nothing
coming
up
for
that,
so
let's
kind
of
jump
into
1.11
then,
and
let's
quickly,
review
the
latest
release
from
there,
which
looks
like
it
was
on
May
2nd,
which
I
was
not
around
for.
A
Let's
look
at
the
is
that
the
right
yeah
there
we
go.
Let's
look
at
the
1.11.5
release
from
May,
2nd,
then,
and
check
all
lots
of
highlights
here.
B
Sure,
let's
see
that
was
just
our
or
bi-weekly
release.
We
had
a
number
of
fixes
in
there,
let's
see
which
ones
to
call
out
k8s
reference.
Api
references
were
updated.
Oh
a
nice
one
from
Blaine
was
reducing
the
size
of
the
Seth
NFS
crd.
It
was
pulling
in
a
whole
bunch
of
child
settings
that
we
just
never
used
so
clean
those
up
and
it
we
were
having
issues
with
the
crds
being
too
big
before
so.
People
couldn't
even
use
a
coupe
cuddle,
apply,
command,
I,
think
or
replace
one
of
those.
B
So
if
there
are
a
couple
of
commands
that
are
really
similar
and
but
subtle,
slightly
different,
they'll
replace
and
apply
I
think
we
could
use
one,
but
not
the
other
one
that
got
too
big.
So
we
just
updated
the
docs
to
use
the
other
one
got
it.
It's
all
resolved.
Now,
since
it's
reduced
again,
it
literally
cut
like,
was
it
5
000
lines
out
of
the
crd
animal
when
we
reduce
that
one.
A
B
A
B
Yeah
and
the
one
in
progress
there
from
saturu
it's
he
pushed
it
fixed
for
it
I
think
he
was
testing
it
I
need
to
review.
If
it's
it's
ready,
he
said
it's,
he
asked
for
review,
so
it
might
be
an
interesting
one
to
get
into
the
release
today.
If
we
feel
like
it's
ready
just
yesterday,
he
said
he
was
still
testing
it
and
I
haven't
reviewed
his
updates.
Today,
people
have
been
asking
this
for
for
a
bit
resize.
It
lbm
based
lsds,.
A
So
yeah
yeah
I
got
it.
It
looks
like
yeah,
he
was
pushing
come
in
the
commits
in
and
getting
a
review
from
you
earlier
today.
In
fact,
now
that
you're
online
in
your
time
zone
too.
A
During
during
public
meetings,
I
Leave
Myself
signed
off
because
you
know
any
sort
of
like,
like
customer
related
like
information,
the
LinkedIn
from
private
repos
into
the
activity
feed.
Don't
don't
want
to
show
any
of
that
stuff
on
public
recorded
channels,
good
point
so
I
stay
signed
off
all
righty,
okay,
cool
and
then
so.
That's
the
only
thing.
That's
in
progress
or
implementation
progress.
It
looks
like
there's
another
pull
request
that
is
in
review
already
as
well
any
chance
for
that
making
it
today
as
well.
A
Movement
on
it
at
least
three
weeks
ago,
okay,
cool
and
then
otherwise,
the
regularly
scheduled
recurring
every
two
weeks
type
of
releases
is
the
intent
of
today
for
this
patch.
Yes,.
B
A
See
yeah
it'd
be
good
anyways
too,
to
when
you
take
a
look
at
that
PR
to
assess
you
know
any
sort
of
risk
that
it
may
have
for
you
know,
even
if
it
is
ready,
if
there's
is
there's
risks
that
would
be
incurred
for
including
another
release
today
also.
A
You
take
a
look
at
it:
yeah
cool
okay,
so
that
is
that
looks
like
everything
for
the
1.11.6
release
scheduled
for
today,
and
then
we
still
have
a
fair
amount
of
time.
A
couple
of
months
left
in
the
cycle
for
1.12
as
well
Travis,
do
we
have
a
project
board
for
that
as
well?
Pretty
if
you
do.
B
A
I'll
just
go
ahead
and
Link
it
here,
so
it's
available
in
the
agenda
doc,
okay,
cool
anything,
then
that
we
want
to
go
ahead,
go
over
for
that's
already
on
the
1.12
board,
keeping
in
mind
that
it's
still
being
fleshed
out,
and
there
will
be
more
things
that
will
be
added
later
on.
B
Right
and
I
think
later
in
the
agenda,
doc
I
pointed
out
that
so
the
roadmap
is
updated
in
the
repos,
the
roadmap
for
1.12
it
just
has
basically
list
these
features
that
some
of
these
issues
we
have
in
the
board
here
so
there's
I
mean
qazi,
will
be
the
big
feature
or
one
of
the
big
features.
I
think
you
can
get
that
that
done
in
time
and
then
what
else.
B
Node
fencing
for
application
failover
is
an
important
one,
based
on
the
new
kubernetes
node
taint
for
an
out
of
service
node.
Now
so
that's
yep.
That's
an
interesting
one
for
our
oldest
active
Rook
issue
1507.
My
favorite
number.
A
And
Travis,
what
what
versions
of
kubernetes
will
that
will
that
work
on,
because
it
has
to
have
that
that
no
taint,
you
said.
B
Exactly
I
believe
it's
more
than
25
or
newer.
Okay
I'd
have
to
double
check,
but.
A
It's
pretty
new
yeah,
that's
that
is
a
issue.
Long
talked
about
issue
that
did
not
have
suitable
support
and
infrastructure
that'll
be
really
exciting.
To
see,
see
progress
on
that
one
really
cool.
B
Know
you
gotta
forced
lead,
pods,
you
gotta,
go
delete,
volume,
attachments
and
things
so
anyway,
so
be
a
much
better
experience.
At
least
around.
A
Cool
sounds
good,
so
this,
then,
is
the
identified
items
that
we
have
and
then
we're
not
12
roadmap,
and
then
the
1.12
project
board
should
largely
reflect
that
perhaps
maybe
a
couple
things
that
are
out
of
sync
from
the
roadmap,
but
the
intent
is
to
have
this
project
for
capturing
everything
in
the
roadmap
as
well.
A
A
I
heard
excellent,
okay
cool,
then,
if
folks
don't
have
anything
else,
they
want
to
include
in
our
Milestone
checkup.
Section
quick
review
is
that
we
will
have
a
1.11.6
release
out
today,
perhaps
depending
on
on
one
PR
there,
that
we
want
to
assess,
assess
for
including
and
maybe
check
on,
maybe
push
the
release
to
tomorrow,
but
that
should
be
coming
very
soon
at
least,
and
then
the
1.12
project
board
will
be
updated.
A
A
little
bit
more
about
the
roadmap
has
been
committed
and
updated
in
the
main
main
roadmap
entry
for
the
in
the
in
the
Rookery
bulb.
So
that
is
the
direction
at
least
for
what
we
are
we're
expecting
to
be
delivering
in
the
1.12
time
frame,
all
right.
So
let's
move
on
down
to
the
community
topics
section
then
so
yeah.
So
it
looks
like
the
cnccf
monthly
meetings
we
had
with
them
have
been
officially
canceled.
Now.
B
Oh
yeah,
those
are
canceled
but
there's
a
link
there.
We
can
schedule
it
on
demand,
meeting
with
I
assume,
with
her
or
or
others
on
the
whoever
the
cncf
project
coordinators
are
to
figure
things
out,
but
I.
Think
in
general
we
haven't
had
a
lot
of
a
lot
to
talk
about
in
those
meetings
anyway,
so
we
can
just
think
up
on
slack,
probably
in
general,
with
her
she's
really
responsive
on
the
cncf
select.
B
A
C
A
That's
what
I
got
when
I
clicked
on
clicked
on
this,
but
it
just
got
to
a
new
place
in
Brussels
here
and
maybe
this
first
time
trying
to
connect
to.
A
A
B
Yeah
exactly
so
the
she
said
that
oh
yeah
they'll
put
us
on
the
list
for
bigger
conference
rooms
for
the
project
or
the
maintainer
suggestion
to
maintain
your
talks.
Somehow
we
were
on
not
on
a
big
conference
room
list,
so
we
got
a
really
small
conference.
Room
did
I
tell
you
about
this,
so
there
were
72
seats
in
the
room
and
650
people
registered
so
that
doesn't
oh
geez.
B
A
That
so
many
people
were
turned
away
too
bad.
They
couldn't
be
accommodated,
though,
has
the
the
recordings
are
out
now.
I
I
saw
an
email
from
that
did
was
that
has
that
been
shared
with
the
community
like
over
slack
and
stuff,
to
the
recording
of
the
talk
and-
and
you
know
so,
people
can
see
that
and
if
they're,
especially
if
they
weren't
able
to
get
into
the
room.
A
Cool
yeah
I
definitely
do
that,
so
folks
can
see
it
and
catch
up
cool,
nice,
okay,
great
and
then
yeah.
If
we
need
to
meet
up
with
cncf
folks,
then
we'll
do
that
at
recess
we
talked
about
the
roadmap
getting
updated
for
1.12,
so
there's
a
link
to
the
specific
PR
in
which
that
was
updated.
We
can
move
on
then
to
the
next
one,
since
we
already
talked
about
that
there's
a
documentation
cleanup,
that's
in
progress
of
Travis.
B
Yeah,
so
it's
definitely
Khan
I
had
a
chat
with
the
Seth
docs
owner,
I'm
gonna
forget
his
name
on
the
spot,
I'm,
sorry,
but
anyway,
it's
a
great
discussion.
I
mentioned
it
in
our
last
Community
a
couple
weeks
ago,
but
just
to
review
a
couple
of
things.
I'm
kind
of
going
through
and
looking
I
mean
obviously
I'm.
Looking
for
old
content
as
I
go
through
the
docs
and
but
also
kind
of
for
consistency.
B
Looking
for
how
to
speak
more
directly,
instead
of
you
might
want
to
do
this
or
maybe
consider
this
just
remove
those
kind
of
iffy
words,
people
will
do
what
they
want
to
do
anyway.
We
just
tell
them
what
we
think
they
should
do
and
be
direct
and
avoid
the
word
you
in
general,
it's
kind
of
standards
for
documentation.
A
The
topic
come
up
at
all
about
any
available,
tooling
to
like
linting
for
the
docs
to
make
sure
that
these
rules
are
adhered
to.
You
know
in
a
in
PR
future
PRS
for
them.
B
Now
we
can
talk
about
that.
We
already
have
linters
for
spelling,
for
example,
in
all
the
dots,
but
that
helps
alrightings,
but
yeah
I,
don't
know,
it'd
be
a
hard
winter
to
probably
have
because
it's
more
about
grammar
and
phrasing,
because
you
don't
want
to
prevent
some
of
these
words,
because
sometimes
you
do
need
work
words
like
might
or
whatever,
but.
A
Cool
okay,
well,
yeah,
thanks
for
they're,
taking
a
stab
at
getting
those
docs,
updated,
Travis
yeah,
you
know
it's
not
like
the
docs
are
getting
Rewritten
and
the
content
is
being.
You
know
completely
started
from
scratch
multiple
times.
So
you
know,
there's
not
a
whole
ton
of
churn
in
the
docks
so
doing
a
pass
through
now
will
largely
keep
them
fairly.
You
know
fairly
in
a
fairly
good
state
for
a
while
I'm
sure.
A
B
A
So
yep,
and
was
this
added
I,
didn't
look
at
the
contents
of
the
PRS?
Was
this?
Were
these
kind
of
rules
or
guidance
guidelines,
were
they
added
to
like
a
contributor
Guide
to
the
dev
guide?
You
know
around,
like
the
docs
docs
guidelines
section
for
these
types
of
rules,
so
we
can
easily
Point
people
at
them
as
opposed
to
having
this.
You
know,
review
and
state
them
over
and
over
again
manually
exactly.
B
A
For
cool
yep
and
then
after
you
get
a
chance
to
codify
that-
or
you
know,
write
them
guidelines
then
and
refer
people
to
that
easily.
Then
that
would
that'd
be
useful,
exactly
cool
awesome,
all
right,
we're
good
yeah
thanks
for
that,
Travis
and
okay.
So
then
a
quick
update
here
about
the
crew
plugin.
B
Yeah,
so
a
lot
of
good
work
on
converting
the
free
plugin
from
bash
to
going
or
Siobhan's
almost
done
with
merging
the
last
couple
PRS
for
that
and
then
I
think
we'll
be
ready
for
a
bug.
Bash
I
want
to
do
something
something
like
that
where
basically
we
need
a
bunch
of
people
to
just
eyes
on
it
and
testing
manual
testing,
because
we've
got
CI
for
it,
but
we
need
some
testing
just
to
make
sure.
B
Like
one
thing
we
discussed
at
kubecon
is
embedding
our
example
manifest
in
the
plugin
so
that
you
can
just
say:
Coupe,
cuddle,
Rook,
create
create
cluster
and
it'll.
Just
create
you
a
test
mini
cubes
cluster,
not
creating
mini
Cube
for
you,
but
deploying
all
the
sample
manifests
nothing
like
that.
Yeah.
A
A
Cool
any
information
about
the
bug,
bash
or
timing
for
that
or
anything
else
that
can
be
shared
now
or
that's
you
know
kind
of
this
is
the
intent
to
do
that.
B
Yeah,
that's
the
intent
yeah.
So
after
these
final
PR's
emerged,
maybe
next
week
or
by
the
next
community
meeting.
Hopefully
we'll
have
more
details.
A
Cool
sounds
good,
all
right
and
then
another
item
here
from
Alex
about
about
orbit.
C
I
have
to
maintain
us
would
like
to
introduce
this
tool
to
have
a
better
insight
into
the
community
in
regards
to
like
who's
using
it.
Is
it
more
bigger
companies,
smaller
companies,
that
we
can
better
focus?
What
features
are
needed
and
to
go
to
the
question
available
tiers?
They
have
like
a
well
special
pricing
for
open
source
projects,
or
at
least
it's
like.
A
That
on
this
pricing,
page
Alex,
or
is
it
like
something
else,
that's
kind
of
like
you
have
to
reach
out
to
them
a.
A
No,
no,
it
would
be
that
it
was
that,
and
it
also
it
looks
like
a
you
know,
sign
up
for
our
newsletter
type
of
box.
Some
of
my
eyes
immediately
are
just
like
nope
like
this
is
not
what
I'm
looking
for
so,
oh
okay,
that's
super
interesting
that
they
have
this
too.
Now.
Did
you
you're
going
to
reach
out
to
them
Alex,
or
have
you
already
had
that
conversation
with
one
of
their
the
Reps
I'll.
C
Are
you
adding
cncf
sponsorship?
As
a
point
main
point
is
really
just
like
that
we
have
something
to
like
combine.
What's
going
on
on
slack,
what's
going
on
on
GitHub,
maybe
even
Twitter,
if
there's
even
still
possible,
to
see
like
who's
talking
about
it
and
so
on.
I
said
like
gaining
some
insights
into
the
community
around
Rook.
C
That
will
better
understand
because
I
think
every
now
and
then
we're
like
yeah,
so
who's
using
Rook
again
and
I
think
that
this
tool
can
help
us
with
that.
I.
Don't
know
if,
like
cross
plane
or
up
on
this
using
it
as
well,
yeah.
A
Crossbane
is
using
it
so
I
have
a
fair
amount
of
experience
with
orbit
already
in
the
free
tier,
and
you
know,
like
the
amount
of
insight
like
yeah,
it's
not
exactly
where
the
intent
that
you
have
here
with
it
Alex
is
what
it
provides
essentially,
and
it
gives
you
a
good
way
to
connect
to
the
contributors
and
especially
I,
like
the
availability
of
you
know.
A
Identifying
who,
who
is
who
is
very,
is
valuable
in
the
project,
so
you
can
nurture
them,
and
you
know
like
do
developer
enablement,
sort
of
things,
and
you
know
maybe
sending
some
swag
to
new
contributors
that
are
growing
in
the
project
as
well.
So
it's
it's!
It
helps
with
that
to
you
know,
really
grow
the
community.
It
does
help
with
that
when
I
was
asking
about
CNC
Shapiro
what
I,
what
I
meant
by
that
is
is
it
is
this?
A
C
Yes,
to
be
honest
right
now,
I
would
just
reach
out
to
orbit
and
see
like
if
I'm,
like
I'm
going
to
mention
hey.
We
are
rogue
scenes
here,
post
the
project
and,
if
they're
going
to
be
like
talk
with
the
cncf,
you
know,
but
if
not
and
they're
like
well,
we'll
see
like
I
yeah
I'll
reach
out
to
them,
they
should
hope
like
they
should
hopefully
know
how
to
handle
a
cncf
project.
If
cncf
does
any
sponsors
of
accounts
for
a
project,
so.
A
Sounds
good,
okay,
so
yeah,
so
yeah
I.
Definitely
think
it's
a
great
idea.
It's
a
very
good
Tool!
You
do.
You
do
have
to
end
up,
maybe
doing
a
little
bit
more
like
sanitizing
or
you
know.
What's
are
these
enrichment
of
the
data
as
well,
so
you've
got
like
good
clean
data.
Sometimes
it's
a
little
gets
a
little
confused
about
some
things,
but
you
know
being
able
to
see
what
you
know:
who's
contributing
in
slack
who's,
contributing
GitHub
who's.
A
C
I
know:
that's
I,
guess
it's
like
it's!
It's
I
think
at
coupon
as
well.
We
talked
a
little
bit
about
it
as
well,
with
like
yeah
so
who's
using
it
like
everyone's
stopping
by
but
yeah.
Well,
you
don't
you're,
not
really
catching
company
names
or
anything,
sometimes
so.
Yeah
Integrations,
available
I
hope
that
this
can
help
us
solve
these
questions
for
ourselves.
A
Cool
man
yeah,
let
us
know
what
you
find
when
you
talk
to
them,
then
alrighty
Travis.
In
real
time
you
were
adding
a
new
agenda
item.
B
Yeah,
just
remembering
that
related
to
this
understanding,
the
community
and
everything
the
so
we've
for
about
a
year
ago,
we
enabled
or
allowed
users
to
enable
the
Telemetry
through
Seth,
and
we
report
Rook
to
Rook
specific
Telemetry,
a
few
data
points
about
the
Clusters
where
they
enable
it,
and
so
we
haven't
had
anything
in
that
Telemetry
dashboard
that
the
Seth
team
has
but
they're
they're
working
on
adding
it
in
the
next
couple
of
weeks.
So
I'm
hoping
soon
we'll
have
something
like
a
rook
dashboard,
at
least
or
some
widgets.
B
That
show
us
some
Rook
information,
but
just
as
a
a
preliminary
thing,
I
think
yerid,
who
owns
the
the
Telemetry.
She
said
that
there
are
about
150
Rook
clusters
with
Telemetry
enabled,
so
we
should
get
some
data
I,
don't
know
how
big
they
are
or
whatever,
but
once
we
have
that
in
the
dashboard,
we'll
start
to
get
some
insight,
which
will
be
helpful
related
to
the
yeah
what's
happening
in
the
community.
We
just
haven't
known
until
now,
so
it'll
be
nice.
B
A
All
right
so
then
that
looks
like
that's
everything
that
was
on
the
agenda.
Doctors.
Anybody
have
any
other
items
that
they
wanted
to
bring
that
wanted.
That.
C
B
A
C
A
A
Cool
and
then
action
item
here
about
setting
up
slack
and
extended
yeah
now
that
I'm
back
from
Super
extended
PTO,
then
this
is
something
I.
Can
you
know
that's
at
some
time
in
the
near
future?
I
definitely
won't
be
doing
it
today,
but
you
know
sometime
I
can
get
I
can
get
to
this
now
and
take
care
of
all
of
it.
B
A
Time
but
like
400
invites
they
they
will
expire
after
that.
So
that's
that's
the
the
kicker
to
watch
out
for.
A
A
All
right,
then,
cool,
well
good,
to
see
everybody
today
and
then
yep.
We
will
follow
up
with
the
1.11.6
release
soon
and
talk
on
Slack.