►
From YouTube: 2020-11-17 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
A
So
let's
jump
into
the
milestones,
because
we
just
had
a
big
1.5
release
that
went
out
and
the
intent
was
to
get
that
out
before
kubecon.
So,
let's
jump
into
some
of
these
here,
you
know
1.3,
I
don't
think
we're
having
any
patches
or
servicing
going
out
for
1.3
that
we
have
planned
at
least
so.
Maybe
we
can
hop
to
1.4
first
and
talk
about
some
of
the
things
we
may
patch
your
back
port.
There.
B
Yeah
1.4
is
has
been
pretty
stable.
I
don't
know
that
we
have
any
urgent
need
to
get
another
release
out.
So
I
think
we'll
hold
this
thought,
maybe
another
couple
weeks
till
after
the
thanksgiving
holiday
and
then
maybe
in
a
couple
weeks,
we'll
do
another
one
if
needed.
I
think
there's
already
been
something
back
ported
since
the
seven
released
last
week,
so
we
should
do
another
update,
but
we
can
wait
a
couple
more
weeks.
I
think.
A
All
right,
let's
talk
about
1.5,
then
so,
first
of
all
great
release
to
get
out,
and
that
was
done
on
friday
of
last
week.
So
it's
still
fresh
and
hot
off
the
presses.
There.
A
So
we
are
planning
a
1.5.1.
A
patch
for
this
week
looks
like
travis.
Do
you
want
to
fill
us
in
on
that
more.
B
Yeah,
so
just
to
follow
the
the
usual
pattern
of
you
know
after
release,
we
look
for
any
urgent
issues.
We
need
to
fix
and
this
and
do
a
release
within
one
week
after
so
I
think
thursday
is
just
the
target.
There
are
a
couple
of
issues
that
come
up.
Nothing's
super
urgent,
I
think
so
far,
but
we'll
just
plan
on
that
first
release
on
thursday.
I
think,
since
that
gives
us
a
lead
on
thanksgiving
before
some
of
us
are
out
too.
B
B
A
B
No,
I
think
it
didn't
get
tagged
yet.
I
didn't
review
this
board
this
morning.
Unfortunately,
oh
got
it
not
all
up
to
date,
I'll
do
that
yep
and
then
there's
yeah
there's
some
other
changes
coming
in.
That
would
be
good
to
have
in
their
lease
but
yeah.
Overall,
it's
been
a
pretty
quiet
weekend
as
far
as
since
the
1.5
release-
or
maybe
people
just
haven't
installed
it
yet.
B
A
Awesome
that
sounds
great
any
any
other
comments
about
the
1.5
release
or
issues
that
are
on
our
radar
to
be
patching
and
backboarding.
B
A
So
that's
all
the
news
on
releases.
It's
good
to
get
the
quarterly
release
out
there
and
then
matt
matt
howe
heilman
did
confirm
that
he'll
be
able
to
provide
images
for
us
or
icons
for
the
blog
posts
for
upcoming
releases.
So
we
just
give
him
a
week's
lead
time
and
he'll
be
able
to
whip
up
a
little
a
little
image
for
us
to
use
there.
So
we
can.
We
can
let
our
artistic
skills
go
unsharpened
and
dull
again.
A
Okay,
all
right
all
right
so,
as
we
talked
about
kubecon
in
north
america
is
ongoing
right
now,
as
we
speak
friday
afternoon,
eastern
time
and
evening
later
evening,
european
time
there
is
the
talk,
the
rook
talk
and
a
live
q
a
afterwards
that
blaine
alexander
and.
A
Cool
okay,
yep,
so
the
three
of
you
all
will
be
more
than
enough
to
handle
the
q
a
there.
So
that's
all
in
good
hands
and
thank
you
folks
for
for
stepping
up
to
do
that.
A
Okay,
anything!
If
there's
anything
else
about
kubecon,
you
know
feel
free
to
share
that
either
in
slack
or
chime
in
you
know
during
this
meeting
here
or
you
know,
the
the
really
the
big
presence
that
we
have
is.
Is
you
know
in
the
being
mentioned
in
the
queue
keynotes
in
the
for
the
project
updates
that
we
get
around
being
graduated
and
the
talk
that
we
have
on
friday.
So
that's
pretty
much
our
big
day.
We
don't
have
a
rook
booth.
A
This
time
the
suitcase
only
gave
out
five
five
total
booths.
We
decided
we
didn't,
we
weren't
going
to
invest
in
one
anyway,
so
not.
A
Presence
going
on
here,
but
would
be
nice
when
they're
in
person
again
maybe
late
next
year.
Who
knows.
D
A
B
A
Yeah
and
eventually
all
right,
so
an
update
on
our
helm,
charts.
B
B
But
if
you
change
that
setting
and
you
upgrade,
your
cluster
will
be
killed
and
I
haven't
found
a
way
that
we
can
prevent
that
from
happening.
B
D
Well,
that's
that's!
How
seth
and
not
enough
that's
how
helm.
B
D
A
B
B
A
Okay,
that's
okay,
cool
yeah:
it
doesn't
it
made
it
for
that
that
option
is
in
there.
I
don't
I
mean,
maybe
there's
some
hooks
you
can.
We
could
add
to
the
chart
to
handle
that,
but
I
don't
know
how
much
logic
you
get
to
invoke,
or
you
know
how
much,
how
much
like
how
much
flow
you
can
actually
have
in
there
to
like
kind
of
block
that
type
of
change
during
an
upgrade.
I'm
not
I'm
not
sure.
A
Okay,
so
ci
we
can
move
on
to
that
there
not
running
jenkins
by
default.
Is
super
cool.
I
think
collective
headaches,
maybe
just
subsided
amongst.
B
Yeah
so
kudos
to
subham
and
sebastian
for
working
through
getting
our
integration
test
running
on
github
actions,
we're
about
ready
to
merge
the
last
pr
for
that
that
you've
got
there.
So
this
takes
each
of
our
suites
and
runs
them
as
a
github
action
yeah.
So
for
prs
at
least
for
now,
once
this
is
merged,
we
need
to
only
need
a
separate
pr
that
modifies
the
jenkins
file
to
skip
the
ci.
A
Yeah
this
is
this
is
awesome.
I
I
absolutely
love
this
and
then,
and
then,
if
once
we're
off
of
that
too
travis,
you
know
with
github
actions
exclusively
then
that
that
helps
a
lot
too.
With
our
you
know,
aws
bill
for
running
jenkins
and
everything
like
that
too.
So
that
sounds
fantastic.
A
Were
there?
Do
we
see
any
speed
ups
as
well
too,
like
the
integration
tests,
like
the
time
that
they
take
to
run?
Is
that
any
better
or
worse
or
different
than
with
jenkins.
A
D
Well,
I
guess
the
only
thing
I
can
tell
is
that
the
longest
run
was
18
minutes
total,
that's
short
yeah,
and
previously,
when
we
had
to
go
through
the
pipeline,
we
were
like
at
some
point.
We
were
up
to
an
hour
before
that
we
managed
to
reduce
to
reduce
it
to
40
or
45
minutes,
but
because
it's
a
pipeline
and
then
you
have
to
build
and
do
the
unit
tests
and
because
you
also
have
to
wait
for
the
worker
to
be
available
where,
on
the
github
action
you
just
get
a
worker
immediately.
A
D
I
just
found
one
which
I've
registered
and
I
think
I
have
I
haven't
seen
it
for
like
a
week
or
two
really
yeah.
It's
super
intermittent,
but
I
think
it's
more
or
less
like
a
timing
issue
when
we
create
partitions
like
we
should
be
waiting
a
bit
more
for
the
prop
devices,
but
it
is
like
so
unfrequent
that
I
don't
really
feel
like
working
on
it
right
now,
but
it
is,
I
mean
other
than
this
one.
I
don't
think
we
have
seen
any
intermission
failures
at
this
point.
D
D
Yeah
and
because
we
are
well,
you
were
there,
but
because
we
are
a
graduated
project
now
we
get
more
rate
limits
for
for
the
repo.
So
it's
not
like.
We.
D
D
So
if
you
see
that
we
have
more,
then
it's
it's
better,
but
I
mean
at
this
point:
it's
not
like
we
have
seen
any
and
even
if
we
do,
I
think
it's
pretty
acceptable
because
from
the
shortest
to
to
to
the
longest,
we
I
think
on
average
we
are
about.
I
don't
know,
maybe
10
minutes,
maybe
less.
So,
even
if
we
have
to
wait
a
bit,
then
we
just
have
to
wait
like
max
10
minutes
on
average
to
to
get
a
worker.
D
So
that's
like
that's
that's
one.
I
think
it's
a
major
milestone
for
us
right
now
and
what's
next
is
that
to
fully
convert
and
fully
like
completely
move
away
from
from
jenkins,
we
would
have
to
implement
an
action,
a
a
hook,
action
to
do
releases
and
do
build
releases,
and
that
can
be
done
as
well.
D
So
we
just
need
to
investigate
a
bit
more
and
connect
our
docker
account,
which
actually
brings
me
to
an
interesting
question
which
is
not
in
the
agenda
and
maybe,
if
we're
done
with
this
one,
I
think
it's
a
good
segue,
because
we
recently
docker
announced
that
they
really
now.
I
think
it
was
november,
2nd
they're
really
enforcing
their
their
rich
limiting.
D
D
D
D
B
A
Fluffle
that
people
are
angry
about,
we
get
yeah,
we
have
20
free,
sorry,
not
20
free,
but
we
pay
for
20
private
repositories
per
month.
Is
our
plan
sebastian?
Okay?
So
I
don't
know
what
impact
that
has
on
rate
rate
limiting
then
exactly
because
it's
kind
of
it's
a
bit
confusing
like
the
messaging
around
it
and
what
the
actual
impact
is
and
such,
but
so
yeah.
C
D
So
maybe
we
don't
really
see
any
effects
yet
and
yeah.
I
agree
with
you
jared
it's
really
hard
to
quantify.
I
guess
what
those
limits
would
apply
and
how
like
we
might,
they
might
be
triggered
and
how
we
might
be
impacted,
and
I
see
that
at
least
internally.
We
got
an
email
about
this
and
it
looks
like
everyone
is
freaking
out
and
because
obviously
is
red
hat
and
a
lot
of
projects
are
moving
on
quay.
D
A
Yeah-
and
they
do
they
do
have
a
like
an
open
source
project
plan
too.
That,
like
that
you
can
apply
to
to.
I
remember
hearing
somebody
mention
that
that
is
kind
of
a
a
bit
of
a
workaround
I
suppose
to
get
like
exempted,
or
you
know,
approved
to
not
have
the
right
limits
of
enforce.
So
that
might
be
something
to
look
at
as
well
too,
like
this
open
source
application
guide
here,
because.
D
A
D
They
don't
use
docker
anymore,
so
it's
accepted
yeah
for
the
the
whip
branches
like
when
you
push
a
when
you
push
a
patch
in
itself
and
it's
when
you
pat
and
you
push
it
into
like
cfci,
then
you
get
a
container
image
build
and
it's
under
a
dedicated
query
instance:
not
the
way,
not
the
option.
D
D
Yeah
the
set
main
repo
yeah
yeah,
but
not
the
images
we
do
use.
When
I
said
ceph
I
said
like
get
up
stuff,
not
the
docker
except
stuff
images
right.
Just
the
code.
D
A
Yeah,
absolutely
you
know
we
maybe
should
we
should
consider
just
applying
for
the
open
source
application
project
application
thing
regardless
because
it
sounds
like
it
might
be,
might
be
helpful
either
way.
But
if
we
certainly
if
we
get
any
reports
of
here's,
here's
a
window
here,
let
me
bring
this
over.
I
think
you
can
see
this
here.
So
if
we
get
any
user
reporting,
this
type
of
behavior
like
we
should
take
action
for
sure
to
address
that
either
with
like.
A
Well,
if
we
haven't
applied
to
the
open
source
application,
they
do
that
or
you
know,
increase
the
paid
plan
or
move
to
koi
dot
io
or
something
like
that.
What
are
what
are
the
long
term
maintenance
or
plans
for
quay
is
that
is
that
something
that'll
be
like
in
the
long
term.
Road
map
for
for
red
hat.
D
D
Really
like
on
on
the
when
you
look
at
what
happened
in
the
past,
the
docker
like
the
docker
issue.
That
appeared
like
I
think,
two
or
three
years
ago,
and
then
you
had
this
little
thing
kind
of
okay,
then
red
hat
is
going
to
write
something
else
and
that
redder
has
spot
man
so
red
activity.
Actually,
video
has
moved
away
from
docker
in
general
and
even
more
with
quay.
I
guess,
because
that
doesn't
even
need
to
have
a
docker
registry
so
yeah.
A
A
A
How
about
how
about
I
take
an
action
item
just
to
fill
this
fill
this
guy
out
and
see
how
it
goes.
It
doesn't
look
like
it'll
hurt.
B
A
B
Me
let
me
write.
A
A
Okay,
anywho,
okay,
so
then
outreachy
there's
some
updates
from
from
blaine.
I
think
you
added
some
stuff.
A
C
All
right
I
switched
to
my
laptop
microphone,
I'm
not
sure.
What's
going
on
yeah,
we
have
an
outreachy
intern,
the
we
have
one
applicant
for
the
disaster
recovery
for
first
fmons,
like
restoring
quorum
project
named
modavi,
the
like
whether
mondavi
is
accepted
as
an
intern
or
not
will
be
announced
november
23rd
and,
if,
like
I'm,
assuming,
there's,
also
a
process
by
which
madavi
either
agrees
to
be
an
intern
for
for
rook,
also,
which
is
sort
of
the
kind
of
I
guess,
open
question
that
we
have.
C
But
those
will
be
announced
next
week
and
then
the
start
date
is
two
weeks
from
now
on
december
21st.
If,
if
she
does
intern
with
us
december,
1st.
C
Yeah,
it's
it's
two
weeks
from
today,
it's
through
tuesday,
okay.
A
Yep,
well,
that's
exciting,
exciting,
updates
playing
for
sure
it's
it's
great
to
have.
You
know
more
contributions
and
growing
the
community
there,
especially
with
folks
earlier
on
in
their
career
to
to
get
that
experience
and
be
part
of
the
community.
Here
is
always
fantastic.
C
A
It's
a
bit
of
a
bit
of
a
ramp
up
cool
awesome
blaine.
That
sounds
great,
so
that
was
the
end
of
the
topics
we
had
on
the
agenda.
Was
there
any
other
agenda
items
that
folks
wanted
to
bring
up
or
we
can
all
go
head
on
over
to
kubecon
to
enjoy
the
content
there.
B
D
Anyway,
yeah
I
I
got
it
delivered,
but
got
it
delivered
to
my
parents
home,
because,
because
we're
moving
soon-
and
I
was
kind
of
like-
because
I
actually
previous
speaker
gift-
I
had
registered-
and
she
never
got
it
where
this
time
I
registered
and
like
two
days
later,
it
was
delivered
so.
A
A
Cool
alrighty
cool,
hopefully
we'll
see
folks
at
kubecon
and
we'll
see
you
all
online
and
we'll
be
working
towards
the
1.5.1
patch
release
later
on
this
week,.