►
From YouTube: Helm Developer Call 20180419
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
D
E
E
Last
week
there
was
one
PR
that
was
merged
into
master
that
had
basically
added
helm
package
that
in
values
which,
when
we
were
testing
it
out
manager
actually
pointed
this
out,
but
it
was
actually
an
incompatibility,
breaker
or
a
compatibility
breaker,
because
it
basically
stripped
all
the
documentation
so
reverted
that
PR
and
that
one
is
out
there.
It
was
never
gonna
make
it
into
2.9,
but
it
was
slated
for
2.10,
so
that
issue
was
reopened
and
whatnot
other
than
that.
E
It's
been
triaging
issues
and
trying
to
make
or
trying
to
pare
down
any
of
the
bugs
that
are
available
in
2.9
rc3
and
I
think,
we're
down
to
one
last
buck
and
I
didn't
open
to
file
an
issue
for
that
and
I
have
manually
tested
it.
So
if
anyone
can
take
a
look
at,
it
is
literally
a
one-line
fix.
After
that,
we
should
be
able
to
do
in
our
c4.
I
can
post
the
link
to
the
issue
after
this,
so
pass
it
off
to
Nikhil.
D
So
the
only
thing
I've
been
doing
mostly
other
kubernetes
things
and
I
haven't
really
touched
much
of
any
thing
with
home
outside
of
governance.
The
one
thing
that
I
could
have
brought
up
under
announcements
probably
is.
If
anybody
knows
the
dashboard
is
looking
for
contributors
and
even
more
cores.
So
if
anybody
knows
anybody
who
does
you
eyes
and
wants
to
go
work
on
the
dashboard
project,
it's
got
a
really
low
barrier
to
entry
to
get
started
come.
D
D
B
D
See
I,
don't
know,
that's
four,
that's
four
sig
UI,
but
if
anybody's
interested
come
chase
me
down
and
I'll
be
happy
to
help
point
you
in
the
right
direction
or
if
you
know
people
feel
free
to
send
them
to
me
and
I'll,
send
you
in
the
right
direction.
So
with
that
I
will
see
butcher
you're
already
talking
a
passive.
G
Helm
to
stuff
been
doing
helping
out
here
and
there,
with
with
reviewing
PRS
and
trying
to
test
out
things
helm.
Three
stuff
I
have
one
PR
open
on
the
helm,
spec
for
hum
3.
That
is
about
trying
to
incur
some
stricter
security
guidelines
for
signing
things,
and
so
that's
been
going
on
for
a
little
while
now,
I
have
one
I'm
about
to
open
about
some
changes
to
where
releases
are
stored
to
kind
of
formalize
that
so
we
would
store
releases
in
the
namespace
for
the
release
instead
of
storing
them
all
in
the
same
namespace.
G
A
Yeah
so
I've
been
heads
down
all
week
on
down,
so
I
got
a
few
patches
in
for
the
RCS
other
than
that
I've
been
working
on
some
of
the
helm,
3
stuff,
primarily.
A
B
I
Home
yet,
but
here
to
get
too
many
guys,
I
work,
the
Red
Hat
I'm
on
a
particular
part
of
openshift.
That's
a
service
broker
behind
Service
Catalog.
We're
can
all
all
different
kinds
of
ways
that
you
could
potentially
use
home
and
make
sure
that
technology
is
matching
up
well,
very
interesting,
home
3,
so
I'm
here
to
kind
of
learn,
especially
what
that
Direction
is
what's
going
on
and
hopefully
get
involved
in
that
effort
at
some
point
feature.
A
C
A
A
A
A
G
We
removed
all
of
tiller
all
the
middleware
between
the
client
and
the
server
is
just
gone
and
then
along
the
way,
I'm
just
off
to
make
it
streamlines.
So
it's
like
if
it's
a
patch
that
changes
the
the
help
text
documentation
on
a
flag,
there's
a
good
chance.
We
could
tear
you
pick
that,
but
if
it's
anything
anywhere
else.
A
G
D
H
D
D
All
right,
so
my
terrible
most
painful
view
in
the
world
is
we
should
helm.
We
should
probably
keep
features
man
so
ideally
I'd
like
to
say
some
features
that
can
be
added
to
helm
and
home
3
cleanly
that
don't
break
helm,
I'd
like
to
see
going
for
a
little
while
I
would
see.
Maybe
we
want
to
give
people
time.
There
are
a
lot
of
people
using
helm.
D
Right
but
I'm
just
saying:
there's
lots
of
people
who
continue
to
use
helm
and
will
update
home
too
for
a
while,
so
they
trust
home
3a
lots
of
companies
will
say
you've
got
to
keep
something
around
for
at
least
six
months.
So
I
would
like
to
see
helm
three
out.
I
mean
what
we'll
do
patches
for
a
long
time
on
it
right
by
the
I'm,
probably
gonna,
be
in
the
longer
side
of
things
than
on
the
shorter
side.
Yeah.
A
G
A
C
E
And
we
just
same
way
over
I'm,
almost
of
the
opinion
that
say
like
so:
we've
got
2.9
that's
currently
coming
out
and
we've
got
and
we've
made
promises
to
people
that
features
that
are
not
in
2.9,
we'll
make
it
into
210.
I
know
that
we're
basically
at
the
point
where
any
new
features
that
are
coming
like
any
new
features
that
are
committed
to
the
master
branch
right
now
probably
will
be
a
very
difficult
process
to
get
that
into
the
helm,
3
branch.
E
E
We
can
continue
to
do
for
helm
to
potentially
patch
over
to
helm
three
if
it
makes
sense,
but
after
210,
perhaps
that's
when
the
best
point
is
to
say
that
okay,
we're
only
taking
fixes
from
now
on
for
helm,
and
if
you
want
features,
then
they
should
probably
be
putting
it
into
hell.
Three
or
ricans
for
helm,
three:
okay,
sorry.
A
D
Was
just
gonna
say
the
maybe
flip
it
on
to
the
contributor
side
of
things
and
say
you
have
to
get
your
feature
addition
hole
request
in
by
this
date
for
it
to
be
considered
in
helm
two
or
it
can
needs
to
be
against
hell
three
like
give
them
the
cutoff
date,
because
you
know
we've
had
trouble
getting
it
into
a
version
and
we
bump
it
another
release
as
we
work
through
that.
Maybe
the
important
thing
is
to
say
for
them:
here's
the
date
right.
D
D
C
See
so
I
mean
like
why
don't
we
just
have
a
cut
like
after
10
you're
after
it
or
they're?
After
this
release,
we
can
just
say
that
all
the
new
features
that
get
added
to
home
just
there's
no
guarantee
that
that's
gonna,
be
the
functionality
in
home
3.
Would
that
make
sense
instead
of
dropping
development
on
home.
E
B
I
A
A
Know
that
if,
if
an
end-user
is
has
no
awareness
of
art
development
discussions
that
are
going
on
with
the
difference
between
home
to
in-home
three,
this
is
just
somebody
who's,
a
basic
user.
Then
they
download
the
latest
help
to
then
they
are
using
these
new
features
and
then
become
three
and
something
drastically
changes,
or
that
isn't
an
obvious
like.
Oh,
this
is
a
helm
three
feature.
A
F
I
A
Not
an
issue
because
it's
a
major
version
bump
and
you
can
expect
breaks,
but
that's
what
my
concern
more
is
it's
not
so
much
the
contributors
and
you
know
making
sure
that
they're
happy
about
their
features.
I
mean
it's
kind
of
obvious
that
we're
moving
to
we're
doing
a
major
version
bump.
It's
it's
brand
new
mitts
gonna
have
a
different
feature
set
like
you're.
Probably
gonna
have
to
read
patching
yourself.
D
We
can
be
fluid
in
this
right.
We
can
say
you
know
once
the
I
don't
know
say
June
first,
whatever
day
we
pick,
we
can
say
after
this
day,
if
you
are
contributor-
and
you
want
to
contribute
a
feature,
you
have
to
contribute
up
both
to
helm
to
and
helm
three
and
then
after
this
date
we're
not
going
to
accept
any
more
features
to
help
to,
and
we
tell
people
that
so
that
way
we
have
that
continuity,
and
we
let
people
know
what
they
have
to
do.
E
Then,
if
people
are
missing
functionality,
then
they
can
just
PR
that
feature
over
to
helm.
Three,
if
it
makes
sense,
I
would
make
sense
from
a
development
model
in
the
sense
that
if
someone
developed
something
brand-new
for
helm,
210
doesn't
make
it
a
helm
3
they
want
that
feature.
Then
the
onus
would
be
on
the
user
or
on
the
contributor
to
contribute
that
to
helm
3.
It
would
necessarily
be
on
us
to
patch
that
forward.
Yeah.
D
C
D
Who's,
a
user
who
doesn't
contribute
because
most
of
our
users
don't
contribute
they're,
gonna
go
and
they're
gonna
start
saying:
I'm
gonna
switch
to
helm
3.
Oh
that
feature
that
was
in
home
too.
Isn't
there
then
they're
gonna
come
back
and
blame
us
the
people
who
maintain
it
for
not
porting
that
feature
over,
even
though
you
know
that,
but
that's
you
know.
A
G
D
C
Freeze
date,
now
that
we've
had
this
discussion,
I
just
want
to
say
like
when
we
do
have
the
alpha
release.
We
can
make
it
a
point
to
like
make
a
big
push
to
the
people.
Who've
contributed
features
be
like
hey,
like
just
make
sure
that
your
functionality
exists.
This
is
kind
of
the
time
to
fill
in
any
gaps.
G
F
To
me
that
the
idea
of
having
sort
of
the
freeze
window
sort
of
makes
sense,
especially
if
we
wanted
focus,
sir
users,
if
we
want
to
focus
users
to
upgrade
to
v3,
then
making
sure
that
any
new
features
that
come
in
going
to
be
three
would
give
them
sort
of
a
carrot
to
upgrade
as
well
right.
So
it
would
be
sort
of
positive
reinforcement,
channeling
them
to
the
right
direction.
Yeah.
E
And
I
think
that
I
think
we
can't
really
make
a
cutoff
window
for
helm
to
development
until
we're
ready
on
the
helm
three
development
to
start
accepting
PRS
yeah.
Do
we
have
a
Adam?
Do
you
know
like
no
commitment
to
timelines
or
anything
like
that?
But
do
you
know
if,
like
things
would
start
slowing
down
and
say
three
four
weeks
or
five
six
weeks
to
start
accepting
contributions
on
the
helm,
three
development
branch
or
don't
rush
me
bro.
A
D
Yeah
Brina
can
I
just
if
we
don't
know
when
we'd
want
to
do
the
date.
Maybe
the
thing
we
do
is
every
one
of
these
meetings.
We
come
back
and
say:
do
we?
Are
we
ready
to
talk
about
a
date
yet
and
if
the
answer
is
no,
we
bump
it
to
the
next
meeting.
If
the
answer
is,
we
think
so,
then
we'll
have
the
date
conversation
and
in
the
meantime,
we
can
track
stuff
with
with
labels,
as
Butcher
pointed
out.
A
D
Propose
to
that,
yes,
we
open
a
new
branch
and
the
proposal
would
be.
We
tell
people
that
work
only
making
a
major
architectural
change
and
so
we're
asking
people
to
hold
off
on
their
pull
requests
until
that
major
change
is
done
to
remove
tiller
and
if
they
want
to
dig
into
why?
If
somebody
actually
is
curious,
why
then
we'll
answer
that
question?
Otherwise
they
just
know
we're
removing
tiller
and
it's
a
big
architectural
change,
and
so
most
people
would
be
okay
waiting
going.
Oh
my
god,
I!
Don't
touch
that.
How.
F
B
C
D
You
whoever's
the
Sherpas.
If
they
see
it
could
also
just
say,
hey
right
now,
we're
not
doing
it.
If
somebody
does
submit
one
mm-hmm,
some
people
just
aren't
gonna
read
the
docs
anyway,
and
so
if
the
Sherpa
comes
across
one,
they
could
say
you
know
here's
the
current
status
of
it.
Here's
what's
going
on
we'll,
let
you
know
when
we're
ready
for
that
and
odds.
Are
your
PR
isn't
gonna
work
in
the
future
anyway,
because
the
major
changes,
but
we
can
politely,
say
something:
yeah.
G
B
I'll
be
here
Oh
Matt
Farina.
Was
there
any
update
on
the
ammo
stuff.