►
From YouTube: 2021-01-26 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
january
26
2021
rook
community
meeting.
Let's
go
ahead
and
take
a
look
see
here
at
the
latest
milestones,
so
there
isn't
one
planned
for
1.4,
but
the
next
release
here,
a
patch
release
for
1.5
will
be
expected
in
a
couple
days
here.
Travis.
Do
you
want
to
update
us
on
that.
B
A
Good
cool
and
we
do
have
the
bucket
names
changed
merged,
backboarded
back
to
both
1.4
and
1.5.
So
if
we,
when
it
comes
time
to
do
a
release
there,
I
don't
anticipate
any.
A
To
be
aware
of,
when
we
run
the
release,
if
we
have
issues
like
publishing,
artifacts
sounds.
B
A
Yeah,
I
think
that's
in
the
agenda
later
on
as
well
too.
True
all
right,
any
other
notes
on
1.5.
A
All
right,
let's
talk
about
1.6.
Is
this
project
board
up
to
date
and
ready
to
talk
about
the
I
mean
a
quarterly
release
as
a
whole
will
be
late
march.
So
there's
still
lots
of
time
to
be
putting
in
and
investing
into
this
release.
B
Right
we're
really
looking
at
the
end
of
march
and
possibly
even
early
april
they're
saying
for
pacific,
so
I
think
we'd
like
to
to
match
their
lease.
So
we
can
support
pacific
right
after
it's
out
and
the
project
board.
I
was
looking
at
it
last
week,
so
it's
sort
of
up
to
date,
but
it
needs
more
work.
Still
honestly,
I
I
did
update
the
rope
road
map
after
our
last
meeting
too
a
week
or
two
ago.
B
A
Ready,
yes,
so
travis
you've
been
doing
some
work
with
the
storage
providers
and
defining
you
know
the
requirements
for
him
and
doing
some
cleanup
as
well
too.
B
Yeah
after
our
last
community
meeting,
I
thought.
Okay,
I
really
gotta
start
moving
this
forward
here,
so
I
got
the
pr
merged
with
the
storage
provider
documentation
there
just
to
be
clear
with
people
hey,
here's,
what
rook
provides
here's
our
framework,
here's
what
to
expect
here's,
what
not
to
expect
and
yeah
it's
just
being
more
open
about
it.
So
people
don't
have
to
basically
get
answers
and
not
not
be
consistent
over
time,
but
anyway
there
it
is.
A
Yeah,
thank
you
for
for
writing
that
up
and
making
that
a
little
bit
more
clear.
I
think
that's
kind
of
clear,
like
kind
of
guidance,
is
really
useful.
B
Yeah
and-
and
one
thing
I
think,
we're
at
least
not
clear
on
before,
or
how
do
we
deal
with
where
the
code
lives
for
new
providers?
So
the
proposal
with
with
that
document
is:
let's
put
new
providers
in
new
repos
and
enable
basically,
then
the
github
actions
are
all
independent
per
provider
we
can
now.
B
We
need
to
find
a
good
way
to
to
share
things
whether
it's
you
know
merge
modules,
although
that's
the
is
that
the
old
way
of
doing
it,
I
haven't
shared
across
repos
for
a
long
time,
so
anyway,
we
should
really
look
at
how
to
to
share,
but
also
by
saying
hey,
whatever
is
in
the
repo
already
it's
kind
of
grandfathered
in
so
when
new
providers
are
added
the
first
one.
That's
added
will
go
through
that
exercise
of
really
sharing
things
and
getting
that
benefit
there.
B
So
if
there
are
other
ideas,
certainly
it's
still
open
for
discussion,
but
that
was
the
proposal
and
then
specifically
for
our
current
storage
providers,
so
cockroach
db
operator
was
removed.
That
merged
yesterday
hadn't
seen
any
feedback
to
the
contrary,
edgefest
operator,
I
opened
the
pr
for
that
one
yesterday
and
it's
got
a
couple
of
approvals
unless
I
hear
any
concerns
here
about
that
removal.
B
I'm
assuming
no
no
concern
about
that.
B
Exactly
yeah
and
edgefest
had
told
us
a
few
months
ago
that
hey
yeah
we'd
like
to
come
back
in
some
time
frame,
maybe
later
this
year
and
add
it
back
basically
the
new
stuff
they're
doing
so
when
they
do
that,
we
can
just
have
them.
Follow
the
new
process
have
a
new
repo
and
that
may
be
the
forcing
function
if
well,
if
they're,
the
first
one.
A
Any
update
on
that
in
2021,
yet
travis.
B
B
Yeah
it's
just
from
a
few
months
ago
I
haven't
had
an
update,
got
it
yep,
cool
and
then
for
a
gigabyte
db
operator.
So
I
just
I
just
pinged.
Sorry,
I'm
terrible
with
names
it's
like
from
you
by
team.
It
was
sanketh,
so
he
did
come
back
and
say
you
know
they.
B
B
C
B
Can
resurrect
them
based
on
that
if
we
need
to,
but
that's
kind
of
the
visibility
still
that's
there
and
I
haven't
updated
the
website
yet
work.io
to
remove
them
so
yeah.
I
think
that's
well
that'd
be
the
next
step.
I
think
removing
from
them
from
the
website
makes
sense,
but
keeping
the
link
here
on
the
readme.
A
Yeah
that
seems
reasonable
to
me.
Travis
cause
yeah,
especially
with,
like
the
you
know,
link
to
1.5
docs
they're
directly
there
that
they'll
be
present
there.
B
A
Good
cool
yeah
we
should
we
should
get
a
steering
committee
meeting
together
soon,
let's
to
just
meet
and
talk
about
some
of
those
updates-
and
you
know,
feature
direction
and
stuff
like
that.
A
A
Okay
cool
already,
I
want
to
move
down
to
the
next
next
guy
here
yep.
So
we
did
the
migration
successfully.
It
would
appear
so
far
of
moving
all
of
the
s3
buckets
for
the
rook
artifacts,
home
charts
and
binaries
and
stuff
from
outbound
s3
account
to
the
official
request,
aws
account
that
seems
to
be
working
well.
A
So
far
we
didn't
have
to
make
a
couple
updates
and
there
was
a
little
bit
of
downtime
to
the
rook.io
site
like
on
friday
night
to
friday
nights
ago,
while
we
were
moving
around
the
dns
and
all
sorts
of
stuff
or
the
not
cloud
formation.
What's
that
what's
aws's
cdn
the
college
cloudfront
cloudfront,
while
moving
that
around
so
a
little
bit
of
rook.io
main
site.
A
On
a
friday
night,
I
think
that
was
okay,
but
everything
looks
good
there
so
far,
and
then
you
know
it
will.
I
have
told
our
tour
from
the
upbound
engineering
team
to
keep
the
buckets
and
everything
intact
in
the
old
upbound
account
until
we
do
actually
do
a
release,
like
master,
seems
to
be
doing
fine,
but
until
we
run
a
real
release,
capacity,
1.5
or
whatever,
to
get
a
little
more
confidence
in
that
before
we
decommission
the
old
buckets
right.
A
Yep,
okay,
cool
and
so
now
we're
questioning
the
binary
aspect
of
those
buckets
that
traps.
Maybe.
B
A
Yeah
I.
A
B
All
right,
so
I
need
to
double
check,
but
I'm
pretty
sure
that
when
I
looked
at
it
it
was
just
you
know,
gzip
for
each
of
the
operators
and
well
that
would
be
included
in
a
docker
image.
B
A
Yeah,
it's
a
good
question.
I
want
to
take
a
look
at
that
again
see
what's
in
there
and
like
maybe
look
at
the
build
the
build
scripts
and
things
too
to
make
sure
there's
not
like
a
dependency
in
there
somewhere.
That's
you
know
we
would.
C
A
Yeah
it's
an
interesting
idea,
though
we
are
archer,
did
put
a
policy
on
there
for
master
builds.
I
think
like
older
than
60
days
or
something
like
that.
Those
will
get
cleaned
up
now,
because
we
have
multiple
terabytes
on
the
old
buckets,
and
so
with
that
policy
there
now
like
we
don't
we
don't
need
these
0.2
binaries
anymore
type
of
thing,
so
we
so
we
are.
A
Space,
at
least
for
on
those
buckets,
that's
cool.
B
C
B
Use
this
github
action
and
okay,
that
makes
sense
so
it
just
merged,
as
this
meeting
was
started,
thanks
seb,
so
the
it
is
now
but
and
we'll
see
so
it's
scheduled
to
run
at.
I
think
8
p.m,
utc
every
day
so
noon.
My
time,
I
think
so
we
may
see
a
bunch
of
emails
in
the
next
couple
of
hours
from
new
stale.
A
That,
actually
it's
really
interesting
you!
You
brought
that
up
travis
that
now
so
it's
running
as
a
scheduled
github
action.
What
was
the
trigger
before
like?
Where
did
that
bot
run
like
who's,
whose
compute
resources
hosted
that.
C
C
Had
a
server-
and
it
was
just
just
subscribing
to
get
up
events
because
you
can
subscribe
to
get
up
events
and
then
you
get
notified
like
that,
because
every
single
action
is
an
event
and
then
based
on
that,
then
you
could
apply
your
label.
You
could
watch
for
things.
I
guess,
but
it's
it's
it's!
It's
just
competition
on
the
stale
bot
server
that
lives
somewhere.
A
A
C
Yeah
every
bot
can
like
they
all
do
this,
like
mergify,
does
that
they
they
have
their
own
servers.
That's
why
you
can
kind
of
support
them
like
through
sponsorship,
wow,
you
have
to
pay
for
the
fees
and
stuff
like
for
the
servers.
I
guess
yeah
good.
A
A
C
A
Sponsor,
oh,
oh,
I
thought
I
thought
with
travis
said
contribution
or
whatever
I
thought
you
meant
like
upstream
contribution
like
you
know,
features
we
could
we
could.
C
The
engine
is
open
source,
so
we
could.
If
we
wanted
to
implement
new
features,
we
could
set
a
pr
for
that
cool.
A
All
right
so
yeah,
so
that
should
be.
That
has
not
run
yet
travis
with
the
new
github
action.
Okay,
so
that
will
run
like
noon
your
time
you
said,
eight
eight
pm,
utc
yeah.
B
It's
set
up
with
a
a
cron
on
the
github
action
and
yeah.
I
think
I
started
that
for
you
in
my
time,
awesome
cool.
It's.
A
B
C
B
A
Yeah
nope,
I
am
looking
at
the
participants
list
and
I
don't
I
don't.
I
have
that
on
my
screen
right
here
in
front
of
me,
so
I
haven't
seen
anybody
trying
to
get
admitted
if
I
saw
mike
perez.
I
would
certainly
let
him
in
right
sure
quality
quality,
human
being
right.
There.
B
Well,
so
we
were
just
talking
yesterday
and
he
was
telling
us
about
some
conferences
coming
up
and
they
have
virtual
booths
and
things
and
he's
going
to
help
us
create
some
videos
for
kind
of
get
people's
attention
in
the
booth.
A
A
Want
to
do
a
booth
this
time,
because
we
opted
not
to
do
a
booth
at
the
last
kubecon
virtual.
B
Right
well-
and
he
mentioned
a
couple-
other
conferences
too
lane
do
you
remember
which
ones
I'm
forgetting
already
yeah.
I
forgot
the
specific
names.
B
D
Just
just
wondering
as
a
question
should
I
ping
mike
like
when
I'm
when
I'm
at
the
meet
up
or
something
because
tomorrow,
like
I'm
talking
about
rook
at
a
meet-up,
well,
which
is
virtual
because
well
hello.
C
D
B
Yep
and
then
he
also
had
this
next
idea
of
doing
a
survey
he
said
he's
working
with
this
new
great
survey
platform
that
makes
it
easy
to
have
contextual
questions
based
on
your
previous
answers
and
things
so
we're
gonna
put
together
a
survey
in
the
next
couple
of
months.
Hopefully-
and
I
was
thinking
I
have
a
few
benefits-
I
mean
we
really
need
to
update
our
rook
adopters
and
the
who
loves
rook,
section
and
friends
of
rook
they're.
I
mean
they
just
need
to
be
updated
periodically,
especially
friends
of
rook.
A
We've
kept
the
doctors
updated
at
least
with
each
transition
through
the
cncf
stages.
You
know
incubation
in
graduation.
We
have,
but
friends
of
brooke
is
like
probably
one
of
the
first
100
commits
to
the
repo
type
of
thing.
B
A
B
A
D
Yeah
but
they're
like
just
as
I
think
everyone
knows
more
or
less
that
that
there's
a
handful
of
people
well,
companies
which
just
can't
be
named
on
like
publicly
about
that.
D
We
have
a
few
customers,
not
a
few.
We
have
a
handful
of
customers
which,
where
we
help
with
rook
cephalo
and
and
like
we
asked
them,
and
most
of
them
are
like
no,
no,
we
could
we
can't
we're
like
we
should.
We
should
not
be
named
to
put
like
that
and.
D
B
A
D
C
A
That
item
yeah,
that
that
we
applied
and
got
like
the
initial
acceptance
of
your
application
email,
but
have
not
heard
anything
back
from
from
them
about
these,
like
particular
status
that
we've
achieved
or
anything
like
that,
I
think
they're
still
probably
pretty
swamped,
but
I
have
we
have.
We
heard
any
instances
no
running
into
it.
C
But
it,
but
it's
funny,
because
I
was
looking
back
at
the
rate
limiting
doc
they
have
and
they
don't
even
mention
the
what
we
were
discussing
a
few
weeks
back.
It
looks
like
now.
If
you
don't
want
to
get
rid
limited,
you
would
have
to
have
a
plan
like
they
have
two
like
pay
plans.
Basically,
otherwise
you
would
be
rate
limited.
C
D
I
can
I
can
only
add
to
that
that
I've
as
well
most
most
people
we
help
out
at
with
consultancy
and
have
like
a
harbor
or
something
as
a
caching,
proxy
or
something
in
between
nowadays.
Like
I
think,
even
before
that
message,
like
most
yeah,
most
customers
were
like
hey.
We
need
to
have
a
registry
and
no
direct
internet
access
and
all
the
companies
with
like
direct
internet
access
for
the
cluster
so
that
they
are
able
to
pull
from
dock
up,
had
some
kind
of
registry
available
and
well.
D
D
A
I'll
and
I'll
follow
up
by
the
way.
Let's
do
another
action
item
for
me
on
on
the
status
of
our
application.
B
Oh
and
we
missed
our
meeting
with
cncf
this
month,
I
was
going
to
ask
about
the
github
actions.
If,
if
that
went
through
to
bump
us
up
to
60,
instead
of
the
default
20.,
we
have
over
20
actions.
Now
I
guess
I
haven't
noticed.
If
we're
getting
queued
up,
because
there's
so
many
or
or
if
we're
fine,
it
seems
fine.
B
A
Yeah
it'd
feel
free
to
you
know
if
you
need
to
to,
because
I've
gotten
good,
I
always
get
good
traction
with
it
is
using
the
cncf
service
desk
to
you
know,
to
open
up
a
ticket
and
have
it
like
officially
tracked
that
way.
That's
a
good
idea,
yeah
that.
A
Yeah,
it's
essentially
the
cncf's
like
way
to
do
support
for
their
projects.
Okay,
yeah!
It's
super
useful.
It's
like
you
always
get
a
response
like
they
take
it
pretty
seriously.
It's
good
cool
cool!
Okay!
If
there
are
no
other
agenda
items,
then
then
we
could
go
ahead
and
adjourn
for
the
week
looks
like.
B
A
Yeah
here
we
go
yeah.
The
community
meeting
section
here
has
has
all
that
you
can
get
to
the
current
agenda
here
and
then
add
anything.
You
want
dave.