►
From YouTube: Carvel Community Meeting - January 25, 2023
Description
Carvel Community Meeting - January 25, 2023
This week we focused on several community discussion topics and brought up some long-standing issues. We are also working on our 2023 Roadmap and would love community input, so please do express what you'd like to see the team working on! Full agenda from this meeting here: https://hackmd.io/G8dN30WvQl-8Sirnp8AgRA#January-25-2023-Agenda
A
Hi
everyone
welcome
to
this
week's
edition
of
the
Carville
community
meeting.
Today's
date
is
January
25th
2023..
If
you're
watching
this
from
home,
we
would
love
for
you
to
come.
Join
us
live.
We
meet
every
second
and
fourth
Wednesday
at
8,
A.M,
Pacific
time,
it's
a
great
opportunity
for
you
to
come
and
meet
the
folks
that
work
on
Carvel
meet
the
other
members
of
the
community
that
use
Carvel
that
contribute
to
Carvel.
If
you
have
any
questions
about
how
to
use
Carvel,
you
can
come
and
ask
those
or
yeah
feature
requests.
A
If
you
like
to
chime
in
on
what
the
the
folks
are
working
on,
it's
it's
just
a
good
way
to
interact
and
engage
you're.
Also
welcome
just
to
sit
and
listen.
If
you
aren't
comfortable
in
participating,
we
would
love
to
meet
you
and
have
you
part
of
the
community
meeting
for
those
that
are
on
today's
meeting?
Please
add
any
discussion
topics
you
wish
to
bring
up
with
the
folks
here
the
discussion
topics
section
at
the
bottom
of
the
agenda
and
we
will
get
to
it
towards
the
end
of
the
meeting.
A
If
you
are
unable
to
come,
join
us
for
the
meeting
and
you
still
want
to
get
in
touch
with
us,
there
are
several
other
ways
you
can
find
us.
You
can
write
Us
in
the
cardboard
channel
on
the
kubernetes
slack
workspace.
You
can
email
us,
you
can
find
us
in
GitHub
and
any
of
our
project
repos.
You
can
find
us
in
on
Twitter
at
Carvel
underscore
Dev
at
any
point
you're
interacting
with
us
or
any
other
members
of
the
community.
A
For
those
that
are
using
Carvel
tools,
we
would
love
to
know
more
about
how
you're
using
those
tools.
So
we
created
this
pinned
issue
and
we
ask
that
you
just
leave
a
comment
here
detailing
what
your
use
case
is
for
any
of
the
tools,
your
organization
or
company,
that
you
represent
links
to
your
website,
your
country,
any
contact
information,
you
feel
comfortable,
sharing
and
optionally.
You
can
add
a
logo
for
your
company
and
we
would
get
that
added
to
the
adopters
file.
A
A
A
A
Except
for
upcoming
I
know,
I
promised
a
blog
post
for
this
week,
but
there's
just
a
lot
more
to
it.
That
I
need
to
iron
out
to
write
a
blog
post
about
all
the
processes
and
different
tips
and
tricks,
and
all
that
good
stuff
to
becoming
a
contributor
and
then
to
a
maintainer
of
Carvel.
So
I
want
to
make
sure
you
know
this
is
as
clear,
concise
and
helpful
as
possible.
A
Okay,
a
lot
of
us
will
do
one:
okay,
okay,
cool.
Well,
thank
you,
anyways
for
anything
for
for
either.
One
that
you
you
do
is
super
appreciated
right
now.
The
team
is
just
so
swamped
with
all
of
the
work
that
they're
doing
and
it's
it's.
It's
very
much
appreciated
when
members
of
the
community
are
able
to
to
represent
Carvel
and
share
their
knowledge
of
the
tools.
A
A
D
Maybe
I
can
give
give
it
a
shot.
So
so
this
has
been
not
a
very
big
release,
but
it
contains
pretty
interesting
things,
so
two
of
them
were
contributed
by
the
community
and
I
added
something
else
that
was
like
very
time
compared
to
what
the
community
did.
So
this
is
a
basically
a
community
based
release.
D
So
they're
Alex
we're
about
to
added
a
feature
on
on
tag
when
you're
trying
to
get
the
text
to
filter
out
the
tags
that
are
image
package
internal,
so
you'll
only
see
the
tags
that
are
not
so.
Basically,
if
you
have
like
a
tag
for
a
version
of
your
of
the
images
or
something
like
that,
those
will
appear
so
check
that
out
it's
a
pretty
cool.
The
other
one
was
a
long
time
running
bug
on
on.
D
A
A
But
if
you
have
anything
that
you
wish
to
see
part
of
railroad
map
when
I
have
input
on
what
the
team
is
working
on,
there's
any
specific
issues
or
on
any
of
the
tools
that
you
would
like
to
see
being
worked
on.
Please
let
us
know-
and
we
will
you
know,
discusses
a
team
and
see
if
it
makes
sense
for
us
over
and
overall
in
our
development
process.
So
we
would
love
to
have
Community
input
on
our
roadmap.
So
please,
let
us
know.
E
B
So
yeah,
this
is
something
that's
come
up
a
while
ago
and
then
again
a
while
ago,
but
less
than
a
while,
but
so
a
while
ago.
It's
something
that
I've
been
seeing
a
lot
and
hearing
from
a
lot
of
users
that
I've
been
introducing
to
Cargo
is
image
package
today,
while
very
efficient
and
very
beneficial.
B
And
then
you
go
and
see
the
image
that
was
scanned.
That
has
vulnerability,
and
you
can't
figure
out
her
life
with
you.
What
the
actual
image
that
was
failing
to
scan
was
supposed
to
be,
and
while
the
default
behavior
is
easy
and
the
other
behaviors
would
require
more
preparation.
Let's
say
on
the
registry
side,
most
likely
I'm
wondering
if
there
is
any
thing
plan
for
moving
forwards
with
supporting.
C
D
But
it
can
be
like
a
a
star.
10
point
yes
like
on
that
on
that
there
are
like
other
issues,
but
I
think
there
are
also
linked
on
that
particular
one
and
there's
also
a
PR
link
to
it
in
one
of
our
repos
that
contain
like
what
CU
Scott
were
saying.
There's
a
there's,
a
proposal
to
implement
this
for
image
package.
Unfortunately,
till
this
point.
B
D
Yeah
yeah
yeah,
we
we
are
aware
of
that.
We
have
like
a
couple
of
them
that
we
still
haven't
finished
like
the
move
of
all
the
things
that
are
cargo
related,
we
do
have
other
repos
that
are
also
in
the
process
of
moving,
but
because
they
were
not
called
like
Carvel
like
oh
this.
This
one
was
because
it's
called
Purple
Community
but
but
like
there
are
some
that
were
not
called
karbal
and
we
didn't
move
them
right
away,
but
we
are
in
the
process
of
doing
that
right
now,
yeah
yeah.
D
So
basically,
unfortunately,
we
didn't
have
time.
We
didn't
have
like
resources
to
stuff
that
could
like
the
finishing
of
the
the
proposal
and
the
implementation
of
it.
We
also
see
this
as
a
a
very
big
hurdle.
We
heard
it
in
in
multiple
places,
multiple
different,
different
places
that,
in
fact
this
is
something
that
is
desirable
and
behavior
for
image
package,
even
though
it
is
the
it
is
pretty
good
for
machines.
D
Not
only
machines,
look
at
the
animals
right
and-
and
it
also,
as
you
said,
makes
it
hard
to
integrate
with
other
tools,
especially
because
in
some
cases,
the
only
visual
representation
of
what
that
image
is,
is
the
the
repository
where
it
lives,
and
it
makes
it
hard.
So
we
are.
We
are
aware
of
that.
We
would
like
to
have
people
to
to
stop
this
and
we
are
trying
to
push
for
it,
but
we
still
haven't
had
luck,
there's
there's
been
like
a
lot
going
on
on
the
on
the
VMware
side.
D
Thank
you
so
and
like
like
on
that
proposal,
there
they're
they're,
like
also
some
like
some
of
the
issues
that
explain
why
this
was
not
implemented
to
start
with,
because
there
are
like
some
complications
on
not
not
real
complications,
but
some
obstacles
that
can
happen
when
you're,
when
you're
doing
a
move
of
images
to
multiple
repos
at
the
same
time
so
yeah
but
like.
If
you
want
to
know
more,
if
you're
interested
in
looking
through
this
proposal,
and
you
need
you
need
some
context.
D
Just
being
me,
I'm
not
talking
to
you
specifically
so
Scott,
but
if
you
are
interested
in
liking
and
oh,
this
is
something
that
I
feel
like
is
interesting
and
that
I'd
like
to
look
into
and
maybe
help
with
just
feel
free
to
reach
out
to
me
and
I
like
I'm,
more
than
happy
to
give
a
little
bit
of
context
more
about
it.
And
eventually,
let's
see
if
2023
is
the
year.
E
C
Yeah
I
just
want
to
pile
on
a
little
bit
of
plus
one
here
to
this
on.
All
those
points
show
out
that
we
are
very
aware
of
the
difficulty
that
this
causes
and
have
had
to
make
painful,
prioritization
choices
up
to
this
point
of
like
across
the
suite
and
what
we
pay
attention
to,
but
but
yeah
we
as
much,
maybe
not
more
than
but
as
much
as
as
folks
want
this
to
be
different.
C
A
D
So
like
it's
the
second
time
we
do
this
to
people
right
like
like
we
move
towards.
Hopefully
it's
the
last
time
right,
but
maybe
we
should
start
thinking
about
having
vanity
links
for
our
applications
so
that,
if
it
happens
for
us
to
move
works
again,
we
don't
have
to
revisit
all
the
code
changes
and
tell
people
to
change
their
modules
and
stuff
like
that.
So
I
think,
since
we
are
with
the
hands
dirty
already
with
the
move
to
cnncf,
maybe
we
could
do.
D
We
could
add
these
vanity
links
just
just
to
make
our
life
easier
and
also
the
people
that
are
consuming
our
tools
as
as
apis
as
well,
because
now
we
are
going
to
have
to
do
the
change
again.
We
are
going
to
have
to
change
the
orgs,
so
it
will
stop
being
VMware
10
to
slash
whatever
tool
it
is
and
it
becomes
Carval
Dev.
So
if
you're
doing
that,
why
don't
we
just
create
a
vanity
leaning?
Since
we
do
own
Carvel,
they
have
Carvel
dot
Dev
domain.
C
Yeah
I
agree
I
remember
when
we
moved
the
last
time
we
thought
well.
This
is
it
when
from
k-14s
to
to
VMware
and
yeah
like
in
some
weird
crazy,
like
Devil's
Advocate
sense
like
that
argument
is
actually
even
stronger
now,
but
but
I
agree
with
you,
like
I
I.
Think
in
general,
part
of
what
I've
learned
to
this
in
in
in
in
this
adventure
is
yeah.
C
E
C
C
E
A
B
Picked
up
hard
topics
already,
maybe
I'll
bring
up
another
one
and
this
time
a
huge
on
no.
But
a
question
on
ytt,
which
is
there
has
been
long
talk
about
emitting
comments
and
I
was
just
working
on
another
situation.
Where
admitting
comments
would
also
be
very
beneficial.
It's
specifically
emitting
ytt
templates,
like
generating
ytt
templates
from
ytt
and
wondering
if
there
is
anything
like
is
that
is
that
also
a
matter
of
prioritization
is
that
there
are
technical
issues
there.
What
like,
where
does
that
stand
as
well.
C
C
So
I
that
went
GA
some
months
back
the
version
three
went
GA
some
months
back,
so
that
is
a
bonus
to
be
able
to
like
start
to
build.
On
top
of
that,
there
were
a
few
like
pretty
nasty
lingering
bugs
so
from
an
implementation
perspective.
I
feel
like
the
roads
kind
of
opened
up
there
and
that
that
will
be
the
essence
of
it.
So
there's
some
there's
some
issue
about
okay.
Well,
do
you
wholesale
just
completely
replace
which
version
of
the
parser
you're
using,
which
is
a
heavy
duty?
C
It's
not
a
rewrite,
but
there's
a
lot
of
Plumbing
that
would
need
to
get
replaced
there.
So,
thankfully,
there
there's
a
translation
in
between
the
way
that
ytt
manages
the
yaml
structure.
Internally
has
its
own
data
structures,
but
you'd
have
to
replace
both
the
parsing
side
of
that
translation
in
and
the
translation
out,
which
is
a
very
risky
in
terms
of
like.
Are
you
going
to
create
regressions
kind
of
thing,
so
we
we?
We
do
have
the
context
to
be
able
to
do
that.
C
B
It's
making
sure
that
it's
also
you're
limiting
the
mistakes
that
someone
makes
where
they
added.
It's
not
like
just
saying,
hey,
hashtag
hashtag
at
is
a
ytt
comment.
That's
going
to
pass
through
because
immediately
you
start
messing
things
up
completely
and
someone
adds
in
that
extra
hashtag
and
it
breaks
it.
So
it's
figuring
out
the
right
syntax.
It's
not
over
complicated
to
get
it
in,
but
is
also
not
similar
enough
that
it
would
bring
people
right.
C
Nice
one
Nancy
yeah
great
question.
That
also
seems
like
one
of
those
like
big
power
moves
that
opens
up
a
whole
class
of
solutions
and
it
comes
up.
It
comes
up
because
you
have
build
time,
template
generation
that
generates
templates
for
deployment
time,
for
example,
if
you're
using
in
the
kubernetes
context,
like
that's
a
very
natural,
understandable,
workflow.
B
Yeah
yeah.
No,
this
has
come
up
a
lot
of
times
with
like
the
idea
of
like
basically
like
staff
holders
or
like
application
accelerators
or
things
like
that,
where
you
can
scaffold
out
an
application,
but
that
application
in
the
end
you
want
it
to
be
a
ytc
template
or
you
want
to
have
a
templating
mechanism
to
fit
it,
which
could
be
very
beneficial
to
have
right.
B
B
E
B
B
Is
that
I'm
not
doing
good,
templating
and
I'm
structured,
aware
yeah,
yeah
but
yeah,
and
it's
for
the
context
on
that
and
happy
to
go
over
at
some
point
with
you
like
happy
to
you
know,
try
and
revisit
some
of
the
things
that
see
from
the
different
things
that
I've
been
working
on
recently,
but
would
make
sense
from
a
design
perspective.
At
least
I
I
had
no
clue
in
writing.
Go
so
you
know.
C
Coming
up
with
the
right
problem
statement
is
90
of
the
problem
exactly
right,
so
that's
you've
been
incredibly
helpful
along
that
way.
Yeah!
Let
me
let
me
just
give
a
pitch
around
this.
If
you
know
this
is
a
great
opportunity.
If
somebody
from
the
community
really
wants
to
be
able
to
to
dig
in
into
some
some
language
design
aspects,
it
may
not
sound
on
on
the
face
of
it
like
it
would
be
a
whole
lot
of
that.
C
It
looks
like
a
lot
of
Plumbing,
but
but
in
fact,
there's
a
lot
of
really
interesting
problems
in
there.
That
could
be
a
way
to
for
someone
to
dip
their
toe
in
in
the
pool
of
of
language
development
to
get
exposed
to
some
of
that
stuff,
you
can.
You
can
use
our
project
as
an
opportunity
to
try
that
out,
and
we
would
do
our
best
to.
We
would
definitely
want
to
support
that.
So
if
someone
else
can
beat
us
to
it,
we
would
love
that
but
yeah.
C
A
Thank
you
Scott
and
thank
you.
John
before
we
go,
I
I
should
add
another
announcement
that
we
did
not
cover
in
the
last
meeting
and
then
some
things
that
have
happened
since
that
meeting.
So
it
adds
a
little
bit
more
context
to
the
strong
one
of
my
the
strong
drive
towards
prioritizing
tasks
right
now.
So
as
as
everybody
is
dealing
with
across
Tech,
we
have
faced
some
attrition
here
in
Carville,
so
Joe
Kimmel.
A
He
is
no
longer
on
the
Carville
team
and
Aaron
Hurley
is
no
longer
on
the
Carville
team.
As
of
Friday,
Aaron
decided
to
move
on
and,
and
you
know,
take
a
break
and
focus
on
himself
and
figure
out
life
and
whatnot.
So
right
now
we
we
are
working
with
what
we
have,
and
so
we
are
leaning
towards
the
community
to
to
contribute
to
participate
to.
A
Let
us
know
what
we
should
be
prioritizing,
what's
most
important
for
us
to
develop
across
the
cargo
tools,
and
we
really
want
to
collaborate
as
much
as
possible
to
make
this
to
make
this
all
possible
and
to
continue
the
work
that
we're
doing
for
Carvel.
So
we
just
want
to
I
just
want
to
to
be
transparent
as
possible.
What's
going
on
here,
and
you
know
all
these
different
issues
we
really
want
to
work
on.