►
From YouTube: Kubernetes WG Apply 20191001
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
Okay,
welcome
to
working
with
apply.
We
are
Tuesday
October,
1st
2019.
Let's
get
started
and
look
at
the
issues.
Maybe
I'm
gonna
open
these,
because,
let's
start
with
these,
because
we
don't
have
much
yeah
I
think
it'd
be
nice.
If
we
could
palma
try,
run
and
FSG
a
few
drills
in
117,
the
next
least
because
which
we
don't
have
many
problems
with
the
futures.
I
think
that
pretty
complete
now
so
that's
slow
quickly
at
what
needs
to
be
done.
A
A
People
wanted
it
I.
Remember
when
I
I
remember
when
I
did
the
feature
like
some
people
were
saying,
we
need
to
have
the
flag
on
every
single
command
and
some
other
people
were
like.
We
don't
need
to
do
a
lot
of
work
for
almost
nothing.
So
I
don't
have
a
strong
opinion
on
that.
The
trail
runs
support
in
client
go
I.
Does
it
mean
anything
I.
A
A
B
A
A
A
A
Okay,
let's
move
on
to
beta
to
Southside,
apply
okay,
so
we'd
use
fellow
the
number
of
allocations
improve
benchmarks
to
be
clear
soldier.
Okay,
I've
done
many
of
these.
We
have
many
many
many
of
these
now
I
think
the
situation
is
much
better.
We
have
a
much
better
understanding
also
found
that,
even
if
the
fieldset
is
very
small,
we
still
have
problems
so
I
think
that's
interesting.
I
have
I'm
working
these
days
on,
like
reducing
the
number
of
allocations.
I
have
some
very
good
results.
A
B
B
A
A
I'm,
probably
gonna
want
a
lot
of
the
dapi
machinery
people
to
look
at
it
anywhere,
so
it's
gonna
have
to
be
shot
extensively,
but
yeah
it'd
be
nice.
If
we
had
like
a
good,
maybe
even
an
example
of
like
how
do
we
sorry
dies,
a
specific
object.
It'd
be
nice
if
we
had
numbers
on
like
the
actual
reduction
on
some
of
the
golden
data
that
we
have
now.
B
B
A
A
A
A
A
B
A
B
B
A
B
A
Okay
theses:
this
isn't,
but
this
is
not
very
high
priority.
The
declarative
managed
field,
the
Whitfield
removal
I
think,
based
on
the
some
of
the
discussions.
I
had
a
lot
of
people
are
super
interested
in
having
mutability
and
union
as
soon
as
possible.
So
I'm
gonna,
keep
unions
and
immutability
here.
A
Yes,
that's:
okay,
okay,
and
we
need
to
revive
the
Union.
So
these
two
tasks
mostly
depend
on
the
on
this
first,
as
the
number
of
education
performed,
so
we'll
see
what
we
have,
people
that
are
working
on
it
at
the
same
time,
so
I
was
right,
we'll
see
how
it
goes,
Kevin
going
back
to
declarative
knowledge,
or
do
you
have
anything
to
say
about
that?
Yeah.
C
C
B
Yeah,
actually,
that's
fixed
by
the
PRI
have
out,
but
it's
not
merged,
so
I.
Don't
think
that
we
can
mark
it
as
fixed
it
I
just
fixed
it
by
accident,
when
I
was
doing
that's
a
factor.
C
B
C
A
C
A
C
Also
think
that
might
get
addressed
accidentally
when
I
read
the
security
stuff
for
us
that
there's
too
much
custom
stuff
with
Jason
and
Yama
going
on.
So
if
they
address
bad,
they
might
fix
it
because
then
the
problem
is
we
use
different
Jason
and
yellow
libraries
or
modified
libraries
and
that's
a
conflict.
So
my.
A
A
B
A
A
A
A
B
A
B
B
A
A
B
A
D
I
think
it's
a
couple
down.
It
says
something
like
ownership
is
not
yeah,
so
quick
update
on
this
one,
so
Hannah's
and
I
spent
some
time
working
on
this,
and
when
we
went
down
the
path
of
updating,
the
storage
should
go
file
which
is
under
each
main
resource.
So
we
started
with
replica
set,
for
example,
and
there's
a
bit
there.
Actually
that
looks
at
the
scales
of
resource
and
gets
the
replica
said
value
and
puts
it
back
on
them.