►
From YouTube: Sig-Testing Weekly Meeting for 20230418
Description
Sig-Testing Weekly Meeting for 20230418
A
B
Hello
I
am
new,
wish
I
used
to
participate
way
back
when
but
kind
of
stopped.
So
my
name
is
Vladimir
Vivian
I'm,
with
with
VMware
about
a
couple
years
ago,
I
started
the
the
e2e
framework
project
as
a
way
to
help
folks
write
kubernetes
tests
without
depending
on
the
intrinsic
built-in
kubernetes
test
framework.
So
this
one
is
completely
independent,
so
yeah
so
kind
of
came
back
to
we'll
we'll
be
trying
to
participate
more
and
more
in
the
in
the
Sig
testing
meetings
as
often
as
possible.
C
A
B
So
this
is
the
one
place
that
I
know
where
we
can
have
continuous
face
to
face
with
with
the
community,
so
definitely
want
to
jump
back
in
and
and
put
my
face
in
the
meeting
and
participate
so
that,
if
folks
have
any
questions
and
about
the
project,
the
last
thing
that
just
happened
is
I.
I
had
a
chance
to
finally
do
a
release.
B
Last
week
or
last
weekend,
I
don't
remember
version
0.2
and
again
the
the
project
is,
you
know
when
it
first
started,
it
was
I,
I
wrote
a
lot
of
code,
but
for
the
last
couple
years
it's
been
Community
Driven
completely,
which
is
great
and
folks
are
adding
things
that
they
want
to
see
and
and
the
project
is
healthy
and,
like
I
said
it's
getting
adopted,
I,
don't
know
if
there's
any
question,
but
I
can
just
talk
about
the
project.
If
there's
no
question.
B
B
B
The
only
thing
is:
there's
a
kind
of
a
build,
a
pattern
that
you
get
with
with
the
project
that
allows
you
to
do
some
further
setup
of
your
tests,
even
in
inside
the
test
function.
So
you
can
do
things
like
labeling
your
tests,
give
it
a
name.
So
you
can
see
in
the
report
which
test
was
running
and
you
know
the
main
thing.
B
Is
you
get
a
the
access
to
the
to
a
kubernetes
client
that
allows
you
to
run
your
tests
and
have
access
to
the
to
to
the
to
the
API
server?
There
are
other
there
are
other
supporting,
tooling
or
apis
that
you
get
such
as
there's
a
weight
API,
which
is
a
a
wrapper
of
I,
think
it's
API
machine
weight,
but
it's
it's
a
little
bit
simpler
to
use
where
you
can,
during
a
test,
set
up
weight
conditions
to
wait
for
a
specific
condition
to
become
true.
Before
the
test
can
proceed.
B
B
B
B
B
C
Assume
the
question
in
the
Channel's
been
answered
by
Ben,
maybe
for
folks
not
looking
in
the
chat
check
the
chat
for
a
question.
My
question
is
just
to
be
very
specific
and
clear
about
but
you're
talking
about
you're
talking
about
the
test
framework
used
in
the
kubernetes
test
directory
for
e2e
and
stuff
of
that
sort.
B
No,
that
is
that
was
one
of
them
driving
motivation
for
this,
because
we
didn't
want
to
because
the
the
test
that's
in
kubernetes
kubernetes
has
its
own
framework.
It
uses
I,
think
it
uses
Ginkgo
and
it's
very
closely
coupled
with
kubernetes
itself
and
if
I'm
creating
a
project,
and
at
least
two
years
ago,
when
this
started.
That's
how
that
was
the
state
of
things.
I,
don't
know.
B
If
things
have
changed
since
then,
and
it
was,
you
know
a
bit
difficult
to
to
kind
of
vendor
that
so
this
project,
the
one
of
the
motivation
of
this
project,
is
hey.
You
don't
need
to
you,
don't
need
trying
to.
You,
know,
reuse.
What's
in
kubernetes,
because
again,
it's
very
tightly
coupled
and
organically
grown
with
kubernetes.
C
D
D
A
lot
lighter
if
you
could
start
from
scratch
today,
like
this
project,
has
because
the
rest
of
the
ecosystem
has
evolved
like
when
kubernetes
adopted
Ginkgo
early
on
go
didn't
have
a
way
to
do
control
flow
for
like
cleanup
right.
They
had
added
test
main,
but
that
was
it
is
test
made
and
test,
and
you
had
no
way
to
do
things
like
cleanup.
You
had
no
way
to
get
structured
output
out
of
go
tests,
so
I
think
even
Ginkgo
didn't
have
that.
B
Yeah,
thank
you
for
for
adding
that
and
and
that's
exactly
what
it
is.
It's
it's.
It
was
kind
of
a
reset
of
of
what
was
and
a
lot
of
the
concepts
that
are
in
here.
You
know,
I
took
when,
when
we
were
first
starting
took
a
good
few
days
to
look
at.
What's
what
folks
have
been
doing
in
inside
kubernetes
kubernetes
and
there's
a
lot
of
good
stuff
in
there,
you
know
stuff
like
the
ability
to
wait
for
a
condition.
We
wanted,
that
the
ability
to
construct
objects
with
fragments.
We
wanted
that.
B
C
B
B
B
So
originally,
the
intention
was
not
to
basically
leave
kubernetes
kubernetes,
as
as
it
is
because,
as
Ben
mentioned,
it
has
its
own
Cadence
its
own
pace.
This
is
more
for
folks
who
are
building
tools
in
one
an
easy
way
to
test.
You
know
if
you're
building
on
top
of
kubernetes,
you
want
to
test
whatever
you're
building.
This
would
be
the
tool
rather
than
you
going
and
recreating
your
test,
your
own
test
framework
and
end
up
at
a
place
very
close
to
this.
B
Why
not
just
use
this
to
as
a
starting
point,
so
that's
the
intended
audience,
but
the
the
stuff
that
maintained
testing
for
kubernetes
kubernetes,
completely
separate
but
I
mean
in
the
you
know
some
sort
of
future.
If
somebody
is,
you
know
brave
enough
and
have
a
lot
of
time,
and
they
want
to
explore
using
some
of
this
for
kubernetes
kubernetes
they're
welcome
to,
but
for
now
the
two
projects
are
intended
to
be.
You
know
to
be
separate.
D
The
test,
the
the
test
framework
in
kubernetes
kubernetes,
is,
is
used
by
the
tests
in
kubernetes
kubernetes
for
testing
kubernetes
itself,
with
the
exception
of
the
conformance
program,
those
tests
aren't
super
useful
if
you're
doing
other
things
other
than
developing
kubernetes
itself.
The
the
conformance
tests
on
a
handful
of
the
other
tests
may
be
useful
if
you're
developing
like
a
kubernetes,
distro
or
something,
but
if
you're
developing
kubernetes
applications,
then
you
you
would
want
to
be
looking
at
Vladimir's
project
instead
of
instead
of
the
the
the
things
we
have
in
kubernetes
kubernetes.
D
D
There's
just
so
many
tests,
I
think
the
biggest
thing
that
we're
doing
with
that
is
just
trying
to
keep
them
rolling
forward
with
the
ecosystem
as
much
as
we
can
and
trying
to
decouple
them
a
bit
from
even
some
of
the
tests
and
kubernetes
kubernetes
are
like
coupled
to
the
the
cluster
tools
like
Cube
up.sh,
and
would
don't
we
didn't
want
that
concept
coming
back
as
well,
but
it's
going
to
be
very
hard
to
remove
that.
There's.
B
B
B
So
if
I
don't
know,
if
anybody
has
the
project
pulled
up,
but
there's
a
specific
package
name
client
with
a
K
and
I
intentionally
pulled
that
out
with
the
intent,
maybe
at
some
later
Point
down
the
line.
Maybe
pull
that
to
be
its
own
thing,
its
own
simplified
way
of
managing
kubernetes
client
goal
client,
but
you
could
use
that
with
your
existing
test
framework
and
you
get
the
same.
B
You
know
you
get
the
same
benefits,
even
if
you
didn't
want
to
use
E2
the
this
project
need
to
be
test
framework.
So
that's
that
that
that's
good
to
hear
that
somebody
is
using
it
with
Ginkgo
and
the
other
thing
I
I
didn't
mention,
but
past
past
releases.
One
of
the
thing
I
worked
on
in
the
previous
release
was
the
the
integration
with
Cube
test2.
B
So
you
can,
if
you
didn't,
want,
if
you're
already
using
Cube,
Test
2
or
you,
you
know,
you're
looking
if
you're
already
using
Cube
tester,
you
could
still
use
E2
test
framework,
you
let
keep
test2
set
up
your
and
tear
up
down
your
environment
and
and
then
E2
test
framework
will
actually
run
your
tests.
Yeah
go
ahead.
C
B
B
Yeah,
that's
a
good
idea.
I
probably
should
add
it
in
the
dock
that
the
intent
of
that
package
is
to
show
that
you
can.
There's
I
wanted
to
get
to
a
point
where
we
have
a
another
layer
of
abstraction,
on
top
of,
what's
available
with
a
client
go
and
that's
what
client
with
a
K
does,
is
it's
kind
of
it
high?
Actually
what
it's
one
of
the
things
it's
doing,
it's
reusing
God!
B
What's
the
it's
an
it's
reusing,
another
project
and
the
name
controller
runtime,
so
the
client
there
I
like
what
they
were
doing
so
I
was
like.
Let
me
wrap
some
of
that
and
hide
some
of
the
complexity
so,
whether
or
not
you're
using
a
type
type
client
or
generic
client,
it
doesn't
matter
it
hides
all
that
it
makes
that
decision
for
you
and
hides
it
for
a
and
gives
you
something
you
can
just
use
and
what
else
is
in
there.
B
The
all
the
like
some
folks,
some
one
of
the
a
contribution
I
think
it
was
last
year
that
somebody
did
was
the
ability
to
encode,
basically
any
kind
of
arbitrary
yaml
chunk.
You
can
pass
it
to
the
client
and
it'll
give
you
the
action.
It'll
realize
the
objects
for
you
so
which
is
very
useful
in
tests,
especially
if
you
have
something
that's
very
structured
and
you
don't
want
to
take
time
to
kind
of,
or
you
don't
even
you're,
not
even
sure
what
the
structure
is.
You
can
pass
it.
B
The
the
yaml,
Chuck
and
it'll
give
you
a
realized
object.
So
there's
a
lot
of
good
things
in
there
that
I'm
like
well
I
would
like
to
see
this
in
a
generalized
API,
not
just
for
testing.
So
but
it's
a
good
fertile
ground
to
kind
of
play
around
with
these
ideas-
and
you
know,
hopefully
time
permits,
push
them
further
up
the
stack
as
far
as
maybe
you
know,
other
cigs
that
may
be
interested.
B
B
B
D
I
just
want
to
add
if
folks
are
interested
in
the
topic.
This
applies
more
to
the
entry
framework,
but
we
actually
just
had
some
Publications
that
had
a
kubecon
about
like
how
to
write
good
ewe
tests
and
best
testing
practices.
I
think
there'll
be
some
overlap
there
pretty
interesting
from
one
of
our
recent
leads
Patrick
and.
B
D
D
If
you,
if
you
can
catch
some
time
with
them,
I
would
recommend
connecting
up
with
Antonio
and
Patrick,
who
are
our
most
recently
promoted.
Tech
leads
in
the
Sig.
They
both
were
I
nominated,
both
of
them
because
of
all
their
work
on
the
entry
framework,
which
suddenly
got
a
ton
of
work
past
couple
years,
I
still
wouldn't
recommend
that
people
like
reuse
that
thing
but
I
think
there's
been
some
good
ideas
brewed
in
there.
D
Okay,
like
I,
was
I
was
just
poking
around
in
here
now,
and
one
thing
that
comes
to
mind
that
I
would
suggest
you
might
want
to
poke
some
folks
about
and
and
see
about
kind
of
copying.
The
idea
into
here
is
the
the
host
exec
pod
trick.
I
didn't
see
anything
for
that
poking
around
the
current
state
of
the
the
kubernetes
six
ew
framework,
and
that's
been
a
really
useful
thing
that
we've
moved
towards.
B
D
D
That
is
a
really
useful,
pretty
portable
trick.
You
know
it
won't
work
on
all
clusters,
they're
going
to
be
clusters
that,
like
block
this
sort
of
behavior,
but
if
you
have
sufficient
privileges
just
using
the
kubernetes
API,
you
can
do
that
so
almost
everywhere
that
we
were
using
SSH
to
do
things
like
checkmates
nodes,
away,
move
this
I
think
for
like
application
devs.
This
is
less
relevant,
but
for
people
that
are
building
like
critical
add-ons
for
things
like
storage
or
networking.
D
D
D
D
B
Okay,
I'll
dig
through
that
length
that
under
hosts
exec
util
to
see
what
yeah,
because
one
other
thing
I
wanted
to
do
and
I'm
pushing
forward
with
this
project,
too,
is
to
kind
of
integrate.
I
guess,
integrate
kind
of
a
strong
word,
but
make
sure
that
we're
we're
leveraging
other
tools
like
somebody
is
already
looking
into
using
the
new
the
quack
project
as
a.
C
B
Instead
of
running
kind,
which
I
think
quack
kind
of
started,
something
like
kind
in
the
background,
but
quack
we're
looking
into
integrating
with
Quark
we've
done
it
with
Cube
test
two,
so
anything
that
helps.
You
know
that
that
stays
and
and
reach
out
in
in
the
ecosystem.
It
makes
it
easy
I'm.
Definitely
looking
into
that.
Yeah.
D
I
think
we
have
a
couple
of
just
a
few
of
these
actually
good
ideas
that
are
in
the
that
are
in
the
entry
framework
that
may
make
sense
to
clone
over
here
that
the
host
exec
is
one
I,
think
you
have
a
lot
of
the
other
things
like
that.
How
like
how
to
Wade
on
things
properly.
Most
of
what
Patrick's
talking
about
here
is
just
like
the
approach
to
doing
things
reliably.
Where
is
this
more
of
like?
B
D
Yeah
I
think,
if
I
think
we
connect
you
with
Antonio
and
and
Patrick
Ayo,
Jaya
and
Pioli,
they
they
both
have
done
a
lot
of
work
on
the
entry
one
recently
and
there's
probably
a
few
other
ideas
like
this.
That
I'm,
not
thinking
about
thought,
my
head,
that
are,
are
worth
looking
at
and
seeing
if
they
can
be
of
use
for
the
yeah.
B
Absolutely
framework
Absolutely
I'll,
definitely
reach
out
to
Patrick
when
I
was
doing
storage
way
back
when
we
crossed
paths
so
I
definitely
reach
out
to
him
yeah
and
I'm.
Looking
at
the
blog,
it
looks
like
some
of
the
stuff
like
it
looks
like
they're
directly
built
in
can't
go
now
like
the
waiting
and
the
polling
and
stuff
like
that.
Yeah.
B
D
The
trickiest
one
off
the
top
of
my
head,
that
was
I've,
been
like.
Oh,
we
should,
like
you
know,
document
this
better.
This
is
a
good
idea.
I
mean
it's
a
good
bad
idea.
It's
a
little
confusing
yeah
I'll
be
abusing
some
functionality,
but
I
would
guess
that
between
the
two
of
them,
there's
a
couple
more
of
these
that
I'm,
not
thinking
of
since
I,
haven't
spent
as
much
time
on
it
recently
cool.
D
Up,
thank
you
for
working
on
this
I'm,
really
glad
that
there's
a
place
for
people
to
collaborate
on
the
auto
tree
one.
My
focus
has
usually
been
on
kubernetes
itself,
but,
like
you
know,
we
want
to
be
able
to
provide
good
practices,
but
every
time
someone
would
come
and
talk
to
us
we're
like
don't
use
the
thing
where.