►
From YouTube: Carvel Community Meeting - February 22, 2023
Description
Carvel Community Meeting - February 22, 2023
This week we went over 2023 roadmap planning and what the team's been working on this week. Full notes and agenda: https://hackmd.io/G8dN30WvQl-8Sirnp8AgRA#February-23-2023-Agenda--
A
Hi
everyone
welcome
to
this
week's
edition
of
the
Carville
community
meeting.
Today's
date
is
February
23rd
2023..
If
you're
watching
this
from
home,
we
encourage
you
to
come.
Join
us
live
we
meet
every
second
and
fourth
Wednesday
of
the
month
at
8,
A.M
Pacific
time.
It's
a
good
opportunity
to
come
meet
other
members
of
the
community
meet
the
maintainers.
Listen
in
on
what
the
maintainers
are
working
on.
You
can
provide
feedback
if
there's
something
you
need
help
with,
or
you
have
an
idea
or
feature
request,
or
anything
like
that.
A
A
If
you
are
unable
to
join
us
live
you
can
still,
and
you
want
to
reach
out
to
us.
You
can
still
find
us
in
other
areas.
In
the
Carvel
Channel
and
the
kubernetes
slack
workspace,
you
can
email
us,
you
can
find
us
in
GitHub
with
any
of
our
project
repos
and
you
can
find
us
on
Twitter
at
Carvel
underscore
Dev
and
if
you
at
any
point
are
interacting
with
us
or
any
members
of
the
community.
A
We
ask
that
you
please
read
and
abide
by
our
code
of
conduct
which
is
listed
in
the
agenda
but
is
linked
out
and
throughout
all
of
our
repos
as
well
foreign
for
those
that
are
on
the
meeting
today
and
you
have
something
you
want
to
bring
up
with
the
team.
Just
make
sure
to
add
that
to
this
discussion,
topic
section
at
the
end.
A
So
it
just
helps
us
and
other
members
of
the
community
understand
how
people
are
using
the
tools
and
may
help
others
work
with
those
tools
in
similar
ways,
and
it
also
helps
the
team
to
maybe
think
differently
and
how
they
develop
the
tools.
So
we
would
appreciate
you
taking
the
time
and
filling
that
out
and
then
everyone,
that's
on
the
call
today
just
make
sure
to
add
your
name
to
the
attendees
list.
We
just
want
to
keep
track
of
who's
attending
these
meetings,
but
if
you're
uncomfortable
doing
that,
that's
totally
fine
as
well.
A
Moving
on
to
announcements,
so
for
those
that
didn't
see
a
few
weeks
ago,
we
put
out
a
survey
with
several
issues
attached
to
each
of
the
tools
asking
folks
to
kind
of
pinpoint
which
issues
out
of
each
of
the
tools
are
most
important,
then
that
helped
us
helped
us
narrow
down
or
what
were
the
top
issues
across
all
the
tools.
So
you
know
the
Top
Choice
in
image
package,
Top,
Choice
and
cap,
so
on
and
so
forth.
A
So
we
had
nine
different
issues,
I
believe
to
choose
from
so,
and
we
just
asked
that
you
know
you
help
us
narrow
it
down
even
further
and
what?
What
is
the
next
issue
that
the
team
should
work
on
and
and
then
we
would
go
from
there
and
building
out
the
road
map.
So
the
deadline
to
fill
this
form
out
to
short
just
a
short
survey,
is
by
end
of
day
to
day
and
what
I
mean
by
that
is
like
11,
59,
PM
Pacific
time.
A
So
please
be
sure
to
fill
that
out.
If
you
haven't
already
I
just
wanted
to
do
a
huge
thank
you
to
the
members
of
the
community
who
did
provide
input
on
issues
and
help
to
to
create
this
form.
So
that's
Scott,
rosenbar,
Rosenberg,
Thomas,
Vettel,
I,
don't
even
know
if
I'm
saying
your
last
name
right:
Robert,
Van,
Voorhees,
again
I'm
gonna
butcher
that
Birch
bershay.
But
yes
thank
you
to
those
I,
really
appreciate
all
your
your
guidance
and
help
with
that
and
I'm
sure
the
community
at
large
really
appreciates
it
as
well.
A
So
K
build
was
featured
here
and
if
you
want
to
check
that
out
and
get
more
information
and
all
about
pay
build,
and
this
week,
as
of
yesterday,
we
had
one
with
featuring
ytt
and
thank
you
to
Scott
for
for
representing
Carvel
and
presenting
ytt
super
appreciate
all
your
your
help
with
that
and
all
your
efforts
after
you
go
and
watch
this
video.
We
ask
that
you
go
vote.
So
what
that
means
is
you
can
go.
A
Add
your
input
here
and
it's
already
filled
out,
but
you
can
see
the
results
that
are
current
right
now
and
you
have
two
days
left
to
vote,
so
you
can
vote
for
any
one
of
these
course
or
biased
to
ytt.
But
we
don't
want
to.
You
know
make
you
vote
any
one
way
or
the
other,
so
whatever
you
think
should
be
the
Top
Choice.
Please
go
do
that
now,
upcoming
on
March
14th
at
6
30
p.m.
A
B
B
B
Another
thing
that
was
changed
was
API
related,
so
there
was
like
an
internal
like
internally
image
package
as
a
Constructor
for
go
container
registry
that
we
use
underneath
it
as
a
library,
and
we
were
allowing
people
to
pass
in
to
that
Constructor
the
options
for
gtcr
and
we
decided
to
make
a
cut
clean
there
and
starting
on
node
36
there.
You
cannot,
you
can't
anymore,
send
both
image
package.
Configuration
plus
go
container
registry
configuration
so
there's
a
new
Constructor
for
it
that
only
provide
allows
you
to.
B
If
you
want
to
use,
go
container
registry,
let's
call
it
vanilla,
you
can,
but
you'll
be
responsible
for
everything
and
image
package
no
longer
contains
like
things
like
some
caching
that
it
does
and
and
like
some
some
niceties
that
that
it
had
before.
So
that's
an
internal
change.
I,
don't
think
this
is
going
to
affect
anybody.
It
was
affecting
just
we
had
like
one
consumer
that
was
using
image
packaging
this
way
and
because
of
them
like
we
found
the
problem,
so
we
decided
to
split
these
interfaces
with
the
split.
B
A
So
if
you
are
interested
in
that
there
is
a
question
in
that
Forum
that
asks
that,
and
you
can
provide
your
information
for
me
to
contact
you
and
and
start
that
process,
but
also
feel
free
to
DM
me
directly
in
the
kubernetes
kubernetes
like
workspace,
and
we
can
provide
more
information
and
answer
any
questions
you
may
have
on
that.
So
we
would
really
appreciate
all
the
help
we
can
get.
A
Move
into
status
updates
so
again,
project
roadmap
is
currently
in
a
work
in
progress,
so
I'm
gonna
just
keep
beating
this
down.
Please
fill
out
that
form,
and
hopefully
we'll
have
everything
ironed
out
and
news
to
share
with
you
next
week
as
to
what
we
will
be
working
on
onto
the
backlog
so
stuff
that
the
team
has
been
working
on
and
who
here
can
give
more
information
about
cat.
C
So
this
week
we
are
trying
to
wrap
up
a
few
things
and
I
think
the
major
one
is
fixing
this
book.
Fair
number
of
characters
in
the
app
name
cannot
be
more
than
63
characters
like
we
were
just
trying
to
finalize
which
approach
to
take,
because
it
also
involves
backward
compatibility
for
the
app
changes.
C
So
right
now
we
have
decided
to
introduce
a
new
label
that
will
be
used
in
the
new
app
changes
and
the
the
new
app
changes
of
existing
apps
would
also
add
this
label
and
then
at
a
later
stage,
we'll
migrate
to
this
new
label
instead
of
the
Legacy
one.
So
this
will
be
like
carried
over
in
steps
and
they
will
be
wrapping
up
the
first
step
in
this
week.
C
C
Me
again,
so
we
are
trying
to
add
the
dry
run
functionality
in
K
control.
Basically,
while
installing
like
in
package
install
commands
users
can
try
to
take
a
look
at
the
resources
that
will
be
applied
on
to
the
cluster
instead
of
like
directly
creating
them.
So
we
are
just
trying
to
finalize
some
stuff
on
the
pr
and
wrap
this
up.
C
D
D
A
B
C
B
It
just
stayed
there
staling
and
then
so
I
decided
to
re-pick
it
up
now
that
I
had
a
little
bit
of
time
and
I
do
realize
that
this
is
going
to
to
this.
This
will
have
like
a
quite
a
big
impact
when
we
deploy
this
because
also
like
what
is
this
thing,
this
PR?
What
does
it
do
so
previously?
You
were
able
to
copy
around
and
describe
the
signatures
created
by
cosine,
but
cosine
does
more
than
just
create
signatures
for
your
images.
B
If
there's
signatures
there
or
not,
but
now
we
would
have
to
do
the
same
thing
for
s-bombs
for
the
signatures
of
the
s-bombs
for
the
attestation
and
the
signature
of
the
attestation
itself.
So
this
would
like
exponentially
increase
the
amount
of
requests
to
the
to
the
registry,
so
I'm,
trying
to
see
if
I
can
do
like
some
performance
tweaks
here
to
make
sure
that
this
doesn't
like
completely
bring
it
to
a
stall
image
package
when
you're
trying
to
copy
or
describe
any
of
these
things.
B
D
B
So
like
it's
going
to
be
the
same
way
like
we
are
changing
the
flag,
there
was
a
flag
already
called
cosine
signatures,
I
believe
or
see.
I
think
this
was
the
name
of
the
flag
and,
first
of
all,
that
flag
is
going
to
change,
to
become
cosine
artifacts
to
better
represent
everything
so
that
that
will
be
like
a
breaking
change
if
you're
using
it
and
the
default
behavior
is
false.
B
So
if
you
want
to
copy
signatures
and
so
on,
you'll
have
to
enable
it
in
the
same
way
when
you're
describing
you
need
to
tell
it
like
just
describing
give
me
the
signatures
in
this
box
like
the
idea
here
is
to
like,
we
don't
know
like
how
many
people
do
use
cosine
signatures
right
now.
So
let's
keep
it
conservatively,
assuming
that
you
don't,
and
if
you
do
you'll
have
the
option
so
right
same
as
Behavior
as
now.
D
B
Like
I'm
doing
a
change
right
now,
that
is
going
to
make
it
a
little
bit
better
because
like
if
we
want
to
go
technical
here
like
instead
of
searching
for
every
image,
I'm
just
going
to
go
and
find
all
the
tags
first
and
then
I
know
if
the
the
images
will
be
there
based
on
the
text,
so
I'll
replace
I
think
it's
going
to
even
make
it
a
little
bit
better.
If
you
have
all
the
images
already
in
a
single
repository,
we
don't
have
to
go
like
for
every
single
single
signature
so
like.
B
If
you
had
like
10
images
there,
we
only
need
to
go
to
the
registry
once
now.
Well
previously,
we
had
to
go
10
times
so
like
it's
going
to
be
like
a
an
improvement,
even
though
the
retrieval
of
tags
takes
a
little
bit
of
time,
more
than
a
hand
request
it's
going
to
improve
like
it's
going
to
be
much
better
when
you
have
much
more
images,
so
I'm
hoping
to
have
like
a
little
bit
of
a
gain
of
performance.
B
D
B
A
A
A
A
We
would
love
to
get
your
input
on
what
the
team
should
be
working
on
next,
so
we
we
really
want
to
make
sure
we're
we're
getting
that
Community
input
and,
and
you
know,
contributing
and
into
what,
what
the
open
source
Community
would
like
to
see
next.
So
with
that,
we
hope
to
see
you
at
the
next
meeting.
Thank
you,
everyone
and
enjoy
the
rest
of
your
day.