►
From YouTube: Carvel Community Meeting - March 17, 2022
Description
Carvel Community Meeting - March 17, 2022
We meet every Thursday at 10:30am PT. We'd love for you to join us live!
This week we had Soumik Majumder demo kctrl, kapp-controller's native CLI! Check out full notes here: https://hackmd.io/F7g3RT2hR3OcIh-Iznk2hw?view#March-17-2022-Agenda
A
If
you're
watching
this
from
home,
please
come
join
us
live,
we
would
love
to
have
you.
We
meet
every
thursday
at
10
30
a.m.
Pacific
time
it's
a
great
opportunity
for
you
to
come
and
meet
the
team.
Other
members
of
the
community
bring
up
any
questions
you
might
have
of
using
any
of
the
carvel
tools
or
have
any
feature
requests
or
just
want
to
kind
of
sit.
Listen
in.
We
would
love
to
have
you
for
those
that
have
anything
they
want
to
discuss
with
the
team.
A
If
you
aren't
able
to
join
us
for
these
meetings,
you
can
find
us
on
slack
and
twitter,
we're
in
the
carville
channel
and
the
kubernetes
slack
workspace
and
we're
on
twitter
at
karbal
underscore
dev
at
any
point,
you're
interacting
with
us
or
other
members
of
the
community.
Please
read
and
abide
by
our
code
of
conduct,
which
is
tagged
here
and
it
goes
to
towards
our
repo,
which
is
where
you'll
find
it.
A
A
Moving
on
to
announcements,
so
we've
got
an
exciting
opportunity
here
for
you
to
come
and
join
the
carnival
team,
we're
looking
for
a
product
line
manager,
the
job
requisite
is
here
listed
in
the
agenda.
You
can
also
find
it
on
the
the
careers
page
for
vmware
aaron
or
anyone
that
knows
more
about
this.
That
wants
to
talk
about
this
particular
open
role.
B
Yeah,
I
can
speak
to
it
a
little
bit
this.
This
is
a
fairly
high
level
position,
so
it'd
be
working
with
the
project
and
really
understanding
a
bit
better
like
where,
in
the
marketplace,
the
ecosystem
that
we
fit
in.
What
are
the
opportunities
that
we
want
to
pursue,
and
I
mean,
generally,
you
get
to
work
with
a
great
team
of
motivated
engineers,
so
yeah
come
come
check
it
out
and
join
us
and
it'll,
be
it'll,
be
fun.
A
Thanks
erin
and
yeah,
I
might
be
a
little
biased,
but
I
love
this
team.
They're
rock
stars
they're
a
lot
of
fun
to
work
with,
so
I
highly
encourage
you
to
look
into
that
and
find
us
on
slack.
If
you
have
any
questions
for
that
particular
role
now,
moving
on
to
content
this
week,
we
have
a
few
blog
posts
coming
out
that
are
regret
regarding
the
new
kctlr
release,
so
stay
tuned
for
that
we're
hoping
to
either
post
it
today
or
tomorrow,
but
yeah
we'll
put
it
on
our
website.
A
Whenever
those
become
released
upcoming
content,
we
have
a
free
virtual
workshop
kubernetes
days,
bengaluru,
it's
cloud
native
application,
life
cycle
management
with
cap,
the
cap
maintainers-
and
we
do
have
cap
containers
here
today
which
I'm
super
excited
about.
They
are
based
in
india,
so
this
time
isn't
always
so
friendly
with
them.
So
if
either,
if
anyone
from
the
cap
team
wants
to
sumic,
do
you
want
to
say
anything
what
to
expect
for
this
workshop.
C
While
you
know
managing
the
life
cycle
of
an
application
that
is
deployed
on
top
of
humanities
and
then
sort
of
distributing
them
reliably,
and
we
sort
of
initially
want
to
focus
on
the
motivation
behind
each
of
the
individual
tools
and
then
how
cap
controller
sort
of
helps
us
to
replicate
dev
workflows,
built
using
these
these
tools
reliably
on
a
cluster
and
then
package
and
version
and
distribute
different,
such
workflows,
so
we'll
sort
of
be
building
like
a
small
demo,
app
of
sorts
from
scratch,
along
with
the
participants
yeah.
That's
what
we'll
be
doing.
A
A
Okay
on
to
just
a
reminder:
we
have
community
content
sharing,
so
this
means
we
have
what
we're
doing
is
we
want
to
post
weekly
content,
whether
that's
a
blog
post,
video
demo
presentation,
whatever
medium
that
you're
most
comfortable
with?
We
would
like
folks,
not
only
just
the
maintainers
but
members
of
the
community,
to
share
things
about
karbal,
any
ways
that
they're
using
the
tools,
if
they're
using
it
with
other
other
projects,
other
tools.
How
are
they
using
it?
A
A
If
you
have
a
twitter
handle
and
want
to
us
to
tag
you
in
a
tweet,
whenever
we
promote
that
that
content-
you
can
put
it
here,
but
essentially
I
will
we'll
post
it
in
all
our
channels,
we'll
you
know
make
sure
we
we
mention
it
in
our
community
meetings
and
we'll
post
it
wherever
we
can
to
share
that
content
and
for
those
that
aren't
carnal
maintainers.
You
will
receive
a
carnival
t-shirt
as
a
thank
you.
A
D
Hello,
here's
our
friend
image
package.
Again,
it's
like
releases
every
week,
it's
like
christmas
every
week.
Look
at
that
new
features,
bug
really
bug
fixes.
Everything
is
awesome,
so
just
to
give
you
a
little
color
here
we
last
week
we
talked
about
the
describe
command
that
we
added
now
we
add
the
new
flag
that
allows
you
to
show
to
enable
or
or
not
the
retrieval
of
cosine
artifacts.
D
So
we're
talking
about
the
display
images,
sorry,
the
signatures
costline,
so
you
can
just
provide
this
flag
and
tell
it
tell
image
package
if
you
want
or
not
to
see
the
cosign
artifacts,
the
the
release
was
done
right
now,
because
there
was
a
an
issue
with
the
copy
of
bundles
two
tars
and
then
the
upload
again,
the
import
to
the
registries.
Again,
the
one
of
the
images
that
image
package
controls
that
that
stores
to
survey
the
cache
was
being
correctly
formed.
D
So
this
was
causing
problems
to
people
that
were
copying
to
tar
and
then
uploading
the
tarp
importing
the
guitar
to
the
repo
and
then
downloading
the
tar
again
to
tar.
Sorry
downloading
the
repo
again
to
tar.
It
was
not
correct.
The
output,
so
this
is
what
this
fix.
So
if
you
have
this
scenario
where
you
copy
the
tar
to
repo
and
then
copy
from
the
reboot
to
tar,
please
update
to
this
version
and
then
you
shouldn't
have
any
problem.
So
I
think
that
was
it
for
image
package.
A
C
C
C
F
C
So
in
case
the
user
directly
tries
to
install
the
package
without
specifying
a
version
we,
instead
of
installing
the
latest
floating
version
on
the
cluster.
What
we
do
is
we
list.
The
version
then
say
that
we
are
expecting
the
user
to
provide
a
version
explicitly
that's
what
that's
what
we're
doing
today,
and
so
I'm
gonna
specify
the.
C
C
C
C
C
Okay,
so
we're
gonna
be
kci
trl's
package
install
date
and
the
package
install
that
we're
updating
is
called
cert
one.
So
since
the
package-
and
the
version
remains
the
same,
we
are
only
going
to
specify
the
values
file
right
now
and
the
values
file
is
values.yaml
so
now
kctrl
will
create
a
secret
and
update
its
reference
in
the
package
install
itself
and
then
wait
for
it
to
reconcile.
C
So
I
don't
think
I'll
be
doing
that
right
now,
but
what
we
can
also
do
is
when
we
are
dealing
with
package
repos.
We
can
also
update
them
with
a
new
url,
which
leads
the
which
leads
to
new
packages
being
added.
Basically,
if,
for
instance,
we
want
to
update
to
maybe
a
newer
version
of
the
reaper
and
the
workflow
is
pretty
similar
to
what
we're
doing
over
here.
C
C
So
now,
what
I'm
gonna
do
here,
quick,
is
try
and
update
the
package
installed
to
maybe
a
new
version,
and
so,
instead
of
using
package
installed
update.
What
I'm
going
to
do
is
I'm
just
going
to
do
a
package
install
with
the
newer
version
so
that
way,
what
I'm
trying
to
show
here
is
that
the
package
install
command
is
it's
reentrant
like
if
you
try
to
install
an
already
installed
package,
it
just
switches
to
update
updating
it,
so
I'm
gonna
do
package
install
I'm
gonna
call
it
cert,
one
which
it
is
and.
C
C
E
C
So
we
wait
for
the
packet
installed
to
be
deleted.
In
the
same
way,
we
wait
for
it
to
reconcile
and
what
we
will
be
doing.
Is
we
also
clean
up
the
resources
we
created
for
the
package
installed
to
work
like
the
secret,
the
service
account
and
the
other
related
resources
there
you
go.
So
all
the
resources
that
were
created
with
it
are
cleaned
up.
C
Okay,
the
repository
is
still
reconstructing,
but
so
to
add
on
to
that.
So
for
the
future
work
that
we
have
planned
right,
we
often
find
that
let's
have
a
package
repository
or
if
a
package
install
is
failing.
Users
are
sort
of.
The
first
instinct
is
to
look
at
the
package
install
resource
and
the
package
repository
resource,
and
it
does
not
surface
enough
information.
G
Yeah,
I
think
I
think
it's
going
to
be
very
obvious
when
we
have
that
feature,
what
we
actually,
what
we
actually
want
to
surface
or
what
the
people
want
to
actually
or
want
to
see
right
it.
It's
you
can
always
compare
it
to
like
the
stuff
that
you
see
in
cap.
Deploy
right
is
useful
in
understanding
what
the
current
state
is
right
so
like
similar,
that
similar
information
popped
up
for
packaging
style,
and
even
you
know,
app
cr-related
interactions.
A
B
No
no
updates
to
the
roadmap-
I
guess
renew
since
or
summix
since
you're
y'all
are
here.
If
there's
any
additional
detail
that
you
want
to
provide
regarding
the
cap,
controller,
milestone
or
kctrl
milestone,
three
y'all
could
do
that
now,
but
I
also
know
I'm
putting
you
on
the
spot
so
feel
free
to
decline.
H
H
H
A
I
A
J
K
K
So
we
would
love
to
see
that
in
tce,
because
we
have
users
who
use
our
unmanaged
clusters,
especially
on
m1
max,
which
are
effectively
just
arm
64
linux
boxes
and
one
of
the
key
things
to
unblock
that
was
to
do
a
custom
build
of
cap
controller.
So
I
opened
up
a
pr
that
reflected
that,
but
yeah
would
be
happy
to
do.
The
work
would
probably
just
need
guidance
on
what
y'all
would
want
to
do
from
like
a
philosophical
standpoint,
because
you
know
again,
I
don't
know
your
build
systems.
K
K
K
G
G
J
K
A
All
right,
so
thanks
everyone
for
joining
today,
I
will
post
that
demo
separately,
so
folks
can
check
it
out
if
they
want
to
provide
any
more
feedback
on
that.
Please
do
so.
You
can
find
us
on
slack
and
on
twitter
if
you
have
any
comments
regarding
that.
Otherwise,
you
can
expect
that
release
in
the
next
few
days
and
we
look
forward
to
hearing
from
you
regarding
that.
Otherwise,
please
join
us
in
our
next
community
meeting.
We
meet
every
wednesday
or
every
thursday
at
10
30
a.m.
Pacific
time
with
that
have
a
great
day.