►
From YouTube: Cluster API as Code - David McKay, Equinix Metal
Description
Don’t miss out! Join us at our upcoming event: KubeCon + CloudNativeCon North America 2021 in Los Angeles, CA from October 12-15. Learn more at https://kubecon.io The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.
Cluster API as Code - David McKay, Equinix Metal
Cluster API is a Kubernetes sub-project focused on providing declarative APIs and tooling to simplify provisioning, upgrading, and operating multiple Kubernetes clusters. Cluster API provides clusterctl, which can be configured with environment variables and allows the generation of Kubernetes manifests that describe your workload clusters. While this provides a great on-boarding experience, managing and wrangling more YAML isn't something we're all yearning to do. Fortunately, there's a better way. Introducing Cluster API bindings for TypeScript, Go, and Python. In this talk, I'll introduce you to managing Cluster API through your favourite programming languages.
A
My
name
is
david
mckay
and
I
am
a
cncf
ambassador
and
senior
developer
advocate
for
equinix
metal
and
I
am
from
glasgow
in
sunny
sunny
scotland,
I
have
a
menagerie
of
animals
in
my
office.
I
have
chancellors
vegas
a
fair
underdog,
I'm
also
a
prolific
live
streamer
streaming
multiple
times
per
week,
trying
to
cover
all
of
the
cloud
native
landscape
technologies,
hopefully
providing
learning
materials.
So
we
can
all
learn
together
and
of
course,
I'm
also
supporting
my
wonderful
covet
here.
You're
welcome.
A
A
A
A
A
A
A
A
A
A
A
Next,
there's
a
create
cluster
target,
this
one's
a
little
bit
more
robust,
but
this
will
generate
the
gamma
required
for
us
to
apply
to
our
management
cluster.
In
order
to
allow
the
controllers
to
create
our
new
workload
cluster,
we
specify
the
kubernetes
version
that
we
want
how
many
control
plane
nodes
we
want
and
how
many
worker
nodes
we
want.
A
A
A
A
A
A
Now,
inside
of
our
cluster
vehicle,
you
will
see
a
cube,
adm
control
plane.
This
is
a
custom
resource,
tells
cluster
api
how
to
get
a
control
plane
node
on
your
provider
of
choice.
Here
we
see
a
whole
bunch
of
shell
commands
that
are
required
to
configure
the
host
and
install
all
of
the
kubernetes
components.
A
Unfortunately,
yaml
is
not
the
best
programming
language
for
complex
logic,
and
we
seem
to
have
got
ourselves
into
a
bit
of
a
pickle
in
the
cloud
native
ecosystem
when
it
comes
to
yaml.
In
fact,
there
are
memes
all
over
the
internet,
but
how
you
know
to
be
a
devops
engineer
to
be
a
platform
engineer
to
be
a
kubernetes
developer,
is
to
be
a
yamo
developer
and
well
they're,
funny,
sometimes
incorrect
and
a
whole
bunch
of
other
things.
A
Let's
identify
a
real
problem
that
we
have
that
we've
gotten
ourselves
into
we've
got
helm.
We've
got
carville,
we've
got
capitan.
We
have
customize
to
help
us,
try
and
wrangle
this
yaml
into
something
that
is
much
more
fluent
to
work
with.
That
allows
us
to
handle
complex
logic
and
loops
and
templating.
A
The
cluster
api's
responsibility
is
not
to
provide.
You
know
air
economic
tooling,
to
generate
the
ammo
to
describe
those
clusters
and,
as
we've
seen
through
the
quickstart
whale,
it
does
offer
some
simple
mechanics
to
generate
that
getting
started
yaml
the
minute
you
need
to
be
able
to
make
your
own
tweaks
things
get
a
little
bit
complicated.
You
have
to
start
copying
and
pasting
your
own
yaml
to
get
the
kind
of
cluster
topology
that
you
would
want
or
expect
yeah
fine.
A
It
gives
you
a
control,
plane
cluster
highly
available,
but
it
only
generates
one
single
worker
pool
and
for
most
production
clusters,
you're-
probably
going
to
want
more
potentially
within
different
availability
zones
within
a
single
region,
with
a
variety
of
instance
types.
Some
descartes
some
memory
heavy
some
cpu
heavy-
that
really
are
tailored
to
your
workload,
we're
seeing
that
the
same
confusion
and
complexity
that
we
see
across
the
broader
kubernetes
ecosystem
for
deployments
and
templating
now
starting
to
come
to
the
cluster
api,
is
that
not
all
clusters
are
the
same
and
as
an
end
user.
A
A
And
that
means
that
I
want
something
that
is
flexible.
I
want
to
be
able
to
define
a
cluster.
That
is
the
size
I
want
that
uses
the
node
pills.
I
want
to
use
the
instant
type
that
I
want
as
the
operating
system
that
I
want
to
use,
because
maybe
there's
other
things
on
there
that
I
want
to
take
advantage
of,
I
think
more
importantly,
it
also
has
to
be
composable.
I
think
that
we're
in
a
stage
of
kubernetes
awareness
and
adoption,
where
we
know
that
having
one
giant
monolithic,
kubernetes
cluster
is
not
the
answer.
A
A
A
Lumi
allows
you
and
provides
an
sdk
to
work
with
the
language
you're
more
comfortable
with,
and
what
we
have
here
is
an
example
of
using
the
typescript
sdk
for
azure
to
spin
up
an
app
service
which
has
a
handler
an
anonymous
function.
My
business
logic
can
go
there
and
then
just
four
lines
of
code
to
describe
how
to
deploy
that
to
the
azure
ecosystem.
A
A
As
I
said,
polymer
supports
the
languages
you're
already
familiar
with
I'm
a
big
fan
of
using
typescript.
I
think
it
works
really
well
for
infrastructure
is
good
with
a
strongly
tight
but
dynamic
nature.
However,
this
is
cloud
native.
Go
is
an
option
as
long
as
you
don't
mind,
checking
for
errors
every
13
seconds
python.net
are
also
available
and
more
languages.
A
I've
heard
are
coming
soon
and
there's
one
secret
thing
that
launched
very
recently
from
the
bulimic
operation,
and
is
that
that
they
have
enabled
cross
language
sdk
runtime
capability,
meaning
I
like
typescript,
I
publish
libraries
in
typescript,
you
let
go.
You
want
to
write
your
infrastructure's
code
and
go.
A
Okay.
Let's
take
a
look.
So
what
I
have
here
is
a
brand
new
lumi
project
inside
of
my
kubecon
directory,
it's
configured
for
kubernetes
and
typescript,
which
means
that
it
comes
with
the
lumia
sdk
kubernetes
sdk
and
some
kubernetes
helpers
in
my
own
namespace.
I
have
access
to
all
of
the
cluster
api
resources
that
have
already
generated
and
published.
A
Now,
one
of
the
more
difficult
things
to
automate
with
the
cluster
api
is
that
initial
infrastructure
provision,
because
the
only
way
to
do
it,
is
through
a
cluster
control
init
dash
dash
infrastructure
packet.
It
then
requires
a
secret
to
exist
in
the
environment
that
tells
the
controllers
how
to
speak
to
the
cloud
provider.
A
A
A
Do
we
know
what
a
cluster
api
config
is?
Well
not
yet,
but
we
can
expand
that
and
use
our
autocomplete
and
we
can
see.
Oh,
it
wants
to
know
whether
we
should
install
cert
manager
and,
if
so,
which
version
it
also
wants
to
know
whether
we
want
to
enable
any
of
the
feature
gates
and
finally,
it
needs
a
kubernetes
provider.
A
So,
let's
just
quickly
run
through
this
one
by
one,
when
we
did
the
cluster
control
in
it
earlier,
we
did
see
that
it
installed
start
manager.
In
fact
it's
required.
So
I'm
just
going
to
say
true
yeah,
why
not
install
start
manager
what
version
well,
I
already
know
that
110
is
available,
so
I'm
just
going
to
drop
that
straight
in,
but
you
could
find
that
from
the
cluster
there
from
the
server
manager.
Github
repository
next,
oh
feature
games.
A
A
Can
I
get
and
finally,
we
need
a
kubernetes
provider,
I'm
going
to
leave
this
blank
for
just
a
moment
and
that's
it
that
will
enable
the
cluster
api
controllers
on
my
management
cluster.
However,
I've
not
provided
the
dash
dash
infrastructure
provider.
Yet
let's
do
that
next,
so
we're
going
to
pull
in
one
more
import.
A
Okay,
now
we
can
come
back
and
complete
this
we're
going
to
pull
in
the
packet
provider.
Again,
we
don't
know
the
api
up
front.
We
can
say
packet,
cappy
equals
capped.
Up
again
we
have
the
ability
to
create
a
control,
plane
or
initialize
the
management
cluster
just
like
before
it
needs
a
config
okay.
So
let's
take
care
of
that
api
key
first.
A
A
A
Next,
we
need
a
cluster
api.
What
is
that?
Well,
we
can
hover
over
and
see
that
it's
just
looking
for
some
providers
that
come
from
our
cappy
init.
Our
copy
init
actually
returns
a
set
of
manifest
so
from
here
we
can
see
cluster
api
dot,
cluster
api
and
finally,
there
is
a
cougar
nanny's
pervader.
We
ignored
that
above,
but
we're
going
to
take
care
of
it
now.
A
A
So,
of
course,
I
would
make
youtube
my
word
for
it.
Let's
actually
run
this
we'll
pop
over
here
jump
to
the
terminal.
We're
gonna
run
lumi
up
it's
going
to
work
out
from
those
functions
that
we
provided,
which
resource
have
to
be
created
within
the
management
cluster.
You
can
see,
there's
a
fair
few.
A
A
Now
one
of
the
things
the
polymer
does
is
try
to
ensure
that
what
we
apply
will
actually
become
healthy.
That
means
that
it's
probably
going
to
step
there
for
quite
a
while,
while
it
waits
to
make
sure
that
the
deployments
and
the
images
are
pulled,
the
pods
are
passing
all
the
probes.
The
services
have
endpoints
all
of
those
little
bits
and
pieces
that
normally
we
just
allow
the
kubernetes
reconciliation
loop
to
take
care
of.
A
So,
let's
jump
back
into
our
code
and
where
we
created
our
kubernetes
provider,
we're
going
to
make
a
few
small
tweaks
we're
going
to
open
up
the
arguments
and
we're
going
to
see
that
we
have
a
bunch
of
things
that
we
can
tweak
with
the
kubernetes
provider
for
one
it
doesn't
have
to
use.
Whichever
context
is
available
to
me
in
the
environment,
I
can
provide
my
own
cubeconfig.
A
A
A
We
can
add
and
layer
on
more
abstractions
to
make
our
list
easier.
You
can
see
that
there's
already
the
ability
to
create
a
control
plane
on
an
equinox
metal
cluster
that
has
the
configuration
options
that
an
equinox
metal
customer
would
come
to
expect
the
project
id
the
number
of
replicas,
the
machine
types,
the
facility
and
the
image,
and,
of
course
it's
not
equinix
metal
specific
and
in
fact
we
can
take
a
look
at
cap
d,
which
is
the
digital
illusion
provider
again
using
just
a
simple
init
command
and
a
config.
A
A
Okay,
so
what's
coming
next
well,
the
cd
kits
is
a
really
really
cool
project,
it's
very
similar
to
pilgrimage
and
that
it
exposes
a
multi-language
or
runtime
for
defining
and
creating
kubernetes
resources
generating
the
types
is
actually
a
lot
easier
with
cdks
than
it
is
in
polymer.
It
doesn't
require
an
external
command,
but
there
are
some
trade-offs
from
both
approaches.
A
A
A
And
I'd
like
to
see
more
use
of
open
policy
agent
for
testing
the
clusters
that
we
are
creating
the
plumbing
sdk
that
I've
provided
applies
some
basic
tests
to
ensure
that
all
of
the
feature
gates
are
interpolated
before
they
hit
your
management
cluster.
But
there's
a
lot
more
that
we
can
do
there
too,
and
I'd
like
to
see
more
providers,
I'd
like
types
generated
for
aws
and
for
gcp,
and
maybe
even
oracle
cloud.
Who
knows.
A
So
that's
my
talk.
I
hope
I've
given
you
some
food
for
thought.
Not
only
does
the
tooling
that
I've
shown
today
for
cluster
api
exists
and
can
better
our
lives,
but
it's
not
confined
to
cluster
api
either.
There's
no
reason.
We
can't
use
cdks
and
pollumi
across
our
entire
deployment
surface
for
kubernetes.