►
From YouTube: 20210408 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
Welcome
everybody
today
is
april,
8th
2021.
This
is
the
kubernetes
stick
architecture,
community
meeting
and
please
remember
to
be
respectful
to
one
another.
We
have
a
a
relatively
short
agenda
today
up
first,
we
have
rian.
B
A
An
update
on
the
conformance
sub
project.
C
C
There
is
some
freebies
that
came
in
so
there's.
Actually,
I
think
like
32,
that
actually
came
in,
but
from
my
eyes
side
we
covered
28
white
tests.
C
No
problem,
okay,
so
removing
technical
data.
We
are
focusing
quite
a
lot
at
the
moment
on
the
technical
date
of
sick
apps,
which
is
basically
all
one
nine
and
we
manage
within
this
release
to
move
from
48
percent
cover
up
to
62,
which
is
pretty
sweet.
Then
there's
32,
endpoints,
that's
came
in
there.
It's
back.
Okay,.
C
That
from
chrome,
job,
endpoint
slice
and
price
distribution
and
part
of
our
monitoring,
we
managed
to
get
all
those
in
with
this.
Some
of
them
did
come
without
this,
but
the
six
were
very
corporate
they've
got
them
all
sorted.
Then
the
flaky
testing,
everybody
probably
see
the
flaky
test
investigation
going
on
in
the
channels
in
the
mailing
list
and
in
get
up
there's
quite
a
quite
a
bit
of
progress
being
made.
None
of
it's
actually
related
to
the
test,
most
of
the
underlying
bugs
or
the
timeouts.
C
So
it's
not
test
bug
things
then,
looking
forward
to
122
for
122,
we
got
a
target,
20
endpoints,
previously
not
covered
and
again
we're
going
to
focus
on
all
the
the
1
11
to
1,
9
technical
deck
reason
why
the
target
is
going
down.
Is
we're
really
running
into
a
lot
of
underlying
bugs,
specifically
111?
We
want
to
do
111
this
release
already,
but
there
is
underlying
votes
before
which
these
issues
being
opened,
but
even
at
24
next
three
releases.
C
We
will
still
hit
our
goal
of
less
than
75
endpoints
remaining
by
the
end
of
2021,
which
would
be
quite
a
a
nice.
D
C
Slow
the
base
is
going.
What
community?
What
is
really
coming
up
now
is
the
edge
cases,
because
clearly
we
you
would
go
for
the
for
the
low
hanging
fruit
first,
so
the
difficult
stuff
is
left.
D
C
So
we
are
busy
hacking
at
things
that
behave
funny.
We
actually
had
a
good
conformance
meeting
this
week
where
clayton
helped
us
look
at
another
bug,
that's
underlying
another
way
of
patching
because
the
normal
way
doesn't
want
to
work.
So
there
is
really
a
lot
of
funny
things
coming
out
now
and
we
are
picking
up
and
that's
the
point
of
the
testing
we're
picking
about
by
the
testing.
So
it's
it
feels
good
like
we're
doing
what
we're
supposed
to
be
doing
and
if
johnny
want
to
go
to
the
api
sniff
page.
C
A
C
A
Really
great
to
see
so
much
so
much
of
this
tech
that
right
paid
down.
That's
really
nice,
then
we're
getting
to
like
a
really
you
know
new
new
things.
You
know
all
the
new
things
that
came
in
were
promoted
with
tests,
so
it's
we're
we're
not
slipping
backwards
and
we're
making
your
progress.
It's
awesome.
It's
really
awesome.
C
C
254
and
we're
sitting
at
half
of
that.
So
it's
really
really
really
nice.
What
would
be
helpful
if
I
can
soarbox
for
a
moment
if
we
can
have?
I
know
everybody's
been
extremely
busy.
Clayton's
been
very
helpful
in
the
performance
meeting,
but
some
more
support
from
the
different
six
attending
the
conformance
meeting
would
be
helpful
because
we're
dealing
with
what
are
quite
a
bit
of
votes
at
the
moment
so
that
that
would
be
helpful
but
other
than
that
slowly
plotting
along.
D
D
We
can't
numb
up,
like
all
six
show
up
kind
of
thing
right.
So
if
you
can
give
us
like
a
hand
full
of
sick
that
you
want
to
focus
on,
maybe
we
can
rustle
up
some
some
interest.
Yeah
from
the
tech
leads,
if
you
you
said
you
were
trying
to
do
c
gaps,
for
example
right
so.
C
So
what
what
we
do
from
our
side?
We
basically
speak
to
cigarettes
directly
and
they've
been
very
helpful
and
in
this
release
I
attended
a
couple
of
their
meetings
as
well.
So
I
took
a
take
on
performance
to
the
six
right.
B
C
It's
more,
I
must
say,
jordan.
Liggett
always
gives
good
feedback
faith
and
gives
good
feedback.
John
you're
also
a
very
good
support
in
giving
us
feedback.
So
so
it's
basically
having
the
the
expert
in
kubernetes
giving
us
some
feedback
of
what
you
think
of
the
test
and,
and
that
keeps
us
honest
to
make
sure
that
we
don't
just
slip
things
in
for
the
sake
of
getting
them
in
with
we
really
test
what
we
intend
to
and
from
the
feedback
that
john
gave
us
on
status.
C
D
C
D
C
That
and
we
try
and
replicate
things
through
our
different
resources
in
the
same
way.
So
we
have
a
consistent
method
and
we
did
the
same
with
many
of
the
apps
endpoints,
because
stateful
set
replica
says
they
they
work
much
the
same,
so
you
can
follow
similar
patterns.
A
Excellent,
so
I
know
some
of
the
tests.
I
believe
that
we're
added
we're
really
around
the
rest
apis
and
are
we
and
we
have
had
discussion?
I
guess
in
the
past
around
the
test
testing
the
the
functionality
itself
versus
just
the
api
machinery,
and
you
know
in
some
cases
we've
added
tests
or
usually
hopefully,
there's
tests
for
the
already
for
the
end
to
end.
But
when
we've
added
things
to
cover
like
status
patching,
what
are
we
doing?
Are
we
keeping
track
of
of?
A
C
Sorry,
my
internet
broke
up
a
little
bit,
mostly
we're
trying
do
behavior
to
catch
the
actual
behavior
of
the
api
and
the
endpoints
that
do
not
qualify
or
we
cannot
properly
test
all
now
at
the
moment
in
the
eligible
endpoints
list
and
what
the
plan
is
when
we
buy
next
year
property
middle
next
year.
We
hope
to
have
most
of
the
end
points
covered
and
then
we
will
for
sure
have
to
look
back
to
what
is
what
was
ineligible
and
is
that
reason
still
valid,
which
is
at
the
moment
I
think
about
75
endpoints.
C
Roughly
there
is
a
list,
I
think.
If
you
scroll
up
there
you'll
see
the
link
for
the
individuals-
yes
they're
unaligned
at
the
top,
so
there
are
78
of
them
and
these
will.
We
will
look
back
because,
and
most
of
them
are
things
like
storage
and
and
that
proxy
invoice
that
will
be
deprecated
and
then
it's
they.
They
we
took
it
to,
I
think
network
and
they
said
it's
going
to
deprecate
and
then
again
follow-up.
Is
it
actually
going
to
difficult?
And
if
not,
why
not?
C
A
Okay,
awesome,
so
the
only
thing
left
on
our
agenda
unless
somebody
added
something
in
last
10
minutes
is.
We
have
an
annual
report
that
we're
supposed
to
do
and
it
was
due
today
I
believe-
and
it's
not
done
we
have.
We
have
a
start
on
it
and
and
just
before
the
meeting
I
pushed
a
couple
a
couple
small
changes,
so
jim's
had
suggested.
We
take
this
time
to
work
on
that.
I
guess
that's
probably
not
of
interest
to
most
people.
A
I
don't
know
that
we
really
need
to
record
that
it's
really
just
a
working
session,
so
I
guess
if,
if
anybody
who's
interested
in
staying
on
and
helping
out
with
that,
please
feel
free
to.
But
at
this
point
I'm
gonna
stop
the
recording
and
we'll
just
make
a
working
session
and
everybody
who
doesn't
care
can
go
about
their
lives.