►
From YouTube: 2023-01-10 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
started-
and
this
is
the
January
10th
2023-
welcome
2023
folks,
rookie
community
meeting.
So
let's
go
ahead
and
get
started
with
Milestone
checkup
I
have
been
offline
and
sick
for
quite
a
bit,
so
I'm
definitely
out
of
the
loop
on
a
number
of
things.
So
we
will
dive
into
things
and
obviously
Travis
will
pick
us
up
with
a
lot
of
good
details
so
with
nothing
that
looks
planned
for
a
patch
release
for
1.9,
so
I
think
we
can
skip
over
that
one
1.10.
A
B
A
D
A
Oh,
we
could
push
on
forward
then
to
something
of
more
relevance
then
so
we're
planning
on
doing
a
1.10.9.
Then
this
Thursday
yeah
so
two
days
from
now.
So
let's
talk
about
the
1.10
board
then
and
what
might
be
ready
to
go
out
and
anything.
It
doesn't
look
like
anything's
blocking
the
one
that
this
this
next
1.10
patch
exactly.
D
B
D
A
D
Now
the
1.11
really
is
honestly
for
me
is
going
to
be
the
first
one
where
I'm
not
sure
we
have
any
super
big
features
to
report.
It's
going
to
be
just
a
lot
of
new.
You
know,
maintenance
things.
Of
course
you
know
progress
progress,
but
a
lot
of
the
things
we've
been
working
on
have
been
backward
to
1.10
in
those
releases
already.
So
this
is
going
to
be
more
of
a
kind
of
just
oh
time
for
a
minor
release
on
some
sort
of
cadence.
It'll
have
been
like
five
months,
I.
D
Let's
see
things
in
progress
on
the
board.
I
mean
yeah
like
the
one
in
progress
there.
It
shows
we're
just
updating
our
main
kubernetes
version
and
still
trying
to
get
the
1.26
build
to
work
because
we're
waiting
for
an
update
for
minicube
yeah,
updating
the
CI.
Some
other
things
operate.
Updating
operator,
SDK,
I,
think
that
doesn't
really
affect
the
Upstream.
So
much
because.
D
That's
within
Rook,
where
we
are
generating
some
CSV
with
the
operator
SDK,
that's
used.
It's
really
only
used
for
Downstream.
They
output
of
that
works
using
an
older
version.
So
we
almost
don't
even
need
to
track
this
for
the
Upstream
release,
because
it's
a
downstream
artifact,
but
it's
related
to
the
CI.
We
do
use
it
in
the
CI
because
it
could
be
used
for
other
things
other
than
our
Downstream
project.
A
D
A
D
Well,
the
I
think
with
operator
Hub
we've
figured
out
well,
there
should
be
a
way
to
kind
of
automate
the
process
or
automatically
open
a
PR,
at
least
in
the
operator
Hub.
That
would
update
it,
but
honestly
even
doing
any
CI
worker
on
that
it
doesn't.
The
benefit
doesn't
seem
obvious
to
me
because
nobody
seems
to
notice
or
or
care
about
it,
so
I'd
almost
rather
visit.
A
D
A
A
C
D
A
Or
whatever
I
want
to
mix
I
mean
if
there's
if
they
were
destinations
like
strong
destinations,
for
people
to
go
and-
and
you
know
like
find
the
software
they
want
to
use
than
having
you
know
an
automated
build
process
that
you
know
that's
just
another
destination
for
where
our
packages
images
binaries,
whatever
go
to
get
published
to
automatically
without
even
thinking
about
it.
That
would
make
a
lot
of
sense.
A
B
B
B
It
kind
of
feels
like
this
situation,
where,
like
companies,
don't
just
want
to
like
give
you
a
download
like
binaries
or
something
because
they
always
want
to
have
like
the
latest
version
on
their
website.
You
know
where,
like
they
are
in
control,
I
guess
and
it's
kind
of
you
know
it
kind
of
feels
like
the
same
for
a
rook
right
now
where
there
seems
to
be
older
versions
and
that
might
cause
issues
for
people
if
they
really
use
it.
B
B
D
D
D
A
A
A
A
A
Making
progress
on
that
we
have
a
little
bit
over
a
month
to
before
that
release
comes
out,
so
we'll
keep
making
progress
and
we'll
talk
more
about
it
again
next
community
meeting.
So
we
talked
about
this.
So
let's
move
on
then
to
the
planned
agenda
items
of
the
retrospective
of
the
rook.io
website
going
down.
So
let's
pull
up
this
issue
here
and
then
Alexander
and
Travis.
Listen
to
your
thoughts
on
that
one.
B
B
The
reason
for
that
is
was
small,
as
it
was
because
it's
fixed
now
that,
when
I
restructured,
the
documentation
to
use
MK,
Docs
I
seem
to
have
pushed
the
cname
file.
I,
don't
know
who's
who
knows
about
guitar
page,
but
that
found
more
or
less
is
like
a.
This.
Is
the
custom
domain
I
guess
of
like
the
custom
address
for
the
website
then?
B
I
went
ahead
and
unpublished
the
GitHub
pages
on
our
Fork,
because
I
also
didn't
want
that
to
pop
up
in
the
search
results
on
Google
or
whatever,
and
because
of
that,
the
Rogue
hyphen
GitHub
hyphen,
I
o
codef
domain,
so
to
say,
God's
freed
up
and
then
because
of
this
cname
file
existing
in
The
Rook
GitHub.
I
o
GitHub
Pages
branch
that
is
published
by
guitar
Pages.
B
It
got
basically
like
GitHub
Pages
courses
like
Auto
redirects
you
to
this
cname,
then
at
least
in
some
cases
it's
a
bit
unclear.
Github
I
just
feels
sometimes
a
bit
inconsistent.
But
that's
beside
the
point,
and
because
of
like
this
Cinema
existing
and
US
deleting
or
unpublishing
the
guitar
pages
on
our
fog.
Like
this
whole,
redirect
thing
happened
and
it
wasn't
like
a
DNS
issue
or
something
it
was
purely
based
on
GitHub
Pages,
then
redirecting
the
actual
domain
so
to
say
or
like
to
the
actual
address
and
yeah
fixed
it.
D
B
B
A
D
B
Now
so
it's
you
know,
we
just
decrease
the
cash
I
guess
to
be
maybe
just
two
or
three
hours
or
we
maybe
even
remove
the
whole
caching
for
the
website
from
AWS.
It's
like
technically,
we
have
it
on
GitHub,
Pages
anyways
and
it's
so.
If
you
visit
Rook
IO,
you
basically
go
to
AWS
end
up
at
the
caching
layoff.
What
is
called
the
out.
B
Cloudfront
basically
talks
to
GitHub
pages
and
yeah.
Well,
then
you
get
the
content
or
if
it's
cached,
then
you
can
well.
So
it
has
an
advantage
just
having
this
layout,
but
I
think
at
least
from
a
configuration
side,
reducing
that
to
like
an
hour
or
just
a
few
hours
might
make
sense
just
in
general
in
regards
to
updates
to
the
documentation,
I
guess.
D
B
A
B
B
B
And
I
said
like
because
during
testing
of
our
Fork,
like
with
the
m
full
MK
docs
changes,
if
you
remember,
we
like
set
it
to
a
custom
domain
that
we
can
well
easily
test
it
so
that
cname
file
ended
up
in
the
repository
asset
like
because
we
still
use
the
domain,
it
was
blocked
till
we
took
down
our
fog
and
then
the
GitHub
page
is
like.
Oh,
it's
free,
so
bam
it
you
know
starts
redirecting
people
today
in
our
case,
I'm
wrong
domain.
D
Richard
to
answer
your
question:
I
think
you
can
see
the
change.
If
you
look
at
the
a
commit
the
last
commit
on
the
branch,
the
GitHub
Pages
Branch,
since
it
publishes
from
the
branch.
It's
really
definitely
odd
that
it's
not
a
pull
request,
but
if
you
change
to
that
Branch
history
will
show
Alex's.
C
A
B
Yeah
but
yeah
so
at
least
in
like
GitHub,
page
or
settings,
if
you
change
or
like,
if
you
set
or
even
then
remove
the
custom
domain,
it
basically
automatically
creates
like
a
commit
to
create
or
remove
that
file
for
you
and
then
basically
just
went
into
that
settings.
Press
the
remove
or
manually
deleted
it
that
it
get
that
did
we
get
it
working
again.
A
Okay,
cool
Okay
cool,
so
yeah,
that's
good
that
we
understand.
We
have
an
understanding
of
of
you
know
what
happened
there,
thanks
Alex
for
kind
of
peeling,
the
layers
of
the
onion
back
there
and
getting
to
and
understanding
of
the
root
cause
and
then
I
I.
Believe
then,
from
your
explanations.
It
sounds
like
you
know:
we're
not
at
risk
for
this
happening
again.
Now
that
we
use,
you
know,
got
things
configured
and
set
up
the
way
they
are
now
exactly.
B
Yeah
I
said
this
was
really
just
a
I
guess
in
general,
I
think
waiting
to
happen
because
I
was
at
the
CNN
file
existing
due
to
the
testing.
I
didn't
really
reckon
like
I
didn't
Pat
and
I
and
then,
like
just
oh
yeah.
Let
me
take
down
the
fork
of
The.
Rook
I
get
up
I
O
pages
and
then
I
said
like
it's
got.
Freed
up
so
yeah
shouldn't
have
another
one.
A
D
D
A
A
D
Right
so
it's
dead
on
kubernetes
community,
honestly,
it's
just
something
that
came
on
my
radar
last
month
like
oh.
What
is
this
thing?
Oh
maybe
we
should
join
and
it
sounds
like
it
just
totally
makes
sense.
People
are
already
familiar
with
it.
There's
the
website
link
to
the
website
and
then
some
slides
to
discuss
kind
of
what
their
goals
are
and
how
we
could
benefit
by
by
joining.
D
But
basically
we
could
be
the
first
Community
sponsor
for
more
data
on
kubernetes
community
and
they
they
set
up
events
they're
going
to
have
meetups
they're
going
to
have
sound
like
even
full
conferences,
eventually
that
they're
still
getting
underway
with
that.
But
I
think
it
just
makes
sense
for
us
to
say:
hey
we're
a
community
project.
D
We
think
it's
great
to
get
together
and
talk
about
data,
it's
just
more
visibility
for
a
rook
and
at
the
same
time
I
think
be
great.
If
we're
multiple
maintainers
are
on
board,
then
it's
not
one
person
trying
to
to
run
it
all,
but
so
maybe
if
we
yeah
I,
don't
I
don't
have
any
there's
no
sort
of
speaking
commitment
yet,
but
it's
kind
of
like
yes,
oh
here's
something
coming
up,
let's
participate
or
I
think
there's
a
virtual
Meetup
where
we
might
be
able
to
present
them
in
a
couple
months.
D
A
Goodness
yeah
yeah-
and
you
know
this
is
this-
is
like
what
I
believe
to
be
an
evolution
right
of
the
group
that
that
we
were
participating
with
that
put
on
the
cloud
native
storage,
Day
events
as
co-located
zero
day,
events
at
kubecon
right,
that's
the
same
group
of
companies.
It's
the
same
people
behind
it,
I
believe
so.
I
think
this
is
the
evolution
of
that
group.
A
So
those
were
good
people.
Those
were
good
events.
That
was
that
was
definitely
a
useful,
a
useful
way
to
spend
our
time
a
few
years
ago
on
this,
so
that
all
definitely
all
makes
sense
to
me
participating
in
this.
You
know
from
what
you
were
saying:
Travis
I
wasn't
quite
sure.
If
I
understood
it,
you
know
you're
just
talking
about
being
the
first
Community
sponsor
for
that
on
kubernetes
community.
A
So
are
they
making
a
distinction
between
like
data
on
kubernetes
like
as
a
vendor
group
or
a
group
that
does
events
that
are
vendor
backed
and
vendor
sponsored
and
then
on
a
parallel
group
that
is
the
community
this
one,
or
is
that
you're
just
saying
there
hasn't?
It's
all
been
vendor
sponsors
so
far
and
we
would
be
the
first
Community
sponsor
to
the
still
the
same
entity,
the
same
group,
not
a
parallel
offshoot
group
or
something.
D
Right:
that's
what
it
is.
It's
really
just
been
paid
funds
for
company
sponsorship
until
now
and
they're
got
it
adding
this
community
sponsorship
thing
where
it
just
makes
sense
for
a
rook
and
like
yeah,
red
hat
had
been
a
sponsor
in
the
past
and
now
with
IBM
we're
looking
at
trying
to
get
IBM
as
an
official
sponsor
of
this
group,
but
then
worked
at
the
St
diamonds,
community
and
anyway
yeah,
so
that
red
hat
will
be
replaced
by
IBM.
Since
our
whole
storage
group
just
moved
over
right.
A
D
Anyway,
I
think
unless
there's
any
reason
not
to
do
this
or
anybody
has
any
concerns
that
yeah
I'll
go
ahead
and
tell
them
yep,
let's
officially
sign
up,
and
then
the
maintainers
slack
Channel
I
put
some
more
details
about
what
Melissa
she's
this
CEO
of
this
group,
I,
think
or
leading
the
effort
yeah.
She
gave
some
guidelines
kind
of
their
what
he
called
their
governance:
governance
for
how
they'll
consider
Upstream
Community
sponsors
can
get
that
free
sponsorship
and
I
think
it
all.
A
Do
we
something
that
I
found
some
value
in
Travis
a
few
years
ago?
Was
you
know,
participating
in
the
planning-
and
you
know,
program,
selection
and
stuff,
like
that,
for
the
the
events
that
they
put
on
does
being
a
community
sponsor
give
you
some
access
to
that
as
well
to
be
able
to
participate
in
you
know
putting
together
the
the
agenda
and
schedule
for
these
events,
and
you
know
being
a
speaker
and
stuff
too,
or
is
it
like
a
different
path.
D
A
D
And
I
feel
like
I've,
dropped
the
ball
in
past
conferences
and
not
getting
more
involved
with
that
storage
group.
It's
like
I,
don't
know
it
was
something
about
the
Cutthroat
vendors
for
storage.
It's
a
competitive
group
right
and
they
all
want
their
pieces
of
it
and
I
just
didn't
want
to
get
involved
with
that
after
it
was
hard
enough
just
getting
graduated
based
on
that
all
that
process
anyway,.
D
A
D
A
A
D
Nice
make
sure
with
IBM
funding
or
whatever
that
won't
be
a
problem,
but
for
those
speaking
at
conferences,
theoretically
we'll
be
able
to
do
that
at
least.
Even
if
we
don't
have
big
team
meetings
at
conferences
like
we
used
to
yeah,
it
seemed
like
budgets
are
locked
down
since
covet
haven't
lifted
those
lockdowns.
No,
so
well,.
A
D
But
if
we
want
poor
speakers,
we
do
have
to
have
at
least
one
female
on
that
that
group
and
so
I
think
we've
got
two
possible
possibilities
there.
So
we've
got
a
net
clue
it
I've
talked
to
her.
She
said
she
might
be
willing
to
go
and
then
I
think
the
other
one
was
Deepika
yeah
working
with
Alexander's
team.
Now
I
don't
know
if
she
would
how
much
she
would
want
to
go
Alexander,
but
we
could
work
that
out
offline
as
far
as
who's
who
could
be
there,
but
by
default.
Maybe
who?
A
A
A
D
D
B
D
A
Work
yeah.
That
combination
could
work
yeah
cool,
okay,
sweet.
Well.
It
would
be
an
absolute
pleasure
to
see
you
you
cool
folks,
at
a
kubecon.
Again,
it's
been
Vincent
I'm
planning
on
it.
Yeah
I'll
be
I'll,
be
in
Europe.
Already
that's
my
plan.
So
it's
it
would
be
a
train
ride.
I!
Think
for
me
to
go
from
Brussels
to
Amsterdam,
so
I
I
don't
see
any
reason
why
I
I
wouldn't
attend
as
well.
That's
that
should
be
in
the
cards.
A
A
A
C
Conspicuously
absent
was
the
I
mean
I
I've
started
doing
like
kind
of
prototyping
and
research
on
just
setting
up
active,
active
NFS
such
that
it
goes
through
a
load
balancer
like
aha
proxy
and
that's
a
a
fair
bit
of
work
to
kind
of
get
get
done
and
get
moving
and
I
wanted
to
make
sure
that
was
captured
and
it
should
be
on
the
project
board.
Now.
A
A
A
All
right,
then,
if
there's
nothing
else,
so
we
can
go
ahead
and
adjourn
for
today
and
then
there
may
be
a
a
bit
of
a
backlog
for
the
last
community
meeting
that
didn't
get
uploaded
to
YouTube.
So
I'll
make
sure
that
when
I
get
the
recording
for
today,
it
all
upload
that
very
quick
and
then
make
sure
that
if
there's
any
missing
ones
from
December
that
they'll
uploaded
to.