►
From YouTube: Kubernetes SIG Testing - 2020-12-15
Description
A
Let's,
let's,
let's
roll
back
hello,
everyone!
This
is
the
kubernetes
testing
community
meeting.
My
name
is
benjamin
elder
I'll,
be
hosting
today.
One
of
the
sig
leads
today
is
december.
15
2020.
A
This
meeting
will
be
recorded
and
posted
to
youtube,
and
this
meeting
is
under
the
cncf
code
of
conduct,
the
very
tourist
version
of
this.
It
is
excellent
to
each
other.
Thank
you
all
and
we'll
lead
with
matt.
B
All
right,
I'm
matt,
foley
I've
got
a
fair
bit
of
experience
in
the
pantry
groups,
but
have
not
participated
in
the
cncf
group
before
so.
I'm
glad
to
be
here,
I'm
very
interested
in
integration.
Testing
specifically,
it
seems
like
there
isn't
a
lot
of
prior
art
on
standardizing
integration
test
frameworks.
B
I'd
be
very
grateful
for
pointers
that
people
have
to
to
prior
work
there,
but
also
I'm
interested
in
seeing
if
we
can
get
some
some
thorough
integration
testing
of
kubernetes
stacks
available
in
under
under
the
edges
of
this
sig.
A
A
Given
that
almost
everything
bounces
through
the
api
server,
we
do
have
some
tests
that
we
call
integration
in
the
main
repo
that
are
like
component
plus
api
server
plus
ncd,
but
those
are
actually
actually
bash
for
reasons
I
think
I
think
it'd
be.
It
would
be
good
to
explore.
A
You
might
find
a
little
bit
of
friction
and
things
like
getting
adoption,
like
I
said,
like
we've,
had
some
efforts
in
the
long
past,
but
I
think
they've
most
submitting
word
because
developers
have
found
it.
You
know
for
many
components
more
viable
to
just
take
the
integration
test
framework
and
write
one.
There.
B
By
the
way,
I
have
a
hearing
impairment
so
I'll
sometimes
ask
people
to
repeat-
and
I
didn't
catch
that
last
bit
say
again.
A
I
think
I
was
saying
something
along
the
lines
of
the
the
the,
because
it's
a
that
the
developers
I
think
have
sort
of
chosen
end-to-end
because
they
can
test
all
of
their
components
there
consistently,
whereas
like
integration,
maybe
we
could
probably
more
deeply
cover
certain
components,
but
it
would
be
a
lot
harder
to
cover
other
ones.
B
Right
one:
one
of
the
interesting
question
is
where
the
cut
lines
should
be
right
right,
but
end
to
end
is
also
a
very
good
start.
So
I
I'd
love
to
be
pointed
at
that
stuff
too.
A
A
If
we
could
do
this
better,
but
also
it's
like
this
huge
maturish
thing,
so
it's
kind
of
get
rid
of,
but
you
can
find
you
can
find
what
we're
doing
for
kubernetes
under
test
e
and
the
main
repo
and
that's
that's
all
the
tests,
there's
also
an
integration
directory
adjacent
but,
as
I
said,
that's
a
little
bit
less
interesting
at
the
moment.
D
E
I
wanted
to
introduce
myself
as
well
as
so
I'm
I'm
unkit.
I
work
with
with
matt
foley
and
he's
my
manager
and
for
us
like
we're,
also
just
trying
to
figure
out
how
we
can
do
internal
releases
for
communities
also
with
our
internal
components,
etc,
and
and
have
a
good
validation
and
testing
pipeline
in
place.
For
that.
So
that's
why
we're
here
and
would
like
to
learn
and
contribute
as
well
in
the
future.
A
Awesome
when
you
say
kubernetes
releases,
do
you
mean
like
applications
or
or
like
a
kubernetes
district.
A
Yeah,
for
that
I
would
definitely
recommend
taking
a
look
at
the
end-to-end
tests.
In
particular.
Conformance
suite
is
a
really
good
starting
point,
but
you
can
expand
from
there
to
to
get
better
coverage
for
things.
We
haven't
quite
worked
out
how
to
put
in
conformance
yet.
E
Yeah,
I
think
we
did.
We
have
started
exploring
the
conformance
test
quite
a
lot
and
I
think
so
yeah
thanks
a
lot
we'll
be
around.
C
Okay,
my
turn
okay,
mimi
and
also
in
the
same
group
as
matt
in
the
anchet
and
I'm
the
one
that's
gonna,
be
focused
around
the
testing
part
of
the
kubernetes
apple
and
for
our
own
distribution.
So
I'm
the
one
actually
looking
into
the
e2e
test
frameworks
and
the
test
and
hoping
that
we
can
see
something
available
for
us
and
we
can
adapt
it
from
the
existing
work
and
running
some
tests
to
evaluate
the
entire
kubernetes
in
the
system.
C
Integration
level
instead
of
components
level.
So
I
joined
the
group
sometimes
back,
but
it
never
said
anything
just
observing
and
I
like
to
get
more
active
as
you
are
going
like
to
be
participating
more
and
probably
learn
something
from
it
and
if
we
can
contribute
to
it
as
well.
F
I'm
just
going
to
say:
hi,
I'm
patrick,
I'm
working
on
sig
securities,
static
analysis
tool
for
kep
1933,
which
hopefully
will
be
part
of
the
visible,
proud
jobs
in
the
near
future.
So
yeah
hello,
I
yep.
G
Sorry,
I'm
vladimir
I'm
from
vmware.
I
come
here
in
and
out,
but
today
I,
since
I
didn't
know
if
we
were
gonna,
have
a
meeting
or
not
so
I
didn't
post
anything
on
the
dock,
but
part
of
I'm
part
of
the
testing
common
effort,
which
is
kind
of
a
subgroup.
I
believe,
and
one
of
the
things
that
we're
trying
to
do
is
come
up
with
a
testing
firmware.
G
End-To-End
testing
framework
too,
as
you
as
you
alluded
to
the
current
testing
framework
is,
is
can
be
hard
if,
if
to
use,
if,
if
you're,
trying
to
consume
it
programmatically
because
it's
embedded
directly
inside
of
kubernetes,
so
one
of
the
effort
that
started
earlier,
maybe
about
a
couple
months
ago,
we're
looking
to
see
how
we
can,
what
a
testing
framework
end
to
end
would
look
like
and
taking
a
another
stab
at
it
to
make
it
easy
for
for
folks
to
create
into
in
testing.
G
And
you
know
this
the
way
we're
looking
at
it
is.
We
have
cube
test
two
which
allows
you
to
stand
up
your
environment
and
now
we're
looking
at
hey.
What
would
what
would
it
looks?
It
look
like
to
have
a
an
opportunity
to
create
a
new
end-to-end
testing
framework
that
can
be
easily
consumed
and
write
test
about
and
reason
about
our
first.
G
You
know
we're
not
gonna,
try
to
undo
or
rewrite
the
massive
amount
of
testing
that's
already
in
kubernetes,
but
eventually,
as
we
as
folks
adopt
this
and
kind
of
shake
out
what
works
and
what
doesn't.
Hopefully,
we
can
circle
back
around
to
to
kubernetes
to
see
what
what
can
be
done
there,
but
this
is
definitely
a
long
long-haul
project.
So
we'll
we'll
see-
and
I
pasted
the
excuse
me-
the
link
and
I'll
put
it
on
on
the
dock
as
well.
G
I
paste
it
in
the
chat
for
for
zoom.
So
if
you
want
to
check
it
out,
give
me
some
feedback
and
also
in
I
have
the
link
in
testing
commons
is
where
we're
gonna
be
socializing
around
this.
So
if
you
wanna
join
that
that
that
slack
channels,
it's
sig
dash
commons,
that's
all.
I
have.
B
A
Thanks
for
that,
can
you
I
I
don't.
I
don't
remember
this
man
box.
If
you
haven't
already,
can
you
send
this
to
the
suggesting
mailing
list,
so
we
can
get
more
people
looking
at
it.
I
know
the
you
know,
there's
the
the
testing
commons
subgroup,
but
I
think
we
have
a
number
of
people
that
aren't
necessarily
in
that
that
be
interested
in
this.
A
Sorry,
claudia
did
you
want
to
bring
up
your
pocket.
H
Oh
yeah,
basically
I
had
a
couple
of
questions
regarding
this
issue.
H
I
don't
know
if
you
know
any
new
updates,
it's
kind
of
hard
to
track
all
the
discussions,
because
it's
basically
spread
across
multiple
ripples
and
multiple
issues
and
docker
hub
is
more
like
spiderweb,
but
apparently
we
are
still
getting
hit
by
the
docker
hub
rate
limiting,
even
though
we
should
be
using
mirror
registries
for
the
test
jobs-
and
I
have
sent
some
time
ago,
some
requests
which
would
address
this
issue.
H
One
of
them
would
be
to
use
the
mirror.gcr.io
into
the
e3
test
images
as
default
instead
of
docker
hub
and
the
other
one
is
to
just
have
the
the
docker
hub
images
into
the
staging
registry,
which
is
already
being
used
by
the
other
images
as
well,
and
basically
it's
a
small,
almost
no
up
change.
That
needs
to
be
added
to
the
community
test
images.
A
H
A
I
think
the
last
update
is
that
we
that
we
want
to
take
the
second
approach.
The
first
approach,
the
mirror,
is
really
a
cache
and
isn't
meant
to
be
used
as
a
primary
host,
especially
outside
of
gcp,
is
actually
originally
introduced,
as
just
an
optimization
to
get
faster
polls
inside
gcp.
A
The
the
moving
things
into
our
into
our
case
gcr.io
makes
a
lot
of
sense
to
me
and
was
discussed
a
little
bit
further
and
worker
kate's
emperor.
I
think
the
problem
is
just
getting
anyone
to
pick
it
up.
H
H
The
only
thing
that
we'll
have
to
do
now,
in
addition
to
to
this,
would
be
to
add
the
the
jobs
to
testing
from,
because
antonio
made
some
changes
to
how
the
tests
are
being
triggered,
and
now
all
the
test
images
are
being
built
atomically.
H
So
each
individual
image
has
its
own
job,
so
he
also
wrote
a
script,
so
we
just
have
to
run
the
script
to
generate
the
the
jobs
for
the
new
test
images
to
say
so,
but
I
can
do
that
by
at
at
the
very
last,
maybe
not
today,
but
tomorrow
definitely.
A
Yeah,
I
think
that
was
super
helpful.
The
only
other
thing
I
remember
now,
paging
back
in
I've,
been
out
for
a
bit
between
this
stephen
augustus
was
looking
at
having
the
release.
Engineering
group
and
sig
release
owns
some
of
this.
We
need
to
mirror
all
the
things
possibly
broader
than
test
images.
I
believe
some
work
was
done
in
kate's
that
I
owe
to
create
to
create
a
staging
registry
for
this.
I'm
not
sure
how
far
that
get.
We
should
probably
get
back
in
touch
with
stephen.
A
Sorry
so
there's
the
staging
registry
and
then
there's
the
the
production
registry
right,
yeah,
yeah
yeah
yeah
for
this,
but
I
I
definitely
think
we
should
probably
be
trying
to
get
all
the
images
we
use
in
hirui
into
the
kubernetes
production
registry,
because
that
means
that
beyond
even
testing
you
can
just
deal
with
in
your
like
air
gap,
environment
mirroring
just
the
one
prod
registry
and
whichever
images
we
use
both
for
production
kubernetes
and
for
staging
for
a
typical
cluster.
That's
using
upstream
components
and
upstream
testing
also
apologies
everyone.
A
H
About
that,
okay,
then
yeah,
then
I'll
unabandon,
that
request
and
I'll
just
send
the
requested
testing
as
well,
which
adds
the
necessary
jobs
for
the
new
images
in
quotation
marks.
A
Yeah,
I'm
extremely
plus
one
on
that
I'll
I'll.
If
you
draw
me
a
ping
I'll
I'll,
take
a
look
at
those.
Yes,
yes,
of
course,.
A
A
Thank
you
all
for
coming,
usually
we're
a
little
bit
more
organized
than
this
with
the
meeting
agenda
and
everything,
but
I
think,
kind
of
being
the
end
of
the
year.
You
know
it's
not
on
everyone's
front
line,
so
hopefully
we'll
get
things
a
little
bit
more
streamlined
for
21
and
you
all
have
a
great
rest
of
your
day.