►
From YouTube: Helm Developer Call 20180308
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
B
C
B
D
Hey
guys
for
me,
I've
been
looking
at
a
couple
of
issues
and
answering
those
things
that
I
had
commented
on
earlier.
In
addition
to
that
also
was
doing
some
investigation
on
how
to
and
scopes
work
so
that
can
propose
something
concrete
for
the
scope
schema
for
museums,
always
working
with
Josh
on
that
and
also
I've
been
looking
at
a
couple
of
key
ours,
but
we'll
keep
doing
that
this
week.
So
that's
me
and
with
that
I
will
pass
it
on
to
Michelle.
E
E
E
E
Only
other
thing
is:
you
have
some
confusion
with
the
mailing
list.
There's
people
who
are
not
maintained
or
training
experience
keys
like
public,
so
we
should
probably
just
revisit
like
you
know,
who
should
join,
which
mailing
list
document
somewhere
and
if
the
charts
maintainer
is
want
their
own
mailing
lists.
We
should
probably
somebody
on
the
CMC
outside
also
several
other
mat
admins
to
the
mailing
list
so
line.
If
I
get
hit
by
a
bus,
then.
F
Sorry
I
was
just
posting
a
little
thing
in
the
comments,
so
yes
or
I
guess.
Last
week,
I
have
been
working
hard
on
just
reviewing
pr's
moving
forward
on
some
discussions
on
the
upgrade
fix
or
the
upgrade
bug
and
the
Helmand.
It's
wait
after
it's
been
mostly
just
kind
of
looking
at
the
proposals
and
saying
like
okay,
this
is
good
and
that,
but
we
haven't
actually
done
an
in-depth
kind
of
like
review
and
after
discussions
with
Brian
and
Adam,
and
a
few
other
maintain
errs
on
what
are
some
good
approaches
for
those.
F
We
came
up
with
a
couple
of
different
solutions
that
actually
turned
out
to
be
a
lot
cleaner,
at
least
for
like
Helmand.
It
wait
like
plugging
into
the
G
RPC
health
service,
which
is
built
into
G
RPC,
which
I
never
knew
about,
which
is
kind
of
cool,
so
I
was
spending
last
week
working
on
one
feature
for
that
which
was
the
Helmand
is
wait
plugging
into
the
G
RPC
stuff,
and
then
otherwise.
It's
been
mostly
reviews
so
this
week.
F
What
I
plan
to
do
is
that
I
think
Adam
and
I
shortly
after
this,
we
want
to
pair
together
and
take
a
look
at
some
of
the
PRS
and
just
have
some
discussion
on
those
other
than
that
steady
as
she
goes
yeah,
let's
go
with
Farina.
G
So
I
have
been
working
on
gathering
some
of
the
documentation
from
the
helm
summit
and
getting
that
stuff
together.
So,
for
example,
we
got
the
user
profiles
documented
and
that's
merged
into
the
home
community
repo
and
right
now
there
is
a
hack
MD
that
has
a
whole
bunch
of
the
user
stories
that
have
been
pulled
out
of
the
sessions
from
the
unconference
and
I'm
working
on
a
pull
request
to
also
bring
that
into
the
community
repo.
So
we
can
iterate
on
things
there,
but
kind
of
gather
this.
What
has
been
going
on?
G
A
C
C
Think
what
the
biggest
thing
we
gained
out
of
it
was
able
to
take
the
temperature
of
the
community
to
find
out
what
was
really
important
and
what
was
not
more
so
than
actually
get
requirements
from
the
summit,
so
we're
trying
to
collect
all
of
that
and
kind
of
make
it
cohesive
and
all
in
one
proposal
something
for
us
to
work
off
of
so
come
back
next
week.
If
you
want
to
check
that
out,
you
start
the
discussion
on
that.
C
We
just
want
to
make
sure
it's
closed
enough,
that
we
can
have
some
good
discussion
around
it.
So
it's
not
too
loose
and
kind
of
I
was
at
the
summit,
where
it's
just
tell
us
what
you
want.
We
want
something
concrete
that
we
can
actually
say
yes
or
no,
maybe
change
this
change
that
so
hopefully
what
will
be
at
that
point,
and
what's
here
it
goes.
C
I,
don't
want
me
to
clear
that
you
know
like
there
are
certain
things
that
the
community
is
not
ready
for
round
three
and
want
to
push
back
on
certain
things.
You
know
too
much.
Change
could
be
a
bad
thing
and
I
just
want
to
make
sure
that,
like
we
should
take
that
into
consideration
also
where
we
want
to
cause
too
much
destruction,
helmets
really
kicking
off
right
now,
I'm
not
trying
to
discourage
anybody,
but
just
I
wants
to
keep
that
in
mind
of
you
know.
C
Are
we
doing
this
for
the
next
latest
and
greatest
thing,
or
is
this
something?
That's
really
gonna
benefit
the
community?
So
I
just
want
supposed
to
keep
that
in
mind
as
well,
when
we
look
at
it
next
week,
other
than
that
I'll
be
reviewing
a
couple
outstanding
hockey
ARS
with
Fisher.
If
anybody
else
wants
to
join
in
on
some
fun,
let
me
know
we're
just
gonna
pair
and
try
to
get
through
doing
a
proto.
C
H
Semmy
course
I
want
to
be
presumptuous,
I've
been
pairing
with
Fischer
on
the
helm,
white
stuff
and
implementing
a
basically
the
ping
using
the
proto
health
check
specification
other
than
that
that's
about.
As
far
as
my
contributions
to
help
my
then
last
week
same
way
knock
on
a
hot
potato,
but
back
to
Taylor.
I
do.
F
Have
one
last
thing
to
tack
on
on
my
stand
up,
which
is
Ronin
and
I
are
also
working
on
the
helm,
donna
se-jin
docks,
LSH
site
or
the
repository
that
is
building
that
infrastructure.
It's
on
older
Deus
infrastructure
like
CIJ
sto,
and
it's
being
deployed
that
way
and
I.
Think
it's
like
on
an
old
days
cluster
somewhere
from
our
migration
over
from
Microsoft,
so
somewhere
out,
there
based
workflow
is
still
running
but
other
than
that.
We're
just
trying
to
move
it
over
I.
Think
as
your
resources
and
it's.
B
B
Okay
looks
like
we
will
move
on
to
the
points
of
discussion.
So
first
thing
we
have
up
in
our
notes
is
a
templating
in
the
okay.
Actually,
we
have
like
four
different
discussion
points.
So,
let's
make
the
assignments
now,
so
we
don't
have
to
make
them
at
the
very
end.
I
can
volunteer
to
be
issue
Sherpa
for
this
week.
E
B
C
B
E
B
G
G
And
you
actually
you'll
see
it
in
the
image.
If
you
go
there,
it
gives
an
example
of
how
you'd
want
to
use
it,
and
here
it's
being
used
in
the
pod,
anteye
affinity
configuration
where
the
release
name
is
passed
in
and
then
then
that
is
to
you
and
they
do
some
interesting
things
with
the
TPL
to
get
it
here.
But
there's
questions
around:
how
do
we
is
there
a
way
we
can
go
about
doing
something
like
that.
Oh.
C
G
I
J
F
With
a
one,
the
one
argument
that
has
been
made
or
the
one
use
case
that
I've
seen
solidly
in
that
issue,
was
the
ability
to
pass
the
name
of
a
parent
chart
to
child
charts.
I've
seen
that
pattern
in
that
issue
queue
or
in
that
specific
issue
several
times
so
I
wonder
if
we
solved
that
case
somehow
and
I
know
that
in
the
proposal,
dr.
helm,
3
I
think
was
it
but
sure
had
an
idea
that
might
solve
that
use
case,
but
I'm
not
sure
yet,
but
that
is
the
one
primary
driver
for
this.
F
A
B
What
were
you
saying,
Taylor,
sorry,
if
I'm
interrupting
I
think
my
video
feeds
Bing
lagged,
but
the
I
was
I
like
what
you
were
saying,
Fisher
about
doing,
like
maybe
addressing
that
one
use
case
passing
through
the
the
parent
chart,
name
or
other
chart
names,
because
that
definitely
is
useful.
I've
run
into
that
several
times.
But
maybe
what
we
can
do
is
implement
this
as
a
as
a
plugin
as
an
alpha
feature
and
then
like
with
actual
templating
of
the
values
file
and
see
like
how
nasty
it
becomes
or
how
many
people
use
it.
B
It's
just
kind
of
just
a
possibility
of
trying
this
out
before
actually
pulling
it
into
core.
If
we
see
a
lot
of
people
using
it
even
from
a
programmatic
standpoint,
it's
kind
of
a
little
gnarly,
but
if
a
lot
of
people
use
it
and
find
value
out
of
it,
unintended
I
will
I
would
say
we
could
move
forward
with
that,
because
that's
something
that
obviously
we
see
the
community
wants,
and
so
maybe
that's
the
way
we
do
it.
B
Maybe
we
do
try
to
implement
the
whole
passing
through
template
and
I'm
sorry
chart
names
down
to
children,
which
would
make
sense
and
then
the
other
stuff
of
template,
izing
of
value
values
could
be
a
plugin
for
now,
especially
if
someone
has
a
reference
implementation
already,
that
they
kind
of
want
to
just
put
a
little
polish
on
and
then
see.
If
we
can
go
from
there
and
we
can
say,
hey
here's
the
thing
somebody
implemented.
What
do
you
guys
think
yeah.
F
So
I
I
see
there
are
two
things
that
is
our
two
core
problems.
That
is
one
is
that
there
are
no
good
go
standard,
lives
or
llamó
parsers
that
don't
allow
the
anchoring,
but
you
can
solve
that
use
hit,
but
at
the
same
time
it's
the
same
pattern
that
we
see
with
like
helm,
template
and
coop
CTL
apply
and
where
we're
rendering
values
client-side
and
then
applying
it
to
things,
whereas
in
this
case
people
want
to
render
value
files
before
submitting
it
to
helm.
So
I
can
see
some
parallels
there
too.
C
Allow
its
templating
of
the
values
file,
so
we
can
still
get
that
information
in
there
in
a
more
structured
way.
That's
why
I
was
asking
originally
like.
What's
the
use
case,
because
if
it's
just
a
matter
of
there
is
a
common
data
set
that
people
are
looking
for
to
have
available
when
they're
rendering
their
templates?
C
Like
there's
a
lot
we
to
do
there
without
going
down
the
route
of
like
fully
templating
their
value,
saying
because
okay,
we're
gonna
enable
people
to
get
into
trouble
if
we
start
doing
that,
where
they're
gonna
end
up
with
spaghetti
that
it's
gonna
be
so
hard
to
debug
their
way
out
of
certain
values,
especially
with
trying
to
have
reproducible
builds,
which
was
what
Fisher
was
alluding
to
I.
Think
before
where
some
of
the
template
hanging
happens,
client
so
I
had
some
of
the
templating
happens,
server-side
to
be
able
to
trace
that
back
to.
C
B
C
G
I'll
reach
out
to
Reiner,
who
originally
brought
this
up
the
more
I'm
starting
to
look
at
some
of
these
again
and
revisit
it.
It
looks
like
release
name
and
it
looks
like
written
lease
name
as
like
I'm
gonna,
yeah
mall,
some
section
of
my
values,
file,
which
kind
of
was
where
things
get
interesting,
because
if
you're
just
doing
that,
you
could
move
these
sections
into
your
templates
and
then
just
have
that
and
release
name
will
work
that
right
and
so
I'm
curious.
G
That's
meet
you
alright,
so
tiller
on
transport,
air.
There
are
cases
and
you'll
see
them
on
some
of
the
weight
issues
that
are
currently
open
where
the
connection
to
tiller
gets
broken.
We're
experiencing
this
over
on
the
chart,
see
I,
wear
a
chart
might
be
currently
running,
helm
test
and
then
transport,
the
tiller
gets
broken
and
the
chart
fails.
G
C
G
Okay,
we'll
have
to
take
a
look
at.
It
might
already
have
the
service
going,
but
this
is
kind
of
a
newer
thing.
We've
only
recently
started
to
experience
and
I
thought
GRP
see
that
automatic
reconnect
in
it
and
so
I'm
wondering
if
there's
something
detailed
inside
of
there
to
go
dig
into
I,
because
we
just
upgraded
GA
RPC
to
write
a
new
version.
The
library
I
also
wonder
if
there's
something
going
on
there.
What's.
B
F
F
H
C
Possible
there's
two
possible
points
of
failure.
One
is
the
tunnel
keeping
that
open
because
there's
a
open
tunnel
and
then
a
closed
tunnel
at
the
end
of
every
helm,
action
and
then
there's
the
Jaro
PC
events
that
happen
in
between.
So
it
could
be
that
the
tunnel
is
having
issues
or
the
GRP
C.
So
that
would
be
the
thing
good.
C
C
G
B
B
C
B
I
G
G
B
Stay
perfect
and
that
I
did
that.
One
looks
like
something
we'll
probably
end
discussing
next
week
so
next
week
and
when
we
leave
the
meeting
I'm
assuming
we're,
because
our
unique
presenting
at
helm
three
thing
we'll
probably
have
no
other
discussion
topics,
except
that
we'll
try
to
keep
stand-up
pretty
short
and
so
that
we
have
as
much
time
as
we
can
to
discuss
the
the
helm.
Three
proposal
to
Adam
and
butcher
will
be
bringing
and
I.
I
B
I
G
Like
some
of
the
suggestions
in
there
do
things
that
won't
work
if
you're
using
a
static
or
object,
storage
and
now
stuff
doesn't
work
anymore
with
possible
changes
here,
so
go
take
a
look
at
it
and
some
functionality
would
change
like
helm.
Search
may
end
up
changing,
so
you
can't
search
all
of
your
repositories
at
once.
You
have
to
search
one
at
a
time
and
individually
choose
it.
So
really
go.
Take
a
look
at
the
issue.
I'd.
B
H
I
I
C
G
Awesome,
the
fetching
is,
but
not
the
authentication
so
for
something
like
chart.
Museum
you'd
need
use
like
cm
colon,
slash,
slash
and
then
it
would
drop
into
a
chart
museum
plugin
to
do
something.
If
you
look
at
the
s3
plug-in,
you
can
look
at
how
they
did
it
for
the
same
kind
of
thing
and
then
you
can
support
whatever
authentication
mechanism.
You
want
well.
I
G
I
mean
there's
a
way
how
you
today
does
it
is
you
have
HTTP
and
HTTPS
for
the
schemes
in
your
URL
and
those
map
to
what
you
know
with
basic
authentication
if
you
want
to
do
transport
outside
of
that
or
other
authentication
mechanisms
outside
of
that,
you
change
the
scheme
so
like.
If
you
have
the
s3
plug-in
s3
colon
slash,
slash,
will
connect
to
an
s3
repository
and
then
it
will
use
s3
authentication
mechanism.