►
From YouTube: Carvel Community Meeting - December 14, 2022
Description
Carvel Community Meeting - December 14, 2022
This week marks the last meeting until 2023! We discussed the CNCF Onboarding update and its impact on projects once we migrate, new blog posts, lots of releases, discussion topic from Thomas Vitale, and much more. Check out full notes here: https://hackmd.io/F7g3RT2hR3OcIh-Iznk2hw#December-14-2022-Agenda
A
A
It's
an
opportunity
for
you
to
come
and
join
other
members
of
the
community
here
with
the
maintainers
are
working
on
bring
any
discussion
topics
to
the
meeting
anything
that
you
need
help
with
when
it
comes
to
to
carble-
and
you
know-
or
you
can
just
sit
and
listen
in
if
you
are
here
at
the
meeting
today-
and
you
do
have
a
discussion
item.
Please
add
that
down
below
in
the
section
of
discussion
topics
here
and
we'll
get
to
it
towards
the
end
of
the
meeting.
A
If
you're
unable
to
join
us
live
for
a
meeting,
there
are
other
ways
for
you
to
reach
out
to
us.
You
can.
We
can
be
found
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
in
Twitter
at
Carvel
underscore
Dev.
A
And
if
you're
a
list,
if
you
are
using
any
of
the
cargo
tools,
we
would
like
to
know
more
details
about
how
you
are
using
the
tools.
So
we've
created
this
pinned
issue,
and
it
just
asks
for
you
to
provide
a
few
details
about
yourself,
any
organization
or
company
representing
and
your
use
cases
with
Carvel
optionally.
You
can
add
your
logo
to
the
comment
itself
and
we
can
get
that
added
to
the
adopters
file
here
for
those
that
are
attending
today's
meeting.
A
On
to
announcements,
so
while
we
do
meet
every
second
and
fourth
Wednesday
of
the
month
at
8
A.M
Pacific
time,
we
are
not
meeting
until
January
11th,
given
all
the
holidays
and
everything
so
we're
going
to
have
a
bit
of
a
break
and
until
next
year
and
on
January
11th.
So
we
will
see
you
then,
when
we
reconvene.
A
A
So
once
we
do
that
everything
else
will
just
kind
of
happen
really
fast
and
then
everything
will
be
complete.
So
that's
one
of
the
biggest
things
and
after
we
do
that
we're
gonna
migrate,
our
our
website
and
domain
transfer
and
all
that
to
cncf.
So
I
just
wanted
to
give
you
all
an
update
there,
we're
we're
still
very
much
working
on
it
and
hopefully
we'll
have
it
complete
by
you
know:
mid-January
I'm
thinking.
A
And
then
on
to
content
so
content.
Since
last
meeting
we
had
a
blog
post
using
q
and
Carvel
together
for
your
kubernetes
soda.
This
was
written
by
Dimitri
and
Dimitri
is
one
of
the
the
kind
of
founders
of
Carvel
one
who
you
know
started
creating
carbon
to
begin
with
so
be
sure
to
check
that
out,
and
then
we
have
getting
started.
Ytt
part
two.
This
is
a
video
tutorial
and
also
has
a
blog
post
accompaniment
and
then
the
kubecon
keynote
we
did
for
kubecon
or
North
America
in
October
was
posted
on
YouTube.
A
Once
we
have
links
and
more
details,
there
I'll
be
sure
to
share
it,
both
on
through
email
and
Twitter
and
slack
I.
Think
there's
a
couple
of
them
that
might
happen
before
our
next
meeting
so
just
take.
Take
a
keep.
Keep
your
eyes
out
on
those
other
channels
for
that
information
and
then,
as
far
as
content
goes
it's
not
just
limited
to
us.
A
We
would
love
for
the
community
to
also
share
things
that
they're
working
on
with
Carvel,
so
we've
created
this
sign
up
sheet
here
on
our
repo
and
if
there's
anything
you
wish
to
share,
you
can
add
your
the
date.
You
want
it
to
be
shared
your
name.
What
topic
you're
going
to
be
discussing,
how
you're
going
to
be
delivering
that
information?
Is
it
a
Blog,
a
video
or
you
have
an
upcoming
talk
about
Carvel,
etc,
etc?
A
A
B
C
B
Into
the
benefits,
so
this
is
going
to
be
like
somewhat
of
a
theme
like
on
the
last
couple
of
weeks,
we've
been
releasing
a
lot
of
I've,
been
bumping
a
lot
to
our
tools,
because
there
were
some
cves
that
we
were
trying
to
catch
to,
to
get
not
to
catch
but
to
to
fix.
This
is
one
of
the.
This
is
one
of
the
releases
we
did.
We
also
created
a
bunch
of
patches
for
other
releases
and
you
might
have
seen
them
coming
out
and
yeah.
B
B
B
Tool
in
the
suite
image
package
there
we
go
image
packets,
wherever
new
things
added
to
image
package.
So
we
also
did
some
bumping
up
libraries
to
fix
some
some
issues
and
so
on,
but
we
did
two
things.
One
was
that
there
was
like
it's
like
every
time
that
you
run
a
command.
There's
like
this
one
message
that
in
the
end
says
that
it
finished
successfully
the
the
command
and
unfortunately,
that
was
being
pushed
into
to
the
wrong
output
and
there's
a
fix
for
that.
That's
line,
oh.
B
Okay,
you
see,
that's
that's
what
happens
when
you
release
things
a
month
ago,
and
then
you
don't
see
them
again.
So
this
fix
is
a
little
bit
different.
So
Vic
helped
us
out
in
here
and
basically,
when
you're
trying
to
create
a
bash
complex
completion,
there
will
recommend
that
we're
being
added
there
and
then
that
that
that
message
was
showing
up
when
you're
trying
to
create
a
completion
for
your
bash
or
for
Z
for
your
zich
or
something
or
your
fish
or
whatever
your
you
use.
So
that
was
causing
problems.
B
So
that's
when
I'm
fixed
there
and
describe
now
it
it
changed
a
little
bit
how
the
describe
command
Works.
Previously
it
gathered
all
the
information,
and
while
it
was
gathering
your
information,
if
there
was
any
kind
of
failure,
if
you
couldn't
talk
to
the
registry
or
something
it
would
just
abort
it,
it
wouldn't
show
anything
right.
B
So
from
version
note,
34
forward,
what's
going
to
happen,
is
that
it's
going
to
get
you
all
the
information
that
it
can
and
if
there's
an
error,
it
just
displays
everything
that
it
could
provide
you
and
also
tells
you
like.
Oh
by
the
way,
this
one
particular
image
there
was
an
error
trying
to
get
it.
So
it's
making
it
a
little
bit
more
robust
in
here
I
think.
That's
it
for
image
package.
C
E
Yeah
they're
in
ytt
as
well.
We
have
a
little
bit
of
additions
by
a
Max
Pro
in
this
release
and
for
like
storing
the
replace
and
insert
annotations
via
quarks
as
callable
and
a
few
more
documenting.
Why
did
you
overlay
inserts?
So
this
is
part
of
0.44.0
and
0.44.1?
Is
part
of
bumping,
go
library
and
everything
for
fixing
CVS.
E
C
C
Second
thing
is
weight
check
interval.
We
have
increased
to
three
seconds
as
a
performance
enhancements,
so
it
is
helping
to
decrease
the
API
cause
we
made
to
the
server
and
yeah,
and
then
there
are
small
contribution
from
Max
who's,
adding
template
rules
for
packaging
resources
like
package
repository
package,
installs
apps
and
one
more
contribution
from.
C
A
F
I
think
so
this
one
just
came
out
yesterday,
the
vast
majority.
It's
like
a
little
bit
hard
to
to
to
grok
this
release.
Note
message,
but
the
vast
majority
are
bumps
to
third-party
dependencies,
but
I
did
want
to
call
out
that
we
have
Thomas
on
the
call
and
Thomas
did
their
first
contribution
to
key
control
Dev.
So
thank
you
for
that.
A
So,
as
you
can
see,
the
team's
been
focused
on
some
cves.
Primarily,
it's
been
kind
of
a
big
task
that
they're
all
focused
on
until
the
end
of
the
year,
and
you
know
once
we
we
complete
all
these
tasks,
that's
when
we're
really
hoping
to
have
a
bit
of
a
lull
to
migrate
the
repos
over
to
the
the
new
org.
So
if
you
have
any
questions
on
that,
just
let
us
know.
A
H
A
B
Maybe
I
can
I
can
again
so
like
we
do
inactive
development
for
image
package.
We
have
Alex
that
Alexa
is
providing
more
information
to
describe
comments,
so
we're
gonna
have
some
layering
information.
What
are
layers
that
are
part
of
the
images
and
so
on,
so
they
are
currently
on
the
process
of
it,
and
bandana
is
also
creating
another
PR
that
that
there
was
like
problem
with
certificates
in
Windows
and
go
fix
the
issue,
and
then
they
are
trying
to
put
it
back
into
our
code
because
we
had
a
work
around
there.
G
How
is
the
consumer
experience
for
packages?
And
specifically,
this
issue
is
about
having
the
namespace
created
automatically
when
we
add
the
repository,
because
right
now,
like
the
the
flow,
is
I
create
a
namespace,
then
I
add
the
repository
and
then
I
install
a
package.
So
it
would
be
nice
to
have
the
step
where
I
add
the
repository.
A
H
H
H
A
A
B
No
I
was
just
gonna
say,
maybe
it
would
make
sense
for
us
to
like
if,
if
there
were
reasons
why
we
didn't,
we
didn't
implement
this
before
or
like
get
something
on
it.
It
would
be
good
if
whoever
is
in
the
know
commented
on
this
issue
so
that
we
can
have
a
discussion
there.
So
at
least,
if
we
do
it
or
we
don't
do
it
at
least
there's
like
information
that
is
spread
out
on
what
what
are
the
reasons.
G
Yeah,
so
it's
the
same
context-
and
this
comes
from,
for
example,
feedback
because
I
really
like
working
with
Carvel
and
so
I
show
it
to
people
like.
Have
you
tried
Carvel
packages?
It's
so
great,
give
it
a
try
and
the
feedback.
What
some
of
the
feedback
is
about,
having
like
the
setup
in
an
research
setting,
so
I'm
not
talking
about
production,
but
maybe
on
the
developer
machine
when
setting
these
up.
G
Is
this
a
few
different
commands
to
run
and
usually
I,
get
it
compared
to
helm
where
I
do
help
add
repo
help
install
its
two
commands?
So
I
was
trying
to
think
about
how
to
reduce
the
number
of
commands.
That
right
now
is
probably
five
commands
where
I
also
have
to
install
cup
controller
first,
so
I
wanted
to
share
this
idea
of
having
perhaps
K
control
doing
that
so
that
overall,
we
might
have
three
steps.
G
A
A
F
All
right,
I'll
go
first,
I
think
it's
a
great
idea,
I
think
it's
one
that
I
have
also
found,
as
you
get
started
with
the
whole
Suite
with
cap
controller
in
particular,
is
that
we
are
directing
people
to
K
control.
As
the
you
know,
most
user-friendly
paths
and
the
experience
tends
to
be
a
little
better
there
than
writing
lots
of
yaml,
so
I
think
having
some
sort
of
way
to
install
it
or
even
instructions
to
install
it.
D
A
F
I
guess
I
imagine
I
could
foresee
a
conversation
happening
around
permissions
and
like
giving
kid
control
or
something
like
all
the
permissions
and
how
that
would
work
to
install
a
cap,
controller
and
so
I
guess,
just
as
we
create
the
issue
I.
Imagine
that
will
be
like
a
discussion
if
you
want
to
preempt
it.
But
if
you
don't
that's
totally
fine,
just
bringing
it
up
early.
A
A
F
One
last
thing:
we
talked
about
the
cncf
migration
and
it
sounds
like
you
know,
a
little
high
level
from
that
perspective.
But
if
anyone
in
the
community
is
using
any
of
the
corval
tools
as
go
modules,
the
URL
will
change.
The
organization
is
going
to
be
changing.
So
that
is
a
breaking
change
that
is
coming
in
the
next
versions
or
I
guess
when
it
happens,
and
then
the
following
release
after
it.
F
F
A
A
Well,
thank
you,
everyone
for
joining
for
our
last
community
meeting
of
the
year
for
those
watching
you
watching
from
home.
We
encourage
you
to
come.
Join
us
live
again.
We
meet
every
second
and
fourth
Wednesday
of
the
month
at
8
A.M
Pacific
time,
and
we
will
meet
again
on
January
11th
of
2023.
So
we
hope
to
see
you
then,
for
that,
thank
you
and
happy
holidays.
Everyone.