►
Description
https://hackmd.io/CiuO4V0AT6WL_TgA47MXBA
Discussion Topics:
- Welcome and Objective
- Announcements
- No Meetings December 22, December 29, and January 5th for Holidays!
- Reminder: APAC Community Calls starting in February
- How to Get Swag
- Community Shoutouts
- TCE UI Discussion (Maharshi and Justin)
- Additional Feedback: https://github.com/vmware-tanzu/community-edition/discussions/2632
- Engineering Updates (John McBride)
- Advocacy Updates
- Thanks and signoff
A
Okay,
here
we
go
here,
we
go
hello,
hello
and
welcome.
Today
is
the
first
of
december.
This
is
our
community
meeting,
our
first
community
meeting
for
the
month
of
december.
Welcome
back
to
all
of
you
that
were
observing
thanksgiving,
happy
hanukkah
to
those
of
you
who
are
observing
that
holiday
this
week.
A
As
always,
our
objective
in
our
community
meetings
is
to
give
you
the
community
an
update
of
how
things
are
going
with
the
project.
This
meeting
is
recorded
and
is
being
uploaded
to
youtube.
So
if
there
are
company
specific
things
or
things
not
directly
relevant
to
the
project,
I
ask
that
you
please
hold
those
so
that
this
can
be
for
the
general
welfare
of
everyone
in
the
community
and
let's
get
started
with.
We
have
a
second
objective
today
and
that's
to
get
some
feedback
on
our
ui
for
tons
of
community
edition.
A
So
we've
got
a
couple
of
special
guests
here
that
are
going
to
help
us
and
I'll
be
helping
moderate
that
conversation
as
well.
So
first
thing
we're
not
going
to
have
meetings
on
december,
22nd
and
29th
for
us
holidays.
One
thing
that
we're
feeling
out
right
now
is
how
we
feel
about
the
15th
of
december
and
the
5th
of
january,
which
would
ordinarily
be
meetings.
The
current
consensus
is
that
we
keep
the
15th
meeting
and
we
cancel
the
5th
of
january
meeting.
Are
there
any
objections
to
that?
A
You
can
use
the
thumbs
up
or
thumbs
down
or
if
you
want
to
add
comment,
you
feel
free
to
raise
your
hand
and
we'll
get
through
those
okay,
I
see
no
thumbs
downs.
So
all
right,
we
will
be
canceling
that
meeting
for
january
5th,
so
we'll
see
you
all
back
on
7
plus
5
12.
january
12th,
we'll
see
you
on
january,
12th.
A
Okay,
as
a
reminder,
we
have
our
apac
calls,
starting
in
february,
still
figuring
out
how
that
that's
all
gonna
go,
but
for
those
of
you
who
are
watching
the
stream,
don't
worry,
we
have
not
forgotten
about
you.
We
want
to
be
sure
to
include
some
more
time
zones
and,
as
usual,
we've
got
a
system
in
place
now
for
receiving
swag.
Some
of
you
on
this
call
have
already
gotten
some
swag.
A
So
thank
you
for
helping
us
out
we're
glad
that
we're
able
to
send
you
some
things
and
yeah
for
the
show
and
tell
we
were
doing
one
person
a
month.
The
the
winner
this
month
is
robert,
who
is
here
on
the
call.
So
please
get
in
touch
with
me
and
I
will
be
sure
to
send
you
out
some
swag
from
us
yeah,
but
we
thank
you
for
all
of
your
activity
and
the
slack
channel
and
the
github
repo.
A
We
don't
have
any
targeted,
shout
outs
this
this
week,
but
we
are
looking
for
more
opportunities
to
thank
you
all
for
all
the
contributions
that
you
all
are
making
to
tons
of
community
edition.
With
that,
I
want
to
start
with
the
ui
discussion,
so
we
have
justin
here
and
yeah
justin.
If
you
wanna
just
go
ahead
and
take
it
away,
hey.
B
A
C
Yeah,
so
I
just
wanted
to
raise
one
thing
that
really
knocks
me
a
little
bit
is
that
there
is
no
ui
for
them
for
the
workload
class
clusters
right.
So
the
experience
is
a
management
cluster.
There
is
a
ui
and
basically
we
need
to
copy
a
configuration
file.
I
mean
and
understand
and
know
how
to
change,
remove
customized
configuration
values
to
many
people
that
sees
enough
for
me.
C
I'm
a
developer,
my
I'm
a
half
a
developer
background.
So
to
me
that
is
complicated,
sometimes,
and
I
basically
has
just
one
type
of
cluster
or
workload
cluster
configuration
that
I
typically
reuse.
But
then
the
problem
is,
I
don't
know
if
I
need
to
update
some
like
if
my
version
09
to
version
10,
there
is
a
difference.
I
probably
will
be
applying
still
the
version
9
configuration
to
my
warrior
cluster.
Basically
because
I
don't
know
what
what
I'm
doing.
B
Yeah
yeah,
that
is
certainly
a
valid
request
and
something
that
I
wanted
to
our
teams
wanted
to
address
for
for
quite
a
long
time.
I
think
you
know.
Maybe
we
can
have
some
discussions
over
slack
involving
roger
and
you
know,
determine
how
we
can
sort
of
you
know
fit
this
alongside.
You
know
the
the
core
underlying
application
it.
It
would
likely
have
to
be
something
that's
specific
to
the
community
edition
which,
which
is
great
but
yeah
for
certain.
D
Yeah
I've
been
seeing
a
lot
of
comments
about
prerequisites
and
knowing
what
people
need
it
looks
like
people
are
getting
stuck
and
we're
having
a
troubleshoot
a
lot
to
go
back
to
hey.
This
is
a
prereqs,
I'm
wondering
if
other
people
are
seeing
that
as
well
as
just
a
thread
that
I
keep
seeing
come
up.
B
C
B
Workflow
and
then
maybe
even
you
know
doing
some
some
real-time
validation
of
prerequisites
and
helping
to
guide
the
user
there
a
little
bit
more,
I'm
all
for
it.
I
think
I
think
I
agree.
That's
largely
what
we're
missing
here
for
new
users-
maybe
this
is
even
just
sort
of
you
know
the
the
for
this
type
of
solution.
What
we
should
probably
do
is
just
create
sort
of
like
a
like
a
bucket
github
issue
to
start
to
float
some
ideas
in
there,
but
roger
I've
looked
at.
E
E
I
think
there's
a
hierarchy
right
where
people
will
want
a
guided
experience
and
yet
want
to
be
able
to
turn
off
the
guiding
to
some
extent
so
that
they
don't.
You
know,
throw
a
brick
at
the
screen,
the
seventh
time,
they're
running
it,
but
still,
just
as
we
do,
for
example,
to
see
that
docker's
running
you
know
there
should
be
more
checks
that
I
agree.
There
should
be
more
checks
that
we're
providing
vm
configuration
with
enough
memory,
we're
providing
reasonable
instances.
E
You
know
stuff
like
that,
and
that
should
go
on.
You
know
people
that
one
should
be,
I
won't
say
harder
to
to
disable,
but
that
one
should
be
for
most
people
later
to
disable
so
separately.
You
know
you
should
be
able
to
hit,
and
I
know
what
I'm
doing
on
that.
But
but
it's
a
separate
issue,
so
yes,
I
will
absolutely.
B
Yeah
sounds
fantastic
and
I'm
kind
of
reading
through
the
chat
here
I
saw
a
couple
of
mentions
around
some
of
the
the
docker
prerequisites
on
resources
there
and
yeah.
That's
a
fantastic
example.
I
can't
recall
if
it
was
josh
or
someone
else
who
had
raised
the
github
issue,
but
I
believe
for
or
in
the
in
the
the
current
code
base.
We
do
have
some
additional
checks
now
to
confirm
that
the
user
has
the
appropriate
resource
settings
or
the
minimum
requirements
there.
F
C
E
And
well,
and
it's
especially
aggravated
by
some
of
the
failure
modes.
Aren't
you
know
the
feedback
isn't
isn't
good,
even
from
not
just
from
the
ui,
but
isn't
good
from
the
system.
You
know
you
get
hanging
pods,
you
get
you.
You
get
things
that
are
not
clear
failures,
so
it
they're
even
harder
to
diagnose
than
they
might
otherwise
be
so
yep.
That
especially
makes
the
pre-checks
more
important.
A
And
we
see
jace's
comment
there.
What
about
conceptual
prerequisites?
Is
that
something
that
we
want
to
handle
in
partnership
with
advocacy,
creating
content
or
something
that
we
should
cover
in
the
docs?
So
some
of
the
prerequisites
that
they
bring
up
are
networking
cluster
configuration
container
runtime.
I
would
say
cluster
api
as
well,
but
we
can
have
that
conversation
another
time
because
that's
not
specific
to
the
ui,
but
just
something
for
us
to
to
think
about.
Okay,
you
had
your
hand
next.
G
Something
specific
to
the
ui
and
I
didn't
get
an
answer
in
chat.
Sorry
is
the
ui
assumes
you
know
all
the
things,
what
all
the
things
in
your
cloud
provider
mean
and
how
to
do
a
whole
bunch
of
stuff,
and
I
that
for
me,
as
a
new
user
to
I
mean
I
don't
know
that
much
aws,
but
I
was
using
aws
and
so
like
ssh
keys
and
all
this
other
stuff
that
you
were
asking
where
they
had
no
idea
where
they
should
be
put.
G
E
E
A
H
Yeah
I
mean
similar
point
there.
Really,
I
think,
to
what
josh
is
saying
so
like
we
did
meet
before
justin
I
looked
at
you
know
what
we
could
do
to
integrate
some
of
the
content
that
is
in
the
dock,
into
the
ui
and
vice
versa,
how
we
could
link
from
the
ui
to
some
of
the
content,
that's
in
the
dock,
so
I
mean
we
definitely
need
to
to
work
on
those
on
both
of
those
and
see
what
needs
to
be
done.
H
But
I
think
the
thing
with
the
ui
is,
as
as
mentioned
it's
very
complex.
You
can't
give
a
lot
of
detail
about
everything,
that's
in
there,
because
it
would
just
get
it
would
get
overcrowded
very
quickly.
So
it's
just
to
give
the
minimum
amount
of
detail
that
would,
you
know,
hopefully
work
for
a
lot
of
users
but
to
allow
them
to
easily
get
more
information
by
either
just
a
hover
button.
Where
you
know
a
bigger
piece
of
information
will
help
you
know
appear
or
else
a
link
out
to
the
documentation.
H
So
it's
really
just
figure
out
the
mechanics
of
how
to
to
share
the
information
that
love
that
prerequisite
information
that
people
might
need
at
certain
points
when
they're
working
through
the
ui-
that's
in
the
dock,
but
they
don't
know
how
to
you
know
where
to
go
in
the
dock,
to
find
that
that's
just
to
get
those
to
get
those
links
set
up.
So
we
did
look
at
doing
this
before
so
it's
something
that
definitely
want
to
go
back
to
and
do
some
do
some
more
work
on.
F
Yeah
angel,
if
I
could
jump
in
just
on
this
point,
my
name
is
shimon
by
the
way
and
I'm
on
the
same
team
with
justin
working
on
the
ui.
We
have
built
a
contextual
help
system
that
would,
I
think,
solve
a
lot
of
the
things
that
we're
talking
about.
If
we
had
the
help
docs
structured
in
a
particular
kind
of
format,
then
we
can
allow
the
user
to
discover
those
things
in
the
ui
in
a
friendly
way.
That's
not
intrusive.
So
I
think
it
would
be
good
to
explore
that.
A
Yeah,
I
think
that
sounds
good,
and
I
think
this
is
also
like
sort
of
speaking
to
a
larger
conversation
that
we
had
been
having
about.
You
know
what
we
wanted
to
provide
as
a
community
for
tons
of
community
edition
and
about
this
education
piece
that
keeps
coming
up
with
the
contextual
help,
with
kind
of
defining
some
of
these
terms,
with
all
the
knowledge,
the
knowledge
prerequisites,
as
opposed
to
just
the
hardware
ones.
Josh
I've
got
your
hand
next.
I
Yeah
I
wanted
to
hit
on
something
that
jorge
said,
that
relates
to
maybe
an
architectural
consideration.
You
know
the
desire
for
workload.
Cluster
creation
obviously
expands
what
the
kickstart
ui
currently
does,
and
I
really
view
the
ui
as
an
opportunity
to
really
understand
the
scope
of
tonzu
and
getting
started
with
tanzu,
and
I
think
that
makes
it
a
little
bit
awkward
that
the
kickstart
ui
is
embedded
in
the
management
cluster
plugin.
I
B
B
Yeah
yeah
it's
I
I'd,
love
to
continue
this
conversation
and
talk
about
the
solution.
You
know
not
only
at
like
the
high
level
user
experience
and
design
level,
but
also
at
the
technical
level.
You
know
how
how
because
that
will
impact,
how
the
user
you
know
sort
of
bootstraps
the
ui
itself
right,
whether
if,
if
it
is
part
of
the
cli
they're
gonna,
run
a
cli
command
and
then
maybe
it
has
to
to
live
in.
You
know
tons
of
core.
F
I
I'm
sorry
I
just
wanted
to
tag
along
on
that,
and
that
is
that
I
think
you
know.
Justin.
I've
talked
to
fairmont
now
about
the
idea
of
having
the
user
enter
the
entire
experience
through
a
ui
and
just
turn
the
paradigm
on
its
head,
which
I
think
just
is
what
josh
was
saying.
Instead
of
having
different
ui
elements
associated
with
different
clique
commands
and
different
little
parts,
turn
it
on
its
head
and
start
with
a
ui
that
will
allow
you
to
do
various
things
and
that
way
the
user
experience
is
integrated
and
holistic.
J
Yeah,
I
think
the
one
thing
in
terms
of
the
ui
that
I
always
have
seen
is
that
the
ui
is
great
for
the
simple
use
case
for
the
standard
use
case.
But
there
are
a
lot.
Unfortunately,
there
are
a
huge
or
fortunately
or
not.
There
are
a
huge
amount
of
ytt
values
in
tanzania
that
can
be
set
and
a
subset
of
those
are
available
via
the
ui,
and
I
think
that
enabling
them
all
in
the
ui
would
be
way
too
complex
and
way
too
large
to
perform.
J
They
can
use
the
ui
for
90
of
the
way,
but
having
that
way
that
they
can
add
in
the
special
values
of
audit
logging
or
machine
health
check,
specific
values
that
exist
that
you
can
do
when
you
go
the
configuration
file
path.
But
can't,
if
you
go
down
the
ui
path,
having
just
that
escape
hatch
kind
of
at
the
end
would
just
allow.
E
E
J
So
just
allowing
the
way
to
then
in
that
review,
like
summary
page
allowed
to
add
something
right.
That
would
be
a
small
change
that
would
just
enhance
the
capabilities
of
using
it,
because
I've
had
many
use
cases
where
I
just
can't
use
the
ui
or
I
use
it,
cancel
it
take
that
file
and
then
go
and
manipulate
it
myself
before
deploying.
F
A
I
I
You
can
also
track
our
release
here
in
this
issue.
1293.,
and
then
we
will
be
cutting
another
rc
soon.
I
don't
know
if
today
or
tomorrow,
if
josh
wants
to
chime
in
on
that.
But
quick
note
on
that,
there
is
a
known
issue
on
the
vsphere
ovas
and
there's
a
few
issues
in
the
repo
about
that.
So
the
rc
currently,
as
is,
doesn't
work
with
vc,
since
those
overs
aren't
in
customer
connect,
so
yeah
new
rc
coming
soon
josh.
I
You
have
an
idea
when
yeah,
I
think
we'll
probably
have
something
towards
the
end
of
week,
where
paul's
got
something.
Okay
sounds
good
so
end
of
week,
some
long-standing
things,
the
standalone
cluster
overhaul
is
happening.
There's
a
proposal
there's
also
a
branch
where
you
can
get
that
build
and
try
it
out.
All
the
details
are
in
there
and
then
a
shameless
plug
tuesday
I'll
be
giving
a
talk
on
tce
with
tanzu
tanzu
tuesdays
on
twitch
so
tune
in
for
that
yeah.
That's
in.
A
K
Okay,
so
I'm
gonna
be
playing
a
little
bit
with
the
ui
actually
today,
but
I
am
super
stoked
about
the
tanzania
tuesday's
episode
and
yeah.
You
should
definitely
jump
on
there
for
anyone
tuning
in
to
the
call
or
who
hasn't
jumped
onto
that
stream
before
we
stream
it
on
twitch,
and
you
can
find
the
link
either
at
tanzu.tv,
where
we
have
all
of
the
episode
details.
You
can
see
josh's
face
there
or
you
can
go
to
our
twitch
channel
twitch,
slash,
vmware,
kanji,
so
yeah.
A
L
I
just
wanted
to
to
note
the
the
dutch
v
mug,
the
dutch
vmware
user
group,
meetup
used
to
be
the
the
biggest
one
in
the
world.
It's
been
dead
for
two
years
because
of
corona,
it's
restarting
16th
of
december.
I
have
a
session
there,
where
I'm
going
to
compare
the
different
tkg,
flavors
and,
of
course,
after
being
world.
E
L
A
Thanks
for
the
lively
conversation
about
the
ui,
I
feel
like
that
went
pretty
well
we're
going
to
leave
a
mechanism
online
for
those
of
you
who
are
watching
the
video
to
be
able
to
give
your
feedback
as
well.
Don't
want
you
to
feel
left
out.
So
if
there
are
things
that
you
want
to
add
we'll
we'll
have
something
in
the
slack
channel
for
you
to
be
able
to
do
that
and
we'll
also
link
to
it
in
the
discussion
post
about
this
community
meeting
thanks.
So
much
for
joining
us.