►
From YouTube: Kubernetes SIG Apps 20220808
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
Okay,
good
morning,
good
evening,
good
afternoon,
depending
on
where
you
are
today
is
August
8th-
and
this
is
another
of
our
bi-weekly
say
gas
calls.
My
name
is
Pache
and
I'll
be
your
host.
Today,
announcements
I
didn't
put
any,
but
basically
were
roughly
a
day
before
this
test
freeze.
A
So
if
you
have
any
particular
test
PR
that
you
want
to
merge
into
q.25,
I'll
make
sure
to
get
them
tacked
and
merged
by
tomorrow
and
I'll
put
the
links
into
the
exact
date
because,
depending
on
where
you're
located,
it
is
either
halfway
through
afternoon
or
halfway
through
the
night
from
tomorrow
on
to
the
Wednesday
Ken
Janet.
Is
there
anything
else
that
we
want
to
ask
with
the
announcements.
B
Today
is
the
deadline
for
the
co-located
events
submission
to
kubecon
North
America.
We
have
a
batch
Day
event.
Today
is
the
deadline
for
submitting
proposals
if
your
talk
was
not
accepted
to
the
main
event
it
related
to
batch.
Please
feel
free
to
submit
to
this
color
events.
Deadline
is
today
midnight
PST.
A
Okay,
with
that,
we
can
jump
over
to
the
main
topics:
Aldo
Abdullah.
C
Yes,
so
I
wanted
this
I
wanted
to
bring
the
discussion
to
the
table.
As
you
know,
we
we
worked
on
job
tracking
with
finalizers
I.
Think
it's
over
I
think
it's
four
releases
now,
since
we
first
did
the
alpha,
but,
as
you
also
might
know,
we
had
some
some
pitfalls
there.
We
discover
bugs
in
123
124
iteration,
so
we
disabled
the
featuring
124.
C
and
it's
now
enabled
back
for
the
125
release
so
because
of
that
I
can't
I
wanted
to
to
ask
if
it's,
if
you
find
that
it
would
be
good
to
graduate
to
ga
on
126,
and
the
motivation
here
to
run
into
GA
is
to
remove
the
Legacy
code
that
is
making
very
hard
to
maintain
the
job
controller,
because
every
time
we
have
to
add
a
new
feature,
we
have
to
maintain
two
parts
giving
the
the
history
of
you
know,
failures
that
we
I
think
I'm,
confident
saying
that
we
have
like
we've.
C
Every
time
we
have
found
more
and
more
more
and
more
narrow
or
obscure
bugs
so
I
think
the
confidence
is
now
higher
that
the
the
the
job
tracking
with
analyzers
is,
let's
say,
production
ready.
C
So
that's
that's
the
question
I'm
bringing
to
the
table
whether
we
can
graduate
to
GA
in
126
and
basically
also
at
the
same
time
kind
of
proposed
feature
freeze
in
in
in
your
controller
for
126.
So
we
just
focus
on
cleanup
and
graduates.
C
We
would
only
do
graduations
of
any
feature
that
is
already
in
the
pipeline,
but
we
wouldn't
introduce
any
new
Alphas.
So
that's
that's
the
proposal
that
we're
bringing
Abdullah
and
I
so
I
wanted
to
hear
your
thoughts.
B
I
just
wanted
to
clarify
here
is
that
what
all
those
proposing
is
to
remove
the
code
that
we've
been
reverting
to
every
time
we
had
these,
like
you
know,
bugs
until
they
were
fixed,
but
we're
getting
to
the
point
where
it's
just
bug
fixes
like
any
other
controller,
it's
not
that
the
whole
the
the
premise
and
the
algorithm
itself.
That
is
not
there's
something
wrong
with
it.
B
It's
just
we're
discovering
new,
sometimes
new,
really
weird
edge
cases,
but
they're
getting
fixed,
and
so
now
things
are
getting
harder
and
harder
to
do
with
all
the
maintenance
that
we're
doing
with
the
with
the
with
the
other
code,
so
yeah.
A
I
can
personally
add
that
I
I
can
support
it.
I
don't
have
any
parts,
personal
objections
that
particular
code
where
we
were
tracking
the
jobs
with
leaving
the
parts
around
has
been
an
issue,
since
basically
the
exception
of
the
job
controller,
and
we
were
aware
of
it.
Big
thing
for
alto
and
Abdullah
for
for
pushing
this
particular
feature
through
and
improving
the
job
controller
I've
been
pulled
in
four
of
reviews,
every
single
time
that
functionality
was
going
haywire.
A
B
C
Yep
and
and
it's
any
thoughts
on
the
let's
say
feature
freeze-
is
that
something
reasonable
or
does
anyone
have
very
pressing
need
they
need
to?
They
want
to
push
in
126.
A
That
also
sounds
reasonable,
focusing
or
closing
that
particular
controller
for
a
little
bit
to
ensure
the
stability
and
improve
the
overall
quality
of
the
code
and
the
durability.
Readability,
especially
after
we've
removed
the
double
paths
with
the
job
tracking
with
finalizers.
A
A
Maybe
not
necessarily
the
graduation
of
a
job
Trucking
with
finalizers,
but
sending
an
email
about
freezing
the
job
controller
for
126
would
be
a
good
to
send
out
to
the
say,
that's
mailing
list
so
that
we
so
that
the
people
who
are
not
necessarily
attending
the
today's
meeting
can
also
be
aware
that
this
is
a
thing
that
we're
we
will
be
enforcing
in
126..
A
A
Ryan
has
been
on
our
previous
calls
a
couple
of
times
in
the
past,
we've
been
usually
reaching
out
to
us
to
either
report
the
progress
of
the
apps
endpoints
and
their
coverage
with
recent
vrs
that
we
emerge
I
think
a
week
or
two
weeks
ago
we
reach
100
test
coverage
for
all
of
the
apps
and
points
which
is
one
of
the
goals
that
Ryan
and
his
group
is
going
after.
A
Okay,
so
the
last
topic
I'll
try
to
pronounce
your
name
correctly:
ferns,
War,
I,
I,
hope,
I
didn't
close
enough.
D
So
I
was
absent
for
a
pretty
long
time.
I've
got
a
bit
so
I,
also
texted
you
and
slack
about
that
I'm
just
here
to
just
lay
out
the
expectations
like
what
you
were
supposed
to
do
in
the
group
mentoring
thing
and
when
it's
gonna
start
and
how's
the
frequency
gonna
be
so
since
you
know
the
group
mentoring
God
for
the
CLI
thing
has
already
been
kicked
off.
So
I
was
thinking
that
maybe
we
can
also
start
with
this
next
week.
It's
possible.
D
Yeah
because
Paris
isn't
there
she's
out
on
a
medical
day,
there's
15,
so
maybe
I
was
thinking.
I
was
thinking
that
eighth
week
of
today
only
but
today
would
be
very
fast
I
guess.
So,
let's.
A
A
A
Know
the
invitations
on
Wednesday
morning
for
Wednesday
afternoon
so
yeah
definitely
next
Monday
should
be
enough,
and
probably
we
would
pick
a
time
slot
after
this.
The
gaps
I
remember
correctly,
that's
something
similar
to
what
we
did
for
for
six
CLI
as.
D
A
D
Exactly
and
as
you
know
so
since
we're
starting
on
the
August
of
15,
that
will
basically
cover
the
Rules
of
Engagement
to
people.
You
know
like
the
mentors
and
the
mentees
will
have
a
face-to-face
interaction
like
they
will
know
what
they
are
expecting
to
do
like
being
a
reviewer
how
to
land
in
the
owner's
file
and
all
that
expectations
of
clamping
up
the
ladder
in
the
contribution
thing.
D
So
that
is
upon
the
kickoff.
Basically,
and
another
thing
is
we're:
gonna,
do
a
Buy
weekly
meeting
rate.
A
A
D
It's
going
to
be
a
Buy
weekly
meeting
on
Mondays
and
on
every
Monday.
There
will
be
a
slack
stand
up
and
the
mentors
are
expected
to
be
there
and
help
out.
But
it's
not
a
teacher
and
student
thing.
It's
a
mentoring
thing,
so
they're
gonna
just
help
with
some
resources,
some
videos
and
stuff
like
that.
But
if
so,
it
should
not
be
pretty
hectic
on
you.
D
It
should
be
light
on
you,
that's
the
expectation
out
of
this
program,
and
so,
if
you
are
feeling
burdened
or
any
kind
of
thing
like
that,
we
request
you
to
just
DM
Paris
or
let
any
of
the
coordinators.
Like
me
or
Arthur,
know
about
this
thing.
D
Itself
we
have
mentioned
there
are
other
things
like
we
have.
There
are
other
cohorts
of
this
mentoring
thing
which
has
been
done
earlier
and
the
it
the
process
we
are
expecting
is
we're
gonna,
do
some
release
cards
and
like
cherry
picking
in
a
deep
dive
and
how
things
are
done
in
a
structured
manner
and
all
that
stuff.
D
So
this
is
that
and
other
thing
that
Paris
mentioned
in
the
CLI
meeting,
which
is
I,
think,
is
pretty
important
that
mentors
need
to
assign
topics
to
themselves
and
they're
gonna
be
two
things:
it's
one
is
a.
If
you
can
do
a
sub
project,
team
type
or
they're
gonna
be
a
refuted
type,
and
what
do
you
mean
by
reputive
type?
Is
a
mentor?
Is
gonna
go
through?
D
D
A
Oh
we're
gonna
Focus,
just
on
the
controllers,
I
think
I
put
it
in
the
academy
as
well
already.
D
D
A
Yeah
yeah:
we
want
to
focus
just
on
the
main
kubernetes
repository
for
this
particular
group.
We
don't
want
to
talk
to
any
of
the
some
projects.
D
Yeah,
thank
you
and
I
talked
about
the
time
commitments
and
since
this
is
basically
a
three-month
process,
so
like
from
being
a
contributor
to
a
reviewer,
since
you
know
like
most
of
the
participants
or
the
mentees,
they
have
self-selected
themselves
to
be
in
this
process
and
we
are
not
sure
about
their
qualification
in
say,
gaps
or
their
experience
in
doing
stuff
inside
apps.
So
this
is,
we
don't
have
any
expectation
out
of
them
that
any
of
them
is
going
to
land
in
a
bonus
file.
D
But
who
is
the
aim
of
this
program?
Is
that
at
least
50
go
into
that?
But
nothing
is
guaranteed
out
of
this.
So
this
is
basically
an
accelerated
process
and
we
would
like
mentors
to
be
available
on
all
the
days.
But
it's
okay
to
you
know
like
it
shouldn't
be
a
burden
on
you,
as
I
just
said,.
D
And
also,
if
someone
out
here
in
the
meeting
is
willing
to
help
in
this
process,
like
you
have
enough
experience
and
you
want
to
Pro
help
this
mentees
in
the
process
of
becoming
a
reviewer,
you
are
very
very
welcome
to
the
process.
Please
let
us
know-
and
we
will
sign
you
up
in
in
the
that
we
have
a
private
slack
and
we
can
let
you
in
and
can
help
us
in
the
process
too.
D
So
I
wanted
to
say-
and
there
is
one
such
question-
that
what
if
the
mentees
are
very
very
lost
yeah
so
like
it's,
it's
gonna
happen
like
since
most
of
them
self-selected
themselves,
so
we
are
not
expecting
any
kind
of
experience
out
of
them.
So
your
job
is
to
be
a
mentor
and
not
a
teacher,
and
you
can
just
provide
reading
materials.
You
know
references
any
issues,
so
they
can
invest
their
time,
learning
20
30
hours.
D
A
Thanks
very
much
does
anyone
have
any
particular
questions
for
foreign.
E
Topic
so
to
make
their
process
more
efficient,
that's
the
the
partitions
has
to
make
sure
that
they
already
see,
for
example,
the
presentation
that
might
say
you
served
and
any
other
documentation
that
we
should
cover
and
prepare
for
our
search
in
order
to
make
the
whole
process
efficient.
A
A
Together
all
the
information
and
that
I
can
be
as
we
go
all
the
information
I
can
have
before
the
next
kickoff
I'll
make
sure
that
it
is
linked
there
and,
as
we
will
be
going
I'll
be
sharing
all
the
additional
information,
if
all
find
something
that
I
just
missed
before.
E
Super
cool
thanks
and
one
more
a
is:
do
we
have
to
start
working
on
an
issue
like
good,
first
issue
thing
or
we
should
wake
the
develop
the
whole
process
unveiled,
and
then
we
can
start
working
on
something
either.
D
A
A
Be
working
on
it
so
that
we
have
some
some
rough
overview
for
the
matter
for
the
next
kickoff
sure
cool.
Thank
you
very
much.