►
From YouTube: Carvel Community Meeting - July 29, 2021
Description
Carvel Community Meeting - July 29, 2021
We meet every Thursday at 10:30am PT; we'd love for you to join us live!
Full details on this week's meeting here: https://hackmd.io/F7g3RT2hR3OcIh-Iznk2hw?both#July-29-2021-Agenda
A
Hi
everyone
welcome
to
this
week's
edition
of
the
carnival
community
meeting.
If
you
are
watching
this
recording
from
home
just
a
reminder
that
we
are
now
meeting
every
thursday
at
10
30
a.m.
Pacific
time-
and
we
encourage
you
to
join
these
live
it's
just
an
opportunity
for
you
to
come
and
meet
the
team.
A
A
We
ask
that
you
read
and
abide
by
our
code
of
conduct
when
you
attend
these
meetings
and
also
input
your
name
and
any
organization
that
you
represent
when
you
attend
these
meetings
as
a
way
for
us
to
keep
track
of.
You
know
who,
from
the
community
outside
of
vmware,
is
attending,
and
we
can
keep
those
lines
of
communication
open.
B
Yeah
sure
so,
zero
fifteen
zero.
When
you
pull
when
you
run
the
pull
command
and
you
give
it
an
image
index,
it's
gonna
error
out,
saying
you
can't
do
that,
but
you
can
give
it
the
exact
shower
of
an
image,
that's
being
referenced
by
the
image
index
and
then
there's
a
few
bug
fixes
around
copying.
Now
you
can
copy
an
image
index
completely
before
you.
B
It
wouldn't
copy
an
image
index
completely,
would
just
copy
a
single
image
referenced
in
the
image
index
and
also
when
you
pass
in
the
registry,
insecure
flag
and
you're
running
against
an
insecure
registry,
it
actually
will
work.
It
won't
error
out,
saying
I'm
you
know
unable
to
connect
to
this
registry
essentially,
and
that's
basically,
it.
C
Our
way
of
basically
supporting
overlays
as
part
of
packages
is
to
specify
annotations
on
the
package
crs
themselves,
but
due
to
the
original
implementation,
there
were
issues
for
annotations
being
part
of
the
crs
themselves.
That
was
causing
error
messages
that
can
be
sort
of
pointed
out
in
the
pr
itself.
C
A
A
C
Sure
so
what
we
that
it's
technically
live,
that
catacota
tutorial
and
the
boss,
and
I
and
did
a
bunch
of
work
yesterday
to
so.
We
have
one
kind
of
branch
sitting
for
our
website
that
has
the
blog
post.
It
has
a
little
announcement
banner.
It
has
links
to
the
katakota
tutorial
and
it
also
has
sort
of
the
katakota
tutorial
content
as
a
as
a
one-pager,
and
we
just
went
over
the
blog
post
again
with
dimitri
and
so
we're.
C
A
A
A
C
So
it's
it's
a
it's
an
interactive
tutorial.
It
starts
with
basically
a
katakota
stock
kubernetes
1.18
image.
It
gives
you
some
basic,
like
here's.
The
kind
of
curl
commands
to
install
the
necessary
carvel
tools
and
bootstrap
your
way
into
using
cap
controller,
and
then
here's
a
demo
of
authoring
a
package
and
pushing
it
to
a
repository
and
then
pretending
that
you're
also
the
consumer
of
your
own
package
and
installing
it
back
into
your
kubernetes
cluster.
A
D
A
A
D
D
I
guess
a
couple
of
weeks,
just
I
guess
just
a
general
heads
up
many
folks
will
be
out
next
week.
So
any
responses
in
github
or
slack
may
be
delayed
a
bit,
but
I
know
some
of
us
at
least
will
be
checking
in
throughout
the
week
to
to
try
and
nudge
things
forward,
but
yeah
yeah,
this
private
registry
authentication,
work
likely
gets
started
in
a
couple
weeks
and
we
need
to
figure
out
firmer
kind
of
timelines,
but
I
would
probably
currently
estimate
it
to
be
around.
A
D
D
You
know,
folks,
taking
time
off
and
us
trying
to
just
like
generally
clean
up
things
that
are
in
flight,
so
trying
trying
to
land
more
items
versus
starting
more
things,
but
yeah
worked
with
carrie
on
this.
Carry
will
be
leading
this
track
and
still
just
kind
of
like
working
through
scoping
and
polishing
the
stories,
but
planning
to
start
this
in
august
as
well.
C
I
guess
you
know
there
was
the
getting
the
version
of
cap
controller,
making
that
easier
to
surface
that.
I
think,
there's
a
solid
draft
on
that
and
it
just
it
turns
out.
We
actually
have
two
different
release:
distribution
processes
and
we're
still
figuring
out
how
to
what's
the
right
way
to
slide
that
information
in
so
that
it's
in
both
release
processes,
but
ideally
not
in
a
development
build
so
that
development
builds
look
like
development
builds
and
don't
get
tagged
as
releases.
E
Soon-Ish,
I've
also
been
working
on
a
k-build
story
this
week
still
in
progress,
but
what
that
involves
is
when
you're,
using
cable
to
resolve
images
and
storing
that
resolved
image.
Mapping
from
like
an
image
digest
to
a
or
an
image
tag
to
an
image
digest
when
you
store
that
in
a
lock
file,
just
persisting
the
metadata
around
what
the
image
tag
was
so
that,
if
you
use
k
build
with
other
tools
like
cap,
you
can
actually
get
that
annotation
into
your
kubernetes
cluster
to
see
what
the
digest
image
that's
deployed
in
your
cluster.
E
C
Actually,
I
would
call
that
one
more
quick
win
in
cap
controller.
We
did
slide
in
the
stretcher,
testify
testing
library,
so
I
think
that
that
does
honestly
lower
the
bar
slightly.
Anyone
who
was
would
be
looking
to
you
know
enter
a
cap
controller.
The
exciting
field
of
cap
controller
development
could
now
do
so
with
familiar
assertion
in
their
unit
test.
A
A
A
F
F
C
Yeah
super
helpful
and
I
I
appreciate
the
tour-
and
I
I
I
guess
I'll
highlight
you
know
I
think
in
particular.
What
I
saw
is
in
nick's
use
case
was
a
couple
of
places
where
he's
like.
Well,
we
you
know
so
if
you,
for
instance,
follow
that
a
tutorial
on
katakota
you're,
just
gonna
pipe
ytt
to
k,
build
to
cap
and
it's
all
gonna
work
the
first
time
and
what
I
saw
nick
doing
was
like
oh
well.
C
First,
I
run
ytt,
you
know
alone,
so
that
I
can
debug
and
and
then
I
I
have
these
other
steps
and
actually
you
know
up
the
some
of
the
custom
resources
or
the
the
yamls
to
define
the
crs.
That's
not
always
trivial.
So
actually
some
of
that
is
even
scripted.
So
I
I
thought
that
was
really
cool
to
see
everything
in
in
motion.
Thank.
F
F
F
So
yeah,
okay,
so
on
to
the
the
second
discussion
topic
so
yeah
I
did
I
did
cruise
through.
I
didn't.
I
didn't
go
through
all
the
tool
suites
because
I
I
figured
I
didn't
want
to
you
know,
bombard
myself
with
too
much,
but
I
just
like
looked
at
cap
and
cap
controller
and
image
package-
and
I
don't
know
I
just
thought-
I'd-
find
or
see
what
the
good
first
issues
were
and
there's
there's
not
a
lot.
F
F
You
know
or
update
some
documentation
and
image
package.
So
I
don't
know
if
I
don't
think
there's
been
any
recent
activity
on
like
the
one
from
cap
controller.
That's
it's
pretty
old,
probably
low
priority
perfect
place
for
someone
that
doesn't
know
anything
to
try
something
out.
I
suppose
you
know
so
I
was
thinking
about
just
you
know,
picking
up
one
of
those
and
dropping
a
pr
at
some.
F
F
To
toss
out
is
another
item
of
discussion.
I
I
had.
I
thought
I
had
found
a
bug
in
cap
controller
this
week,
and
and
so
I
put
it
into
the
the
into
the
slack
channel
and
it
turns
out
it
was
not
a
bug
in
cap
controller,
but
it
was
more
so
I
guess
kind
of
a
bug
in
contour
because
we
were
installing
it
was
a
problem.
F
F
It
would
like
start
up,
run
disappear
and
cap
never
saw
that
it
was,
you
know,
actually
completing
successfully,
so
it
flagged
the
you
know
the
the
installation
sort
of
is
you
know
you
know
failing,
and
you
know
I
it
was
actually,
I
think,
pretty
good,
because
it
was
like
a
combination
of
carvel
and
my
team
and
the
contour
team.
You
know
all
kind
of
working
on
it.
You
know
and
figured
out.
F
You
know,
honestly,
I
forget
what
the
solution
was
off
the
top
of
my
head,
but
had
something
to
do
with.
Basically,
you
know
in
a
package
deploy
of
contour.
It's
like,
don't
don't
make
it.
You
know,
look
for
this
job,
so
you
know
it.
So
I
think
I
think
it
resolves
the
problem
and
yeah.
It
was
kind
of
cool.
Just
to
see
all
three
teams
come
together
and
you
know
fix
something
like
that.
A
B
Was
just
going
to
say,
look
yeah
on
to
nicolas
on
the
previous
topic,
when
you
were
looking
for
issues
for
image
package,
a
good
first
issue
you
mentioned
documentation.
I
think
that's
a
good
first
one
as
well,
but
I
just
wanted
to
say
if
you
wanted
to
also
pair
or
work
together
on
finding
a
good
first
issue
discussing
it
and
then
like.
I
can
give
you
some
pointers
as
well
in
terms
of
how
we
can
maybe
work
on
it.
Like
that's,
that's
an
option
as
well.