►
From YouTube: Carvel Community Meeting - February 24, 2022
Description
Carvel Community Meeting - February 24, 2022
We meet every Thursday at 10:30am PT. We'd love for you to join us live!
This week's meeting notes can be found here:
https://hackmd.io/F7g3RT2hR3OcIh-Iznk2hw#February-24-2022-Agenda
A
A
If
you're
watching
a
recording
of
this
from
home,
we
want
to
remind
you,
you
can
come
join
us
live.
We
do
meet
every
thursday
at
10
30
a.m.
Pacific
time,
if
you're
unable
to
join
these
meetings,
you
can
always
find
us
on
slack
and
twitter.
You
can
look
at
those
details
here.
If
you're,
not
a
member
of
the
kubernetes
slack
workspace,
you
can
just
simply
request
an
invitation
to
gain
access
and
then
our
twin
door
handle
is
at
carville
underscore
dev
right
here.
A
One
of
one
of
the
things
we
ask
of
the
community
if,
whenever
you're
attending
the
community
meetings
or
engaging
with
us,
is
to
read
and
abide
by
our
code
of
conduct,
and
that's
just
so
you
could
go
to
the
repo
here.
Code
of
conduct
is
listed
out
here
and
we
just
appreciate
you
following
that.
Whenever
you're
you're
interacting
with
us,
no
matter
what
platform
you're
on.
A
A
Next
up
for
announcements,
we
want
to
remind
you.
This
is
a
final
call
out
we're
looking
for
feedback
on
the
karbal
tools
as
well
as
the
community
meeting
here,
and
you
know
we
want
to
know
what
are
the
ways
that
we
can
improve
the
tools.
What
are
the
ways
that
we
can
improve
this
meeting?
We
want
to
make
sure
that
the
way
that
we
work
is
benefiting
you
as
well,
and
you
know
the
only
way
to
do
that
is
to
hear
from
you.
So
we
would
love
for
you
to
fill
out
this.
A
You
know
we're
asking
anyone
from
the
community,
including
the
maintainers,
to
share
their
knowledge
on
the
carvel
tools
in
whichever
way
that
they
prefer
and
anything
that
they
are
working
on
most
excited
about
anything
that
they
find
interesting,
that
they
want
to
share
with
the
community.
So
this
week
we
have
a
blog
post
by
one
of
the
maintainers
carrie
lynn,
and
it
looks
like
that
link
is
broken.
A
A
Carrie
is
out
this
week
so
next
week
she
actually
wants
to
do
a
demo
that
adds
to
that
blog
post.
So
you
can,
you
know
not
just
read
about
it.
She
can
show
you
more
in
a
demo
form
now
for
this
content
sharing
stuff.
A
If
there
is
something
that
you
find
interesting
about
karbal
that
you're
the
way
that
you're
using
it
anything
that
you
would
like
to
share
with
the
community.
We
have
a
sign
up
process
here
and
you
can
put
in
your
name
the
topic
type
of
medium,
that
you're
sharing
your
your
information
with
twitter
handle.
A
If
you
have
one,
if
you
want
us
to
tag
you
in
a
tweet
when
we
share
the
post-
and
you
can
choose
a
date
here
and
if
it's
even
further
out
in
march,
we
are
welcome
to
add
more
lines
here
to
the
date
that
works
for
you
and,
if
you're,
a
non-carnival
maintainer,
we
will
love
to
send
you
a
t-shirt
as
a
thank
you.
So
if
you
have
any
questions
regarding
that
again,
please
reach
out
to
us.
We
would
love
to
hear
from
you.
B
Yeah,
we,
I
think,
are
just
continuing
to
like
iterate
on
this
roadmap
and
updating
it.
I
think,
since
last
week
everything
is
pretty
much
holding
true
there's
just
a
bit
more
detail
to
some
of
these
things.
I
think
maybe
the
cap
controller
cli
milestone
three.
I
think
that's
one
that
was
was
added
from
from
the
carvel,
india
folks,
but
yeah.
I
think
everything
else
here
is
either
in
flight
or
in
the
planning
stages.
A
B
B
B
And
hopefully
you
know
things
things
you
won't
know
about.
A
Great
thanks,
aaron
on
to
image
package.
B
Yes,
joelle's
been
working
on
image
package
describe
command
so
way.
We
can
get
some
details
about
a
bundle,
an
image
package
bundle.
I
think
that
I
I
can
I'll
find
the
issue
and
link
it
here,
but
it's
it's
something
that
a
number
of
folks
from
the
community
have
have
asked
for,
but
a
way
to
just
provide
more
visibility
into.
B
You
know
these.
These
objects
that
we
we
call
image
package
bundles
so
that
you
know
what
it's
about,
and
you
know
don't
have
to
do
all
the
work
yourself
digging
into
it.
A
C
I
don't
think
there's
any
like
conclusions
yet
as
to
like
whether
we'll
be
actually
doing
it,
but
just
flagging
that
as
something
that
we
are
looking
at.
The
other
major
work
that
we
are
looking
at
is
today.
If
you
have
a
package
repository
or
an
app
cr
or
a
package
install-
and
it
has,
if
you've
the
same
name
for
those
they
they
conflict
due
to
like
the
underlying
deployment
method
of
camp
having
the
same
name.
C
D
D
Secondly,
we
kicked
off
our
schema
validations
track,
so
there's
been
some
work
defining
what
that
is
and
how
we're
going
to
approach
it
and
the
schema
validations
are
going
to
be
annotations
that
allow
you
to
further
restrict
the
value
of
your
data
values.
So
there's
more
information
in
the
proposal
and
yeah.
Those
are
the
updates
for
ytt.
B
Yeah
and
maybe
just
a
note
on
the
schema
validations,
we,
I
would
say
there,
there
is
a
proposal
like
there's
kind
of
like
multiple,
I
don't
know,
stages
to
the
proposal
and
we've
started
working
on
some
of
what
we
consider
like
the
non-controversial
things
like
some
of
the
basic
functionality.
But
I
know
that
john
ryan
is
interested
in
talking
with
with
folks,
regarding
you
know
some
of
the
the
ux
around
some
of
the
other
kind
of
like
functionality
based
on
top
of
the
the
basic
stuff.
B
So
if
it's
something
that
you're
interested
in
and
chatting
about,
yeah
we'd
love
to
hear
from
you.
A
Theron,
I'm
gonna
go
back
up
to
status,
update
outside
announcements
because
there's
two
things
that
I
did
not
put
in
here:
the
we
had
two
releases
this
week.
We
had
image
package
with
0.25
and
we
had
cap
with
0.46.
So
I
don't
know
if
there's
anyone
who
wants
to
talk
about
these.
A
E
So
so
this
this
this
release,
can
you
just
go
back
quickly
to
the
release
notes,
so
the
for
image
package
was
pretty
simple
release.
You
had
documentation,
so
it's
the
do.
We
we
had
a
little
bit
of
documentation
for
the
copy
command,
but
the
main
thing
was
that
there
were
people
that
were
using
the
one
of
our
packages,
the
registry
one,
and
there
was
a
little
problem
with
it
in
the
way
the
authentication
was
done
and
that's
why
that's?
E
The
main
reason
why
this
this
is
out
this
new
release
is
out,
even
though
it
is
about.
This
only
affects
people
that
are
consuming
our
registry
as
a
library,
not
people
that
are
using
the
the
tool
itself.
So,
if
you're
using
the
image
package
as
a
library
and
you're
using
the
the
registry
package,
just
take
a
look
at
this
pr
and
and
maybe
there
there
might
have
be
having
some
errors
that
you
were
not
expecting.
So
that's
that's
the
main
reason
for
it.
B
A
Thanks
aaron
for
those
of
the
of
you
that
don't
know
the
cap
team
is
primarily
based
in
india,
so
sometimes
they're
able
to
make
it
it's
very
late
for
them
to
come
to
the
community
meeting.
So
we
have
aaron
who's.
The
engineering
manager
for
some
of
the
other
tools
he's
he's
able
to
provide
some
some
context,
but
we're
just
missing
out
on
the
cap
team
to
to
give
more
information.
A
Okay,
do
is
there
anything
else
that
the
team
wishes
to
discuss
anything
that's
popped
up,
wants
to
bring
up
with
the
community
anything
that
they're
working
on
need,
help
with.
E
E
What
are
the
contents
of
the
bundle
and
we
hope
to
get
that
in
somewhere
next
week-
and
I
know
this
is
something
that
has
been
asked
before
so
we're
trying
to
do
an
effort
to
give
you
a
little
bit
more
of
insight
of
what
the
bundle
contains
that
way
you
can
without
having
to
like
pull
the
bundle
and
do
some
wrapping
around
to
find
what
is
happening.
E
A
E
Completely,
as
I
was
saying
like,
I
am
expecting
to
get
this
in
so
like
there's
a
pr
already
like
back
and
forth
with
dimitri
and
we're
talking
a
little
bit
about
more
architecture
than
anything
else,
and
I
I
hope
that
I'll
get
this
merged
next
week
and
eventually
you'll
get
a
release
out
as
well.
With
this
feature,
and
eventually
with
another
feature
that
I've
also
been
working
on,
that's
transport
related
so
get
those
two
in
and
they
could
be.
They
could
be
like
a
very
one
is
a
performance
improvement
in
this
one.
E
Is
the
this
interesting
new
command.
E
E
I
can
talk
about
that
discussion
topic.
It's
going
to
be
pretty
light.
Do
you
mind
just
opening
it
and
scroll
to
all
to
the
bottom
of
that
issue
so
like
there
was,
there
was
an
issue
that
was
created
by
josh
and
some
of
the
complaints
that
we
had
previously
was
that
it
was
hard
to
understand
like
where
an
image
that
was
part
of
a
bundle
came
from
like
what
is
the.
What
is
the
image
right
and
the
objective
here
and
what
what
josh
was
asking
for
was.
E
Can
we
create
a
tag
that
somewhat
resembles
or
have
like
some
information
where
this
this
image
came
from
right
so
like
this?
Is
the
the
thread
and
it's
a
little
bit
of
a
background
image
package
creates
a
tag
for
each
image
that
it
copies
from
one
registry
from
one
repository
to
another,
because
some
of
the
the
registries
require
you.
You
cannot
push
an
image
without
a
tag
or
some
others
when
they
garbage
collect
the
images.
They
look
for
images
that
have
tags
and
if
it
doesn't
have
a
tag,
it
just
garbage
collects
the
image.
E
So
this
could
be
a
little
bit
disruptive
for
people
that
are
using
image
package
right
now,
if
you
scroll
down
to
my
second
to
last
message
there
so
that
that's
the
one
so
currently
when
we
create,
when
I
image
package,
creates
a
tag,
the
tag
is
called
sha
255
dash,
then
the
the
digest
of
the
image
dot
image
package
and
that's
the
name
of
the
tag
like
our
proposal-
is
to
change
that
to
contain,
before
the
shabby
to
contain
the
information
of
the
repository
where
the
image
came
from
okay.
E
So
this
is
this
is
a
proposal
and
we
we
are
bringing
this
here
to
try
to
understand
if
this
could
be
in
some
way
impact
people
that
are
currently
using
image
package
in
some
capacity
that
are
relying
on
this
tag
to
exist
or
the
stack
to
be
on
a
specific
format.
E
If,
if
we
don't
get
like
any
feedback,
saying
that,
oh
my
god,
this
is
gonna
break
because
then
we
are
going
to
go
with
this
feature
where
we're
gonna
change
the
tag
as
it
is
right
now
and
add
this
a
little
bit
more
information,
so
you
can
be
more
human
humanly
readable.
E
So
this
is
more
like
a
call
out
like
if
you
see
this
as
a
problem,
please
look
at
it
and
let
us
know-
and
if
not
we
like-
I
think
alex-
has
already
had
a
first
pr
and
we
will
move
on
with
this
feature
by
the
way.
This
is
good.
The
idea
is
that
this
is
going
to
be
behind
a
flag
that
apparently
I
propose
like
repository
based
tags
or
whatever,
like
we
haven't
settled
on
the
the
flag
name,
but
this
would
be
underneath
that
flag.
E
E
So
this
is
more
or
less
the
idea,
if
you
have
any
questions
just
come
to
to
the
channel
and
talk
to
us,
if
you
have
any
doubt
if
you
have
any
concern,
just
come
and
talk
to
us
in
in
our
cargo
channel
on
kubernetes
or
just
reply
to
this
issue
and
say
like
oh,
my
god,
this
is
going
to
break
my
my
world
because,
okay,
so
that's
just
a
little
thing.
E
A
Okay,
great
well,
thank
you
for
joining
us
today.
Again,
if
you're
watching
this
from
home,
we
would
love
to.
Have
you
join
us.
Live
you
can
come,
listen
in.
You
can
meet
the
maintainers
other
people
in
the
community
and
bring
anything
that
you
may
need
help
with
or
have
feedback
on
or
any
ideas
you
have
for
the
tools.
We
would
love
to
have
you
and
hear
from
you
so
with
that
and
we
hope
to
see
you
next
week.
Thank
you.