►
From YouTube: Carvel Community Meeting - October 28, 2021
Description
Carvel Community Meeting - October 28, 2021
We meet every Thursday at 10:30am PT. We'd love for you to join us live!
Agenda for this week's meeting can be found here: https://hackmd.io/F7g3RT2hR3OcIh-Iznk2hw#October-28-2021-Agenda
A
A
Pacific
time
it's
an
opportunity
for
you
to
meet
the
maintainers
that
are
working
on
the
carvel
tools,
bring
up
anything
you
wish
to
discuss
with
them
or
need
help
with,
or
you
know,
just
simply
listen
and
participate,
and
and
however
you
you
wish
to,
if
you
have
any
discussion
items
that
you
do
want
to
bring
up
with
the
team.
Please
add
those
down
at
the
bottom
of
the
agenda
in
the
discussion
topics
section
and
we'll
get
to
that
towards
the
end
of
the
meeting.
A
If
you
aren't
able
to
make
it
to
this
meeting
and
wish
to
connect
with
us,
we
can
be
found
on
the
carmel
channel
in
this
kubernetes
slack
workspace.
If
you
aren't
already
a
member
there,
you
can
simply
request
an
invitation
to
gain
access.
The
link
is
is
within
the
agenda
here,
and
you
can
also
find
us
on
twitter
at
carville
underscore
dev.
A
Whenever
you
are
interacting
with
the
carville
team,
whether
it
be
in
twitter,
kubernetes,
slack
github,
whatever
avenue
you
find
us
yeah,
so
you
please
read
and
abide
by
our
code
of
conduct.
A
Next
up,
when
you
are
attending
these
meetings,
please
put
your
name
and
the
organization
that
you
are
representing
that
helps
us
keep
track
of
who,
from
outside
of
the
maintainers
are
joining,
and
we
can
keep
those
lines
of
communication
open,
and
we
also
ask
that
you
put
some
details
on
how
you
are
using
the
carbon
tools.
When
then,
this
pinned
issue
that
goes
over,
like
what's
your
organization
link
to
your
website,
how
you're
using
the
the
carvel
tools
and
then
you
can
also
add
your
company's
logo
for
a
little
bit
of
cross
promotion.
B
A
Yeah,
okay,
on
to
announcements,
just
a
couple
of
items:
here
we
had
some
releases
over
the
last
few
days.
We
have
image
package,
21
and
22,
and
then
cap
controller
29
anybody
available
to
go
over
image
package.
What
happened
there.
B
Yeah,
I
can
talk
to
a
little
bit
about
why
we
have
two
releases
back
to
back
we're
in
the
midst
of
migrating
finishing
our
migration
from
the
k14s
github
org
into
the
vmware
tantu
github
org,
and
as
a
part
of
that,
the
the
each
of
the
projects
declare
their
module,
usually
with
that
url
that,
where
they're
hosted
at
so
today,
if
you
were
integrating
with
tools
like
image
package
before
release,
2
2
0.22
you'd
be
referring
to
the
k14s
after
that
release,
if
you're
integrating
programmatically
with
image
package,
if
you're
using
it
as
a
dependency
for
your
co
project.
B
Now
you
would
use
the
vmware
tonzo
based
url,
that's
in
there,
and
we
wanted
to
have
that
as
a
separate
change
completely
separate
release
completely,
so
that
if
you
needed
any
of
the
features
that
we
released
in
0.21
that
you
could
enjoy
those
without
having
to
necessarily
take
on
that
that
change,
but
from
0.22
on
you'll
need
to
to
make
that
change
in
your
dependencies.
If
you're
programmatically,
integrating
with
image
package.
C
You
know
I
wasn't
involved,
but
I
think
it's
kind
of
a
cool
story,
because
in
some
ways
almost
none
of
us
was
involved.
This
is
basically
a
contribution
from
the
open
source
community
that
then,
basically
so
that
this
contributor
could
use
what
they
had
contributed
promptly.
Dimitri
cut
a
release,
and
so
it
I
I
add,
some
helps
us
work
with
helm
better
in
in
our
packages
to
consume
health
charts,
and
I
I
really
couldn't
tell
you
more
than
that.
That's
the
beauty
of
open
source.
A
Onto
project
roadmap,
any
updates
to
share
here
from
last
week,
cytt
guides
and
examples
that
seems
to
be
new.
I
know
it's
tbd,
but
anybody
want
to
go
over.
D
Yeah,
I
can
share
at
a
high
level
state
of
the
road
map
for
for
the
cap.
The
first
item:
I
think
that
work
is
still
in
progress.
I
know
it's
just
like
a
substantial
feature,
but
looking
at
the
backlog,
it
seems
like
it's.
It's
still
being
worked
on
ytt
side
of
things.
The
export
ytt
schema
as
open
api
schema
is,
is
definitely
a
top
priority
and
something
that
we're
continuing
to
work
on.
After
that
we
can
see
lots
of
tbd
items.
I
would
say
roughly
like
these
this.
D
This
looks
like
the
order
of
priorities,
at
least
if
you
were
to
filter
by
tool.
But
what
this
probably
signals
is
that
it's
time
for,
like
another
quarterly
planning
meeting
where
we
can
flesh
out
some
of
these
timelines
and
estimates
a
little
bit
better,
so
so
yeah,
that's,
I
think,
for
the
most
part,
most
things
in
here
are
the
same.
We
just
have
started
to
remove
things
as
they've
been
completed,
which
is
why
it's
a
bit
shallower
from
the
timeline
perspective.
A
C
I
think
I
I
could
share
on
cap
controller,
there's
an
issue
that
a
few
people
have
bumped
into
where
it
turns
out.
If
you
do
it
just
just
wrong,
you
can
have
a
package
repository
and
a
package
sharing
the
same
name
and
cap
cap
controller
doesn't
handle
that
gracefully.
C
So
neil
and
I
have
had
kind
of
a
a
back
burner,
but
you
know
kind
of
one
or
two
hours
a
day
for
the
last
couple
days
of
digging
into
that
and
trying
to
understand
whether
there's
a
an
easy
way
out
or
or
there's
an
obvious
longer
road
out
and
we're
we're
still,
you
know,
checking
for
shortcuts,
and
so
that
that'll,
I
forget,
you
know,
there's
a
story.
C
I
I
couldn't
tell
you
where
it
has
a
number:
it
has
a
ticket,
it
exists
in
in
our
backlog
somewhere,
but
it's
anyways
the
end.
E
I'm
just
going
to
toss
out
that
I
met
with
dennis
and
zhao
earlier
this
week
and
they
kind
of
got
me
going
on
another
image
package
issue,
one
that
I
actually
proposed,
which
is
adding
a
tag.
E
E
This
goes
back
to.
We
were
having
some
issues
with
tce
where
packages
that
got
pushed
up
if
their
their
tag
got
removed,
then
harbor
would
come
around
and
garbage
collect
the
you
know
the
image.
So
if
we
always
have
some
sort
of
default
tag,
images
won't
get
garbage
collected
and
deleted
anymore.
So.
B
I
got
a
little
one.
That's
kind
of
that
might
be
under
the
radar
that
you
know
if
you're,
if
you're
watching
this
recording
and
you'd
be
rewarded.
By
being
here,
the
in
the
in
the
ytt
lan,
there's
there's
been
an
uptick
in
people
wanting
to
use
ytt
as
a
project
dependency,
not
just
the
command
line
tool
but
like
actually
use
ytt's
templating
capabilities
in
their
own
projects.
B
B
B
So
this
is
just
right
now
we're
trying
to
document
the
current
state
you
can
see.
This
is
a
work
in
progress.
So
here's
my
call
to
action.
If
you
have
an
interest
in
if
you're
thinking
about
integrating
with
ytt
programmatically
now
is
a
great
time
to
influence
what
sort
of
apis
we
will
develop
in
addition
to
the
one
that
we
have
today,
which
we
understand
is
a
little
bit
clunky
at
the
moment,
we
there's
a
couple
examples
of
integration
in
here
you
can
kind
of
get
started
with
even
just
the
stuff.
B
That's
in
this
pr,
but
we'd
love
to
hear
from
you.
So
if
you,
if
this
is
the
kind
of
thing
that
you're
interested
in
in
doing
soon,
let
your
voice
be
heard.
If
you
have
opinions
about
what
that
api
should
look
like,
you
can
either
comment
on
that
pr.
You
could
just
drop
into
the
slack
channel
like
all
of
those.
B
There
is
no
ether
in
this
project
like
your
requests
or
our
notes.
Don't
just
disappear,
we'll
see
it,
but
the
slack
channel
is
the
most
visible
love
to
hear
from
you.
A
A
Well
thanks
everyone
for
joining
today.
Again,
if
you're
watching
this
from
home,
we
encourage
you
to
come.
Join
us
live
we
meet
every
thursday
at
10.
30
am
pacific
time,
and
so
until
then
have
a
good
rest
of
your
week
enjoy
your
weekend.