►
From YouTube: Helm Developer Call 20180201
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
A
Right
then
I
guess
we'll
go
around
with
stand-up
Nikhil.
Do
you
wanna
go
first
sure,
oh
by
the
way
for
anybody,
who's,
new
or
listening?
The
way
we
quickly
do
this
is
for
stand-up
we
go
around
to
the
core
maintainer
and
they
do
a
quick
stand-up
and
then
we'll
get
into
discussion.
Go
ahead
and
kill.
That's.
B
Good
thanks
thanks
man,
so
last
week
did
a
little
bit
of
issue
triage
and
a
couple
of
PRS
in
addition
to
that,
had
some
good
conversations
with
folks
in
Susa
a
tail
end
of
my
trip
to
Nuremberg,
and
there
were
there's
a
lot
of
interest
in
actually
coordinating
stuff
to
kubernetes
and
using
home
to
do
that.
So
that
was
good
in
addition
to
that
God
started.
B
A
A
It
turns
out,
there's
some
odd
testing
scenarios
which
I'll
be
talking
about
in
my
talk
at
the
helm
summit
on
testing
some
of
this
stuff,
where
things
look
like,
they
were
ready,
but
they
really
weren't
yet,
which
was
causing
our
CI
system
to
fail.
There's
some
little
things
like
that.
Reinhard
actually
was
the
one
who
ended
up
fixing
it.
We
got
that
merged
in
today,
but
poking
at
some
of
those
CI
things.
This
week
and
that's
been
most
of
my
week
on
this-
let's
see
us
do
we
have.
B
C
Just
done
you
know,
issue
mostly
issue:
follow-up
I
am
looking
into
the
reused
values.
Bug
I
just
came
to
their
conclusion
last
night,
but
it's
around
the
tags
of
conditions
thing
that
I
implemented,
so
I'm
gonna
try
to
see
if
anything
can
be
done.
Essentially,
I,
never
use,
reuse
values
and
in
manual
testing
back
in
the
day
when
I
wrote
that
did
not
test
it
so
yeah,
that's
gonna,
probably
get
other
than
just
following
up
and
generally
trying
to
help
people
that
are,
you
know
having
their
one-off
issues,
I'm
gonna
dig
into
that
one.
C
It
was
actually
got
reliable
to
bug
last
night
by
me
after
revisiting
the
issue,
because
people
started
complaining
about
it.
Think
that's
it
I'm
in
my
sights
right
now
anybody
else
here.
We
should
throw
this
to
you.
How
was
it
okay
and
I'm
very
excited
about
the
helm
summit?
Do
you
do
we
know
as
cores
do
we
have
to
register
pay
and
everything
I
don't
know
if
we
do
I
plan
on
doing.
A
B
A
Right,
I
guess
the
first
one
that
I'll
jump
on
is
we
just
discussed
it
in
sega
architecture,
which
is
why
I
haven't
thrown
it
in
here
and
it
came
out
of
control
box.
I
did
file
an
issue
on
it,
but
kubernetes
is
going
to
attempt
to
shift
away
from
the
use
of
the
term
master.
We've
been
using
that
to
describe
our
control
plane
and
things
like
that,
but
it
is
not
exactly
a
sensitive
term
to
use
these
days.
You'll
see
other
tools
like
we're.
A
Looking
at
Drupal
went
with
primary
and
replica
there's
a
number
of
projects
that
are
shifting
away
from
that,
and
it
is
finally
come
up
in
kubernetes
people
have
started
to
speak
up
on
it
in
some
forms.
I
don't
know
who
those
who
they
are
I
just
know
it
came
through
contributes,
and
so
we
discussed
it.
Sega
architecture
and
we're
gonna
propose
that
you
use
a
better
term
such
as
api
server.
But
if
there's
not
some
better
term
today
and
most
likely,
you
can
switch
to
using
control
plane.
A
A
B
A
B
A
Or
something
like
that
might
be
a
better
term
that
we
can
use.
That
would
be
specific
to
us,
but
those
are
the
kinds
of
things
that
they
would
like
to
have
done
is
to
remove
words
like
that
and
just
change
the
language
we're
being
sensitive.
We
joked
that
it
was
funny
that
we're
in
a
meeting
with
all,
but
one
person
was
a
white
male
discussing
this
issue
because
it's
come
up
and
that
just
happens
to
be
how
kubernetes
is
and
part
of
the
reason
the
terminology
came
this
way
anyway.
A
So,
let's
see
other
thing,
has
anybody
else
looked
at
that
2.8
bug,
I.
B
A
D
A
Okay:
okay,
there
was
a
question
also
you
might
be
able
to
answer
here
to
he'll.
Maintain
errs,
need
to
reserve
a
get
a
seat
just
like
everybody
else.
Get
tickets
for
the
home
summit,
I.
D
D
And
I
don't
know
so
anyone
I
am
figuring
that
out.
I
will
let
you
know,
I.
Think
the
the
plan,
though
that
I
last
heard,
was
that
we
want
people
to
unless
you're
speaking
or
or
anything
like
that,
then
you'll
be
doing
then
you'll
need
to
buy
a
ticket,
but
the
large
majority
of
us
are
speaking
or
doing
something
that
would
have
that
so
I'm
gonna
say
that
for
now
and
I'll
change
my
mind
and
add
in
the
dev
channel.
If
I
hear
anything
different,
okay.
A
Thank
you
then
yeah.
We
were
talking
about
the
otherwise
the
gnarly
issue,
which
is
issue
33,
82
I'll
drop
it
in
chat.
This
is
the
the
rather
gnarly
one,
which
is
errors
and
deployments,
and
actually,
looking
at
this,
we've
gotten
to
a
few
of
the
details
and
poked
API
machinery
and
they
came
and
gave
a
couple
of
two
cents
on
it
and
it
has
to
do
with
metadata
and
that's
where
I
stopped
and
it
was
in
how
we're
doing
patches
and
then
metadata
and
validation
of
that
and
some
of
that
code
actually
changed.
A
An
API
machinery
which
were
leveraging
through
client
go
I,
think
so
the
code
there
changed
and
now
we're
experiencing
upgrades,
which
it's
an
upgrade
issue,
because
it's
a
patching
of
an
object
and
then
validating
the
metadata
is
what
it
looks
like,
and
so
folks
could
go.
Take
a
look
at
this.
Even
if
you
find
the
next
step
on
and
what's
going
on,
it
would
be
appreciated
because
this
we
probably
need
to
get
rolled
out
and
soon
because
there
are
a
number
of
people
who've
rolled
back
from
2.8
to
2.7,
because
they've
experienced
this
issue.
B
B
A
D
D
A
Because
this
one
here,
I
think's
a
big
enough
deal,
it
might
be
good
to
get
this
one
fixed.
There's
a
number
of
little
bugs
I
mean
we've
got
now
that
you
say
that
one
we
probably
got
three
or
four
bugs
together
that
I'll
go
into
the
two
eight
one
release,
but
this
one's
kind
of
been
an
early
hairy
one.
B
D
A
Think
one
of
the
good
folks
to
get
is
on
the
issue
he's
st
TTS
and
you
could
get
him
he's
over
at
Red,
Hat
and
I
mean
he's
been
all
over
the
API
machinery.
Stuffin
knows
this,
so
he
might
be
a
good
person
to
look
at
he's
already
commented
here.
So
he's
looked
at
the
issue.
A
little
bit.
I'll
have
some
cycles,
probably
tomorrow
that
I
can
dedicate
to
this
I.
Don't
think
I
have
enough
the
rest
of
the
day,
but
tomorrow
I
think
I
can
jump
on
and
help
with
us
as
well.
D
I
actually
know
it
fairly
well,
like
most
of
my
contributions
to
Elm
directly
have
been
all
through
the
kubernetes
and
release
clients
stuff.
So
the
coop
and
the
release
server
package,
so
I
know
it
fairly
well.
I
just
haven't
touched
a
lot
of
the
patching
parts
of
it
so
I,
but
I've
touched
it
enough
to
kind
of
look
around
and
see
what
they've
been
doing
with
it.
So
I'm
gonna.
That's
why
I
want
to
try
to
jump
in
and
see
what.