►
From YouTube: Kubernetes WG Apply 20190416
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
Let's
say
we
have
a
few
details:
we
need
to
be
careful
with
and
I
feel,
like.
That's
gonna
take
a
significant
amount
of
time,
more
than
I
expected,
maybe
and
I
think
we
need
to
change
strategy.
Okay,
I!
Guess
it
speed
up
working
right
well,
so
the
problem
is
that
Jenny
and
I.
We
can
spend
like
all
of
our
time
doing
that
and
I
give
up
on
everything
else.
A
B
A
How
because
yeah
I
mean
is
what
we've
seen
in
in
the
last
week
also
is
that
you
need
to
be
deeply
invested
in
it
and
it's
a
very
engage
and
it's
hard
to
do
anything.
At
the
same
time.
You
have
to
be
right
in
the
middle
of
the
thing
like
super,
okay
and
I
think
you
can
be
extremely
useful
by
doing
some
of
these
items.
So,
let's
go
through
them.
Yeah
the
low
setting
field
manager,
all
decked
out,
agree,
I
feel
like
you've
progress,
I
haven't
reviewed.
Your
latest
change,
yeah.
B
I
changed
torch
of
when
you
suggested
I
think
yeah.
The
only
thing
left
is
the
validation
part
which
I'm
still
not
sure
how
to
handle
it
still
in
invalidation
itself,
and
the
feed
mentor
is
using
it,
but
I
moved
parts
of
the
code
as
you
requested
and
yeah
now.
We
I
also
think
Jordan
about
the
cap,
but
he
didn't
respond.
Okay,
maybe
out
being
injured.
A
Let's
assume
that
this
is
gonna
be
done
before
the
end
of
the
spring,
though
yeah.
So
we
need
to
find
you
something
else.
On
top
of
that,
yep
design,
open,
API,
v3,
optional,
one
of
I
think
we've
done
a
ton
of
progress
on
that
I've
returned
it
under
under
pls
the
values
P
else
that
I
have
like
a
couple
of
times
many
times
there
are
still
other
things
to
be
done:
I'm,
definitely
hoping
everything's
gonna
be
wrapped
up
by
the
end
of
this
point.
A
A
B
A
A
C
Right
I
think
well,
we
need
to
decide
about
this
because,
like
you
said
not
all
of
the
skimmers
that
are
provided
in
B
3
are
going
to
be
convertible
to
B
and
we're
doing
something
out
and
we
could
use
the
service
schema,
but
it's
gonna
make
it
a
little
bit
unpredictable.
Someone
changes
their
skin.
That
is
something
that
is
no
longer
convertible
and
their
changes.
Okay,.
A
C
C
A
A
B
A
C
A
The
problem
with
this
one
is
that
when
you
send,
when
you
apply
with
the
status
at
the
very
end
of
the
process,
what
you
applied
in
the
status
is
gonna
be
stripped,
searched.
Ok,
it's
almost
in
LCDR,
and
so
it's
how
fast
you
know.
What's
gonna
happen.
We
don't
know
how,
when
we
let
you
saw
the
fields
when
we
track
the
fields
so
I
don't
know
exactly
how
we're
gonna
fix
this
one.
A
Maybe
we
could
do
a
strip
in
the
apply
code
that
that
would
work,
but
there
are
like
probably
bugs
hidden
behind
this
one
as
in
I.
Think
if
you
send
yeah,
if
you
send
something
on
the
status,
then
you
can
maybe
set
some
stuff
in
the
spec
and
you
shouldn't
be
able
to
do
that.
So
we
need
to
be
extremely
careful
with
this
one
I'm.
A
A
For
this
one,
yes,
but
okay,
one
of
the
poem
is
that
since
the
code
out
like
the
pieces
of
code
are
like
in
very
different
locations,
it's
kind
of
how
to
assume
that
we
can
do
that.
Okay,
right,
it's
like
if
the
code
change
whatever
somewhere
else,
then
it's
kind
of
being
consistent,
I'm,
not
super
excited
of
like
deciding
we're
going
to
strip
everything
in
the
set
us
out
in
the
process,
and
then
it's
going
to
actually
be
wiped
later.
A
A
Jenny,
do
you
remember
what
this
means
make
sure
built-in
types
are
you
we
don't
know
for
sure,
okay,
one
thing
that
could
be
useful
and
maybe
we
could
use
these
is
that
we
want
to
make
sure
that
no
objects
are
going
to
fail
to
be
updated
because
of
the
manage
fields
and
so
I
think
someone
has
to
go
over
all
the
types
and
see
I,
don't
know
how
we
can
do
that,
but
we
would
need
to
find
a
way
to
make
sure
that
all
the
types
can
be
encoded
successfully.
I.
A
You're
not
there
is
that
how
it's
built?
Yes,
magic,
okay,
okay,
cool
I,
think,
that's
it!
We
don't
have
much
to
say
or
do
we
don't
I
think
we're
on
time
well
slightly
late,
because
we
expected
these
tasks
to
be
done
by
now,
but
I
think
we
have
some
margin
of
error,
so
we
should
be
good,
but
we
should
definitely
have
the
five
first
ask
done
by
at
the
end
of
the
Sprint,
but
inside
that
which
we
will
must
the
entire.
We
have
the
scalability
issue,
which
is
probably
going
to
be
critical.