►
From YouTube: Kubernetes WG Apply 20180424
Description
For more information on our meetings check: https://github.com/kubernetes/community/tree/master/wg-apply
C
B
D
A
E
I
think:
okay,
let's
let's
go
through
this.
A
D
A
A
E
C
C
C
A
D
A
A
F
D
E
E
E
A
D
I
was
curious.
Are
we
agreed
that
we
want
to
have
a
simple
path
through
all
the
way
through
the
you
know
and
then
to
be
able
to
basically
just
put
something
to
start
off
with
basically
and
then
the
way
we
mentioned
that
we
wanted,
I
had
mentioned
a
strategy
to
get
be
simple
in
and
apply
working
and
then
iterate
on
it.
Okay,
literally
think
about
that
and
I.
A
D
A
A
A
B
A
A
I
added
to
the
API
machinery,
sig
meeting
an
entry
or
a
line
item
tomorrow
about
open
API,
there's
some
hesitancy
to
incorporate
it
more
widely
through
the
server
snare,
so
I
mean
I'm,
not
in
love
with
open.
Api
is
just
the
thing
that
we
have
and
we
need
some
time
with
understand:
yeah
either.
Basically,
our.
A
E
A
Would
be
nice
to
have
one
schema
used
for
everything
everywhere,
rather
than
making
everybody
here
rewrite
the
functionality
for
two
different
sources?
So
if
we
can
make
it
work-
and
we
should
probably
investigate
Union
tags
sooner
rather
than
later,
if
we
can
make
it
work,
I'd
rather
just
use
open,
okay,
everywhere,
I,
don't
care
about
the
operations
actually,
because
over
the
open,
API
has
both
operations.
The
data
model
you.
A
F
A
A
B
Well,
well,
there's
a
few
things:
one
would
be
greatest
open.
Ep
I
was
able
to
recite
the
validation
was
able
to
handle
things
like
string
length
and
min
Max
on
things.
You
know,
because
there
are
such
limitations
on
many
resources,
so
it
would
be
great
to
have
that,
but
just
in
general
didn't
oh
I.
A
Have
thoughts
on
that
which
is
basically
there's
two
kinds
of
validation:
there's
kinds
that
you
can
declare
statically
and
those
kinds
of
you
need
a
program.
You
need
to
write
a
program,
all
right,
I
think.
Eventually
we
want
to
do
the
static
kind
declaratively
to
free
up
programmers
from
having
to
write
validation
for
that
and
to
make
it
more
consistent.
So
eventually
like
string,
length
and
and
min/max
those
are
and
also
I
think
maybe
like
matcha
regex
I,
think
those
are
in
scope,
eventually
yeah,
but
we've
got
a
like
right
now.
A
B
A
B
We
do,
but
if
you
try
to
create
an
object
like
this
I'm
coming
in
from
like
the
customer
resources,
you
know
point
of
view
where,
if
we
created
some
of
these
objects
we
would,
you
would
be
warned
probably
a
normal
kubernetes
primitives,
that
you
can't
have
something
more
than
62
characters
long,
but
we
can't
have
that
sort
of
validation
right
now.
So.
H
B
This
argument
I
mean
yes,
it'd,
be
even
better
if
it
had
even
better
validation
than
that,
but
that
was
just
what
was
driving.
That
was
a
little
bit
about
open,
API
I
believe
has
such
such
an
ability
to
express
limits
and
stuff
like
that,
but
our
open,
API
Jen
doesn't
doesn't
understand.
Oh,
we
don't
have
any
annotations
for
that.
That
would
then
be
able
to
do
that,
so
that
I
think
we
could
probably
add
that
yeah.
A
I
think
it's
definitely
in
scope
eventually,
like
me,
maybe
maybe
not
for
well
I,
mean
I,
definitely
think
adding
validation.
We
want
to
add
validation
for
like
list
keys,
and
once
we
have
the
path
that
goes
from
spec
develop,
it
should
be
pretty
trivial
to
add
that
kind
of
validation,
though
I,
wouldn't
necessarily
say
that,
like
adding
string,
length,
validation
is
part
of
the
apply,
but
the
thing
that
we
we
have
to
like
solve
all
the
prerequisites
for
that
anyway.
So
write
another
thought
I
had
when
hearing
you
talk
was
we
want.
A
I
would
like
all
of
our
egg
has
to
be
consistent
and
the
way
you
reduce
an
API
should
be
like
somewhat
consistent
like
if
you
learn
how
to
make
a
C
or
D
some
of
that
knowledge
to
transfer
over
to
build
an
API.
So
for
that
reason,
I
would
like
our
are
like
separate
stacks
converging
and
just
give
people.
A
B
In
and
then
along
with
that,
there's
the
comment
that
just
trying
to
go
through
the
process
of
learning,
how
to
create
your
own
custom
resources
or
controllers,
or
whatever
this
API,
that
the
API
validation
thing
is
not
really
well
documented.
You
know
their
site
and
that's
just
probably
just
a
growing
pain
yeah,
and
it's
also
not
clear,
like
should
I
use,
open,
API,
gender,
so
I
use
that
update
code,
gen
script
or
whatever.
B
You
know,
because
is
the
that
you
can
build
a
open,
API,
gen
binary,
you
know
through
go
or
you
can
use
that
the
scripts,
just
like
some
sort
of
guide
for
people
I
think
would
really
be
helpful.
You
know
because
basically
I'm
just
looking
at
other
people's
code
and
going
oh
yeah.
This
is
how
I
this
is
how
this
person
did
it,
which
is,
of
course
different
than
how
the
next
person
did
it
and
we
I
don't
want
to
use
the
term
best
practices,
but
maybe
intended
practices.
B
Well,
if
we
tell
people
hey,
we
created
this
open,
API,
gen,
binary
or
say
a
command
that
can
then
create
this
stuff
for
you,
which
you
can
then
stuffed
into
your
C
Rd
validation
area
at
least,
then
people
understand
like
why
it
exists
where
you
can
use
it
and
and
and
they
can
hopefully
kind
of,
we
can
all
kind
of
agree
to
kind
of
go
about
the
same
approach.
So.
B
There
is
like
that,
so
you
know:
building
your
own
custom
resource
stuff
was
kind
of
an
interesting
thing,
because
even
the
kunais
guide
and
I
believe,
even
though
the
sample
controller
says
take
a
look
at
this
blog
article
for
more
documentation,
which
probably
isn't
a
great
idea.
I
mean
not
just
because
it's
a
blog
article
on
some
other
website
and
shouldn't
be
within
the
kubernetes
documentation
itself.
But.
A
A
A
B
D
Called
coop
builder
that
Phil
would
Rock
the
steering
committee
has
created
and
I
was
just
in
in
talks
with
him
about
this
min
max
validation
automatically
being
generated
through
this
coop
builder
tool.
It
hasn't
happened
yet,
which
you
know
that
doesn't
help
you,
but
at
least
I
think
there's
a
path
to
to
have.
You
know
you
using
these
automated
tools
to
to
get
this
more
significant
validation
available
for
the
CRTs
that
are
generated
through
crew
builder
yeah.
H
A
A
B
E
A
A
A
D
C
H
A
D
H
A
H
D
A
At
least
I
mean
to
be
incredibly
technical.
We
don't
need
any
of
that
to
give
a
simple
path.
Working
like
we
have
emerging
where
that
works
right
now
it
just
doesn't.
Yasim
news
doesn't
have
features,
so
we're
actually
blocked
on
this
patch
handler
stuff,
so
but
I
think
I
think
we
should
view
the
like
tool
chain
as
its
own
like
product,
it's
unlivable,
so
I
think
it
makes
sense
to
filled
out
the
total
change
in
parallel
with
the
rest
of
the
stack
I
mean.