►
From YouTube: Tanzu Community Edition Office Hours - March 9, 2022
Description
Tanzu Community Edition Office Hours - March 9, 2022
We meet every 2nd and 4th Wednesday at 11am PT. We'd love for you to join us live!
This week we had a lively discussion on v0.11.0 updates. Check out full agenda and notes here: https://hackmd.io/CiuO4V0AT6WL_TgA47MXBA?view#March-9-2022-Office-Hours
A
Hi
everyone
welcome
to
this
week's
edition
of
the
tanzu
community
editions
office
hours
for
those
of
you
that
are
watching
this
from
home
as
a
recording
on
youtube.
We
encourage
you
to
come.
Join
us
live
for
these
office
hours.
We
meet
every
second
and
fourth
wednesday
at
11
a.m.
Pacific
time
it's
a
more
open
discussion
format.
So,
if
you
have
anything
you
wish
to
bring
up
with
the
team
that
requires
a
little
bit
more
time
to
go
over.
If
you
have
a
feature
request,
any
help
you
may
need
with
getting
started
with
tce.
A
A
India's
standard
time,
so
those
are
some
great
opportunities
for
you
to
join
us,
live
and
and
get
to
know
the
team
and
other
members
of
the
community
and
bring
any
questions
you
have
up
with
with
folks
here
and
if
you
aren't
able
to
come
and
attend
any
of
these
options,
you
can
still
reach
out
to
us
we're
we're
eager
to
help
out.
You
can
find
us
in
the
kubernetes
slack
workspace
in
the
tanzania
community
edition
channel.
You
can
find
us
in
github
discussions
if
you
have
a
special
request
or
suggestion.
A
Please
add
that
to
our
issue
list
and,
as
always,
send
us
an
email
for
those
on
this
call
and
any
one.
That's
watching
the
recording
and
you
have
something
you
wish
to
bring
up.
You
can
add
your
discussion
topic
to
the
agenda
that
is
down
here
at
the
bottom,
so
for
folks
on
this
call,
if
there's
something
that's
come
up
that
you
wish
to
discuss
while
we're
meeting
today,
please
add
that
here
and
we'll
get
to
it.
A
And
today's
date
is
march
9th
2022,
if
you're
using
tce.
We
want
to
know
more
about
how
you're,
using
that,
so
we've
created
this
pinned
issue
here.
Please
go
to
that
add
a
comment
with
some
details
on
your
use
case
with
tce
helps
us
and
the
community
get
to
know
how
others
are
using
it
a
little
bit
better
to
help
us
build
better
products
and
also
help
the
community
know
other
ways
of
using
this.
A
So
it's
a
win-win
we'd
love
to
hear
from
you
all
attendees
on
this
call,
please
put
in
your
name
and
any
company
that
you
are
representing
and,
like
I
said
earlier,
we
have
an
announcement
here.
We
are
starting
our
apac
community
meeting,
which
is
happening
at
9
a.m.
Indonesian
standard
time
march
10th,
which
translates
to
7
30
pm
today,
pacific
time
on
march,
9th.
B
B
For
those
who
might
not
be
aware,
one
of
the
primary
focuses
is
tce
working
with
this
thing
called
tmc,
which
stands
for
tonzu
mission
control.
So
for
folks
who
want
to
hook
and
register
tce
into
something
that
can
lifecycle
manage
from
you
know
a
sas
perspective
and
you
know
basically
create
clusters.
B
Delete
clusters
do
package
installs
things
like
that,
that'll
be
something
that
will
be
possible
tons
of
mission
control
is
a
vmware
product
just
to
be
clear,
but
we
will
have
compatibility
and
and
that
going
into
v011
and
then
the
implications
of
all
this
work.
We're
currently
doing
is
a
couple
things
that
I
think
a
lot
of
people
been
asking
for
for
a
very
long
time.
So
in
this
release,
some
things
to
know
is
that
upgrades
of
clusters
will
work
again.
There
was
a
bug
in
upgrading
clusters.
B
B
We
will
finally
be
on
capi
v1
beta
1,
and
the
cap
controller
version
will
bump
to
0
30
from
what's
currently
0.25.
So
those
are
some
of
the
big
implications
I
think
end
users
are
going
to
see
so
in
summary,
we're
targeting
a
march
release
the
things
that
you
see
in
red
up.
There
are
around
the
bill
of
materials
being
produced
so
from
a
community
perspective.
Y'all
actually
don't
see
the
bill
of
materials
process.
B
It's
today
at
least
a
lot
of
like
downstream
vmware
things
that
we
do
to
like,
build
all
the
things
like
the
machine
images,
the
packages
and
then
eventually
bubble
it
up
into
this
bill
of
materials
right.
So
that's
all
being
worked
on.
That's
a
bit
at
risk,
so
I
would
say:
there's
a
chance.
This
release.
If
we
don't
get
this
bill
of
materials
by
tomorrow
could
get
pushed
into
april.
We
got
to
talk
to
product
management,
to
figure
out
what
the
right
time
framing
would
be.
B
But
again,
if
all
goes
well,
we
we'd
hopefully
be
on
track
for
v011
and
that's
kind
of
a
summary
of
some
of
the
key
things
that
will
be
in
it
and
with
that
that's
kind
of
all
the
tmc
and
updates
to
tce
there's
a
lot
going
on
with
tons
application
platform.
So
maybe
I
could
turn
it
over
to
cardiac
cardic.
If
you
want
to
give
some
updates
wait.
B
B
B
D
Yeah
sorry,
just
on
that
topic,
what
steve
said,
I
think-
and
I
would
love
to
I'm
happy
to
work
with
you,
anyone
else
to
highlight
like
four
or
five
key
unmessed
cluster
features
like
the
one
you
just
mentioned,
about
calico
being
the
default
cni,
that's
amazing
and
like
supporting
these
startup
clusters,
so
also
keeping
them
going
after
restart.
So
that's
fantastic.
All
right
on
the
tab,
oss
side
there's
been
some
great
updates,
literally
even
from
the
time
I
wrote
this
and
from
the
time
I'm
giving
the
update.
D
So,
as
you
can
see
here,
cartographer
will
be
available
as
a
package
in
tce
in
a
v11
release,
flux,
cd
source
controller
is
actually
merged.
I
should
update
that
and
will
also
be
available
as
a
package
in
pce
the
tc
team.
Thankfully,
thank
thanks
to
them,
gave
us
a
new
package
repository
with
those
new
packages
in
so,
if
you
all
want
to
give
it
a
give
it
a
try,
I
would
love
to
see
any
early
feedback.
You
have.
What
is
in
progress
in
right.
Now
is
one
of
one.
D
The
concept
of
the
meta
package
that
we
have
mentioned
here
before
the
concept
of
meta
packages-
it
just
installs
a
collection
of
packages,
but
the
user
experience
of
installing
packages
remains
absolutely
the
same.
So
in
a
sense
it's
yet
another
package
with
the
implementation
detail
around
installing
a
group
of
packages
should
probably
stop
using
the
word
meta
package
until
it's
actually
a
first
class
feature
in
karel,
the
and
the
and
the
last
one
which
is
in
development.
D
Is
the
transfer
apps
cli
plugin,
that
one's
on
the
yellow
side?
I
should
have
done
a
better
job
of
indicating
the
status
of
that,
but
that
one
is
on
the
yellow
side
just
a
bit
just
because
there's
some
binary
signing
work
that
needs
to
happen
for
it
to
be
make
it
in
time
for
the
tc
v11
release,
but
yeah.
Those
are
all
the
things
I
want
to
mention.
D
One
quick
thing
about
the
apple
assessment
package:
the
the
user
outcome
that
we
are
really
focused
in
on
is
enhancing
or
enabling
the
the
a
developer
with
the
local
development
and
iteration
experience.
This
is
the
start
of
that
journey
and
the
intent
is
to
make
that
and
make
it
as
easy
as
possible
for
a
user
to
start
with
source
code
and
get
to
a
running
app
yeah.
So
those
are
all
the
things
I
see.
A
question
from
scott,
which
I
think
is
good
techton,
is
something
that's
on
the
roadmap.
D
D
More
questions.
Oh
yes,
roger!
Yes,
that's
a
good
question,
so
the
app
cli
plugin,
let
me
back
up
cartographer,
introduces
the
concept
of
a
workload
which
is
sort
of
the
abstraction
or
the
interface
that
application
developers
can
interact
with
or
any
users
can
interact
with
when
they
want
to
create,
deploy
or
delete
their
workloads.
Tanzu
app,
cli
plugin
makes
it
easier
for
anyone
to
interact
with
the
workload
object
using
the
cli
plugin.
D
A
D
Yeah
k-
and
I
were
having
a
conversation
this
morning
or
morning
for
me
afternoon
for
her,
but
about
like
just
the
docks
and
the
way
we've
in
a
lot
of
places.
We
talk
about
installing
tce
and
in
some
places
we
talk
about
installing
the
tanzu
cli.
In
my
mind,
and
my
first,
my
opinion
is
that
we
should
I-
and
this
sometimes
bleeds
into
a
larger
topic,
but
I'll
try
to
keep
it
focused.
D
On
the
specific
question
I
have
or
discussion
I
want
to
bring
up,
is
I
think,
of
tce
as
a
collection
of
various
capabilities,
and
I
think
of
so.
I
don't
really
think
of
installing
pce,
I
think
of
like
installing
tanzu
cli
to
get
started
just
wanted
to
get
folks
here
and
their
thoughts
of
of
being
more
one
being
consistent
of
whatever
we
mean
in
our
talks
and
then
well
aligning
or
what
that,
what
what
we
are
consistent
about
and
then
making
it
consistent
in
our
docs.
C
B
Real
quick
before
we
get
into
docs.
I
just
want
to
make
one
quick
technical
clarification
here.
Yeah,
it's
it's
a
bummer,
it's
a
tech
debt
that
we're
currently
surfacing
right
now.
The
problem
with
the
install
flow
today
is
that
there
are
linker
flags
used,
which
is
a
build
time
concept
that
tell
the
cli
in
accompanying
binaries
at
times
whether
it's
running
in
a
tce
mode
or
a
different
version
mode.
So
you
are
actually
installing
a
tonzu
cli
that
is
compiled
for
usage
inside
of
tce.
F
Yeah,
that's
exactly
right,
so
we
did
do
some
work
that
should
be
coming
out
with
this
on
territory.
Release
of
the
tanzanian
framework
that
does
take
the
sort
of
addition
information
out
of
the
binary
and
puts
it
into
your
configuration
file.
So
the
same
binary
that
you
use
for
the
you
know
tkg
product
and
the
binary
that
that
you
install
when
you
download
and
say
I'm
doing
a
tce
thing.
F
G
C
I
don't
know
for
sure,
but
is
it?
Is
the
tap
tanzhu
cli
the
same
for
tkg
or
tce,
or
is
it
its
own
special
tonzu,
because
we
have
three
different
places
where
in
the
instructions
where
I'm
told
to
install
tomsu-
and
I
don't
understand,
if
there's
compatibility
issues
between
all
three,
so
I
don't
know
if
that's
still
an
issue
as
well.
Yeah.
C
Right
tons,
no,
if
I
actually
go
to
the
tap
instructions
right
now
it
says
download
the
tonzo
cli
and
I
don't
know
which
one
it's
actually
telling
me
to
download.
What's
it
compatible
with
like
it
doesn't
say,
this
is
the
tk,
it
doesn't
say
which
version
it
just
says:
go,
get
the
tons
of
cli
and
then
update
your
repository
and
do
the
following
things.
And
so
that's
what
I'm
saying
we
use
tons
of
cli
in
three
different
places,
and
it's
not
right
now.
B
E
C
E
It
was
confused.
It
was
confusing
for
me
yeah,
because
I
kind
of
thought
you're
installing
a
product
you're
installing
the
product
tce
but
yeah.
It's
it's
it's
not
that
simple
and
I
think
it
it's
easier
for
everybody.
If
it's
referred
to
as
times
cli,
it's
it's
clearer.
It
seems
to
be
what
what
folks
understand
better
yeah.
B
Yeah,
we
should
definitely
take
it
into
a
pr
and
talk
about
it.
Thanks
for
doing
all
that
work,
okay,
it
is
really
complicated,
because
I
just
make
sure
that
we're
saying
the
right
thing
like
you
are
installing
a
compiled
tonzu
cli
that
is
compiled
for
tce
at
this
juncture
and
due
to
technical
debt.
That
is
the
state
that
we're
in
so
I
just
want
to
make
sure
we're
all
on
the
same
page
there,
and
I
totally
hear
it
as
remarkably
painful
no.
C
H
Yeah
steve
installing,
if,
if
you
ask
me
what
quote
installing
pce
means,
is
it's
a
to
me
when
I
think
about
that?
You
know
what
installing
something
means.
It's
what
happens
in
the
deployment
process
as
the
north
half
of
each
of
each
node,
as
opposed
to
you
know
the
lower
half,
which
is
prepping
the
nodes
right.
So
you
config
you
deploy
a
cluster
which
consists
of
configuring
infrastructure
and
quote
installing,
and
configuring
dce
unquote
on
those
nodes.
D
Yeah,
I
think
I
mean
I
understand
some
of
the
technical
challenges
around
the
cli
and
sort
of
slightly
different
versions
of
the
cli
yeah
across
our
open
source
and
commercial
products.
But
keeping
that
aside,
I
agree
with
you
steve
for
the
larger
issue.
I
I
think
of
you're
installing,
like
a
tce
version
of
kansas
cli,
and
then
you
create
a
cluster
yeah.
D
I
I
look
at
and-
and
this
again
does
go
back
to
the
broader
issue
which
I
don't
want-
I
didn't
want
to
go
too
much
into
which
is
you're,
installing
capabilities
or
components
which
are
available
in
pce
you're,
not
really
installing
pce
etc.
But
pc
is
an
addition
like.
How
do
you
install
an
edition
addition
in
my
mind
but
anyway,
that
I'll
pause
here,
because
this
can
get
into
bike
shedding
very
quickly
so.
H
H
D
Yeah,
I
think
it'll
be
good
to
just
close
the
stop
again
move
on
to
something
else,
but
just
want
to
raise
it
up
with
the
dc
team.
I
think
this
is
something
to
figure
out
and
it's
definitely
a
gnarly
one.
So
I
understand
the
challenge
around
it.
Yeah
I
think,
over
in
in
the
long
term,
I
think
it'll
simplify
the
the
user's
journey
and
knowing
what.
B
A
I
One
question
actually
that
in
tkg-151,
because
I
see
that
we're
also
trying
to
base
it
off
of
that
bomb
or
building
a
tc1,
the
plugins
there
at
least
cluster-
and
I
think
one
other
one
became
context
aware.
So
they
actually
aren't
installed
like
during
the
installer
is
tc.
Moving
to
that
approach
as
well,
where,
like
the
cluster
plug-in,
gets
downloaded
after
creating
a
management
cluster.
B
I
Okay,
yeah,
because
if
it
does
go
that
way,
all
I
would
say
is
that,
because
in
tkg
it
wasn't
done
well.
I
think
that
should
be
documented,
because
it
was
really
weird
for
anyone
that
installed
dkg,
that
it
wasn't
documented
that
you
don't
have
a
cluster
plug-in
and
no
one
could
figure
out
why
it
wasn't
there.
So
if
that
can
be
added
to
the
docs,
if
that
does
happen
in
0-11
that'll
be
helpful
and
remove
some
pain.
I
think
of
weirdness.
B
Yeah,
we
completely
agree,
and
we
think
the
sharp
edges
are
largely
one
of
the
reasons
why
we're
trying
to
wait
a
bit
because
in
so
we're
pinning
to
tonsil
framework
version
v011
ii
just
by
chance,
by
the
way
the
version's
lined
up,
and
a
lot
of
this
has
gotten
better
in
newer
versions
of
framework.
So
that's
another
reason
that
it's
compelling
for
us
to
wait,
but
totally
heard
you
on
the
dock
scott.
We
shouldn't
surprise
our
users
by
plugins
just
disappearing
thanks.
C
Another
quick
question
around
somewhat
related
to
this
thing
as
well,
though,
is
it
wasn't
just
that
the
clies
were
different?
It
was
that
the
config
files
were
also
different,
or
something
like
that,
if
I
remember
right
or
like
they
overwrote
in
the
same
location
or
something
like,
I
can't
have
both
on
my
machine,
because
I
can't
have
both
like.
I
can't
do
a
sim
link
to
one
and
call
or
call
rename
the
binary
and
call
it
something
because
they're
writing
to
the
same
location,
even
like
you
just
can't
even
have
either
binary.
C
B
Yeah,
unfortunately,
not
we
had
some
work
in
flight
and
newer
versions
of
framework
that
we're
going
to
enable
this
type
of
behavior,
but
for
a
variety
of
reasons,
we're
pinned
to
an
older
version
of
framework
and
excuses
aside.
The
short
answer
is
no.
Unfortunately,
it's
going
to
be
this
painful
in
v011
as
well.
B
B
No,
it's
a
super
fair
question
and
we
do
hear
it.
We
bounce
back
between
different
versions
as
well.
Even
developing
tc,
like
we'll
use
the
pure
framework
stuff
and
we'll
bump
to
the
tce,
builds,
and
it's
extremely
painful
for
us
too.
So
needless
to
say,
we're
very
compelled
to
make
this
better.
A
lot
of
the
changes
that
will
make
it
possible
actually
are
in
frameworks
main
branch
and
v017
team
release.
Today,
it's
just
a
matter
of
some
complexities
around
us
getting
tce
on
those
new
versions.
So.
C
But
related
to
that,
since
we
don't
have
the
binaries,
does
the
engineering
team
actually
have
some
sort
of
like
handy
little,
shell
scripts
or
something
that
like?
Because
if
you
guys
are
switching
a
lot,
maybe
somebody
has
written
some
sort
of
cool
little
utility
that
they
could
put
in
like
somewhere
that
the
community
could
get
access
to
that.
For
those
of
us
who
use
both.
That
would
make
your
life
a
little
bit
easier.
I
mean
it's
not
fixing
the
problem,
but
it
makes
life
easier.
That
would
be
awesome.
B
Yeah,
I
would
say,
ask
in
slack
just
so
that
the
whole
engineering
team
can
respond.
I
don't
want
to
speak
for
everybody,
but
my
intuition
is
a
lot
of
us
use
some
make
tasks
that
rip
and
replace
everything
constantly,
and
that's
probably
due
to
the
nature
that
a
lot
of
our
validation
is
quite
ephemeral,
which
does
not
represent
probably
what
our
end
users
do
where
they
want
these
things
to
be
more
long-running.
B
I
I
Exactly
just
sue
into
that
user,
and
the
only
thing
that
you
need
to
do
after
installing
is
move
tanzu
cli
from
usr
local
bin
to
let's
say
like
whatever
dot
local
bin
or
whatever
in
your
path.
It's
just
for
your
user
right
and
I
have
a
tce
user
and
a
tkg
user
on
my
jump
box
and
a
tap
user,
because
back
in
the
day,
tap
couldn't
use
either
of
those
tens
of
clients.
So
I
have
three
users
with
different
ads
and
clies.
Well,
I
actually
have
forks.
C
Do
this
and
you've
installed
it
like
you,
don't
actually
have
to
use
any
of
the
package
managers
which
is
or
even
the
shell
script,
which
puts
it
in
user
local
bin
right,
because
if
I
had
those
steps
documented,
that
would
be
much
easier
than
what
scott
said,
which
is
like
okay,
install
it
but
then
go
to.
I
don't
go
to
that
directory
and
then
come
back
and
move
it
over
here
like
if
it
was
just
take
this
download
unzip.
C
E
C
But
it
may
not
be
your
issue,
it
might
be.
Everybody
says
no,
we
need
the
shell
script,
so
I
don't
want
to
say
yeah,
okay,
change,
this
when
everybody's,
like
no,
we
actually
require
the
shell
script.
So
I
shouldn't
have
tagged.
You
sorry
I'll
tag
josh
because
he's
in
he's
grandpa
josh
do
we
need
the
shell
scripts.
B
C
I
would
because
I
do
the
exact
same
thing
you
are
forgiven,
always
for
that.
I
at
some
point
I
raised
the
issue
of
getting
rid
of
the
shell
like
at
least
documenting
how
to
just
install
the
binary
and
what
and
like
manually
setting
up
on
your
machine,
because
I
felt
like
the
shell
script
plus
all
the
packaging,
plus
all
that
other
stuff
was
doing
too
much
for
what
was
actually
really
needed.
C
In
most
cases,
or
at
least
we
could
just
document
it
for
people
who
wanted
to
do
it
because,
like
scott's
example
of
well
okay,
if
I
install
it,
then
you
have
to
actually
go
to
user
local
bin.
Take
it
out
of
user
local
bin,
put
it
back
into
that
user's
direct.
But
if
I
just
had
instructions
like
download,
put
the
binary
here,
your
you
know
add
the
binary
to
your
path
and
you're
good
to
go,
which
is
basically
what
we
do
and
oh
initial
and
then
run
these
two
commands
right
like.
C
B
B
So
my
short
answer
would
be
yeah,
I'm
all
for
it.
Is
there
an
issue
to
track
the
need,
and
then,
let's
figure
out
some
of
the
details
of
what
it
would
look
like
knowing
what
we
know
about
like
how
plug-in
installs
are
going
to
change
in
the
near
future?
I
don't
know
whether
I
made
an
issue.
I
will
check.
I
I'm
also
I'm
working
right
now
by
the
way,
steve
on
a
vendor.
You
know
file
that
will
download
the
tkg
and
pc
once
and
install
them
into
different
users
into
different
paths
that
does
like
the
whole
installation
takes
all
the
right
files
puts
them
in
the
right
place.
Once
I
have
that,
I
can
also
share
it
and
then
that'll
just
be
a
single
command.
You
could
run
to
download
tkg
and
tc
clies
and
put
them
into
the
right
places.
A
A
Okay,
thank
you.
Everyone
for
joining
today,
a
really
great
discussion
was
had.
Thank
you.
Everyone
who
engaged
with
us
today
if
you're
watching
this
from
home,
come
join
us
next
week
we
meet
at
11
a.m,
pacific
time
for
our
community
meetings,
we're
going
to
have
a
great
demo
for
some
of
the
stuff
that
gary's
team
is
working
on
so
stay
tuned
for
that
and
find
us
on
slack.
If
you
have
any
questions
thanks.