►
From YouTube: CNCF Kubernetes Conformance WG - 2018-06-14
Description
Join us for Kubernetes Forums Seoul, Sydney, Bengaluru and Delhi - learn more at kubecon.io
Don't miss KubeCon + CloudNativeCon 2020 events in Amsterdam March 30 - April 2, Shanghai July 28-30 and Boston November 17-20! Learn more at kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects
A
Okay,
so
we're
winging
it
today.
I
will.
A
B
A
Seems
like
this
might
be
a
quick
one.
One
I
know
top
of
my
head.
There
was
a
watch
conformance
test
added,
an
API
machinery
that
one
is
particularly
interesting
and
I
will
send
a
note
if
I
can't
pull
it
up
quickly
here,
but
that
is
essentially
to
ensure
that
the
watch
asynchronous
watch
works
in
in
the
conformance
test
suite
and
are
there
others
that
went
in
in
the
last
couple
few
weeks.
A
A
C
D
A
B
D
D
A
D
Alright
I
is
just
actually
updating
this
live.
So
thanks
for
that
she's
at
a
conference
internal
to
Google
and
then
so
they
get
lots
of
watch
tests,
though
Rabbid
I'm
there's
a
PR
for
that
it's
on
slide
2.
It's
also
I'm,
so
aggravated
test
where
they're
waiting
for
some
review
there,
but
they're
in
scope
for
1:12
and
there's
a
conformance
guidance,
PR
I'm
almost
ready
and
the
link
is
there
on
that
slide
on
slide
slide
3.
D
There
was
two
main
groups
that
I
think
she
was
working
with
a
bi
machinery
and
the
note
with
napi
machinery.
This
is
the
list
of
the
edu
tests
that
they
were
able
to
promote.
They've
also
got
a
tracker
sheet
for
that.
She's
gonna
be
working
with
see
Bender's,
particular
to
make
sure
the
flakiness
improves
and
they're,
not
skipping
particular
providers
and
they're
about
to
do
some
promote
these
cases
via
PRS
for
API
machinery
sig
before
looping,
in
with
Sagarika
tech,
chure
is
actually
editing
the
slide
so
that,
hopefully
it's
getting
there.
D
D
4
she's
been
working
with
us
to
correlate
the
ete
test
to
the
api,
calls
that
they
make
it's
helping,
particularly
in
cig
note,
to
be
able
to
see
which
endpoints
are
already
covered,
but
the
tests
are
promoted,
we're
looking
to
try
to
provide
a
matrix
for
each
of
the
end
points
to
all
of
the
tests.
We
have
an
initial
dump
right
now
inside
ete
correlate
and
see
if
I
can
drop
that
into
the
chat,
real
quick.
D
D
Where
is
also
working
closely
with
the
globe
on
vendors
to
understand
what
they're
doing,
particularly
at
how
different
API
and
verb
combinations
are
being
exercised
and
ended?
Moving
a
bit
into
the
pod
API
spec,
that's
a
little
bit
different
than
just
the
ete
test,
and
so
we're
digging
in
a
bit
further
to
see
how
we
can
include
that
in
API
snoop
as
well
to
see
which
of
those
are
worth
promoting,
I'm
still
a
bit
unsure
how
we
look
at
ete,
test
and
conformance
with
regards
to
pot
API
spec.
D
But
the
initial
findings
are
are
in
a
link
here
and
I'll
drop
that
in
the
channel.
I
think
this
is
they
have
to
request
permission
for
that
one
and
for
next
steps.
They're
gonna
do
an
API
analysis
for
the
API
verb
combination
and
take
the
results
to
signo,
we'll
be
doing
something
similar
within
API
snoop,
going
beyond
just
the
simple
dump
of
the
correlate
we
have
and
hopefully
to
give
them
something
on
the
web.
That
looks
nice
with
an
API
snoop
we've
got
a
couple
of
open
tickets
and
it
might
be
of
interest.
D
I'm
gonna
drop
the
our
issues
link
and
here
one
of
the
things
we're
looking
into
right
now
is
trying
to
augment
client
go
so
that
every
time
any
application
uses
client
go
to
connect
that
we
could
somehow
correlate
that
call
to
an
entry
in
the
audit
log
which
provide
some
really
interesting
data
to
analyze
for
all
applications.
Instead
of
we
are
currently
working
to
do
it
within
just
within
the
edu
test
space.
D
And
it's
it's
been
some
interesting
interesting
things.
We
also
updated
the
API
snoop.
So
if
you
look
at
API
snoop
CN
CF,
dot,
IO,
it's
it's
working,
but
it's
kind
of
a
mock-up
of
where
we
think
things
should
go
in
the
future.
I'll
drop
that
link
as
well.
D
D
When
you
see
a
particular
API
call
being
able
to
click
on
it
and
seeing
all
the
eee
tests
that
hit,
that
particular
API
call,
and
possibly
all
the
applications
at
some
point,
including
all
of
the
data
that
flows
through
it,
so
we
can
get
a
better
visualization,
for
you
know
how
we're
using
our
API
there's
also
been
some
work
on
the
capture
to
make
that
easier.
I
think
that's
another
ticket
where
we
were
looking
at.
D
Yes,
using
admission
web
hooks
as
an
alternative
to
audit
locks.
Yes,
audit
logs
are
where
we
will
go
and
be
long-term,
and
there
is
that
kept
if
you
haven't
seen
it
to
add
support
for
audit
logs
to
be
added
dynamically,
but
right
now
this
might
be
useful
to
get
us
a
good
way
there.
As
far
as
the
the
call
itself,
we
won't
get
the
results.
We
won't
get
some
of
the
other
data.