►
From YouTube: Carvel Community Meeting - November 9, 2022
Description
Carvel Community Meeting - November 9, 2022
We meet every 2nd and 4th Wednesday at 8am PT (time and day subject to change over time as we adjust to community requests). We'd love for you to join us live!
This week we went over what to expect with our CNCF onboarding and asking for the community's input regarding some of our experimental tools, an imgpkg feature request, and what the team's been working on. Check out full agenda here: https://hackmd.io/F7g3RT2hR3OcIh-Iznk2hw#November-9-2022-Agenda
A
Hi
everyone
welcome
to
this
week's
edition
of
the
carpool
community
meeting.
Today's
date
is
November,
9th
2022..
As
a
reminder,
we
meet
every
second
and
fourth
Wednesday
and
starting
today
we
are
meeting
at
8
A.M
Pacific
time.
It's
a
good
opportunity
for
you
to
come
and
join
us
live,
listen
in
on
what
the
team
is
working
on,
provide
feedback.
If
you
have
anything,
you
need
help
with
and
getting
started
with,
Carvel
or
just
want
to
listen
in
participation
is
not
required.
A
If
you
are
unable
to
meet
us,
live
in
person,
there's
a
great
way,
there's
other
ways
for
us
to
be
found.
You
can
reach
us
at
the
Carville
Channel
and
the
kubernetes
slack
workspace.
You
can
email
us
and
you
can
find
us
in
GitHub
and
I-
have
announced
more
information
on
this,
because
this
will
be
changing
and
the
TWiT
on
Twitter
at
Carvel
underscore
Dev
at
any
point
you're
interacting
with
us
or
any
members
of
the
community.
We
ask
that
you
please
read
and
abide
by
our
code
of
conduct,
which
is
listed
out
here.
A
A
If
you
would
like
for
us
to
add
that
to
the
adopters
file
here,
but
it's
not
required
the
details
that
that
we
ask
of
you
like
it
just
helps
us
understand
further
about
how
folks
are
using
Carvel
tools
and
helps
us
in
the
developmental
process.
So
you
know,
if
you
have
any
questions
on
that,
please
let
us
know.
A
Everyone
that
is
joining
us
today,
just
a
reminder
to
add
your
name
to
the
attendees
list
here.
Just
helps
us
keep
track
of
those
that
are
joining
us
today.
It's
not
required.
So,
if
you're
not
comfortable
with
it,
please
don't
feel
like
you
have
to,
but
just
a
nice
way
to
to
see
who
else
from
the
community
is
here
with
us.
A
A
B
A
A
A
A
All
right
moving
on
to
content
stuff.
So
since
last
meeting
the
getupscon
North
America
presentation
was
posted
on
YouTube.
So
this
was
a
co-located
event
with
kubecon
and
Dimitri
Conan,
who
is
sort
of
the
founder
of
all
of
the
cardboard
stuff
and
as
our
project
lead,
he
and
Rupa
did
this
talk
experimenting
with
q
and
Carvel
to
get
up
enable
get
Ops
for
your
applications,
so
be
sure
to
check
that
out.
We're
still
waiting
on
a
couple
of
the
other
talks
looks
like
kubecon.
The
main
conference
still
hasn't
posted
their
videos.
A
B
A
Awesome
and
along
with
that
Dimitri,
is
writing
up
a
blog
post
about
q
and
cap
controller
in
particular.
So
he
estimates
it's
going
to
be
posted
sometime
this
week,
so
keep
an
eye
out
for
that
whenever
I
share
it
on
all
the
channels
and
then
next
week
we
have
a
highly
anticipated
tutorial
of
ytt
part
two
by
varsha,
so
we
all
have
a
YouTube
video
up
and
accompanying
blog
post,
just
like
we
did
for
part
one
so
be
on
the
lookout
for
that,
and
then
we'll
go
over
that
in
more
detail.
A
Now,
as
far
as
sharing
content
and
your
knowledge
of
Carvel,
it's
not
just
limited
to
the
maintainers
that
work
on
Carvel.
We
want
to
know
more
from
those
outside
of
us
and
how
they're,
using
it
and
sharing
their
knowledge.
We
find
that's
highly
valuable
because
they're,
the
ones
that
are
using
it
on
a
daily
basis,
and
you
know
all
the
tips
and
tricks
and
things
like
that
that
they
have
in
terms
of
their
use
cases
with
Carvel.
It's
really
interesting
to
us
and
others.
A
So
if
you
have
anything
that
that
you
would
like
to
share,
you
can
come
in
here
and
add
your
name
and
the
topic
you
want
to
cover
and
how
you're
going
to
be
delivering
the
topic.
You
know
it
could
be
anything
you're
comfortable
with
it's
a
video
or
blog,
or
you
know,
if
you're
going
to
be
presenting
somewhere.
A
D
Yeah
I
just
realized
that
so
don't
do
like
the
major
features
other
than
some
like
tweaks
here,
and
there
are
mainly
that
some
of
our
users
saw
the
need
that
they
want
to
fetch
bundles
that
they've
pushed
so
that
easily,
so
that
they
can
sign
it
and
do
other
like
secure
practice
and
stuff
with
it.
And
so
that's
something
we
have
made
a
change
for,
but
users
are
able
to
fetch
the
bundle
that's
created
automatic
created
by
doing
acdr
really
easily
and
other
than
that.
D
We
now
generate
open
API
schemas
when
someone's
wrapping
a
hand
shot
into
a
Carvel
package.
So
it's
the
thing
is
when
it
comes
to
health.
Folks
have
a
lot
of
different
conventions
that
they
use,
but
we
try
to
sort
of
generate
the
best
schema
we
possibly
can
so
that
the
user
gets
some
information
about
what
the
values
goes
into
the
hand
head
chart
rate
and
I'm.
Sorry
I
haven't
gone
through
this,
so
yeah
I
think
I
think
those
are
the
significant
ones.
D
D
F
D
A
Okay,
before
I
move
on
I
saw
Pete
hadn't
gotten
one
of
these
shirts
and
I
I,
just
I'm,
so
ashamed
of
myself
that
I
didn't
send
you
this
form
before
I
know
that
you
wrote
a
blog
post,
so
this
is
so
I
sent
the
form
over
and
I
know
Thomas
as
well
has
been
very
active,
so
please
feel
free
to
fill
out
that
form
and
get
all
the
fun
things
sent
to
you.
We
definitely
appreciate
everything
you've
done
for
us
and
the
community
at
large
for
sure.
F
G
F
We
didn't
talk
about
this
yeah
I,
don't
know
I,
don't
remember,
but
yeah,
if
we're
like
we're
here
today
to
to
talk
about
Peach
right.
So
thank
you.
Pete
there's
one
feature
here
from
you
and
so
basically
like
this,
this
release.
It's
been
long
awaited.
People
have
been
crying
ahead
of
joy
for
having
like
this
new
feature
here.
That
is,
you
don't
no
longer
need
image
package
in
your
system
to
use
windier
like
everybody
rejoicing
about
that.
So
that's
that's
cool!
F
That's
what
happened
on
no
32
and
the
other
thing
that
that
was
happening
was
that,
and
this
is
what
Pete
gave
us.
It
is
like
every
time
that
vindir
was
pulling
the
images
down.
He
could
rewrite
the
log
file,
even
if
nothing
changed,
and
that
was
causing
problems
to
people
that
were
using
make
files
and
so
on.
So
thank
you
Pete
for
for
the
fix
there,
and
then
there
were
two
bugs
there
where
we
had
like
the
first
contribution
from
to
Nursery.
F
Thank
you
for
that
that,
basically,
the
two
things
that
were
there
one
was
that
when
you
were
trying
to
download
a
an
HTTP
from
an
HTTP
server
from
somewhere
and
you
disable
unpacking,
there
was
like
a
bug
internally.
That
was
not
a
if
you
had
like
a
second
like
something
some
another
folder
that
you
wanted
to
download
after
that
one.
F
It
would
just
fail,
because
we
were
deleting
the
the
main
folder
that
that
we
used
as
a
caching,
and
then
there
was
like
some
more
helpful,
some
more
helpful
error
messaging.
No,
when
you're
trying
to
download
a
file
from
a
GitHub
release,
then
the
file
does
not
exist
previously.
It
was
just
getting
like
a
stranger.
So
that's
that's!
Basically
it
for
o32
yeah
and
thank
you
everybody
for
their
contributions.
A
A
E
Yeah,
so
the
ones
that
are
titled
October
2022
are
actually
done.
The
first
one.
Definitely
we
have
reached
that
pay
control
per
Milestone
where
we
wanted
to
get
most
of
the
stuff
out
and
ready
for
use
by
everybody,
including
yeah,
for
everybody,
and
then
we
have
also
the
second
one
where
tab
deploy
will
trigger
a
new
version
asset
based
on
the
predetermined
wheel.
That
is
out.
So
all
these
things
marked
as
October
22,
are
out.
B
There's
a
tiny
bit
of
color
around
the
ytt
stuff,
the
the
the
getting
started
series
that
varsha's
been
working
on
as
a
piece
of
some
of
the
guides
and
examples
we
kind
of
pull
out
the
little
chunk
of
that
the
scope
of
that
initiative
is
is
meant
to
be
bigger
than
that,
but
we're
kind
of
scraping
the
top
we
are
like.
We
know
the
we
need
this
piece
and
and
and
the
Stars
lined
up
for
just
that
piece.
B
E
E
F
Yeah
I
can
take
that
so
yeah,
so
we
delivered
the
the
next
step
of
the
describe
commands.
So
one
of
the
one
of
the
major
issues
that
people
are
having
one
of
the
not
the
major
issue
that
we
were
having,
but
one
of
the
major
issues
that
we
were
having
with
with
the
Scribe
was
that
if,
for
example,
it
failed
to
to
get
one
particular
image,
it
would
fail
so
and
it
would
not
print
anything.
F
So
this
was
causing
problems,
especially
when
you
were
talking
to
Registries
like
Arbor
that
sometimes,
if
things
do
not
exist
in
the
registry,
instead
of
giving
back
a
404,
they
give
you
a
poor
one
right.
So
now
the
image
pack
is
a
little
bit
more
resilient
and
it
will
get
you
all
the
information
that
it
can
and
the
information
that
it
can.
It
also
provides
information
so.
F
F
So
we
had
to
do
a
bunch
of
triaging
or
like
go
of
all
the
libraries
that
we're
using,
and
we
did
realize
that
they
were
false
positives,
where
the
version
that
we're
using
of
the
library
yes
contained
the
cve
but
cap
controller
in
itself
did
not
use
the
part,
the
package
or
the
part
of
the
library
that
had
the
CD
itself.
So,
in
order
to
be
like
good,
open
source
citizens,
what
we've
did
what
we
did.
We
just
bumped
all
these
libraries,
even
though
they
didn't
affect
directly
image
back
sorry,
a
cap
controller.
F
G
F
So
that's
like
the
one
of
the
things
that
we've
been
doing
playing
a
lot
around
Webby
series,
the
other
thing
that
that
has
landed
since
all
32
came
out
from
vindir.
We
were
able
to
pick
the
functionality
for
caching
and
now
cap
controller
on
the
next
version
will
be
able
to
have
like
interact
less
with
the
registry
which
make
it
is
going
to
make
it
more
resilient.
F
So
the
caveat
here
is
that
this
caching,
this
functionality
will
only
work
if
you
have
a
bundle
and
if
you
are
referencing
the
bundle
with
a
shot
right
like
if
you're
doing,
if
you're
referencing
a
bundle
with
a
shot
cap
controller
will
be
able
to
Cache
it
and
save
that
information,
and
it
will
not
need
to
go
to
the
registry
again
to
to
get
information
again.
So
this
is
going
to
come
out
in
the
next
on
the
next
version
of
cap
control.
I,
don't
know
Neil.
D
I'll
probably
talk
about
it,
so
for
Gaff,
we've
been
sort
of
playing
around
with
a
few
ideas
to
make
it
more
performant
and
that's
what
we
mentioned
in
the
roadmap
as
well
and
so
to
be
more
specific.
What
we
have
been
playing
around
with
this
week
is
how
we
can
tweak
parameters
we
pass
to
cap
for
different
packaging
scenarios.
For
example,
we
found
that
some
weight
intervals
are
better
when
let's
say
you're
trying
to
reconcile
five
packages
and
another
works
better
when
you
reconcile
I,
said
10
or
15
packages
right.
D
Yeah,
oh
that's
me
again,
oh
so
so
we
have
mainly
been
working
on
this
week
to
figure
out
how
we
let
users
use
the
dev
command
without
requiring
to
create
service
accounts
on
the
cluster.
So
today
the
behavior
that
is
always
accounted
is
required
is
in
place
because
because
that's
how
the
cap
controller
reconciler
works
and
we
basically
use
the
same
logic
to
reconcile
packages
locally
packages
are
upstairs
locally.
So
what
we
want
to
change
up
is
we?
D
A
lot
of
users
have
said
I,
don't
want
to
create
service
account
right
off
the
bat
and
we
want
to
let
them
have
a
flag
where
they
can
say.
Okay,
just
use
my
coupons,
they
can
start
to
deploy
stuff.
So
that's
what
we've
been
working
on
and
the
other
two
items
are
like
something:
we've
been
doing,
some
figure
out,
figuring
figuring
out
around
a
common
request,
is
while
using
the
def
command.
D
I
want
to
be
able
to
pass
my
values
easily,
so
we're
sort
of
figuring
out
how
we
can
allow
the
users
of
Supply
values
and
map
it
to
package
installs,
because,
while
running
the
dev
command,
they
might
have
multiple
package.
Installs
or
apps,
yes,
don't
need
values,
multiple
packages
and
stuff
right.
So
that's
something
we're
figuring
out,
and
the
third
point
is
more
about
allowing
users
to
sort
of
arrange
whatever
yaml
and
boilerplate.
D
They
have
a
packet
generation
in
the
repos
more
effectively
like
maybe
keep
everything
in
a
single
directory
and
today,
if
a
user
supplying,
let's
say
their
own
images,
because
they're
already
born
to
use
that
log
file,
they
have
to
have
that
image
package
folder
in
the
root
directory,
which
is
not
desirable
right,
so
folks
have
been
working
around
it
by
doing
some
like
vendor
magic
before
running
K
control
packet
release.
But
we
want
to
sort
of
make
that
experience
better,
so
yeah.
D
E
B
You
make
the
call
to
to
run
that
you,
you
can't
get
control
back
of
that
of
that
go
routine
like
if
there's
something
that
happens
in
there,
that's
running
too
long,
there's
not
much!
You
can
do
if
you're
running
it
in
process,
so
so
wanting
to
be
able
to
like
pass
into
context
and
be
able
to
cancel
on
that
context.
It's
totally
reasonable.
B
A
The
first
item
on
here
was
actually
something
we
were
hoping
to
discuss
with
the
hashicorp
team,
but
unfortunately,
I
just
got
a
notice
that
they
are
unable
to
make
it,
but
they
do
want
to
set
up
a
meeting
with
some
of
the
maintainers
to
discuss
further
about
this
issue.
So,
just
to
give
you
some
context,
they
were
talking
about.
A
provider
doesn't
work
on
Windows,
and
so
we
just
wanted
to
get
some
more
details
here,
for
this
particular
item
and
John
I
know
is,
is
actively
looking
into
it.
B
B
A
Okay,
so
the
next
item
is
something
that
we
really
want
to
get
more
feedback
from
the
community
at
large
on
and
just
similar
to
I'll
use,
I.
Think
Joelle
had
this
analogy
yesterday,
when
you're
moving
and
you're
packing
up
stuff
and
you're
moving
into
a
new
house,
you
start
looking
through
stuff
you're
like
why
do
I
need
this?
A
Do
I
even
use
it,
and
you
know
it's
like
a
good
way
to
shed
stuff
that
you
no
longer
need
and
start
fresh
on
using
the
stuff
that
you
still
need
and
use
so
as
we're
moving
all
of
our
Carval
stuff
to
the
vendor.
Neutral
GitHub
org
we're
looking
through
some
of
the
tools
and
different
repos
that
are
attached
to
Carvel,
but
we
don't
necessarily
pay
attention
to
or
we're
not
sure
if
anyone
even
uses
them
things
like
that,
so
we're
curious
to
know
from
the
community
at
large.
A
B
So
this
is
about
being
able
to
basically
kind
of
create
a
workspace
type
feel
with
interacting
with
a
cluster
and
being
able
to
do
things
like
easily
yeah
I
think
it
was
the
first
one
too
Sonic
nearly
positive
you're
right
so,
but
so
so
that's
interesting.
That's
an
interesting
bit
in
and
of
itself.
B
F
Yeah,
like
like
it,
looks
like
we're
peeking
on
this
tool,
where
we
are
yes,
we
are
picking
on
this
too,
but
not
only
on
this
two
right,
like
we
want
what
we
wanted
to
like.
We
were
talking
about
this
yesterday
and
the
idea
here
is
that
we
we
want
to
understand,
like
what
are
the
tools
that
the
community
currently
are
using,
that
are
part
of
Carvel,
so
that
we
can
have
a
better
understanding.
F
So
we're
not
sure
if
people
are
using
this
provider
as
well
as
like
kwt,
when
you
know
people
are
using
it
and
it
doesn't
cost
us
anything
to
have
them
there,
but
at
the
same
time,
because
they
are
there
we're
telling
people
that
yes,
this
is
something
that
you
can
use
and,
and
that
will
support
in
some
sense.
That's
true
and
we'll
try
to
do
our
best.
But
these
are
not
like
tools
that
we
like
we
even
use
on
a
regular
basis.
F
So
it's
a
little
bit
hard
to
change
context
to
something
that
hasn't
changed
since
2019.
right.
So
what
we
would
appreciate
from
the
communities
to,
let
us
know
we're
gonna
we're
gonna
delete
kwt
and
we
want
to
know,
can
we?
But
so,
if
you
have
anything
any
tool
or
you're
using
any
library
in
here
that
we've
labeled
as
experimental,
please
reach
out
to
us.
B
H
H
B
B
Those
are
those
are
straightforward,
but
then
there's
things
like
this,
where
they're
integration
or
Bridges
from
The
Suite
into
other
tools,
and
so
that
that's
an
interesting
question
to
explore,
especially
as
a
cncf
project,
where
we're
going
to
want
to
sort
of
long-term,
especially
this
project
are
going
to
want
to
make
it
easy
to
use
these
tools
either
individually
or
on
Moss,
with
other
projects
and
so
there'll,
be
there
might
be
tools
like
that
or
or
adapters
like
that,
that
we
will
build
that.
Like
looks
exactly
like
this,
it's
like!
B
B
Is
that
something
that
we
should
be
providing
so
yeah
I?
Think
part
of
that
is
us
getting
clear
about
what
what
what
what
do
we
want
to
commit
to,
especially
in
the
context
of
cncf,
in
terms
of
the
so
there's
an
inner
circle
of
of
like
commitment
and
like
what
we're
doing
and
then
there's
another
range
that
our
that
I'm
not
saying
we're
doing.
But
but
we
should
consider
like
let's
get
clear
about
how
much
are
we
going
to
try
and
adapt
to
other
tooling?
B
H
Nine
I'm,
a
huge
supporter
of
like
having
an
Argo
CD
ytt
arcade,
build
plug-in.
That's
not,
you
know
just
a
example
from
a
blog
post
that
works
really
well
still
today,
but
like
that
that
was
maintained
by
the
Carvel
team
or
for
flux
or,
for
you
know
the
integration
tools
of
what
we're
seeing
being
utilized
in
the
field
today,
right
terraform
is
one
of
those
the
difficulty
with
the
terraform.
B
H
Exactly
if
we
were
using
the
go
modules
of
if
we
were
rendering
in
the
go
modules
of
the
tools
into
the
terraform
provider
itself
and
the
terraform
provider
was
calling
out
to
just
basically
using
the
go
code
of
cap
of
ytt
of
whatever,
then
it
would
be
much
more
beneficial
because
it
would
actually
be
a
package
of
what
it
was.
Instead
of
shelling
out
to
tools
that
I
have
to
have
on
that
workspace.
For
terraform.
H
I
think
the
one
last
thing
I
would
add
is
that
it
may
be
interesting,
John
and
you
know
to
go
down
the
approach
that
kubernetes
has
added,
where
we
don't
want
things.
Staying
in
Alpha
forever,
kubernetes
had
the
issue
of
Alpha
and
beta
apis
staying
around
for
a
million
years
and
never
changing,
and
they
now
have
like
so
Alpha,
considering
it
like
experimental
I,
think
having
experimental
projects,
make
sense
right
within
carvo,
but
we
should
have
a
policy
of
what
does
it
mean
when
something
is
experimental?
H
Is
there
an
estimated
time
until
something
either
gets
dropped
or
goes
to
GA
and
I?
Think
that
having
that
aligning
with
kubernetes
as
the
lead
project,
basically
in
the
cncf
I
think,
would
be
a
good
pattern,
possibly
to
look
at
for
how
we
look
at
the
future
at
those
adapters
at
these
different
tools
as
well
kwt
or
the
terraform
provider.
B
H
B
B
Part
too,
if
they're,
if
there
are
folks
that
truly
truly
truly
want
it.
This
is
the
beauty
of
Open
Source
like
4K
right.
It's
an
Apache
2
license
knock
yourself
out.
If,
if
it
comes
to
that,
it's
like
we're
not
leaving
somebody
in
a
Lurch
we're
just
saying
right:
okay,
but
being
clear
about
that,
because
nobody
wants
to
Fork
when,
when
like
it's
unclear,
whether
or
not
the
Project's
going
to
commit
to
it.
F
You
talk
about
is
that,
like
in
terms
of
our
functionality,
the
fact
that
you
can
archive
hey
repo
and
the
repo
is
still
available
to
people,
but
it's
archived.
Kinda
kinda
could
be
like
the
solution
to
this
like
when
we
decide
that
like
we
are
not
going
to
be
able
to
maintain,
but
in
the
in
the
future
we
can
also
and
archive
it
I
think
so.
If
we
decide
that
oh,
it
is
to
be
best.
If
we
just
jump
back
to
this
and
do
something
else,
maybe
we
can
archive
it.
F
C
G
G
Anything
something
that's
got
mentioned
earlier
on
too,
is
that
an
archived
project
kind
of
signals
to
the
community
of
you
know
we're
doing
housekeeping.
You
know
if
we're
not
really
interested
in
keeping
this
up
or
if
we
haven't
seen
a
lot
of
traction
on
this,
then
we're
acknowledging
that
and
it's
not
just
leaving
something
dangling
out
there,
which
kind
of
contributes
to
the
the
the
the
emphasis
or
the
impression
of
like
a
well-maintained
tight
set
of
tools.
A
Thank
you
for
those,
the
Insight
from
Pete
and
Scott,
and
that's
very
for
me,
that's
very
helpful
as
we
we
work
to
figure
this
out.
I
I
know
right
now
we
are
planning
on
moving
everything
and
then
we're
not
going
to
make
any
final
decisions
on
until
after
we've
moved
everything
over,
but
I
think
I
think
we're.
This
is
very
helpful
to
get
us
in
a
place
closer
to
where
we
end
up
with
these
tools.
A
E
F
A
B
A
E
A
A
There,
okay,
it's
my
I,
put
it
here,
because
I
think
not
think
I
believe
that
we
should
revive
this
and
I
I
want
to
hear
more
from
the
community
on
this,
because
we
started
seeing
more
chatter
about
it
on
Twitter
it.
It
seems
to
be
a
feature
that
I
think
could
be
very
useful,
but
Joelle
are
you
able
to
give
just
a
few
minutes
like
a
couple
of
minutes
context
overview
about
what
all
this
is
as
I
would
I
would
not
do
it?
Justice.
F
Just
give
power
to
the
people
right,
that's
basically
what
this
is
right,
so
we
don't
want
the
federal
government
to
okay
different
different
thing.
So,
basically,
what
this
is
is
enable
people
to
when
they
are
copying
images
from
one
registry
to
another,
from
one
repository
to
another
innate,
allow
people
to
Define
where
those
images
land.
F
Why
is
that
so
currently
image
package
when
you
copy
images
from
one
registry
to
another,
it
copies
all
the
images
to
the
same
repository
right
and
in
some
sense,
if
we're
talking
about
machines
that
doesn't
really
matter
at
all.
Right
like
where
you
put
the
images,
it
doesn't
really
matter
because
image
package
knows
where
they
are,
so
you
can
pick
them
up
again,
there's
no
problem
there.
F
The
problem
is
humans
humans,
because
in
some
in
sense,
in
some
situations
people
want
to
know
and
want
to
see
the
you
want
to
see
the
images
where
they
are
and,
for
example
like
if
they
have
a
controller
and
that's
a
controller
for
some
sort
of
error
for
application
one
they
want
to
have
an
image
that
is
in
a
repository
called
application.
One
called
control
right
so
with
with
this
proposal
is
trying
to
achieve,
is
to
enable
people
to
Define
where
they
want.
F
The
images
to
be
copied
to
this
has
a
bunch
of
problems
associated
like
permissions
image
package
will
lose
the
the
ability
to
track
where
all
the
images
are
and
so
on,
and
these
are
like
very
in
some
case,
complicated
problems
that
are
addressed
in
this
proposal.
So
this
is
basically
it
and
I.
Think
I
use
more
than
my
thought
in
two
minutes.
I
hope
this
is
like
a
good
first
step
for
people
to
understand
what
this
is
about.
A
H
I
really
really
really
really
really
really
really
really
really
would
love
this
yeah
I
think
I
brought
it
up
a
few
times
a
while
back.
It's
something
that
we
hear
from
our
end:
users
and
customers
on
a
consistent
basis,
because
they
aren't
machines
and
it
usually
comes
from
their
security
team
that
when
they
do
cve
checks
on
things,
they
want
to
actually
know
what
that
CV
is
on.
H
I
know
that
there's
the
tagging
that's
gotten
better
and
like
some
of
the
things
can
move
to
a
tag
and
so
from
there
are
ways
to
kind
of
make
it
better.
But
this
would
just
be
huge
and
would
also
solve
in
another
way
draw
the
issue
that
we
were
dealing
with
with
image
package
framework,
because
you
could
use
image
package
to
relocate
everything
but
yeah.
A
A
F
A
Oh
yes,
I'm
just
saying
I'm
hoping
we
will
get
the
wheels
moving
again
on
this
okay,
and
with
that
we
yeah.
That's
it.
Thank
you
for
everyone
staying
a
little
bit
past
time
and
for
all
of
your
comments
and
questions
and
great
conversation.
Today
it
was
good
seeing
all
of
y'all
it's
been
about
a
while
and
it
was.