►
From YouTube: Carvel Community Meeting - March 22, 2021
Description
Carvel Community Meeting - March 22, 2021
Discussion topics include vendir v0.17.0 release, kapp-controller v0.17.0 release, and other items. Full details here: https://hackmd.io/F7g3RT2hR3OcIh-Iznk2hw
A
All
right
welcome
everyone
to
this
week's
edition
of
cargo
community
meeting
today
is
march
22nd
2021,
just
a
reminder
that
this
meeting
is
being
recorded
and
adding
to
our
cargill
youtube
playlist.
A
If
there's
anything
that
we
don't
get
to
in
this
agenda,
we
do
have
carnival
office
hours
that
happen
every
second
and
fourth
thursday
of
the
month,
starting
at
11
30
a.m.
Pacific
time
we
do
have
one
this
this
week,
which
is
march
25th.
A
So
please
join
us
for
that
as
well
for
anything
that
we
might
need
to
move
from
this
meeting
to
there
or,
if
there's
anything
that
you
need
help
with
regarding
karmal,
if
you're
interested
in
becoming
a
contributor
or
anything
like
that,
that's
just
some
more
in-depth
time
that
the
maintainers
have
available
to
you
to
really
get
into
the
project
tool
suite,
and
with
that,
I
will
hit
it
off
to
aaron
to
go
over
the
announcements
and
other
status
updates,
as
well
as
the
black
backlog
of
different
things.
B
Here
we
go
so
a
few
announcements.
We
got
a
couple
releases
last
week.
First,
one
we'll
mention
is
vendor,
so
adding
authentication
arguments
to
the
home
repo
ad
command,
and
then
we
also
cut
a
release
for
cap
controller,
consuming
that
vendor
change,
as
well
as
a
recent
cap
bump
that
we
talked
about
last
week
as
well
as
maybe
the
most
noteworthy
item
is
this
issue
that
was
delivered
immediately.
Reconciling
apps
when
associated
secrets
or
config
maps
change.
C
Only
other
thing
is
that
there
was
the
addition
of
adding
an
image
package
bundle
as
a
fetch
source,
and
this
has
actually
been
around
for
a
bit,
but
I
I
think
we
just
had
some
time
between
when
our
last
release
was
cut
and
when
this
was
added.
So
that's
the
only
other
thing
in
there.
D
I've
been
taking
a
look
at
community
issues
this
morning
and
one
came
in
about
vendor
version
17,
which
no
longer
has
the
versions
package
which
k
build
now
depends
on.
Is
there
any
consideration
or
plan
for
that,
or
is
that
something
that
we'll
just
have
to
address.
E
E
Awesome,
oh
yeah,
okay,
so
this
was
done
because
we
had
to
generate
some
like
kate's
specific
code
for
that
using
the
code
generator.
So
it
should
just
be
updated.
It's
now
in
like
a
v1
alpha
one
package
instead,
so.
B
Cool
thanks
for
the
live
troubleshooting,
it's
one
other
thing
to
mention
was
we
also
cut
a
new
alpha
of
cap
controller
last
week
as
well,
including
some
of
the
changes
that
we
just
mentioned
in
zero
and
likely
some
kind
of
stability
experience
enhancements
as
well.
B
So
on
to
oh,
I
guess
last
announcement
as
we
mentioned
last
week,
but
we
are
hiring
a
staff
engineer,
so
please
check
it
out.
If
you
are
interested
status
updates,
we
have
a
number
of
things
in
flight
ytt
schemas.
It's
in
progress
currently
folks
are
working
on
the
type
checking
private
libraries
anything
else.
These
people
want
to
add
there.
F
Just
while
we're
talking
about
ytt,
there
are
also
a
couple
of
nice
like
ux
improvements
that
we're
looking
at
excited
about
releasing
one
was
detecting
when
your
yaml
is
not
a
template,
just
a
plain
ml
file.
Now
we're
automatically
recognizing
that,
so
you
can
just
pipe
yaml
in
as
part
of
your
set
of
files
that
you're
sending
in
and
it'll
just
work.
Just
for
that
file,
which
is
great,
you
can
turn
off
that
ignore
unknown
comments
flag
so
that
that'll
be
coming
soon.
F
That's
exciting
and
then
another
improvement
that
came
out
of
schemas
is
the
ability
to
overlay.
When
you
have
a
value,
that's
currently
null
to
like
add
in
a
different
value
that
was
like
before
you
would
get
hey,
expecting
a
map,
but
was
nil,
that'll
be
in
in
the
past
soon.
So
we're
excited
about
a
couple
improvements
that
are
just
being
pushed
forward
by
schema
stuff.
It's
great!
B
You
we
also
have
recursive
bundles
track
in
progress.
Any
any
updates.
G
Doing
progress
just
working
on
updating
the
image
lock
files
in
this
bundles
recursively
and
in
parallel
with
this,
is
also
a
ux,
a
ux
improvement,
which
is
ideal
like
we
submitted
up
here
upstream
and
that
got
merged
we're
waiting
for
that
library
to
get
updated
so
that
the
ux
of
image
package
can
change
from
what
we
have
to
date.
Where
to
you
can
see
in
real
time
how
many
bytes
are
being
uploaded
versus
the
total
amount
of
bites
you're
waiting
for
so
you
can
maybe
see
a
progress
bar
or
something
to
that
effect.
B
Very
cool:
let's
see,
we
also
have
some
cap
enhancements
in
progress.
I
believe.
Last
week
we
had
a
like
a
ducks
improvement
story.
I
think
that
was
wrapped
up
yeah
anything
going
to
show
there
yeah.
H
B
Great
cool
and
then
cap
controller
world,
the
package
measure,
api
mvp,
is
still
very
much
in
progress.
I
don't
know
daniel
eli
anything
you
want
to
share
at
a
high
level.
There.
E
We
just
merged
a
change
that
was
mentioned
before
I
think
of
now.
You
can
update
your
values
for
a
package
and
it'll
get
pulled
in
immediately,
but
other
than
that,
I
don't
think
there's
been
any
major
updates.
B
Cool
and
then,
similarly
with
with
cap
controller,
we're
also
weaving
in
some
some
enhancements
between
all
the
api
mvp
work,
so
those
are
ongoing
as
well.
B
If
folks
have
any
triage
help
topics
they
want
to
discuss
today,
please
feel
free
to
add
a
add.
A
note
here
same
with
more
general
discussion
topics
we'll
try
to
keep
an
eye
on
these
lists
and
if
any
topics
show
up
we'll
try
to
cover
some
time
out
at
the
end
of
this
meeting.
B
Let's
see,
we
have
a
story
currently
in
progress,
a
documentation
story
pointed
and
then
we
have
the,
I
guess,
kind
of
one,
one
more
story
which
is
remove
experimental,
the
the
flag
and
then
an
additional
follow-on
story
for
supporting
copying
bundles
referenced
by
other
bundles
and
images.
Lock.
B
Let's
see,
maybe
we
can,
I
don't
know,
discuss
one
story
this
week.
Does
that
sound
fair.
G
B
Okay,
I
don't
know
if
we
don't
think
we'll
get
to
it.
Maybe
we
can.
We
can
just
postpone
until
next
week
then.
B
B
Good
stuff,
this
cluster
fulfilled
resources.
That's
one
that
we
had
already
discussed
as
an
explorer
story.
Let's
take
a
look
at
what
is
it
show
all
issues
not
in
an
epic.
B
E
E
E
Yeah
because
you
get
into
someone's
pool
yeah,
if,
if
it's
added
to
copy,
you
get
into
some
weird
cases,
where
there's
no
longer
guarantees
that
all
the
images
are
coming
along
with
the
bundle
and
then
if
people
don't
know
that
certain
things
were
filtered
beforehand,
you'll
get
like
weird
failures
and
stuff.
So
only
for.
E
E
H
G
B
Okay,
so
it
sounds
like
maybe
whoever
picks
up
this
story
might
have
some
discovery
work
to
to
do.
I
mean
there
certainly
is
a
proposal
as
to
a
way
that
we
could
take
this.
But
at
this
point
I
don't
think
we
I
don't
know
have
converged
on
a
solution
yet.
B
Okay
sounds
good,
so
maybe
what
we
need
to
do
is
pull
this
from
our
prioritized
backlog
and
do
some
discovery.
Work
first.
Does
that
make
sense.
F
F
F
F
F
F
F
F
And
then
I
asked
a
terrific
question
around:
is
there
sort
of
a
general
way
that
we
want
to
refer
to
bundles.
F
Because
this
is
being
recorded,
I
have
to
say,
like
that's,
tongue-in-cheek,
the
greatness
of
my
question
anyway,
but
then
that,
like
the
expected
outcome,
would
be
either
we've
come
up
against
some
kind
of
we
discovered
something
that
sort
of
prevents
this
for
some
crazy
reason.
Maybe
maybe
there
is
or
we've
got.
F
B
Okay,
so
I
think
we're
we're
pretty
good
in
terms
of
like
runway.
Let's
see
any
topics
added.
G
B
F
B
I
drafted
a
pr
that
describes
how
our
backlog
works,
in
particular
like
what
the
name
of
the
columns
are
descriptions,
any
labels
we
use
and
how
they
progress.
Like
I
mentioned,
this
is
still
under
construction,
it's
in
draft
state,
but
but
please,
please,
do
give
any
early
feedback.
If
you
have
it.
E
Okay,
so
where's
the
accepting
unannotated
yaml
is
data
values
proposal
at.
F
Yeah
good
good
question:
eli
we
we
have,
it
looks
pretty
good.
We
have
an
approach,
so
we
believe
that
at
a
minimum
we'll
want
to
support
an
additional
yeah
thanks,
aaron
yeah.
So
this
this
one.
Let
me
contextualize
it
real
quick.
So
this
this
proposal
is
about
there's
a
there's,
a
need
for
many
different
places,
and
this
is
sort
of
actually
a
long-standing
request.
Can
I
please
provide
to
ytt?
F
F
Sometimes
it's
saying
well,
you'll
omit
it
from
the
output
when
by
default
normally
would
be
included
or
usually
you
think
this
is
a
template
once
you
treat
this
as
a
file
that
could
be
loaded
by
a
template
and
used
as
data
and
then
this
new
one
we're
going
to
add
is
usually
you
might
think.
This
is
just
plain
yaml
and
you'll
process
it
that
way,
but
actually
we
want
you
to
treat
it
as
a
data
values
file.
F
F
F
If
you're
used
to
like
the
unix
file
system,
you
can
load
up
and
attach
different
drives
to
make
it
look
like
it's
one
single
file
system,
the
problem
with
the
the
challenge
that
comes
up
with
that
is,
you
could
actually
have
two
files
that
have
the
exact
same
path
and
it's
possible
that
you
may
want
to
treat
one
file
one
way
and
another
file
another
way,
and
today
there
isn't
a
way
of
doing
that.
F
F
So
there's
an
issue
that
that
we
created
around
that
to
sort
of
like
think
it
was
like
a
mini
mini
proposal.
If
you
will
just
saying
hey
what
what,
if
we
accepted
operating
system
file
paths
optionally
for
that
path,
value
of
a
file
mark.
F
If
you
did
that,
then
you'd
be
able
to
uniquely
identify
a
file
because
you're
back
in
the
operating
system,
land
that
place
where
and
you
would
be
able
to
like
point
uniquely
to
a
file
so
that'll
be
a
nice
downshift
option.
If,
if
you
run
into
a
collision,
you
can
name
that
otherwise
it's
fully
backward
compatible.
F
We
would
continue
to
support
relative
paths
so
that
that
issue
just
needs
a
little
bit
of
review
and
then
turn
into
sorry
to
get
implement
that
one
block
the
the
proposal
and
and
then
then
we
can
proceed
with
that
primary
implementation.
F
Was
good
cool
and
then
there's
another
half
to
the
proposal
or
or
a
second
potential
approach
which
would
be
to
introduce
yet
another
flag,
but
it'd
be
specialized.
It
would
be
dash
dash
data
dash
values
file
and
what
this
flag
would
do
is
include
a
a
specific
file
that
you
name
as
as
its
argument,
and
it
would
give
it
that
same
treatment
as
if
it
would
file
market
as
a
data
values,
file
and
the
reason
for
there's.
There's
two
reasons
for
that.
One
is
that.
F
Then
my
data
values
file
is
probably
not
inside
the
library
in
the
first
place.
So
it's
it's
not
unreasonable
to
think
that
that
file
wouldn't
have
been
included
in
the
config
in
the
first
place.
So
that's
kind
of
nice.
It
reads
nicely
the
command
line,
sort
of
says
what
it
does:
it's
sort
of
self-documenting,
it's
pretty
cool
and
then
the
the
other
case
is
in
providing
data
values
that
are
pure,
that
are
plain
yeml,
no
annotations
that
contain
sensitive
data.
F
Maybe
you
maybe
are
including
a
decryption
key
or
secrets
bodies,
or
something
like
that
or
something
assert
or
or
sorry,
private
key.
F
For
some
reason
you
want
to
include
that,
and
so
you
don't
want
it
written
to
disk
you
you'd
rather
use.
What's
called
process
substitution.
That's
for
that!
You
do
that
like
redirect
and
then
there's
a
parenthesis
and
whatever
is
inside.
There
actually
gets
its
own
file
descriptor
like
it's
piped
in
as
if
it
were
like
a
file,
and
you
can
even
give
a
name
for
that
thing,
so
sometimes
to
be
useful,
just
to
be
able
to
not
have
to
give
it
a
name
but
be
able
to
do
that
process.
Substitution.
F
So
that's
that's
another!
It's
sort
of
a
nicety,
it's
it's!
Definitely.
The
second
option
is
a
convenience
feature,
so
I
think
we're
going
to
split
the
first
part
in
the
second
part
and
make
sure
that
we
at
least
get
that
file
mark
approach,
completed
and
then
consider
the
you
know
the
added
complexity
and
maintenance
that
it
might
be
to
include
this
convenience
feature.
It
would
be
a
little
bit
more
judicious
about
that.
E
B
Question
cool
good
stuff,
I
think
maybe
just
like
one
other
thing
to
note
with
the
the
image
package
proposal
here.
Is
that
joao,
I
believe,
had
oh,
oh,
what
did
I
do.
B
F
All
right
I'll
I'll
do
one
real,
quick,
not
to
expand
the
work
to
fill
the
time
but
just
be
on
the
lookout.
There's
a
another
proposal
that
I'm
hoping
we'll
get
resolved
pretty
quickly
going
to
put
in
today
around
how
we
manage
documentation
so
I'll
make
some
noise
on
on
the
carville
channel
just
be
just
be
on
the
lookout
for
that
we're
really
hoping
to
there's
a
couple
parts
that
are
a
little
bit
bumpy
right.
Now,
it's
not
a
huge
deal,
but
it'd
be
nice
to
get
that
resolved
and
going.
A
Okay,
all
right
well
thanks
everyone
for
joining
today,
and
this
will
be
uploaded
to
our
youtube
playlist
later
today,
so
be
on
the
lookout
for
that.
If
you
weren't
able
to
attend
today's
meeting
just
a
reminder,
we
do
have
the
carnival
office
hours
this
week
on
march.
25Th
looks
like
the
bulk
of
that
will
be
available
to
use
for
anything.
A
You
might
need
help
with
from
the
maintainers,
whether
that's
learning,
how
to
contribute
or
if
there's
something
that
you're
stuck
on
or
are
interested
in
a
particular
part
of
the
tool
suite
that's
a
great
opportunity
for
you
to
to
come
and
attend
those
it's
going
to
be
at
11,
30
a.m,
pacific
time,
2,
30
p.m.
Eastern
time,
on
march,
25th
of
this
week
and
again
we
do
meet
every
monday
for
our
community
meetings.
At
that
same
time,
11
30
a.m.
Pacific
time,
2
30
am
2,
30
p.m.