►
From YouTube: Carvel Community Meeting - June 30, 2022
Description
Carvel Community Meeting - June 30, 2022
This week we announced two new blog posts from the team, vendir v0.28.0 release, discussed updates to the community meeting cadence, and what the team's been working on. Full details here: https://hackmd.io/F7g3RT2hR3OcIh-Iznk2hw#June-30-2022-Agenda
A
Hi
everyone
welcome
to
this
week's
edition
of
the
karvel
community
meeting.
Today's
date
is
june.
30Th
2022..
If
you
are
watching
this
as
a
recording
from
home,
we
encourage
you
to
come.
Join
us
live
we
meet
every
thursday
at
10
30
a.m.
Pacific
time
it's
a
good
opportunity
for
you
to
come
and
meet
the
maintainers.
A
A
A
If
you're
unable
to
meet
us
live-
and
you
still
want
to
reach
out
to
us,
there
are
other
ways
to
do
so.
You
can
find
us
in
the
cargo
channel
and
the
kubernetes
kubernetes
slack
workspace.
You
can
email
us
in
our
google
groups.
You
can
find
us
in
github
within
any
of
our
project
repos
and
you
can
find
us
on
twitter
at
karbal
underscore
dev
at
any
point
that
you
are
interacting
with
us
or
any
other
members
of
the
community.
A
And
for
those
that
are
using
the
carnival
tools,
just
a
reminder,
we
do
have
this
pinned
issue
here
that
we
would
love
for
you
to
add
a
comment
to
outlining
your
use
case
of
any
of
the
carnival
tools
that
you're
using.
We
just
want
to
know
more
details
about
how
others
are
using
the
tools.
It
helps
us
plan
for
the
development
of
the
tools
and
also
helps
the
community
understand
further
on
how
others
are
using
it
and
how
they
may
be
able
to
use
them
as
well.
A
So
we
would
really
appreciate
if
you
submitted
a
comment
here
and
if
you
wanted
to
be
added
to
the
adapter's
file.
You
can
add
your
logo
to
that
comment
as
well
and
we'll
get
it
added
for
you
and
if
you
have
any
questions
regarding
that,
please
don't
hesitate
to
reach
out
and
then
a
quick
reminder.
Just
attendees.
Please
make
sure
to
add
your
name
to
the
attendees
list
here
and
it's
totally
optional.
But
we
appreciate,
if
you
do
so
so
that
we
know
who
all
is
attending
these
meetings.
A
Yeah
we
already
had
our
our
goodbyes,
but
yeah
and
it'll
be
sad
but
yeah.
Moving
on
to
content,
we
have
a
couple
of
blog
posts
this
week,
we've
kind
of
missed
out
on
a
couple
of
weeks.
Previously,
just
you
know,
it's
been
a
busy
week
for
us,
but
now
we're
we're
pumping
them
out.
We
got
two
blog
posts
posted
converting
concourse
pipeline
to
ytt
by
neil
hickey.
C
So
it
seemed
like
a
perfect
fit
to
try
to
have
ytt
come
and
dry
up
some
of
that
stuff.
So
this
is
a
like
tutorial,
slash
walkthrough,
of
taking
an
example
pipeline
from
the
concourse
team
and
going
through,
and
just
I
guess,
describing
how
I
would
start
off
with
pulling
things
out
into
smaller
functional
parts
and
reusable
yeah
and
like
making
it
reusable
more
maintainable.
A
D
A
Okay
and
as
far
as
content
goes
for
next
week,
we
don't
have
anything
posted
or
in
the
in
the
works
for
next
week.
But
if
you
have
anything
that
you
want
to
bring
up
as
a
community,
you
want
to
share
any
knowledge
you
have
and
how
you're
using
karvel
or
anything
like
that.
We
would
love
for
you
to
share
that
with
us,
so
be
sure
to
reach
out
to
us,
and
let
us
know
what
you
want
to
share
and
we
can
get
it
posted
for
you.
A
E
E
If
you
were
trying
to
vendor
sync
using
hg,
and
your
term
info
was
misconfigured,
it
would
fail
now
that
continue
that
works
again
as
far
as
features
one
that
stands
out
is
if
you're
pulling
you're
syncing
a
git
repo
and
that
git
reaper
has
a
bunch
of
sub
modules.
You
can
now
configure
it
so
that
you
can
ignore.
E
B
B
I
and
get
give
us
feedback
and
then
also
garrett's,
been
working
on
kind
of
one
of
the
the
last
of
those
validation
rules
that
are
sort
of
outside,
of
like
the
core
set,
but
ones
that
are
now
productivity
enhancements
and
that's
what
692
is
there
outside
of
working
on
the
validation
stuff?
We've
had
a
number
of
improvements.
A
key
here
is
group,
came
in
who's,
been
doing
some
robotics
and
they
were
using
ytt
and
they
wanted
to
do
some
floating
point
map.
B
They
want
to
do
some
trig
and
some
other
stuff
and
that's
available
in
starlark
in
the
in
the
core
libraries,
but
not
not
in
the
in
the
base
implementation
you
get
when
you
integrate
with
it.
So
they
pointed
that
over
for
us,
we've
had
that
in
set
up
and
integrated
the
way
that
floating
point
math
generally
works.
You
can't
really
guarantee
bitwise.
B
I
identical
results
across
architectures,
so
it's
a
little
warning.
If
you
use
one
of
those
things
not
to
worry
just
a
reminder
that
it
can't
necessarily
be
deterministic
across
cpus,
but
you
should
get
the
same
result
with
the
on
on
the
same
machine,
but
a
little
reminder
will
be
there
just
to
make
sure
you're
not
surprised
but
yeah.
Thanks
to
to
the
folks
that
I
don't
have
a
name
there.
Hugo
31
is
the
github
handle.
It
sounds
like
it
was
a
crew
there
so
appreciate
that.
Thank
you
for
the
contribution.
A
C
C
One
happy
side
effect
is
that
tce,
which
is
the
tanzu
community
edition,
who
basically
was
doing
something
similar?
They
had
their
own
package
cr
for
secret
gen.
They
will
now
be
able
to
use
this
instead,
so
they'll
be
able
to
be
able
to
keep
up
and
be
in
parity
with
us
much
quicker
than
before,
where
I
think
it
was
somewhat
unmaintained,
so
benefits
us
community
and
in
the
tensor
community
edition
folks.
So.
F
And
here
comes
the
most
exciting
update
of
the
day
image
package,
so
three
things
have
been
happening
on
image
package
we've
been
working
a
little
bit
on
the
ux.
There
were
some
issues
that
community
reported
and
we're
working
through
them
and
to
make
our
ux
a
little
bit
better.
The
other
thing
is
related
to
dependencies.
F
That's
that's
going
to
be
pretty
good,
it's
still
in
pr,
but
I
hope
that
we
can
get
it
merged
in
the
next
couple
of
weeks.
This
comes
with
like
an
interesting
effect.
That
is,
we
we
had
some.
We
heard
some
people
complaining
about
about
using
openshift
in
gcr,
like
openshift,
has
a
very
strict
policy
that
closes
some
ports
and
some
routes
when
that
is
in
the
strict
mode
and
image
package
was
not
able
to
to
authenticate
to
to
gcr
the
google
container
registry.
F
A
A
A
B
Yeah,
I
think
this
is
a
pro
to
decrease
the
frequency,
because
I
think
you're
right,
and
so
what
happens
is
if
we
can
kind
of
bunch
up
the
updates,
then
it's
it's
more
signal
for
your
time.
It's
more
information
for
your
time,
instead
of
some
more
incremental
updates,
I
think
they'll
make
them
more
interesting
to
participate
in
so
yeah.
I
think
this
is
a
smart
move.
B
F
A
A
F
That's
a
question
like
I'd
like
to
understand:
if
we're
still
happy
with
this
time
for
the
meeting
or
if
we
want
to
jiggle
it
around
just
asking,
because
there
might
be
other
other
meetings
that
I
might
attend.
If
this
isn't
it
wasn't
in
a
different
time,
so
just
make
sure
that
everybody
everybody's
still
happy
here.
A
B
Seems
like
that,
I
don't
know
how
what
folks
sort
of
lifestyles
are,
but
the
difference
there
in
ist
in
indian
standard
time
is
right.
Now
it
is
midnight
and
at
9
a.m.
It
would
be,
I
think,
that's
9
30.,
like
that's
a
pretty
significant
difference
there
in
terms
of
like
how
I'll
let
you
stay
up
to
be
able
to
participate
in
this.
If
you
just
happen
to
be
in
india,.
B
So
if
we
can
find
a
way
of
replicating
that
last
minute
urgency
as
a
stop
gap,
ideally
before,
then,
then
we
wouldn't
suffer
from
the
folks
who
are
in
pacific
time
kind
of
rubbing
our
eyes
as
we
get
up
to
jump
on
the
call
for
community
meeting.
So
I
just
want
to
call
that
out
as
like
something
I
wouldn't
want
to
lose,
but
I'm
pretty
bullish
about
the
possibility
of
this
being
a
more
reasonable
time
for
our
teammates
in
india.
A
Yeah,
I
agree
something
that
aaron
and
I-
and
we
were
talking
about
yesterday-
about
how
to
have
a
more
like
a
better
earlier
process
of
getting
information
and
making
sure
we
have
stuff
to
talk
about
and
all
that
maybe
starting
like
with
the
standups
on
monday
or
ipms
on
monday
and
just
me
trying
to
catch
end
of
things
that
are
being
talked
about.
That
may
other
others
might
be
missing,
and
I
can
catch
that
and
be
like
that's
something.