►
From YouTube: Kubernetes SIG Apps 20190506
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
Welcome
to
kubernetes
cig
apps
for
Monday
May
6th
2019
share
a
link
to
the
agenda
in
the
chat
here.
Anybody
doesn't
have
it.
We
have
the
agenda
here
and
remember.
We've
got
two
topics
for
discussion
today
and
if
anybody
has
anything
else,
they
want
to
add
in
feel
free
to
go
ahead
and
put
it
under
open
discussion,
go
ahead
and
add
it.
In
later.
We
have
no
announcements
or
demos
today,
so
we
can
jump
right
into
the
discussion
topics.
The
first
one
is
the
examples.
Repo
discussion,
sig
apps,
owns
the
examples.
A
Repo
was
at
github,
comm,
/,
kubernetes,
/
examples.
Those
examples
are
mostly
used
in
documentation,
so
you're
gonna
find
links
to
them
and
copies
of
that
material
throughout
the
docs
that
are
part
of
the
website.
In
fact,
that's
what
originally
got
me
to
bring
it
up
a
couple
of
weeks
ago
well,
as
I
found
out
dated
things
in
there
like
using
versions
of
PHP
that
are
no
longer
supported
or
not
following
the
modern
conventions,
because
they
were
actually
written
a
long
time
ago.
A
A
So
while
it's
an
examples,
repo,
it's
just
a
subset
of
the
examples,
and
it's
not
really
maintained,
and
it's
quite
a
bit
dated,
so
it's
probably
better
to
to
just
have
the
examples
be
updated
in
their
current
locations
and
then
work
to
maintain
them
there
rather
than
this
repo.
What
does
everybody
think
about
that?
Anybody
have
any
comments.
A
It
sounds
like
none
one
of
the
things
about
this,
those
before
we
can
deprecated
the
examples,
repo
we're
going
to
need
to
update
the
examples
as
they
are
in
Docs,
so
that
way,
they're
up
to
date
and
then
strip
out
the
links
to
those
places,
and
so
this
is
one
of
those
places
where
we
can
actually
call
for
contributors.
It's
a
fairly
simple
thing
to
get
into
as
far
as
updating
the
docs
and
updating
their
references
in
the
mo
within
them
those
kinds
of
things.
A
So
that's
one
of
the
places
we'll
need
to
do
before
we
do
that,
so
we'll
probably
need
a
deprecation
plan
and
get
those
updated,
and
so
this
is
an
area.
If
anybody
knows
new
contributors
who
want
to
get
into
Doc's,
this
would
be
a
great
place
for
them
to
get
started
and
just
start
poking
around
and
I'll
bring
up
more
of
that
as
we
put
together
a
plan
or
or
figure
out
how
we're
going
to
handle
this.
B
Another
method
would
be
that
people
we
could
have
effectively
people
sign
up
for
triage
and
then
having
a
shadow.
Remember
so
have
one
of
the
owners
or
viewers.
First
gasps,
effectively
shadow
you
on
triage
and
as
you
get
issues
you
can,
you
know
CC
them
for
support
where
you
don't.
You
know,
if
you
don't
know,
what's
going
on
with
the
ED
warburg,
we
can
kind
of
point
you
in
the
right
direction
and
help
kind
of
get
issues
resolved.
B
That
way,
and
my
thought
is
that,
like,
if
someone's
looking
to
join
in
and
contribute
into
the
worklets
control
over
one
way,
it's
the
barrier,
entry
was
probably
still
gonna
hide
the
runway.
It
might
that
might
work
is
by
doing
break
things,
and
that
would
be
a
good
way
to
start
getting
convinced
into
the
repository.
So
you
can
get
membership
for
the
Cooper
day's
project
because
right
now,
it's
kind
of
hard
to
get
the
requisite
number
of
commits
to
kubernetes
be
a
contributing
just
to
say
gaps.
B
A
So
so
I,
like
the
idea
of
spending
time
in
a
meeting
doing
it
part
of
that
is,
is
there's
a
whole
lot
of
issues
out
there,
and
you
know
if
we
have
recorded
meetings
on
this,
it
can
teach
people
how
to
go
in
and
triage
them.
So
they
have
some
examples
of
people
who
do
it,
showing
them
how
they
do
it.
So
we
can
kind
of
scale
horizontally.
A
B
B
Janet's
fine
with
it
if
Tomas
and
my
jack
and
the
others
from
Europe
were
fine
with
it
and
sounds
good.
But
we
I
think
neither
duelist
decide
to
use
part
of
this
meeting
to
do
it
or
to
set
up
a
separate
E
and
if
either
way,
we
need
to
take
the
time
difference
between
US
and
EU
and
where
other
contributors
are
into
account,
so
that
we
can
do
it
during
a
time
frame
with
her.
C
B
B
B
You
compare
the
number
of
open
issues,
the
number
of
bugs
for
sig
apps
relative
to
the
rest
of
the
project,
we're
actually
doing
pretty
good
we're
not
like.
There
are
other
ways
that
you
could
look
at
how
bugs
are
triaged
and
say
to
compare
them
to
our
our
metrics
and
say
that
we're
pretty
not
bad
anyway.
So
I
think
that
sounds
super
reasonable.
We
can
just
like
one
with
wall,
maybe
agenda
to
spend
some
time
on
a
weekly
basis,
going
over
a
high
priority
issues.
A
B
Say
just
I
would
do
it
next
week,
just
because
I
don't
want
to
I'd,
rather
at
least
pre-screen,
what
we're
going
to
triage
as
opposed
to
randomly
Peggy.
Does
that
might
get
time-consuming,
cumbersome
and
not
be
super
useful,
but
maybe
we
should
also
like
in
the
meeting
minutes.
Just
have
people
add
the
issues
that
they
think
are
important,
who
are
sick
members,
and
then
we
can
go
through
them,
but
I
might
want
to
like
take
a
pass
through
what
gets
put
in
there
a
lot
of
issues
we
get
that
pop
up
are
I.
B
Guess
the
term
is
a
player
issues
and
not
necessarily
on
the
part
of
the
user
itself,
but
sometimes
on
the
part
of
not
great
documentation
on
the
project's
behalf.
But
a
lot
of
the
times
like
you'll,
see
an
issue
and
it's
like
well,
that's
intended
behavior,
so
I'd
rather
not
start
doing
those,
because
those
are
easy
to
triage
I'd
rather
get
try
to
take
issues
that
are
a
little
bit
more
informative
for
other
people
to
look
at.
C
A
B
That
there
was
one
other
announcement,
so
Barney
took
a
first
cut.
I,
don't
know
if
anybody
is
taking
a
look
at
it.
Yet
I've
been
super
busy,
so
I
have
it.
I
got
took
on
very
brief.
First
pass,
but
I
haven't
a
chance
to
review
it
of
the
cron
job
ta
plan
and
that's
opening
in
enhancements
I
linked
it
into
the
document.
I
think
right
now,
Liggett
and
my
sulfurous
I'd
be
good
I.
Think.
If
Tomas
well
yeah,
you
should
get
more
people
to
take
a
look:
Thomas
Janet
magic.
A
D
J
I'm
I'm
somewhat
new
to
the
sig
apps
world.
So
hello,
hey
you
guys
doing
or
you
folks
doing
so,
yeah.
It's
a
nice
nice
to
see
you
guys,
I
I,
just
I'm,
not
sure
what
open
discussion
is.
I
was
interested
in
learning
more
about
where
homes
going
with
certain
things
and
getting
involved
in
some
of
the
community
work
in
that
area,
but
I'm
not
sure
that's.
This
is
dedicated
to
if
home
is
a
subset
of
sig
apps
as
far
as
where
its
community
and
stuff
is
or
what
so.
A
D
D
D
A
Not
up
on
that
right
now,
it
is
a
separate
sig
that
does
that
called
sig
service
catalog
and
they
handle
those
things.
To
be
quite
frank:
I'm
gonna
drop
a
link
into
them
in
do
the
chat
here,
I'm,
not
sure
where
they're
at
because
I
have
not
been
following
as
of
late
all
right,
so
that
happens
here.
We're
gonna
work
with
things
more
like.
A
What's
in
the
community,
and
we've
been
spending
a
lot
of
time
lately
on
things
like
the
workloads
api's,
so
things
like
cron
job
deployments,
daemon
sets
a
bunch
of
the
core
controllers,
things
of
that
nature.
Things
like
there's
an
application,
C
or
D
in
controller
that
were
in
submitting
in
kubernetes
SIG's.
Some
of
the
things
like
that.