►
From YouTube: Kubernetes SIG Apps 20180129
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
And
you'll
notice
in
here
real
quick,
the
first
thing
I'll
say,
is
in
the
demo
slot.
We
don't
have
a
demo
our
demo
for
today
had
to
move.
So
if
anybody
had
a
demo
they'd
like
to
do
at
some
point
in
here
today,
please
feel
free
to
put
your
name
in
there
and
go
forward
or
to
speak
up.
Otherwise,
because
may
not
have
won
this
week.
A
I
think
MIT
Nami
is
having
theirs
right
around
now,
there's
a
whole
bunch
of
things
going
on
and
so
they're
a
bunch
of
the
usual
suspects
who
just
they're
not
here
today
due
to
travel
and
things
like
that,
so
my
name
is
Matt
Farina
for
anybody
who
doesn't
know
and
I'll
jump
in
one
of
the
first
announcements
is
the
helm
summit
is
coming
up.
You
can
book
your
hotel,
you
can
get
tickets.
All
of
that
stuff
is
there.
The
speakers
are
announced
on
the
one
thing
I'll
say
is:
there's
the
embedded
thing
for
the
speakers.
A
If
you
go
to
the
full
thing,
you
can
see,
there's
a
two-day
schedule,
so
it's
not
just
the
first
day,
but
you
can
even
get
into
the
second
day,
but
the
link
is
in
here
for
that.
So,
if
you're
interested
in
the
helm
summit,
if
you're
interested
in
helm,
you
can
go
see
what's
there
and
see
if
you
want
to
go,
it
is
being
held
in
Portland
in
February.
The
next
announcement
that
I've
got
is
I,
don't
know
how
widely
this
has
been
communicated.
A
So
we
can
talk
about
that
again
in
a
minute,
but
that
was
said.
Can
we
solve
that
in
the
ecosystem?
And
then,
if
it
works
for
all
the
different
cases,
we
have
from
the
smallest
cases
to
the
largest,
maybe
there's
a
way
we
can
bring
it
into
core
rather
than
trying
to
solve
it
there,
because
there's
a
lot
of
complexities
to
that
you
know
it
were
before
we
might
have
tried
to
do
that.
They're
now
saying.
A
Well,
that's
an
ecosystem
thing
and
so
you'll
see
the
prioritization
of
feature
developed
being
more
on
CR
DS,
API
servers
and
essentially
extension
points.
If
you're
not
following
there's
been
things
like
moving
the
cloud
provider
code
out
of
core
so
that
every
cloud
providers
code
doesn't
sit
as
part
of
the
core,
a
repo
and
set
up
but
make
an
extension
point
in
core
and
then
have
that
code
elsewhere,
and
that
shift
is
now
kind
of
well
underway.
A
But
I,
don't
know
how
often
it's
talked
about,
and
so
I
just
wanted
to
make
a
point
to
bring
it
up
here,
because
it's
come
up
in
several
of
the
past,
say
Karka
texture
meetings
as
making
decisions
as
I
push
it
out
has
been
now
happening
rather
than
just.
How
do
we
get
there
but
interesting?
This
should
happen
out
there
are
there
any
questions
about
that
is.
A
This
moment
probably
look
at
the
meeting
moments.
Maybe
look
at
last
week's
cig
architecture
if
the
videos
up
yet
because
we
talked
about
a
couple
of
cases
in
there
and
even
we
had
a
little
discussion
about
how
we
haven't
been
great
at
communicating
it
and
and
some
of
what
that
means,
and
so
that
might
be
a
good
place
to
get
started.
It's
just
the
meeting
minutes
from
the
last
one
or
or
watch
the
meeting
cool.
A
All
right,
so
that's
what
I
for
the
announcements
I,
guess
that
we
can
jump
into
the
updates
we
made
have
a
quick
meeting
or
maybe
well
have
a
long
open
discussion
and
so
for
the
first
two
we
have
kind
of
the
kubernetes
core,
which
is
sets
and
jobs
at
the
moment.
I
guess
I'll
just
jump
in
real
quick
before
somebody
else.
A
Does
the
cron
job,
one
that
we
talked
about
last
week
in
here
with
time
zones
that
one
of
has
been
asked
to
be
pushed
into
the
ecosystem
and
the
issue
on
it
has
been
updated
to
reflect
that
as
of
the
end
of
last
week.
So
that's
the
status
on
that
particular
one
I,
don't
know
if
anybody
else
at
any
other
statuses.
A
C
Okay,
so
we're
trying
to
get
a
few
things
done
inside
of
the
core
controllers.
We
want
to
get
the
ete
tests
and
the
core
controllers
themselves
on
the
v1
API,
and
we
want
to
get
conformance
tests
done
this
quarter,
basically
for
the
next
release,
we'd
like
to
have
conformance
right
now,
so
one
of
the
things
I'm
doing
now
is
trying
to
investigate
the
process.
A
C
So
really,
we've
already
put
some
effort
into
adding
integration
tests
and
removing
things
that
should
really
be
at
an
integration,
a
medium
level
down
to
there,
so
that
our
EDD
becomes
more
of
a
black
box
and
you
not
only
get
their
stronger
test
signals,
but
is
in
alignment
with
what
is
generally
agreed
upon.
That
conformance
test
should
be
so,
in
theory,
are
a
été
at
the
end.
State
should
be
our
conformist.
A
A
All
right
well
we'll
move
on.
We
don't
have
a
demo
right
now,
so
we
can
move
on
to
the
other
tooling
projects.
There
are
four
of
them
listed
right
now
that
I
just
grabbed
from
last
time.
If
somebody
here
has
another
project,
they
want
to
add
to
this
list
that
they
want
to
talk
about
here.
Please
go
ahead
and
feel
free
to
add
it
did
we
have
anybody
here
from
the
helm.
Anybody
here
wanted
to
talk,
helm.
A
A
Alright
I'll
talk,
we
I'm
doing
a
little
too
much
talking
this
week.
So
if
somebody
else
wants
to
jump
in
and
talk
about,
these,
please
feel
free,
I,
don't
need
to
talk
to
the
whole
time
for
Hjelm
release.
2.8
has
now
gone
out.
It
went
out
last
Monday.
It
turns
out
that
there
is
a
bug,
though,
so,
if
you
use
it
and
you're
experiencing
issues
make
sure
you
test
with
it.
First,
we
didn't
get
enough
use
of
the
release
candidates,
which
is
something
we've
talked
about.
How
to
increase
a
release.
A
Candidate
usage
and
a
bug
was
found
out.
It
actually
has
to
do
with
doing
patch
merges
with
code
from
client
go
down
to
API
machinery
and
we're
trying
to
trace
through
that,
but
it
seems
that
there's
some
upgrade
test
problems
that
could
come.
Some
people
are
experiencing
it,
others
aren't
and
we're
still
working
through
trying
to
solve
that.
So
expect
a
dot
one
release
to
come
out
here
soon
as
soon
as
we
can
figure
out
that
and
get
it
fixed,
I
think
that's
the
big
news
on
the
home
front,
just
the
release
in
the
bug.
A
Okay,
I
guess
I
can
give
this
name
to
fajn
that
one
too
so
with
charts.
One
of
the
things
that's
been
going
on
in
the
charts
repository
is
we've
been
working
to
document
processes?
How
do
you
deprecated
charts?
How
do
you
promote
charts
from
incubator
to
stable
incubator
and
stable
used
to
mean
it
just
used
stable,
api's,
or
it
used
like
alpha
api's,
particularly
workloads,
and
things
like
that?
A
But
now
that
the
workloads
API
has
graduated
to
B
b1
and
most
of
those
are
stable
and
on
alpha
api's
we're
using
now
that
are
on
all
the
time,
then
incubators
kind
of
become
more
of
the
testbed
to
create
and
work
out,
new
charts
and
then
stable
has
become
the
ones
that
are
more
stable
is
the
direction
it's
going,
but
we've
been
documenting.
How
do
you
promote
things?
How
do
you
do
this
so
now
working
on
lots
of
process
documentation
along
with
review
documentation
because
we've
added
owner's
files?
A
So
if
anybody
wants
an
owner's
file
for
their
chart,
come
see
me
and
I'll
help
you
get
set
up
with
that
we're
trying
to
work
those
in,
and
so
we
also
want
to
have
consistent
documentation.
So
people
know
the
processes
that
are
going
on,
so
they
know
how
to
promote
things,
what
to
go
through
how
to
review
stuff
and
so
right.
A
The
other
thing
that
we're
doing
in
charts,
which
might
be
interesting,
we're
gonna,
add
office
hours
in
on
the
charts
chat
meeting,
is
every
other
Tuesday
and
so
last
Tuesday,
the
maintainer
x',
and
whoever
else
wanted
to
join
met
to
just
hash
through
things
it
meets
every
other
week
and
we're
gonna
try
something
new
called
office
hours
and
if
you've
got
a
chart
or
a
PR
and
the
charts,
a
repository
you
want
to
talk
to
somebody
about,
like
we've,
been
bad.
Getting
back
to
the
pull
request,
reviews
or
something
like
that.
A
You
want
to
corner
us
or
you
want
to
talk
through.
How
do
you
do
something
we
are
going
to
have
a
meeting
for
that?
I'll
paste
the
link
in
here
in
just
a
minute,
but
we're
going
to
have
that
on
the
off
Tuesdays
from
our
normal
meeting,
to
give
people
an
opportunity
to
do
that
if
nobody
comes
face-to-face,
we're
going
to
start
having
time
to
work
through
those
pull
requests
to
try
to
get
better
at
curating
those,
especially
some
of
the
harder
ones,
and
so
that's.
What's
going
on
with
charts
any
questions,
charts
or
home.
A
D
D
At
the
home,
we're
back
yes
and
I
think
this
is
just
managed
under
the
releases
yeah.
That's
where
it
is.
That's
that's
good
to
see,
there's
a
there's,
a
link
at
the
top.
The
other
is
I
noticed
that
and
there
the
issues
there's
a
number
of
them
that
are
labeled
and
a
proposal
and
some
have
like
helm,
3
and
then
so.
My
question
really
is:
where
where's
the
best
way
to
see
what
people
are
like
requesting
sort
of
proposals
for
what
help
3
might
be.
A
I
would
recommend
writing
it
up
as
a
proposal
and
putting
it
in
as
an
issue
will
be
specifically
talking
about
those
at
the
helm,
but
we've
teetered
around
some
of
these,
such
as
the
use
of
CRTs
and
API
servers
and
changing
things
up
the
way
tiller
works
and
home
3.
But
a
lot
of
that
discussion
is
more
about
trying
to
maybe
curate
some
of
those
ideas
and
issues
right
now
and
then
talk
about
them
at
the
helm
summit.
A
D
A
A
Great
and
if
you
can't
make
those
for
other
folks,
the
helm
folks
have
a
meeting
every
Thursday
this
week
up
might
be
light.
I
have
no
idea
what
it's
going
to
be
like
with
the
Microsoft
folks
and
the
bit
Nami
folks
are.
Some
of
the
people
are
traveling,
but
normally
every
Thursday
there's
a
meeting.
If
you
go
to
the
kubernetes
community
repo
and
you
go
to
see
gaps
in
there,
you'll
actually
see
we
have
the
charts
meeting
and
the
helm
meetings
listed
with
the
links
and
all
of
that,
but
that's
Thursday,
like
10:00
a.m.
Pacific.
A
D
Where
those
kinds
of
things
can
be
discussed,
yeah
that
was,
it
was
just
gonna
lead
into
like
being
prepared
to
show
home
summit
I
guess
with
some
of
these
be
three
topics
so
either
knowing
what
you
may
be
talking
about,
or
what
we
should
be
prepared
like
either
present
or
have
really
ahead
of
time
or
just
kind
of
show
up
and
we'll
figure
it
out
it.
While
we're
there
yeah.
A
And
I
know
some
folks
have
topics
that
they're
thinking
about
ahead
of
time,
such
as
I
would
say:
CRTs
and
API
controllers
are
a
couple
of
them.
There's
talk
of
you
know,
moving
from
G
RPC
to
Jason
I,
you
know,
I,
don't
know
where
a
lot
of
this
is
gonna
go,
but
there
are
a
lot
of
ideas
out
there
for
what
people
would
like
to
do
a
lot
of
its
additive
or
breaking
changes
to
try
to
fix
things
that
are
problematic.
Oh,
okay,
okay,
thank
you.
B
B
B
A
A
Going
once
going
twice
going
three
times:
I
guess
this
is
going
to
be
an
incredibly
short
meeting
this
week,
we'll
we'll
try
and
have
more
prepared
for
you
if
there's
anything
that
you
want
to
get
on
the
agenda
for
a
demo
or
a
topic
to
discuss
in
the
future
that
you
weren't
prepared
for
today,
please
reach
out
to
me
or
Ken,
who
is
here
today
or
stick
it.
You
know
into
the
meeting
minutes
and
bring
it
up.
Alright
folks,
I'll,
stop
recording
and
have
a
wonderful
week.