►
From YouTube: 2021-04-20 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
has
started,
and
this
is
the
april
20th
2021
rook
community
meeting
big
news
is
the
release
of
1.6
last
week.
Obviously,
so
congratulations
to
everybody
on
getting
that
out
the
door.
You
know
there's
a
number
of
integration
tests
and
you
know
obstacles
to
try
to
get
to
the
finish
line
there,
so
that
was
that
was
great
to
see
from
from
everybody.
A
So
we'll
definitely
be
it
was
fun
yeah.
It
was
super
fun,
we'll
be
getting
to
some
patches
again.
Now
that
the
big
release
is
out
there
travis
do
you.
Anybody
want
to
kind
of
talk
about
high
level,
lessons,
learnings,
etc
or
news
from
1.6
itself.
Before
we
start
talking
about
batches
and
upcoming
stuff.
B
Yeah
so
follow
up
from
1.6.
I
think
there
were
definitely
a
few
issues
to
resolve
at
the
last
minute.
I
think
with
I'm
going
to
forget
some
of
them.
Now
I
mean
pacific.
What
was
it
with
pacific?
Basically,
the
some
integration
tests,
just
weren't
working
reliably
with
pacific
and
then
got
that
and
then
the
cassandra
test
took
a
few
days,
but
with
janice's
help
we
got
those
done
and
then
those
were
masking-
or
at
least
we
didn't
notice.
Some
other
ci
issues
because
of
the
cassandra
failures
had
been
written
for
a
few
days.
B
So
then-
and
that's
actually
just
affecting
the
1.5
branch,
because
we
had
to
back
port
the
cassandra
test
fixes
there
and
then
we
found
so
there's
still
an
issue
open
for
1.5
builds
to
get
green
again,
but
yeah
those
issues.
All
aside,
we
got
through
it.
We
got
the
release
out
and
I'm
confident
we've
got
good
quality
there.
As
always,
there
are
a
few
issues
to
follow
up
on.
We've
already
got
a
few
fixes
in
getting
ready
for
a
one
release.
B
And
a
couple
of
issues,
I
guess
I
didn't
list
any
issues
specifically
to
talk
about,
but
there
is
one
where,
if
you've
upgraded,
if
someone's
upgraded
a
few
times
from
our
v1
beta
1
crds,
there's
an
issue
where
the
preserve
unknown
fields
flag
is,
is
for
some
reason
preventing
the
upgrade
now,
so
people
need
to
do
a
manual
workaround
where
you
remove
that
that
flag
from
the
crds
before
you
upgrade.
B
Other
issues-
oh
erasure
coding,
was
broken
in
the
schema,
but
that
that
was
an
easy
fix
and
a
couple
other
things
but
yeah.
I
think
thursday
we're
on
track
it'll
be
good
to
have
the
dot
one
release
out
and
but
I
haven't
heard
of
any
major
issues
with
with
the
release
really
so
overall,
it's
it's
good
news.
A
What
did
so
did
we
get
to
a
good
root
cause
then,
or
a
good
per
more
permanent
fix
for
the
cassandra
integration
test
issues
that
giannis
was
working
on.
B
It
looks
like
the
test
started
breaking
because
we
updated
the
base
image
for
the
jenkins
ci
tests.
The
test
runs
and
like
it
was
updated
up
until
20
20
that
doesn't
sound
right
anyway,
and
the
cassandra
testers
started
failing.
So
we,
instead
of
trying
to
get
the
cassandra
test
working
on
on
that
in
jenkins.
B
B
A
A
B
B
That
would
probably
be
our
final
official
patch
release
for
1.5,
maybe
not,
but
but
if
we
can
get
that
out,
people
have
been
waiting
for
that
top
fix
for
a
while,
at
least
with
watching
for
note
events
and
then
the
that
issue
in
the
blocking
release
column,
that's
the
one
with
the
integration
test,
still
failing,
but
it
doesn't
actually
affect
upgrades.
It's
just
a
test
issue.
A
Right
so
we
still
have
red,
that's
what's
causing
the
still
having
red
tests
and
in
the
105
branch,
exactly
yep
yep.
A
Stuff
and
then
have
we
already
made
any
updates
to
1.6
board
for
upcoming
patches
too,
or
is
too
soon
for
that.
B
Yeah
I
was
trying
to
make
sure
it's
updated
as
far
as
what's
in
review.
What's
that
issue
in
the
blocking
release
column,
I'd
like
to
understand
before
we
get
that
one
out,
and
then
I
guess
I
didn't
mention
that
one,
yet
that
one
is
if
you're,
installing
with
pacific
and
you're,
using
a
metadata
drive
for
those
these.
A
Be
a
simple
resolution:
yeah
if
it
was
just
an
output
change,
just
change
the
way
we
parse
it
or
handle
it.
Hopefully,.
C
A
Cool
then
yeah
that'd
be
great.
If
that's
an
easy
fix,
that'd
be
wonderful.
C
A
Can
and
as
feedback
comes
in
from
the
folks
in
the
community
upgrading
to
1.6-
and
you
know
trying
their
scenarios
with
it,
then
we
can
remain
pretty
agile
in
terms
of
fixes
that
we
take
on
that.
We
would
like
to
patch
in
response
to
issues
that
found
out
in
the
wild
after
release
after
the
release.
A
All
right,
well
yeah,
definitely
great
work,
everybody
for
getting
the
1.6
out.
That's
that's
definitely
going
to
happen,
and
you
know,
and
not
last
minute
before
kubecon
as
well
too.
So
it's
nice
to
kind
of
not
be
in
that
habit
here,
get
it
out
a
couple
weeks
before
keep
going
so
we
have
some
breathing
room
there.
A
Else:
okay:
we've
got
other
other
issues
on
the
table
here.
So
we'll
continue
down
the
agenda
dock
here:
okay,
so
yeah
ci
improvements,
I
think
blaine
you're,
adding
some
to
this
is
travis
or.
B
We've
I
mean
we
all
know
that
we
need
to
keep
a
green
ci,
so
we
can
consistently
be
consistent
about
delivery
and
not
get
bitten
when
things
they
read
too
long
like
that.
That
seems
like
that.
Always
what's
a
recurring
challenge,
I
think
any
time
you
change
software
you're
going
to
have
that
challenge,
but
so
just
I
think,
with
the
github
actions,
we're
seeing
more
reliability
as
we
convert
them
from
the
from
running
in
jenkins.
B
As
of
just
a
few
days
ago
now
so
when
you
merge
to
master
or
a
release
branch,
you
get
a
single
email
that
tells
you
the
results
of
all
the
github
actions.
So
that's
really
nice
that
I
don't
feel
like
we're,
not
consistently
green
in
there
yet
so
we
need
more
follow-up
there.
But
I
really
like
this
idea
of
having
that
single
email
that
tells
us
the
results
afterwards,
I'm
not
clear
who
gets
that
email
like
if
it's
all,
if
it's
just
core
maintainers
or
if
it's
everybody
in
the
work
github.
B
A
C
B
A
B
Well,
the
one
thing
we
definitely
rely
on
jenkins
for
still
is
to
publish
the
release,
so
in
1.7
we
want
to
have
actions
also
for
that,
but
otherwise
yeah,
I
think
everything's
running
as
we
get
up
actually
would.
B
D
D
B
Yes,
I
think
pretty
soon
we
should
be
able
to
enable
that
so
that
master
builds
are
published
that
way
and
we
could
disable
publishing
from
master
from
jenkins
and
then,
as
after.
We
see
that
okay,
that's
stable
for
master
now,
let's,
then
we
could
convert
for
the
release
branch
as
well,
and
then
that
might
be
the
last
thing.
We
really
need.
A
C
A
Yeah
then,
so,
if
we
did
that,
then
the
our
aws
account
would
basically
just
be
s3
object,
storage
right,
just
buckets
for
charts
and
artifacts.
B
A
All
right,
okay,
then
we
want
to
go
ahead
on
down
to
stuff
month.
I
think
mike
you.
I
think
you
added
this
one.
E
Yeah,
so
we
have
a
kind
of
like
an
event
but
we're
accepting
proposals
for
doing
a
month,
long
of
self
presentations,
and
so
these
are
going
to
just
be
scheduled
throughout
the
month.
And
we
are
accepting
proposals
both
on
presentations
through
a
set
time
and
lightning
talks
as
well
as
unconference
sessions,
so
that
people
want
to
set
up
different
discussions.
So
we
will
be
accepting
these
throughout
may
12th
and
then
working
with
each
submitter
and
to
schedule
them
out
for
the
month
of
june.
A
E
B
A
Thank
you
mike
cool
guys,
all
right
awesome,
and
then
I
just
added
this
note
about,
because
a
lot
of
people
have
been
bit
hard
by
this.
This
is
actually
fairly
catastrophic
for
a
lot
of
people
in
the
cncf
in
general,
or
the
greater
ecosystem
codecov.
So
just
to
confirm
I
I
looked,
and
I
was
we
do
not
use
code
cover
for
rook
right.
A
Okay,
excellent
good,
thank
goodness
because
there
is
a
very
bad
security
breach
with
some
of
code
covers,
like
integrations
that
they
do
to
upload
your
code
coverage
results
as
part
of
your
ci
pipelines,
and
basically
it
was.
It
was
vulnerable
for
three
months
and
malicious
party
there
that
whoever
was
was
had
exercised.
This
vulnerability
could
get
access
to
all
of
your
tokens
credentials.
A
You
know
all
sorts
of
stuff,
that's
available
in
the
environment,
for
a
ci
build
which
tends
to
be
a
lot
when
you're
running
releases
and
stuff,
like
that,
and
you
get
all
of
your
all
of
your
tokens,
everything
so
other
projects.
I
know
that
are
using
codegov.
You
had
to
rotate
everything
all
your
production
credentials,
everything
and
that
was
exposed
for
three
months.
So
it's
pretty
pretty
catastrophic.
A
I
don't
know
I
would
wonder
if
codecov's
still
gonna
be
in
business
after
this.
This
is
a
horrendous
breach.
Yeah
right,
it's
like
good,
so
brooke
is
safe
in,
like
other
every
other
projects.
You
guys
are
a
part
of
you
know.
If
you
haven't
heard
about
this
or
you
haven't,
looked
into
it
yet
definitely
make
sure
that
if
you're
using
codecov
anywhere
to
rotate
everything,
the
cncf
sent
out
an
email
about
it
to
multiple
lists
as
well
too,
to
make
to
get
more
visibility.
So
do
you
share
the
word.
A
D
A
It's
ridiculous
how
bad
this
speech
was:
okay
and
then
a
lighterhearted
email
that
the
cncf
sent
out
was
about
the
maintainer
survey,
so
that
should
be
they
sent
that
to
the
brook
maintainers
email
list.
So
you
should
have
a
link
there
to
fill
out
the
survey
for
the
first
half
of
2021
and
they
really
appreciate
the
feedback
and
they
do
I've
noticed
they
do
improve
the
programs
in
the
way
that
they
support
the
projects
from
from
the
feedback
from
the
maintainers.
So
take
a
take
a
chance
to
fill
that
out.
If
you
haven't
already.
A
All
right-
let's
see
this
here-
include
the
foam
full
zoom
meeting
link
in
the
invitation
is
that.
D
A
D
Yeah
hi,
no,
it's
just
me
being
lazy,
I
guess,
but
each
time
I
have
to
click
to
the
invite
I'm
being
redirected
to
the
invite
link
that
doesn't
have
the
password
embedded.
So
each
time
I
open
zoom,
I
have
to
go
ahead
and
copy
the
password
again
from
the
document.
So
if
we
could
have
the
entire
link
in
the
invitation,
then
I
guess
that
would
help.
C
D
A
A
D
D
A
No
problem
we're
happy
to
get
you
sorted
out.
My
friend,
okay
and
then
oh
just
gonna,
delete
it
from
the
history
all
right
and
then
for
upcoming
quincy
is
looks
like
there's
a
link
to
the
discussion
here.
That
happened.
E
Yeah,
so
this
is
the
recording
if
anybody
wants
to
go
through
it,
and
I
have
provided
the
agenda
link
as
well
just
for
the
rook
discussions
that
took
place
for
quincy.
I
don't
know
some
of
the
other
groups
are
doing
follow-up
meetings.
Travis.
I
don't
know
if
you
were
planning
on
doing
one,
but
these
are
essentially
to
set
the
priorities
based
on
what
was
discussed,
but
they
are
optional.
But
if
you
want
to
set
one
up
and
we
can
work
offline.
B
B
E
B
A
B
C
A
Cool
okay,
nice
yeah
thanks
thanks
for
linking
this,
then
here
mike
appreciate
it.
E
Yeah,
thank
you.
Everybody
who
attended
and
provided
technical
discussions
so.
A
Awesome:
okay:
are
there
any
other
agenda
items
here?
Is
the
stuff
that
folks
want
to
bring
up.
A
Thanks
to
blaine
for
updating
the
meeting
notes
agenda
with
some
notes
as
we're
going
through
the
discussion
here.
I
really
appreciate
that
blaine
awesome
all
right.
Well,
if
that
is
everything
then
then
we
can
go
ahead
and
adjourn,
and
you
know
congratulations
to
everybody
and
thanks
for
all
the
hard
work
too
on
getting
you
know
the
1.6
release
out
last
week.
So
we'll
see
you
everybody
online,
then.