►
From YouTube: Carvel Community Meeting - May 10, 2023
Description
Carvel Community Meeting - May 10, 2023
We talked about two open job reqs, items the team is working on, and GCP Cherry Pick Bot. Notes can be found here: https://hackmd.io/G8dN30WvQl-8Sirnp8AgRA#May-10-2023-Agenda--
A
Hi
everyone
welcome
to
this
week's
edition
of
the
Carvel
community
meeting.
Today's
date
is
May
10
2023..
If
you're
watching
this
recording
from
home,
we
come,
we
encourage
you
to
come,
join
us
live
we
meet
every
second
and
fourth
Wednesday
of
the
month
at
8,
A.M
Pacific
time
we
haven't
met
in
about
two
months
due
to
some
scheduling,
conflicts
and
kubecon,
and
you
know,
teams
just
been
really
busy
there
and
now
we're
back
and
and
we're
ready
to
have
these
meetings
regularly
again.
A
So,
if,
if
you're
watching
this,
we
encourage
you
to
come
join
us
the
fourth
Wednesday
of
the
month
of
this
month
at
8am
Pacific
time
and
you
can
bring
any
discussion
topics
you
wish
to
you
wish
to
bring
up
with
the
team.
You
need
help
with
anything
on
the
Carville
tools.
If
you
have
any
feedback-
or
you
know
just
anything
in
general,
regarding
Carvel,
we
would
love
to
to
talk
to
you
and
meet
you
and
for
those
that
are
on
the
the
meeting
today.
A
Just
a
reminder
to
please
add
any
discussion
topics
you
wish
to
bring
up
at
this
meeting
at
the
end
of
the
agenda
and
we
will
get
to
it
after
we
go
over
some
announcements
and
status
updates
if
you
are
unable
to
join
us
for
these
meetings
live,
and
you
still
wish
to
reach
out
to
us.
There
are
several
ways
to
get
in
touch.
You
can
find
us
in
the
Carville
Channel
and
the
kubernetes
select
workspace.
A
A
If
you
are
using
Carvel
tools,
so
if
you're
using
ytt
cap
controller
any
of
the
tools
at
all,
we
would
like
to
know
how
you're
using
those
tools.
So
we've
created
a
pinned
issue
here
and
just
ask
for
you
to
provide
a
little
bit
of
information
about
yourself,
a
company
that
you're
representing
you
know
just
the
any
contact
information
and
then
your
scenario
for
how
you're
using
the
Carvel
tools.
This
helps
us
learn
more
about
how
folks
are
using
the
tools
just
to
better
understand.
A
Maybe
you
know
new
features
or
bugs
or
anything
like
that
and
also
helps
the
community
understand
how
others
are
using
cardboard
tools.
So
they
know
maybe
some
new
and
interesting
ways
how
to
use
the
tools
as
well.
So
we
ask
that
you
just
put
it
in
a
comment
here
and
you
can
provide
your
logo
and
a
PNG
version
and
we'll
get
it
added
to
the
adopters
file.
A
B
So
we
are
looking
for.
These
are
basically
the
essentially
the
same
position,
just
two
two
additional
people
to
work
on
the
carball
tools
in
helping
our
cus,
our
community
with
any
enhancements
feature
requests.
As
Nancy
mentioned,
we
have
been
very
busy
with
the
donation
and
now
we're
trying
to
get
more
into
a
productive
mode
of
being
able
to
contribute
back
and
acknowledge
the
the
requests
coming
in
and
faster
support.
B
C
D
C
B
A
A
So
for
those
of
you
who
are
familiar
with
Renu,
she's
engineering
manager
and
and
she's
been
really
active
in
the
community
as
well,
and
so
you
would
be
in
good
hands
for
sure
recording
to
her.
So
if
you
have
any
questions
whatsoever,
please
reach
out
to
us
in
any
of
the
aforementioned
contact
and
we'll
we'll
get
to
you
and
we'll
see.
If
this
is
a
good
fit.
B
A
A
Thanks
Anthony
all
right,
so
another
announcement
is,
we
have
a
new
mix,
so
we
were
using
Google
Groups
before,
but
now
that
we're
cncf
project,
we
have
a
fancy
new
mailing
list,
so
we
are
going
to
be
no
longer
using
the
Google
Groups.
We're
moving
over
to
the
the
cncf
mailing
list
so
be
sure
to
click
on
this
list.
A
D
A
D
Yep,
so
the
long
running
performance
enhancement
work
that
Rohit
has
been
working
on.
It
is
under
review.
There
are
a
few
things
that
we
need
to
close
out
on
that
before
we
merge,
so
it
will
probably
go
out
in
the
release
that
we
are
planning
may
end.
June
first
week
is
Our
Hope
the
cap
controller
issue
that
Praveen
has
been
working
on
Praveen.
Do
you
want
to
give
a
quick
update
on
that
one
where
we
are
at?
We
had
a
meeting
today.
F
G
Yeah,
we
are
just
picking
up
this
proposal
again
and
trying
to
finalize
the
contents
of
The
Proposal,
so
if
a
community
has
any
Imports
or
feedback
for
us
to
start
with
this
new
feature,
you're
all
welcome
to
drop
in
in
the
slack
Channel
and
yeah.
We
are
excited
to
start
working
on
this
feature
again.
Foreign.
A
Yeah,
so
just
for
this
one
in
particular,
this
is
one
of
the
ones
that
was
highly
requested
again,
whenever
we
put
out
a
survey
to
the
community
asking
what
are
the
issues
that
the
team
should
be
focused
on
the
next,
you
know
road
map,
so
you
know
we
heard
you,
and
this
is
definitely
something
we
are
actively
working
on.
So
if
you
have
any
any
new
comments
or
questions
or
anything
about
this
or
if
you
wish
to
to
help
us
out,
you
know
please
do
and
reach
out
to
us.
A
D
So
I
will
change
the
status
of
that
one
stage
of
that
one
as
soon
as
we
have
a
proposal
pretty
by
DD
the
next
one
signature
and
salsa
attestation
for
kaval
artifacts
I
think
this
is
still
under
discussion
phase.
We
do
not
have
a
proposal
for
this
yet
so
awaiting
that.
I
will
prioritize
that
once
few
of
the
other
things
are
cleared
upper
plate.
D
A
All
right
thanks
renu
and
this
one
is
also
one
that
was
the
number
one
thing
most
requested
in
that
roadmap
survey.
We
did
so
you
know
this
is
you
know
we're
we're
going
to
hopefully
get
to
it
as
soon
as
possible,
but
if
you
have
any
desire
to
come
help
us
get
that
bed
off
the
ground,
please
let
us
know.
E
What
celium
does
is
it
copies
the
labels
from
pods
to
the
celium
identity
resource
that
it
creates
for
storage
purposes,
and
it's
it's
not
garbage
collected
instantly.
So,
if
I
delete
my
pod,
it
won't
get
deleted
instantly
and
that's
why,
when
Capital,
it
happens
and
Gap
gets
stuck
on
waiting
for
the
cluster
to
delete
the
celium
identity
resource
and
since
helium
is
also
being
used.
Finally,
we
would
want
to
support
this
out
of
the
box
and
cap
so
yeah.
This
is.
This
is
something
that
we
want
to.
E
A
G
No
nothing
much
just
we
are
going
to
pick
this
proposal
again
and
the
work
is
in
progress
for
this
feature
to
include
invitating.
So
if
Community
has
any
comments,
feedback,
please
reach
out
to
us
via
our
slack
Channel.
Your
feedbacks
are
welcome
or
any
questions.
If
you
have
please
drop
that
in
the
slack
Channel,
and
then
we
have
a
GitHub
issue
as
well.
For
this.
A
G
Yeah,
so
this
is
something
what
we
are
thinking
to
streamline
the
release
process
for
our
OSS
releases
and
the
get
Cherry
big
bot
seems
to
be
a
good
candidate
to
try
out
configuring
on
all
our
repo.
So
we
are
trying
to
pick
this
up
and
applied
on
all
all
our
repos.
If,
if
anyone
has
any
feedback
on
that
or
any
comments,
if
they
have
used
that
in
their
projects,
you
are
welcome
to
share
your
feedback
as
well
so
yeah.
G
G
To
fix
some
CVS
so
once
we
have,
for
example,
now,
let's
take
quite
eating,
I
want
to
apply
Go
bomb
on
develop
branch,
and
then
cherry
pick
that
commit
to
the
LTS
branches
that
we
support.
So
in
that
case,
what
happens
is
when
I
create
a
PR
to
apply
the
Go
Bump
changes
on
develop
branch
I
just
have
to
add,
as
a
comment
to
that
PR.
What
all
LTS
branches
I
want
to
cherry
pick
that
commit
too
and
as
soon
as
I,
give
all
those
comments
in
the
pr.
G
The
pr
is
ready
when
we
click
on
merge
the
git
cherry
pick,
bot
automatically
takes
care
of
going
to
those
branches,
creating
new
Branch
out
of
those
branches.
Applying
the
commit
to
I
mean
get
cherry,
pick
the
commit
to
those
new
branches
and
raise
a
PR
to
apply
those
changes
again
onto
those
respective
LPS
branches.
So
this
would
like
the
monotonous
work.
This
is
only
for
variety
now.
If
we
applied
on
all
right
posts.
G
Yeah,
so
we
tried
like
Praveen
and
I,
had
a
discussion
on
this,
and
we
tried
applying
this
on
our
temporary
folk
triple
and
also
I.
I
did
POC
on
my
own
personal
repo
and
I
verified
the
it
is
working
fine
on
those
repos.
So
now
it's
a
matter
of
applying
the
same
thing
on
our
our
repos
and
see
how
it
works.
D
Yeah
and
as
part
of
all
our
as
part
of
all
the
cover
tools
that
we
have,
we
do
try
to
remove
all
the
CVS
that
are
identified
in
our
daily
scans
and
gersh's
handling
that
part
where
he
does
the
scans
on
all
these
repos
checks.
The
scan
sees
if
there
are
any
vulnerabilities
which
have
been
identified
and
create
PRS
to
remove
those
in
develop
and
with
this
I
think
it
will
help
the
other
branches
awesome.
Definitely.
A
G
So
we
all,
as
a
team,
came
together
as
in
a
retro
and
like
a
brainstorm,
some
ideas
and
then
I
think
Rohit
or
Praveen,
or
someone
from
our
team
only
came
up
with
this
kind
of
Bot,
which
is
which
is
present
outside,
and
that
was
mentioned
in
the
in
the
issue
so
like
later
on,
we
start
we
picked
up
and
looked
at
it.
It's
like
everyone
in
the
team
is
I
was
looking
forward
to
automate
this
stuff.
A
G
G
C
D
Not
on
this,
however,
I
would
want
to
add
a
discussion
topic,
probably
for
the
next
time,
which
would
be
to
see
if
there
are
any
tools
that
we
can
use
for
code
coverage
and
what
are
your
thoughts
all
of
your
thoughts
on
having
checks
on
code
coverage
for
these
tools,
but
maybe
a
topic
for
next
time.
It's
discussion.
A
D
D
F
F
If
you
do
introduce
a
bot
which
keeps
track
of
your
trip.
We
should
make
sure
that
it
does
not
reduce,
but
I
I'm,
not
sure
how
much
value
we
would
add
if
we
sort
of
push
for
a
higher
code
coverage
after
adding
the
bot,
because
we
do
have
a
lot
of
bits
that
cannot
be
unit
tested
and
making
those
like
rearranging
those
in
a
way
that
allows
unit
testing
will
add
a
lot
of
turn.
F
D
Okay,
no
more,
maybe
next
time,
I
I
need
to
also
do
some
research,
whether
it
will
add
value
or
how
much
value
it
will
add.
What
would
be.
Who
would
be
interested
in
seeing
this
information
I'm
definitely
interested
interested
in
seeing
this
information
so
as
an
engineering
manager
but
others
outside,
if
they
would
want
to
see.
F
C
F
F
So
like
what
I
was
wondering
is
is
does
artifact
or
maybe
need
to
make
any
tweaks
so
that
when
someone
pushes
a
package
repository
like
a
tiny
Carvel
logo
shows
up
like
a
dustful,
let's
say:
Helm
charts,
okay,
like
I
I,
wasn't
like
that's.
What
I
was
wondering
about
actually
like
does
that
need
any
action
from
us.