►
From YouTube: Carvel Community Meeting - April 26, 2021
Description
Carvel Community Meeting - April 26, 2021
We meet every Monday at 11:30am PT / 2:30pm ET. We'd love for you to join us!
Agenda notes from this meeting can be found here: https://hackmd.io/F7g3RT2hR3OcIh-Iznk2hw
A
Well,
hello,
everyone
and
welcome
to
the
april
26
carvel
community
meeting,
we'll
start
with
any
we'll
start
with
the
announcements
here
up
at
the
top.
Who
wants
to
take
this
one.
B
I
can
take
it
so
during
the
upcoming
kubecon
cloud
native
con
europe
carbo
will
be
there,
so
we
have
three
exciting
things
going
on.
B
One
is
a
recorded
talk
by
drow
and
myself
regarding
kubernetes
package
management,
using
unix
philosophy
with
carvo,
so
it'll
be
a
great
way
for
y'all
to
come
check
out
how
you
could
leverage
car
vote
to
do
package
management
and
what
kind
of
benefits
you
could
reap
so
for
those
who
are
in
the
america
time
zones-
it's
it's
early
in
the
morning,
but
for
those
in
european
time
zones
it'll
be
perfect
for
you
all
to
come,
join
so
there's
going
to
be
a
short
q,
a
as
well
so
looking
forward
to
meet
you
there
and
we
also
have
live
office
hours.
B
So
two
of
our
maintainers
will
be
there
for
about
30
minutes.
To
answer
any
of
your
questions
and
discuss
any
topics
that
you
would
like
to
talk
through,
and
there
is
a
company
virtual
booth
where
you
can
check
out
the
demo.
We
have
the
link
here,
so
you
can
also
take
a
look
ahead
of
time
for
our
main
for
our
community
members.
So
yeah
check
those
out
and
we'll
see
you
at
kubecon.
A
C
Yeah
garrett
did
you
want
to
talk
about
the
new
release.
D
D
D
We've
included
some
support
under
the
experimental
schema
flag,
so
there's
more
features.
If
you
want
to
kick
the
tires
there,
but
yeah.
If
you
want
to
know
more,
all
the
links
to
the
issues
that
were
addressed
in
this
release
are
linked
here
and
I
think
there's
also
some
support
for
the
arm.
64
binaries
as
well
now.
A
Okay,
that
sounds
great,
which
brings
us
down,
or
do
we
want
to
talk
about
our
schemas.
C
Yeah
yeah,
the
the
schema
track,
continues
to
progress,
we're
we're
continuing
to
make
progress.
There.
Garrett
was
talking
about
some
of
the
stuff
that
you
can
actually
see
under
the
experimental
flag
and
there's
active
work
right
now
going
on
in
terms
of
being
able
to
provide
the
same
level
of
support
for
contributing
your
own
schema.
C
If
you
inherit
someone
else's
library,
adding
your
own
working
on
that
kind
of
thing
right
now,
there's
a
few
items
left
and
we'll
get
to
the
point
where
we've
reached
kind
of
a
base
like
minimum
viable
functionality,
we're
calling
that
v1
we've
already
started.
Looking
at
v2,
we've
talked
about
this
a
little
bit
but
just
being
able
to
support
exporting
ytt
schema
in
open
api
schema
format.
So
you
can
use
all
the
tooling
that
you're
used
to
for
that
and
support
for
that.
C
So
there's
a
couple
parts
to
that
piece
being
able
to
export
the
schema
and
then
we're
also
looking
into
ways
in
which
guise
that
generate
nice
experience
for
end
users,
who
are
entering
in
configuration
values
like
being
able
to
give
hints
to
those
gui
generators,
so
we're
digging
into
that
kind
of
stuff.
There
that's
what
the
v2
stuff
is
about.
A
E
I
can
take
it
so
yeah.
There
was
this
morning
just
a
new
alpha
release
put
out
of
cap
controller.
That
has
basically
the
three
main
features.
Two
of
them
are
really
related
to
this
idea
of
improving
the
debuggability
of
cap
controller.
As
far
as
how
people
interact
with
installed
packages
and
package
repositories.
E
What
ends
up
happening
is
that
both
these
resources
actually
create
this
underlying
app
cr
when
they
are
created
and
folks
were
finding
it
very
difficult
to
find
errors
associated
with
those
app
crs
when
they
would
occur.
So
one
of
the
things
that
we
did
was
just
elevate
that
error
message
up
to
the
installed
package
and
package
package
repository
statuses
to
help
people
find
error
messages
a
bit
quicker.
E
The
other
work
that
was
added
in
here
was
support
for
helm,
v3,
templating
and
then
there
there
will,
as
part
of
this
eventually
be
the
removal
of
helm,
v2
templating.
But
for
this
time
both
versions
are
still
supported
as
far
as
sorry
about
that,
as
far
as
the
installation
docs,
they
can
be
found
at
the
link
there,
but
yeah.
This
should
be
available
for
anyone
to
get
started
with.
A
Excellent,
thank
you
daniel
and
looks
like
there's
a
list
being
compiled
of
guides
and
examples
for
ytt.
Did
anyone
want
to
talk
a
little
bit
about
this.
F
Sure
so
we
have
a
amount
of
work
coming
up
for
making
guides
of
real
life.
Examples
that
showcase
specs
best
practices
of
using
ytt
and
we've
come
up
with
a
first
pass
list
of
guides
that
we
want
to
create
these.
This
is
going
to
be
prioritized
for
some
time
in
the
future,
so
there
is
time
to
get
your
feedback
in
if
there
are
any
guides
that
you
want
to
see
or
if
there's
any
specifics
around
these
five
guides
listed
in
this
issue
that
you
want
to
share
like
specifics
on
so
yeah.
F
We're
really
interested
in
hearing
feedback
on
this
feel
free
to
share
what
kind
of
guides
that
you
want
to
see
in
this
issue
or
on
slack,
because
we'd
love
to
hash
out
some
of
those
use
cases.
A
A
See
a
lot
of
no
head
shakes
all
right,
so
we'll
press
on
that.
What
have
we
got
coming
up
this
week?
B
I
could
quickly
share
my
screen
if
that
will
be
faster.
Let's
see
screen
google
chrome.
B
Clicking
on
that,
that's
the
screen
wider.
So
this
week
we
have
so
again.
Our
priorities
are
working
through
ytt
schema
work,
the
both
type
checking
part
and
so
we're
working,
focusing
on
a
lot
of
our
efforts
there.
Another
track
that
we're
working
on
is
also
this
issue
around
performance
for
image
package
copying.
So
we've
noticed
that
we've
heard
from
some
users
that
the
the
actual
copying
takes
a
while
or-
and
it
doesn't
give
you
any
input-
information
feedback
in
terms
of
like
what's
going
on
behind
the
scenes.
B
So
one
of
our
maintainers
draw
here
is
working
through
that
so
kind
of
improving
the
user
experience
of
image
package.
That's
another
focus
area
that
we
have
this
week
and
we
don't.
B
We
normally
go
through
like
different
issues
to
talk
through
what's
coming
up
and
we
throw
estimates
on
them,
but
I
believe
we
have
a
lot
of
you
know
estimated
work
already
in
our
pipelines.
So
a
lot
of
the
issues
that
you
see
here
under
the
prioritized
backlog,
we've
already
reviewed
them
in
our
previous
community
meetings.
So
I
won't
bore
you
to
review
them
again,
but
just
just
so
you
know,
these
are
the
things
that
we
have
prioritized
in
the
backlog
and
we'll
be
working
through
them.
B
So
that's
what
we
have
planned
for
the
maintainers,
but
for
the
community
members
out
there
please
feel
free
to
you
know
chime
in
and
any
of
this
prioritized
backlogs
or
we
have
issues
that
we
have
marked
as
good
first
issues,
so
we'll
love
to
see
more
engagement
from
the
community
so
and
if
there
is
any
particular
issue
that
is
either
not
prioritized
or
it's
just
like
triaged,
we
do
have
this
thing
called
future
voting
and
I
think
we've
mentioned
it
in
the
past
as
well.
B
So
if
there's
an
issue
that
you're
interested
that
you
want
to
indicate
that
either
you
want
to
work
on
it
or
you
want
others
to
work
on
it
with
you
or
maintain
us
to
take
a
look
at
it
more.
Please
vote
on
this
particular
issue.
The
way
you
can
do
it
is:
let's
see
how
do
I
do
it
on
zenhub?
If
you
go
to
that
specific
github
issue,
there's
a
smiley
face
on
the
right
top
corner,
you'll
see
it.
B
A
That
sounds
great,
so
what
we
have
up
next
are
triage
help
and
it
doesn't
look
like
anyone
put
anything
in
there,
but
in
case
there's
someone
that
does
want
to
add
something
feel
free
to
speak
up
now.
A
Okay,
seeing
what
looks
like
all
parts
clear:
let's
go
on
to
the
discussion
topic,
so
any
final
feedback
proposal
for
carvel
documentation.
C
Yep,
I
added
that
one,
so
we've
had
a
chance
to
go
through
a
couple
of
rounds
of
of
looking
through
this
scheme
about
how
do
we
maintain
our
documentation
across
the
carvel
suite
do
today
we
have
a
scheme
where
we're
maintaining
exactly
one
version,
which
is
the
latest,
and
this
proposal
suggests
that
we
actually
maintain
one
live
version
which
would
which
would
be
the
latest
version
and
but
but
keep
copies
of
previous
versions,
but
they're
completely
frozen.
C
They
wouldn't
be
updated
once
we
released
new
versions,
so
we've
gone
through
a
number
of
round
rounds
of
feedback
feels
like
we've
gotten
to
a
point
where
there
hasn't
been
much
new
feedback
here.
But
if
there's
anything,
that's
been
outstanding
for
you
that
you
meant
to
to
comment
on
it.
You
meant
to
make
a
suggestion
here
or
you
don't
feel
like.
The
changes
have
adequately
addressed
your
concern.
C
I
really
appreciate
if
folks
would
go
ahead
and
jump
in
and
do
that
best
way
is
to
like
make
a
review
here
and
that'll
sort
of
restart
our
clock
in
terms
of
waiting
for
things
to
settle
out,
but
otherwise
you
can
see.
I've
asked
the
folks
who
are
meant
to
be
approvers
for
this
proposal.
C
They
could
go
into
github
and
go
ahead
and
indicate
for
themselves
that
they're
that
they're
happy
with
the
with
the
way.
This
looks
when
we
pull
the
trigger
on
that,
then
that
can
result
in
a
set
of
stories
for
us.
Some
chore
work
for
us
to
kind
of
get
our
pipeline
set
up
so
that
we
can
follow
this
approach.