►
From YouTube: 20201103 SIG Arch Conformance
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Good
day
welcome
to
the
performance
office
hours
meeting
for
november
3rd
2020..
I'm
marianne
keep
in
mind
that
this
meeting
is
being
reported
and
will
be
shared
via
the
internet
on
youtube
shortly
and
keep
in
mind
we'll
buy
the
kubernetes
code,
of
course,
or
cncf
her
code
of
conformance
and
code
of
conduct
and
please
be
excellent
to
each
other.
A
So
thank
you
effie
for
taking
the
notes
and
let
me
go
it's
a
short
agenda
and
we
are
fairly
short
on
people.
I
think,
because
of
the
time
change
in
their
elections
in
america,
but
so
the
first
point
on
the
agenda.
A
We
had
last
time
had
in
the
meeting
the
proxy
endpoint
for
no
proxy
an
issue
up
for
that
to
make
it
to
figure
out
how
exactly
we're
going
to
test
him
for
performance
and
that
possibility
was
raised
that
it
should
actually
might
not
be
valid
for
conformance.
So
we
took
it
to
the
node
up
to
sick
node,
for
discussion
and
in
the
meeting
on
the
7th
of
october,
they
informed
us
that
they
actually
created
these
endpoints
right
in
the
beginning,
when
developing
kubernetes
and
the
purpose
for
which
they
created
is
properly
not
valid
anymore.
B
C
It's
probably
good
just
to
have
discussion
here
and
then
put
it
out
to
the
mailing
list
as
well,
pointing
to
our
pr
apis
to
mark
them
as
deprecated
in
our
in
the
yaml.
I
think
that
you
use
for
noting
which
endpoints
are
deprecated
or
that
are
not
available
for
conformance,
and
that
was
really
performance.
Thank
you.
A
B
A
A
A
A
It
is
just
re-running
the
basal
job
and
that
should
be
ready
for
approval
shortly.
So
we
will
re
reach
out
to
the
relevant
people
to
get
that
approved.
C
C
C
And
my
my
hope
is
that
that
will
get
rid
of
our
flakes.
A
Good
thank
you
for
that.
Then.
The
next
issue
to
discuss
is
the
pull
request
for
the
pod
status
resource
lifecycle
test
stephen.
What's
the
latest
update
there,
I
see
we
had
a
funnel
again
today.
B
Those
failures
they
this
morning
are
related
to
another
flaky
test
that
aaron
mentioned
this
morning
to
do
with
cube
control
test.
That's
failing!
So
those
if
you
look
at
the
pr
history.
B
Where
you
want
to
go,
oh
just
open
up
one
of
the
details
and
then
we
can
go
to
the
pr
history.
D
B
Yeah,
so
this
a
stack
of
tests
run
against
the
e2e
yeah,
so
those
tests
here
it
relates
to
that
other
test.
That's
been
flaking,
they
got
flaked
this
morning.
A
A
B
B
So
if
you
go
that's
just
imports
and
stuff.
So
if
we
go
over
further
down
the
big
thing
oh
hold
on,
I
was
thinking
sorry
just
trying
to
see.
B
B
B
See
are
we
going
we're
staying
a
bit
further,
more
work,
fishing
patching
yeah
still
a
little
bit
further
along.
A
B
So
and
the
delay
section
yeah
on
that
line,
just
where
you
are
under
the
delete
options,
we
I
switched
it
so
the
grace
timeout
is
set
to
zero,
so
that
just
speeds
up
the
whole
process
of
removing
the
pod
and
hopefully
getting
a
event
back
a
lot
sooner
than
it
had
been
in
the
past.
D
B
The
last
flaky
error
messages
we
had
a
little
early
last
week.
A
B
Yep
pretty
much
yeah,
okay
yeah!
Well,
what
one
I'll.
B
Chat
as
well,
we
still
need
those
tests
to
be
reruns
over
there.
B
We've
got
the
appropriate
checks,
ticks
in
place.
C
I've
dropped
them
into
the
chat.
Ninety
three:
four:
five,
eight,
nine,
three,
four
five:
nine.
I
think
clayton's,
the
only
person
on
the
call
who
has
the
what
it
takes.
E
Yeah,
once
again,
once
it
gets
tagged,
looks
into
me
I'll,
come
back
and
refresh
this.
If
y'all
want
to
drop
that
on
in
the
next
like
right
at
the
end
of
the
meeting,
I
have
to
drop
it
in
10
minutes,
but
I'll
come
back
and
sure
once
it's
been
tagged,
looks
good
to
me.
Thank
you.
Thanks,
we'll
talk
about
that.
A
Okay,
thank
you
very
much
for
that
and
then
the
did
I
not
throw
in
the
proxy.
Oh
yes,
I
did
okay,
so
far,
proxy
steven,
if
you
just
want
to.
A
What
you
did
to
fix
that
with
the
remotes
updates.
B
And
yes,
we're
bumping
inversions
and
we
go
down
to
yeah
so
and
here
we're
just
setting
up.
D
E
A
And
that
would
then
help
us
to
sort
out
the
proxy
with
that
and
service
proxy
with
bath
once
you
want
that
fast,
you
will
update
this
test
and
that's
the
law.
The
last
outstanding
point
that
we
need
for
this
test
to
to
be
ready.
Am
I
right.
D
A
Did
run
quite
well
if
we
were
only
needing
this
change
so
once
we've
made
it,
we
also
reach
out,
if
you
can
just
review
that,
we
really
appreciate,
because
we're
all
running
a
little
short
on
time
to
get
these
things
into
the
into
this.
C
Scroll
down
just
a
little
bit
further,
if
you
wouldn't
mind
clicking
on
the
api
student
performance
progress,
I
just
wanted
to
go
over
our
new
thoughts
on
release
blocking
so
that
we
have
a
place
to
have
a
conversation
when
this
happens
so
just
launch
that
real
quick
and
take
a
look
and
note
that
before
this
merge,
the
graph
does
not
show
any
of
the
horrible
orange
that
are
the
new
ga
endpoints
without
test.
C
Now,
if
you
go
back
to
that,
the
poll
401
to
api
snoop,
that
is,
the
the
job,
go
back
to
the
document
and
open
the
crown
job.
C
This
is
the
helicopter
files
changed.
This
is
the
cloud
build
dmo
that
we're
currently
using
to
generate
it
and
it's
the
fourth
tab
on
file
stream.
C
That's
right
and
we
go
through
some
steps
to
get
a
github
token
that
we've
stored
in
gcb.
We
check
out
the
hub
command,
so
we
can
create
the
pr
from
within
the
job
and
use
the
the
bot
to
do
so,
and
then
we
use
our
api
smooth
db
to
run
the
the
coverage
to
generate
the
jsons
and
move
that
into
the
api
repo
and
then.
Finally,
on
the
last
step,
we
copied
into
place
and
pushed
the
pr
through
it's
still
loose
and
a
little
bit
messy
at
the
moment.
C
C
So
this
is
the
pr
that's
a
result
of
that
job
by
the
bot
17
hours
ago
and
if
you
click
on
files,
change
we're
going
to
try
to
find
a
way
to
make
it
a
little
more
clean
to
read.
But
there
was
a
lot
of
changes
within
the
dip
it.
The
main
thing
is
to
note:
there
are
now
two
untested
endpoints
that
are
about
to
show
up,
and
if
we
go
down
to
the
bottom,
I
think
we
can
even
see
what
those
are.
C
Maybe
not
so,
let's
go
ahead
and
merge
that
rihanna.
If
you
can,
if
not
I'll
I'll,
go
ahead
and
merge
it
so
then
we
can
go
back
and
that
will
update
the
front
of
apis
to
the
website.
C
New
api
snoop
site
and
apple
r
control,
r,
whatever
your
favorite
reload,
the
site
command,
is
and
they'll
need
to
go
to
the
conformance
page
performance
progress.
We
will
note
a
change
here
and
the
data
will
say
it
came
from
the
third
of
november,
but
the
main
thing
is
it's
growing
up
a
bit
they'll
be
a
little
should
be
a
little
lying
around
performance
program
november.
C
No
problem
just
scroll
down
to
the
bottom,
and
it
actually
shows
that
there
are
two
stable:
it's
internal
api
server
and
open
api
id.
It's
get
service
account
open
id
configuration
and
get
service
account
open
issue
id
and
they're
neither
tested
nor
conforming,
and
so
we
should
probably
link
to
those
and
if
there's
any
conversation
or
direction
that
either
you
have
dentists
or
clients,
would
love
that.