►
From YouTube: Carvel Community Meeting - June 2, 2022
Description
Carvel Community Meeting - June 2, 2022
We meet every Thursday at 10:30am PT. We'd love for you to join us live!
Full agenda here: https://hackmd.io/F7g3RT2hR3OcIh-Iznk2hw#June-2-2022-Agenda
A
Welcome
to
this
week's
edition
of
the
carnival
community
meeting
today's
date
is
probably
june
2nd
2022
we
meet
every
thursday
10
30
a.m.
Pacific
time,
if
you're
watching
this
recording
for
some
reason.
Why
weren't
you
here,
you
totally
missed
it
dude,
maybe
next
time,
maybe
hopefully
you
can
join
us
soon.
It's
an
opportunity
to
listen
to
what
the
maintainers
are
working
on
and
etc,
etc.
A
When
you
attend
these
meetings,
we
ask
that
you
please
read
and
abide
by
our
code
of
conduct.
If
you
have
anything
you
wish
to
discuss
with
the
team,
please
add
that
to
the
discussion
topics
at
the
bottom
of
the
agenda.
Additionally,
when
you
attend,
we
ask
that
you
input
your
name
and
any
organization
that
you
represent
into
our
hack
md,
which
everybody
present
has
already
done
so
for
today,
thus
far
skipping
some
parts
of
the
script.
B
A
Okay,
that's
my
announcement
good
numerology!
That's
that's
healthy
sure.
Why
not
great
any
other
announcements.
A
Okay,
similarly,
content,
I
think
this
is
about
like
blogs.
We
love
to
publish
blog
posts,
except
not
this
week
or
next
week,
because
nobody's
written
any
so
moving
on
community
content
sharing,
oh
by
the
way,
if
you
don't
work
for
vmware
and
you
feel
like
writing
a
blog,
we'll
give
you
a
shirt
it'll,
be
so
stylish,
you'll
love
it
status.
Updates
we
have
project
roadmaps.
A
Yeah
right
there's
there's
no
news
on
the
on
the
roadmaps
good
this
week
on
ytt.
B
Yup
yup
we're
continuing
to
plug
away
at
our
validations
feature.
So
this
week
we've
been
working
on,
including
some
out
of
the
box
validations.
We
have
like
the
core
plumbing
in
place,
there's
an
experimental
flag
that
you
can
switch
on.
If
you
want
take
a
look
at
last
week's
conversation
around
that
there's
a
blog
post,
a
recent,
our
most
recent
blog
post
gives
you
a
quick
intro
into
that
in
a
way
to
kick
the
tires,
so
we're
we're
adding
more
to
it.
B
A
D
Okay,
so
on
this,
like
the
last
week,
we
started
looking
into
caching
and
how
might
we
create
some
sort
of
caching
that
would
enable
cap
controller
to
have
to
talk
so
many
times
with
with
the
registry
like
we
started
doing
that
work,
but
then
we
kind
of
stopped
it
for
a
little
bit,
because
we
do
have
some
questions
about
where
the
caching
might
go
or
like.
Are
we
doing
it
in
the
correct
layer
or
not,
and
so
we
are
investigating
around
that
area.
D
We
also
started
looking
into
some
so
for
image
package
start
looking
into
some
performance
issues
when
you're
doing
a
describing
pool
the
the
commands
take
a
lot
of
time
and
we're
trying
to
somewhat
trying
to
find
out.
If
there's
like
anything
that
we
can
do
to
improve
that
experience,
we
saw
that
there
might
be
some
changes
that
we
can
do
in
one
of
the
libraries
that
we're
using
that's
go
container
registry
that
might
increase
our
timing
there
and
the
number
of
requests.
D
We
also
do
to
the
registry,
especially
on
arbor,
more
than
any
other
registry,
because
arbor
has
like
a
different
behavior
from
the
other
registries,
where,
if
you
talk
to
the
registry
on
the
v2
path,
it
just
returns
to
401,
it
returns
like
an
unauthorized,
while
the
other
registries
allow
anonymous
anonymous
checks
on
that
on
that
particular
path.
Harvard
does
not
so
that
kind
of
makes
all
the
requests
to
arbor
like
a
little
bit
more
complicated.
D
E
A
D
D
If
you
start
adding
like
all
the
versions
of
your
software
into
it,
and
when
you
need
to
transport
the
the
image
package,
bundle
that
is
associated
with
the
package,
repo
from
register
to
registry,
like
everything
that's
going
to
be
copied,
is
going
to
increase
and
increase
and
increase,
because
one
of
the
one
of
the
things
that
we've
been
telling
people
is
to
you
can
put
all
your
versions
there.
So
we
are
starting
to
look
into.
D
How
might
we
address
this
into
a
and
to
address
this
issue
and
to
try
to
make
it
easier
for
people
that
especially
people
that
have
air
gaps
environment
so
that
they
install
their
software
in
in
a
network
that
doesn't
have
access
to
the
internet,
so
they
need
to
copy
to
disk
all
the
assets
then
copy
to
that
network
and
then
just
push
it
up.
So
there's
like
this
extra
step
that
can
be
a
little
bit
cumbersome.
D
So
we
are
looking
into
that
yeah
and
we
have
like
a
discussion
topic
a
little
bit
about
it
but
I'll
park
it
here
and
we'll
talk
when
the
discussion
time
arrives.
A
Wonderful,
thank
you.
I
think
we
could
leave
cap
controller
for
now
updates
on
cap,
I'm
actually
not
sure
who
wants
to
speak
stomach
awesome.
That's
me.
F
Okay,
so,
firstly,
we
we've
had
users
like
ask
for
an
easy
way
to
look
at
the
final
manifest
that
cap
flies
onto
a
cluster.
This
is
more
like
a
client-side
driver
and
I
would
say
which
helps
users
figure
out,
which
the
base
rules
they
want
and
what's
going
to
the
cluster
at
the
end
right.
So
that's
something
we've
been
working
on,
and
so
we
have
a
user
who,
like
who's,
working
on
something,
that's
heavily
dependent
on
customized
and
customized.
F
Does
this
thing
where,
when
it's
generating
config
maps
and
secrets
it
sort
of
appends
a
random
string
to
it,
it's
customizes
way
of
versioning
conflict
maps
and
secrets,
so
one
easy
way
of
going
around
this
was
to
disable
this
behavior
and
to
depend
on
cap
for
versioning.
However,
blister
seems
to
be
working
with
something
that
is
pretty
heavily
dependent
on
customized,
so
they've
been
sort
of
working
with
us
to
enable
sort
of
implement
a
feature
which
lets
cap
version,
customize,
config
maps
and
secrets,
while
ignoring
the
suffix,
yes
suffix,
while
ignoring
the
suffix.
F
A
Wonderful
and
you
know
the
much
debated,
k-control
kctrl
tool-
this
is
okay.
Are
you
also
going
to
speak
about
that?
One
yeah.
F
I
think
that's
me
yeah
nothing
new,
so
we
talked
about
last
time
that
we
are
going
to
sort
of
figure
out
how
we
want
the
experience
to
be
when
users
are
trying
to
sort
of
apply
overlays
while
installing
a
package,
and
so
we
have
been
sort
of
plotting
out
how
that
looks,
how
we
want
to
order
overlays
and
stuff
like
that,
so
yeah,
that's
where
we
are
at
with
k,
control.
A
Okay,
wonderful,
thank
you,
and
now
we
at
long
last
the
moment
you've
all
been
waiting
for
discussion
topics.
Joe
did
you
have
something
on
your
mind
to
discuss.
D
It's
not
really
a
discussion,
it's
more
ask
here,
so
we're
trying
to
find
people
that
are
using
package
repositories
to
provide
their
software
and
we'd
like
to
talk
to
you.
If
you're
doing
that,
we
we
want
to
try
to
better
understand
what
are
your
workflows
and
what
how
you're
doing
it?
How
do
you
separate
versions
and
all
those
nice
things
about
package
repositories
and
packages
for
us
to
try
to
provide
to
see
if
there's
like
room
for
us
to
provide
a
better
user
experience
this?
D
This
also
like,
as
as
a
relationship
with
the
topic
that
I
was
talking
about
cap
controller,
where,
if,
if
our
image
package
bundles
associated
with
the
package,
rebar
just
gonna
keep
on
increasing,
we
need
to
have
a
way
we
need
to
have
a
way
to
make
it
easier
for
for
the
users
right
so
like
if
you
do
have
some
time.
D
A
Okay,
that's
all
for
now.
Okay,
great.
A
And
also
our
friends,
david
and
by
proxy
sean,
we'll
just
thanks
both
so
the
other.
The
other
topic
is
from
lee,
who
isn't
here
some
kubecon
follow-up.
A
A
Yeah,
thank
you
all
for
working
with
me,
but
you
can't
click
this
link
anyway,
but
I
could,
if
I
wanted
to
they're,
hosted
here
you
you
can't
click
it
it's
on
my
screen,
not
yours,
and
now
we
have
a
moment
we're
already
at
the
bottom
of
the
agenda,
and
so
we
can
have
I'll
I'll
give
a
couple
minutes
for
free
discussion,
thoughts.
Anything
on
the
group's
mind
in
the
air.