►
From YouTube: 2021-03-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
Okay,
the
recording
has
started-
and
this
is
the
march
23rd
2021
rook
community
meeting
in
terms
of
our
milestones.
We
did
a
1.5.9
just
last
week.
Just
move
my
keyboard
here.
I
I've
linked
here
in
the
agenda
doc
the
release
itself,
which
had
a
fair
number
of
fixes.
So
it
was
a
nice
little
patch
to
get
out
there,
so
that
was
out
at
the
end
of
last
weekend,
thursday,
maybe
so
that
is
out
and
now
we're
working
towards.
A
You
know
another
act,
release
for
on
1.5
the
1.5.10
release
would
be
next.
I
think
that
that's
kind
of
a
recurring
you
know
regular
pattern,
every
two
weeks,
type
of
thing
to
get
that
release
out
there.
Actually
it's
more
like
a
three
week.
It
looks
like
probably
shifted
because
the
the
major
1.6
is
going
to
go
out,
but
I
don't
think
there's
any
pressing
issues
that
are
in
1.5.
I
think
on
the
board.
There's
actually
nothing
in
progress.
I
think
too
yeah.
So
nothing.
A
I
know
of
that's
pressing
for
1.5
alexander
sebastian
same
same
for
you,
you
don't
have
anything
for
1.5.
B
I
think
there
was
an
issue.
Someone
commented
on
at
least
asking
why
this
was
removed
from
the
from
the
what
is
the
column
called
blocking
release
column.
I'm
not
sure
if
I'm
able
to
find
the
email
again
about
that.
B
C
Yeah,
but
I
don't
think
there
were
any
particular
reason
particular
reason
to.
I
think
just
blocking
release
means
that
we're
blocking
the
next
pinpoint
with
these,
but
now
it's
in
the
to-do
list
so
most
likely,
if
it's
urgent,
it
will
make
it
for
the
next
pinpoint
release.
I
guess:
do
you
know
what
number
that.
C
Maybe
the
one
called
endpoint
is
not
available
the
one
this
one.
This.
C
C
C
A
Yep
yeah,
that's
that's
that's
fair
yeah.
It
sounds
like
it
may
be.
A
good
candidate
to
get
in
for
1.5.10,
then
yeah
for.
C
Sure
I
I
feel
like
the
user
base
has
grown
somehow
in
one
five.
A
C
B
B
Yeah,
but
mostly
like,
I
think
there
have
been
a
few
cases
where
well,
how
should
I
put
it?
There
have
been,
there
have
been
a
few
people
getting
their
clusters
more
or
less
well
messed
up,
because
they
were
stayed
on
like
an
older
version
or
something
but
well.
I
think
I
think
how
should
I
put
it?
B
B
Like
well
one
or
two
like
knit
things
so
that
came
like
we
usually
realized
after
we
have
published
like
the
latest
one,
something
something
released
again
or
like
not
on
the
new
miner
release
and
it's
well,
it's
just
hard
to
help
people
with
an
old
version,
because
it's
like
hey.
We
like
we
haven't,
dealt
with
that
version
for
like
almost
a
year
now
and
yeah.
Well,
it's
good
to
see
the
people
updating
though,
so
it's
good.
A
Yeah,
it's
yeah,
it's
great.
That
is
definitely
could
be
a
challenge
to
support.
You
know
older
releases
after
we're
not
doing
batches
for
them
anymore
and
they're.
Also
paged
out
of
our
minds
as
well
too.
It
is,
it
does
get
more
challenging.
B
A
Okay
and
then
for
1.6
we're
coming
up
within
another
week
here
for
our
feature,
freeze
and
the
target
here
for
the
release
is
one
a
week
after
that.
So
basically,
two
weeks
from
now
is
when
we
are
looking
for
getting
the
1.6
release
out
there
travis
mentioned
gave
me
the
heads
up
to
go
ahead
and
reach
out
to
our
designer
graphic
designer
matt
for
an
image
for
the
blog.
So
I've
gone
ahead
and
done
that.
A
C
Yeah
we're
just
getting
distracted
with
downstream
issues
so
yeah,
but
the
goal
is
really
to
I
think
blaine's
pr
might
be
in
this
week.
A
Yeah,
should
this
be
an
review
in
progress
if
there's
already
the
pr
yeah,
I
just.
A
Oh
yeah
yeah
4500
lines
of
additions.
That
is
cool.
So
let's
do
you
want
to
move
this
to
review
and
progress
then,
because
you
just
you
review
oh
you're,
right,
yeah,
yeah
yeah
sounds
fair:
okay,
great
who's,
the
assignee
on
this
one.
C
C
I
don't
think
nitin
is.
The
thing
is
that
nitin
is
not
part
of
the
org
okay
yeah,
that's
so
annoying
that
you
have
to
each
time
you
want
to
sign.
A
C
Won't
make
it
yeah.
I
think
there
are
a
few
that
will
make
it
like
allow
to
auto
grow
with
this
on
pvc,
for
instance.
I
don't
think
anybody
has
really
committed
to
take
on
that
one
yet
so
I
I
feel
like
we
just
yeah
it's
kind
of
best
effort
yeah
but
like
they
will
likely
move
to
the
170
board.
I
think
we
do
have
the
170
board,
because
I
think
I've
added
things
for
code,
hygiene
and
cleaning
up
stuff,
so
yeah
yeah.
A
There
is
a
1.7
board
has
been
started,
yeah
a
good
point
and
we
can
yeah.
We
can
move
things
from
the
to-do
column
that
don't
make
it
for
this
into
1.7,
yep,
okay,
okay,
alex
anything.
What's
on
your
mind
for
for
1.6.
B
Well,
more
or
less
one
or
two
issues
which
even
just
popped
up
today,
at
least
on
my
mind
right
now.
I
think
I
saw
this
morning
all
right
and
I
just
found
it
rook
cockroach
db,
cluster
opened
nine
hours
ago.
B
Well,
yeah,
so
nothing
well,
nothing
really
separated
or
anything
that,
like.
I
just
saw
an
issue
popping
up
that
someone
is
using
the
kokoro
tv
operator
and
yeah
well.
B
A
Okay,
but
but
in
terms
of
like
issues
that
you
you
know,
you
definitely
want
to
see
get
included
in
1.6.
Nothing
comes
to
comes
to
your
mind,.
A
That
sounds
good
all
right,
so
yeah,
oh
all,
the
way
to
2018
yeah
okay.
So,
as
we
mentioned
two
weeks
until
the
release
here
and
so
another
week
here
until
we
get
to
future
freeze
and
then
we'll
try
to
stabilize
in
the
subsequent
week
so
next
week
by
the
next
community
meeting
ish.
Maybe
this
is
the
wednesday
we'll
be
trying
to
get
that
release
out
there,
so
we're
kind
of
winding
down
on
that
effort.
A
Okay,
so
we
can
move
ahead.
Excuse
me
to
the
community
topics
here,
so
kubecon
never
never
gives
us
like
a
moment
to
rest
and
there's
already
another
cfp
for
north
america
right.
So
that
is
a
four
days
after
the
release
that
when
that
sixth
release
the
cfp
for
kubecon
closes,
most
people
don't
do
their
proposals
until
like
the
two
or
three
days
beforehand.
So
I'm
not
surprised
if
anybody
hasn't
even
thought
about
this.
A
Yet
considering
we
feel
like
we
were
just
doing
one
for
europe
a
couple
weeks
ago,
but
yeah
this
is
so.
This
is
coming
up.
That
should
be
on
our
radar
for
the
end
of
the
weekend
there
for
sunday
april
11th
is
when
it
closes
so
into
that
weekend.
Anybody
planning
on
already
already
know
that
they're
gonna
be
submitting
a
proposal.
C
No,
I
think
we
decided
to
let
blaine
into
two.
Oh
blade
is
true
to
to
do
it
because
we
did
it
so
many
times
and
yeah.
I
think
it's
time
for
for
them
to
to
get
the
the
spotlight
up
spotlight
on.
I
guess
cool.
A
C
It's
just
yeah.
I
think
we
were
just
where
it's
just
too
bad,
that
we
couldn't
make
it
like
the
four
of
us
or
something
because
of
the
the
rules
yeah
in
place,
so
yeah
yeah.
A
A
Okay,
but
well
yep,
so
that's
coming
up
for
folks
I'll
definitely
be
submitting
something,
but
I
gotta
figure
that
out
yeah
it's.
It
may
be
a
good
opportunity
for
things
that
were
rejected
for
europe
to
resubmit,
maybe
work
them
a
little
bit
more:
rework
them
and
resubmit
those,
because
it's
fairly
tight
intervals
since
the
last
cfp.
So
you
know
resubmitting
rejected
ideas
is
not
a
bad
strategy.
A
Cool,
so
it
looks
like
there's
a
youtube
video
out
here
for
for
what's
new
in
the
new
the
pacific
release
for
steph.
Well,
it's
already
a
pretty
cool
little
graphic
there.
I
like
that
so
yeah.
So
that's
I'm
not
gonna
watch
it
together
right
now,
but
that
is
available
and
folks
can
check
that
out
to
see
all
the
new
features
and
everything
there
it's
exciting.
C
No,
it's
like
literally,
it
should
be
this
week
or
next
week.
Oh
cool,
it's
like
soon
yeah,
it's
like
it's
should
be
there
almost
yeah
almost.
A
B
C
Yeah,
that's
the
target
end
of
this
month
and
soon
after
we
would
be
raising
one
and
reusing
one
sex.
Exactly
I
feel
like
we.
If,
if
it
slips,
then
we
should
slip
a
little
bit
as
well,
so
that
we
can
use
it
as
the
basis
for.
A
A
A
Okay-
and
then
I
mentioned
this
in
the
maintainers
channel,
but
it's
it's
worth
bringing
up
here
as
well
too
for
a
broader
audience
that
so
github
actions
they
had
a
security
vulnerability
that
they
sent
out
a
message
about
just
a
couple
days
ago.
A
The
vulnerability
was
actually
back
in
february
early
february
and
they
fixed
it
apparently
pretty
pretty
quickly,
but
they
so
people
repost
using
github
actions
were
vulnerable
to
the
issue,
but
github
believes
from
their
forensics
and
their
investigation
that
there
were
not
exploits
of
this
in
the
wild.
A
It
was
responsibly
disclosed
this
vulnerability,
so
it
doesn't
seem
to
have
been
exploited,
but
they
did
mention
to
take
a
look
through
in
that
one
day
window
when,
when
we
were
vulnerable
to
this
from
the
github
actions
bug
for
february
4th
february
5th
to
see
if
there
was
any
unauthorized
commits.
Basically
the
exploit
would
be
that
somebody
could,
with
github
actions,
could
craft
a
workflow
that
they
could
get
access
to
your
github
token
and
do
unauthorized
actions.
A
So
I
looked
through
the
commits
and
releases
and
stuff
like
that
back
then,
during
february
4th
and
5th-
and
I
didn't
see
anything
that
looked
unauthorized-
I
saw
activity
of
course,
but
it
all
looked
to
be
from
users
that
man
we're
familiar
with,
and
people
that
are,
you
know,
expected
work.
So
I
didn't
see
anything
fishy
get
in
there.
A
But
if
people
want
to
take
a
look
too
for
anything
in
the
repo
or
any
artifacts
there
from
those
those
two
days
february,
4th
and
february
5th,
then
that's
totally
totally
reasonable
to
take
a
look
as
well
too
just
to
get
more
coverage
on
that
more
eyes
on
that
yeah,
and
then
I
had
a
question
to
seb.
Maybe
you
can
help
out
with
that.
So
we
we
have
branch
protection
rules
in
place.
You
know
for
master
and
release
all
the
release
branches.
I
was.
A
I
was
curious
if
you
knew
what
is
the
life
cycle
for,
like
the
mergify
branches,
do
those
get
automatically
created
by
the
merger,
five
bot
and
then
they'll
get
deleted.
C
A
A
C
Oh
okay,
interesting
looks
like
I
missed
it,
which
I
I
guess
yeah.
I.
C
A
Then
yeah
this
one
here
yeah,
I
don't
know
this
branch,
something
merged.
C
C
A
It
okay
yeah,
no
problem
with
it.
Yeah
see.
I
was
just
when
github
said
that
there
were
some
unprotected
branches.
You
know
they're
not
covered
by
our
normal
pr.
You
know
human
manual,
pr
workflow
and
protection
branch
protection.
I
was
curious
what
they
were
so
that
totally
explains
both
of
them.
Why
they
were
there
and
we
unders.
We
understand
those
now
and
that's
that's
perfect.
That's
that's
great
sounds
good
cool
thanks
yeah
and
then
you
know
accidentally
pushing
to
that
branch.
A
You
know
like
mistakes
happen
of
course,
and
like
it's
recently
in
another
project,
I'm
on
we,
we
accidentally
pushed
some
aws
keys
to
to
the
public
branch,
so
that
was
we
had
to
rotate
all
the
keys
and
stuff.
So
that
was.
C
Think
I
was,
I
was
reading
something
about
this
is
that
that
they,
I
think
I
think
they
were.
They
were
doing
experiments
where
they
were.
They
were
like
pushing
out
keys
and
get
up
yeah,
and
I
guess
they
were.
They
were
just
waiting
to
see
how
long
it
will
take
for
those
keys
to
be
used,
and
it's
just
a
few
minutes.
A
Exactly
so
exactly
it
only
takes
a
few
minutes
before
those
keys
start
getting
used
and
trying
to
access
resources
in
your
aws.
It's
pretty
crazy
and
there's
a
whole
bunch
of
automation
around
that.
Now
that,
like
github,
yeah
and
aws
they'll
send
you
an
email
like
within,
like
there's
a
five
minute
delay.
A
B
That's
quite
hard
because,
for
example,
I
have
like
a
presentation
like
a
gitlab
presentation,
and
I
think
I
just
generated
like
a
self-signed
certificate
for
it,
and
I
added
it
as
a
secret
for
the
in
the
repository
and
pushed
it
public,
and
I
also
got
like
an
email
five
minutes
and
I
was
like
well
yeah
thanks
for
telling
me
there's
a
priority
and
there's
about
certificate
and
private
key
in
the
in
a
public
repository.
But
well
that
should
be
there.
A
Yeah,
but
thank
you
for
for
the
watchful
eye.
I
appreciate
it
awesome
well,
yeah,
that's
all
the
things
we
had
on
the
agenda
here
and
were
there
anything
any
other
topics
that
anybody
wanted
to
bring
up.
A
All
right,
well
cool,
so
we'll
keep
keep
working
over
the
next
two
weeks
towards
the
1.6
release
and
thanks
everybody
for
joining
today
and
we'll
see
you
all
online
or
on
slack
yep.
Thanks.