►
From YouTube: Helm Developer Call 20180208
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
B
A
Do
it
Michele,
but
I've
got
it
okay.
So,
since
there's
no
other
announcements,
helm
summit
is
coming
up
here,
get
your
tickets.
Tell
your
friends,
tell
them
to
get
tickets
and
come
it's
gonna,
be
pretty
awesome,
we'll
be
working
at
the
final
and
last
little
nitty-gritty,
details
here
and
then
next
few
days
and
we'll
be
ready
to
go
and
Michele's
are
supposed
to
be
the
landing
page.
I
apologize
for
the
slightly
cut
off
schedule.
A
So
if
anyone
gets
that
gets
to
hear
in
as
I
ki
can't
read
the
schedule
for
some
reason,
there's
some
way
the
embed
works.
It
overrides
the
scrolling
tag
on
an
iframe
which
why
we're
using
iframes,
but
whatever
so
I
it
doesn't
scroll
and
so
I'm
working
on
it,
trying
to
come
up
with
an
equally
happy
way
to
fix
it.
Yes,
it
is
the
90s
enjoy.
A
A
I'm
guessing
it
isn't,
we
can
just
link
to
it
and
if,
if
I
can't
fix
the
embedding
I
might
just
switch
it
to
that,
so
people
can
go
out
to
there
she's
just
trying
to
make
it
easy
on
on
people
and
anyway,
so
I
think
is
it
for
helm
summit.
Anything
I
missed,
Michelle,
okay,
perfect,
then,
for
anyone
who
is
here
for
the
first
time,
what
we'll
do
at
after
announcements
is.
D
A
The
other
thing
we'll
need
to
follow
up
on
that
necessary
this
week
is
the
test
impressed
of,
and
maybe
it
comes
some
and
we
should
all
have
a
little
powwow
and
decide
what
we
want
to
use.
So
we
can
let
those
people
know
so
anyway,
let's
go
ahead.
I
will
start
off
the
stand
up
and
this
week
was
just
helm
summit
stuff.
For
me,
I
am
just
putting
some
finishing
touches,
bouncing
some
ideas
off
of
people
and
then
I
will
be
back
to
reviewing.
A
F
Yeah
I
think
so.
I
am
a
little
behind
on
everything.
I
really
been
away
from
my
day
job
for
two
weeks,
so
just
getting
back
into
so
many
things,
so
I
don't
have
too
much
to
report.
I've
just
been
trying
to
be
available
for
answering
questions.
If
anybody
has
needs
pairing
help
and
there's
a
lot
going
on
in
chat,
I'm
getting
distracted,
people
are
laughing
too.
F
G
D
So
you'll
end
up
in
the
case
where,
if
you
have
version
1
release
that
ok
version
2,
that's
upgraded
and
that's
okay,
you
do
a
version,
3
release
that
fails,
and
then
you
roll
back
to
version
1
or
2
version
2
or
something
like
that.
Because
of
state
changes,
then
a
version
4
will
come
out
that
will
be
deployed,
version,
2
will
be
deployed
and
version
3
will
be
superseded,
which
and
the
real
estate
should
be-
that
version.
1
and
2
should
be
superseded.
A
D
Is
failed,
4
is
deployed,
so
I
think
I've
nailed
that
down
I've
written
in
a
unit
test
to
get
that
through,
but
I
haven't
actually
followed
up
with
that
one.
But
that
was
the
majority
of
my
work
yesterday
getting
that
through
so
for
the
for
this
week
and
then
going
through
into
next
as
well,
Matt
butcher
and
I.
We
have
two
pair
at
some
point
on
our
keynote
on
day
two.
D
F
F
G
G
If
we
added
superseded
as
a
field,
instead
of
as
a
value
for
that
status
field,
we
could
even
put
it
in
label
selectors
and
make
it
easy
to
select
out
that
way
because
I
think
at
max.
If
you,
if
you
did
it,
if
you
went
the
array
route
at
max,
you
would
only
have
two
items
in
that
array
ever,
one
of
which
would
be
either
succeeded,
failed
or
any
of
those
in
you
know
like
status
ones
and
the
other
one
being
suit,
whether
or
not
it
was
super
Saiya
yeah.
F
B
G
D
E
Okay,
so
let's
see
this
week,
I
reviewed
the
auspey.
Our
Fisher
did
initial
initial
review,
but
that's
a
large
change
by
Jay
frog,
so
I
jumped
in
there
and
today
I'm
aiming
to
do
a
second
review.
There
were
some
changes,
and
so
that's
my
big
priority
for
today.
I
did
also
realize
how
much
I
missed
reviewing
home
PRS
and
working
on
home.
E
E
So
I'm
gonna
try
to
set
those
up
eventually
and
tailor
I'll
reach
out
to
you,
because
you
know
you
probably
want
to
get
going
on
that
really
feeling
lesson
so
I
think
other
than
the
home
summit
planning
things
are
coming
along
quite
well:
I'm
not
blocked
and
will
be
run
more
in
the
issue,
queue
and
here's!
That's
it
for
me,
but
sure
did
you
go
I.
G
Can
go
yeah
so
last
week
most
of
the
Microsoft
folks
were
on
an
off
site.
So
that's
why
we
were
mostly
gone
last
week
this
week,
so
I've
been
dealing
with
random
bits
and
pieces
of
helm
infrastructure
stuff
this
week,
so
I'm
trying
I
think
we
are
now
cleared
to
move
the
helm
images
out
of
the
wherever
they
are
now
the
container
repository
and
into
docker
hub.
If
we
want
to
do
that,
so
we
can
start
that
one
like
I'm,
still
working
on
the
binaries,
where
we
would
upload
the
binaries.
G
All
of
this
is
mainly
in
an
effort
to
start
gaining
first
of
all,
more
findability
for
some
of
this
stuff
and
second
of
all,
better
publicly
available
metrics
of
what's
going
on,
because
right
now,
there's
no
way
for
anyone
other
than
the
bucket
admins
to
get
any
idea
as
to
how
much
how
frequently
helm
is
being
pulled
and
things
like
that,
and
we
actually
I
don't
know.
If
people
know
this,
we
actually
get
quite
a
few
requests
to
us
individually,
an
email
saying.
A
G
Is
a
great
idea
because
most
of
the
other
stuff
I
was
looking
at
was
basically
just
buckets
and
a
frog
stuff
tracks.
Lots
of
metrics
and
I
think
we
can
mark
a
project,
public
and
Jay
frog
and
have
the
download
stats
and
things
like
that
available
as
long
as
well
as
like
the
history
of
releases
and
all
those
things
that
basically
people
want
to
be
able
to
see
and
there's
no
reason
to
to
hide
that
information
from
people
yeah.
A
C
G
I
Yeah
I've
just
been
doing
issue
triaging
I
haven't
really
done
in
a
PR
reviews.
The
thing
that's
on
my
mind
right
now,
those
late
last
night
I
was
taking
a
look
at
some
Doc's
issues
with
the
helm,
docks
that
Sh
website
and
I
couldn't
get
Hugo
to
even
load
it
with
instructions
that
we
have
on
him
www
and
also
all
the
fragments
seem
to
be
broken
or
not
all
of
them.
I
But
many
of
the
fragments
so
I
there's
an
issue
out
there
and
I
think
I
know
Fisher
you're
on
it
and
so
yeah
I,
don't
know
it
seems
totally
busted
to
me.
I
couldn't
really
build
it
to
try
to
even
start
fixing
it
last
night,
but
yeah
put
a
comment
on
that
issue,
and
maybe
me
I'm
gonna
fix
your
unit.
You'll,
probably
see
that
if
you
wanna
give
me
some
feedback,
I
think
you'd
built
it
more
than
I
have,
which
is
zero
times.
I.
D
G
I
Like
the
whatever
j/s,
it
uses
his
rewriting
the
URLs
to
have
a
slash
before
the
fragment
before
the
hash.
You
know
and
then
that's
breaking
the
or
elles
that
then
on,
so
maybe
just
a
little
a
little
fix
or
something.
But
definitely
it's
an
entry
point
for
users
and
then
they
come.
You
know
they
can't
find
something
like
our
back
or
whatever
it
is,
and
then
they
inevitably
come
and
ask
questions,
and
it
just
goes
from
there.
Yeah.
D
Actually,
we
should
push
this
to
a
larger
discussion,
because
there
actually
is
some
other
things
as
well
like
it's
I
just
looked
on
the
issue
queue
and
we
have
we're
still
on
CIA
s,
dot
IO,
which
is
our
CI
infrastructure
from
the
dais
acquisition,
and
that
is
slated
to
be
shut
down
in
March.
So
we
should
probably
get
off
that
and
not
to
circle
or
something
else.
We
got
time,
yeah.
I
Yeah,
let
me
know
if
anything
I
could
do
on
that.
Like
I
said,
I
didn't
really
fully
rocket
last
night
at
1:00
a.m.
but
but
yeah
I
just
work
on
issues,
nothing
major.
Yet
there's
one
bug
with
reuse
values
and
some
of
the
sub
chart
stuff
that
I'm
trying
to
figure
out
how
to
handle
and
it
might
have
to
move
some.
That's
a
tiller,
but
yeah.
That
is
it
for
me,
is
that
everybody.
I
C
So
what
I
do
there
was
the
gr
PC
bug
it
turns
out
when
we
upgraded
gr,
PC
versions
in
gr
PC?
They
there
used
to
be
a
a
max
data
size
or
whatever,
and
it
used
to
be
one
size
for
send
and
receive,
and
they
split
it
in
two
and
so
it
broke
the
API
changed
so
I
dealt
with
that
there
were
some
other
2
a1
bugs,
because
I
know
we
want
to
get
that
one
out
the
door
I
think
there's
just
what
bugs
left
and
then
we're
close
to
getting
it
out.
C
C
There
so
helm
has
a
chart
I
KML
file,
a
whole
lot
of
other
people
want
to
do
that
for
their
own
thing,
as
well:
kind
of
and
they're
trying
to
work
together
to
come
to
some
common
thing
and
doing
it
the
name
of
interoperability.
So
maybe
you
can
expose
it
in
dashboard
or
wherever
else
and
just
have
it
be
accessible
through
lots
of
different
tools.
C
And
so,
if
a
lot
of
other
people
are
gonna
go
work
together
on
that
and
in
many
ways
it's
just
replicating
what
the
chart
IMO
file
does
and
maybe
instances
of
a
chart
having
an
instance
we're
still
discussing
it
then,
and
do
that
as
a
CR
D.
Then
that's
probably
a
good
idea
for
home
to
be
involved
in,
and
that's
all
coming,
the
appdev
working
group.
So
I've
been
sticking.
C
C
A
C
Right
I
will
take
it
to
do
to
go
and
email
you
some
links
and
stuff.
Thank
you,
and
so
that's
what
I've
been
up
to,
oh
and
for
anybody
who
doesn't
know
the
chart,
CI
system
totally
fell
over.
We
had
I'll
call
it
a
memory
leak,
I'm
err,
quoting
here
during
my
video
on
of
a
CI,
would
crash
out
before
we
deleted
charts.
We
were
testing
and
over
time
it
slowly
built
up
until
a
rather
sizable
cluster
ran
out
of
resources.
C
We
had
things
all
the
way
back
to
September
that
had
gotten
left
behind
and
we
ran
out
of
stuff,
and
so
now
we've
got
our
memory
leak
and
things
like
that
fixed,
but
CI
systems
failing
to
purge
stuff
and
leaving
stuff
mine,
it
can
happen.
We
actually
ran
into
an
interesting
case
where
the
home
release
would
still
be
around.
It
would
still
be
listed
as
deployed
still
be
using
resources
and
somehow
the
name
space
couldn't
be
deleted
because
it
didn't
know
it
was
gone.
C
A
B
B
Pr
that's
sitting
on
me
to
just
actually
improve
the
test
on
before
we
move
forward
on
it,
and
but
there
are
two
things
on
the
side
of
that
one,
one
of
which
was
as
part
of
that
and
as
part
of
another
ticket
to
do
with
how
conditions
are
evaluated.
I
was
talking
to
Jay
Scott
and
it
looks
like
to
actually
resolve
these
properly
means
that
there's
going
to
be
quite
a
lot
of
changes
in
where
this
logic
is
evaluated
because
it
have
to
move
from
crying
into
the
back.
B
I
see
my
PR
being
very
sympathetic
to
the
import
values
way
of
doing
things.
It's
just
basically
reversing
the
logic
of
that.
So
anyone
who's
used
to
import
values
would
be
very
used
to
the
export
value
is
one
but
yeah
I'd
quite
like
to
know
when
that's
going,
and
maybe
it
makes
sense
to
raise
a
separate
issues
ticket
and
track
it
in
terms
of
what
we're
trying
to
achieve
and
how
we're
trying
to
even
try
and
collate
all
the
thoughts
together.
Does
that
make
sense,
I.
I
Sorry
I
know:
Kevin
Fox
had
gotten
on
there.
He
had
grander
ideas
to
expand
it
further
than
than
your
implementation,
and
then
we
would
kind
of
think
mad
or
sorry
Fisher,
you
jump
in
there
and
it
said
maybe
yeah.
We
can
wait
and
talk
about
it
at
the
summit.
So
I'm
not
sure
we're
gonna
move
on
it
in
two
weeks.
We're
gonna
have
a
feature
release
before
then
as
I
understand
it.
So
sorry,
sitting
on
the
vine
but
yeah.
B
I
mean
it
was
more
to
kind
of
try
and
understand
how,
where
the
thoughts
are
to
how
it's
going
to
progress,
because
as
I
say,
people
keep
on
saying
always
have
every
mask,
so
you've
got
some
of
it
in
values.
We've
got
some
of
it
in
requirements,
possibly
some
of
their
other
places,
but
I
haven't
really
seen
any
kind
of
proposals
on
how
it
might
involve
one.
I
B
Obviously,
from
one
perspective
and
originally
I
was
I
was
putting
the
PR
for
what
is
a
kind
of
working
progress
just
to
go
see
so
that
people
could
see
what
it's
trying
to
achieve.
I
could
see,
there's
a
large
implication
there,
but
be
honest.
It
was
mainly
I
wanted
people
go
yeah
yeah,
it's
worth
pursuing
before
I
actually
made
it
completely
pristine
and
ready
to
match
sure.
I
I
A
Thanks
for
bringing
that
up,
I
have
to
drop
here,
but
I
just
wanted
to
give
a
quick
report
on
the
mailing
list
thing
and
I'm
sure
Michelle
will
talk
more
I,
didn't
really
get
too
many
people
biting
when
I
sent
out
the
feelers
like
one
or
two
I'm
going
to
announce
it
at
Helm's
summit.
Is
what
I'm
thinking
and
see
if
there's
anyone
good
on
as
our
users
and
then
really
start
putting
that
together
anyway?
A
A
E
E
Well
anything
else,
we
had
some
other
discussion
items
correct
sure
you
had
something
yeah.
D
One
of
them
is
my
PR
for
reverting
the
cute
config
flag
that
was
introduced
into
eight
that
broke
existing
functionality
with
the
cute
config
environment
variable.
So
someone
has
reviewed
that
and
improved
it,
but
it's
missing
a
second
one,
so
we
could
get
someone
to
take
a
look
at
it.
That
would
be
fantastic
and
then
Matt
fariƱas
fix
that
he
was
talking
about
earlier,
where
we
upgraded
G
RPC
and
only
the
is
that
the
send
message
or
the
send
message.