►
From YouTube: Carvel Community Meeting - September 2, 2021
Description
Carvel Community Meeting - September 2, 2021
We meet every Thursday at 10:30am PT. We'd love for you to join us live!
Full details on this week's meeting can be found here: https://hackmd.io/F7g3RT2hR3OcIh-Iznk2hw?view#September-2-2021-Agenda
A
Hi
everyone
welcome
to
this
week's
edition
of
the
carville
community
meeting.
Today's
date
is
september,
2nd
2021,
just
a
reminder
that
these
meetings
are
being
recorded
and
uploaded
to
our
youtube
playlist.
So
when
you're
attending
these
meetings,
we
ask
that
you
please
read
and
abide
by
our
code
of
conduct
which
is
listed
out
here
in
the
agenda.
A
If
you're
watching
this
from
home,
we
encourage
you
to
come
and
join
us
live
we
meet
every
thursday
at
10,
30
a.m,
pacific
time
and
that's
just
an
opportunity
for
you
to
come.
Listen
in
on
what
the
team
is
working
on,
provide
any
feedback
for
any
of
the
tools
you
may
have
or
ask
any
questions
that
you
may
need
help
with
regarding
the
tools
themselves
and
we
welcome
any
engagement
whatsoever
if
you
want
to
just
listen
in
that's
totally
fine
as
well.
A
B
So
the
the
way
that
this
will
essentially
work
is
that
cap
controller
will
be
able
to
integrate
with
secret
gen
controller
when
they
are
both
installed.
On
the
same
cluster
cap
controller
will
be
able
to
create
placeholder
secrets
that
are
then
populated
by
secret
gen
controller
as
a
way
of
more
easily,
basically
sharing
secrets
across
a
cluster
and
as
a
way
of
supporting,
actually
authenticating
to
underlying
registries
that
require
authentication.
A
B
B
B
C
Oh
yeah,
so,
the
week
before
last,
we
talked
about
the
proposal
for
this
work
for
ytt
in
the
community
meeting,
and
the
proposal
has
now
been
accepted.
It's
still
open
in
a
pr.
If
you
go
to
the
cargo
repo,
I
think
it's
193.
so
feel
free
to
continue
to
leave
comments
on
that.
If
you
have
any,
but
we
have
actually
kicked
off
the
work
this
week.
A
D
Yep
so
this
week
we
actually
work
towards
like
showing
the
application
warnings
when
users
are
using
that
resources
that
are
going
to
be
deprecated
and
be
unavailable
in
next
versions
and
other
than
that.
We
are
working
towards
ordering
resources
in
a
more
granular
manner
and
that's
still
work
under
progress,
and
we
hope
to
have
a
poc
on
that
soon.
D
Like,
for
example,
let's
say
there
are
three
namespace
resources
with
different
namespaces.
How
it
worked
so
far
was
that
three
of
them
will
wait
for
all
the
namespaces
to
be
created,
and
what
we
are
trying
to
do
right
now
is
like
each
resource
just
waits
for
it,
its
own
name
space,
and
there
are
a
few
other
examples
like
this,
which
we
think
will
improve
the
ordering
significantly
and
other
than
that.
D
We
also
worked
on
retrying
some
errors,
which
were
sometimes
caused
by
like
improper
network
configurations
on
the
host
or
hcd
errors,
and
which
basically
caused
app
cap
to
error
out
when
it
shouldn't.
So
we
just
started
retrying
these
errors,
so
they're
like
minor
enhancements
and
we
are
working
towards
having
more
like
consolidated
milestones.
That's
all
from.
D
A
E
Hey
nancy:
there's
a
couple:
I'm
not
sure
how
to
point
at
them
in
in
the
the
backlog,
but
just
some
notes:
real
quick!
So
there's
a
little
bit
of
cables
getting
a
little
bit
of
love
this
last
week
there
there's
an
improvement
around
how
we're
managing
metadata
garrett.
Do
you
think
you
can
elaborate
on
on
that
one
in
a
second
and
then
the
the
other
pieces?
E
Were
we
just
got
a
contribution
for
integrating?
I
think
it.
I
can't.
I
don't
know
if
it's
pronounced
bazel
or
basil,
it's
a
the
build
system
as
a
builder
for
cable,
which
is
great,
it's
like
yet
yet
another
option
for
you
to
be
able
to
configure
and
orchestrate
your
builds
to
that.
That
should
be
landing
very
soon,
so
garrett
on
the
the
metadata
stuff.
What
what's
that
about.
F
G
G
You
know
talk
to
the
gcr
to
the
google's
registry
without
having
to
do
any
additional
configuration
or
setting
environment
variables.
It
just
knows
it's
running
on
a
gcp
vm
and
does
all
the
right
calls
to
get
the
credentials
it's
in
draft,
it's
going
through
a
review.
Now
it
just
needs
some
additional
manual
testing.
A
H
No,
I
don't
think
so.
I
just
say
I
guess
I
was
talking
with
dennis
a
couple
weeks
ago
and
he
gave
me
a
good
first
issue,
actually
an
image
package
to
pick
up,
so
I
started
looking
looking
into
that
and
came
across
a
couple
of
typos
and
some
bad
grammar,
so
I
put
in
a
couple
of
pr's
for
those
I
hope.
That's
okay,.
G
It's
more
than
okay,
it's
appreciated,
I
definitely
merged
one
of
them,
the
other
pr.
I
have
to
look
into
it,
but
it
looked.
There
was
a
bit
maybe
a
bit
of
overlap
but
duplication,
but
like
it
could
just
be.
I
just
didn't
glance
I
didn't
dig
into
it
enough,
but
definitely
planning
on
reviewing
it
emerging
at
the
second
one
as
well.
Okay,.