►
From YouTube: Carvel Community Meeting - June 9, 2022
Description
Carvel Community Meeting - June 9, 2022
We meet every Thursday at 10:30am PT. We'd love for you to join us live!
This week we welcomed Twilio to our official list of adopters, went over several releases (both completed and upcoming), and discussed progress on Package Authoring flow with small demo for kctrl. Full agenda here: https://hackmd.io/F7g3RT2hR3OcIh-Iznk2hw#June-9-2022-Agenda
A
All
right,
hi,
everyone
welcome
to
this
week's
edition
of
the
karbal
community
meeting.
Today's
date
is
june,
9th
2022..
If
you
are
watching
this
recording
from
home,
we
encourage
you
to
come.
Join
us
live
we
meet
every
thursday
at
10.
30
am
pacific
time.
It's
a
great
way
for
you
to
come
and
meet
other
members
of
the
community.
The
maintainers
bring
up
any
questions.
You
have
put
a
face
to
names.
If
you
have
any
feature,
requests
or
or
anything
you
want
to
bring
up
to
the
team,
it's
just
a
really
good
live
interaction.
A
A
Now,
if
you
aren't
able
to
come,
join
us
live,
and
you
still
want
to
interact
with
the
team
or
have
questions
or
anything
like
that.
You
can
find
us
in
a
variety
of
ways.
You
can
reach
us
to
the
carville
channel
in
the
kubernetes
slack
workspace.
You
can
email
us
through
google
groups.
You
can
find
us
obviously
in
github
with
any
of
our
project
repos,
so
you
can
submit
an
issue
with
your
feature,
requests
or
anything
like
that
there
and
you
can
also
find
us
on
twitter
at
carmel
underscore
dev.
A
A
A
It
helps
us
understand
just
better
about
you
know
how
folks
are
using
the
tools
and
maybe
helps
us
better,
develop
the
tools
in
that
regard.
It
just
you
know
it's
a
it's
a
good
opportunity
for
us
to
learn
more
and
also
for
other
members
of
the
community
to
learn
more
on
how
to
use
the
tools
optionally.
You
can
also
add
your
logo
to
the
comment
in
a
png
form
and
we'll
get
it
added
to
the
adopters
file
here.
A
B
Yeah
I
can
chime
in
real,
quick,
just
sean
chun
from
twilio,
I'm
just
a
software
engineer
for
the
platform
team
as
well
just
kind
of
hanging
out
and
just
listening
in
most
of
the
other
team
is
out
this
week
just
for
like
a
internal
think
week,
but
yeah.
You
know
happy
to
be
here
thanks
for
having
me.
C
A
D
Yeah,
I
think
this
is
some
of
the
beginnings
of
our
work
around
shipping
cap
controller
and
secret
gen
controller,
for
example,
with
arm
images,
but
this
also
will
be
generally
useful
to
the
community,
since
some
folks
previously
have
inquired
around.
What's
our
plans
around
build
x
integrations,
there
is
another
buildex
functionality
called
bake
that
I
personally
haven't
figured
out
how
people
are
using
it.
It's
a
little
bit
lightweight.
I
think
on
some
examples
out
there.
D
I'm
no
expert
in
docker
build
x,
but
from
my
understanding
it
just
uses
a
different
underlying
mechanism
for
building
the
images
and
so
for
with
build
apps.
You
can
actually
build
images
that
are
multi-platform
versus
with
regular
docker
build.
You
cannot,
as
far
as
I
know,
so
that's
one
difference
that
I'm
aware
of
there
might
be
plenty
more.
A
F
Maybe,
for
the
sake
of
sean
and
scott,
I
guess
you
know
this
thing
that
we're
calling
layering
what
you
should
imagine
is
what,
if
you
had
multiple
packages,
packaged
repositories
and
they
all
contained
identical
copies
of
you
know.
Let's
just
say
this:
the
cert
manager
package
and
you
didn't
want
to
care
that
they
had
identical
copies
of
cert
manager,
because
they're
identical
like
is
fine
right.
F
Just.
Why?
Don't
you
just
like
layer?
Those
package
repositories,
one
on
top
of
the
other
and
pick
whichever
cert
manager
is
on
top
they're,
identical
anyways,
and
so
this
feature
lets
you
do
that
and
it
also
lets
you
set
a
revision
so
that
if
they
aren't
truly
identical,
there's
a
way
of
giving
priority
to
one
package
repository
or
the
other
prior
to
this
feature,
if
you
had
a
packaging
resource
of
an
identical
name,
it
would
cause
the
repository
containing
it
to
fail
to
reconcile.
E
F
G
E
B
G
F
It's
I
always
say
two
packages
that
have
the
same:
like
ref
name,
the
same
name
and
the
same
version
they're
going
to
be
identical
if
the
entirety
of
the
spec
plus
the
the
non-carval
parts
of
the
labels
and
annotations
are
identical
right.
So
it's
it's
gonna
that
identical
check
is
gonna
include
the
sha,
but
it's
gonna
include
much
more
than
just
the
shot.
F
D
So
we
don't
want
to
end
up
in
cases
where,
like
you
know,
you
ask
hey:
what's
your
assert
manager
160
or
something
like
that,
and
you
get
two
results
back?
That
should
never
be
the
case
and
in
fact,
at
the
api
level,
it's
impossible
for
us
to
get
that
right
and
so
the
question
then
results
is
well
what,
if
multiple
things
are
trying
to
give
you
search
manager,
160
right,
multiple
package
repository,
and
so
this
is
a
logic
to
figure
out.
What
is
the
right
thing
that
you
actually
want
to
pick
up.
G
D
G
D
I
guess
I'll
just
mention
real
quick
regarding
the
secret
gen
version,
so
this
was
a
contribution
from
vmware
but
external
to
our
team
to
the
carvel
team.
This
was
a
new
api
introduced
to
secret
gem
that
allows
you
to
kind
of
squish
multiple
pieces
of
data
from
different
resources
into
a
single
secret.
D
It's
going
to
be
useful
to
folks
that,
for
example,
deal
a
lot
with
various
services
and
operators
where
they
just
kind
of
want
to
provide
a
consolidated
piece
of
data
to
their
let's
say
deployment
or
whatever
other
workload
entity,
but
also
at
the
same
time
this
because
this
api
is
genetic,
it
also
could
be
useful
for
providing
input
to
things
like
app
crs
and
package
installs
from
other
external
resources.
So
coming
up
real,
quick
and
then
I
think,
as
a
follow-up
release,
we
will
do
a
ytt
version
of
templating.
D
H
Yeah
sure
so
this
blog
post
is
for
beginners.
Basically,
if
someone
wants
to
someone
is
really
new
to
open
source
and
want
to
start
contributing,
I
have
basically
come
through
a
return
ship
and
it
was
a
totally
new
experience
for
me.
Even
I
had
questions
like
what
is
open
source
and
how
how
do
I
start-
and
I
have
just
consolidated
some
of
my
questions,
some
of
my
learnings
and
my
experience,
and
that
can
help
a
newbie
to
get
started
with
contribution.
H
A
All
right
thanks,
varshad
super
inspiring
and
I'm
sure,
inspiring
to
others
who
are
intimidated
by
getting
started
with
open
source
and-
and
this
certainly
helps
folks
who
may
be
so
used
to
working
in
downstream
stuff
and
proprietary
projects
and
and
helping
them
further
understand
what
it
means
to
work
in
open
source.
So
I'm
really
excited
to
see
see
this
series
come
come
to
life.
A
So
if
you
out
there,
if
anyone
on
the
on
this
meeting
is
interested
in
sharing
their
knowledge
of
how
they
use
the
carvel
tools
with
the
community,
we
have
created
a
sign
up
for
you
to
add
your
name
and
the
topic
you
want
to
cover
and
what
medium
you're
going
to
be
using
to
cover
that
topic.
So
is
it
a
video,
a
vlog
or
a
blog
or
a
workshop,
or
you
know,
are
you
presenting
at
a
conference
on
this
anything
like
that?
How,
however,
you
wish
to
share
your
knowledge?
A
A
And
for
anyone
who
is
outside
of
the
maintainers,
we
want
to
say
thank
you
for
sharing
your
knowledge
and
we
will
send
you
a
t-shirt
or
other
carnival
type
of
swag.
If
a
t-shirt's,
not
your
thing,
we
do
have
beanies
available
as
well
as
we
have
long
sleeve,
shirts
and
short
sleeve
shirts.
So
we
want
to
make
sure
that
we
we
gift
you
with
something
to
to
show
our
appreciation.
I
I
A
E
Yeah
I'll
speak
up
around
that
of
russia,
and
I've
been
carrying
the
torch
here
this
week
on
continuing
our
work
on
out-of-the-box
validation
rules
for
our
upcoming
validation
feature.
You
can
actually
start
to
use
that
feature
right
now.
It's
experimental,
there's
a
previous
blog
post
that
describes
what's
involved
and
how
to
get
started
with
it,
but
we're
continuing
on
that
work
this
week
as
well.
A
J
Sharing
yeah
hi,
so
we
we
have
been
working
on
the
package,
authoring
experience
and
last
time
when
we
showed
we
have
made
improvements
from
that
time.
So
we
try
to
streamline
the
the
we
have
tried
to
streamline
the
way
the
information
is
gonna
be
shown,
and
that
is
what
we
wanted
to
share
today,
so
yeah.
So
I
have
this
package
author
flow.
So
I
already
have
my
kc
drl
binary
here.
It
is
because
it
is
not.
I
J
J
J
For
example,
if
let's
say
I
want
to
leave
the
package
version
as
1.0.0
I'll
just
enter,
and
then
it
it
is.
Gonna
create
multiple
directories
which
are
needed
in
the
package
creation
journey
and
giving
an
explanation
of.
Why
do
we
need
this?
Why
do
we
need
those
basically,
and
then
there
is
this
package
content
step,
so
we
have
reworked
on
the
questions
assuming
that
the
beginners
they
don't
know
much
about
the
carvel
tools,
so
without
introducing
the
carvel
tool.
J
It
is
a
general
idea
on
like
or
to
introduce
them
with
the
questions
which
they
are
familiar
with,
for
example,
if
somebody
want
to
create
a
package
hope
they
will
know
where
their
artifact
is
currently
located.
Is
it
a
release
artifact
from
github
repository
or
is
it
a
helm,
start
from
helm
repository
things
like
that?
J
J
J
J
This
can
be
updated
further
for
more
complex
scenarios,
so
we
will
be
adding
the
links
and
over
there
we
will
be
talking
about
like
how
you
can
update
it,
and
what
does
it
mean?
Also?
It
is
called
it
is
supporting
the
non-interactive
flow
as
well,
and
then
these
are
the
next
steps
which
can
be
done.
For
example,
the
package
can
be
added
to
the
package
repository
and
then
it
can
be
run
and
we
can
publish
the
package
on
the
github
depository.
J
So
again
for
package
repo
as
well,
we
have
a
prerequisite
and
basic
information
just
giving
a
bit
information
about
what
is
a
package
repository.
It's
a
collection
of
package
and
package
metadata
crs
and
let's
say
I
want
to
name
it
demo
repository
and
then
again
giving
a
bit
of
information
on
the
image
package
and
what
is
the
package
repository,
bundle
and
again
creating
the
required
directories?
J
The
next
step
is
to
add
a
registry
url,
so
I'll
add
the
url
and
it
is
going
to
create
the
bundle
again
run.
The
k
build,
create
the
bundle
and
it
is
pushing
the
bundle
and
as
part
of
the
output,
it
has
created
the
package
repository.yaml
again.
The
information
is
that
repo
build
is
generated
where
you
can.
You
know,
make
the
modifications
directly
and
run
it
in
the
non-interactive
flow.
But
these
are
the
next
steps
like
you
can
actually
take
this
package
repository
and
install
it
using
kcdrl.
J
Any
repo
so
and
there
are
no
packages
in
the
system.
So
let
me
try
to
add
this
repo
this
this.
I
am
moving
to
the
consumer
flow
now
right,
just
to
show
the
full
demo.
So
we
are
gonna
see
what
are
the
packages
available
in
this
repo.
So,
as
we
have
created
only
one
package
which
is
dagner
trace,
it
was
created
just
now,
and
that
is
what
we
see
on
the
time
and
let
me
just
install
this
package
yeah,
so
so
it
is,
it
is
in
the
fetch
stage.
J
J
That
is
the
demo.
The
next
steps
will
be,
for
example,
in
the
package
authoring.
We
we
have
not
added
or
even
for
the
repository
on
the
links
to
the
documentation,
and
they
are
yet
to
be
added.
So
we
are
gonna.
Do
that
and
any
feedbacks
we
are
gonna
get.
We
are
gonna
incorporate
and,
as
I
was
saying
like
the
there
are
a
couple
of
flags
which
we
want
to
expose,
as
that
is
what
we
are
gonna
do
yep.
So
let
me.
E
J
Thank
you,
john,
so
also,
I
think
I
I
should
call
out
one
more
thing,
so
the
the
artifacts
we
are
creating,
for
example,
the
package
package,
build
if
you
just
take
a
look
at
it,
so
it
is
actually
encompassing
the
package
and
the
package
metadata,
which
means,
if
you,
because
that
tool
interactively
it
is
gonna
handle
mostly
for
the
beginner
scenarios.
But
let's
say
if
we
want
to
really
handle
a
very
complex
scenarios.
J
The
users
can
just
come
over
here
directly
and
change
the
thing
save
it
run
the
tool
in
a
non
interactive
flow,
and
what
is
it
gonna
do?
Is
it
is
gonna
run
through
all
the
steps
of
doing
a
vendor
sink
running
the
k,
build
image
package
push
and
do
the
image
package
push
on
the
user
behalf
and
ultimately
giving
the
packets
here
so
the
the
end
user?
They
don't
have
to
write
their
own
automation,
scripts,
so
yeah.
G
This
is
really
awesome
from
a
user
and
package
author
perspective.
I
think
this
will
add
huge
usability
and
will
make
adoption
of
the
carvel
tools
much
better
and
much
easier
for
newcomers.
So
this
is
really
awesome
and
I,
like
the
simplicity
of
it,
while
still
giving
huge
value
and
the
educational
part
is
what's
really
key
here.
J
C
C
G
A
Thank
you
so
much
rohit
on
on
a
demo
super
exciting
stuff
to
see
there.
If,
if
anyone
is
watching
this
from
home-
and
you
have
comments
or
feedback
or
any
questions
regarding
this,
you
know
feel
free
to
reach
out
to
us
on
slack
or
any
of
the
other
channels
or
come
find
us
in
the
community
meeting
next
week.
We
would
love
to
hear
from
you
on
that.