►
Description
Tanzu Community Edition APAC Community Meeting - March 10, 2022
We meeting every 2nd Thursday at 9am India Standard Time. We'd love for you to join us live!
The release engineering team gave updates on their E2E tests for vSphere, Azure, and AWS. Check out full notes here: https://hackmd.io/CiuO4V0AT6WL_TgA47MXBA?both#March-10-2022-APAC-Community-Meeting
A
You
can
bring
questions.
You
may
have
any
feature
requests
just
listen
in
on
what
the
team
is
working
on
meet
other
members
of
the
community.
Anything
like
that.
We
would
love
to
have
you
join
us
if
you
aren't
able
to
make
it
to
this
meeting,
we
do
have
a
another
option:
we'll
meet
every
first
and
third
wednesday
of
the
month
at
11
a.m,
pacific
time
for
other
community
meetings
and
then
every
second
and
fourth
wednesday
of
the
month
at
11
a.m.
A
If
you're
using
tce,
we
want
to
know
how
you're
using
it
we
want
you
to
be
able
to
share
how
you're
using
it
with
the
community
because
it
it
helps
us
know
more
about
those
use
cases
to
build
better
products,
and
then
it
also
helps
the
community
see
how
others
are
using
tc.
They
give
them
better
ideas
of
how
they
can
use
it
as
well.
A
So
we
created
this
pin
issue
and
you
can
go
and
put
in
a
comment
with
the
details
we
ask
of
you
and
if
you
want
to
be
featured
on
our
adopters
page,
you
can
include
logo
of
your
organization
and
we
would
love
to
have
you.
So
please
share
any
details.
You
have
on
how
you're
using
tce
everyone
that's
attending
today
in
this
meeting.
Please
add
your
name
and
then
the
company
or
organization
that
you're
representing
in
the
attendees
list
here.
A
As
far
as
announcements
go
for
apec
area,
it
doesn't
look
like
we
have
any
announcements
to
share
just
yet
it's
our
first
meeting,
so
we're
kind
of
getting
the
hang
of
it.
A
little
light
start
to
this.
But
you
know,
as
we
get
get
the
feel
of
it
and
the
feel
of
the
community
we'll
have
more
to
share
in
in
the
the
next
one
and
and
again,
if,
like
there's
anything,
you
want
to
see
these
meetings.
B
B
So
the
last
one
that
I
was
working
on
was
yesterday
fixing
the
azure
and
vsphere
entrance,
which
was
basically
around
recently.
We
actually
started
using
a
newer
version
of
transfer
framework
and
it
actually
uses
a
newer
virtual
machine
images
for
vsphere
and
azure,
so
we
had
to
actually
you
know,
accept
the
license
for
azure
virtual
machine
image
and
use
newer
over
for
our
vsphere.
B
C
Yeah
it'd
actually
be
sorry.
I
was
gonna
chime
in
here
yeah.
Actually,
it
would
be
really
good
if,
like
I
know,
bash
is
great
and
it's
wonderful
and
it's
very
easy
and
quick
to
like
create
something
very
quickly
but
yeah
like
it.
It
would
definitely
be
very
cool
to
like
move
away
from
from
a
lot
of
the
bash
stuff
and
like
do
it
and
go
so
that
we
can-
and
I
know
like
the
main
repo
code
base
for
like
some
of
the
plugins
and
stuff.
C
So
we
can,
you
know,
kind
of
get
like
a
a
smoke
test
of
like
whether
or
not
we
think
that
a
lot
of
the
automation
or
release
engineering,
stuff
or
the
end
and
testing
stuff
would
you
know
you
know,
survive
a
go
test,
let
alone
you
know
doing
a
like
a
full-blown
and
then
test
on
like
azure,
so
yeah.
That
would
be
very,
very
cool.
D
Sure,
but
not
to
the
point
that
david
mentioned,
but
plus
one
to
david's
point.
I
I
wanted
to
see
if
you
know
the
images
prepare
that
to
mention
the
vcr
and
all
images
that
we're
gonna
accept
licenses,
for
is
that
some
is
that
something
that
image
names
and
whatnot
we
surface
part
of
the
release
process
or
in
the
documentation.
The
new
images
that
are
learning
yeah.
B
B
Yeah
sorry
so
I
was
saying
like
this
has
been
an
idea
for
a
long
time
but
yeah
we
still
haven't
like
implemented
it,
so
we
still
have
to
do
that
for
vsphere.
I
think
it's
a
tricky
thing
because,
as
of
now,
we
create
our
virtual
machine
images
like
internally
and
like
public.
We
don't
yet
publish
it
all
like
in
a
public
thing,
so
we
have
to
actually
use
a
downstream
pipeline
to
actually
upload
it
whenever
we
have
a
new
virtual
machine
image
for
vsphere
and
in
the
future.
B
D
Sure,
but
the
operation
has
to
be
repeated
for
any
other
trying
to
do
the
cluster
life
cycle
with
new
dc
release
beside
you
know,
one
of
the
thing
that
I
found
tricky
is
you
know.
Having
found
the
name
of
the
os
image,
accepting
a
license
is
very
well
documented
for
each
cloud
product,
but
finding
the
name
of
that
os
image
from
the
bom
is
not
documented.
B
Yeah
yeah,
that's
the
idea.
As
of
now
I
think
even
bomb
is
tricky
because
tanzhu
there
are
tanza
is
very
configurable,
so
you
can
actually
even
mention
from
where
to
pick
up
the
bomb,
a
different
registry
and
whatnot.
So
the
idea
is
basically
to
use
sanju
itself
and
then
finally
get
the
dry
run
and
which
would
tell
exactly
what
virtual
machine
image
would
be
used
but
yeah
as
of
now.
My
plan
was
only
for
end
to
end
test
but
of
course,
ideally
to
be
able
to
automatically
update
the
documents.
B
C
Thanks,
I
would
even
float
this
idea
out
there,
because
that
is
actually
very
awesome.
It
almost
seems
like
we
should
have
that
functionality
and
like
tons
of
cli
and
be
basically
saying
hey.
These
are
the
assets
that
you're
dealing
with
and,
like
you
run
a
command,
and
it
says,
like
you
know,
this
is
the
version
of
the
ova.
This
is
where
it
lives
and
stuff
like
that,
or
these
are
the
amis
and
these
these
are
the
ami
ids.
I
mean
that
would
be
very,
very,
very,
very
useful.
C
I
mean
even
just
for
my
sake
like
instead
of
like
having
to
like
run.
I
can.
This
is
what
I
normally
do.
Is
I
run
like
a
management
cluster
create
and
I
intentionally
exit
out.
I
go
look
at
the
bomb
and
try
to
figure
out
all
this
stuff,
but
if
you
had
like
a
command
that
just
said
like
yeah,
if
you
had
a
command
that
just
basically
like
tons
of
cli
version
like
or
version
assets
or
assets
versions
or
whatever
right,
so
it
just
dumps
all
that
information
like
to
you.
B
Yeah
yeah,
as
of
now
the
dry
run
feature,
I
mentioned
it's
more
of
a
internal
detail
where
we
get
the
whole
yaml
that
will
be
used
to
actually
create
the
cluster,
and
we
have
to
look
for
this
detail.
It
will
not
be
exactly
a
human,
readable
format,
so
yeah
this.
This
is
this
would
be
a
new
idea
like
where
we
get
the
names
of
say,
amazon,
machine
image
or
the
azure
virtual
machine
image,
and
things
like
that
based
on
the
cluster
conflict
that
we
provide
and
things
like
that.
A
How
does
the
tce
engineering
team
test
cluster
deployment
manually?
What
steps
do
you
folks
follow?
This
is
respect
to
a
few
different
github
issues
listed
out.
This
is
to
understand
if
the
release
engineering
team
has
a
similar
approach
or
different
approach
to
test
cluster
deployment,
and
then
things
like
package
repo
edition
package,
installation
test
who
who
put
this
in
and
is
there
any
more
context
you
want
to
give
before
we
start.
B
C
Yeah
for
like
I
can
just
speak
to
how
I
do
it,
it
is
I
it
is
literally
I
if
I
want
something
stable,
I
use
like
a
you,
know,
a
release.
That's
out
there
so
like
currently
zero,
zero,
ten
zero,
and,
if
I'm
looking
for
like
to
verify
new
functionality,
I
I
literally
just
do
a
make
release
which
basically
builds
the
entire
all
the
tarballs
for
all
the
versions.
Like
you
know
the
platforms
and
the
architectures
that
we
care
about
and
then
run
the
install
script
to
install
you
know,
like
I,
usually
tech.
C
D
C
I
mean
I
like,
I
would
just
be
interested
in
like
the
highlight
of
like
some
of
the
work.
That's
being
done,
because
I
know
you
guys
are
you
do
a
lot?
You
know
over
there,
and
so
you
know
very
interested
in
like
some
of
the
things
that
you
think
are
very
cool
and
interesting,
even
some
ideas
that
you
might
want
to
kick
around
like
hey
like.
C
Maybe
we
should
do
this
or
collaborate
on
that,
not
just
for
us
but
like
even
for
the
community
at
large,
so
like
yeah,
I
would
definitely
be
interested
in
hearing
your
thoughts
about
like
like
like
what
what
you
think
could
be
like
benefit.
You
know
the
project
and
like
or
even
like
your
efforts
to
you
know
like
accelerate
some
of
the
stuff
that
you're
doing.
D
A
A
A
If
you
are
watching
this
from
home,
and
you
have
some
feedback
or
any
ideas,
you
want
to
bring
up
with
how
we
improve
this
meeting,
what
you'd
like
to
see
in
the
future
or
if
you
have
any
discussion
topics
you
want
to
bring
up
on
regarding
tc,
please
join
us.
We
would
love
to
hear
from
you
and
with
that
have
a
great
time
and
we'll
see
you
next
time.
Thank
you.