►
From YouTube: Tanzu Community Edition: v0.10.0-rc3 Demo
Description
John McBride takes us through a demo of the new unmanaged cluster model in Tanzu Community Edition v0.10.0
A
We
did
set
aside
some
time
to
look
at
the
latest
release
candidate
because
there
are
a
few
cool
things
in
it
that
we
wanted
to
show
off
to
you
all.
So,
while
you
all
are
thinking
of
your
questions
I'll
hand
it
over
to
john
to.
B
B
Yeah
no
problem:
let's
share
my
screen
here.
We
go
all
right,
welcome
everybody!
So
primarily
what
I
wanted
to
talk
about
in:
let's,
let's
arrange
my
zoom
things.
Real,
quick
there
we
go
is
unmanaged
cluster,
which
is
coming
in
v010
of
tanzania
community
edition
and
is
what
it's
it's.
What's
going
to
be
kind
of
replacing
in
the
future
standalone
cluster
as
standalone
cluster
is
being
deprecated.
So
what
is
unmanaged
cluster?
B
It
gives
you
a
single
node,
a
local
workstation
cluster
with
all
of
the
tc
bits
installed
on
top
of
it,
which
primarily
is
cap,
controller
and
all
of
our
packages.
So
I
can
come
over
here
and
we
can
do
unmanaged
cluster.
Let's
just
look
at
the
help
here,
quick.
So
this
gives
us
our
single
node
static,
tens
new
kubernetes
clusters,
as
we
see
here,
so,
let's
just
jump
into
it
and
start
bootstrapping.
B
So
we
can
tanzu
unmanaged
cluster
great
and
we're
just
going
to
call
this
first
one,
my
cluster,
and
that
starts
right
away.
I
have
a
bunch
of
this
stuff
already
downloaded
on
my
machine,
but
right
away
it
will
start
pulling
the
bomb
and
the
tanzu
kubernetes
release.
As
we
can
see
here,
our
default
one
we're
installing
is
v121.5
and
it
pulls
the
images
for
deploying
the
kubernetes
cluster
on
top
of
kind
and
then
cure
it
is
actually
creating
the
cluster.
B
So
this
will
be
a
little
bit
of
a
lull
in
the
demo,
as
as
it
starts,
actually
deploying
the
cluster
on
top
of
kind.
But
we've
gotten
this
bootstrapping
pretty
stripped
down,
and
it
actually
should
be
much
much
faster
than
people
have
experienced
with
standalone
cluster
in
the
past.
Where
now
really.
This
is
not
going
through
the
whole
code
path
that
unm
sorry
that
managed
clusters
had
where
you
had
to
have
a
bootstrapper
and
that
would
actually
get
a
cluster
up.
B
This
is
just
our
single
node
cluster,
right
away
that
it's
going
to
start
now
already
built
the
cluster
and
it's
going
to
start
getting
cap
controller
on
top
of
there
as
well,
and
doing
all
that.
So
once
that
is
done,
installing
we
can
actually
take
a
look
inside
and
see
what
what
it,
what
it
did.
If
there's
any
intermediate
questions
here
as
this
is
bootstrapping,
feel
free
to
unmute,
and
let
me
know
john.
A
B
What
is
a
bomb
and
what's
importance
to
the
process?
Yeah,
that's
a
great
question
josh.
So
a
bomb
is
the
bill
of
materials
and
it
sort
of
is
the
kind
of
declaration
of
what
individual
pieces
of
software
make
up
the
broader
platform
of
unmanaged
cluster
there's
also
a
bomb
that
goes
out
for
managed
clusters
and
framework
clusters,
tkg
clusters
and
right
now
they
are
in
a
sense
coupled
together.
So
this
bomb
that
we're
consuming
is
the
same
one
from
framework.
B
I
believe
correct
me
if
I'm
wrong
josh,
but
so
that
that
installed,
it's
done
great
wow
that
took
like
two
minutes
or
something.
So
now,
let's
take
a
quick
look
inside.
It
automatically
sets
the
context
and
targets
this
new
cluster
that
we
have.
B
So
let's
get
pods
all
and
we
can
see
here
that
it
has
a
bunch
of
stuff
primarily
down
here
in
the
tkg
system-
name,
space,
cap
controller,
so
speaking
of
which,
let's
scroll
down
a
little
bit,
and
we
do
get
a
cap
controller,
including
all
of
the
packages,
and
we
do
install
the
tc
default
package
repository,
which
is
that
same
one
that
you
would
have
used
for
managed
clusters
and
standalone
clusters.
B
So
we
can
actually
take
a
look
and
package
available
list
and
this
is
going
to
give
us
a
list
of
all
the
packages
that
we
can
install
onto
this
cluster
and
that
workflow
is
pretty
much
exactly
the
same
as
if
you
were
using
a
managed
cluster
or
a
standalone
cluster.
So
you
could
install
cert
manager
or
grifon
or
whatever
that's
all
available
here.
So
cool,
very,
very
neat.
B
Another
big
thing
that
you
can
do
with
unmanaged
clusters
is,
you
can
actually
configure
the
bootstrapping.
So
let's
do
unmanaged
cluster
configure.
Let's
look
at
the
help.
Real
quick
and
what
that
will
actually
do
is
dump
out
a
yaml
file
which
gives
us
the
ability
to
then
change
those
configuration
options
within
the
yml
file.
There
are
also
flags
that
are
associated
with
each
option
in
the
configuration.
So
let's
do
it.
B
Let's
do
unmanaged
cluster
configure
and
we're
just
going
to
call
this
hello
config
and
it
wrote
our
configuration
file
into
helloconfig.yml,
let's
go
in
there
and
let's
change
some
stuff.
So
let's
do
a
different
cni,
for
example,
unmanaged
clusters
support
calco.
So
we
can
change
that
to
calico,
let's
save
and
quit
that,
and
then
we
can
use
that
configuration
yaml
file
to
actually
deploy
a
new
cluster.
B
So
let's
do
tanzu
unmanaged
cluster,
create
give
it
the
c
option
which
then
we
can
point
to
our
hello
config,
and
then
let's
call
this
cluster,
my
other
cluster,
and
that
will
start
the
bootstrapping
process
again.
So
this
will
be
our
second
cluster,
that's
getting
deployed
locally
here
and
that
will
actually
use
calico
for
our
for
our
cni,
so
where's
it
getting
calico.
That
is
being,
I
guess,
deciphered
from
the
bomb,
which
is
what
is
being
pointed
to
for
the
specific
cni.
B
So
I'm
not
gonna,
I'm
not
gonna
make
us
go
through
this
again,
because
that'll
take
another
minute
or
two.
I
wanna
make
sure
we
leave
enough
time
towards
the
end
for
some
questions,
so
I'm
just
going
to
cancel
that
real,
quick
and
we'll
keep
trucking
along.
So,
as
I
mentioned,
we
do
point
to
a
default
tkr,
which
is
tanzania
kubernetes
release
and
defines
which
kubernetes
version
and
other
pieces
of
software
get
deployed
on
top
of
this
as
well.
B
So
we
can
actually
configure
that
using
unmanaged
cluster
and,
as
I
said
here,
it
was
v1.
21.5
is
the
default
one
and
using
the
tactac
tkr
option
or
in
the
config
file.
We
can
actually
configure
that
so
first,
let's
take
a
look
at
the
image
registry
at
what
is
available
for
that
specific
image,
which
is
slash,
tce
tkr.
B
So
I'm
going
to
use
my
history
and
there
it
is
using
crane
to
take
a
look
at
what
the
different
versions
are,
and
I
see
that
there's
a
slightly
newer
one
right
here,
v1.2.2
and
we
can
use
that
as
part
of
this
configuration
for
creating
a
new
cluster
here.
So
I'm
gonna
use
my
history
again,
so
I
don't
have
to
type
all
that
out
somewhere,
it's
gonna
be
way
back
and
history.
It's
this
one!
B
So
here
we're
using
the
tactac
tkr
option
with
that
specific
version
of
that
image
in
the
registry
and
we're
going
to
call
this
cluster,
my
tkr
cluster-
and
we
start
that
right
away,
and
we
can
see
that
I
had
already
done
this
before
so
that
tkr
already
exists,
but
it
is
using
tce,
tkr
v1
22.2,
that's
a
mouthful,
but
that
will
include
a
new
version
of
kubernetes.
I
believe,
and
also
a
new
version
of
cap
controller,
I
believe
so
very
cool.
That's
a
different
cluster
with
a
different
tkr
just
from
a
configuration
option.
B
So
I'm
actually
going
to
set
this
aside
real,
quick
and
we'll
keep
going
in
a
different
terminal
and
there's
a
couple
other
really
nice
little
things
that
we
can
do
with
unmanaged
cluster.
We
can
do
a
list
unmanage
cluster
list
and
we
can
see
all
the
clusters
that
we
have
deployed
with
the
specific
provider
as
well.
B
That
also
takes
an
option.
So
let's
say
we
wanted
this
in
json
and
boom
there.
It
is
in
json
and
then
obviously
we
can
also
delete
clusters
using
the
delete
command
on
top
of
this.
So
we
can
do
tanzu,
unmanage
cluster
delete.
Now,
let's
just
delete
that
first,
one
that
we
created,
which
was
my
cluster
and
that
should
be
deleted
almost
instantaneously
because
it
lives
on
top
of
kind
on
this
local
machine.
So
that,
in
a
big
nutshell,
is
unmanaged
cluster
and
kind
of
what
we've
been
doing
with
that.