►
From YouTube: 20200507 SIG Arch 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
All
right
I've
started
recording
this
is
the
sega
architecture
meeting
for
kubernetes
for
may
7th
2020..
Thank
you
all
for
coming.
Please
abide
by
the
humanities
code
of
conduct
and
with
that
we
will
begin
the
only
thing
really
on
the
agenda
today
are
the
sub
project
readouts.
So,
as
we
mentioned
in
the
last
meeting,
we
have
a
new
sub
project,
which
is
the
enhancement
sum
project,
so
that
team
will
be
doing
the
first
readout
for
this
meeting
today,
but
to
start
with
the
production
readiness
subproject.
A
So
this
has
been
progressing
well,
we
have
a
camp
out.
There
changed
to
the
cap,
template
out
there
right
now,
there's
a
link
there.
It's
emails
were
sent
out
earlier
this
week
to
dev
and
the
chairs
and
tech
leads
or
kubernetes
to
start
at
least
a
consensus.
I'm
merging
that.
Essentially
that
says
that
in
1.19
we
will
expect
capital
authors
to
fill
out
the
questionnaire.
It
adds
the
questionnaire
to
the
cap
template.
A
Words,
we're
not
going
to
deny
a
an
enhancement
being
part
of
the
release,
because
it's
production
readiness
has
not
been
approved,
but
they
do
need
to
fill
it
out
a
lot
of
the
production
writing.
This
piece
is
just
to
force
people
to
think
through
issues
they
wouldn't
otherwise,
so
we
actually
get
quite
a
bit
of
the
benefit
just
by
doing
that,
but
nonetheless
we
need
to
measure
the
kind
of
review
load
that
that's
going
to
put
on
the
team
and
get
a
better.
A
As
part
of
that
cap,
rather
that
er,
we
also
are
trying
to
add
in
some
things
for
tooling
jeremy,
we'll
talk
about
that
a
little
bit
next
in
enhancements,
but
we're
working
closely
with
that
team
to
with
the
enhancements
team
rather
to
to
try
and
make
those
reviews
when
we
do
get
to
like
an
approval
required
for
those
narrow
reviews,
try
and
make
them
as
light
as
possible
and
not
become
a
bottleneck
for
the.
C
D
A
Awesome:
okay,
yeah,
that's
the
zoom
web
client,
okay.
Jeremy
says
his
laptop.
Just
crashed
awesome!
Okay!
Well,
if
we
want
why
don't
we
skip
enhancements
for
now
until
jeremy
gets
back
online
and
in
the
meantime
hippie?
Why
don't
you
do
the
readout
for
conformance.
F
Yes,
we'll
do.
Thank
you,
john
one
of
the
big
changes
that's
affecting
all
of
us
is
the
change
in
release
cycle,
so
the
dates
to
which
we
can
submit
tests
and
and
promotions
have
been
moved
forward
so
july.
16Th
and
july
30th
are
new
deadlines
for
that.
We've
also
kind
of
updated
our
our
okrs
to
reflect
that
period
cycle.
So
I
think
we're
going
to
go
for
the
same
amount
of
increase,
but
we're
going
to
be
doing
it
towards
the
end
of
july.
F
Instead
of
the
end
of
end
of
june,
we've
got
16
new
endpoints
that
are
not
part
of
conformance
a
lot
of
these
endpoints
for
ones.
We
can't
test
yet
feel
free
to
click
on
the
link.
If
you
want
to
see
that
full
list,
this
was
agreed
on
on
our
last
meeting,
but
would
love
to
get
other
people's
feedback
for
other
things
that
shouldn't
be
part
of
conformance,
so
they're,
not
part
of
our
denominator.
F
As
far
as
moving
things
forward,
we'll
update
the
api
snoop
ui
to
reflect
this,
and
it
will
show
a
3.6
increase
in
coverage.
Again,
our
goal
is
50
where
our
stretch
goal
is
50
for
the
quarter
or
for
the
for
the
1.19.
F
We
also
found
some
patterns
that
needed
to
have
some
tooling
written.
So
we
have
two
open
ready
to
approve.
F
Test
test
helpers:
this
will
unblock
a
lot
of
points
that
are
sitting
in
the
queue.
So
if
you
have
the
ability
and
the
knowledge
please
do
give
us
an
lgtm
in
our
approve
on
those
two
tools
to
support
our
testing
efforts.
We've
got
a
pretty
good
flow
going
within
our
conformance
subgroup.
As
far
as
approving
work
before
we
go
through
and
write
it
because
we
have
a
lot
of
people
with
varying
skills
that
are
that
are
ramping
up
and
how
they
can
write
tests.
F
It's
a
lot
to
learn,
so
we
go
through
and
write
these
these
files,
these
org
files
that
create
an
output
of
a
of
a
markdown
issue
and
those
issues
are
what
we
go
through
in
our
two
triage
during
the
meeting
and
one
cool
example
is
steven
hasn't
written
tests
before,
but
he
put
forth
three
related
tests
and
we
said
those
look
great,
but
would
you
mind
parameterizing
those
so
that
we
can
have
one
test
that
will
give
us
those
those
three
extra
points:
caleb
who's,
a
who's,
a
seasoned
tester.
F
At
this
point,
I
was
able
to
have
a
a
mock
test.
If
you
will
to
get
approved
it
says,
should
we
write
this
and
it's
it
can
be
destructive.
So
if
you've
got
thoughts
around
damon
set
particularly
around
how
we
can
schedule
things
like
there
was
some
some
conversations
there
that
he
needs
to
rewrite
that
there
are
other
ones,
but
for
this
meeting
I
just
want
to
give
us
a
feel
of
how
that
flow
is
going
and
definitely
for
for
people
that
can
approve
the
promotions.
F
We
have
three
that
are
past
the
two-week
soap
point
and
are
ready
to
increase
those
numbers.
So
if
you
can
do
some
due
diligence
on
those
and
promote
those
that
would
be
lovely,
otherwise
things
are
doing
well
and
I'm
I'm
happy
to
be
happy
to
be
here.
A
A
B
Was
thank
you
sorry
about
that.
I
went
to
click.
I
went
to
click
on
mute
and
everything
froze
and
then
my
laptop
died.
Awesome,
yeah,
perfect
timing.
So,
as
john
mentioned
a
little
bit
earlier,
the
enhancements
subproject
is
new
to
sig
architecture,
some
of
the
functionality,
some
of
the
responsibilities
that
were
part
of
cpm
kind
of,
I
guess
cpm
dissolved-
became
the
enhancements
sub-project
under
sticker
architecture.
So
we're
kicking
that
off
right
now,
just
a
couple
of
updates
to
give
everybody.
B
We
have
a
mailing
list
at
currenties-caps
at
google
groups,
so
you
should
go
join
that
if
you're
interested
in
any
news
or
anything,
we
publish
there
first
big
one
in
terms
of
the
changes
coming
to
caps.
There
was
pr
that
I
inadvertently
didn't
add
to
the
meeting
notes,
link
I'll
do
that
after
this,
but
basically
it
changes
the
structure
of
caps
and
moves
towards
a
more
directory
oriented
more
kind
of
standard
easier
for
tooling
to
discover
structure
so
that
pr
has
merged
and
again
I'll,
add
the
link
to
that
after
this.
B
Second,
really
big.
One
is
that,
as
john
mentioned,
there's
a
pr
right
now,
1620
that
he
referenced
up
above
and
while
that's
mostly
cons,
you
know
around
the
production
readiness
review.
There
are
a
few
pieces
of
metadata
that
are
going
to
get
added
to
keps.
Specifically,
we
are
adding
if
I
can
find
the
browser
window.
B
Stage
so
it'll
say
alpha
beta
more
stable.
Let
me
share
my
screen.
B
C
Yeah,
so
you
can
either
do
that
or
if
you
need
to.
B
B
How's
that
yeah
okay,
so
some
new
things
that
are
getting
added
here.
Obviously
the
stage
for
the
cap,
the
latest
milestone
we'll
show
you
when
the
last
time
delivery
of
work
was
done
for
this.
So
whenever
changes
were
merged
for
this
at
the
end
of
the
release,
we'll
update
this
to
show
when
you
know
the
latest
activity
was
and
then
finally
some
additional
milestone
information.
Some
of
this
was
found
in
the
the
kep
issue.
B
At
the
you
know,
the
top
of
the
issue
when
people
would
describe
things
out,
it
wasn't
always
kept
up
to
date,
and
you
know
there's
some
issues
with
people
picking
up
keps
after
some
work
have
initially
been
done
and
not
having
the
ability
to
edit
those
things
themselves.
So
we're
adding
it
here
as
part
of
the
metadata,
so
it'll
force
a
pr
to
update
those
things,
but
it
also
enables
to
do
some
more
tooling
along
the
way,
just
adding
some
more
metadata
to
make.
B
B
C
So
can
you
hear
me:
okay,
sorry,
yep,
okay,
cool,
so
yeah,
so,
just
to
add
on
to
what
jeremy
was
saying
we
are
some
of
these.
Some
of
these
enhancements
will
allow
you
enhancements
to
the
enhancement.
Enhancements
will
allow
you
to
more
easily
update
the
issues,
but
also
in
terms
of
searching
as
we
move
into
having
a
kep
website,
which
should
be
coming
soon.
C
The
idea
that
you'll
be
able
to
map
against
like
latest
milestone
and
the
stage
that
that
a
cap
is
currently
in
or
get
a
projected,
or
you
know
a
idea
of
what
the
the
first
time
that
kept
went
into
alpha
or
beta
or
is
proposed
to
go
into
ga
right,
so
we're
adding
that
metadata
to
kind
of
hopefully
get
more
more
information
out
of
the
various
querying
tools
that
we're
going
to
be
building
the
if
you're,
not
in
this
meeting,
and
you
catch
this
later.
C
We're
planning
to
send
an
email
related
to
all
of
this.
So
don't
worry
that
you're
missing
anything.
If
you're
not
here,
it
will
be
very
detailed.
I've
added
a
link
to
the
sig
release,
caps
that
I've
cleaned
up
into
the
directory
structure,
so
you
can
check
out
exactly
commit
my
commit
by
commit
how
you
would
want
to
do
that
yeah!
That's
it
for
me!.
A
C
A
We
had
to
have
one
question
in
the
chat:
it's
not
not
necessarily
the
sort
of
thing
we
usually
talk
about
here,
but
since
we
have
a
few
minutes,
if
anybody
has
an
answer
I
mean
you
can
use
something
like
sono
buoy,
but
there's
a
thousand
questions
in
there
of
how
you're
setting
things
up.
I
don't
know
that's
an
easy
question
to
answer.
You
may
want
to
reach
out
on
slack
for
that.
A
Any
other
comments
to
that
question.
If
you're
not
reading
the
chat,
the
question
is
suggest
a
tool
to
check
whether
the
setup
of
an
on-prem
cluster
is
done
correctly.
A
All
right,
okay!
Well!
Thank
you
everybody.
If
there's
no
more
questions,
we
will
call
it
for
today,
and
everybody
have
a
wonderful
time
and.