►
From YouTube: CNCF Kubernetes Conformance WG Meeting - 2018-03-08
Description
Join us for KubeCon + CloudNativeCon in Barcelona May 20 - 23, Shanghai June 24 - 26, and San Diego November 18 - 21! Learn more at https://kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy and all of the other CNCF-hosted projects.
A
A
B
D
B
E
To
make
sure
that
we
over
communicate
in
the
first
few
releases
work
informants
program,
is
getting
off
the
ground
and
we're
solidifying.
Those
communication
channels
is
that
there
have
been
three
conformance
tests
that
I
know
I've
added
to
one
ten
and
I
just
want
to
call
that
out
here.
So
one
in
the
workloads
API
there's
a
link
to
the
daemon
set
test
that
was
added.
E
So
in
one
8,
+
1
9,
there
were
no
changes
to
that
list
of
confronted
tests,
so
this
represents
the
first
set
of
new
tests
that
are
added
to
be
confronted
program,
and
so
I
just
want
to
call
out
that
we
have
exercised
that
process
and
both
in
workload
API
in
an
API
machinery.
There's
one
for
garbage
collection,
there's
another
PR
which
I
will
find
by
the
time.
This
call
was
over
or
watch,
and
my
suggestion
on
this
one
is
going
to
be
that
since
it
was
not
completed
earlier
and
didn't
get
the
milestone.
E
G
E
No
reason
that
I
know
of
is
more
about.
We.
We
need
a
sane
way
contract,
a
list
of
tests
against
which
the
cluster
is
being
verified,
and
there
may
be
some
reason
that
a
provider
or
a
distribution
or
a
platform
just
has
a
buzz
or
it
isn't
clear,
and
so
we
we
can't
be
shifting
the
definition
of
conformance
after
that
code,
freeze,
Jenna,
so
that
yeah,
so
that
that's
the
philosophy
behind
keeping
that
conformance
test
that
are
associated
with
that
version.
As
part
of
the
cutting
the
release
branch
for
that
version,
right.
G
C
I
think,
as
a
prerequisite
as
we're
starting
to
review
these
changes
going
in
when
we
add
new
conformance
tests,
they're
they're
new
for
a
specific
version,
there
already
exists
inside
the
ability
to
do
version
verification.
So
if
only
only
run
this
this
specific
conformance
test,
if
greater
than
or
equal
to
version
and
I
think
we
should
definitely
exercise
that
capability.
E
E
Think
that
super
useful
and
important
for
the
sanity
of
the
people,
who
are
maintaining
these
platforms
and
distributions,
but
for
the
purposes
of
conformance
what
would
be
the
outcome
if
you
we're
in
the
one
nine
conformance
test
against
one
seven
and
it
just
didn't,
run
some
of
those
tests
because
the
version
wasn't
greater
than
one?
Would
you
then
it'd
definitely
be
you.
C
You
would
not
have
a
mishmash
of
tests
like
so,
if
you
added
new
conformance
tests
and
maybe
something
got
promoted
to
v1,
then
you
you
would
fail
those
tests
in
a
1/7
cluster,
even
though
you
could
just
add
the
version
gate
check
as
part
of
the
test
and
skip,
if
not
very
so,
I
think
this
could
just
be
part
of
a
code
review
process
for
any
new
conformance
test.
I'm,
just
trying
to
call
it
out
here.
B
H
Yeah,
a
one
of
the
largest
consulting
firms
or
analyst
firms
just
said.
There's
a
draft
report
saying
so
you
can
just
become
a
leader
in
kubernetes
by
buying
a
platinum
board,
see
that
seems
yeah
right
and
that's
when
you
can
take
over
the
project.
Since
you
look
like
a
virgin
call
up
and
say
you
know
this
thing
committee
and
the
few
big
yeah
amazing
equals,
but
even
though
it's
out
of
order,
I
was
hoping
to
actually
just
give
an
update
on
this
conformance
test
process.
H
F
H
So
I
just
want
to
remind
everybody
for
context
that
we
started
talking
about
this
like
right
after
we
announced
the
program
in
September
and
specifically
wishes
on
from
NEC
cleared
out
that
we're
at
a
14
percent
acceptance
rates
on
really
desperate
and
so
I
proposed
a
governing
board
in
December
that
we
set
aside
money
in
2018
to
pay
an
external
development
company
to
to
improve
our
tests,
and
the
pushback
that
we
got
was
well
ease.
The
governing
board
signing
up
for
an
unlimited
liability
deal.
H
We
could
pace
away
for
a
test.
New
api's
are
going
to
go
mature
and
then
there's
going
to
be
more
testified,
and
so
we
then
went
to
sick
architecture
in
Austin
and
said
hey.
Could
we
have
a
new
rule
that
says
that,
in
order
for
api's
to
move
from
beta
to
stable,
they
need
to
know
who
the
conformance
answers,
and
there
was
a
discussion
in
the
back
and
forth
on
that
and
cig
architecture
promulgated.
H
A
new
rule
I
mean
which
is
really
like
one
book
a
couple
weeks
ago
and
then
I
was
able
to
bring
that
to
the
governing
board
Monday
and
get
sign-off
that
kid
petition
get
approval
for
this
budget
and
so
in
parallel
means.
Individuation
confirmed
globish.
That
Google
has
worked
with
in
the
past
on
external
test
development
and
so
I
just
signed
contract
and
they've
starting
and
just
a
ballpark
number.
The
truth
is
its
25k
per
month
for
two
developers,
plus
a
little
bit
of
parties,
management,
services
and
so
I'm
really
eager.
H
Now
that
we
do
whatever
we
can
to
support
them
on
getting
up
a
lead
in
the
end
begin
just
submit
pull
requests
into
suggesting
because
all
the
work
that
they
do
is
that
needs
to
come
through
the
regular
process.
And
so,
if
I'm
hoping
to
you,
know,
help
train
them
and
shape
that
and
can
make
sure
this
is
we're
showing
you
how
we're
going
to
hopefully
have
better
a
couple
months
being
a
lot
of
background
noise
continued.
But
after
a
couple
months,
we'll
begin
to
have
some
insight.
H
H
If
this
is
a
great
firm
to
use,
we
could
cancel
this
contract
with
a
30-day
termination
and
so
I
think
I,
don't
want
it
to
be
seen
as
oh
we're
just
you
know,
locked
into
300
days
a
year.
The
other
side
of
it
is
if
it's
going
extremely
well,
we
could
potentially
healthy
up
to
spend
rate
and
adding
a
third
or
fourth
person.
So
that's
the
overview.
H
C
One
of
the
agenda
items
from
last
meeting
if
I,
don't
recall
or
even
before
that
when
we
were
in
Austin,
was
to
get
like
a
apparent
issue
broken
down
in
the
main
repo
that
identified
the
areas
that
needed
coverage.
So
that
way,
it
wasn't
just
kind
of
ad
hoc,
but
we've
up
front
listed
down
the
key
concerning
areas
that
have
the
require
the
most
effort.
C
E
The
Google
side
has
a
bouncer
to
take
that
on,
and
part
of
that
is
to
essentially
shop
around
to
their
related
things
as
the
domain
experts
on
what
should
be,
in
conformance
for
those
the
components
owned
by
those
eggs
she's
in
New
York
this
week.
So
she's
not
on
this
I,
don't
think,
but
she
will
be
putting
that
together
in
the
coming
week.
I
think
okay.
A
I
F
J
Essentially,
I'm
trying
to
build
based
off
of
you
know
the
api's
that
we
have
list
of
all
the
api's
in
a
spreadsheet
form
and
then
against
that
say,
get
but
what
is
covered
and
what
of
the
existing
eating
eaters
in
one
column
and
then
what
is
currently
part
of
the
conformance
test?
Wait
so
that
we
can
leverage
and
say
this
is
the
area
like,
for
example,
our
back
is
not
covered
today
and
what
all
the
API
is.
There
are
four
or
five
IP
eyes
there
and
should
should
be
part
of
the
components.
J
Then
we
we
can.
We
can
use
a
spreadsheet
to
leverage
and
say
this
is
the
work
needs
to
be
done
right.
So
that's
that's.
What
I'm
heading
for
I
do
not
have
access
to
other
six
at
this
point
or
I'm
not
and
also
not
really
contacting
other
states,
but
that
would
be
great
if
I
get
information
from
them,
then
exactly
it
probably
much
faster
than.
C
Reading
through
the
code,
so
for
traceability
with
upstream
execution,
the
we
might
want
to
break
like
a
logistical
way
that
seems
tenable
would
be
to
break
down
by
API
group
and
have
a
tracking
issue
for
each
API
group.
And
then,
as
people
do
pr's,
the
PRS
can
reference
the
issue
and
then
we
can
close
out
the
issue
once
it's
completed,
but
I
think
the
spreadsheet
alone
won't
get
you
the
logistical
tracking
you
need
for
execution
against
upstream.
You
need
to
either
reference
the
spreadsheet
from
a
main
set
of
tracking
issues
on
upstream.
E
F
E
Likewise,
there
are
many
different
hash
operations
that
might
be,
and
those
combinations
may
be
more
important
in
certain
endpoints
than
to
get
to
certain
other
and
like
that
pod
template
API
is
one
that
is
rarely
used.
So
I
think
it
is
that
the
number
of
endpoints
that
are
hit
during
the
conformance
test
is
a
meaningful
metric,
but
it's
not
the
only
meaningful,
metric
and
I
think
the
prioritization
should
include
some
of
these
other
angles
as
well.
Yeah.
C
H
You
know
on
that
line,
particularly
for
Jago
and
Jim,
which
is
it
I
believe
in
Austin.
H
You
guys
are
Brian
mentioned
some
sort
of
rocket
science
work
that
was
going
on
where
there's
an
aspiration,
I
think
using
some
of
the
swagger
definitions
to
try
and
be
able
to
test
a
large
swath
of
the
api's,
at
least
at
a
service
dozen
wrote
relatively
quickly
and
I.
Just
could
you
remind
I'm
not
summarizing
that?
Well,
but
could
you
just
remind
us
what
that
thought
is
and
if
there's
an
issue
associated
with
it
and
then
is
it
possible
to
get
our
test
developers
focused
in
an
area
that's
far
away
from
that?
H
That
is
won't
be
covered.
Assuming
that
that
project
goes
forward.
E
Sure
I
think
that
was
me.
There
was
some
work.
Someone
on
my
team
was
working
on
essentially
a
thought
experiment
about
a
data-driven
test
to
explore
the
API
and
you
that
get
a
simplistic,
not
flaky,
but
not
entire,
not
testing
the
behavior,
but
rather
simply
testing
crud
operations
on
specific
resources,
and
it's
based
on
some
work
that
Eric
toon
did
previously
for
off.
That
would
seemed
valuable,
I
think
that
is
still
in
the
thought:
experiment
phase
and
not
in
the
plan
of
record
phase.
One
comment,
I
think
I
saw
recently
from
David
Yves
was
wow.
E
This
looks
like
a
nightmare
to
maintain
anything
that
has
a
comment
like
that
from
someone.
Thoughtful
is
a
concern.
So
yes,
but
the
intention
is,
is
there
a
non
flaky
repeatable
way
to
verify
that
endpoints
are
exposed
that
may
be
necessary,
but
not
sufficient
to
demonstrate
that
a
cluster
is
implementing
the
desired
behavior
of
the
end
user
and
I
will
drop
the
link
to
that
work
in
progress
in
the
notes
from
today,
as
well.
I.
H
E
B
C
E
D
J
E
Added
one
more
in
fact
been
the
elder
is
here
and
can
give
this
update.
I
just
wanted
to
share.
There
is
a
document
process
published
on
computing,
conformance
test
back
to
test
grid,
which
may
be
useful
for
other
folks
to
be
running
their
own
CI
running
the
conformance
test
and
posting
those
results
back
to
tested
to
raise
the
visibility
that
there's
some
breaking
change
earlier
in
the
process
that
is
Yoanna.
I
Well,
I
took
nama
care
out
soon.
It
pretty
much
followed
that
doc
I
was
told
right
now.
It's
a
Python
script,
but
I'm
open
to
porting
it
to
whatever
works
best
for
everyone.
Pretty
much
just
takes
the
standard
e
to
e
log
and
J
unit
output
and
prepares
it
for
test
written
test.
It
means
a
little
bit
more
metadata
than
know
when
a
job
is
from
something
like
that.
E
E
It
will
give
us
the
ability
to
have
a
single
dashboard
with
multiple
cloud
providers,
and
so,
if
we,
for
example,
add
a
new
conformance
tests
or
add
a
new
feature
and
it
breaks
other
cloud
providers
likely.
An
engineer
working
in
one
group
is
not
likely
to
be
testing
across
every
single
cloud
provider
or
distribution.
And
so
that's
the
intention.
D
So
straining
and
that's
where
the
second
seer
PR,
whether
it's
in
merging
up
but
assuring
the
PR
out
there
to
have
a
some
documentation
to
communities
about
how
to
add.
Instead,
some
of
expectations
are
in
terms
of
documentation
stuff,
like
that
I
think
it'd
be
useful,
then,
to
point
to
this
documents
from
that.
That's
that's.
D
D
D
H
I
had
to
drop
off
in
two
minutes,
I'm
at
the
open
source,
Leadership
Summit,
but
is
there
anything
else
that
I
could
do
for
you
or
answer?
I
mean
I'm
very
excited
to
start
this
work
and
really
looking
to
this
group
and
suggestions
to
make
sure
that
it
makes
sense
on
the
right
track
and
if
it's
not
attracted
to
I
had.
C
H
B
B
I
think
there's
a
deep
dive.
We
can
just
do
like
a
regular
meeting
or
it's
just
like
one
of
these
and
then
the
intro
is
kind
of
more
aimed
at
people
that
have
never
heard
of
committees,
so
actually
the
arrangement
which
actually
developed
I'd
love
to
develop
that
program
together
it
like.
If,
if
we
want
to
share
the
share
the
talk,
we
tell
a
bunch
of
different
people,
maybe
getting
up
and
sharing
their
experiences.
B
D
F
D
E
E
J
Generate
about
seven
pr's,
there
are
all
consecutive
numbers
I
can
I
can
show
one
of
the
thanks
to
came.
He
interviewed
one
of
them,
but
all
these
PRS
are
basically
strengthening
the
documentation
for
the
test.
Actually,
what
using
the
RFC
two
one
online
format.
Basically,
what
shouldn't
happen
in
covenant
is
when
you
run
this
test
and
give
description
of
what
des
does
and
also
we
added
release
information
into
the
test
metadata.
C
It's
in
my
pot
club
to
go
through
it.
The
problem
I've
been
having
right
now
is:
we
are
in
lockdown
for
the
end
of
the
release,
and
so
at
the
end
of
every
release
cycle
is
a
exercise
in
firefighting
and
I've
been
doing
firefighting
duty
for
the
last
couple
of
days
trying
to
track
down
a
couple
of
tests,
blockers
that
have
occurred
for
different
areas.
So
it's
on
the
backlog,
but
it's
just
not
the
highest
priority
right
now.
Absolutely.
J
B
B
Okay,
well
we'll
set
out
a
list
of
action
items
off
this
meeting
particularly
check
out
there.
The
dog
from
then
about
contribute
test
grade,
looks
like
a
spree
double.
Maybe
we
send
out
an
email
deliver
and
we've
got
only
few
concessions
for
the
unconference.
Do
we
need
to
actually
do
anything
for
that?
Or
can
we
just
do
we
just
propose
that
on
the
day,
no.
F
No
I've
submitted
something
so
we'll
see
if
it
gets
accepted,
but
what
what
help
me
is
you
know
to
wanting
to
be
involved
to
participate,
that
we
can
take
that
subgroup
and
all
work
together
to
put
on
something
that
will
be
productive,
so
I
I
heard
some
name.
Besides
myself
participate
there,
so
we
get
those
names
William.
Then
we
can
have
this.
You
know
sort
of
a
sub
meeting.