►
From YouTube: 20220811 SIG Architecture Community Meeting
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
The
meeting
and
record
yeah
all
right
the
recording
started.
This
is
the
architecture
kubernetes
architecture
meeting
for
August
11th,
welcome
everyone,
a
small
crowd
today
and
so
go
ahead.
Rihanna.
B
Thank
you
very
much
all
right.
Let's
stop
project
readout
for
conformance
and
good
news
going.
We
killed
19
endpoints
with
new
conformance
tests.
In
this
release,
three
endpoints
were
moved
to
ineligible.
The
loss
of
the
apps
endpoints
have
now
been
covered,
as
now
100
covered
23
endpoints,
remaining
you'll
see
is
mostly
core.
There
is
some
API
service,
endpoints
and
some
off
I
think
endpoints.
The
rest
is
all
core.
B
So
at
another
point,
I
will
bring
all
those
to
the
meeting.
I
thought.
Well,
let's
just
do
the
sub
project
readout
and
then
I
will
bring
that
to
another
meeting
to
just
discuss,
what's
ongoing
with
the
with
the
remaining
inputs
and
then
some
input
there
might
be
some
more
that's
ineligible
that
we
have
not
looked
at
before.
A
C
I
have
someone
I'm
meeting
with
tomorrow.
That's
got
a
new
API
coming
in,
that
is
external,
so
they
have
a
bunch
of
conformance
tests
that
are
external.
So
next
time
we
swing
back
around
to
cigarch.
I
should
have
some
interesting
conversations
about
where
tests
belong.
When
we
have
new
things
getting
developed
that.
A
Yes,
yeah,
so
I
sent
them
your
way
like
they
I.
Don't
know
that
it's
quite
it
gets
back
to
the
thing
that
we've
tried
like
four
times
and
failed
at
which
is
some
sort
of
optional
reinformance
program.
What
but,
but
what
they
need
is
a
different.
They
need
almost
a
clone
I.
Think
of
the
conformance
programs,
so
I
think
it's
going
to
be
a
little
bit
different.
So
have
the
have
the
call
with
them.
A
C
Was
messed
up,
probably
my
side,
I'm,
driving
and
so
I'm
in
the
car?
Yes,
that
sounds
good.
A
B
Think
I
want
to
mention
it
just
mentioned.
Then
we
can
push
it
over
because
we
need
more
of
a
discussion,
so
the
first
one
is
bug
Discovery.
Something
that
we
found
is
that
we
have
this
running
flight
free
perfectly.
There's
two
examples
that
I
can
show
here
on
this
grid
before
as
e2e
test
at
the
moment
we
push
them
to
promotion,
they
actually
die
and
some
of
them
terribly
bad
or
cause
other
other
conflicts.
B
B
I,
unfortunately,
Stephen
can't
we
have
quite
quite
a
detailed
discussion
about
it,
so
it
also
be
good
to
have
it
here
at
his
point,
but
I
think
the
tested
run
for
emerging
e2e
tests
and
the
test
checks.
That's
being
run
for
performance
tests
is
not
exactly
the
same,
so
okay,
so.
B
So
that
is
the
one
point.
So
yes,
let's
discuss
that.
The
next
meeting,
the
other
one,
is
API
service
life
cycle
test.
It's
four
endpoints
that
we've
been
brought
in
now
for
the
second
time
and
this
time
it's
messing
with
I'm
trying
some
storage
endpoints
that
it
causes
problems
on,
and
then
we
marked
it
as
disruptive
and
we
marked
with
the
serial.
C
B
Stone
Falls
as
a
problem,
so
in
the
next
call,
when
we
have
people
from
API
Machinery
in
maybe
some
Jordan
or
Clayton,.
A
B
What
we
will
properly
do
is
just
discuss
it
in
this
meeting
next
time
for
for
general
information,
and
then
we
would
reach
out
to
API
Machinery.
We
will
probably
go
through
their
meeting
and
say
this
is
what
this
is
all
the
things
we
tried
and
it
would
be
a
more
detailed
discussion
there,
so
just
for
information
for
secret
identities.
These
are
hard
and
if
we
can't
get
them
solved,
they'll
go
right
at
the
bottom
after,
let's
first
try
all
the
others.
A
Time,
hey,
Ben,
we're
just
gonna
wrap
up
because
we
hit
a
small
crowd
and
not
much
agenda
today,
and
so
we
want
to
address
the
things
on
the
agenda
with
a
larger,
larger,
full
yeah.
Yeah
makes
sense
awesome
all
right.
Thanks
all
see
you
next
time.