►
From YouTube: Carvel Community Meeting - September 30, 2021
Description
Carvel Community Meeting - September 30, 2021
We meet every Thursday at 10:30am PT. We'd love for you to join us live!
Full details on this week's agenda found here: https://hackmd.io/F7g3RT2hR3OcIh-Iznk2hw#September-30-2021-Agenda
A
Hello
and
welcome
to
this
week's
edition
of
the
carville
community
meeting
today's
date
is
september.
30Th
2021.
If
you
are
watching
this
from
home
or
the
future,
we
encourage
you
to
come.
Join
us
live.
We
meet
every
thursday
at
10,
30
a.m.
Pacific
time
this
opportunity
to
listen
in
to
what
the
maintainers
are
working
on,
provide
feedback,
ask
questions
or
get
live,
help
with
any
of
the
tools.
If
you
aren't
able
to
attend
live,
you
can
also
find
us
on
the
kubernetes
slack
workspace
under
hashtag
carvillechannel
and
on
twitter
at
carvilleunderscoredev.
A
When
you
attend
these
meetings,
we
ask
that
you
please
read
and
abide
by
our
code
of
conduct
and
if
you
have
anything
you
wish
to
discuss
with
the
team,
please
add
that
to
the
discussion
topics
section
at
the
end
of
the
agenda.
Additionally,
when
you
attend,
we
ask
that
you
input
your
name
and
any
organization
you
represent.
This
is
so
we
can
know
who
from
the
community,
is
attending
and
keep
those
lines
of
communication
open.
A
A
As
a
reminder,
we
do
have
the
carvel
keynote
at
kubecon
coming
up
soon,
breaking
the
tradition,
the
future
of
package
management
with
kubernetes,
given
by
our
own
director
ripa
and
on
that's
on
friday
october
15th
9
40
to
9
45..
I
think
there's
also
going
to
be
a
recording
available
asynchronously
and,
of
course,
you
can
give
us
feedback
regarding
your
package
management
experience.
A
A
B
A
C
C
Yup
that
works.
Thank
you.
So
what
we're
looking
to
do
with
this
enhancement
is
ramp
up
the
existing
app
change
functionality
which
we
have
so
today.
Let's
see
you
make
a
bunch
of
changes
using
cap
and
you
do
something
like
cap
app
change
list,
while
naming
the
app
you
get
a
bunch
of
changes,
you've
made
to
the
app
over
the
over
time,
but
right
now
all
you
can
see
is
mostly
the
duration
of
the
change
that
was
occurring,
the
status
of
it
and
the
operations
that
were
performed.
C
So
we
were
planning
on
enhancing
this
feature
by
letting
the
user
access
the
text.
If
that
was
applied
for
that
particular
change,
so
we
were
hoping
to
do
something
like
if
the
user
runs
app
change
describe
and
the
name
of
that
particular
change.
The
user
will
be
able
to
access
the
tech
stuff
for
that
particular
change.
So,
along
with
that,
we
wanted
to
improve
how
we
are
acquiring
the
app
changes
in
the
first
place.
C
So
maybe
you
want
to
get
app
changes
for
a
particular
frame
of
time
or
you
want
to
paginate
through
the
changes,
so
you're
planning
on
adding
flags.
For
that,
so
that
the
user
can
query
the
app
changes
easily
and
in
addition
to
that,
we
want
to
help
the
user
easily
declutter
any
app
changes
like
app
changes
are
tracked
using
config
maps
on
the
cluster.
So
you
want
the
user
to
be
able
to
easily
do
something
like,
let's
say,
keep
the
10
most
recent
changes
and
drop
the
rest
of
the
changes
to
declutter
historical
cluster.
C
So
that's
what
we're
working
towards
and
that's,
where
app
change,
delete
steps
in.
So
what
we're
trying
to
do
is
we're
mainly
trying
to
help
people
who
are
con
consuming
cap
and
like
automated
processes,
let's
say:
you're
deploying
something
using
cap
every
half
an
hour
or
so,
and
you
want
to
just
go
back
and
see
what
that,
what
a
particular
change
actually
did.
So
that's
the
scenario
which
we're
trying
to
look
at.
We
would
love
to
get
thoughts
on
what
you
would
like
to
see.
C
If
you,
if
you
had
like
an
order,
trail
of
the
changes
that
you
were
applying
and
how
you
would
you
know
like
to
interact
with
your
app
changes.
Maybe
you
want
to
query
them
in
a
certain
different
manner.
Maybe
you
want
to
filter
labels
or
something
like
that,
so
yeah,
that's
what
we're
working
towards
and
we
would
love
to
get
your
thoughts
on
that.
C
B
D
Yeah
this
this
makes
a
lot
of
sense
to
me
and
seems
like
a
great
way
to
just
provide
more
of
that
observability
into
the
the
tools
and
diving
into
the
specific
things
you
need,
especially
over
time
as
the
list
of
changes
can
become
become
quite
long,
so
yeah.
This
seems
like
an
awesome,
awesome
proposal
here.