►
From YouTube: Kubernetes SIG Apps 20191007
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
A
B
Sure,
hey
I'd
known
and
everybody
else
so
I'm
Cheryl
I
am
director
of
ecosystem
at
the
cloud
native
computing,
Foundation
and
I
run
the
CN
CF
end
user
community
and
there's
been
a
couple
of
requests
to
learn
more
about
application.
Cr
DS,
so
I
was
hoping
that
somebody
from
cig
applications
would
like
to
present
to
the
CN
CF
end
user
community
and
take
some
questions
and
answers.
So
these
cores
run
every
two
weeks
and
October
17th
would
be
the
next
one
or
it
would
be
November.
B
C
B
The
call
is
9:00
to
10:00
a.m.
Pacific
time:
okay,
okay,
Thursday
Thursday.
B
D
Everybody
hear
me
yep,
awesome
I
just
want
to
introduce
myself
I'm
one
of
the
release,
lead
shadows
for
117
and
I
wanted
to
go
over
a
couple
of
the
key
dates,
really
quick.
We
are
three
weeks
into
the
release
schedule.
Starting
today,
the
release
117
started
Monday
September
23rd
enhancements
freeze
is
next
Thursday.
D
Next
Tuesday,
so
October
2000,
October
15th,
is
when
enhancements,
freeze
and
all
their
caps
need
to
be
in
code.
Freeze
is
November
14th
and
hopefully,
117
will
be
released
on
December
9th.
This
is
a
shorter
release
than
normal
by
like
a
week,
because
we
wanted
to
try
and
get
everything
in
and
done
before
the
holidays
and
also
with
cube
con
in
the
middle
there.
It's
kind
of
hectic,
so
we
hope
everyone
understands
and
make
sure
those
dates
are
marked.
A
E
C
E
A
A
C
C
My
thought
on
it
is
actually
sort
of
probably
not
so
like.
If
you,
the
one
thing
about
the
Alpha
feature,
gate
is:
if
we
choose
to
remove
it
from
the
API
later,
there's
no
way
that
you
can
have
that
field
enabled
in
your
API
between
versions,
but
it
the
way
the
field
is
being
set.
It's
gonna
go
on
to
a
v1
object
anyway.
E
Yeah
I
know
I've
seen
some
issues
and
rants
about
it.
I
figured
what
was
the
correct
way
to
do
it.
I
would
have
to
look
into
it
because
I
know.
Jordan
has
some
comments
about
like
some
backwards
compatibility
with
regards
to
serializing
the
API
and
stuff.
It
was
a
long
time
ago,
recommendations
we
have
for
that
I
think
they
were
trying
to
change
the
community
dog
around
API
conventions
or
something
do
it
like
that.
Last
time,.
C
Well
so
four
features
that
are
like
behavior
change
is
alpha
feature
gates
or
a
thing,
and
then
for
API
is
that
you're
going
to
release
that
our
new
api's
alpha
gates
are
a
thing
for
a
modification
to
an
existing
API
which
is
basically
backward
compatible
unless
you
enable
it
I,
don't
think
there's
any
direct
guidance,
or
at
least
I
wasn't
able
to
find
any.
But
maybe
I
can
look
a
little
bit
harder
and
see
if
they've
updated
the
guidelines
for
API
modification
to
handle
that
specific
case
I'm.
Just
not
aware
of
there.
C
Let
me
so
I'm
not
opposed
to
doing
the
Appy
either.
Like
I
said
like
to
me.
It
looks
like
this
right.
If
we
do
so,
if
we're
not
confident
that
we
did
this
the
right
way
to
do
it,
then
we
should
probably
think
harder
about
doing
it
at
all,
because,
rather
than
releasing
like
a
V
to
the
API,
which
is
I
guess
the
least
risky
way
to
have
features,
we're
going
to
add
it
in
about
backward
compatible
way
to
a
v1
API,
which
is
slightly
more
risky
in
terms
of
like.