►
From YouTube: Kubernetes SIG Apps 20221003
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
and
now
we're
recording
welcome
all
to
the
October
3rd
2022
meeting
of
State
apps,
going
to
bring
up
the
agenda
and
post
it
into.
B
The
chat.
A
B
All
right,
so,
if
you'd
like
to.
C
Start
us
off:
please,
thanks
I
thought
we
were
done
with
all
the
apps
endpoints,
but
there
is
still
two
that
we
discovered
in
sitting
in
core
so
already
reviewed.
Thank
you
very
much.
The
ballistic
apps
people
that
help
with
that
desperate
is
looking
good
I
had
it
on
the
agenda
and
then
all
these
good
things
happened.
So
I
thought
it
would
be
rude
not
to
come
around.
To
say
all
is
good.
Thanks
for
the
review,
so
I'll
be
back
on
the
14th
of
October
with
a
promotion
PR.
C
If
all
go,
it
all
stay,
green
and
desperate,
and
that
should
be
the
last
of
the
ABS
influence
getting
tested
like.
Could
the
good
news
is
that
we
are
always
there
when
it
comes
to
conformance
progress
with
me.
I
can
share
copy
that
and
share
this
in
the
chat.
C
We
will
reach
100
performance
testing
of
which
line
already
have
e
to
e
test,
so
we
hope
by
Keep
Calm
in
Europe.
We
will
be
able
to
announce
100
performance
testing
of
all
advice,
apis,
that's
from
ga.
B
C
That's
why?
But
thank
you
very
much.
I
think
ABS
has
been
very
helpful,
just
a
point
that
I
might
well
while
I'm
at
it
that
I
might
want
to
mention.
C
There
was
a
talk
of
consolidating
tests,
but
last
year,
this
time
when
we
submitted
the
loss
or
the
apps
endpoints,
because
there's
a
lot
of
tests
where
there
is
testing
of
influence,
bringing
up
one
or
two
endpoints
and
then
bringing
it
down
testing
something
I'll
bring
up
a
new
test,
bring
it
down
so
we're
looking
at
next
year
when
we're
done
with
this
we'll
come
back
to
city
apps
and
start
making
a
life
cycle
tests
where
we
test
all
of
the
variations
of
a
specific
endpoint
in
one
single
test
and
try
and
reduce
the
the.
C
My
not.
A
A
Thank
you
so
much
okay.
Moving
on
the
next
item
is
a
bug
about
the
appointment,
available,
condition.
A
B
A
So,
let's
see
if
we
can
figure
out
exactly
so,
this
is
for
context.
This
is
all
about
this
Catherine
PR.
In
order,
that's
attempting
to
unify
the
status
and
conditions
across
the
workload
controllers.
B
Up
I
think
Philip
is
out
today.
There's
a
holiday
in
Germany,
yeah,
I,
think
he's
just
raising
awareness
about
the
cap
has
been
open
for
a
while.
There
has
been
several
discussions
in
the
cap
and
originally
in
the
in
the
API
PR
that
Philips
submitted
a
couple
of
months
back
when
he
was
trying
to
consolidate
the
first
time
the
conditions
and,
if
I
remember
correctly,
the
comments
from
Daniel
was
that
available
is
not
necessarily.
B
Necessarily
means
that
you're
I
don't
know
deployment
or
replica
set
is
fully
available,
as
in
all,
pods
are
running
that
you
would
expect
that's
why
he
is
proposing
to
change
how
this
is
being
defined.
Currently.
B
So
probably
it
will
be
good
if
folks
could
have
a
look
at
that
cap
and
comment
with
their
own
experiences
and
suggestions
about
the
path
will
work.
A
Okay,
but
if
he's
not
or
yeah
I
think
it's
a
he
he
or
they
are
not
here
to
I,
don't
want
to
misgender
anyone
or
not
there
to
talk
about
it,
we'll
I,
guess
we'll
move
it
to
the
next
time
and
then
Peter.
D
Yeah
so
I'm
just
bringing
this
up
for
review,
so
I
think
I
raised
this
previously
and
like
it
was
a
way
back
back
in
like
June.
D
So
this
is
a
cap
that
would
add
an
additional
field
to
the
staple
set
spec
to
enable
the
asserting
ordinal
to
be
modified
implicitly
of
zero.
The
cap
would
allow
that
to
be
an
arbitrary
integer,
and
the
use
case
here
is
really
supporting
cross-cluster
migration.
So
this
cap
I've
moved
it
under
Sig
multi-cluster.
It
does
align
with
some
of
the
use
cases
in
multi-cluster,
but
the
code
changes
are
all
in
the
staple
set
and
so
just
like
to
raise
this
topic
back
up.
D
A
D
A
Yeah
I
mean
I
think
they
should
be
involved
because
of
the
use
case,
alignment
and
you're
not
going
to
have
to
do
anything
you're
not
doing
anything
specific
with
the
persistent
volume
orchestration.
A
Right,
so
your
your
path
forward
is,
you
want
to
add
the
you
want
to
add
this
to
staple
set
first,
but
are
you
so
okay,
like
when
you're
doing
the
the
persistent
volume
juggle?
Let's
just
take
the
three
major
Cloud
providers,
right,
let's
say
or
let's,
let's
add
Oracle
now
so
on
any
of
those
when
you're
doing
the
persistent
storage
juggle
like
there's
a
whole
other
thing
than
just
scaling
up.
A
The
staple
set
like
you're
gonna
have
to
set
the
PVC
to
retain,
delete
the
PPC,
create
a
new
PVC
that
references,
the
persistent
disk,
slash,
EBS
volume,
slash
Azure
this
volume
instead
of
a
new
cluster,
do
another
dance
in
order
to
make
sure
that
it
actually
gets
adopted
and
the
PVC
gets
created,
and
then
you're
gonna
have
to
do
that
in
conjunction
with
scaling
up
the
staple
set.
So
the
patch
for
the
staple
set
thing
is
nice
and
I?
Don't
I,
don't
think
it's
like
bad,
but
like
are
we?
D
See
yeah
so
I
think
those
aspects
of
like
orchestrating
like
those
can
certainly
be
done
from
an
operator
perspective,
and
so
that's
it's
not
something
that
I've
like
prototyped
and
cut
it
up
specifically
for
like
having
that
as
an
open
source
contribution.
But
it's
something
that
you
know
it
could
be
a
leverage
as
a
library
in
golang
that
an
operator
could
use
for
moving
over
persistent
volumes.
I
think
it
is
kind
of
cloud
dependent,
though,
based
on
like
what
the
target
is,
what
the
source
is.
A
It
is
going
to
be
Cloud
dependent
but
like
it's
a
thing
again,
small
patch
great
kind
of
ambition,
but
if
we
make
the
patch
into
staple
set
and
then
we
don't
have
anything
to
offer,
anyone
to
actually
leverage
like
is
the
intention
to
actually
offer
something
in
the
future
so
that
other
people
can
leverage
it.
Or
is
it
going
to
be
primarily
for
your
internal
use.
D
A
D
D
See
where
it
goes,
and
you
know
if
we
can
get
more
traction,
you
know
prototype
things
out
and
we
look
towards
graduating.
It.
A
A
If
we're
going
to
do
that,
then
how
are
we
going
to
verify
it
right
like
what
like
what
is
it
without
any
use
cases
in
the
community
or
any
kind
of
like
commitment
to
build
some?
So
people
can
actually
verify
this
album
open
source?
How
do
we
get
it
to
a
beta
level,
stability
or
a
ga
level,
stability,
yeah.
D
A
Yeah
I
mean
something
we
can
use
or
like
either
Implement
like
it's
it's
kind
of
hard
to
like.
So
we
do
this
and
we
can
say
this
feature
works
and
it's
not
a
heavy
burden
to
carry
it
and
like
I
I,
certainly
can
see
how
this
would
be
useful
for
my
own
use
cases
internally,
but
to
make
it
more
useful,
broadly
to
the
community.
A
It's
like
okay.
Is
there
anything
we
can
do
here?
How
can
I
help
you
get
some
people
around
it
to
build
something
in
the
open
source,
either
I,
don't
know
as
a
working
group
or
whatever
in
order
to
actually
get
something
that's
available
for
people
to
utilize,
maybe
just
maybe
not
universally,
but
at
least
across
a
couple
of
major
Cloud
providers,
so
that
we
can
like
have
confidence
in
promoting
it
forward.
D
Yeah
and
I
mean
like
certainly
read,
write.
Many
solutions
can
work
with
this
without
needing
a
lot
of
you
know,
PV
PVC
juggling,
and
that
could
be
like
you
know,
an
initial
use
case
that.
A
I
was
thinking
of
because
rewrite
money
is
like
you
know.
You
see
that
a
lot
for
oh
basically,
machine
learning,
notebooks
use
cases
like
that
right,
so
yeah,
okay,.
D
A
D
A
Anybody
have
anything
else
or,
like
everybody,
should
go
check
out
the
cap
for
sure
if
they
haven't
already
does
anyone
have
anything
to
add
or
any
other
questions.
A
B
A
Cool,
hey
Phillip
we
can
back
up
and
so
which
what
was
the
discussion
you
wanted
to
have
around
the
convergence
of
conditions
and
status
for
the
workplace
controllers?
Hand
it
over
to
you.
A
A
So
we
can't
hear
you
do
you
think
we
should
reschedule
given
that
the
internet
is
choppy,
so
we
can
make
this
work
out
like
it's
fine
for
US,
unless
it's
critical
for
you
to
try
to
do
it
now
or.
A
A
There's
nothing
else,
then
we
will
give
back
38
minutes
thanks
everyone
for
attending
thanks
everyone.
You
brought
a
discussion
topic
or
presented
the
success
for
ede
and
see
you
all
next
time.