►
From YouTube: Charts Chat 20171212
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
Yeah
in
dentist,
so
you
know
Matt
pointed
out
that
these
tests
have
been
failing,
so
they
got
added
by
Fox
in
like
the
one
six
one
seven
release
I
think
and
then
had
been
broken
for
a
little
bit
or
a
long
bit
so
I
started
to
look
at
those
again.
We
had
an
issue
with
one
chart.
Failing
to
install
due
to
time
out
was
the
spinnaker
chart
that
downloads,
a
bunch
of
images
and
so
I
removed
that
one
temporarily
and
found
other
issues
like
leaking
resources
from
PVCs
which
we're
making
the
test
to
fail?
B
A
A
So
Aaron
who's,
the
co-lead
of
sake,
testing,
I,
work
with
him
and
so
he's
the
one
who
came
to
me
to
point
this
out
and
he's
been
bugging
me
for
weeks
and
weeks
on
it
and
so
I
finally
decided
to
file
the
issue.
So
at
least
it's
recorded
somewhere
rather
than
him
just
telling
me,
and
so
one
of
the
things
we're
talking
about
is
if
tests
like
this
are
failing
all
the
time,
then
they're
not
useful
to
the
project
and
they're
costing
us
money
and
our
bill
is
not
small.
A
When
you
look
at
how
much
compute
we
use
and
resource
time
so
they're
saying,
if
it's
not
doing
anything,
we
should
either
fix
it
or
remove
it,
and
so
I
find
that's.
Why
I
finally
filed
that
issue
and
where
it
comes
from
so
I'm
happy
to
and
if
we
get
this
working
it'll
making
him
happy
so
I
can
justify
helping
you
with
that
as
much
as
you
need
off.
B
A
D
B
I
think,
actually,
that
that's
I'm
I
think
that's
what
I
was
gonna
do
basically
everything
until
we
have
some
cream
and
then
I
think
back
in
decrement
ELISA.
That's
the
easiest
path
to
green
I.
Think
at
this
point
yeah
so
I
was
gonna.
Go
for
that,
basically,
that
the
Cowardly
way
out
and
then
come
back
through
with
a
date.
Justice,
blue
yeah.
D
B
B
Been
occur,
chart
to
place
I
think
it's
nine
nine
different
deployments
each
with
their
own
image
and
every
test
is
running
on
a
fresh
cluster,
so
no
images
cached,
whereas
in
like
the
PR
testing,
we
run
on
a
warm
cluster.
So
with
that
we've
extended
the
time
out
in
in
the
PR
tests
and
also
most
of
the
time
at
least
some
of
those
images
are
cached,
so
it
takes
not
quite
as
long
so
it's
just
it's
a
matter
of
extending
the
time,
outs
and
stuff
like
that.
But
again,
I
think
that's
why
we
just
rebuilt.
A
It-
and
that's
that's
great-
that's
that's
really
great
so
you've
extended
to
time
out,
we've
removed
a
test
that
just
takes
a
really
long
time
as
we
can
it
to
green
and
I.
Think
the
last
issue
from
right
is:
there's
some
issue
with
log
files,
a
sea
peeing
over
to
GCP,
where
we
can
get
to
them
later
and
there's
some
issue
with
that
and
I
think
that's
the
last
problem
we
have
in
there.
Am
I
right
on
that
yeah.
B
A
Errors,
so
so
the
way
to
look
for
it
is
the
highlighting
is
just
actually
to
help
us
read
it
because
one
of
the
problems
of
the
head
is
they
used
to
not
highlight
anything,
and
then
it
was
really
hard
to
find
out
where
the
problem
was
so
just
for
our
visual
nature.
They
added
highlighting,
on
the
word
error,
to
help
you
quickly
scan
the
files
and
display
stuff
up
front
it
that
doesn't
actually
trigger
the
failure.
It's
a
non
zero
exit
code
that
does
and
you'll
see
that
it's
the
SCP,
that's
returned.
B
A
B
C
A
So
we're
actually
gonna
have
to
because
one
of
the
things
that
we
did
this
week
is
we
turned
on
required
tests.
Now
you
can't
press
that
merge
button
until
all
the
tests
pass
and
we
did
that
because
we're
owner's
files,
you're
gonna
kind
of
have
to
so
people
just
say:
oh,
it's
family
emerged
anyway
right.
We
want
to
keep
people
honest
and
actually
have
passing
stuff
and
so
now
everything's
required,
which
is
why
you're
gonna
see
the
yellow
dot
in
there.
A
C
A
In
this
case,
it's
just
they
still
every
turn
you
ready
to.
We,
we
actually
spin
it
up
and
make
sure
it
starts
up
and
everything
okay,
but
that
that
has
to
run
now
and
has
to
be
successful
in
order
for
it
to
get
that
green
checkmark,
for
anybody
to
hit
have
a
merge
button
or
for
even
CI
to
merge.
It's
now
a
blocking
job,
and
so
we
have.
C
C
B
D
B
A
C
C
B
A
A
B
Yeah,
if
it's
not
already
in
there
I
didn't
actually
look
at
edit,
was
was
in
there
already,
but
yeah
wait.
We
could
add
that
there,
the
timeouts,
are
just
different
in
the
in
the
script
and
I
talked
to
Fox
ish
a
couple
weeks
ago,
and
he
said,
there's
kind
of
like
two
sets
the
timeout,
so
I
need
to
talk
to
him
about
okay,.
A
A
I'll
paste
the
repo
in
when
I
put
them
here.
There's
two
scripts
here:
one
is
called
Jen
owners
and
what
that'll
do
is
you
point
it
at
a
chart
and
it
can
generate
an
owner's
file
from
the
chart
and
even
if
somebody's
name
and
email
address
are
in
there,
but
you
don't
have
their
github
ID.
It
can
try
to
find
that
using
the
github
API.
You
will
need
to
set
it
github
token.
A
It's
got
a
couple
of
options
to
help
with
that,
like
if
you're
an
admin
on
the
repo
which
a
couple
people
are
I'm,
not
sure
who
you
can
actually
go
ahead
and
make
them
pull
or
read-only
collaborators
on
the
repo
with
a
flag
automatically
or
you
can
get
a
nice
bulleted
list
output
that
can
be
sent
to
the
mailing
list
to
ask
for
them
to
be
members.
There's
number
of
things
we
can
do,
but
it
provides
those
tools
to
help
fill
in
that
gap.
So
that
way
so
proud
the
merge
API.
A
When
you
do
things
like
approve
and
looks
good
to
me,
they
have
to
be
a
collaborator
on
the
repo,
even
if
they're
only
a
read-only
poll
only
collaborating
on
the
repo
and
have
no
special
permissions
beyond
what
they
have
today.
They
have
to
have
that
for
the
access
to
control
to
say,
I'm
sure
they're
in
an
owner's
file-
and
we
also
you
know
trust
them
and
so
that
before
those
come
ants
work,
and
so
that's
the
ideas
to
figure
out
who
those
are
so
that
way,
we
can
do
something
with
them.
A
But
it's
a
start,
and
so
this
was
my
my
way
to
start
messing
with
those.
So
once
we
get
it
turned
on
which
I'd
like
to
do
today
or
tomorrow
we
can
start
layering
in
owner's
files
as
pull
requests,
and
this
tooling
was
just
designed
to
kind
of
help
with
that.
So
who
wants
to
help
me
because,
on
the
pull
request
and
I
need
somebody
with
admin
access
to
deal
with
things
like
adding
collaborators
to
repos,
because
I
don't
have
that
access
right
now,
Vic.
Are
you
gonna
be
around
to
help
with
that?
A
E
A
Works,
that's
the
gap
I'll.
Send
you
an
invite
just
to
make
sure
and
I'll
also
share
it
out
to
the
list
here
in
case.
Anybody
else
wants
to
jump
on
there
as
well,
but
well
I'll,
try
and
get
a
bunch
of
the
the
tasks
done.
So
that
way
we
can
just
crunch
down
another
thing:
we
need
admin
access
for.
At
that
point,.
A
D
A
Yeah,
so
one
of
the
things
that
I
found
when
I
was
doing
the
cig,
apps
update
for
coop
con
was
that
if
you
look
over
time
tracking
the
months
you
actually
see,
that
uptake
is
not
having
the
nice
curve.
You'd
like
to
see
and
I
think
that's
really
because
of
our
ability
to
respond
to
things
and
if
we
can
remove
us
out
of
the
loop
on
things
such
as
old
charts.
A
You
know,
so
we
don't
have
to
deal
with
new
charts
and
common
patterns
and
CI
and
the
charts
we
own
or
the
church
that
don't
have
owners.
We
can
start
to
get
more
interest
in
charts
coming
in
again,
of
course,
we'll
need
better
CI
and
other
documentation
and
stuff,
but
we're
out
of
the
critical
path
for
a
bunch
of
things.
B
D
If
it's
okay,
I'll,
just
repeat
real
quick
I,
just
wanted
to
say
that
I
think
that
that
announcement
that
you
were
talking
about
Matt
would
go
a
long
way
toward
helping
maintain
the
enthusiasm
of
the
community
who
are
starting
to
grumble
a
bit
because
PRS
are
taking
a
while
I
realize
also
reviewing
their
peers
would
be
good,
but
but
if
we
have
some
automation,
that
might
you
know
just
help,
make
the
whole
process
easier.
Anything
we
can
do.
You
know
I,
think
that
would
help
keep,
though
a
below
that
spirit
up
mm-hmm.
A
All
right,
so
I
will
probably
tweak
the
tools
a
little
bit
more
today.
One
of
the
the
other
tweaks
that
I
wanted
to
bring
in
was
to
handle
the
case
of
who
should
you
have
if
it
says
bit
Nami
bot,
because
bit
Nami
bot
manages
a
bunch
of
charts,
but
it's
never
gonna
be
merging
polar
requests,
because
it's
just
automation
and
so
I
did
get
a
list
of
names
from
the
bitNami
folks
of
who
to
put
in
the
owners
files.
For
that
we
probably
need
to
update
the
charts
for
that
as
well.
A
D
A
A
All
right,
then
one
of
them
that
I'm
gonna
kick
in
here
is
we
had
the
documenting
best
practices
from
the
28th
and
I.
Don't
think
somebody
came
to
me
and
said:
did
you
notice
nobody
submitted
a
PR,
yet
for
this,
and
so
I
was
gonna,
bring
it
up
again
that
we
had
some
folks
who
were
interested
in
writing
some
of
the
documentation
on
this
and
I.
A
Don't
know
if
anybody's
actually
here
who
volunteered,
but
we
probably
need
to
start
getting
on
some
folks
or
finding
ways
to
write
some
of
this,
so
I'll
probably
bring
it
up
every
meeting
until
it's
checkbox
to
that
I'm
here,
I,
don't
think
anybody's
here
who
signed
up.
Maybe
they
maybe
they
were
the
only
current
on
their
homework
and
skipped
I
didn't.
E
A
If
you
scroll
down
to
the
meeting
minutes
from
and
I'll
drop
them
in
again
in
case
somebody
came
late
from
last
time,
you'll
see
the
different
topics
and
some
names
next
to
them.
It's
under
documenting
best
practices
review
guidelines
is
the
doc
link
there.
We
can
put
them
in
and
it's
got
PVC
storage
class,
our
back
network
policy,
those
things
and
you'll
see
some
folks
put
their
names.
Excellent
right.
D
A
D
Think
we
also
said
that
we
would
have
a
bit
of
a
just
an
overview
meeting
about
some
of
these
things
because
you
know
not
to
add
unnecessary
ceremony,
but
just
to
kind
of
mine,
all
of
our
collective,
the
collective
knowledge
not
for
the
writing
itself,
but
to
point
to
examples
where
those
where
those
are
best
currently
exemplified
you
know
like
so
someone
on
the
call
might
say:
hey
that
chart.
Does
this
very
very
well,
but
it
has
these
problems.
This
chart.
D
C
A
D
Was
just
I
I
had
a
I
thought,
I
access,
the
memory
of
which
Kurtz
did
that
pretty
well,
but
then
I
just
kind
of
dropped.
It
I
realize
memory
was
someone
here
may
know
right.
I
know
it
was
brought
up
on
the
last
call.
A
few
a
few
charts
were
listed
and
I
remember
looking
at
them,
but
I
I
myself
have
not
done
much
with
that.
I
know.
D
A
D
Yeah,
so
when
you
do
a
home,
create
that's
one
of
the
things
I
added
to
help
it,
it
allows
I
have
as
many
conversations
with
it's
possible
without
wasting
time,
but
just
to
try
to
gather
the
best
practices,
because
they
were
so
wildly
divergent
in
the
charts
already
and
how
that
was
go,
and
that
was
what
everyone
came
up
with
most
far
so
I'm
sure
all
of
us
have
room
for
improvement.
That's
one
of
the
you
know,
I
think
from
our
last
meeting.
D
We
said
that
would
be
a
great
next
step
after
we
do
some
documentation,
I
think
from
what
I
remember
it
was
basically
get
the
low-hanging
fruit
fastest
and
then
move
on
to
the
to
the
things
that
would
bring
you
the
most
value
next,
but
might
take
more
time
elsewhere.
The
first
was
just
at
least
listing
and
linking
to
charts
that
do
some
of
these
items
well
and
maybe
list
any
caveats.
D
A
Let
me
make
this
suggestion
yeah,
because
we're
talking
about
it
and
we
need
a
place
to
capture
it.
Did
you
want
to
start
an
issue
and
stick
a
few
of
them
in
there
that
you
know
already,
and
we
can
say
capturing
this
for
the
best
practices
guide
kind
of
thing
yeah
than
anybody
else
who
comes
along
could
stick
their
own
like
if
I
saw
one
I
could
go.
Oh
I
know
there's
an
issue
on
it.
D
E
E
A
D
So
maybe
so
maybe
what
you're?
If
am
I
hearing
this
right?
Maybe
what
you're
asking
for
is
a
master
issue,
but
we
could
then
link
to
individual
components
that
need
to
be
documented
from
there.
Whatever
you
think
is
best
okay
I'll.
Do
it
that
way
and
then,
if
we
want
to
shift
it
around,
we
can
sounds.
A
D
A
A
A
C
C
A
You
you
going
once
going
twice.
Alright,
I!
Guess
this
our
final
meeting
of
the
year,
so
everyone
have
a
fantastic
end
of
the
year
and
guess
we're
meeting
again
next
year
and
I'll
go
into
the
calendar,
invite
and
cancel
the
individual
meeting
for
the
December
26th.
So
nobody,
you
know,
gets
notified
or
thinks
about
it
or
any
of
that,
and
this
video
will
probably
be
up
online.
Sometime
later
today,.