►
From YouTube: 2023-08-08 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
August
8th,
2023
Rook
community
meeting.
We
have
Travis
back
after
a
absence
for
a
couple
of
meetings,
so
your
your
presence
is
more
than
welcome
and
glad
you're
back
Travis.
A
For
sure
for
sure,
for
sure
and
there's
no
doubt
about
it,
you
can
ask
Blaine
as
well
for
because
he
he
ran
the
entire
meeting
last
week
so
because
I
I
had
a
conflict,
so
I
think
Blaine
would
agree
with
me
as
well
all
right
yeah.
So
we
don't
have
anything
coming
up
for
1.10
I,
don't
think
we've
done
a
patch
release
for
1.10
branch
in
a
while
either
so
I
think
we
could
skip
over
that
one.
We
did
the
last
1.11
patch
release
before
the
last
Community
meetings.
A
I,
don't
think
we
need
to
go
through
that
and
then
we
also
don't
have
a
dot
11
yet
plans.
Let's
take
a
quick
look,
though,
at
the
board
and
just
make
sure
there's
nothing
hanging
out
there.
That's
important
to
waiting
for
us
or
anything.
A
A
B
Yeah,
so
this
was
I
mean
we
had
1.12
two
weeks
before
that,
and
this
was
the
first
patch
leads.
Not
I
felt
like
the
release
went
pretty
smooth
the
1.12
and
there
was
nothing
really
burning
as
far
as
the
first
patch
release.
Sometimes
there
are
kind
of
burning
patch
release
needs,
but
this
one
wasn't
too
urgent.
So
we
just
got
out
two
weeks
after
the
initial
release
and
that's
some
basic
things.
There
was
maybe
one
or
two
that
were
more
interesting
to
a
few
people.
B
As
far
as
I
guess
there
was
an
old
pointer
there
related
to
NFS.
There
was
anyway
a
few
good
updates,
but
fortunately
it's
all
going
smoothly.
Oh
no,
all
right,
urgent
issues
today
give
me
a
call.
A
Well,
that
sounds
good.
Let's
take
a
look,
then
at
the
1.12
project
board,
because
we
do
have
a
dot
two
patch
lease
that
we're
thinking
about
about
a
week
from
now.
So,
let's
take
a
look
at
the
project
board:
the
state
of
everything,
nothing
in
the
blocking
release,
column,
but
a
couple
things
that
are
being
worked
on:
the
small,
smaller
right
there
we
go.
B
Yeah
and
that
would
be
the
two-week
Cadence
to
just
get
in
I,
don't
know
of
anything
urgent
either
here.
But
honestly,
I
was
just
realizing
that
I
need
to
get
back
in
the
habit
of
reviewing
this
project
board
to
make
sure
we're
up
to
date.
But
I
did
not
do
that
for
today,
yeah
just
some
nice
tabs
as
far
as
the
Cozy
driver
and
then
the
helm,
Charter
group.
A
C
A
You
Travis,
when
you
like,
you
I
know
you
were
tied
to
not
tied
to,
but
you
were
a
big
fan
of
like
mini
Cube
and
also,
like
you
know,
vagrant,
multi-vm,
setups
and
stuff
for
a
long
time.
Do
you
use
kind
at
all
to
for
your
testing
ever.
B
B
A
Cool
and
then
is
there
anything
here
on
the
board
that
Travis
that
you
knew
you
know
we
want
to
clean
up
a
little
bit,
but
anything
you
wanted
to
call
it
specifically
of
hey.
This
is
you
know
it
burn?
This
is
really
important
and
we're
gonna
block
the
dot
two
patch
until
until
this
is
done
or
anything
like
that,.
A
B
Have
a
number
and
then
Santosh
we're
looking
at
this
there's,
not
an
issue
yet,
oh
the
just
to
talk
through
real,
quick
step
osds
if
they
fail
and
restart
too
often,
then
it
gets
into
this
mostly
flapping
state
that
Steph
tries
to
avoid.
So
what
Seth
does
is
it
will
actually
exit
the
OSD
with
a
success
code
if
it's
flapping
too
much,
and
that's
let's
see
if
that
one?
No,
it's
not
a
success
code
anyway,
with
it
exits
with
a
certain
code
where
we
don't
actually
want
the
Pod
to
restart
and.
C
B
Oh,
he
did
open
one
okay
right,
okay,
so
the
OSD
does
exit
with
a
Code
Zero
if
it
doesn't
want
to
restart,
and
the
idea
is
that
the
OSD
pod
should
only
restart
on
failure
so
that
we
can
avoid
the
flapping
state
if
we
just
stop
restarting
the
putt
foreign,
but
it
looks
like
deployments.
Don't
support
the
restart
on
failure.
Policy
is
what
he
opened
that
issue
for
I,
guess
so
into
figure
out.
What's
up
with
that
anyway,
it's
a
discussion
in
progress.
That's
interesting,
I,
guess
my
day
responded
on
it
too,
but
nice.
B
Yeah
I'll
add
that.
A
Real
quick
cool
sounds
good
yep,
it's
12,
1,
12,
682
yeah
got
it
alrighty
cool.
So
then,
as
Travis
mentioned,
then
we're
looking
to
get
into
that
regular
Cadence
of
patches
two
weeks
from
the
last
batch
of
you
know
the
dot
one
on
August
1st,
so
the
dot
two
on
August
15th,
two
weeks
from
the
dot
one
went
through
our
things
on
the
1.12
project
board.
Nothing
major
to
call
out
there
anything
else
that
folks
want
to
bring
up
for
Milestones
patch
releases,
all
that
sort
of
stuff.
B
And
I
was
thinking
about
1
1.13
might
be
just
briefly,
because
kubecon
will
be
around
that
time
frame
and
oh
yeah
I'm
putting
together
this
kubecon
video
we're
trying
to
figure
out
what
to
say
in
the
video
three
months
in
advance
about
the
next
release.
But
probably
the
next
release
would
be
November
or
December.
So
beyond
that,
I
didn't
get
very
far.
A
A
Kubecon
in
Chicago
is
like
the
very
very
beginning
of
the
first
week
of
November.
So
so
it's
not
very
far
into
that.
You
know
expected
timeline
of
November
December,
but
if
you
know
there's
there's
you
know
desire
to
have
released,
or
you
know
to
have
coincidence,
to
have
timing
that
aligns
with
coupon.
You
know
that
can
always
make
sense.
A
Yeah
that
yeah
exactly
do
you
want
to,
but.
A
Let's
capture
that
that
way,
and
then
you
want
to
kind
of
parlay
that,
on
into
the
you
know,
video
here.
B
Sure,
here
yeah
so
there's
this
60
second
video
that
I
think
is
incubating
and
graduated
projects
are
being
invited
to
do
they'll
be
shown
during
the
Keynotes
at
kubecon.
So
it's
kind
of
cool
they.
They
started
at
the
last
kubecon
doing
this
and
got
all
sorts
of
guidelines
in
place
to
make
sure
it's
high
quality
and
consistent
and
everything,
but
I'm
just
trying
to
dig
through
that
and
figure
out
what
to
say
for
60
seconds,
because
it's
not
much.
B
But
what
what's
the
right
thing
to
cram
in
there
it's
due
by
Thursday,
so
yes
it'll
happen
soon.
Yeah.
A
The
the
speaker
notes
that
they
have
in
the
the
template.
Travis
I
found
those
to
be
helpful.
At
least
you
know
to
kind
of
it
gave
a
bit
of
a
framing
for
how
to
speak
about
the
project
three
months
ahead
of
time.
You
know
it
says
you're
not
going
to
focus
as
much
on
you
know,
hey
we
just
released
the
one
dot,
you
know
13
release
and
this
this
feature
we're
in
it.
It's
more.
A
Like
the
you
know,
high
level
sort
of
things
of
like
hey
big
progress
from
the
project.
You
know
that
it's
somewhat
current
throughout
the
year
here
and
then
like
kind
of
helping
it's
it's
also
about
helping
people
understand
what
the
project
is
too.
You
know
there's
like
a
slide
for
what
is
you
know?
What
is
the
project
getting
people
in.
A
Valuable
to
me
honestly,
yeah
exactly
more
than
like
hey
this
concrete
thing
happens
on
this
date.
It's
more
about
hey!
This
is
Project.
This
is
what's
going
on
or
this
is
why
it's
useful
to
you.
This
is
new
stuff.
We've
done
to
make
it.
You
know
more
impactful
for
the
ecosystem
and
then
here's
ways
to
get
involved
and
like
that
framing
of
it
makes
a
little
bit
more
sense
to
do
three
months
ahead
of
time,
but
you
know
still
not
perfect.
B
A
Much
effort
has
to
be
put
in
the
slides,
very,
very
good
question,
but
I
I.
What
I
was
understanding
or
interpreting
is
that
you
know
like
something
they
do
is
like.
They'll
have
video
but
like
on
one
screen
and
then
like
another
screen
can
have
slides
as
well.
So
I
would
put
as
much
effort
into
it
as
possible,
just
like
to
assume
that
those
lights
could
be
shown
on
a
big
screen
at
a
keynote
right.
A
I
think
them
or
whatever
that's
that's
all.
That's
all
of
them
got.
B
A
Yeah
I
think
that
was
that
was
in
response
to
my
question
also
that
was
that
was
exactly
me
that
I
asked
that
right.
Okay,
because
like
in
the
template,
it
doesn't
have
you
know
like
the
body
text,
it
isn't
set
to
a
reasonable
form,
like
you
know,
font,
size
and
color,
and
all
that
stuff
right.
A
Just
picked
something
big
enough
to
fill
up
the
slide
that
matches
color
wise
enough
and
and
called
it
a
day
like
I'm
surprised
they
don't
care
about
that
consistency,
but
I
I
think
he
was
like
planning
on
kind
of
like
tweaking
stuff
as
well,
so
but
but
at
the
bot.
At
the
end
of
the
day,
I
we
put
it
I
put
enough
effort
into
the
Crossway
ones
list
so
that
like,
if
they
do
show
it,
it
won't
be
embarrassing
and
people
can
read
it
right.
That's
that's
my
that's
my
guidance,
yeah
cool.
B
A
Cool
anyway-
and
let
me
know
if
you
need
any
eyes
on
that,
Travis,
like
any
you
know,
take
a
look
at
this
last
second
pair
of
eyes
on
the
slides
or
anything
like
that.
B
A
Totally
cool
all
right
and
then
Travis
we'll
talk
about
ongoing
CI
stability
progression
here,
yeah.
B
Yeah,
the
last
few
weeks
we
had
some
challenges
with
CI
stability.
We
had
the
was
it
the
smoke
suite
and
the
upgrade
Suite
that
were
failing
more
of
the
upgrade
sweep
feeling
consistently
so
I
think
we've
got
most
of
that
under
control
now
or
fixed.
Now,
thanks
to
a
lot
of
shubham's
efforts
and
and
parth
is
looking
into
some
as
well
I
think
it's
just
the
object,
Suite,
that's
failing
the
parts
and
then
only
jiffing
to
look
into
some
things
too
and
then
there's
another
one
with
a
multis
test.
B
The
other
shobon's
gonna
look
into
it.
So
anyway,
it's
it
has
been
a
challenge
but
I
think
we're
looking
better
now,
yeah
Siobhan
any
comments
around
that.
C
B
Yes,
I
open
an
issue
for
multis
at
least
find
that
or
I
can
edit
afterwards,
but
yep.
We
need
to
track
all
that
stuff.
B
A
Yeah,
it's
good
that
we've
made
it
a
little
investment
here,
so
we're
getting
getting
more
of
us
more
to
a
level
of
more
stability.
B
B
The
way
the
the
instability
was
triggered
by
something
that
seemed
out
of
our
control,
like
it
wasn't
a
specific
thing
that
we
cause
with
our
code
changes.
So
just
we
had
we've
had
to
change
some
timeouts
and
change
the
network
settings
and
things
like
that
for
I
assume
GitHub
action
is
changing.
Some
things
that
affected
us,
but
yeah.
A
Yeah
and
that's
mostly
kind
of
opaque
for
us
right,
I
assume
like
it's
like
the
internal.
You
know,
architecture
and
working
inner
workings
of
the
GitHub
actions
Runners
and
all
that
sort
of
stuff
is
yeah.
Don't
have
a
great
idea
of
the
environment.
A
Cool
great
okay,
awesome,
so
that's
the
end
of
the
agenda.
Doc,
then,
is
there
anything
else
that
didn't
make
it
to
the
doc
that
folks
wanted
to
bring
up
while
we're
still
here.
A
All
right:
well,
then,
if
that's
everything,
then
we
can
go
ahead
and
adjourn,
and
then
before
next
meeting
we
expect
to
have
1.12.2
outs
and
available
for
the
community.