►
From YouTube: 2022-08-23 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
august
23
2022
rook
community
meeting.
So
we
can
jump
on
into
our
milestones
and
start
talking
about
things
that
are
coming
up.
1.8.
We
don't
have
a
quite
quite
recent
patch
release
and
we
don't
have
an
upcoming
one
or
a
need
for
an
upcoming
one
right
now.
So
I
think
we
can
just
go
ahead
and
skip
right
on
over
that
for
1.9.8,
that's
a
fairly
it's.
We
talked
about
that
last,
maybe
meeting.
A
I
believe
the
last
patch
release
there,
so
we
can
skip
over
that
as
well.
Oh
yeah
august
11th,
here
we
is
this-
was
in
the
past
as
well.
B
A
Quick
link
to
the
release
notes,
which
is
that
one
right
there
1.9.9
and
then
we'll
throw
that
in
here
there
we
go
all
right
and
now,
let's
start
talking
about
1.10,
because
that
it's
on
the
horizon,
do
you
want
so
we
got
discussion
below?
Do
you
want
to
just
kind
of
roll
into
that?
Then,
let's
see.
B
A
B
A
B
A
B
B
Yep,
so
with
1.10,
so
we
got
the
beta
1.0
release
out
last
friday.
I
think
it
was,
and
so
that
went
pretty
smooth
as
usual,
just
to
get
something
out
there
and
post
it
in
slack
for
people
to
start
trying
it
out.
I
haven't
heard
any
feedback
on
it,
which
is
pretty
normal,
but
anyway,
things
are
in
place
now
the
docs
are
in
place
and
I
just
wanted
to
talk
about
the
kind
of
the
blocking
issues
or
the
remaining
issues
really
that
we
need
to
work
on.
B
So
the
blog
haven't
started
that
yet
I
need
to
do
that
upgrade
testing.
B
I
made
a
quick
pass
at
the
upgrade
guide
when
I
was
creating
the
1.10
branch.
But
blaine
are
you?
Could
you
take
a
look
at
the
upgrade
or
that
testing
that
or
what's
your
availability
yeah,
I
can
take
a
look
at
that.
Yeah
yeah
may
need
more
updates
to
be
up
pretty
good.
B
B
Sounds
good
and
then
the
last
real
code
change,
I'd
still
love
to
get
in
is
this
client.work
operator
keyring
and
we're
really
super
is
really
close
to
getting
this
work,
and
I
spent
some
time
on
the
pr
as
well,
and
we
have
almost
everything
passing
there's
a
couple
of
integration
tests,
particularly
around
object
and
upgrade
that
are
not
passing
yet
so,
hopefully
I
can
mail
those
down
today
and
then
call
it
good.
B
The
I
mean
the
upgrade,
I
feel
pretty
confident
in
it,
because
we're
still
using
the
client.admin
key
even
for
new
clusters
until
after
mon
corum
is
established.
So
I
feel
like
the
upgrade
path,
should
be
pretty
pretty
straightforward
or
low
risk
because
we're
treating
new
clusters
as
an
upgrade
back
to
until
the
long
term.
Anyway.
B
So
I
yeah
I'll
keep
daily
status
on
I'll
post
the
maintaining
channel
or
something
on
daily
status.
So.
A
Travis
for
the
blog
did
you
have
a
a
draft
post
that
you
wanted
to
include
here
a
link
to
here
not
yet.
B
Yeah,
those
are
the
main
things
left
for
1.10.
In
my
mind,
is
there
anything
else
anybody
wants
to
bring
up
for
1.10.
B
The
target
is
originally
like
tomorrow
or
tomorrow's
last
thursday,
further
release
that
yeah,
we'll
we'll
see
if
it
slips
the
next
week.
I
guess
I'd
like
to
get
it
done
this
week,
but
I
feel
like
getting
the
rook
operator
carrying
in
would
be
a
nice
thing
to
have,
even
if
it
slips
till
next
week.
A
If
we
need
more
time
to
you,
know
the
upgrade
testing
and
then
getting
in
that
that
fix
for
the
you
know
using
more
scoped
permissions
key
rings.
That
sounds
fine
to
me.
Have
we
have
we
gotten
any
have
any?
Is
anyone
in
the
community
been
testing
like
the
rc
builds
yet
at
all
the
release?
Candidates.
B
A
Okay
sounds
good
travis
awesome.
I've
been
looking
forward
to
getting
another
successful
release
out.
I
know
there's
been
a
lot
of
hard
work,
that's
gone
into
it.
So
that's
awesome.
A
Okay,
so
kubecon
any
updates
on
folks
attendance
and
availability
for
fucon.
C
B
C
A
B
B
For
sure
I
also
haven't
decided
for
sure
there's
just
a
lot
of
things
going
on
in
my
life
in
general
that
I'm
yeah,
I'm
just
not
sure,
that's
fair,
yeah
and
yeah.
I
still
need
to
officially
say
or
register.
If
we're
doing
a
virtual
talk
or
an
in-person
talk.
C
But
then
again
it's
well
how
many
people
are
officially
registered
for
the
talk
three
people.
C
Oh
no,
no,
I
mean
how
many
people
registered
from
outside
to
speak
for
like
for
this
talk,
three
people
or
four.
C
I
said
I
can
present,
but
it's
I
don't
know
if
well
alone
else.
Well
I
can
do
that
but
yeah,
I
I
don't
know
yeah.
B
C
B
Right
right,
I
don't
know
if
they're
just
keeping
virtual
talks
virtual
or
at
a
certain
time
I
mean
they
have
them
at
a
certain
time
for
sure,
because
they
ask
us
to
join
and
answer
questions.
B
A
Not
that
I
know
it
saw
or
realized
at
all,
it
was
like
a
lot
of
the
virtual
stuff
was
kind
of
an
afterthought
for
folks
in
person.
Yeah
like
you,
could
join
in
your
laptop
and
stuff
to
have
that
experience.
But
it's
not
something
that
there's
a
physical
like
hey,
go
to
this
room
to
participate
and
you
know
watch
it
together
or
collaborate
or
whatever.
I
didn't
see
any
of
that.
C
C
Where
was
it
again
in
in
valencia
yeah,
it
kind
of
worked,
I
guess
yeah,
I
don't
know.
B
C
A
D
B
D
D
Yeah,
I
was
thinking
from
that
perspective.
I
can
start
looking
at
them,
pick
them
up
and
even
if
anyone
wants
to
start
contributing
to
the
community,
even
if
there
are
some
doctor
related
issues,
we
can
push
the
documented
issues
and
add
a
head
pointed
label
on
them.
So
I
mean
some
issues
like
that.
Just
to
I
mean,
starting
with
documentation
to
good
basic
bug,
fixes
and
code
fixes
that
we
can
label
them.
D
A
B
D
C
Well,
my
girlfriend-
and
I,
when
we
talked
about
this
fort
lagalas,
bringing
it
up
in
a
community
meeting,
was
that
I
don't
think
we
currently
have
any
issues
with
a
label
or
like
we
have
the
labels,
but
we
don't
have
any
issues
with
the
label
or
like
these
labels
on
them.
I
think
there
is
for
like
one
or
maybe
two
issues
with
like
the
second
level
that
was
just
named
a
beginner
or
something.
D
C
Help
wanted
oh
help
wanted
yeah.
I
don't
remember
correctly,
like
help
wanted
label
as
well,
for
example,
but
like
there
aren't
really
any
issues,
and
you
know
I
I
get
that
we
are
in
the
end
of
like
hey.
C
Anyone
can
pick
up
anything
as
a
task
but,
like
I
don't
know,
yeah
just
thought
we
bring
it
up
because
we
don't
really
have
any
issues
right
now
with.
C
At
least
for,
like
beginner
or
good
first
issue
tasks,
I
said
it's
like
a
for
someone
to
start
working
on
a
project.
Maybe
if
we
see
issues
or
like
if
we
more
actively
have
a
look
into
that
as
well
and
see
like
the
issue
is
I
don't
know
how
changed
these
two
lines,
but
maybe
just
really
haven't
had
the
time
to
do
that.
Yet
maybe
you
can
just
look
into
using
the
good
first
issue
label
or
more
than
I
guess.
A
Yeah
yeah,
I
so
I
think
that
across
a
lot
of
github
projects-
and
then
you
know
the
cloud
native
ecosystem
as
a
whole,
the
good
first
issue
is
is
fairly
ubiquitously
used.
So
it's
kind
of
common
and
it's
definitely
something
that
new
contributors
are
looking
to
get
involved
somewhere,
do
go
and
seek
out,
so
they
can
go
to
projects
and
they'll.
Look
for
the
good
first
issue
label
to
see
if
there's
like
something
that
they
can
get
their
feet
wet
and
get
started
in
the
project.
A
It's
a
good
little
on-ramp
to
get
new
contributors
and
people
into
the
community
that
could
potentially
help
out
more
in
the
future.
Also.
So
what
my
recommendation
here
would
be
is
that
to
at
least
consolidate
the
beginner
and
good
first
issue
labels
because
they
seem
redundant
to
me.
They
seem
like
they're
trying
to
attack
the
same
problem,
but
good
first
issue
is
the
standard
one
that
a
lot
of
other
projects
use.
A
So
in
terms
of
you
know
having
some
normalization
or
consistency,
I
would
probably
not
use
the
beginner
label
and
advocate
for
using
the
good
first
issue
label
itself.
Instead,.
D
Yeah
sounds
good,
and
we
should
have
at
least
some
issues
classified
in
under
that
as
well.
So
if
there
are
none
at
least,
it
would
be
good
to
have
some
at
least.
B
I
feel
like
the
challenge
of
having
issues
with
that
good
first
level
or
basically
beginner
level
issues.
Is
that
they're
so
quick
for
someone
to
do
at
least
for
the
maintainers
to
do
that?
Sometimes
we
just
end
up
doing
them
real,
quick
and
then
there
aren't
any
left
but
yeah
I'd
love
to
have
some
and
label
something
it.
A
Looks
like
we
have
six
good
first
issues
here,
at
least
right
now
that
I
don't
know
I
haven't
looked
at
them,
but
we
have
six
of
them.
Yeah.
D
C
First
issue
yeah:
I
think
that's
mainly
as
we
headed
right
now.
It's
like
we
have
two
or
maybe
even
more
labels
for
like
hey.
You
can
pick
this
up,
especially
if
you
want
to
like
start
contributing
to
rook
or
something,
and
I
said
like
that's
more
or
less
what
like
a
girl,
and
I
were
looking
for
at
the
time
that
and
realizing
that
there
wasn't
really
at
least
for
the
label
labels.
We
looked
at
any
labels
like
that.
B
B
Yeah,
it's
interesting,
I
feel
like
the
network
community,
I
mean
there's
definitely
some
who
contribute,
but
the
vast
majority
of
users
will,
I
mean
they're,
just
not
coders,
so
they'll
come
and
comment
and
they
want
to
get
things
working,
but
they
just
can't
contribute
to
the
project
itself
so
but
yeah
nurturing
this
whole
thing
of
getting
beginners
to
help
the
project
yeah
that
it's
all
good.
A
Yeah,
it's
definitely
good
project
hygiene
and
then
like
it,
provides
the
you
know
fertile
ground
for
the
jupiters
to
come
in.
B
A
C
Well,
it's
basically
just
about
removing
some
of
the
older
channels,
or
at
least
archiving
them.
I
think
troyston
already
went
ahead
and
archived
like
the
yugabyte
tv
one
and
the.
B
C
By
the
way,
at
least
oh
okay,
interesting
there
is,
I
think
I
think
the
rook's
like
might
have
been.
I
don't
know
who
created
that
one,
but
there's
a
channel
called
christian
christians.
C
A
C
A
A
It's
been
there
for
for
about
a
year.
A
It
says
who
created
it
too.
It
might
be
interesting
to
follow
up
with
them
and
and
see
if
they're
actually
doing
things
on
the
project
or,
if
they're,
someone
who
is
not
really
contributing-
or
you
know,
focused
on
anything
having
to
do
with
rook
right,
there's
a
time
and
a
place
for
this
topic,
but
it
it
is
not
the
rook
slack.
A
And
they're
changing
that
to
90
days,
10k
messages
yeah,
that's
the
change
they're
making.
A
It
depends
on
the
the
frequency
for
some
for
heavily
trafficked
slacks.
You
can
get
more
more
messages
because
it's
you
know,
90
days
or
10k.
Messages
is
actually
less
than
a
90
day
window.
Sometimes
so,
if
you
get
it
90
days,
you
actually
get
more.
If
it's
a
heavily
traffic
slack.
C
Well
then,
let's
see
how
it
goes.
Basically
with
that
at
least
yeah
yeah,
I
don't
know
if
yeah
then
I
think
we
can
take
this
topic
more
or
less
offline,
so
to
say,
yeah
most
channels
have
been
removed
there
because
like
well
yeah
either
they
are,
they
don't
have
a
storage
provider
anymore
with
us
or
something
with
rook,
so
yeah,
that's
all.
C
One
is
okay,
because
the
idea
initially
was
to
what
was
it
about
here
from
souza,
ranger,
well,
suicidal
purchase,
ranger
arranges
like
a
kubernetes
distribution,
and
some
people
had
issues
running
it
and
yeah.
C
It
was
actively
used
by
some
people
using
ranger,
but
they're
gonna
be
wrong.
Nowadays,
it's
our
at
least
also
to
the
other
channel,
is
a
bit
as
we
had
it
before,
like
some
people
that
have
self
issues
use
the
general
channel
and
then
they
post
it
again
in
the
into
like
the
ceph
channel
or
even
another.
So
it's
well
a
bit
mixed
from
what
continuation
there.
B
C
B
B
I
don't
know,
I
think
I
think
the
channels
we
have
now
are
okay,.
C
C
B
A
All
right,
sweet
yep,
so
we
can
follow
on
whack-a-moling
on
those
channels
as
we
want
and
this
topic
I
brought
up
here-
it's
actually
the
deadline's
fast,
so
it's
not
applicable
anymore
but
and
the
mentees
are
applying
for
projects
already,
but
that's
something.
We
should
keep
in
mind,
though,
for
upcoming
opportunities
to
participate
in
lfx,
mentorship
and
and
revive
that
effort
again.
A
Is
that
that's
the
linux
foundation
program,
it's
simply
similar
to
google
summer
of
code,
but
then
you
know
it's
the
linux
foundation
running
it
and
it's
they
do.
I
think
three
terms
a
year,
maybe
so
there's
like
they're
all
each
12
week,
programs
and
so
there's
multiple.
What
I
like
about
it
is
there's
multiple
chances
throughout
the
year
to
be
able
to
get
involved
with
that,
as
opposed
to
just
the
google
summer
of
code,
like
big
commitment
in
the
summer
time.
A
B
There's
that
there's
the
outreachy,
you
know-
and
I
think
a
week
or
two
ago
I
actually
posted
an
engineer
channel
asking
if
anybody
wanted
to
mentor
as
well,
because
we
have
some
funding
already
from
the
past
outreachy
intern
program
that's
still
available
and
but
nobody
said
they
had
the
bandwidth
for
mentoring.
So
that's
a
challenge.
A
How
come
how
come
we
use
outreach,
as
opposed
to
the
linux
foundation
like
just
use
that
and
use
in
that
program.
B
A
B
A
Cool
all
right:
well,
that's
everything!
That's
on
the
agenda!
Anything
else
that
folks
want
to
bring
up.
A
All
right,
then,
I
think
that's
everything
I'm
just
going
to
take
a
quick
note.
Also.
We
should
consolidate
issue
with
labels
to
use
a
good
first
issue.
A
All
right,
cool,
so
travis
hope
you
feel
feel
better
thanks
for
giving
us
some
time
today,
as
you're
recovering
yeah.