►
From YouTube: Kubernetes SIG Apps 20190415
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
April,
15th
2019.
Let
me
get
started
by
sharing
the
meeting
minutes.
We
have
a
light
agenda
today.
There's
the
meeting
minutes
and
everything
it's
for
the
15th.
We
don't
have
any
announcements.
Does
anyone
have
anything
that
needs
to
be
announced
or
otherwise
shared.
A
Note
fantastic:
we
don't
have
a
demo
today,
so
we
can
jump
right
into
the
discussion
topics,
we're
pretty
light
on
discussion
topics.
If
you
had
anything,
please
feel
free
to
stick
it
into
the
open
discussions,
but
otherwise
we'll
start
going
right
through
these.
The
first
one
that
I
wanted
to
share
is
1:15
is
now
under
development
and
just
the
same
as
with
1:14,
every
change,
everything
that
needs
to
go
in
need
still
in
through
a
cap.
They
just
started
at
the
end
of
last
week,
working
on
the
list
of
issues
that
get
tracked.
A
A
C
B
A
Good
cool,
all
right
and
and
in
order
to
get
once
the
tracking
issue
is
in
the
release
team
members
are
there.
This
falls
under
Kendrick
who's
handling,
enhancements
to
make
sure
it
gets
tracked
and
released,
because
if
it's
not
tracked
and
if
it's
not
handled,
they
won't
let
it
in
or
that'll
be
a
problem.
So
I
had
this
to
the.
A
Everything
when
it
comes
to
timeline
and
members
is
tracking
under
the
kubernetes
org
there's
a
sig
release,
repository
and
they've
got
templates
and
everything,
and
so,
if
you
go
look,
I'll
drop
another
link
in
here.
This
has
the
entire
timeline
for
every
week,
and
every
single
thing
of
what's
going
on
with
115
ants
means
freeze,
is
April
all
right.
April,
30th,
yeah,
April
30th,
is
the
enhancements
freeze.
A
And
then
they
really
just
got
started
on
it.
It
was
the
end
of
last
week
that
the
board
got
filled
out
and
there
were
shadows.
Do
the
enhancements
lead
before
that?
None
of
that
was
even
filled
in
so
they're
really
getting
moving
on
this,
and
we
got
about
15
days
left
on
getting
all
the
enhancements
filed
in
and
tracked
all
right.
That's
all
I
wanted
to
share
on
capsule
wanted
to
make
sure
we
knew
where
we
were
at
and
what
it
would
take
for.
115
for
everything
we
wanted
to
get
in.
C
D
Yes,
I'm
looking
at
trying
to
get
for
a
115
at
the
moment,
I
mean
in
terms
of
what's
I
mean
we've
got
good
like
proof-of-concept
already,
so
it
was
like
a
fair
amount
of
coding.
Works
been
done
right.
The
main
thing
that
needs
finalizing
is
the
API.
We
say
that
I
had
I
didn't
raise
the
PR
the
other
day,
Tim
Tim
Hawke,
another.
D
C
D
Stop
please
stop
where
those
hooks
are
already
defines.
They'd
been
like
a
container
then
got
life
cycle
type
sidecar,
something
like
that
is
what
it's
currently
looking
like.
So
if
that
gets
approved,
and
then
we
just
need
a
test
plan,
I
think
and
then,
but
I
should
be
pretty
much
everything
in
terms
of
their
caps
in
terms
of
making
it
implementable,
so
yeah.
E
D
C
So
I
mean,
like
I,
think
it's
realistic
to
target
115
FS
you
want
to
do
or
you
can
just
spend
the
time
getting
it
ready
to
go
in
115
and
target
116
and
have
like
kind
of
a
zero
stress
rollout
for
releasing
it
as
outfit
116
totally
up
to
you.
If
you
want
to
go
115,
you
can
always
slide
the
milestone
to
116
later,
if
that's
true
decide
to
do,
if
you
wanted
to
do
115,
it
will
be
opening
up.
The
tracking
issue
now
would
be
a
good
idea.
Yeah.
C
Again,
I
think
it
readable
PDB
is
accessible
as
part
of
the
GA
cap.
So
if
we
merge
that
that's
fine
and
then
relaxing
it's
not
a
feature
per
se
right,
it's
more
modification
to
an
existing
API
to
relax,
computability,
so
I
think
that's
fine
too,
because
we're
not
really
changing
API
and
the
question
would
be
if
we
want
to
remove
then
available.
Do
we
do
that
think.
E
C
It
should
but
I,
but
I
mean
like
if
we
I
don't
I'm,
not
like
saying
we
shouldn't,
keep
it
like
it.
I,
don't
see
anybody
feeling
strongly
one
way
or
the
other,
so
we
can
just
keep
it,
and
then
we
do
that
and
we
just
have
to
promote
to
G
a
kind
of
wholesale
as
soon
as
the
scales
of
resource
stuff
is
implemented.
Yeah.
E
C
You
want
to
cap
on
the
scales
of
resource.
You
can
split
it
up
if
you
want
to,
whatever
you
think,
is
easier
and
but
sometimes
for
smaller
functionality.
It's
easier
to
get
the
features
merge
if
you
learn
to
smaller
caps,
and
then
we
do
that
back.
It's
agreed.
If
we
get
those
into
one
15
in
B,
1
beta
1,
we
could
go
to
GA
with
it
and.
A
Okay,
then,
let's
move
on
to
a
couple
of
bits
of
housecleaning.
We
have
I've
been
looking
over
the
cig,
apps
thing
and
two
things
jumped
out
at
me.
One
is
that
our
contributing
guy
in
the
kubernetes
community,
repo
and
say
gaps
there
is
a
contributing
guide.
This
is
one
of
the
things
that
what
is
it
can
contribute
sinking.
Try
backs
wanted
us
to
have,
and
it
is
woefully
out
of
date
such
as
it
still
includes
help.
A
A
C
Didn't
take
a
whack
at
it,
but
there's
something
there's
another
PR
I
want
to
get
through.
First,
we
talked
about
this
last
week.
We're
gonna.
The
first
thing
that
we
wanted
to
kind
of
clean
up
was
not
just
the
contributing
guidelines,
but
we
wanted
to
get
our
owner's
files
in
better
shape
and
start
using
owners
aliases
and
then
update
the
reviewers
and
approvers
for
the
api's,
and
we,
the
discussion
was
around.
C
We
think
that
will
make
the
contributing
experiments
in
terms
of
like
making
it
more
clear
what
you
need
to
do
to
get
to
be
a
reviewer
and
how
you
can
go
from
reviewer
to
approver
is
more
clear,
and
then
there
are
some
people
who
aren't
listed
as
reviewers,
who
have
probably
done
enough
at
this
point
that
they
should
be
reviewers
and
maybe
even
like
unpack
approvers.
So
we
just
mind
them.
C
You
know,
make
sure
people
get
out
of
there
and
then
some
other
people
that
probably
like
aren't
really
active
at
all
and
haven't
been
in
quite
some
time
and
some
of
them
never
move
themselves,
but
some
of
them
haven't.
So
we
wanted
to
clean
that
up
and
then
my
goal
is
to
buy
like
in
this
week,
have
that
PR
issued
and
send
it
out
to
the
sig
ass
mailing
list.
C
Maybe
Siddhartha's
consumer
nameless
to
one
of
the
general
things
they're
kind
of
asking
is
everyone
all
those
things
kind
of
go
around
and
clean
their
stuff
up?
Cc
Li
is
already
kind
of
done
this
a
little
bit.
It's
a
bit
different
approach
where
they
I
think
removed
everyone
and
said
hide
yourself
back
I.
C
Don't
think
our
case
is
bad
extreme.
We
don't
really.
We
don't
have
like
50
or
60
people.
So
it's
not
that
big
of
a
deal,
but
not
only
one
thing
to
clean
up
and
then
from
there
I
think
it
would
be
instructive
to
go
through
and
then
talk
about
the
contributing
guidelines
and
we
reference
back
out
to
like
the
process
for
reviewer
ship,
an
approver
sugar.
Although.
A
The
other
thing
that
I
had
had
to
do
with
examples:
I
have
forgotten
that
say:
gaps
technically
owns
the
examples,
repo
which
is
still
around
there's
a
link
to
it
in
the
meeting
minutes.
I
need
to
open
this
up,
it
doesn't
get
a
lot
of
activity
and
the
there
is
an
owner's
file
in
it
with
Sebastian
and
a
in
it.
C
A
I,
look
at
this
I'm
looking
to
say
is
this
something
that
we
should
get
into
a
little
bit
better
shape
or
help
the
docs
folks,
or
do
we
hand
it
off
to
the
docs
folks?
Should
this
be
deprecated
or
kept
around
things
like
that,
I
mean
if
I
go
look
at
so
if
you
go
into
the
PHP
Redis
example
inside
of
guestbook,
it's
using
an
entirely
deprecated
and
probably
unsecure
of
PHP
there's
a
lot
of
little
nuances
in
here
of
this
things,
not
very
well-maintained.
C
A
C
I
can
come
up
with
a
list
of
things
that,
in
my
mind,
you
could
be
done
here
like
my
sequel
or
WordPress
should
be
using
stateful
sets
inside
of
the
deployments
when
they
upgrade
to
be
example,
from
replication
controller
to
the
Plymouth
I.
Guess
you
don't
need
to
have
staples
that
at
the
time,
so
we're
using
that
set
so
that'd
be
like
one
thing
register,
probably
they're,
better
ways
to
run
Redis
the
Cassandra
one
looks
okay.
There
are
better
ways
to
do
a
see
provider.
A
C
I
mean
I,
think
I'll
say
this
rate.
The
quality
of
examples
in
the
kubernetes
community
is
there
are
many
of
them
and
not
all
of
them
are
good,
which
leads
to
a
lot
of
Carnival
team
and
a
lot
of
actual
issues
for
people
who
start
with
an
example
thinking
that
wow
I
got
it
from
the
website.
This
is
the
right
way
to
do
it
and
then
probably
doesn't
get
them
too
far.
So
like
updating
this
stuff
to
like
including
high
disruption,
bug
to
probably
be
a
good
thing.
C
A
I
found
almost
nobody
uses,
pot
disruption,
budget
and
I.
Think
that's
because
every
time
I
bring
it
up,
they
go.
Oh
yeah
I
forgot
about
that,
because
it's
almost
never
talked
about,
and
people
have
already
had
to
do
so.
Many
other
little
things
to
create
numerous
yamo
files
for
their
stuff
that
they
forget
about
all
of
the
things
they
can
do.
Or
you
know,
even
if
it's
horizontal
pot,
auto-scaling
I,
don't
see
that
very
often,
even
when
it
would
be
really
useful.
So.