►
From YouTube: Cluster API v1alpha2 demo
Description
Deploy Kubernetes clusters in AWS and vSphere using a single cluster API management cluster
A
Now,
to
begin
with,
I
already
downloaded
some
of
the
component
files
needed
for
both
the
vSphere
provider
and
AWS
provider
and
stored
them
in
different
folders
on
my
laptop
and
also
updated
some
of
the
environment
files
needed
to
point
to
my
AWS
and
vSphere
environments.
Now,
let's
leg
dig
into
vSphere,
so
here's
my
vSphere
environment
and
my
goal
is
to
create
kubernetes
cluster
in
the
resource
pool
cluster
API
under
the
PA
data
center.
A
So,
let's
start
by
creating
a
kind
cluster
that
will
help
us
bootstrap
these
environments,
I've
already
installed
and
downloaded
kind
and
I'm
going
to
create
a
cluster
using
kind
once
I
had
a
kind
master
created,
I'm
going
to
start
deploying
so
the
infrastructure
components
needed
for
cluster
API.
So
right
now,
you'll
see
it
has
only
the
default
namespaces.
But
as
I
start
installing
my
cluster
API
components
will
start
some
of
the
CR
DS
that
cluster
API
creates
to
start
building
out.
A
Let's
start
deploying
the
bootstrap
components
for
cluster
API
as
well,
and
this
is
a
respective
of
any
provider.
These
are
components
needed
by
transferee
API
on
now.
Let's
get
into
vSphere,
so
I
already
have
an
infrastructure
component
file
with
environments
variables
set
in
a
text
file,
and
this
is
what
I'll
be
using
to
build
the
cluster
API
components
so
I'm
going
to
run
the
infrastructure
component
CMO
file.
This
will
create
a
namespace
called
kami
and
the
c
rd
is
needed
for
a
vSphere
provider.
A
I'll
also
I'm
also
deploying
the
secrets
needed
such
that
cluster
API
can
access
my
least
fear
environment.
Now,
at
this
point,
there
are
no
target
clusters
created
in
vSphere,
so
you'll
see
nothing
created.
So,
let's
start
by
deploying
some
target
clusters,
so
my
cluster
is
going
to
be
workload
cluster,
one
and
I'm
going
to
generate
the
Yammer
files
needed
to
deploy
this
I'm
going
to
start
running
the
cluster
30ml
file.
A
This
will
create
this.
The
target
cluster
within
our
kind,
a
resource
type
as
fast
as
workload
cluster
one.
Now,
let's
deploy
a
master
node
for
this
to
do
so,
I'm
going
to
run
the
control
plane
Tamil
file.
This
will
start
creating
a
virtual
machine
for
the
master
node
using
a
template
that
I
want
to
be
pre
deployed
within
vSphere,
using
a
new
Ubuntu
page
image.
So
that's
the
image
that
I'm
going
to
use
now.
A
A
Without
the
scene
I
installed,
the
node
status
for
the
target
cluster
will
show
not
ready.
So
let's
go
ahead
and
deploy
the
Calico
CNI
again
I'm
going
to
use
the
add-ons
30ml
file.
This
was
automatically
generated
by
the
cluster
API
vSphere
provider
component,
so
calico
is
installed.
After
a
couple
of
minutes,
you
actually
start
seeing
the
master
node
status
as
up
and
running
so
right.
Now,
it's
ready
now.
A
So
the
status
of
the
vSphere
cluster
is
ready.
Now,
let's
start
looking
at
our
AWS
environments,
so
I'm
going
to
switch
to
the
AWS,
folder
and
I'm
going
to
use
the
same
things.
The
same
fluid
workflow
for
a
vSphere
will
start
by
our
AWS
environment
files
and
I'm,
going
to
export
some
of
the
environment
variables
here
for
my
AWS
environment,
once
I'm
done
with
that,
we'll
start
deploying
the
infrastructure
components
needed
to
create
the
AWS
provide
a
specific
CR
DS
within
the
kind
of
question.
A
So
now
you'll
see
some
namespaces
with
AWS
a
or
cap
a
system
created
along
with
cap
V.
So
here
is
my
AWS
a
moment.
It
has
nothing
in
there
right
now.
So,
let's
start
deploying
some
target
components
here:
I'll
apply
the
cluster
30ml
file
to
create
a
cluster
called
Cappy
QuickStart
and
they
should
create
a
bastion
station
in
AWS.