►
From YouTube: Kubernetes WG Apply 20191126
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
C
C
A
A
A
D
B
E
B
Figure
I'm
worried
about
the
we
should,
if
we
think
we're
not
gonna
focus
on
crunching
the
size
like
it
was
a
10%
growth,
like
maybe
I,
don't
know
we
still
probably
would
need
to
figure
out
but
we're,
especially
in
terms
of
proto
or
closer
to
2x
the
object
size,
yeah
yeah
yeah,
because
it
because
it
stores
that
field
names
mostly.
Yes,.
B
A
B
B
B
A
B
F
B
Jenny
and
Europe
and
tag
teaming,
I
think
Joe's
out
this
week,
so
jenny
was
taking
over.
Yes,
basically
implement
the
interface
with
the
reflect
so
that
it
works
in
arbitrary
objects
and,
depending
on
how
that
goes,
we
may
have
to
follow
it
up
with
generating
things
for
the
Tilton
objects.
I
hope
we
don't
have
to
go
there,
but
maybe
move
I
think
I
think
we
should
be
okay
with
the
reflect
based
interface
like
I,
think
it
should
still
be
a
drastic
improvement
over
actually
copying
everything
yeah.
A
Want
to
scoot
yugioh
for
just
one
minute:
this
is
the
beginning
of
the
cycle
muscly
and
we
have
Daniel
so
that's
kind
of
interesting.
What
is
we
have
cupca
relief
and
dry
run,
which
help
us
better
and
we
well
wandering
meat
cycle
less
cycle.
If
we
wanted
to
make
these
GA
yeah.
A
A
A
F
B
That
seems
like
additional
features
that
I
guess.
The
question
is:
are
you
talking
about
the
the
the
the
user
experience
as
a
whole,
or
are
you
talking
about
the
API
server
feature?
If
you're
talking
about
the
API
server
feature,
then
yeah
just
stamp
the
G
and
you're
done
if
you're
talking
about
the
user
experience
as
a
whole,
that
does
sound
kind
of
useful
I.
A
So
we
have
to
do
these:
okay,
cool
yeah,
I,
guess
yeah!
If
you
want
to
call
the
user
experience,
GA
dave
has
nothing
to
be
done.
Okay,
but
it
depends
on
dry
run,
so,
okay
yeah!
So
let's
train
mega.
Let's
make
this
a
goal
for
these.
Ladies
to
make
sure
I
run
and
cook
kernel,
defesa
GA,
yeah
I,
don't.
B
A
A
B
C
A
So
this
is
not
gonna
be
easy,
because
a
lot
of
people
do
keep
current
create.
You
know
how
create
has
these
flags
to
populate
the
object
and
they
do
a
dry
run
and
it
shows
only
the
fields
that
they
want.
If
you
do,
a
Southside
dry
run,
it's
gonna
default
everything
which
is
probably
not
what
people
want,
because
people
do
a
compare,
create
die
clean
through
that
yellow
file
that
they're
going
to
come
in.
D
B
F
F
B
A
C
B
A
A
F
F
B
E
F
A
A
B
D
A
Documentation
I
know
okay,
so
we
have
a
ton
of
things
to
fix
in
the
documentation
Church
where
we
could
do
something
on
these.
But
most
of
these
are
like
inside
one
of
the
big
issue
that
Maria
has
that's
kind
of
messy.
We
have
another
umbrella
insurer,
which
is
about
all
the
things
that
we
want
to
do
if
your
builder
for
the
new
types,
the
least
obstructive
map
type
all
of
these-
and
so
Maria
is
kind
of
looking
into
this
area.
B
D
B
A
C
A
F
Didn't
we
didn't
realize
it
was
hard
when,
when
you
know
we
discussed
something
in
the
last
meeting
and
or
in
the
meeting
before
and
opted
for
doing
the
whole
object
to
internal
and
then
doing
a
fieldset
and
checking
it
feels
changed
so
resetting
and
checking
and
then
even
suggest
something
new
before
cube
con?
Oh
yeah,
you
discussed
it
rolling
in
slack,
but
I
wasn't
sure
which
way
to
go
now
and
I
wanted
to
discuss
it
before
I
start.
A
A
F
A
F
B
B
F
Okay,
yeah
and
one
thing
I
saw,
is
or
I
already
used
this
from
storage.
You
can
only
get
like
get
create.
Storage.
You
get
update
strategy,
create
update
strategy.
Is
it
safe
to
use
one
because
when
installing
the
handler,
you
kind
of
know
or
there's
no
way
to
find
out
which
strategy
to
use
so
they
all
aren't
the
same,
but
is
it
safe
to
use
one
of
them?
I.
A
F
F
F
F
B
So,
where
all
the
strategy
interfaces
are
defined,
we
could
add
a
new
interface
field
field,
clear
info.
If
ratna
do
something
like
that,
and
then
you
see,
if
the
like,
it
doesn't
shouldn't
matter
which
handler
you
you,
which
strategy
you
get
you
test
it
to
see.
If
it
can
be
the
other
interface,
and
then
you
use
that
and
then
it's
the
collars
responsibility
to
make
sure
that
both
objects
give
you
the
same
function
and
in
fact
that's
how
it
worked
by
default
for
all
the
existing
ones,
since
they
reuse
the
same
object
for
both
right.
B
The
way,
the
way,
the
reason
why
there's
separate
create
and
update
strategies,
the
idea
is,
you
write
one
strategy
object
and
then
you
implement
the
corresponding
methods,
and
if
you
implement
something
for
that,
if
you
implement
the
create
interface,
then
we
give
you
a
post
verb.
If
you
implement
the
update
interface,
then
we
give
you
a
book
right.
So
it's
the
same
object
either
way.
B
F
A
Yeah
again,
we
can
set
up
a
meeting
if
you
want
us,
Jenny
and
I
to
look
at
it
with
you
and
you'll
get
the
way
like
we
do.
There
I
think
this
was
super
useful,
yeah,
okay,
I
think
we
have
a
fixed
fella.
The
other
issue
that
I'm
always
confused
with
is
the
replica
on
the
scale,
services
and
I
think
we
have
I
can't
remember
what
we
decided
on
this
one.