►
From YouTube: Carvel Community Meeting - September 14, 2022
Description
Carvel Community Meeting - September 14, 2022
We meet every 2nd and 4th Wednesday of the month at 9am PT. We'd love for you to join us live!
This week we announced our CNCF Sandbox donation, went over latest releases, and the ytt semver proposal. Check out all the notes here:
https://hackmd.io/F7g3RT2hR3OcIh-Iznk2hw?view#September-14-2022-Agenda
A
Hello.
Welcome
to
this
edition
of
the
Carrboro
community
meeting
today
is
September
14th
2022.,
I'm,
John,
Ryan
Nancy
is
out
on
a
well-earned
holiday
today.
So
welcome.
If
you're
watching
this
recording,
we
encourage
you
to
come.
Join
us
live.
We
meet
every
second
and
fourth
Wednesday
at
9
00
a.m.
Pacific
time
it's
a
chance
to
listen
on
what
the
maintainers
are
working
on,
give
us
feedback
ask
questions
just
get
Live
help
with
any
of
the
tools
chance
to
to
be
with
us
synchronously
for
those
who
are
here
today.
A
A
A
So
that's
how
to
reach
out
to
us
when
you
attend
these
meetings,
we
ask
that
you
read
and
abide
by
our
code
of
conduct
and
it's
linked
in
the
agenda
here
and
additionally,
we
ask
that
when
you
attend,
if
you
can
slide
your
name
in
on
this
list
here-
and
if
you
don't
mind
mentioning
the
organization
you
represent,
so
we
know
who's
from
the
community
is
showing
up
to
these
things
and
we
can
keep
our
communication
lines
open.
That'd
be
great.
We
also
invite
you
to
put
a
comment
in.
A
A
A
A
B
C
It's
big
congratulations
to
everybody
here
and
people
who
could
not
make
it
to
the
meeting
today.
I
think
we
have
been
waiting
with
baited
breaths.
Like
you
know
yesterday,
when
that
meeting
was
happening,
they
were
waiting
when
the
results
are
going
to
come
out
and
it
happened
yay.
It
finally
happened.
So
Nancy
is
not
here
today,
but
she
gave
a
big
push
to
get
this
done.
D
A
Beautiful,
thank
you.
Thank
you
all
right,
okay.
Well,
that
was
just
yesterday
so
coming
up,
we're
actually
doing
a
a
presentation
to
the
the
tag
around
application
delivery.
So
that's
happening
September
21st!
So
we're
looking
forward
to
sharing
more
publicly
in
a
more
public
forum
about
how
all
that
works.
B
Yeah
just
wanted
to
share
that.
We
have
spent
I
mean
past
month
or
two
reviewing
our
contributor
model
and
we
have
published
an
updated
one.
We're
still
considering
this
to
be
very
much
as
like
I
don't
know
in
the
settling
state.
So
it's
a
great
time
to
provide
any
feedback
that
you
have
any
questions.
Anything
that's
unclear,
we'd,
love
to
hear
it,
but
yeah,
please,
please
let
us
know
and
we're
I
don't
know
we're
planning
to
revisit
this.
B
E
F
A
G
A
D
A
G
A
B
A
You
know
of
the
highlights
for
the
month,
that's
pretty
cool,
all
right
and
then
upcoming
next
week,
there's
a
blog
post,
that's
pending
for
the
ytt
validation
stuff,
we'll
hear
about
ytt
validations
in
a
little
bit,
but
that
look
for
that
this
next
week
and
yeah,
you
know
you're
seeing
a
lot
of
stuff
coming
out
of
the
the
maintainers
corner
in
terms
of
content
sharing,
but
actually
we'd
love
to
hear
from
you
too.
There's
a
really
easy
way
to
do
this,
there's
a
little
sign
up
sheet.
A
You
can
go
down
in
here
and
do
a
PR
on
this
page.
Put
your
name
in
pick
a
date
and
let
us
know
what
topic
and
what
format
it
might
be.
Is
it
written
a
video
or
what
have
you
and
if
you
have
any
questions
about
that,
just
come
to
our
slack
Channel
and
if
you're,
not
a
maintainer
on
on
the
project,
we'd
love
to
thank
you
for
your
contribution
and
drop
some
swag
over
your
way.
These
are
some
pretty
nice
looking
t-shirts
and
and
whatnot.
So
anyway,.
F
A
Yeah
yeah
definitely
yeah.
If
you
know,
treatments
on
how
to
get
large
grains
of
dirt
and
sand
out
that'd
be
that'll,
come
really
important
being
out
of
the
sandbox
in
the
same
box.
Thank
you,
Joe,
it's
good
stuff,
all
right,
and
then
this
week
we've
got
two
releases
already,
since
the
last
time
we
all
met
together.
One
of
them
is
image
package
version
0.32.
This
is
an
important
one,
so
image
package
032
has
a
deprecation,
so
pay
attention.
So
there
used
to
be
well.
A
There
still
is
an
environment
variable
called
image
package
enable
is
auth
and
it
didn't
work
out
as
great
as
we
wish
it
would.
It
was
authenticating
against
all
of
the
keychains
which
created
problems
of
all
kinds,
and
it
created
a
bunch
of
communication.
You
probably
wouldn't
want
so
we
have
a
replacement
for
that
which
is
for
you
to
select
which
keychain
you
want
to
have
active.
We
have
a
number
of
these
that
you
can
select
from,
and
only
those
that
you
configure
are
the
ones
that
get
used.
A
It
was
some
work
to
get
this
to
to
come
together.
We
really
appreciate
Ben
Moss's
contribution
on
that
particular
fix.
That's
that's
the
Highlight
here
there's
also
some
some
API
changes
to
take
a
look
for
those
who
are
integrating
with
image
package
as
a
go
module
so
check
out
the
release,
notes,
that's
image,
package,
32.
F
Yeah
well,
they're,
really
the
most
exciting
thing
about
it
is
that
it
goes
to
11.
previous
versions
of
secret.
Gen
controller
can
only
go
up
to
10
or
10.3.
This
one
goes
all
the
way
to
11..
It's
do
you
ever
look
at
an
open
source
project
and
you're
like
oh,
they
haven't
had
any
releases
in
a
while
I,
don't
know
if
I
should
use
that,
maybe
they
probably
have
security
patches
that
aren't
even
up
to
date.
F
F
A
B
The
roadmap
has
been
lightly,
updated
to
at
least
reflect
reflect
current
day.
There
are
some
things
here
that
are
penciled
in,
but
we
are
currently
actively
doing
some
roadmap
planning,
so
we'll
get
this
a
bit
more
defined
for
the
upcoming
months
over
the
next
week
or
two,
but
as
always,
please
let
us
know
if
there
is.
A
A
B
Yeah,
this
is
some
other
work
that
I
was
working
on,
so
the
vendor
work
is
supporting
cap
controller's
ability
to
be
resilient
to
either
Network
outages
or
being
unable
to
reach
a
container
registry,
so
just
making
it
a
bit
more
resilient.
So
these
features
are
definitely
linked.
It's
still
questionable,
if
we'll
make
it
into
this
next
release,
because
there
there
is
a
little
bit
more
work
to
go,
but
the
next
release
for
cap
controller
is
planned
for
what
is
that
next
Tuesday.
A
So,
let's
see,
we've
got,
are
much
anticipated,
dot,
43
release
coming
up,
and
this
is
going
to
include
validations
as
a
generally
available
feature.
We're
very
excited
about
this
in
preparation
for
that,
there's
been
a
few
updates
to
the
implementation
based
largely
off
of
feedback
we've
gotten
from
our
usability
test.
Thank
you
for
everybody
who
was
involved
in
those
we've
got
a
ton
of
feedback.
The
motion
critical
stuff
that
related
to
API
design.
A
We
were
able
to
incorporate,
there's
other
great
ideas
that
we
aspired
to
grab
grab
two
we'll
be
pulling
those
into
our
backlog.
So
it's
just
been
wonderful,
Community
effort
there
and
that
also
included
a
validation
of
our
well,
no
pun
intended
of
our
cheat
sheet
and
that's
been
something
that
we
saw
was
very
useful
in
in
those
tests.
C
Yes,
basically,
we
are
finishing
up
with
our
student
organization
dogs.
We
have
included
the
the
main
schema,
validation
related
all
functionalities
in
the
docs,
and
the
validation
cheat
sheet
will
be
very
useful
for
this
and
yeah
that's
pretty
much.
We
have
covered
a
few
things
that
came
up
through
usability
testing
and
we
created
those
stories
and
completed
work
on
that.
So
really
excited
for
this
upcoming
release.
C
A
G
Yep
school:
no,
we
did
we
and
Alpha
release
last
month,
and
after
that
we
have
been
collecting
the
feedbacks
from
users
how
they
are
using
it.
What
are
the
pain
points
or
it
related
to
the
docs?
Are
we
some
features
they
are
requesting
for
so
we
are
capturing
all
of
them
and
working
toward
them.
Creating
issues
on
the
cap
controller,
so
yeah
the
issues
are
already
created.
G
You
can
go
and
look
and
see
if
whatever
the
feature
we
are
requesting,
maybe
somebody
has
already
requested
for
it
and
we'll
encourage
to
share
your
feedback
as
much
as
possible
so
that
we
can
offer
polish
the
product
mode
and
then
so.
We
have
been
working
on
handling
the
difference
between
the
app
specs
of
packaging
sources
and
package
build
better.
We
are
and
the
as
part
of
that
responsibility
will
now
rely
on
the
user.
C
A
A
Great,
this
is
great
work
that
we're
pulling
together
a
lot
of
the
value
of
the
the
Carvel
Suite
into
what
we
hope
to
be
more
user
friendly
and
integrated
experience.
So
this
is
great
work,
cool,
all
right,
I'm.
Looking
at
the
discussion
topics,
no
one's
putting
anything
down
in
the
document
as
I
can
see.
Did
anybody
have
anything
that
came
up
or
as
a
question.
G
I
think
I
had
added
some
cap
updates,
but
I
don't
see
them
here.
Okay,
it
I
did
talk
about
renaming
cap
model,
so
I
just
caught
us
behind
it,
but
I
can
like
talk
about
what
we
have
coming
of
a
cap.
So
we
are
actually
working
on
closing
out
on
our
view
of
open
sets,
interesting
features,
and
we
would
be
making
a
release
by
end
of
this
week
so
probably
tomorrow
or
day
after,
and
that
will
also
have
the
cap
module
renamed
to
VMware
tanzu.
Finally,.
A
D
A
A
It
okay
cool!
Yes,
thanks
for
mentioning
that
Dimitri,
it's
Max
Brower
put
in
that
proposal,
and
the
idea
is
that
within
a
template,
you
should
be
able
to
parse,
manipulate
and
render
out
semantic
versioning
strings,
including
metadata
and
build
information.
So
that
proposal
is
in
progress.
Take
a
look
at
that
link
and
you'll
be
able
to
well
I.
Just
click
on
that
link.
A
Oh,
my
gosh,
my
zoom
Chrome
got
in
the
way
and
if
you
want
to
read
a
nicely
formatted
version,
that's
come
into
the
files
change,
a
save
you
file
and
GitHub
will
generously
render
this
down
as
markdown.
So
take
a
look
so
yeah.
This
is.
This
is
a
really
great
example
of
a
way
to
have
an
in-depth
conversation
about
a
pretty
significant
contribution.
D
A
Cool
yeah
I
could
give
a
tiny
bit
more
color.
It's
we've
done
at
least
a
round
of
reviews
on
that
and
Max
just
responded
to
a
lot
of
that
feedback,
including
laying
out
a
number
of
of
use
cases
that
are
that
are
driving
out
the
proposal.
So
I
feel
like
it's
at
a
point
now,
where
it
it
it's
starting
to
converge
on
at
least
what
the
the
overall
scope
of
what
that
module
will
address.
A
It
does
also
have
some
hints
about
implementation,
so
there's
stuff
that
you
can
go
poke
at
there
thinking
about
any
and
he
came
in
thinking
about
how
else
are
we
doing
sember
in
other
tools
in
carbol,
so
feel
free
to
review
that
work?
That's
definitely
been
something
that's
been
on
his
radar
since
he
started
with
that.
A
C
D
D
We
really
wanted
to
make
sure
that
you
don't
end
up
fetching
or
interacting
with
you
know,
different
content,
every
single
time,
you
let's
say
rerun
the
reconcile
or
you
run
the
vendor
sync
right.
So
we
wanted
that
guarantee
that
there
is
some
same
order
to
a
list
of
versions,
and
that
order
will,
you
know,
remain
every
time
you
run
it
every
time
you
sort
so
I
would
advocate
for
applying
the
same
library
and
hence
the
same
both
Nuance
to
this
implementation,
foreign.
A
Yeah,
that's
a
really
good
call
out.
I
know
that
there
was
the
B
Lang
December
Library
I'm,
not
sure
that
it's
mentioned
in
the
proposal
that
we
would
specifically
look
to
use
the
the
fork
from
the
k-14s
org.
That's
a
really
good
yeah!
Please
leave
a
comment
there
on
that.
So
we
don't
forget
thanks
Dimitri.