►
From YouTube: 2020-10-06 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
welcome
everyone
to
the
october
6th
work
community
meeting,
it's
good
to
be
with
you
today.
Excuse
excuse
jared
who
come
in
couldn't
be
with
us
and
let
me
go
ahead
and
try
and
share
my
screen
again
and
we'll
talk
through
the
agenda
here.
Let's
see
so
desktop
one
now,
let's
try
this
one
share.
A
Okay,
can
you
just
see
my
google
doc
window
yeah
yep
all
right
here
we
go
then,
okay,
so
we'll
start
with
the
usual
project
board
discussion
and
what's
happening
so
1.3
releases.
I
think
we're
in
a
good
place
there
we
don't
have
any
more
planned
releases.
The
project
board
is
empty,
no
active
issues.
A
A
I'll
take
that
as
a
no
and
we'll
go
on
to
the
1.4
board,
all
right,
so
the
1.4
board.
I
think,
there's
nothing
urgent
that
I'm
aware
of
we
can
follow
our
bi-weekly
cadence
for
for
releases
just
to
pick
up
the
latest
bug
fixes
that
would
mean,
let's
see
last
thursday
was
our
last
release
the
1.2.5
so
we'll
plan
on
thursday
of
next
week.
A
I
don't
know
that
we
need
to
talk
through
any
of
these
specific
issues
and
I've
got
a
later
agenda
item
to
talk
about
edge
of
so
we'll
come
back
to
that
one
in
a
minute.
But
does
anybody
have
specific
issues
to
bring
up
for
1.4.
A
A
Move
first,
one
into
the
list
to
the
left
to
in
progress.
No,
no,
no
yeah,
this
one
yeah
yeah
yeah,
that's
in
progress!
Exactly
yep
super
is
working
on
the
api
extensions.
Oh,
maybe
just
to
talk
to
the
api
extensions
for
a
minute.
So
the
you
know
in
kubernetes
1.17
the
or
was
it
16.?
Sorry,
the
api
extensions
v1
became
available
and
v1
beta
1
was
deprecated.
A
A
The
crd
schema,
which
we
have
very
large,
complex
crds.
So
it's
not
exactly
easy
to
define
all
of
that
and
yeah,
so
that
the
risk
is
that
we
have
some
optional
settings
that
we
forget
to
add
to
the
schema
and
then
somebody's
crd
doesn't
work.
So
I
just
want
to
be
really
thorough
with
this
one
and
make
sure
we
get
as
much
coverage
as
we
can
on
that
testing.
A
A
A
So
don't
talk
to
your
friends
in
the
media.
Quite
yet
until
that's,
but
we
are
excited
that
that
is
done.
So
thank
you
for
all
your
hard
work,
contributing
to
that.
It's
been
a
great
journey.
A
I
am
working
on
a
blog
with
that
jared
and
I
were
at
least
working
on
that
I'll
send
out
a
draft
to
the
maintainers
for
those
interested
in
giving
feedback.
Or
if
you
have
a
you
know,
we
should
have
multiple
quotes
from
maintainers.
I
think
in
that
blog
that'd
be
really
nice
to
to
get
people's
input
on
on
everything
alexander
and
sebastian,
and
then
others.
B
Yeah
yeah:
that's
that's
great
news,
especially
also
to
put
it
from
to
directly,
as
you
said,
with
quotes
kind
of
it's
especially
good
for
the
customers,
which
are
actively
actively
using
rooksef.
To
hear
that
news.
It's
awesome,
yeah.
A
B
A
A
Components
in
it
now,
honestly,
though,
it's
it's
good,
it's
good
publicity
for
the
project,
but
at
the
end
of
the
day,
we're
still
still
working
on
features
and
bug
fixes
making
it
the
best
it
can
be,
and
it's
just
a
nice
marketing,
milestone
yeah.
I
think
it's
a
good
message
also
for
the
adoption
too.
The
maturity.
A
B
A
B
B
The
question
arises
if
it
still
makes
sense
to
use
well
as
if
we
have
it
and
the
ch
well,
if
it
still
makes
sense
to
have
the
helm
charts
in
the
same
repository
as
rook
itself,
instead
of
having
a
separate
repository,
especially,
I
think
in
the
starting
well
starting
period
of
the
helm
chart
even
with
reviews.
As
such,
I
think
there
might
be
a
lot
of
changes
needed
fast
to
get
this
whole
thing
moving.
B
A
B
That's
the
that's
the
thing
I
learned,
while
working
with
helm
in
the
last
well
last
few
weeks
months,
that's
like
there
isn't
really
necessarily
a
connection,
at
least
to
the
chart
version
to
the
application
version.
There's
two
variables:
ol2
yeah.
B
Well,
it's
called
parameters
in
the
metadata
of
a
helm
chart
where
one
of
them
is
the
chart
version,
because
the
chart
can
move
independently
inversion
and
even
has
to
move
independently
depending
on
the
public
publishing
mechanism
and
there's
a
second
parameter,
which
is
the
app
version
which
would
then
basically
be
the
version
of
rook.
B
The
latest
version
this
helm
chart
is
possibly
also
then
tested
for
and
then,
if
1.5
would
come
out
at
latest,
then
the
hamilton
would
be
well
tested
against
the
latest
1.5
version
and
then
have
this
f
version
raised
in
the
chart
metadata.
A
A
Right
so
yeah
do
you
have
a?
I
guess
you
got
that
issue
there
it'd
be
good.
If
we
could
do
it,
I
think
a
design
doc
would
help
or
just
describe
hey.
What
are
we?
What
are
we
trying
to
do?
What
benefits
will
we
have?
Are
there
any
downsides
to
this,
and
I
mean
have
you
looked
also
at
how
we
might
structure
the
helm
charts
as
far
as
should
we
have
this
helm,
chart
per
cr
or
yeah?
That's.
B
That's
still
yeah,
that's
still
an
open
question
also
mayan,
because
there's
multiple
ways
depending
on
how
those
points
are
seen,
I
think
going
with
having
oh
well,
that's
the
thing
like,
depending
on
the
structure,
it
would
be
one
big
chart,
but
with
sub
charts
so
that
I
could
like
use
each
single
chart,
but
I
could
we
could
also
have
it
as
independent
charts,
which
would
then
like
require
will
have
their
own
dependencies
and
such
I
think,
yeah.
B
A
A
B
Some
topic:
I
had
the
chance
to
work
more
with
helm
the
last
few
weeks
and
months,
so
maybe
I'm
able
to
bring
the
bit
of
experience.
I
made
there
into
the
existing
operator
chart,
but
just
at
least
from
a
from
a
publishing
perspective,
I
think
it
might
that's
why
I
propose
it.
I'm
going
to
create
a
design
document
in
about
that,
but
the
proposal
basically
would
be
let's
just
kind
of
remove
the
helm
part
from
the
rook
repository
and
use
like
the
normal
helm,
publish
mechanism.
I
think
we
are
using
it
partially.
B
So
I'm
not
sure
if
it's
really
just
like
a
packaging
and
then
pushing
it
somewhere
yeah
I
have
to
see
I'm
gonna
write
up
the
design.
That
is
a
good
idea.
Yeah.
A
B
Yeah,
depending
depending
on
how
we
would
do
it
as
it's
like
from
a
just
a
helm
child
standpoint
as
it
is
their
independent
anomaly
of
the
software,
it's
more
or
less
just
a
well,
so
to
say
just
another
day
of
you
know:
you're
changing
something
in
the
chat
and
the
person
automatically
increases
the
chart
version
then,
and
then
it's
when
it,
the
pr
is
merged.
The
charge
version
is
automatically
updated
in
the
repository
and.
B
B
Yeah,
it
might
be
not
ignorable.
What
is
what.
A
Yeah
cool
yeah:
let's
continue
that
discussion
offline
and,
I
guess
does
anybody
else-
have
thoughts
on
that
before
we
move
on
to
the
next
topic.
A
Yep
sounds
good
alexander
thanks
for
the
topic,
then
moving
on
to
edge
fs
so
recently
jared
and
I
reached
out
to
dimitri
from
edgefest
and
had
a
discussion
on
what
is
the
latest
status
of
hfs.
We
haven't
seen
updates
on
github
issues
or
responses
on
slack.
A
So
for
the
recording
I'll
read
it
dear
community
updated
direct
networks.
The
owner
of
edupaths
would
like
to
inform
you.
We
do
not
plan
to
publish
further
enhancements
or
fixes
to
hfs.
However,
we
do
plan
to
announce
a
replacement
product
in
the
near
future.
That
is
intended
to
provide
much
of
the
same
functionality
of
nhfs.
Please
contact
us
if
you
are
currently
using
hfs
in
production.
I
would
like
to
discuss
options
to
migrate
to
this
new
product,
we'll
post,
further
announcements
in
the
edge
of
select
channel
at
a
later
time
yep.
A
A
So
with
with
that,
that
divest
team
has
opened
this
pr
to
mark
edge
of
has
deprecated
meaning
it
is
still
in
the
rook
builds
we'll
hold
on
to
it
a
while
longer-
and
at
some
point
I
mean
we'll-
also
remove
it
from
the
builds
we'd
like
more
information
from
ddn
on
on
the
replacement
as
well
before
we
decide
on
that,
but
that
that
is
the
status
any
questions
on
it.