►
From YouTube: Carvel Community Meeting - August 10, 2022
Description
Carvel Community Meeting - August 10, 2022
We meet every 2nd and 4th Wednesday of the month at 9am PT. Come join us live!
This week we talk about 3 new releases, our nearly updated roadmap structure, what the team is working on, and had a great demo on package authoring with kctrl. Check out full agenda here: https://hackmd.io/F7g3RT2hR3OcIh-Iznk2hw#August-10-2022-Agenda
A
Hi
everyone
welcome
to
this
week's
edition
of
the
carville
community
meeting.
Today's
date
is
august,
10th
2022.,
if
you're
watching
this
from
home,
we
encourage
you
to
come.
Join
us
live
we
meet
every
second
and
fourth
wednesday
of
the
month
at
9
a.m.
Pacific
time
it's
a
really
good
opportunity
for
you
to
come
and
bring
any
questions
you
have
about
the
cardinal
tools.
A
Any
feedback
or
free
feature,
requests,
listen
in
on
what
the
the
team
is
working
on
or
you
know
if
you
want
to
provide
feedback
on
what
they're
working
on
anything
like
that,
we
we
would
love
to.
Have
you
come
join
us
live
for
those
that
are
here
today.
There
is
something
you
wish
to
discuss
with
the
team.
A
Just
a
reminder
you
can
put
that
down
in
the
discussion
topic
section
of
the
agenda
and
we
will
get
to
it
later
on
if
you're
unable
to
join
the
meeting
live,
and
you
still
want
to
reach
out
to
us.
If
you
have
a
feature
request
or
anything
like
that,
there
are
options
to
choose
from.
You
can
find
us
in
the
carville
channel
and
the
kubernetes
workspace.
A
A
This
helps
us
helps
us
to
further
plan
development
of
the
tools
trying
to
understand
how
folks
are
using
the
karbol
tools,
and
it
also
helps
the
community
understand
how
they
could
also
use
their
cardboard
tools.
So
it's
a
really
good
way
to
share
your
knowledge
with
with
everyone
in
the
community,
including
the
maintainers
that
work
on
the
tools.
A
A
For
those
are
in
this
meeting
today,
just
a
reminder
we
would
like
for
you
to
add
your
name
to
the
attendees
list,
so
we
can
keep
track
of
folks
who
are
joining
the
meetings
live
and
if
you
represent
any
organization,
you
feel
comfortable
sharing
that
make
sure
to
put
that
in
parentheses.
Next
to
your
name,
moving
on
to
announcements
so
for
content,
I
wanted
to
highlight
a
couple
of
posts
that
we
had
by
members
of
the
community
so
by
scott
rosenberg.
A
B
A
D
Yeah,
no,
it's
been
a
fun
process
and
I
just
decided
to
so.
I've
been
setting
up
a
new
home
lab
with
kubernetes
installed,
and
I
just
decided
about
blog
about
the
process
and
one
of
the
things
I
always
wanted
to
put
on
there
was
was
concourse
because
it's
one
of
my
favorite
tools,
but
I
haven't
done
any
helm
yet
and
I
didn't
want
to
do
the
docker
compose
route
and
so
I'm
like
well.
D
How
am
I
going
to
do
this
and
I've
been
using
cap
and
ytt
and
some
of
the
other
tools
to
really
help
with
the
process,
and
it
really
came
together
in
kind
of
a
fun
way
able
to
use
some
really
interesting
things
like
secret,
gen
controller,
to
create
the
certificates,
and
things
like
that
that
I
don't
care
to
actually
know
or
store
in
the
secret
store,
or
anything
like
that.
So
it's
been
pretty
fun.
A
B
A
E
A
B
A
So
we
invite
this
to
to
everyone
to
share
how
they're
using
cargo
tools,
what
excites
them
about
their
cargo
tools,
how
they're
using
it
with
other
projects
with
their
tools,
products.
Anything
like
that
anything
that
you
find
really
interesting.
We
would
love
for
you
to
share
that
with
us
and
all
of
the
community
at
large.
So
please
feel
free
to
sign
up
here
to
input
that
you
are
creating
something
to
share
what
that
medium
is
the
twitter
handle
twitter
handle.
A
If
you
would
like
for
us
to
tag
you,
alternatively,
like
how
I
came
across
scott
and
pete's,
is
that
they
tagged
us
in
twitter
posts,
and
so
I
I
saw
that
they,
I
created
those
posts
and
made
sure
to
give
them
a
shout
out
here
and
did
whatever
I
could
to
to
help
promote
that,
and
and
thank
them
for
for
sharing
their
knowledge.
So
if
you
have
any
questions
about
that,
please
let
us
know.
D
D
D
E
Well,
I
think
I
kind
of
said
this
in
private,
but
the
the
theme
of
this
release
is
basically
oops.
We
waited
a
long
time
between
releases,
so
there's
a
lot
of
things.
I
think
the
downwards
api
is
really
exciting.
You
can
get
more
information
about,
oh
man.
Well,
it
was
really
exciting.
Before
I
forgot
exactly
what
it
did,
but
anyways
you
can
get
more
information
passed
into
your
templating
step.
We
we
upgraded
almost
all
of
the
so
many
things.
B
E
F
D
F
E
E
Some
version
constraint
stuff,
so
it's
we.
This
is
really
just
a
it's
kind
of
this.
This
is
highlighting
that,
in
order
to
make
a
cap
controller
change,
you
often
have
to
first
make
a
change
in
cap,
gender
image
package
or
one
of
the
other
muppets,
so
it
it.
This
is.
This
is
just
our
distributed
code
base
percolating
outwards
so
because
we're
working
on
a
story
for
version
constraints
we
needed
to
generalize
something
and
how
vendor
does
version
constraints.
Cap
controller
doesn't
do
its
own
version
constraints.
E
A
Okay,
moving
on
to
project
road
map,
so
I
renew
one
of
the
engineering
managers
based
in
india
for
cargo,
updated
this
and
merged
the
pr.
I
believe
earlier
today
and
we've
kind
of
changed
a
little
bit
of
the
structure
of
the
roadmap
itself,
adding
a
stage
here
so
more
of
like
a
status
of
what
that
that
feature
where
that
feature
is
and
what
the
team
has
been
working
on
and
the
timeline
expected
to
be
released.
A
G
What
do
you
say,
responsive
and
wanted
to
also
give
crispr
timelines
as
to
what
we
are
doing
and
also
as
to
what
stage
of
those
activities
we
are
in?
So
I
think
theme
and
feature
are,
I
guess
you
guys
are
all
aware
of
what
we
have
added
is
stage
which
tells
exactly
what
is
happening
with
that
feature,
as
is
it
is
it
in
the
proposal
state?
So
I
will
give
out
one
thing
that
is
missing
from
this
is:
what
are
the
different
stages
that
we
are
thinking
about?
G
G
I
hope
the
timelines
give
a
better
visibility
as
to
when
these
features
are
coming
to
the
community
and
we
thought
of
putting
in
quarters
here,
but
that
seemed
very
broad,
so
we
have
actually
try
to
work
to
get
it
to
really
close
closer
timelines
to
when
we
are
expecting
it
to
come
out.
We
do
not
know
the
release,
because
releases
are
still
the
cadence
for
releases
are
generally.
G
A
All
right,
thank
you,
renu,
okay,
moving
on
to
this
week's
what
the
team's
been
working
on
backlog,
I
wanted
to
point
out
that,
while
we've
been
using
zenhub
for
I
don't
know,
last
year
year
and
a
half,
we
have
been
moving
over
to
github
projects.
So
I
know
aaron
was
going
to
talk
a
little
bit
about
this,
but
I
think
he's
still
stuck
in
a
different
meeting.
A
B
Yeah,
I
can
add
a
little
color,
but
our
main
motivator
here
is
to
try
and
just
make
this
more
accessible
to
the
community
like
you're,
saying
and
so
we're
at
the
point
now,
where,
like
all
of
our
work,
is
represented
in,
like
this
view
here
we'll
be
doing
more
to
like
break
things
down
in
like
different
sections
as
we
need
it
or
folks
need
it
so
that
you
can
like
zoom
in
on
the
pieces
that
you
want
to
see.
There's
a
there's,
some
work
that
we
need
to
do
to
all
the
stuff.
B
F
Hello,
your
favorite
time
of
every
other
week
is
here
just
for
you
all
right.
So
what
what
has
been
happening
in
image
package?
So
three
things
have
been
happening.
Image
package
right
now
in
the
last
couple
of
weeks,
we're
still
working
on
this
image.
Caching,
information
part
for
image
package.
This
is
part
of
like
a
bigger
initiative
that
is
to
try
to
make
sure
that
cap
controller
contacts
is
less
times
or
less
often
the
registry.
So
that's
that
work
is
still
ongoing.
F
F
We
didn't
have
that
implemented
and
shaheer
is
doing
this
pr,
so
pretty
excited
to
have
that
and
the
third
topic
is
it's
not
something
that's
on
in
flight?
It's
something!
That's
there
there's
a
pr
there,
that's
the
number
and
it
is
going
to
bump
gcr
to
a
newer
version
and
will
allow
the
users
to
authenticate
a
little
bit
differently
when
they
are
inside
an
is
that
currently
it
stopped.
We
are
not
working
on
that.
F
D
Oh,
so
I
think
most
of
the
work
in
cap
went
towards
allowing
users
to
set
sort
of
like
in
expiration
time
on
the
resource.
Basically,
one
of
our
users
wanted
to
say
that
if
this
resource
has
existed
for
more
than
five
minutes
that
and
if
it
if
cap
tries
to
deploy
it
again,
we
want
to
either
version
it
or
deploy
it
again,
and
so
that's
yeah,
that's
the
new
feature.
D
C
Yep,
I
I
kind
of
provide
an
update
on
the
key
control.
So,
as
you
know
like
we,
we
are
approaching
the
alpha
release
and
we
were
working
towards
that.
So
we
we
were
trying
to
wrap
up
the
documentation,
so
we'll
spend
a
bit
of
time
on
the
documentation
for
the
package
authoring
command
and
we
are
working
to
towards
merging
the
pr
of
package
authoring
code
into
the
dev
branch
and,
as
you
have
mentioned
and
see
next
week,
we'll
be
looking
to
cut
the
alpha
release
for
the
scene.
B
Yeah
varsh
and
I've
been
steeped
in
usability
testing
around
our
validations
feature.
If
you
feel
like
you're,
missing
out
click
that
link
and
that'll
give
you
a
preview
a
way
of
getting
set
up,
and
if
you'd
like
to
have
us,
hang
out
with
you.
While
you
try
that
out,
we
would
love
to
be
there
with
you,
there's
a
number
of
folks
that
we've
reached
out
to
we're
setting
up
times
to
chat
with
them.
B
If
you
want
to
be
one
of
those
folks
just
come
to
our
slack
and
ping
us,
we
would
love
to
get
your
live
feedback
on
this
feature,
it's
in
experimental
mode
right
now,
which
means
that
we
can
make
adjustments
to
the
api.
But
once
we
release
it,
we've
been
committed
to
not
making
breaking
changes
in
most
of
our
tools
and
if
we
have
to
it's
very
rare
so
we're
this
is
work
that
we're
trying
to
do
to
make
sure
that
it's
useful
for
you.
A
A
Okay
on
to
discussion
topics,
so
there
was
an
issue
here
that
has
been
was
posted
back
in
december.
2020
there's
been
discussion
on
it
and
recently
kind
of
brought
back
to
life,
so
joe
had
posted
a
slack
message
in
our
public
channel
in
the
kubernetes
workspace
asking
for
the
community's
input
on
what
they
would
like
to
see
from
this,
and
if
they
they
would
find
value
out
of
it.
A
Okay,
so
for
those
that
are
watching
from
home,
encourage
you
to
go.
Take
a
look
at
this.
Let
us
know
if
it
would
be
something
useful
for
you.
You
know
just
there's,
there's
a
lot
of
different
things
that
we
have
like
requests
on
and,
and
we
want
to
make
sure
that
the
team
is
working
on
on
like
efficiently
and
things
that
that
would
be
valuable,
and
so
we
want
to
know
like
how
how
others
are
using
the
tools,
and
if
this
is
something
that
we
should
prioritize.
So
please
take
a
look.
Go.
C
C
So,
sometime
back,
we
started
looking
on
to
simplifying
the
package
authoring
workflow,
because
the
when
you
author,
a
package,
you
basically
need
to
know
almost
all
of
the
cargo
tools,
and
that
was
a
barrier
and
we
wanted
to
simplify
that
process
so
that
the
new
and
the
like,
the
beginner
and
the
experienced
users
we
if
they
can
come
and
create
a
good
quality
cardboard
packages.
So
that
is
how
all
of
this
simplifying
of
the
package
authoring
has
started,
and
we
did
a
bunch
of.
C
We
floated
around
the
survey
where
we
asked
how
they
envisioned
the
tool
and
it
looks
like
because
everything
is
happening
on
the
cli,
so
the
the
cli
was
a
way
to
go
even
for
the
package
authoring
commands
as
well
and
so
coming
on
to
the
package
authoring.
So
we
envision
that
the
package
authoring
it's
kind
of
an
iterative
flow.
C
So
we
are
package
authors
they
they
already
have
some
kubernetes
configuration
which
they
would
love
to
package
and
once
they
have
the
configuration
they
will
like
to
template
or
add
some
overlays
to
it,
which,
which
is
an
iterative
process
until
they
get
it
in
the
desired
shape.
So
they
will,
you
know,
repeat
over
writing
the
overlay
or
the
template
part
to
get
it
right.
C
So
once
everything
is
in
place,
they
would
love
to
make
a
release
of
the
of
the
package
so
that
it
becomes
distributes
distributable
and
can
be
consumed
by
the
package,
consumers
so
preferably
they
they.
They
want
to
do
it
in
a
automated
way,
maybe
in
a
github
action
or
something
like
that
right
and
yeah,
so
that
that's
how
we
have
envisioned
it,
and
now
I'll
be
so
now
giving
this
in
place.
So
we
have
introduced
a
couple
of
commands
on
the
k
control.
C
C
But
what
will
happen
is
the
dev
deployer
command
will
give
you
the
feel
of
cap
controller
running.
So
when
you
run
the
dev
deploy,
it
will
deploy
everything
locally.
In
the
same
way,
the
tab
controller
will
do
and
you
will
have
your
application
and
up
and
running
so.
You
can
also
like
iterate
over
your
configurations
quickly
and
see
that
the
they
they
are
in
the
correct
place
and
they
are
getting
changed.
The
way
we
want
in
the
desired
behavior
and
once
everything
is
in
place.
C
All
the
pieces
are
in
place,
we'll
see
that
we'll
have
a
command
called
k,
control
package,
release
which
will
help
to
release
the
package.
And
then
you
can
add
those
package
and
package
metadata
to
the
package
repository
and
can
run
key
control
package
wrapper
release
to
release
that
package
repository
itself.
C
So
that
is
the
whole
flow,
so
I'll
be
demoing
that
starting
from
initialization
to
the
dev,
deploy
and
do
the
release
yeah
and
then
we'll
see.
Based
on
the
time,
we
can
do
the
adding
of
the
package
to
repo
and
releasing
the
repo
or
we
already
have
covered
it
in
the
documentation
which
will
be
coming
out
so
yeah.
C
B
C
So
it
is
asking
for
the
package
reference
name
like
the
package
name
again,
some
basic
information
about
how
the
package
name
should
be,
so
let
me
give
it
demo
dot
karbal.dev
and
then
it
is
asking
from
where
it
can
fetch
the
kubernetes
manifest.
So
we
have
a
bunch
of
options
so
this
time,
because
I
want
to
package
my
own
application
from
my
source
code,
so
I'll
say
local
directory
and
then
it
is
asking
which
what
configuration
or
what
files
need
to
be
part
of
this
package.
C
C
So
now,
if
we
look
into
both
of
these
files
package
build.yaml,
this
is
how
it
looks
I'll
I'll
come
back
to
it
later
on,
but
we'll.
Let's
look
at
the
package
resources.yaml
file
first,
so
it
contains
package
package
metadata
and
package
install
again.
Some
of
the
things
are
filled
with
with
the
values
provided
which
are
default
values,
so
they
can
be
changed
by
the
users
once
they
are
changed,
they
will
stay
there,
which
means,
when
you
are
releasing
the
package
at
that
time.
These
values,
you
will
see
these
changed
values.
C
Right
so
now
we
have.
I
also
want
to
bring
attention
towards
the
package
and
package
install
so
when
we
said
that
you
might
want
to
add
some
overlays
or
templates
and
retreat
over
it
multiple
times,
so
how
those
configurations
or
how
those
will
be
picked
up
is
by
the
dev
deploy
feature
is
via
the
package
and
package
install
here
so
dev
deploy
will
pick
up
this
package
and
package
install
and
it
will
try
to
deploy
it
on
to
the
kubernetes
cluster.
C
C
With
the
help
of
k
build,
I
actually
want
to
build
my
image,
but
at
the
during
the
dev
deploy
flow.
I
don't
want
to
push
my
image
to
a
oci
registry,
because
it
is
still
very
much
in
the
development
space
as
of
now
right
and-
and
I
want
to
add-
let's
say
my-
I
already
have
an
overlay
which
will
add
the
resource
requested
and
limit,
and
I
want
to
add
this
overlay
as
well.
C
C
C
So,
if
I'll
do
kctrl
deploy
hyphen
h,
it
has
a
couple
of
flags.
So
what
hyphen
hyphen
k
build
build
will
do.
Is
it
will
allow
the
k
build
to
actually
build
here
binary,
and
then
we
have
the
hyphen
l,
which
is
local
so
that
we
can
use
the
local
fetch
source
yeah,
so
we'll
be
using
these
two
variables.
C
So
let
me
do
k
control
dev,
deploy,
hyphen
b
hyphen
l
and
my
package
and
package
install
are
present
in
the
package.
Resources.Yaml
yeah,
before
we
move
on
one
more
thing:
the
package
install
it:
has
the
service
account,
so
this
service
account
needs
to
be
created
beforehand.
Otherwise
the
dev
deploy
will
fail.
C
If
I
do
cue
cutter
get
essay,
so
I
already
have
the
demo
service
account,
so
let
me
just
run
it
also.
We
can
run
it
in
the
debug
mode
to
see
that
what
is
going
on
to
get
more
depth
in
there
but
yeah,
let
me
just
run
it
in
the
debug
mode,
so
we'll
see
that
cable
is
actually
building.
So
you
can
see
that
here
the
cable
is
actually
building
the
image.
C
Yep
and
then
it
is
on
deploying
that
so
the
reconcile
has
succeeded,
and
if
I
do
cap
ls
hyphen
a
so,
I
can
see
that
my
demo
dot
app
has
been
installed
and
everything
is
there,
but
I
do
not
have
the
cap
controller
in
this
cluster,
so
this
is
the
dem.
The
part
with
dev
deploy,
dev
deploy
is
purely
optional,
and
then
we
move
on
to
so
now
I
have
everything
in
place,
so
what
I
want
to
do
is
I
want
to
make
a
release.
C
C
So
what
I
need
to
do
is
I
need
to
go
to
the
package
build
which
we
said
we'll
come
back
in
a
bit
now
package
build,
has
two
sections:
one
is
this
abspec
section
which
contains
your
deploy
and
template,
and
then
there
is
this
export
section,
so
this
deploy
and
template
will
get
copied
over
to
the
releasable
package.
So
we
need
to
make
sure
that
our
overlay
is
present,
which
should
get
picked
up
by
the
ytt.
C
And
I
also
want
to
pick
my
config
release
folder
now
the
export
will
what
today
the
package
authoring
it
will.
Actually,
when
it
is
trying
to
release
a
package,
it
will
create
an
image
package,
bundle
for
you
and
what
does
that
image
package
bundle
will
include,
will
be
defined
in
this
include
paths.
C
So
now,
if
I
go
in
here
and
if
I
look
into
the
key
control
package-
release
hyphen
h
again,
one
thing
I
want
to
highlight
is
we:
have
this
version
flag
which
is
exported
so
that
the
key
control
command
can
be
the
release
command
can
be
reused
in
the
automated
flow
as
well.
So
let's
say
I
give
version
1.0.0.
C
C
And
then
it
will
do
the
image
package,
it
will
create
that
bundle
and
it
will
do
the
image
package
push
and
we
see
that
these
are
all
the
content
of
the
bundle
which
we
wanted
to
include
and
our
artifacts
are
created
in
here.
So
if
I'll
do
that
of
this?
Is
the
package
metadata
so,
as
I
said
like,
whatever
the
value
will
change
over
there,
it
will
stay
in
in
your
even
released
package.
C
B
C
B
That's
fantastic.
I
love
the
little
flourishes,
there's
little
bits
like
where
the
k
build
configuration
automatically
reaches
in
into
the
images
yaml
in
the
bundle
like
you
don't
have
to
remember.
To
include
that.
There's
a
lot
of
little
things
I
saw
like
the
overlays
had
both
the
the
kind
and
api
version
in
them
like
it
was
really
neat,
seeing
like
all
those
little
easy
to
easy.
Gotchas
are
just
like
covered
just
by
using
the
tool.
H
E
H
H
C
C
A
A
G
A
Yeah
we
could
do
the
banner
at
the
top
that
that
we
haven't
utilized,
since
I
think
kubecon
yep
or
something
yeah
cucumber
north
america
21.
So
we
could
do
that
and
then
I
definitely
want
to
write
a
blog
post.
Get
that
put
out
there
just
quick
synopsis
of
of
what
the
software
release
does
and
how
you
want
folks
to
use
it
and
test
it
and
how
they
can
provide
feedback
so
and
all
the
documentation
associated
with
it.
But
if
anybody
else
has
any
any
ideas.
E
It's
not
clear
to
me
why
we,
it
does
feel
like
the
website
might
be
not
organized
according
to
our
users
goals
so,
like
maybe
our
users
don't
really
care
whether
cap
control
or
cap
or
k
control.
Like
there's
a
lot
of
everything
starts
with
the
letter
k
anyways.
You
could
just
snip
that
first
letter
off
it
has
no
information,
but
it
feels
like.
Maybe
we
are
way
overdue
to
have
our
website
be
a
little
more
like
user
directed,
and
you
know,
barring
that
we
could
just
decide
to
start.
E
A
Yeah,
it's
definitely
been
a
topic
of
discussion
for
a
year
now
about
updating
the
website
to
make
it
more
user-friendly
and
the
information
architecture
is
a
little
bit
easier
to
digest
and
find,
but
to
your
suggestion
on
on
just
like
a
quick
thing
for
this
particular
item,
I
think
that's
like
a
whole
other
thing
that
we
would
have
to
to
talk
about
and
how
to
who
who
would
create
it?
What
would
what
would
it
look
like?
Where
would
it
live?
Who
would
like
all
sorts
of
stuff
would
go
into
that.
A
A
We
will
also
have
someone
joining
us
from
robusta
talking
about
their
initiative
for
a
hundred
tools
in
a
hundred
days,
they're
featuring
the
cardinal
tools
and
wanted
them
to
give
a
little
bit
a
highlight
of
what
what
their,
what
robusta
does
and
what
their
initiative
is,
and
all
that
good
stuff
so
come
check
that
out
for
the
next
meeting.
Again
we
meet
every
second
and
fourth
wednesday
at
9
a.m.
Pacific
time
and
with
that
hope
to
see
you
soon
have
a
good
day.
Thank
you
for
joining
today.