►
From YouTube: SIG-Testing Biweekly Meeting for 20230919
Description
SIG-Testing Biweekly Meeting for 20230919
A
B
A
A
B
B
B
A
B
The
case
authenticated
test
images.
We
have
a
test
that
basically
pulls
images
from
a
private
location
in
Google
cloud
from
from
a
container
registry.
It's
misconfigured
right
now.
I
would
like
to
get
that
changed,
but
It's
Tricky,
so
we're
gonna
recreate
that
in
a
community
and
do
card
project
and
make
it
work
properly
in
there
here.
So
we
just
I
just
need
some
thumbs
up
and
then
you
can
go
and
deploy
that.
C
Program
with
the
pull
request
is
like
we
don't
have.
Ownership
of
the
tests
require
requiring
this
artifact
registry.
Wait.
Bro
I
think
Ben
made
the
comment
about
this
I
think
the
bigger
problem
is
like
for
the
tests
relate
to
private
registry.
We
don't
have
ownership
and
I.
Don't
want
us
to
set
up
a
piece
of
infrastructure.
That's
going
to
be
a
technical
death
in
six
months.
C
C
That
that's
the
intent
it's
like
we
need.
We
need
to
seek
one
thing,
owning
the
test
and
basically
giving
a
plus
one
to
remove
the
test,
because
no
one
is
maintaining
them.
So
what
the
first
one
is
who's
owning
those
tests.
The
second
thing
is
that
do
we
need
them
now,
because
maybe
we
have
a
better
coverage
for
this
test
somewhere
else.
D
Okay,
before
before,
removing
tests
that,
let's
not
passion,
because
the
problem
with
the
moving
and
adding
and
changing
things
quickly,
is
that
in
kubernetes
this
takes
one
or
two
releases.
Until
we
know
the
Fallout,
there
are
a
lot
of
things
here,
like
copying,
shift
that
they're
not
going
to
know
that
you
remove
one
test
until
one
or
two
releases.
Oh,
for
this
specific
case
is
C
gaps
yeah.
We
need
to
go
to
see
that
and
explain
what
is
the
problem
and
and
actually,
you
need
to
provide
a
solution.
D
B
B
D
And
tag
it
so
it
can
only
run
with
a
special
conditions,
all
right.
So
this
is
the
problem
that
we
are
having.
Now
we
have
this
right
and
that's
the
problem.
We
need
to
carve
it
out,
but
we
cannot
do
extracting
a
painful
strategy.
We
need
to
be
a
strategic
and
and
go
one
by
one.
This
is
going
to
be
no.
B
D
But
within
it,
okay,
but
we
need
to
put
the
project
in
that's.
Why
I
ask
it
to
the
I
mean
this
project
has
to
be
managed.
It's
not
now
we
are
going
to
move
to
everything
and
we
are
going
to
remove
tests
and
do
everything
this.
This
needs
a
communication
with
all
the
state,
but
all
the
stakeholders
are
all
the
kubernetes.
D
C
D
B
B
D
D
B
Problem
with
that
is
at
the
end
of
The
Journey,
when
we
have
both
classes
up
and
running.
The
first
thing
we
want
to
do
is
see
how
the
tests
are
configured,
which
ones
are
passing,
which
was
a
failing.
If
there's
too
many
skips,
these
questions
will
come
off
and
be
like.
Why
are
we
doing
this
yeah
foreign.
B
D
D
D
B
D
B
D
D
D
B
B
D
B
D
D
A
D
Okay,
okay
and
then
you
have
the
other
one.
One
important
thing
about
this
replacement
and
I
was
talking
with
Justin
Santa
Barbara
today,
right
now,
I
think
that,
because
of
the,
my
suggestion
is,
is
to
make
the
transition
as
similar
as
possible.
Simple
sample
GC
deploys
a
very
simple
password
single
Master
right
three
work,
so
if
you
can
mimic
that
as
much
as
possible
with
it,
because
if
we
start
to
have
multi-master
in
the
CI,
that's
super
thankful
to
divide.
B
D
Okay,
so
perfect,
that's
another
thing:
okay,
you
you
just
no
more
questions,
because
the
moment
that
you
need
to
divide
a
place
with
multi-master
is
like
spending
hours
all
day
and
I
think
a
master.
Everything
is
much
cheaper,
yeah
appreciate
it.
So,
as
I
said
yes,
I
I
want
to
support
you
and
and
I
think
that
you
are
doing
the
ugly
thing.
So,
let's
try
to
to
put
some
structure
on
this
project
and
and
be
able
to
do
your
best
faster.
B
All
right
so
this,
if
let
me
show
you
this
or
the
job,
is
configured
to
do
yeah
so
yeah.
So
this
is
similar
to
the
I
think
the
43
test
that
we
do,
that
checks
everything
except
serial
slow,
and
so
these
features
tests
it's
looking
great
so
far.
These
are
two
failures
that
we
discussed.
This
is
another
thing
that
I'm
planning
on
fixing.
It's
got
nothing
to
do
with
kubernetes.