►
From YouTube: Kubernetes WG Apply 20181204
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
C
B
A
D
E
B
B
D
Not
tested,
we
gotta
figure
out
something
about
that.
According
about
that
looks
really
bad
yeah.
Anybody.
D
D
B
B
B
D
D
B
B
C
D
D
B
D
B
Okay,
good
given
needs
from
my
stuff
I'm
going
to
each
line
rows
because
it
says,
fix
the
API
I
think
we
already
have
items
for
yeah.
B
D
D
D
F
D
B
So
the
good
thing
is
that
we
have
two
paths
right
now
we
have
the
apply
pass
and
another
glide
path,
so
the
applied
path
should
fade
on
else
and
the
other
one
sugar
right
for
the
non
flight
path
which
on
the
objectives
was
given
in
input.
We
just
changed
the
manage
wheels
yeah.
We
just
need
to
be
careful,
not
changing.
If
we
have
any
air
which
might
be
slightly
problematic,
but.
B
F
F
F
D
B
D
F
B
F
F
D
B
So
I
guess
the
questioning
is:
when
we
do
the
update.
Do
we
use
the
old
object,
manage
fields
of
the
new
object,
manage
fields,
that's
kind
of
the
question
right,
the
one
from
the
old
object
or
the
one
from
the
new
object.
If
they
rested,
yeah
yeah
must
type
most
of
the
time.
I
would
expect
they
don't
that
if
the
person's
updated
it's
gonna
be
in
the
new
one,
not
in
the
old
one,
yeah.
E
D
E
D
D
B
You
seen
cute
back
up.
No,
you
back
up
extract
the
object
from
from
NTD
yeah
to
do
back
up,
not
permit
you
directly.
Bobby
doesn't
watch
others
a
get
away
five
minutes
and
then,
if
you
want
to
bank
any
packs
of
key
objects
right
and
then
he
suggests
that
you
can
apply
them.
To
least
all
this
data
right,
no.
F
D
D
E
D
Other
the
other
option
is
so
so,
but
if
you
want
to,
let
them
update
anything
in
the
same
request,
which
I
guess
is
a
reasonable
position
and,
like
you
were
saying,
you
need
to
decide
whether
you
use
the
old
or
the
new
manage
fields
just
use
the
new
all
the
time.
I
think
you
have
to
use
the
new
otherwise
you're,
effectively
over
writing
and
ignoring
whatever
they're
doing
yeah.