►
Description
Tanzu Community Edition Community Meeting - March 16, 2022
We meeting every 1st and 3rd Wednesday at 11am PT. We'd love for you to join us live!
This week we went over v0.11.0 updates, when to expect v0.11.0-rc2, and had a sneak peek demo on the kickstart UI. Check out full notes here: https://hackmd.io/CiuO4V0AT6WL_TgA47MXBA#March-16-2022-Community-Meeting
A
A
If
you're
watching
this
recording
from
home,
we
would
love
for
you
to
come
and
join
us
live
it's
a
great
opportunity
for
you
to
come
meet
the
team
meet
other
members
of
the
community.
You
can
bring
questions
up
that
you
might
have
about
tce
or
just
kind
of
listen
in
on
what
what
the
team
is
working
on.
A
We
have
a
few
options
for
you
to
choose
from
we
help.
We
hold
these
particular
community
meetings
every
first
and
third
wednesday
of
the
month
at
11
a.m.
Pacific
time
we
also
just
kicked
off
our
apec
monthly
community
meeting
and
those
are
held
every
second
thursday
of
the
month
at
9.
00
a.m,
india
standard
time,
and
then
we
also
have
office
hours,
which
is
a
more
open
discussion
format,
and
if
you
have
anything
that
might
require
more
lengthier
discussion,
that's
a
good
place
for
you
to
bring
up
that
topic.
A
So
we
meet
every
second
and
fourth
wednesday
at
11
a.m.
Pacific
time
for
that,
if
you
aren't
able
to
come
and
join
us,
live
there's
other
ways
to
reach
us,
so
you
can
come
and
find
us
on
the
tomdu
community
edition
channel
on
the
kubernetes
slack
workspace,
github
discussions.
You
can
add
your
request,
question
or
suggestion
in
our
issue
list.
You
can
email
us
or,
as
of
a
few
days
ago
we
just
launched
our
new
twitter
handle
at
vmware
tce,
so
go
give
us
a
follow
and
engage
with
us
there.
A
Whenever
you
do
have
a
discussion
topic,
you
want
to
bring
to
the
agenda
and
then
anyone
that's
in
this
meeting
today
if
there's
something
you
want
to
bring
up.
Please
add
that
down
below
in
the
discussion
topics
area
here
and
we'll
get
to
it
towards
the
end
of
the
meeting
at
any
point
that
you're
engaging
with
us
or
any
members
of
the
community.
A
A
For
those
of
you
using
tce,
we
would
love
to
to
know
more
about
your
usage
of
tc,
so
we
created
this
pinned
issue
here.
Please
add
any
of
all
the
comments
or
all
the
details.
We
ask
in
a
comment
here
and
if
you
would
like
to
feature
your
logo
on
the
doctor's
page,
add
the
logo
to
the
comment
in
a
png
format
and
we'll
get
it
added.
A
All
the
attendees,
please
add
your
name
and
any
company
that
you
represent
to
the
attendees
list
here
on
two
announcements
like
I
mentioned
we're
on
twitter,
so
you
can
follow
us
for
daily
news,
fun
engagements.
All
sorts
of
stuff
will
retweet
you
if
you're
working
on
tce.
If
you
have
content,
you
want
to
share
all
sorts
of
fun
stuff,
so
we're
really
excited
for
another
opportunity
to
engage
with
y'all
here.
A
C
Sure
so,
john
and
I
are
going
to
go
over.
Some
engineering
updates
feel
free
to
ask
us
questions
at
the
end.
So
to
start
off,
v011
rc2
is
on
its
way,
we're
hoping
in
the
next
couple
of
days
to
announce
that
and
our
general
availability
of
this
next
release
is
still
targeting
end
of
march.
We're
on
track
for
that.
Some
core
updates
that
you're
going
to
see
are
that
c
groups.
V2
is
solved,
so
you
will
now
be
able
to
bootstrap
clusters
with
c
groups.
D
So
then
that
will
update
to
use
whichever
ones
you
want
for
the
core
and
the
user
manage
package
repositories.
As
far
as
configuration,
there's
also
going
to
be
the
provider
configurations
you
can
set,
so
you
can
actually
give
a
kind
configuration
when
you
deploy
an
unmanaged
cluster.
The
initial
arm
support
is
also
coming
big,
shout
out
to
josh
for
getting
that
started.
D
C
Josh
quick
question:
yeah,
we'll
answer
your
questions
at
the
end,
give
me
just
a
sec
so
for
the
app
platform
side
of
things,
just
a
couple
updates
on
this
end,
I'm
mostly
speaking
for
cardik
right
now.
There
was
a
plan
for
the
app
cli
plugin
to
be
included
in
this
release.
It's
quite
unlikely.
It's
going
to
make
it.
I
put
a
link
in
chat
for
the
app
cli
plugins
github
page.
If
anybody
wants
to
check
out
what
that
is,
we'll
target
getting
that
into
v012.
C
The
application
toolkit
package
is
on
track
to
get
a
pr
in
this
week,
so
we're
hoping
to
merge
that
that
toolkit
package
brings
a
lot
of
other
packages
together
to
give
kind
of
a
cohesive,
app
platform
on
top
of
tce
and
then,
as
many
of
you
have
seen,
we've
already
merged
in
the
flux
cd
cartographer
insert
injection
web
hook
packages.
Those
will
all
be
available,
starting
in
v011
cool,
sorry
to
cut
you
off,
dude
go
ahead.
E
Cut
me
off:
what's
the
worst
thing,
that's
ever
happened
to
me.
So
could
you
just
give
us
like
a
great
those
upgrades
to
like
cap,
1v1,
beta1
and
the
upgraded
cap
controller
0.3?
Could
you
give
like
a
here's,
the
two
coolest
things
that
are
coming,
because
I
that
those
upgrades
actually
mean
nothing,
but
I'm
sure
they
actually
do
mean
something
to
the
end
users.
Could
you
just
say
like
what
are
your
two
most
things
you're
excited
about
with
them.
C
Yeah,
I
think,
as
far
as
v1
beta
1
cappy
goes.
Most
of
it
is
implementation,
details
and
plumbing
for
us.
I
don't
think
our
end.
Users
are
going
to
be
heavily
impacted
by
that,
especially
if
they're
going
through
the
tons
of
abstractions
for
cap
controller
v030,
similar
story,
there's
a
lot
of
different
things
with
package
reconciliation
that
works
under
the
hood
that
we
need
in
order
to
get
some
of
these
new
packages
out.
E
No,
I
was
actually
just
you
personally
like
why
you
were
excited
that
those
two
things
land
like
it
could
be
like
like
like
for
these
things
in
general,
when
you
guys
do
these
in
the
future,
like
the
cap.
Moving
to
this,
like
this
issue
that
we've
been
grappling
with,
goes
away.
Like
that's
exciting
to
me,
even
though
it
won't
affect
me
directly,
just
as
a
project.
C
Yeah
totally
there's
nothing
that
I'm
particularly
excited
about
with
these
two
upgrades
to
be
super
honest
with
you,
they're
largely
there
to
keep
us
up
to
date
with
the
newest
stuff,
that's
out
so
that
we're
up
to
date
with
patch
releases
security,
vulnerability
things
all
that
good
stuff
and
then
also
our
transitive
dependencies
that
we
have
oftentimes
require
some
of
these
newer
versions
because
they
tap
into
lower
level
components
that
we
expose.
So
it's
largely
to
support
those
pieces.
C
I
think
probably
the
best
thing
I
can
say
is
every
release
of
cap
controller
seems
to
do
a
better
job
of
reconciling
both
not
getting
in
deadlocks
and
doing
it
in
a
more
performant
manner.
So
that
probably
my
my
biggest
line
item
right
now,
but
largely
I
know
it's
not
that
exciting,
largely
it's
implementation,
details
for
some
of
our
dependencies.
F
So
I'm
going
to
step
you
through
a
few
one
particular
follow
with
provisioning
the
management
cluster,
but
I'm
also
going
to
point
out
a
few
things
that
are
of
interest
for,
for
you
all
and
starting
here
where
we
have
a
welcome.
Welcome
page
we're
looking
to
surface
content
that
is
relevant
for
folks
to
understand
what
is
tmz
community
edition,
along
with
documentation
and
things
just
to
get
folks
up
to
speed
as
to
what
we're
going
to
be
going
through
with
creating
clusters
and
working
with
our
workload
clusters
from
here.
F
F
F
Of
course,
this
we're
hoping
to
apply
the
same
patterns
across
things
like
vsphere
and
azure,
so
click
on
create
cluster,
and
here
is
something
that
we've
been
really
digging
into.
For.
The
new
experience
is:
how
do
we
make
the
steps
and
amount
of
inputs
that
a
user
will
need
to
provide
really
clear
and
understandable?
F
So
this
is
a
reimagined
kind
of
layout
and
information
architecture
where
we're
parsing
out
the
major
moments
in
the
installation
step.
Here
we
start
with
providing
credentials,
and
then
we
step
through
to
cluster
settings,
regions
configuration
and
a
summary
page
in
order
to
kind
of
get
a
sense
of
what
exactly
is
happening
as
you're
provisioning.
The
management
cluster
pattern,
two
that
kind
of
persists
across
all
of
these
moments
is
this
advanced
settings
which
will
enable
you
to
compute
into
more
advanced
kind
of
fields
and
selections
in
order
to
really
fine-tune
the
deployment.
F
They
can
click
on
the
advanced
settings
and
you'll
get
this
advanced
settings
area
where
you're
able
to
do
some
further
refinement
and
maybe
even
be
more
specific.
As
to
what
kinds
of
instance
types
you
want
to
provision
the
control
plane
cluster
with,
but
for
now
we're
going
to
go
back
to
our
not
advanced
settings
state.
F
F
F
Beyond
this
point,
it
gets
a
little
bit
fuzzy,
because
this
is
like
work
in
progress,
so
we're
looking
at
workflows
to
support
the
creation
of
workload
clusters
from
those
management
clusters
in
the
ui,
along
with
some
capabilities
for
viewing
the
clusters
that
you've
provisioned
already
and
the
relationships
between
the
management
cluster
to
workload
clusters
and
be
able
to
delete
and
get
contacts
and
create
additional
workload.
Questions
from
that
context,
yeah,
so
that's
kind
of
where
we
are
at
now.
F
There
is
the
github
proposal
issue,
which
kind
of
articulates
what
you
you,
what
I
just
showed
here,
but
also
we're
collecting
feedback
from
that
issue.
So
more
iterations
for
sure
over
the
next
couple
of
weeks
and
we're
very
much
looking
forward
to
hearing
you
all
kind
of
talk
about
and
get
stoked
for
this
ui
concept
that
we're
hoping
to
deliver.
A
G
H
E
Okay,
so
my
feedback
is
this
is
awesome
and
also
amazing
how
fast
you
guys
turn
this
around
like
justin.
Was
it
like
just
two
weeks
ago
that
you
were
saying
there
was
a
proposal
for
this
and
then
now,
two
weeks
later,
we
have
a
really
nice.
I
mean,
I
know
it's
not
finished,
but
it's
a
lot
further.
Along
than
I
inspected
and
expected
in
two
weeks.
My
only
request
is,
I
would
love
to
see
as
the
next
flow
that
you
tackle
is
unmanaged.
E
I
think
unmanaged
is
really
important,
especially
for
getting
new
users
on
board,
because
it's
the
cheapest
and
quickest
way
we
can
get
people
to
start
playing
around
with
tce
so
seeing
that
and
that
actually
should
also
help
you
with
what
a
workload
cluster
should
somewhat
look
like
too,
because
it's
a
very
similar
flow.
That's
just
my
only
request,
but
I
love
the
work.
Let
me
know
when
I
can
beta
test,
because
I'm
super
excited
to
try
or
alpha
test,
or
you
know,
first
working
thing
test.
E
I
might
if
I
was
a
new
user
who
liked
gooeys
and
I
didn't
like
cli,
and
so
we
could
say
that
the
other
reason
I
might
like
a
ui
is,
if
I'm
spinning
up
a
lot
of
unmanaged
clusters
internally,
and
this
gave
me
the
ability
to
see
all
the
unmanaged
clusters
I
have
locally.
I
might
if
the
man
when
I'm
done
spinning
it
up
there,
was
something
that
this
ui
allowed
me
to
interrogate
about
the
unmanaged
clusters.
E
That's
I
would
have
to
like
you
know
like
if
it
actually
somehow
neatly
flowed
into
some
here's
the
management
cluster.
We
just
spun
up
unmanaged
cluster.
We
just
spun
up
and
here's
the
link
to
its
portal,
or
something
like
that,
so
that
I
could
start
looking
into
my
cluster
right
away
other
than
that,
no
especially,
if
I
I
mean,
of
course
not
for
ci
cd
stuff
and
all
that
other
stuff,
but
as
a
new
user,
I
could
see
at
a
new
user
or
a
workshop.
B
E
B
G
Sean
as
far
as
I
understand
from
jaws
manage
clusters
will
eventually
be
able
to
integrate
with
more
providers
other
than
kind
right.
So
when
you
look
into
a
managed
clusters
being
provisioned
on
any
of
this
cloud
infrastructure,
obviously
it
makes
a
lot
of
sense
to
have
similar
ui,
because
then
we
get
into
the
all
the
complexities
of
provisioning,
understanding
the
infrastructure
for
a
managed
cluster,
which
probably
will
be
like
a
dummy
user.
E
Oh,
that
does
remind
me
of
another
piece
of
feedback
I
wanted
to
give
to
gary
about
the
the
choosing
your
profile
screen.
I
am
disappointed
in
that
screen,
though
I
I
thought,
when
I
had
originally
seen
that
I
thought
that
was
going
to
be,
you
were
going
to
install
a
set
of
plugins.
That
gives
me
like
a
a
developer
cluster
or
like
it
had
a
whole
bunch
of
stuff
pre-configured,
but
I
I
that
this
doesn't
help
me
that
much
in
terms
of
compute
type
really
I'd.
E
Rather,
actually
we
had
wait
for
this
kind
of
stuff
until
we
get
the
stuff
kartik's
working
on
our
meta
package
is
done,
and
then
this
is
when
I
choose
a
meta
package
and
then
based
on
the
meta
package,
I
choose,
you
can
make
suggestions
about
what
hardware
you
might
want.
But
in
terms
of
this
I
don't.
This
is
not
that
helpful
right
now.
This
takes
up
a
lot
of
space
compared
to
what
I
think
the
value
it
actually
brings
given
what
it
brings.
C
Yeah,
I
just
want
to
say
on
the
packaging
side,
we
definitely
hear
you
all,
there's
larger
product
conversations
going
on
around
exactly
what
domain
should
own
the
package
installs
and
all
that
stuff,
so
totally
heard
agree.
It
needs
to
be
there.
I
would
love
to
hear
more
about
if
this
instance
type
approach
is
problematic
in
the
proposal.
C
One
of
the
things
that
we
have
observed
with
end
users
is
that
when
you
drop
down
in
the
existing
kickstart
ui,
the
amount
of
ac2
instance
types
there's
about
77
000
of
them,
and
it's
really
confusing
to
understand
and
reason
about.
What's
going
to
be
adequate
for
your
use
case,
so
going
from
77
options
into
a
reference
to
docs
to
five
known
working
options
that
go
slightly
towards
what
you're,
preferring
via
computer
memory,
seemed
compelling
to
us.
G
If
I
have
time
jose
to
answer
one
of
your
questions
related
to
this
instance
type,
one
thing
that
I
just
noticed
is
that
you're
selecting
instance
type
for
management
cluster,
and
you
are
like
talking
about
the
usage
that
you
are
going
to
give
you
give
into
a
new
to
a
management
cluster
which
I'm
not
an
ops
guy.
But
I
pretty
much
understand
that
management
clusters.
They
are
just
there
to
be
able
to
create
clusters,
so,
like
storage
optimized
memory,
optimized
could
optimize.
G
I
don't
know
whether
that
much
makes
a
lot
of
sense
for
for
management
cluster.
It
does
for
workload,
obviously,
but
then
for
for
workload
you
specify
some
type
of
of
like
what
you
are
going
to
be
doing
business
type,
but
then
you
get
to
the
regions
and
that
regions
to
me
it
seems
like
really
complicated
the
fact
that
you
need
to
understand
whether
you
want
to
use
one
a
set
or
three
a
sets.
I
mean.
G
I
know
that
already,
because
I've
been
working
with
this
a
long
time,
but
as
a
user,
I
would
really
not
understand
that
it
means
that
I'm
going
to
deploy
one
node
or
three
nodes.
The
fact
that
I'm
selecting
three
eight
sets
right.
So
that
is
probably
something
that
needs
to
be
better
described.
The
fact
that
the
a
set
means
the
number
of
nodes
that
you
are
going
to
be
defining,
because
what,
if
I
want
six
nodes,
how
many
assets
do
I
need
to
use
six?
C
Yeah,
I
think
that's
really
good
feedback.
If
you
can
put
that
in
the
proposal
to
jorge,
we
definitely
need
to
rethink
tab,
two
with
regards
to
the
context
of
a
management
cluster
because
you're
absolutely
right.
These
are
more
focused
on
decisions.
You'd
make
based
on
workloads.
You're
gonna
run
yeah,
so
I
yeah
get
this
feedback
in
the
proposal.
We
super
appreciate
it.
C
The
line,
we're
balancing
here,
as
as
we
all
try
to
reason
about
this
is
like
how
do
we
give
a
simplified
known,
good
path,
because
so
many
people
are
just
trying
to
get
started
and
failing,
but
still
give
enough
knobs
right.
So
you
know
especially
like
jorge's
feedback
and
your
feedback
steve.
Let's
capture
that
in
the
proposal
and
then
keep
that
kind
of
balancing
act
in
mind
here
and
long
term.
H
If
I
could
also,
you
know,
solicit
feedback
for
one
other
pattern
that
we're
working
around
it
would
be,
for,
I
think,
step
four
right
so
to
josh's
point.
What
we're
trying
to
do
is
include
like
a
reasonable
set
of
defaults,
really
simplified
basic
workflows
for
user
to
you
know,
successfully
deploy
a
management
cluster,
and
then
we
have
these
other
common
configurations
like
cluster
metadata
or
proxy
settings
right,
and
these
are
more
optional
configurations.
H
So
if
anyone
has
any
feedback
or
thoughts
that
they
can
add
to
the
proposal
on
like
you
know
whether
they
feel
that
these,
these
optional
configurations
should
be
part
of
advanced
settings
for
certain
steps
or
if
they
kind
of
deserve
their
own
area
or
like
kind
of
catalog
of
optional
configurations.
That
would
be
helpful
too,
because
I
think
we've
we've
kind
of
gone
back
and
forth
on
this
one,
a
little
bit
internally.
A
D
A
A
Okay,
well
thanks
everyone
for
joining
today,
thanks
to
gary
for
providing
that
demo
really
cool
to
see
super
exciting
stuff.
Again,
please
take
a
look,
provide
feedback,
we'd
love
to
hear
your
thoughts
on
it
and
we'd
love
for
you
to
join
us
at
our
next
meeting.
So
come
join
us
for
the
office
hours
next
week
at
11
a.m.
Pacific
time.
Otherwise,
you
can
find
us
on
on
slack
on
twitter,
on
github
on
email,
we'd
love
to
hear
from
you
again
thanks.
Everyone
have
a
good
day.