►
From YouTube: Carvel Community Meeting - June 14, 2021
Description
Carvel Community Meeting - June 14, 2021
We meet every Monday at 11:30am PT / 2:30pm ET. We'd love for you to join us live!
This week we discuss open roles on the team, usability testing, some backlogged bugs to be worked on, and more - check out all the notes:
https://hackmd.io/F7g3RT2hR3OcIh-Iznk2hw?view#June-14-2021-Agenda
A
Hi
everyone
welcome
to
this
week's
edition
of
carville
community
meeting.
Today's
date
is
june.
14Th
2021
just
a
reminder
that
these
meetings
are
being
recorded
and
uploaded
to
our
youtube
playlist,
and
we
ask
that
everyone
that
attends
reads
by
and
abides
by,
our
code
of
conduct
as
well
as
puts
in
their
name
and
the
organization
that
they
represent.
If
there
is
one
if
you're
independent.
We
also
would
like
to
know
that
this
lets
us
keep
track
of
who's
attending.
A
So
we
can
keep
the
lines
of
communication
open
with
those
that
do
attend
our
community
meetings
for
anything
that
we
may
not
get
to
today
or
if
there's
anything,
that's
more
than
just
me.
More
in-depth
work
on.
We
do
have
office
hours
that
are
every
second
and
fourth
thursday
of
the
month,
starting
at
11,
30
a.m,
pacific
time
or
2
30
p.m.
Eastern
time,
so
we
invite
you
to
attend
those
or
the
community
meetings
and
we
meet
every
monday
for
the
community
meetings
at
that
same
time,
11
30
a.m,
pacific
time.
A
Moving
on
to
announcements,
we
are
hiring
for
three
different
roles.
We
have
the
engineering
role,
we
have
a
return
ship
with
which
is
internship-like
it's
based
on
for
those
that
may
have
had
a
leave
of
absence
for
caring
for
others.
You
know
maybe
have
been
out
of
work
for
that,
while
they're
taking
care
of
someone
with
their
family
members.
This.
This
is
an
opportunity
to
to
join
the
team,
join
the
carville
team
here
for
what
we
call
a
return
ship.
A
A
C
Yeah,
so
I
can
cover
it
a
couple
of
bug
fixes.
Essentially,
when
you
did
an
image
package,
push
across
different
os's.
C
It
would
cause
issues
when
copying
and
and
there's
another
kind
of
edge
case
around
that,
but
they've
both
been
fixed.
B
B
All
right,
let's
see,
status
updates,
starting
with
ytt
schemas
looks
like
I
did
not
finish.
Writing
a
sentence
here,
but
schemas
is
currently
in
the
usability
testing
phase
as
well
as
I
guess,
general
ux
improvements
and
bug
squashing.
Anything
else
that
that
folks
want
to
share
here.
D
Yeah
that
that
is
the
rest
of
that
sentence.
We
we
are.
We
are
a
very
excited
about
trying
to
incorporate
folks
feedback,
we're
actively
soliciting
today,
starting
starting
this
week,
for
anyone
who
is
interested
in
helping
us
kick
the
tires
on
this
feature,
getting
us
to
generally
accepted
state
and
really
the
best
way
for
that
to
work
out
for
us
is
for
someone
else
outside
of
the
team,
because
we're
so
close
to
the
the
problem
in
solution
to
sit
down
and
and
work
with
the
tool.
D
While
we
have
the
camera
rolling
while
we're
a
fly
on
the
wall.
So
anyway,
if
you're
interested
go
check
out
in
our
channel,
you'll
you'll
see
a
solicitation
from
me
on
a
daily
basis.
Asking
folks
if
they're
interested
love
to
have
you
we're
very
friendly,
we
don't
bite
it's
a
lot
of
fun.
It's
just
a
chance
to
sit
down
together
and
and
play
with
some
technology
and
and
help
us
get
some
feedback
on
how
usable
it
is,
and
so
we
can
address
those
gaps
before
we
generally
make
it
available.
D
B
E
There's
also
now
documentation
around
schemas.
So
if
you've
been
wondering
what
this
schema
thing
is
that
we've
been
talking
about,
feel
free
to
check
those
out
in
our
cargo.dev
site
and
yeah.
Take
that
for
a
while.
B
F
No,
it's
a
release
that
has
quite
a
few
breaking
changes,
so
be
on
the
lookout
if
you're
upgrading
to
it.
But
hopefully
this
is
the
last
set
of
braking
changes
and
everything
will
be
stable
from
now
on,
but
just
working
through
some
docks
to
help
capture,
what's
changed
and
update
the
examples
and
then
we'll
share
it
more
publicly
or
widely.
B
Cool
and
to
clarify
there,
breaking
changes
in
the
sense
of
our
alpha
releases
were
pretty
disruptive
in
the
sense
of
we
didn't
make
any
promises
around
competitive
backwards
compatibility.
So
we
also
took
advantage
of
that
by
introducing
quick
changes.
B
B
I
would
say
we
have
some
general
enhancements
or
bug
fixes
that
are
going
on,
then,
is
anything
you
want
to
share
there.
C
Not
really
it's
still
in
progress,
I
have
a
proof
of
concept
just
chipping
away
at
it.
B
And
let's
see
we
have
a
couple
bugs
in
here:
are
these
ones
you
want
to
discuss
today,
john.
D
Yeah
we
should
take
a
peek
at
these
and
again
as
we're
identifying
potential
issues.
We're
gonna,
try
and
take
a
run
at
these
if
they're
things
that
are
either
are
blocking
or
easy
to
do,
we'll,
try
and
nail
those.
Otherwise
they
might
be
things
that
we'll
identify
as
as
a
known
issue
as
we
go
into
this
discussion
of
these
things.
So
just
a
heads
up,
but
yes,
so
we've
we've
talked
about
the
the
first
two
items.
D
This
bug
here,
nested
array
in
schema,
has
a
default
value,
so
appreciate
the
very
thorough,
yet
succinct
capture
kerry
did
on
this
one.
Thank
you.
D
The
essence
of
this
is
that,
if
you're,
including
a
map
that
has
a
map
that
has
an
array
you'll,
actually
get
the
the
the
example
value
of
the
array.
D
Instead
of
it
being
defaulted,
so
here
we
expect
that
the
id
of
the
zeroth
element
of
the
resources
wow.
Let
me
say
that
again
so
within
within
the
array-
that
is
the
resources
in
this
element-
we're
expecting
that
the
source
key
has
an
id,
that's
an
empty
list
in
the
definition
of
this
in,
in
the
schema,
we're
just
giving
a
a
a
value
here.
Really
this
just
means
it's
a
string,
because
the
default
value
for
a
an
array
is
an
empty
list.
E
Yeah,
just
to
add
what
john
said
is,
we
are
essentially
filling
in
like
the
sub
items,
so
this
only
happens
when
you
have
a
nested
or
an
array
nested
in
a
map
item.
E
So
there's
very
specific
scenarios
where
this
happens.
It
doesn't
happen
for,
like
a
top
level
map
item
or
anything
like
or
top
level
every
item
or
anything
like
that.
B
Bug
do
we
want
to.
I
guess,
estimate
this
as
a
way
to
I
guess
figure
out
if
they're,
easy,
ish
or.
D
Not
I
was
the
way
I
was
thinking
about
it
was.
This
is
an
invitation
to
go
in
in
triage's
bug,
and
so,
when
you
pick
this
up,
look
to
see
what
the
possible
fix
is
and
from
there
make
that
determination.
If
that's
something
that
basically
can
get
done
within
a
day,
then
then
it's
then
let's
do
it,
if
not,
let's
circle
back
as
a
group.
B
Gotcha
cool:
it
might
be
useful
to
capture
that
context
here,
just
because
I
know
not
everyone's
here
on
the
call.
Oh,
that's,
fair!
Okay,
that
that
sounds
good.
F
D
Yep
and
here's
another
one
of
these
cases
where
you
will
where's
our
nullable.
E
C
E
D
C
E
Yeah
so
for
scenario:
two
you
can
annotate
a
node
as
schema
nullable,
which
means
that
the
node
could
be
the
type
given
in
the
schema
or
null,
and
it
is
by
default
null.
E
So
as
an
example,
if,
in
your
schema,
you
set
foo
to
null,
there's
not
any
benefit
from
annotating
it
with
nullable,
because
the
value
will
be
null
by
default
and
you're,
not
providing
an
additional
type
that
it
could
be.
D
Yeah,
that's
that's
a
great
clarification
and
then
why
any?
Well,
because,
with
any
two
reasons,
one
is
any
literally
means
any,
and
so
any
any
value
should
be
able
to
be
set
there
and
also
that
it's
actually
pretty
reasonable
default
to
say
any
when
you
know
that
a
particular
chunk
of
configuration
is
just
going
to
be
passed
through
and
you
don't
want
to
specify
what
it
is
null's
a
sort
of
a
great
value
to
represent
that.
D
I
think
we've
got
enough
horizon
for
this
week
with
those,
and
I
think
there's
one
other
bug
that
I'm
triaging
that
might
pull
in
that'll
be
the
same
kind
of
thing,
but
and
you'll
see
these.
These
things
will
sort
of
pop
in
as
we
get
feedback
from
usability
and
and
other
factors,
the
same
kind
of
bug,
triage
type
approach.
E
There's
also
a
bug
garrett
and
I
picked
up
this
morning
that
we
haven't
talked
about
it's
currently
in
progress.
I
don't
know
if
it
would
be
beneficial
to
talk
about
now,
but
I
just
want
to
make
sure
we
don't
close
over.
That's
the
very
bottom
of
the.
D
E
Sure
yeah,
so
this
is
a
regression
identified
between
release,
031
and
032.
E
Emptied
and
so
they're
not
found,
so
the
error
that
you
see
is
none
type,
has
no
dot
example
field
or
method,
because
the
data
values
for
that
library
were
wiped
out.
E
E
B
All
right,
so,
let's
see
just
taking
a
look
at
the
backlog,
then
I
think
ytt
has
plenty
of
horizon
what?
If
we
just
try
filtering
on
image
package.
B
Let's
make
this
a
little
easier
to
follow,
so
we
do
have
another
bug
in
the.
B
B
We
so
I'm
not
sure
if
anyone
here
has
like
sufficient
context
on
this
bug.
If
anyone
does
please
feel
free
to
lead
through
this
discussion,.
B
Yeah,
okay,
so
this
would
be,
I
think,
the
next
one
that
would
be
in
our
backlog
in
the
sense
of
that.
It's
currently
providing
misleading
information,
because
it's
not
actually
copying
an
image
index.
B
B
This
one
we
could
consider,
I
guess,
kind
of
investigating
the
same
way
that
we're
doing
the
ytt
bugs
I
don't
know-
maybe
at
least
like
investigating
for
a
day
or
so
would
be
enough
time
to
figure
out
how
we'd
like
to
proceed
or
what
our
options
there
will
be.
C
Yeah
that
makes
sense
for
the
bug.
I
see,
I
see
a
bug
and
then
there's
also
there's,
maybe
like
an
enhancement
which
is
when
pulling
an
image
index.
You
better
give
us
the
full
the
digest
off
the
image
you
want
in
the
image
index,
otherwise
error
out,
and
that
seems
to
be
like
an
enhancement
unless
of
a
bug
but
yeah.
Definitely
we
can
definitely
triage
for
a
day
and
see
what's
entailed
and
if
it's
way
complicated,
we
can
call
that
out.
B
B
Thoughts
all
right
cool,
so
I
know
image
package
backlog
is
a
little
thin.
We
do
have.
I
guess
some
other
bugs
have
been
filed
recently,
that
maybe
we'll
just
want
to
take
a
look
at
this
week
and
figure
out
if
or
when
we
want
to
prioritize
them.
A
Okay
sounds
good
well,
thank
you.
Everyone
for
joining
this
week's
edition
of
the
carville
community
meeting,
if
you're
watching
from
home
and
and
you
have
any
comments
that
you
wish
to
share
with
the
team.
Please
find
us
on
the
carville
channel
in
the
kubernetes
slack
workspace
or
on
twitter
at
carville
underscore
dev,
that's
dev.
A
Otherwise,
you
can
also
join
us
here
at
our
community
meetings.
We
meet
every
monday
at
11.
30
am
pacific
time.
A
We
also
have
our
carnival
office
hours,
which
are
every
second
and
fourth
thursday
of
the
month
at
11,
30
a.m,
pacific
time
and
that's
a
opportunity
for
you
to
bring
any
anything
that
you
need
more
in-depth,
helps
on
for
discussion
topics
or
something
that
you're
kind
of
lost
on
with
a
tool
suite
the
the
maintainers
are
eager
to
help.
You
navigate
all
the
different
tools
that
are
under
the
karmal
umbrella.
So
with
that,
we.