►
From YouTube: 20220421 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
Yeah
this
is
enough
lag
time
all
right.
Everybody
welcome
today
is
April
21st
2022.
This
is
a
kubernetes
architecture,
community
meeting
and
let's
get
going
I
think
we
just
have
I
checked
a
minute
ago.
We
just
had
one
thing
on
the
agenda,
which
is
to
hear
from
Brianne
on
the
conformance
project
readout,
so
take
it
away.
A
B
So
we
landed
16
endpoints
that
did
not
have
conformance
test
in
this
release
now,
with
conformance
12
points
from
service
proxy,
which
came
quite
a
long
way
to
get
that
landed.
But
that's
in
for
template,
one
endpoint
and
match
the
job
status
end
points
three
endpoints.
We
had
four
more
in
the
queue,
but
because
of
a
bug
with
annotations
that
we
assume
that
annotations
would
be
available
when
we
tried
to
promote
its
flight,
but
that's
already
fixed
and.
C
B
C
B
B
A
B
D
B
Point
I'm
not
sure
if
I
can
share.
B
C
B
C
C
B
We
didn't
lose
any
grounds
due
to
us
trying
to
another
test.
We
lost
this
endpoint,
probably
within
24
hours,
Jordan
picked
it
up
and
fixed
it.
So
thanks
to
Jordan
for
fixing
that
and
then
do
an
endpoints
because
of
a
lot
and.
D
B
Endpoints
all
which
requirements
so
then,
eight
storage,
endpoints
came
in
the
ga
with
just
before
code,
freeze
or
Test
free.
So
that's
the
way.
Well,
so
in
the
release
with
45
endpoints
remaining
without
performance
test,
and
at
the
moment
it
looks
still
look
good
to
get
it
all
caught
by
the
end
of
2022
or
after
this,
the
first
quarter
of
the
next
release.
It
is
harder
it's
slower.
We
already
have
a
PR
coming
for
three
more
end.
B
Points
on
I
can't
remember
off
the
top
right
here,
there's
three
more
invoice
coming
for
which
we
already
have.
B
Really
pushing
it
to
get
to
the
end
of
things
in
by
the
end
of
the
year.
Looking
at
the
ABS
new
graph
you'll
see,
we've
still
got
strongly
up
in
the
right.
The
gray
area
still
that
we
need
to
cover,
which
is
we're.
Always
there
API
Snoop,
the
Sunburst
you'll,
see
that
we
basically
those
batch
endpoints
that
fall
there.
That
is
not
fully
dark,
they
will
be
tested
soon.
B
A
Just
wanted
to
thank
you,
yeah
that
was
great
and
I'm
really
glad
we're
making
good
progress.
I
think
a
few
points
for
the
folks
here
from
our
last
meeting
and
one
is
that
that,
as
Rihanna
I
think
said,
we're
getting
to
the
set
of
technical
debt,
that's
more
difficult
to
address
because
of
various
either
the
tests,
issues
with
the
tests
or
just
various
confusion
about
whether
the
test
framework
can
actually
support
it
and
whether
they
should
be
in
conformance.
So
the
progress
may
not
keep
a
pace
as
what
we've
had.
A
Because
of
that
in
the
last
call,
we
had
a
pretty
extensive
discussion
about
some
of
the
endpoints
and
Rhian
raised
a
couple
of
issues.
I
don't
know
if
those
are
linked
in
the
agenda,
but
if
they're
not
please
put
them
in
there.
A
Folks
should
comment
on
those
and
Clayton
I
I
know
you
weren't
there
in
the
last
call,
and
but
I
think
that,
based
on
looking
at
your
comment
that
Brianna
I
think
Linked
In
in
one
of
those
issues,
I
think
we're
pretty
well
aligned
around
like
the
the
challenges
around
things
like
the
node
node
API,
and
you
know
we,
we
I
wasted
a
lot
of
time
a
few
years
ago,
trying
to
get
this
profile
stuff
in
I'm.
A
Not
sure
I
really
want
to
pick
up
anything
like
that
again,
but
we're
starting
to
get
to
this
area
where
we
have
a
lot
of
kind
of
optional
things
or
you
know
more
challenging
I,
guess
I,
guess
items
and
we
have
to
decide
probably
what
to
do
about
those.
So
please.
D
A
Look
at
those
issues
and
you
know
we
can-
we
can
debate
them
there.
I,
don't
know
that
there's
the
people
aren't
necessarily
have
it
all
swapped
in
right
now
to
be
able
to
debated
here,
but
but
those
issues
raised
those
pretty
well.
B
I
have
the
links
the
first
one
is
resource
quota
which
we
expected
might
not,
but
actually
this
week
we
started
making
good
programs
and
resource
quota,
so
we
already
so
the
first
three
endpoints
that's
coming
in
is
for
resource
quota.
The
resource
squad
or
status
is
the
next
one
which
turned
out
a
bit
be
a
little
sticky,
but
Stephen
is
busy
working
on
that.
So
any
comments
on
that
and
it's
eligible.
B
Now
it
is
eligible
the
next
one
that
I'll
drop
is
where
we
believe
it
should
not
be
eligible
to
tighten.
You
already
did
give
us
quite
a
good
amount
of
feedback
on
drop
that
in
the
chat
as
well
find
the
chat
again
there
we
are,
and
that
is
for
node
status
and
some
some
thoughts
on
that.
If
anybody
want
to
comment
I'll
appreciate
and
then
as
John
says
we
properly,
it's
not
a
question
of
we,
we
don't
want
to
finish
the
work
and
just
try
and
make
anything
everything
ineligible.
B
C
A
A
C
Thank
you,
John.
Okay,
awesome,
oh
yeah,
one
thing
something
comes
to
mind,
so
you
can
make
it
to
the
prr
meeting
yesterday
John
and
there
was
there-
was
something
during
the
I,
don't
know
who
who
here
made
it
to
the
piano
meeting
yesterday.
Anyone.
C
Yeah
yeah
so
John,
so
Elana
is
stepping
down
so.
D
A
Because
she's
been
super,
her
contributions
have
been
really
really
helpful,
so
I'm
I'm
bummed,
but
we
definitely
probably
want
to
recruit
some
more
participants
because
the
the
load
grew
over
the
last
you.
A
And
now,
with
one
last
person,
that's
going
to
be,
you
know,
write
another
another.
You
know
more
more
weight
on
a
few
of
us
and
plus
it's
just
better
to
have
a
more
opinions.
So
absolutely.
A
So
anybody
out
there
who's
interested,
we
would
love
to
have
you
in
the
prr
and
it's
generally
not
too
demanding
except
right
around.
You
know,
right
enhancement,
degrees.
Those
couple
of
weeks
get
intense,
but
the
rest
of
the
time.
It's
not
too
bad.
D
A
I
mean
we
definitely
want
people
in
the
sigs
to
to
hold
that
bar
and
then
that
makes
it
really
easy
for
us.
A
I
think
it's
worth
exploring,
but
I,
don't
I.
Don't
have
right
now,
Clarity
on
whether.
A
Beyond
the
template,
following
the
template,
you
know
some
of
the
pieces
we're
looking
for.
Are
things
like
how
it
might
affect
other
components
that
aren't
necessarily
the
domain
of
that
given
sick,
so
I
think
it's
it's
a
good
question
and
the
more
we
can
put
mistakes.
The
better
I'm
not
super
concerned
yet,
but
we
should
probably
discuss
it.
C
A
Like
we're
running
an
annual
survey
which
we're
going
to
be
putting
out
shortly,
it's
ready
to
go
I
just
have
to
do
that
and
try
to
then
analyze
the
results
and
compare
that
to
what
we
you
know,
hoping
to
see,
impact
for
the
work
that
we're
doing
or
the
process
that's
been
implemented.
A
And
then
we
have
retrospectives
to
see
how
it
went
to
maybe
make
refinements
or
changes
to
the
questionnaire,
but
other
than
that.
There's
not
a
lot
of
regular
business.
We
don't
get
a
lot
of
pings
from
people
during
the
entire
cycle.
It's
really
just
that
two
to
four
weeks
before
enhancement,
freeze
that
we
really
get
a
lot
of
pings
and
you
know
so
that's
that's
when
what
most
of
most
of
the
work
is.
A
A
D
Yeah,
it's
not
a
strong
pressure
for
me.
John
on
that
I
was
just
wondering
if
you
want
to
use
the
rotation
Point
as
a
reflection
point
to
say
why
not
or
why,
as
is
and
I,
think,
maybe
the
other
thing
we
do
is
just
make
a
point
in
every
sick
call
going
forward
that
we're
at
to
kind
of
give
a
call
to
action
to
see
if
folks
want
to
take
part
in
the
process
that
might
not
have
been
aware
of
it
before.
C
The
only
other
thing
I
can
think
of
Derek
is
you
know,
for
each
thing
to
cough
up,
a
name
that
we
can
use
to.
You
know
get
out,
get
help
during
the
time
that
we
need
that.
That's
the
only
thing
like
the
you
want
to
call
out
specifically
it
could
be
the
TLs
for
each
Sig
should
be
available
for
consultation
when
we
need
them
right.
Yeah.
D
A
Just
say
one
more
thing:
we,
you
know,
we
look
at
our
API
review
process,
our
API
approval
process.
We've
got
a
long
list
of
reviewers
and
a
very
small
list
of
approvers,
which
is
which
is
a
concern
right
and
and
and
and
and
so
we're
kind
of
moving
in
that
same
direction,
which
is
like
not
a
great
I
mean
the
API
proof
of
process
is
five
and
all,
but
like
it's,
it's
not
a
good
position
to
be
in
where
there's
just
a
handful
of
people
that
have
that
much
weight
on
them.
A
A
And
let's
40
minutes.