►
From YouTube: Kubernetes SIG Apps 20170403
Description
The retrospective doc is online at https://docs.google.com/document/d/1fAE4qyxhHxjnFYWj8dKUUfoqKbKZVZsN7KDHsAizqSs/edit
Minutes for the meeting are online at https://docs.google.com/document/d/1LZLBGW2wRDwAfdBNHJjFfk9CFoyZPcIYGWU7R1PQ3ng/edit#heading=h.bp6gjps22yy8
A
According
and
so
welcome
everyone
to
the
april
third
2017
meeting
of
Gruber
net
e
cig,
apps,
I'm,
Matt,
Farina
I,
don't
think
Michelle
is
going
to
make
it
today,
she's
traveling
at
the
moment,
and
so
let's
get
started
as
far
as
announcements
go
I,
don't
think
we
have
any
announcements
this
week
we
have
the
category
slot
for
it
and
there's
nothing
that
I
have
that.
I
know
that
it
specifically
should
be
announced
here.
Does
anybody
else
have
anything
that
they're
aware
of
that
came
out
of
khoob,
khun
or
cognitive
con
that
hasn't
been
conveyed
yet.
B
A
A
A
A
D
So
for
me,
for
one
important
equate
from
up
their
perspective
was
that
the
way
to
sessions
welcome
Michelle
and
one
control
better
where
they
emphasize
the
same
topic,
which
is
that
there
is
more
love
needed
for
cuva,
latest
users
or
developers
who
use
google
net.
Is
that
was
like
an
important
theme
for
me
and
that's
why
I'm
going
this
call
and
looking
forward
to
more
into
c
cups
just
being
quite
high
level,
but
I
think
it's
recognized
that
we
have
to
make
gwinnett
is
more
approachable
for
developers,
which
I
believe
is
this.
E
Have
one
observation
escaped
if
I
measure
sure
please?
Yes,
I
think
that
actually
a
lot
of
people
don't
need
any
new
features
abilities.
So,
like
many
people
are
running
the
apps
and
they
are
just
fine
like
there
were
some
stands
with
people
who
are
basically
just
you
know,
running
apps
on
Copernicus
and
just
using
it
without
any
sophisticated
features,
and
it
seems
like
they
were
quite
happy
with
them.
E
So
there
are
quite
a
few
users
who
are
happy
with
how
the
project
behaved
right
now,
of
course,
there
are
still
people
who
want
more,
but
I
think
that
overall,
the
project
made
are
good,
is
making
good
work
of
appealing
to
people
who
just
want
to
run
drops.
Of
course
it
can
be
simplified,
streamlined
as
Michelle
Medical
keynote.
It
can
be
made
much
easier
for
developers,
but
I
think
the
direction
the
overall
direction
is
good.
From
my
point
of
view,
from
what
I
observed
at
Keuka.
A
A
F
Hi
Matt,
thank
you
so
much
this
little
hill
we
met
at
the
cube
con
Seattle
I.
Believe
anyway,
I
was
that
I
was
at
the
q
con
Berlin
as
well
and
I
agree
with
the
person
who
just
said
I'm.
Sorry
I
couldn't
figure
out
the
name
who
just
spoke
just
before
the
previous
guy
and
the
the
keynotes
by
Joe
and
Michelle.
F
Definitely
strike
definitely
struck
for
me
as
very
important
and
even
at
the
see
gaps,
meeting.
I
think
there
were
few
of
us
who
were
in
the
meeting
as
well,
and
we
spoke
around
the
same
thing:
how
to
make
it
easier
band.
It
seems,
and
after
speaking,
to
Antoine
and
very
various
other
people
during
the
conference,
all
together
conference
I
also
felt
that
many
people
are
facing
the
same
problem
and
many
people
are
trying
to
solve
the
same
problem
and
there
each
of
us
are
having
different
takes
towards
the
problem.
F
For
example,
the
mirantis
people
are
trying
to
solve
it
using
app
controller.
There
is
obviously
the
most
famous
project
out
here,
big
helm.
Then
there
is
composed
and
open
compose
and
various
other
people
trying
to
do
various
other
things.
So
that
definitely
strikes
as
stacks.
We
are
the
problem
to
be
soiled
and
many
people
are
trying
to
solve
so
I
just
wanted
to
agree
to
the
previous
comment
by
the
gentleman,
and
we
are
looking
forward
to
work
together
on
this
with
everybody.
F
A
H
We
need
to
work
on
how
to
simplify
writing
resources,
and
this
is
going
beyond
complaining
is
more
like
now
we
have
to
write
many
large
gamma
phi
and-
and
so
there
were
a
couple
projects
like
open
composer
is
cute
college,
keep
the
designers
for
it
shows
or
boot
configuration
with
certain
projects
going
out
now
and
already
what
would
like
to
drive
on
a
disk
in
together
working
group.
So
we
don't
work
in
separate
0
and
get
together.
I
also
simplify
the
first
time,
experience
to
referee
soon.
H
D
I'll
go
for
a
month,
so
not
sure
where
that's
exactly
the
topic
for
this
group.
Well,
my
lightning
talk
with
keep
going
was
on
cloud
native
design
patterns
and
and
I'm
writing
the
time
to
write
the
book
around
to
burnet
his
patterns,
but
I,
wonder
whether
not
just
pulling
but
things
like
use
cases
patterns,
best
practices.
Things
like
that.
D
Our
topic
for
this
sake,
or
not
it's
more
like
when
you
want
to
use
copper,
natives
as
a
developer,
not
a
cluster
of
this
data
and
their
common
use
cases
or
if
you
have
to
solve
again
and
again
whether
documenting
those
is
obviously
like
steak,
because
I
have
to
know
a
discussion.
A
couple
of
comments
they
go
with
that.
Yes,.
I
Also,
there's
also
sick,
app
life
cycle,
which
also
deals
with
these
issues
in
their
supposedly
a
little
bit
more
covering
like
how
did
the
old
template
eyes
config,
you
might
want
to
just
drop
in
there
and
see
what
they're
saying
and
if
you
see,
and
maybe
the
cig
and
thats
a
need
to
make
sure
we
are
clear
to
people
as
what
stick
handles.
What.
J
A
And
I
think
that
it
kept
falling
apart
on
coordination-
probably
my
fault
in
getting
folks
together
to
do
it
only
one
or
two
people
spoke
up
and
being
interested
in
writing
some
of
that
down.
I
think
you
know
documentation
isn't
always
that
interesting
and
we're
all
quite
busy,
but
this
is
really
important.
So
anybody
who
is
interested,
let's
get
the
ball
moving,
and
but
it
didn't
really
get
going
before.
Okay,.
J
J
A
G
K
Right
so
yeah,
first
of
all,
thank
you
so
much
for
inviting
me
to
help
run
the
really
search
perspective.
Obviously
a
it's
always
really
good
to
get
feedback
as
soon
as
we
can
in
terms
of
release
cadence.
So
it's
all
fresh
in
our
minds
and
to
that
end,
I
started
a
document
I'm
going
to
paste
a
link
to
it
in
the
chat.
K
But
the
goal
here
is
for
you
to
go
into
this
document
here
for
a
couple
of
minutes
and
enter
in
your
feelings
about
what
went
well,
what
could
have
gone
better
and
what
we're
going
to
try
and
do
differently
for
the
next
release
17.
So
you
should
have
write
access
to
that
document
and
if
you
write
a
what
could
have
gone
better
or
what
we
should
be
differently,
I
would
risk
request.
K
We
put
your
initials
after
it
just
so
that
you
can
speak
to
it
when
we
go
through
them,
because
it's
really
important
to
have
clarity
in
these
issues,
because
we
don't
want
to
have
misunderstanding
so
just
to
give
a
quick
update
on
what
the
release
retrospective
is
for.
What
are
we
trying
to
accomplish?
Essentially,
the
goal
is
to
have
a
blame
free
place
where
we
can
talk
about
all
the
things
that
if
we
could
rewind
time
and
do
things
differently,
what
what
would
we
have
done
differently
as
a
group?
K
What
are
the
things
that
had
we
known
oi
know
now
we
could
have
optimized
or
changed,
and
how
do
we
can?
How
do
we
bring
those
forward
to
the
next
release
so
that
we
don't
repeat
our
mistakes
and
at
the
beginning
of
these
retrospectives,
because
we're
sharing
a
lot
of
information
and
ideas
and
feelings
about
something
that
was
occasionally
contentious,
I.
Think,
given
my
experience
with
the
last
several
releases
of
committees,
this
particular
one
was
more
contentious
in
some
ways
than
others,
because
there
were
a
lot
of
things
being
changed.
K
It
was
also
considered
stabilization
release
so
that
that
can,
when
you
start
dealing
with
technical
debt,
that
can
raise
a
lot
of
feelings
and
concerns
and
questions
so
I.
What
I
would
ask
is
everybody,
as
you're,
participating
in
this
retrospective
to
just
be
respectful
of
other
people's
opinions?
K
K
K
Great
and
obviously,
if
you
have
questions
it's
going
to
move
forward,
please
feel
free
to
to
do
that,
so
we're
going
to
start
with
what
went
well
and
I
think
the
gaps
did
a
ton
of
really
great
stuff
this
time
around.
So
I
would
expect
there
to
be
quite
a
few
bullet
points
here,
but
I'll
go
ahead
and
scribe
well.
K
K
So
I
think
a
tremendous
amount
of
appreciation
should
go
to
the
organizers
because
I,
you
know,
everybody
has
a
has
a
day
job
that
they're
attending
to
as
well.
In
addition
to
these
things,
as
we
all
do
so
being
an
organizer
can
sometimes
be
a
thankless
job,
so
I
just
want
to
I
want
to
give
that
props
out
to
to
everybody
who's,
helping
organize
this
very
vital
and
active
cig.
K
K
K
A
K
A
A
K
I
K
Would
I
would
absolutely
love
to
do
that?
I'll
talk
to
Michelle
about
getting
on
the
agenda
to
do
that,
I
would
listen
to
you
great
can
I.
Ask
anybody
in
here
who
is
the
cluster
operator?
Do
a
hop
over
to
sig
cluster
ops
a
little
more
frequent
linkous?
We
definitely
need
more
more
operator
experience
on
the
on
the
flip
side,
so.
L
K
K
A
Sure
sure
this
is
the
as
Michelle
noted
earlier,
third
time's
the
charm
and
trying
to
get
this
going,
but
the
first
two
times
we
talked
about
it
and
something
usually
goes
out
on
the
mailing
list
and
maybe
a
person
jumps
in,
but
we
haven't
been
able
to
get
the
ball
rolling
on
taking
this
idea
of
documenting
back
best
practices.
These
things
that
many
of
us
know
and
share
through
word
of
mouth,
it's
a
lot
of
times
called
tribal
knowledge.
A
K
K
M
Yeah,
so
I
am
kind
a
multi-team.
My
first
impression
was
that
supposedly
owners
have
trials
failures
and
plated
in
general,
but
it
would
be
great
if,
from
as
part
of
the
gaps
who
could
sit
down
and
like
coordinate
the
effort
because,
for
example,
I,
I
I'd
realized
the
most
of
the
deployment
failures
because
they
were
about
12
15
players
and
yeah
I
had
in
total,
like
45
yrs.
Most
of
them
were
flakes
from
mod
and
Lady
to
artists,
I.
M
K
K
K
K
K
So
I
can
add
one
thing
here:
is
that
so,
if
people
bring
tools
or
things
that
they're
working
on
end
of
the
cig,
the
single
best
way
to
get
feedback
is
to
do
demo
and
to
make
sure
that
everybody
in
the
in
the
group
gets
a
gets
a
good
look
at
it
and
the
thing
that
demoing
can
be
very
frightening,
especially
when
it's
your
own
project,
because
I
the
demo
gods
can.
Or
can
we
review
with
you
or
violently
against
you
so
I,
you
know,
don't
be
afraid
to
do
that.
A
Here's
the
thing
whether
you're
demoing
a
whole
new
project
or
just
a
feature
on
an
existing
one.
We
want
to
have
those
you
know,
you'll
see
for
some
of
you
who
are
new
you'll,
find
that
in
a
typical
week,
we'll
demo
one
thing
sometimes
two
things:
we
regularly
like
to
have
short,
quick
demos
to
showcase
stuff
off
people
like
it.
They
see
what's
useful,
they
can
give
feedback,
they
can
see
where
they
invest
it
all
around.
A
It
turns
out
to
be
well,
and
so,
if
you
want
to
schedule
a
demo
reach
out
to
Michelle
or
myself
and
we're
happy
to
help
get
that
going.
If
it'll
be
your
first
time,
you
need
a
little
help
with
that.
We
can
help
you
figure
out
how
to
do
that,
we're
more
than
happy
to
help
you
get
a
friendly
demo
on
the
calendar
and.
K
Don't
forget
to
that.
These
people
who
aren't
on
this
meeting
will
actually
go
back
and
watch
it
on
youtube.
So
it
gives
you
a
really
great
Avenue
to
get
the
word
out
about
your
projects,
because
there
I've
seen
some
of
the
things
people
are
working
on
just
know
in
their
spare
time
and
they're.
Absolutely
incredible,
so
I
would
love
to
see
some
of
those
great
things
see
the
light
of
day.
More
awesome
for
sure
you.
K
K
K
So
I
will
ask,
since
we
got
a
little
bit
of
time
here
out,
how
do
how
does
the
group
feel
about
the
connection
to
the
product
management
process
and
the
governance
process
overall?
Is
there
anybody
who
had
concerns
or
feelings
about
how
that
went
this
time
or
or
has
some
some
important
about
that
specifically
because
that's
something
that's
starting
to
emerge
at
the
community
level
and
I
would
love
to
hear
your
all
your
impressions
about
that
and
what
might
might
be
improved
you
you.
A
A
Maybe
I
owner
Jack
for
this.
How
many
has
anybody
had
interactions
with
the
governance
process
and
those
things?
Because
I
think
you
know
I'm
sitting
here
going
which
parts
of
the
governance
process
of
high
interacted
with
us
have
others
done
the
same
thing?
It
may
be
that
some
folks
here
haven't
interacted
with
it
or
realized
when
the
hands
yeah,
or
maybe
none
of
us
want
to
talk
much
today.
That.
I
K
Okay,
well,
if
anybody
thinks
of
any
things
that
you'd
like
to
add
to
this
will
make
sure
that
these
that
this
document
stays
available
and
alive
and
if
you
want
to
retro
actively
add
to
the
retro,
go
for
it
and
we'll
make
sure
that
gets
looked
at
by
sig
leadership
for
sure.
So
last
section
is:
what
are
we
planning
on
doing
differently?
These
are
specific
actionable
things
that
we
want
to
do
differently
for
the
1.7
release.
I
can
imagine
there
might
be
some
ideas
here.
K
N
I
L
I
A
Alright,
and
so
we
had
one
more
item
on
the
agenda
for
today,
and
that
was
a
light,
one
dot,
seven
planning
and
we
have
a
document
for
that
which
breaks
down
this
is
our
proposed
work,
so
let
me
drop
that
document
into
chat,
so
folks
can
pull
it
up.
I
can
even
share
it
just
a
moment.
A
Different
things
here
and
you'll
also
see
their
group
codes
and
I'll
hide
them
here
at
the
top
for
google,
Red
Hat,
chorus,
mirantis
and
day
is-
and
you
can
add
your
own
as
needed,
and
so
you'll
see
to
a
certain
extent
here,
like
under
state
full
set.
You'll
see
the
group
of
Google
and
Google
and
red
hat
codes
here.
I'm
in
here,
like
in
the
road
map
for
GF
Damon,
set
to
see
three
groups
are
coming
together
on
that
particular
one.
A
Some
of
the
stuff,
such
as
helm,
has
a
separate
roadmap
planning
and
I
didn't
know,
I,
don't
know
if
any
of
the
helm
filter
on
today.
If
they
wanted
to
what
the
plan
was,
can
probably
just
link
to
their
roadmap,
which
is
separate
and
you
can
engage
over
there.
Does
everyone
know
how
to
engage
with
the
helm
roadmap
process?
That's
run
mostly
separate
from
sig
absences.
They
do
come
through
here.
A
A
Drop
that
in
and
so
one
of
the
things
we
need
to
do,
and
so
we
can
probably
walk
through
this
I
think.
The
big
thing
is
that
we
all
start
get
going
on
filling
in
what
we
anticipate
for
cig,
apps,
one
dot,
seven
planning
and
I'm,
forgetting
when
is
one
dot,
seven
expected
to
come
out
forget
the
date
right
now.
I
And
I
just
like
to
add,
if,
like,
if
anyone's
ever
experienced,
that
they
sent
a
PR
or
proposal
it
didn't
get
reviewed.
Now
is
the
time
to
put
something
on
here
to
like
get
your
num.
You
know
get
in
line
for
that
process.
If
you
don't
put
something
on
here
and
then
you
show
up
with
a
PR
or
proposal
halfway
through
development
time,
you're
in
a
much
worse
shape,
in
my
opinion,
in
terms
of
getting
getting
it
in
and
feedback.
I
A
I
think
that's
a
great
point.
Well,
it's
fantastic
to
think
we
come
along
with
things
and
they
get
reviewed
as
they
come
in,
because
so
much
stuff
comes
through
Cooper,
Nettie's
and
all
of
the
projects
and
everyone's
so
busy.
But
this
layer
of
organization
really
helps,
and
so,
if
there's
something
you'd
like
to
chase
after
here
and
you'd
like
it
to
be
known
about
ahead
of
time
or
get
some
review
eyes
on
it,
actually
getting
it
in,
you
know
out
in
other
places.
This
is
a
fantastic
place
to
do
that
and.
I
I'll,
just
also
add,
like
I,
don't
see
this
to
being
a
firm
firm
commitment,
so
don't
hold
that
like,
if
you
think
you're
going
to
book
on
something
put
your
name
out
there
so
that
people
know
to
collaborate
with
you,
we
could
build
critical
mass,
don't
feel
like.
Oh
I
can't
put
it
there,
because
what,
if
I
don't
finish
it.
L
L
A
And
so
how
much
of
this
do
we
want
to
walk
through
today?
I'll
leave
it
up
to
the
group,
because
so
four
states
will
set
I
mean
that
that
one's
pretty
well
filled
out
and
Damon
said
are
there
for
stateful
set?
Is
there
anything
missing,
hear
that
folks
know
about.
A
A
You
alright,
then,
for
we've
got
cron
jobs.
We've
got
these
other
Cooper
Nettie's
core
elements,
improving
tpr
support
and
stable
pods,
which
have
been
proposed,
is
anyone
on
who
can
talk
about
those
going
to
see
a
bunch
of
this
fall's
am
NOT
the
Red
Hat
camp,
oh
cool!
Is
there
anyone
who
can
speak
at
ease,
I?
Think.
E
E
A
E
C
Good
time
I
think
the
PPR.
This
is
Marty
from
and
half
open,
sure
I
think
the
ours
will
be
handled
mostly
by
the
sig
Appy
machinery,
Odin
Thor
and
Odin
steps.
That's
probably
the
most
important
thing,
so
I
I
doubt
that
we
can
add.
I
hope
works,
any
support
of
that,
and
if
so,
then,
this
will
be
mostly
done
by
the
core
contributors
for
per
cube.
I
get.
C
So
that's
one
thing.
As
for
the
cron
jobs,
I
can
speak
since.
That's
part
of
this
is
dia
my
piece
of
cake
and
and
n
cube
to
initially
we
thought
that
we
will
be
able
to
graduate
cron
jobs
to
beta
in
1.6.
Unfortunately,
that
is
that
happen.
C
A
B
C
Yeah
I've
landed
already
in
1.6
kind
of
thing
with
that
is
that
it
I've
enabled
by
default.
You
need
to
explicitly
set
the
value
for
I.
Don't
remember
the
fields
name,
you
need
to
explicitly
set
the
fields
value
so
that
there
are
no
more
jobs
left
behind
by
the
con
job
after
in
the
drugs,
because,
if
you
don't
set
it
a
cron
jobs
can
create
a
unlimited
number
of
jobs
behind
okay.
C
C
A
So
we
can
handle,
we've
got
you've
got
a
rough
handle
on
that.
Don't
be
surprised
if
we
start
coming
around
asking
questions
on
it
again.
If
you've
got
some
more
of
those
details,
if
you
could
fill
them
in
as
bullet
points
that
might
help
some
of
the
folks
who
aren't
here,
who
start
coming
around
with
questions
again
to
to
not
come
bug.
You
started
asking
the
same
things
over
again,
so
yeah.
A
If
you
could
just
fill
those
in
I'm
sure
some
folks
would
appreciate
it
so
sure
oh
I'll
do
so
thank
you,
for
we
can
finish
off
with
the
Cooper
Nettie's
tooling,
some
of
this
stuff,
like
helm,
that
keeps
its
flow
documented
elsewhere.
App
controller
and
charts
have
figured
out
a
fair
amount
of
who's.
Doing
what?
Where
and
when
and
filled
that
in.
So
so,
thank
you
for
that.
So,
in
this
case,
I'll
jump
to
for
the
app
registry
I
see
in
one
dad.
A
P
Are
essentially
the
high-level
goals
for
that
time
frame
because
that
registry,
so
on
third
party,
don't
necessarily
tied
to
the
curb
earn
additional
a
strike
so
we're
basically
just
trying
to
make
what
we've
got
more
available
and
clip
into
ecosystem
and
through
that?
Obviously
we
need
to
move
from
Python
to
go
and.
P
P
C
A
O
A
Then
that
is
a
quick
go
at
one
dot:
seven
planning
for
anybody
who
we'll
have
details
I
think
they
can
add
later
this
week.
Please
come
back
to
this
document
and
feel
free
to
add
in
any
of
those
extra
details.
It'll
help
those
who
are
kind
of
trying
to
look
at
everything
holistically
and
have
a
high
level
picture
know.
What's
going
on
not
all
come
ask
the
same
questions,
but
you
know
that
some
of
us
need
to
do
this.
So
if
you
could,
it
would
be
appreciated
and
useful
and
helpful.
A
A
Okay,
well
then,
everyone
have
a
wonderful
week
and
remember
if
you
have
a
topic
you
want
discussed,
if
you
have
a
demo
that
you'd
like
to
share,
please
reach
out
to
Michelle
and
myself,
and
we
are
more
than
happy
to
help
get
the
topic
scheduling
in
so
we
have
space
for
it.
Otherwise,
everyone
have
a
wonderful
week.