►
From YouTube: Carvel Community Meeting - February 17, 2022
Description
Carvel Community Meeting - February 17, 2022
We meet every Thursday at 10:30am PT. We'd love for you to join us live!
See full notes and agenda from this week's meeting here: https://hackmd.io/F7g3RT2hR3OcIh-Iznk2hw#February-17-2022-Agenda
A
A
A
When
you
attend
these
meetings,
we
ask
that
you
please
read
and
abide
by
our
code
of
conduct.
Thank
you
and
if
you
have
anything
you
want
to
discuss
with
the
team,
please
add
that
to
the
discussion
topic
sections
down
here
right
there
add
that
into
that
section
and
and
we'll
definitely
prioritize
and
get
to
that
now
when
you
attend,
we
ask
that
you
put
your
name
in
like
you
see
happening
up
here,
and
we
do
that.
A
A
A
B
A
Thank
you,
sorry
about
that.
So
yeah
check
that
out
and
then
upcoming.
We
have
a
webinar
on
put
with
our
own
scott
rosenberg
and
by
our
own
I
mean
a
great
friend
of
of
the
project
scott's
here
today.
Actually
scott's
gonna
be
hanging
out
with
lee
dan
and
whitney
and
and
talking
about
a
unified
package
manager
for
kubernetes
scott.
Did
you
want
to
say
a
few
words
about
about
that.
C
Yeah,
so
it's
really
going
to
be
a
webinar
talking
about
the
carvel
packaging
apis
and
using
it
for
helm,
raw
yaml
ytt,
really
trying
to
create
that
unified
experience
and
then
digging
deep
into
like
how
you
can
convert
helm
charts
into
carvel
packages
and
how
to
utilize
ytt
with
helm
and
all
of
that
just
to
really
gain
a
great
package.
Experience
on
kubernetes.
A
That
sounds
sweet
all
right,
I'm
booking
myself
on
that
on
text,
tuesday,
okay,
cool
wow,
thanks
man.
Looking
forward
to
that
all
right!
So
that's
that's
it
for
our
content,
but
wanted
to
invite
you
if
you
are
interested
in
sharing
your
knowledge
and
experience
around
car,
but
we'd
love
to
hear
from
you.
We
have
a
sign
up
form
here.
Take
a
look!
A
It's
just
a
matter
of
dropping
a
pr
on
this
page
and
look.
We've
got
folks
that
are
already
signing
up
grabbing
spots.
If
you
have
stuff
that
you
want
to
share
absolutely
get
up
in
here
and
if
you're,
not
one
of
the
maintainers
as
a
as
a
token
of
our
gratitude,
we'll
drop
you
a
t-shirt
so
anyway
check
that
out
all
right,
any
other
announcements
that
maybe
didn't
make
it
on
the
list.
A
D
Yeah
we've
been
doing
some
road
mapping
on
the
project,
so
provided
some
some
light
updates.
Here
with
some
rough
timelines,
you
can
kind
of
see
a
few
themes
throughout
the
tools
regarding
stability,
easy
to
get
started
as
well
as
just
some
kind
of
general
enhancements
that
we
think
are
good
value
adds
to
the
tool
set,
but
please
feel
free
to
give
this
a
review.
D
You
know,
let
us
know
if
you
have
any
feedback,
and
I
saw
that
we
have
a
discussion
topic
today
to
discuss
the
granularity
of
the
roadmap,
but
as
of
right
now
we're
only
kind
of
showing
some
of
the
things
that
I
would
consider
like
the
the
bigger
tracks
of
work,
things
that
would
take
you
know,
weeks
to
months
to
do
rather
than
some
of
the
regular
releases
that
have
smaller
features
but
yeah.
Please,
please
give
it
a
review
and
let
us
know
if
you
have
any
thoughts
or
questions.
A
E
G
Want
to
highlight
so
for
for
the
image
package,
a
couple
of
things
have
been
happening.
We
got
a
contribution
from
the
community
for
one
on
one
issue
that
I
think
we'll
we'll
have
to
discuss
a
little
bit
on
on
what
it
looks
like,
and
basically
it
enables
image
package
to
create
tags
when
it
copies
an
image
from
one
repo
to
another.
It
creates
a
tag
that
is
somewhat
human,
readable
and
so
there's
an
implementation
for
that.
G
G
You'll
be
in
progress,
it
should
be
like
it
should
be
in
progress.
Maybe
maybe
they
didn't
connect.
The
the
add,
legible
tags,
three,
three,
three
yeah!
Well,
the
issue
is
three
three
one,
so
they
didn't
connect
issue.
Okay,
we
should
connect
that
to
you
but
yeah.
So,
basically,
that's
it.
So
there's
a
little
bit
of
more
work.
I'm
gonna
write
something
down
today
or
tomorrow
on
the
review
of
this
pr.
G
The
other
thing
that
we
that
we're
working
on
image
package
is
something
that
we
noticed
where,
if
you
have
an
off,
if
you
ever
like
a
registry
that
uses
oauth
to
to
authenticate
image
package
was
doing
for
every
request
that
it
did
to
try
to
push
an
image
or
to
read
an
image.
It
was
trying
to
get
the
token
from
the
oauth
server
and
that
was
causing
some
issues.
G
So
that's
that's!
A
change
there
that
were
that
we've
been
working
on
as
well
as,
like
I
said,
I
think,
as
I
said
last
week,
we're
also
working
on
a
scrap
command
that
will
provide
a
little
bit
more
feedback
on
what
is
part
of
the
bundle
and,
what's
not
part
of
one
word,
it
was
like
what
are
the
the
images
that
are
part
of
the
bundle
and
where
they
came
from
and
so
on.
So
that's
the
the
issue.
That's
that's
been
under
development,
so
I
think
that's
it
for
image
package
and.
A
B
Well,
yeah,
I
mean
look
like
when
I
play
with
packages.
I
might
have
tens
of
packages
at
the
most
installed
and
when
scott
is
talking
about,
oh,
I
can
shovel
anything
from
helm
into
a
package.
I
was
just
wondering
like
do
you?
Do
you
have
a
sense
scott,
like
order
of
magnitude
how
many
packages
you
you've
run
on
a
system
installed.
C
Except
for
the
fact
that
cube,
ctl
chunks
things
and
then
you
don't
get
them
all
out
with
cube
ctl
get
packages
and
then
trying
to
figure
out
how
to
set
the
chunk
size
when
doing
it
from
a
client
which
is
fun
and
very
poorly
documented
in
kubernetes.
It
was,
you
know,
perfectly
fine.
You
know
I
was
starting
to
get
some
issues
of
in
certain
cases
where
it
was
loading
on
the
api
server.
C
B
C
Yeah
the
best
example
that
I
have
is
when
I
bring
in
the
I
built
one
for
the
entire
bitnami
repository,
which
has
96
helm,
charts,
and
I
took
the
last
10
versions
and
created
a
package
repository
with
960
packages
within
it
that
were
installed,
and
then
I
also
had
like
the
tce1
there.
So
that's
how
I
got
to
a
bit
higher
than
that,
so
it
was
tc
plus
that
in
that
case,.
B
A
G
G
What
are
the
ideas
that
we
have
for
the
next
release
of
like,
for
example,
like
which
package
like
what
are
the
features
that
that
we
can
expect
to
have
on
the
next
version,
or
something
like
that.
So
I'm
not
sure
what
you
all
think
about
it
like.
What
are
your
ideas
if
you
think
that
the
current
information
is
enough,
or
if
you
should
provide
more
information
on.
A
E
E
A
D
A
Oh
sorry,
go
ahead,
alright
I'll
go
for
it,
I'm
just
going
to
say
quick
asterisk
there.
I
just
learned
this
this
morning.
Carrie
turns
out.
Zam
zenhub
has
finally
implemented
a
in
window
like
in
html
without
needing
an
extension
view,
and
that's
that's
actually.
I
was
using
this
morning
as
we
were
going
through
through
that.
I
I've
never
seen
it
before
today,
so
I
don't
know
how
how
absolutely
new
that
is,
but
so
there's
something
there
where
you
don't
have
to
have
the
extension
in
order
to
to
view
the
backlog.
D
D
I
think
going
back
to
carrie's
question
about
who
is
the
roadmap
for
so
far
the
intention
has
been
for
the
community
at
large
just
to
provide
general
transparency
into
what
the
project
has
planned.
So
it
would
be
great
to
hear
from
the
community.
I
guess
like
what
is
the
level
of
detail
that
that
folks
are
looking
for.
D
I
don't
know
proactive
planning
around
we've
we've
been
pretty,
I
don't
know
just
serendipitous
with
when
we
cut
certain
releases,
sometimes
someone's
asking
for
it.
Sometimes
it's
just
been
a
while,
so
we
don't
have
any
sort
of
a
regular.
You
know
monthly
type
cadence
at
the
moment,
but
again
we're
certainly
open
to
feedback
on
all
of
this.
C
And
I
think
that,
from
my
side
I
would
say
you
know,
I
think,
that
the
best
example
of
road
maps
in
an
open
source
that
I've
seen
have
been
tanzu
community
edition,
actually
where
they
actually
have.
Two-
and
I
know
that's
extra
maintenance,
but
they
have
a
high
level,
one
which
is
just
roadmap.md,
which
has
you
know
the
high
level
what's
being
planned
for
the
next
year,
high
level
kind
of
tasks
you
know
whatever,
and
then
there's
the
engineering
roadmap,
which
has
more
detail.
C
It's
not
going
into
the
level
of
a
zen
hub
or
you
know,
looking
at
a
backlog
but
going
into
more
detail
of
what
those
things
actually
entail
and
they
have
like
the
links
to
the
issues
that
are
relevant
in
there
and
it
allows
kind
of
that
two-leveled
view,
because
I
think
there
are
two
types
of
users:
there's
the
people
that
just
want
to
look
and
see
very
quickly.
Okay,
what
what
is
the
general
approach
that's
being
taken?
Where
is
the
product
going?
C
And
then
there
are
people
who
are
actually
looking
for
a
feature
and
want
to
understand
making
cap
more
stable.
Well
is
what
I
believe
that
making
cap
more
stable
is
actually
included
in
that
task,
or
in
that
larger
you
know,
kind
of
bucket
and
having
those
two
road
maps
makes
it
a
bit
easier.
It
doesn't
overwhelm
the
person
who
just
wants
to
get
a
general
idea,
but
gives
also
the
detail
for
those
looking
for
it.
I
personally
have
never
logged
into
zenhub
out
of
principle,
so
I
have
never
seen
the
backlog.
D
C
That's
just
there
that
the
engineering
roadmap
is
a
pinned
issue
that
they
have
just
on
the
top
of
the
issues
so
anyways
someone
that
would
be
going
there
is
someone,
that's
probably
looking
for
a
bit
more
detail
when
they
go
to
the
issue
tab
and
that's
going
to
be
at
the
top
of
the
issues.
So
it's
a
nice
way
of
doing
it
as
well.
A
B
B
B
So
I
just-
and
you
know,
he's
he's
very-
the
author
is
very
enthusiastic
about
the
ytt
templating
also,
so
I
I
thought
I
just
noticed
it
as
I
thought
this
would
be
just
a
good
moment
to
share
this
project.
You
know
because
it
really
establishes
carville.
As
a
you
know,
a
thought
leader
in
the
space
of
of
get
ops.