►
Description
Tanzu Community Edition Community Meeting - March 2, 2022
We meet every 1st and 3rd Wednesday at 11am Pacific Time. We'd love for you to join us live!
This week we went over what to expect with the next release, v0.11.0, engineering updates, and had a Carvel maintainer go over a ytt proposal they're seeking community feedback on. Check out full meeting notes here: https://hackmd.io/CiuO4V0AT6WL_TgA47MXBA
A
Hi
everyone
welcome
to
this
week's
edition
of
the
tce
community
meeting.
If
you
are
watching
this
from
home,
we
encourage
you
to
come
and
join
us
live.
We
have
two
options
for
you
to
choose
from
regarding
our
community
meetings,
we
meet
every
first
and
third
wednesday
of
the
month
at
2
p.m.
Eastern
time,
11
a.m.
Pacific
time,
if
you
aren't
able
to
join
that,
we
also
have
a
new
addition
to
the
community
meetings
for
our
apac
community.
A
A
Additionally,
we
do
have
office
hours
and
that's
more
of
an
open
discussion
style
where
you
can
bring
something
that
might
require
a
little
bit
more
time
that
you
need
help
with
regarding
tce,
if
you
have
something
that
you
want
to
propose
anything
like
that,
those
are
held
every
second
and
fourth
wednesday
at
2
p.m.
Eastern
time,
if
you
aren't
able
to
join
any
of
those
options,
you
can
still
reach
us
at
the
in
within
the
kubernetes
select
workspace
in
the
tanzu
community
edition
channel.
You
can
find
us
in
github
discussions.
A
So,
within
this
issue,
we
ask
that
you
provide
a
little
bit
more
information
about
your
company,
any
links
to
your
website.
What
is
your
scenario
for
using
tce
and
if
you're
comfortable,
we
would
love
to
feature
you
on
our
adopters
page,
so
go
ahead
and
add
a
png
version
of
your
logo
to
the
comment
and
we'll
get
it
added
to
the
doctor's
page.
A
A
Anything
that
you
may
need
help
with
I'm
here
for
you,
I'm
here
to
support
the
community
and
I'm
really
excited
to
participate
in
this
way.
So
please
feel
free
to
reach
out
to
me
drop
me
a
line
in
slack
I'd
love
to
hear
from
you,
as
I
mentioned
before,
we
are
going
to
be
starting
our
apac
community
meeting
next
week
march,
9th
at
9
a.m
and
being
standard
time
and
we're
going
to
be
holding
those
every
second
thursday
of
the
month.
A
On
to
status
updates,
first
off
we
have
our
pm
updates
for
0.11
we're
focusing
on
interop
interoperability
with
tons
of
mission
control,
which
is
tmc.
So
if
you
hear
us
talking
tmc,
we
use
a
lot
of
acronyms
that
stands
for
tons
of
mission
control
and
it'll
provide
new
developer
experience
capabilities.
B
I
can
I
can
talk
about
that
a
little
bit
hi,
I'm
eddie
danelle
for
folks
who
don't
know
me.
I
am
one
of
the
product
managers
over
here
at
vmware,
and
so
the
there's
a
couple
of
things
that
we're
doing
here.
One
of
them
kartik,
is
actually
going
to
talk
about
much
more
extensively.
The
with
the
cartographer
stuff
and
the
app
platform,
meta
package
and
so
forth,
but
tons
of
mission
control
or
tmc
is
like.
B
This
is
one
of
the
things
that
we're
trying
to
drop
into
0.11
a
couple
of
things
to
note
about
0.11,
it's
going
to
be
a
relatively
small
update
because
it
is
coming
as
fast
on
the
heels
of
0.10,
as
we
actually
want
our
updates
to
come,
as
opposed
to
the
gap
that
we
had
in
in
prior
releases.
So
like
we're,
we're
trying
to
move
a
little
bit
quicker
with
this.
B
So
it
provides
policy.
It
provides
a
central
management
plane,
both
cli
ui
api,
to
be
able
to
interact
with
a
whole
bunch
of
kubernetes
coming
from
a
whole
bunch
of
different
places,
and
it
is
kind
of
the
core
of
you
know.
What
what
vmware's
kubernetes
strategy
dovetails
into
is
is
around
that
that
product.
A
C
Yeah
absolutely-
and
I
think
I
think
scott
has
a
common
slash
question,
so
maybe
we
can
address
that
from
a
developer
experience
phase
one
I
think
we
have
been,
I
think,
first
of
all,
I'm
karthik.
I
think
I've
been
around
enough.
That
hopefully
folks
know
me
by
now,
but
if
not,
I
think
I'm
a
pm
focused
on
the
open
source
strategy
of
the
tanzania
application
platform,
which
is
our
commercial
product
and
obviously
focused
on
bringing
all
of
that
goodie
goodness
to
tce.
C
We
had
kpac
come
in
to
tce
in
the
previous
release
and
in
this
one
we're
working
on
bringing
cartographer
into
tce.
If
y'all
don't
know
what
cartographer
is
cryptographer
is
a
new
vmware
originated
open
source
project
that
makes
it
easy
for
users
to
choreograph
or
choreograph
their
supply
chains,
aka
their
path
to
production
into
a
into
a
set
of
steps
that
they
can
use
various
technologies
for
so
it's
really
powerful.
I
really
recommend
folks
checking
that
out.
C
The
other
thing
that
we
are
planning
planning
slash
trying
to
bring
in
the
v11
release
is
the
what
is
known
as
app
platform
meta
package.
Disclaimer,
our
platform
is
a.
He
is,
the
name
is
still
tbd
that
might
change
so
just
want
to
give
you
a
heads
up
on
that.
The
links
are
there
for
the
proposals,
but
this
is
sort
of
the
first
package
of
packages
that
will
bring
a
lot
of
the
the
application
platform
capabilities
together,
make
it
so
it
does
both
things
right.
C
A
D
D
So
recently,
we've
had
some
big
prs
merge
and
I
guess
really
what
unmanaged
cluster
is
for
those
that
are
unaware
is
it's
our
lightweight
way
to
kind
of
tamsuify
some
cluster
locally
on
your
workstation
right
now
that
defaults
to
kind
which
is
kubernetes
in
docker
and
one
big
feature
that's
coming
now
is
multi-node
clusters,
which
is
supported
by
docker.
So
this
is
useful
for
people
who
want
to
test
multi-node
configurations,
multiple
workers,
multiple
control
planes
and
now
that
works
with
unmanaged
cluster.
D
We
also
had
lagged
just
a
little
bit
with
our
package
repository,
so
that
is
now
updated
and
will
also
be
updated
to
the
new
v11
or-
I
guess
v011
excuse
me
package
repository
if
you
weren't
able
to
get
onto
or
if
you're
lagging
a
little
bit
behind
and
you're.
Still
on
the
v09.1
package
repository,
you
can
use
the
tanzu
package
repository
update
command
to
still
get
the
newest
one,
but
yeah
that
will
be
coming
by
default
in
the
next
release.
D
Also
coming
is
exit
codes,
which
will
be
really
useful
for
automation.
An
exit
code
is
really
just
a
way
for
a
process
to
communicate
what
happened
to
the
higher
level
process.
So
if
something
went
wrong,
we
can
return
a
certain
exit
code
and
tell
the
automation
or
your
cic
pipeline
or
something
maybe
they
can
try
to
recover.
D
The
diagnostic
plugin
now
also
supports
unmanaged
cluster
and
I
just
dropped
a
pr
for
passing
in
a
config
for
the
kind
provider
which
will
actually
cover
quite
a
bit
of
future.
Requests
from
people
like
jorge,
has
had
a
bunch
of
these
requests
about.
You
know
attaching
to
a
different
interface
or
different
port
mappings
and
things,
and
that
will
all
now
be
supported
by
just
passing
in
a
kind
configuration
for
the
kind
provider.
D
E
E
The
deliverable
would
in
essence
be
a
set
of
executables
for
windows-
mac,
perhaps
linux,
to
assist
with
installing
the
the
the
tonzo,
cli
and
plugins,
ensuring
that
everything
is
up
and
running.
There's
been
a
lot
of
feedback
that
there
is
is
friction
in
that
area
for
customers,
so
so
looking
to
have
like
a
msi
style
installer
to
to
assist
users
with
that
process,
and
the
other
proposal
is
around
a
guided
ui
experience
that
would
essentially
contain
a
simplified
set
of
workflows.
E
F
F
E
G
No,
no,
the
more
you
can
put
in
there
the
better,
because
otherwise
this
is
steve.
I
don't
know
where
to
give
feedback
and
that
it's
really
sparse
in
there
right
now
like
I
gave
I
don't
know,
should
I
re-put
my
figma
thing
back
in
there
about
my
what
I
would
like
to
see
and
like
it's
just
there's
no
context
for
what
you're
asking
for
and
there's
no
way
to
give
for
right
now.
It
feels
like
there's
no
way
to
give
constructive
feedback.
G
C
E
E
I
Yeah,
so
if
you've
seen
in
any
of
like
the
roadmap
or
anything
coming
up,
a
cartographer
is
going
to
become
a
package
in
tons
of
communication.
This
video
doesn't
specifically
use
to
haunted
community
edition,
but
it's
a
very
like
in-depth.
It's
like
about
three
hours
actually
about
cartographers.
So
if
you
want
to
look
in
that
into
that
before,
if
you
aren't
familiar
with
cartographer
before
it
becomes
a
package
there's
that
and
a
few
weeks
ago,
scott
did
a
video
on
tonsi
tuesday's.
I
I
So
yeah,
if
and
for
anyone
wanting
to
see
more
intensity
communication
stuff,
if
you
look
on
top
zooda
tv
under
search,
you
could
search
for
tonsi
communication
or
you
could
click
on.
If
you
scroll
down
on
this
page
and
click
on
scott's
profile,
it
should
show
ideally
all
the
yeah,
all
the
videos
that
scott's
done
that
have
something
to
do
with
tattoo
community
edition.
A
A
Okay,
so
discussion
topics
we
have
one
of
my
favorite
humans,
john
ryan,
he's
a
maintainer
of
carvel.
So
for
those
of
you
don't
know,
I
also
am
a
community
manager
for
carvel
and,
seeing
as
how
I
intertwined
carville
and
tcer,
we
thought
it'd
be
a
great
way
to
present
this
proposal
to
the
tce
community
and
gather
feedback
from
y'all.
So
I
will
would
it
be
helpful,
john
for
you
to
share
your
screen.
J
Yeah,
I
gotta
say
I'm
super
nervous,
but
not
for
the
reason
you
might
think
I've
really
got
into
tick
tock
like
in
the
last
year
and
one
of
my
favorite
tick
tock
creators
is
here,
so
I'm
really
hoping
to
make
a
good
impression
on
john
mcbride,
with
our
first
in-person
interaction.
Why
do
you
have
to
have
me
like
that?
Right?
J
I
just
wanted
to
come
over
and
say
hey
to
folks
and
give
a
little
bit
of
error
to
something
that
we're
doing
that,
I
think
is
going
to
be
I'm
hoping
that's
going
to
be
helpful
and
valuable
to
all
tools
that
are
integrating
with
karbol,
and
this
is
a
a
feature
where
we're
adding
validations
to
initially
like
data
values,
but
ultimately
to
kind
of
anything
you
do
in
yaml,
so
really
quickly.
For
folks
that
may
not
be
familiar.
J
We're
actually
working
on
healing
integration
as
well,
but
ytt
is
the
templating
tool
that
we're
providing.
So
let
me
just
kind
of
jump
into
it,
real,
quick,
let
me
find
the
so
so
this
so
the
link.
That's
there
has
the
actual
proposal
and
we're
doing
that
thing
where
we
were
talking
about
how
to
get
feedback
on
proposals.
So
we
have
a
pr
with
a
proposal
in
it,
and
so
you
can
have
conversations
and
make
updates
and
respond
to
stuff.
J
J
J
So,
like
an
example
here
would
be,
this
is
a
really
common
one.
So,
where
you
have
some
configuration
value,
this
is
this.
So
let
me
orient
here
so
like
inside
this
piece
of
yaml.
This
is
defining
a
bunch
of
variables.
We
call
them
data
values
and
ytt
in
its
the
way
it
does
schema
actually
infers
as
much
as
it
can
from
the
structure.
J
J
I
used
as
an
example
actually
a
bunch
of
code
out
of
tce
or
some
of
the
add-ons.
So
here's
one
for
harbor
and
here's
what
we're
talking
about
there's
there.
You
can
write
your
own
validations
today,
and
teams
have
had
to
do
that
and
what
we're
hoping
to
do
is
actually
provide
enough
out-of-the-box
functionality
that
we
can
absorb
a
good
chunk
of
that,
so
that
you
don't
have
to
write
and
maintain
that
code,
we'll
just
handle
that
for
you
with
declarative
rules.
J
But
if
you
need
to
downshift
into
including
code,
then
you
can
so
here's
one
for
harbor,
the
harbor
add-on.
It's
an
example
of
it's
a
complete
example.
As
far
as
we
know
of
like,
for
example,
here,
if
you
want
to
constrain
what
values
are
allowed
in
log
level,
you
can
set
up
an
enumeration
just
using
the
one
of
rule.
J
J
J
We've
had
a
bunch
of
conversation
going
on
already
would
love
to
hear
anything
that
you
would
want
to
react
to
to
this
big
or
small,
something
you
think
that
should
be
there
that
isn't
there
something
that
feels
weird
or
or
not
the
way
that
you
would
expect
it.
You
can
jump
into
the
pr
and
just
start
commenting.
You
just
come
over
to
our
channel,
we're
in
the
kubernetes
slack
as
well
at
parent
carvel
yeah.
F
Here
that
is,
this
is
great
to
see
this
coming
because
as
a
package
author
that
I've
been
creating,
this
I've
been
suffering
with
with
the
misinvalidations
and
having
to
do
assertions
and
stuff
like
that.
So
obviously
this
is
great
stuff
and
we
will
test
it
thoroughly
and
give
feedback,
and
then
the
other
thing
is
that
I
find
great
that
for
one
time
like
somebody
from
prairie
that
we
use
in
this
case,
cargo
comes
to
the
transit
community
division
to
just
ask
for
feedback
about
what
they
are
doing
and
that
impacts
us
directly.
J
Yeah-
and
this
is
early
enough
yeah
thank
you
jorge
and
I'm
looking
forward
to
your
feedback.
You
always
give
pointed
meaningful
and
and
and
you're
advocating
for
users.
I
love
it
yeah.
This
is
early
enough.
You
can
really
shape
how
how
this
would
work
so
yeah,
looking
forward
to
making
sure
that
this
fits
your
needs.
That's
the
point.
G
Currently,
if
you
do
unmanage
it
uses
entreya
by
default
and
kind
does
not
like
or
andrea,
does
not
like
kind,
and
so
you
end
up
with
these
clusters
that
cannot
restart
I
put
in
a
pr
to
ask:
can
we
just
for
now,
until
we
figure
this
thing
out
with
andrea?
Can
we
please
just
use
calico
by
default,
because
it's
giving
us
the
expected
behavior
john,
has
already
done
the
pr
for
it
and
we're
kind
of
stuck
waiting
for
someone
to
say?
G
Yes,
we
approve
of
this
change
for
the
default,
so
I'm
raising
the
village
ability
issue
of
this,
because
I
think
this
is
a
high
impact
thing.
We've
got
tons
of
feedback
about
how
people
keep
them.
Like
writing.
Questions
like
I
started
my
machine
again
and
I
can't
connect
to
my
cluster.
What's
wrong
right
and
doc
could
fix
it,
but
I
think
we
should
actually
just
give
the
people
what
they
expect
and
there's
an
easy
way
to
do
that
and
then
swap
it
once
we
entreya
and
kind
play
nicely
together.
G
A
Awesome
thanks
steven
and
thanks
john
for
presenting
that
to
the
community
here
again,
if
you
have
any
feedback
regarding
that
proposal,
we
would
love
to
hear
from
you
just
follow
that
link
in
the
in
the
hack,
md,
there's
a
video
that
he's
done.
That
covers
all
the
basics,
and
you
know
if
you
have
any
feedback,
please
drop
us
a
line
there.
A
A
We
would
love
for
you
to
engage
with
us
here,
so
we
meet
every
first
and
third
thursday
or
sorry,
first,
every
first
and
third
wednesday
of
the
month
for
the
community
meetings
and
every
second
and
fourth
wednesday
for
office
hours
as
well
as
for
apac
folks,
we
meet
every
second
thursday
of
the
month,
so
check
out
the
times
for
all
of
those,
hopefully
there's
something
that
fits
your
schedule
and
you
can
come
join
us
otherwise,
you'll
find
us
on
slack
github
email.
All
of
the
above.