►
From YouTube: Carvel Community Meeting - February 3, 2022
Description
Carvel Community Meeting - February 3, 2022
Our first community meeting of 2022! We meet every Thursday at 10:30am Pacific Time. We'd love for you to join us live!
This week we announced our community content sharing process (please sign up to share your Carvel knowledge!), discussed the project roadmap, three new releases, versioning documentation, feedback survey, and what the team is working on this week. See all the notes here: https://hackmd.io/F7g3RT2hR3OcIh-Iznk2hw
A
Hi,
everyone
welcome
to
the
first
carville
community
meeting
of
2022..
If
you
are
watching
this
recording
from
home
just
a
reminder,
we
do
meet
every
thursday
at
10
30
a.m,
pacific
time.
So
if
you
have
anything
you
wish
to
discuss
with
the
team
or
if
you
just
want
to
sit
in
and
listen
on
what
we
got
or
meet
the
team.
Please
join
us.
We
would
love
to
get
to
know
you
and
have
you
join.
Our
meetings
live
when
you
do
join
and
you
do
have
something
you
wish
to
discuss.
A
If
you
are
using
any
of
the
carvel
tools,
we
would
love
to
know
more
about
how
you
are
using
the
tools.
So
we
have
a
better
understanding
of
the
use
cases
and
to
help
us
improve
the
tools
in
the
future,
as
well
as
helping
out
others
on
on
how
they
might
be
able
to
to
utilize
the
tools
as
well.
And
if
you
add
your
logo
in
there,
we
can
add
you
to
the
adopters
page
and
help
promote
your
organization.
A
A
We
asked
a
few
questions
regarding
the
tools:
how
you're,
using
it
getting
feedback
on
what
you
might
want
to
see
in
the
future
on
the
road
map,
any
anything
that
you
want
to
discuss
regarding
the
tools
as
well
as
the
community
meeting,
so
for
2022.
We
would
like
to
do
some
improvements
to
this
meeting
to
make
sure
that
what
we're
talking
about
what
we
do
here
is
benefiting
you,
and
so
we
would
love
to
hear
if
you
attended
these
meetings
before
and
you
no
longer
attend.
A
Is
there
any
particular
reason
why,
if
you
have
never
attended,
is
there
something
that
that
we
could
do
to
improve
and
increase
your
chances
of
attending
anything
at
all
that
you
wouldn't
want
to
bring
up?
Regarding
this
meeting,
we
would
love
to
get
that
feedback
so
that
we
can
improve
what
we
we
have
going
on
in
this
meeting.
So
please
add
that
by
february
13th
and
then
from
there
we'll
we'll
start
to
to
use
that
feedback
on
how
the
roadmap
looks
and
as
well
as
this
community
meeting
on
to
some
content
stuff.
A
So
we
recently
had
how
to
use
how
to
customize
the
tonzu
community
edition-
and
I
just
add,
additional
value
using
the
carville
tool
switch
tool
set
by
scott
rosenberg
and
scott
is
an
active
community
member
both
with
us
and
tce,
and
some
other
open
source
projects
he's
been
super
helpful
in
help
helping
us
with
some
various
development
in
our
tools,
as
well
as
providing
these
interesting
presentations
to
help
the
community
understand
the
the
tools
and
other
open
source
projects
better.
So
thank
you,
scott
for
for
doing
this.
This
is
great.
A
A
As
far
as
upcoming
content,
we
have
two
webinars
that
are
with
tonzu
tv
and
again
it's
with
scott,
so
he's
a
rock
star.
We
really
appreciate
him
on
february,
8th
12
p.m.
At
pacific
time,
there's
going
to
be
a
tap
overview
and
impressions
talk
there.
There
will
be
some
elements
of
cargill
discussed
within
there
and
then
on
february
22nd.
At
the
same
time,
hill
scott
will
also
be
talking
about
carnival
packaging
as
a
unified
package
manager
for
kubernetes
scott.
Is
there
anything
that
you
wanted
to
touch
on
on
either
one
of
those.
A
Now
in
the
realm
of
content
sharing,
we
want
to
be
better
at
sharing
our
knowledge
of
karvel,
whether
that's
through
video,
through
blog
posts,
workshops,
etc,
etc,
and
we
also
want
to
invite
members
of
the
community
to
do
the
same,
because
what
the
maintainers
may
know
about
carvel
and
how
they
use
it
could
be
completely
different
on
how
users
of
the
tools
are
using
it.
So
we
are
starting
to
do
a
weekly
content
sharing
plan,
there's
a
pr
open
here
for
for
adding
it
to
our
processes,
doc.
A
D
I
guess
real,
quick,
the
I
think
a
couple
of
highlights.
First
of
all,
it's
a
power
of
two
release.
That's
a
you
know:
it's
a
big
milestone.
The
next
one
is
gonna,
be
just
as
much
work
as
the
first
one
that
this
one
was.
I
you
know
I,
the
the
cube
cuddle
get
all.
I
think
that's
a
really
good
example
of,
like
kind
of
well
ben
coming
in
and
just
being
like
hey.
D
D
If,
if
that's
important,
to
call
out
separately-
and
I
guess
the
other
thing
we
did-
is
we
reduced
our
memory
footprint
just
by
compiling
with
a
newer
version
of
go.
So
it
was
like
the
rare
case
where
there
really
was
something
in
the
language
tooling
itself,
but
luckily
someone
had
already
fixed
it.
C
E
Yep
I
can
cover
this
release
so
starting
off.
It's
version
39
released
yesterday
and
we've
got
a
new
assert
equals
package
huge
shout
out
to
nick
c
miller
for
this
contribution.
Thank
you.
There
are
three
new
schema
annotations
that
you
can
add
to
your
data
value
schema
files.
They
are
schema,
title
schema
examples
and
schema
depreciated.
E
There
is
a
new
function
added
or
a
new
parameter
to
a
function
added
to
plane,
merge
data
values
into
a
library.
So
now
you
can
add
this
parameter.
Plane
equals
true
into
your
with
data
values,
function
to
merge
data
values
in
a
similar
way
that
they
would
merge
with
the
dash
dash
data
values
file
flag.
E
Then
there's
been
some
various
error
message
improvements.
Some
inclusion
of
annotations
in
those
error
messages,
as
well
as
just
quality
of
life,
improvements
for
the
maintainers
of
ytt,
and
then
there
was
a
continuation
of
a
bug
fix
regarding
nested
schema
annotations
within
a
data
value
marked
as
an
any
type.
So
big
release
got
a
lot
in
here
and
huge.
A
Okay,
the
other
thing
to
add
on
to
the
topic
of
releases
is:
we
have
added
the
ability
to
under
documentation
and
there
are
now
versions
available
for
you
to
to
go
to
within
the
search
we
have
available
now
for
cap
controller
and
with
the
latest
release
of
ytt
that's
available.
So
as
we
continue
to
release
new
versions,
you'll
now
have
the
ability
to
click
on
the
different
documentation.
That's
associated
with
those
versions.
F
So
if
you
want
something
to
show
up
in
the
next
release
on
the
documentation,
if
you're
helping
us
with
that,
just
do
changes
on
the
develop
folder
and
if
you
do
want
to
make
changes
on
an
earlier
version
or
the
current
latest
version,
and
you
do
not
want
to
to
go
further
down
on
that
on
next
new
versions.
You
can
just
change
on
the
on
that
folder
for
that
particular
version.
So
there's
this
new
way
of
having
the
documentation
in
our
in
our
site.
F
So
I
hope
this
helps
you
when
you're
searching
for
something
the
search
is
also
related
to
that
particular
version.
So
you
will
not
like
in
version
31,
you
will
not
be
able
to
find
something
that
was
included
only
on
version
32,
for
example.
So
if
the
search
is
restricted
to
the
versions
to
help
out
so
we're
trying
to
help
out
as
much
as
we
can
you
you
all
when
you're
trying
to
look
at
our
documentation.
A
C
C
C
So
the
next
things
on
the
roadmap,
around
asset,
signing
and
verification
that
will
likely
span
multiple
tools
within
karvel,
ytt,
validations,
ytt
guides
and
examples.
These
are
all
things
that
I
think
we're
pretty
confident
and
will
be
coming
up.
We
just
haven't
yet
really
set
timelines
for
them
yet
but
yeah
as
always.
Let
us
know
if
there
are
other
things
that
you
would
like
to
see
here.
We
are
actively
planning
and
defining
our
roadmap,
so
we'll
just
share
more
as
we
define
it
more.
A
A
G
G
A
H
A
F
I'm
gonna
do
a
two
sweep
here:
okay,
build
an
image
package.
We've
been
trying
to
keep
our
dependencies
up
to
date.
That's
that
has
been
like
the
bulk
of
the
work.
We
did
start
working
on
the
on
a
feature
for
image
package
that
allow
you
to
describe
a
bundle
to
understand
what
is
part
of
the
bundle.
So
if
you
have
anything
that
you'd
like
to
see
or
something
on
that
area
feel
free
to
reach
out
to
us,
and
there
are
some
issues
that
are
being
picked
up
around
that
area.
A
H
There's
an
issue
that
I'm
taking
on
for
a
secret
gen
controller
just
about
people
are
having
problems
with
like
it,
duplicating
annotations
across
secrets.
I
don't
know
if
there's
an
issue
open
for
it.
If
people
are
interested
but
yeah,
it's
a
little
bit
in
the
weeds,
but
that's
it
and
yeah
for
vendor.
I
don't
think
there's
anything
in
the
works.
A
Thanks
ben
discussion
topics-
I
had
put
this
in
here,
I
think
prematurely
regarding
the
health
checks
so
for
what
we
do
in
the
community
engagement
team
at
vmware.
We
have
launched
health
checks
in
this
repo
over
community
engagement
within
the
vmware
tanzu.org,
and
we
create
we
conduct
health
checks
for
all
of
our
open
source
projects
twice
every
six
months
so
two
times
in
six
months.
A
C
F
I
think
we
can
start
deleting
those
the
ones
that
that
say
something
like
this
feature
works
starting
this
version
like
so
we
now
you
can
provide
this
flag
on
version
39
right,
there's,
like
the
only
the
caveat
of
the
verb
where
we
deprecate
something.
I
don't
think
we
ever
deprecated
a
flag
or
something
like
that,
but
when
we
do
like
the
the
caveats
should
still
be
there
saying
that
in
the
next
couple
of
releases,
we
are
going
to
remove
this,
so
be
careful.
F
F
I
F
A
A
again,
if
you're
watching
this
from
home,
we
would
love
for
you
to
come.
Join
us
live
we
meet
every
thursday
at
10,
30
a.m.
Pacific
time,
if
you
have
any
feedback
regarding
this
community
meeting
or
the
tools
themselves,
the
roadmap,
etc,
etc.
Please
fill
out
the
survey
we
would
love
to
hear
from
you.
We
would
love
to
anything
that
you
have
whatsoever,
no
matter
how
minor
or
big
we
would
would
love
to
know
what
you
think
about
anything
regarding
karvel.
So
with
that,
we
hope
to
hear
from
you.