►
From YouTube: TGI Kubernetes 182: Karpenter
Description
Join Naadir Jeewa and Marko Bevc of Scale Factory to discuss new Kubernetes cluster autoscheduling solution Karpenter ( https://karpenter.sh/ ).
Episode notes at: https://tgik.io/notes-182
Photo by Ricky Kharawala on Unsplash
A
B
B
B
A
Let's
see
who's
around
happy
friday,
all
from
israel
from
home
thanks
happy
friday
to
y
hi,
martin
from
the
netherlands
from
saudi
arabia,
egypt
cool.
So
as
ever
our
first
thing,
oh,
I
should
post
a
link
to
the
notes
we
are.
The
notes
are
going
to
be
at
notes,
one
eight
and
let's
please,
let's
check
out
okay
yep,
that's
the
notes
so
feel
free
to
edit
in
real
time.
So
the
first
thing
we
are
gonna
do
is
our
week
in
review.
A
If
I
can
find
the
correct
things
now,
the
banners
that's
white
one.
So
there
we
go
all
right,
let's
so
first
things
first
in
week
in
review,
so
from
kubernetes,
quite
we've
had
a
couple
of
new
patch
releases.
One
thing
we've
that's
happened
in
the
last
week
is
docker
shim
support's
been
with
me.
I
probably
should
share
my
screen.
Let's
do
that
hold
on
let's
there
we
go.
A
There,
okay,
so
dr
shim
support
has
moved
from
cuba
adm
now.
Some
of
you
might
remember
the
sort
of
semi
controversy
around
this
when
it
was
first
announced
about
a
year
ago.
I
think
that
we
would.
This
was
going
to
happen
in
the
kubernetes
project
and
there
was
a
lot
of
confusion
around
what
that
actually
meant.
A
Yes,
so
don't
panic
is
the
answer,
so
doc
is
not
going
to
go
anywhere.
You
can
still
build
your
containers
using
docker,
and
what
we
mean
by
this
is
the
using
docker
on
its
own,
as
the
container
run
time
for
kubernetes
is
going
to
go
away
and
in
mostly
in
favor
of
using
container
d
actually
for
most
what
this
means
for
most
people,
which
docker
ultimately
uses
anyway.
So
really
nothing
really
changes.
It's
just
we're
just
removing
one
of
the
middle
people.
A
I
guess
in
between
like
container
d
and
kubernetes,
so
don't
worry
still
we're
still
expecting
people
to
use
their
favorite
tooling
to
create
images.
So
just
in
case
you
might
see
that
in
your
panic,
so
well
so
just
notice
in
the
cncf
sandbox
and
we
had
a
new
project
join
and
that's
devfile.io
which
I'd
not
seen
before,
but
I
think
this
is
around.
A
A
Jesus
anyway,
it's
it's
a
replacement
for
that
and
also,
I
think,
it's
also
a
bit
from
what
I've
seen
it's
a
bit
like
tilt.dev,
so
which
is
something
we
I've
used
a
lot
until
we're
using
cluster
api.
It
it's
a
mixture
of
actually
using
stala
compost.
That's
right!
Darker
compost,
that's
the
one!
Yes!
So
this
is
kind
of
like
docker
compose
and
the
bit.
I
think
there's
been
a
couple
of
other
similar
sorts
of
projects
as
well.
So
it's
another
one
in
that
space.
So
let's
join
the
cncs
sandbox
people
interested.
A
We
might
do
tg
ak
on
this
might
take
give
it
give
it
a
spin
find
out
what
it's
all
about.
What
I'm
really
familiar
with
is
tilt
which
uses
the
starlark
language,
and
we
use
that
a
lot
in
in
cluster
api
and
but
it
says
compose,
is
very
light
alive.
You
can
push
from
compost
to
ecl
or
aks
yeah.
Thanks
for
that,
I
stand
corrected.
A
Yeah
cool
is
there
and
if
you
haven't
seen-
and
please
don't
all
just
sort
of
start
watching
this
instead,
like
I,
I
know,
like
you-
know,
youtube
short
attention
spans
and
all
them
fickle
viewers.
You
know
it's
not
like.
We've
got
the
sponsorship
spots,
you
know
not
gonna,
do
any
here,
we're
sponsored
by
skillshare
or
brilliant.org,
or
anything
like
that,
so
you
can
stick
around,
but
the
kubernetes
documentaries,
just
out
their
first
part,
was
premiered.
Earlier
today
I
haven't
seen
it
yet.
A
It's
got
a
lot
of
the
founders
from
kubernetes
suggest
everyone
watches
it,
but
not
right.
Now.
Okay,
later
all
right.
So
today
we're
going
to
talk
about
carpenter,
which,
which
has
been
on
the
horizon
for
a
while
now
I've.
I've
certainly
had
some
conversations
with
aws
around
this
previously
talking
about
how
we
might
use
it
in
cluster
api,
but
yeah,
it's
I
think
they
did
a
formal
announcement
at
the
end
was
it
I
think,
possibly.
B
A
My
personally
I
develop
on
the
kubernetes
project
itself,
but
as
far
as
I
don't
use
it
in
production,
much
actually
the
last
couple
of
months
I've
been
doing
design,
stuff
and
other
bits,
so
I
haven't
actually
used
kubernetes
for
ages,
so
this
is
going
to
be
fun,
isn't
it
as
we
play
around
so
I
think
the
way
I'm
going
to
play
this
is
revisit
cluster
with
a
scalar,
basically
as
you're.
Well,
probably,
people
are
sick
of
me
going
on
about
I'm
from
the
cluster
api
space.
A
So
I'm
going
to
redeploy
cluster
autoscaler
with
cluster
api
and
then
we'll
take
a
look
at
that
and
go
through
the
shortcomings
and
then
we'll
switch
over
to
carpenter
on
eks
for
reasons
that
I'll
get
into
later
and
yeah
and
go
through.
Why
did
what
the
difference
are
why
we
might
want
to
support
it?
Support
cluster
api
using
carpenter,
yeah
and
just
get
some
ideas
see
what
that's
about
so
yeah.
Does
that
work
for
you,
marco.
B
A
Yeah,
thank
you
valid
for
dropping
the
link,
so
there's
a
talk.
The
talk
that
marcus
mentioned
was
from
ellis
tan
and
petit
kudia
from
amazon
in
kubecon
eu
2021
yeah.
It
was
ls
that
I
had
talked
to
previously
about
this
yeah.
So
all
right.
So
if
I
go
to
my
terminal,
so
I
have
spun
up
both
clusters.
I
we'll
just
close:
it's
got
eks
cluster,
which
has
spun
up
with
dks
cattle.
A
A
A
A
A
A
A
Probably
shouldn't
have
been
yeah,
so
I
was
yeah,
formerly
a
reviewer
for
the
prs
that
were
coming
in
to
the
cluster
with
this
scale
across
the
api
provider
right.
So
I
think
when
this
first
started,
you
had
to
run
two
copies
of
the
cluster
autoscaler
one
in
your
management
cluster,
one
in
your
actual
cluster.
Today
you
only
need
to
do
it
in
the
one
place
and
that's
because
we
can
set
this
setting
so
we're
gonna
actually
run
the
autoscaler
on
in
my
kind
cluster,
on
my
laptop.
A
So
in
production
usage,
you're
gonna
have
one
permanent
management
cluster,
which
is
probably
going
to
be
in
aws,
and
that's
going
to
manage
lots
of
other
clusters
that
create
underneath
it,
and
you
would
just
install
auto
scan
on
that.
I've
not,
and
there
is
a
process
in
which
you
can
move
resources
from
your
local
machine
over
to
a
newly,
create
created
workload,
clustering,
converting
management
cluster.
We're
not
going
to
do
that
today,
because
it's
a
bit
of
a
pain
there
are
tools
to.
There
is
a
see
there
is
a
cluster.
A
A
Basically,
if
I
did
this,
it
would
convert
that
cluster
that
I've
ma
made
into
its
own
self-managed
management
class.
Then
we'd
run
it
all
together,
but
for
the
purposes
of
this
and
to
sort
of
simulate
how
you
would
do
this
for
real
we're
going
to
pretend
that
my
local
docker
based
kubernetes
cluster
is
a
permanent
management
cluster
and
that's
where
you
would
run
one
autoscaler
that
manages
all
of
the
other
clusters.
A
A
A
Yeah,
so
I
was
just
going
to
deploy.
I
already
have
that
workload.
So
uvh
has
a
nice
little
demo,
so
I'm
just
going
to
use
it
also.
I
do
these
are
not
permanent
clusters.
So
all
right.
So
let
me
okay.
One
thing
I
need
please
watch
out
and
tell
me
off
if
I'm
getting
up
going
to
the
wrong
context,
because
I've
done
this
like
five
times
already
today,
deploying
things
into
the
wrong
place
right.
A
It
doesn't
matter
like
I
mean
basically
what's
going
to
happen.
Well,
if
we
have
a
look
at
what's
happening
on
that
other
cluster,
if
we
having
a
bad
bad
time,
I
think
it's
yeah
there
we
go
it's
incredibly,
we
can
have
it
look
at
what's
why
it's
in
and
it
should
be
pretty
yeah
yeah.
I'm
I'm
not
convinced
that
the
output
of
this
is
particularly
helpful
today,
but
once
you
do
get
scroll
all
the
way
up
to
the
top,
it's
fairly
obvious.
A
A
B
B
A
B
B
A
A
Yeah,
I
I
don't
know
if
that
counts
as
a
heftier
project.
I
think
that's
more
or
less
just
someone
that
hemtia
did
that
yeah
vlad
goes
auto
scooter,
it
does
have
auto
discovery,
but
it
needs
certain
tags.
Yes,
these
ones.
So
so
on
this
bus
there
I've
got
a
machine
deployment
and
I
had
already
manually
scaled
it
to
one
earlier
right.
A
A
These
specs
I
forget,
but
I
just
pick
it
because
it
it
sounds
like
it's
not
going
to
crash,
so
I
just
don't
know
we're
using
an
upstream
cis
that
value.
This
is
why
I
use
that
one
or
you
might
be
using
2x
large,
I'm
not
sure.
I
know
it's
not
so
small
that
once
you
deploy
like
cni
and
stuff
that
it
doesn't
just
start
falling
over
right,
so
we're
gonna
add
the
metadata
which
let's
go
back
to
the
docs
okay.
I
need
this
one
annotations.
A
A
A
A
A
A
A
A
A
A
B
A
A
A
A
A
A
The
question
valid:
are
you
following
the
aws
cluster,
auto
scalia
provider?
No,
I
am
following
the
cluster
api
provider
for
cluster
autoscaler,
which
is
supposed
to
be
infrastructure
agnostic.
It
does
come
with
some
limitations,
it
mean
there's
also.
I
want
to
look
at
carpenter
because
the
us
api
authorizator
doesn't
know
about
things
like
what
instance
type
it
is.
It
doesn't
know
if
it's
doesn't
know
like
if
it's
got
gpus
or
whatever.
A
A
A
For
that
you
know
to
then
join
the
kubernetes
cluster,
there's
a
bunch
of
stuff
that
happens,
but
so
cluster
autoscalers
only
interface
is
a
hook
into
the
workload
cluster
to
be
able
to
monitor,
like
pods,
that
are
waiting
to
be
scheduled,
etc,
and
I
hook
into
the
management
cluster
side
to
be
able
to
scale
machine
deployment
resources.
It
doesn't
need
any
other
credentials
than
that,
so
it
operates
on
its
own.
So
I
don't
have
to
do
anything
with
iem
beyond
what
I've
already
given
to
cluster
api.
A
B
A
B
A
A
B
A
A
A
B
B
As
we've
seen
with
the
cluster
auto
scale,
one
of
the
reasons
why
you
probably
want
to
go
with
something
else
rather
than
cluster
autoscaler
is,
is
exactly
the
reason
we
seen.
So,
if
you
know
your
workloads,
don't
always
kind
of
match
the
resources
you
have.
This
is
obviously
one
big
limitation
with
cluster
scale
or
similar
solutions
in
this
space
right.
B
So
it's
not
just
the
cluster
autoscaler,
probably
worth
mentioning
the
reason
why
we
showed
you
the
cluster
autoscaler,
because
this
is
kind
of
let's
call
it
a
de
facto
kind
of
auto
scaling
solution
out
there,
or
at
least
the
solution.
That's
mostly
most
popular
at
this
point,
but
you
know
in
case
you're,
adding
you
know
things
that
don't
fit.
B
Add
those
resources
in
your
cluster
based
on
the
workloads
you're
trying
to
schedule,
and
there
are
other
kind
of
kind
of
advantages
as
well.
So
the
speed
is
a
big
advantage
as
well,
so
with
the
cluster
autoscaler
right.
You
need
to
wait
until
you're
in
aws,
auto
scaling
group
figures
out.
Oh,
I
need
to
scale
up
it.
That's
instances
in
so
all
that
kind
of
you
know
procedure
can
take
up
to
like
maybe
like
three
to
five
minutes.
I
guess
depends
on
the
oh
thanks,
dom
yeah.
B
The
note
group
is
a
concept
in
the
eks.
Yes
correct,
but
it's
implemented
with.
You
know
using
autos,
sorry,
auto
scaling
groups
which,
like
I
said
it,
can
take
up
to
like
five
minutes
to
kind
of
provision,
your
resources
based
on
what
you're
requesting
which
region
and
other
bits,
whereas
with
the
you
know,
carpeter,
it's
actually
using
the
direct
api
access
and
it's
using.
B
I
think
it's
a
api
call,
that's
using
its
fleet
create
fleet
and
that
literally
requests
a
fleet
of
resources
for
you
using
the
api
calls
and
they
can
they're,
probably
spun
up
in
this
in
the
quickest
way
possible.
I
would
say
that
you
can
actually
get
those
resources
available
from
aws
and
as
they're
being
provisioned.
B
B
Sorry
not
region,
easy
yeah,
you
guys
already
have
so
the
the
easy
where
a
carpenter
actually
provisions
the
the
notes
in
exactly
the
same
region
where
you
actually
need
it,
which
is
also
a
big
advantage
there
and,
like
we
mentioned
before
the
nodes
that
you're
getting,
are
actually
the
right
size.
So
with
the
cluster
autoscaler,
you
would
always
end
up
with
the
same
type
of
nodes
that
the
original,
auto
scaling
group
or
the
template
was
used,
whereas
with
carpeter,
it's
actually
using.
I
think
they're
calling
it
like
a
really
fast
kind
of
controller.
B
That
kind
of
it's
using
a
bin
packing
algorithm,
that
kind
of
tries
to
figure
out
and
kind
of
figure
out
which
resources
can
actually
provision
in
order
to
fit
all
the
specific
parts
that
need
to
schedule.
So
it
would
actually
use
the
optimized
instance
size
that
would
satisfy
the
the
need
for
scheduling
your
workloads,
which
is
also
kind
of
cool
as
well.
B
So
obviously
it
will
provision
the
you
know
the
nodes
from
the
list
that
you
provide,
but
at
the
same
time
it
will
pick
the
optimal
one
for
the
specific
specific
need
that
you
have
at
this
point.
So,
for
example,
if
you
need
to
provision
a
single
part,
you
might
end
up
with
a
really
small
instance.
If
you
have
like
a
a
large
amount
of
pots
or
a
huge
one
like
on
the
deer,
show
that's
before
right.
A
Cool
yeah,
just
yeah
thanks
for
that
ellis,
is
saying.
Carpenter
has
a
full
scheduler
implementation.
It's
also
scheduler
is
only
in
the
loop
when
capacity
already
exists.
Okay,
there's
some
questions
about
azure,
yeah,
so
azure
uses
vm
scale
sets
you
kind
of
have
to
do
it
in
azure
as
well,
because
so
there
is
a
difference
in
actually
one
thing
I
like
about
azure,
not
too
big
obvious.
It's
like
you,
can
put
everything
in
the
resource
screen.
A
You
can
also
hit
delete
on
a
resource
group
and
everything
goes
along
with
it,
which
is
really
nice.
When
you
want
to
clean
up,
you
don't
have
to
use
tools
like
aws,
nuke
and
stuff.
Now
there
is,
you
can
kind
of
use
the
resource
tagging
api
to
do
some
of
that
now.
But
one
of
the
limitations
around
resource
groups
in
azure,
however,
is
that
there
is
a
it's
like
some
weird
number
like
you
can
only
have
about
834
resources
in
it
or
something
it's
some
weird
limit.
Anyway,
every
vm
counts
towards
that
limit.
B
A
So,
if
you've
wanted,
if
you
want
to
do
a
large
cluster
in
azure,
you
absolutely
have
to
use
vm
scale
sets
and
from
a
cluster
api
perspective.
That's
implemented
in
using
something
called
a
machine
pool
resource
which
I
don't
think
the
cluster
auto
scaler
quite
yet
supports,
because
there
needs
to
be
additional
information
for
the
cluster
authenticator
to
figure
out
what
what
the
machine
type
is
and
whatever.
So
I
think
today
what
happens?
Is
cluster
autoscaler
on
the
cluster
api
context?
A
So
there
is
a
design
document
in
the
cluster
api
project
to
give
more
information
around
how
that
would
work,
and
then
that
would
allow
asgs
essentially
to
work
with
cluster
api,
but
class
api
based
cluster
auto
scada
today
does
not
use
auto
scanning
groups
or
vm
sets
in
it.
Lets
cluster
api
creates
machines
on
its
own
there's
a
question
from
changuin:
can
the
user
customize
the
node
size
and
type
to
optimize
the
cost.
B
Oh
yeah,
absolutely
as
you
I
mean
we're,
obviously
going
to
see
it
kind
of
more
more
a
little
bit
better
as
we
go
through
the
example,
but
there's
a
concept
of
provisioner
so
which
is
defined
through
the
crd
and
in
the
crd.
You
can
actually
define
a
list
of
instances
that
you
want
to
provision
from,
so
you
can
actually
limit
it
down
to
a
certain
set
of
instances
that
you're
happy
to
have
provisioned
and
obviously,
when
you're
provisioning
workloads
they
need
to
fit
into
that
those
kind
of
instant
sizes.
B
B
What
I
what
I
really
like
about
carpet
comparing
to
cluster
autoscaler,
is
it's
completely
decoupled
from
the
from
the
scheduler,
so,
for
example,
if
you're
using
cluster
autoscaler,
you
actually
need
to
use
the
same
version
than
the
kubernetes
version
that
you're
currently
running
it
on,
whereas
with
carpenter,
it's
completely
decoupled.
So
it's
not
really
using
any
of
the
kind
of
dependencies
on
the
scheduler
itself,
which
is
quite
nice,
but
at
the
same
time
it
is
working
quite
closely
together
with
the
scheduler.
B
A
Yeah
yeah,
I
I
didn't
realize
that
was
the
reason
why
the
class
auto
schedule
is
so
tightly
coupled
to
the
kubernetes
version.
It's
certainly
been
a
pain
for
us
in
terms
of
it's
just
yet
another
dependency
that
we
need
to
think
about
when
we're
like
from
a
vendor
perspective
or
from
like
versioning
all
the
components,
it's
yeah
another
one.
We
need
to
take
into
consideration
whenever
kubernetes
gets
spun.
I.
B
B
There
are
some
kind
of
rough
edges
around
there
and
there
is
an
issue
opened
and
even
though
it's
gonna
be
merged,
for
example,
the
way
how
the
merging
process
works
it's
going
to
be
merged
in
the
next
version
of
cluster
autoscaler,
which
is
1.24,
and
it's
even
gonna,
made
it
in
1.25
or
something
like
that
to
the
eks,
which
you
know
you
can
imagine
that
the
you
know
the
release
cycle
is
quite
long
if
you're
waiting
for
a
feature
that
will
make
it
to
your
eks
cluster.
So.
A
A
A
B
I
think
how
it
currently
works,
it
just
provisions
using
crate
fleet.
I
believe,
if,
if
I
remember
correctly
from
the
initial
talk
that
was
posted
before
in
the
comments,
it
was
explained
that
they
were
kind
of
contemplating
between
one
of
another
kind
of
api
call,
basically
they're
literally
the
same
thing,
so
they
just
decided
to
go
defeat,
but
it
it
should
offer
the
same
functionality.
A
B
A
A
B
B
A
A
A
B
B
A
A
Confirmation
templates
a
lot
of
the
same
things
or
you
can
just
run
create,
and
it
just
does
it
for
you
just
love
the
same
thing
except
a
bit
more
stuff
because
we're
managing
the
pcs
as
well
all
right,
so
that
stack
was
created.
We
now
need
to
do
that.
So
is
this,
because
is
this?
I
am.
Is
this
fiddling
around
with.
A
Someone's
got
some
time
might
be
worth
creating
finding
an
issue
for
that
one,
oh
yeah,
justin
just
said
they
create.
I
am
wood.
Come
on
modifies
the
aws
off
conflict
map
all
right
yeah,
so
it's
with
aws.
I
am
authenticated,
then
yeah.
That
makes
it.
I
guess
we
can
just
take
a
look
at
that
config
map
after
I've
just
won
this.
Why
don't
we
take
a
look
at
before
and
after
okay?
Where
is
that
config
map.
A
B
B
A
B
B
A
A
A
I
got
a
lot
of
output
there's
a
lot
of
so
this
is
just
a
dev
account
to
be
fair,
but
that's
a
load
of
additional
garbage
in
this
dev
account
for
reasons
yeah.
That's
fine!
So
I'll
put
my
screen
back
there
we
go,
so
we
got
that.
That's
that
node!
Well,
blah
blah
blah!
That's
that's
why
we
wanted
the
account
id.
B
A
A
A
B
A
Yeah,
so
the
way
this
is
work
is
we
nee.
We
need
a
way
to
make
sure
not
any
old
machine
is
joining
your
kubernetes
cluster,
because
that
could
be
bad.
So
we
spin
up
a
machine
with
an
im
role.
It's
going
to
have
some
credentials
from
the
instance
metadata
service,
then
to
authenticate
the
kubernetes
cluster.
It
does
and
it
doesn't
call
aws
sds,
get
caller
identity,
but
it
creates
a
signed
request.
So
aws
uses
hmac
the
aws
hmac
v4
is
its
signing
mechanism
for
requests.
It
creates
the
site.
A
A
They
have
credentials
valid
for
this.
I
am
role
and
I'm
going
now.
Gonna
look
it
in
my
mapping.
It
then
looks
it
in
the
config
map
and
says
right
if
someone
comes
in
and
they
are
able
to
present
a
sign
request
that
matches
this.
I
am
role,
then
we,
I
will
issue
a
service
account
token,
which
is
a
member
of
these
groups
to
beat
stratege
group
with
this
identity,
and
this
just
happens
to
be
exactly
what
is
required
for
kubler
to
be
able
to
register
itself
against
the
control
plane.
So
that's
how
this
is
working.
A
Right
so
we
got
that
next
bit
is
and
whatever
the
helms
that
I've
not
used
helm
for
like
a
million
years,
so
that's
going
to
be
fun
right.
We
need
to
create
a
so
now.
We
need
to
create
an.
I
am
roll.
I
like
to
now
be
coming
to
the
oidc
bit
bit.
We're
going
to
create
a
service
account
for
use
with
carpenter,
so
competent
itself
needs
permissions
to
create
one
easy
to
run
fleets
and
all
those
api
calls.
So
we
are
now
going
to
do
that
bit.
A
A
A
B
B
A
B
A
A
A
A
So
from
people
not
familiar
with
the
oidc
stuff,
so
this
is
kind
of
based
on
bits
which
were
introduced
in
what
kubernetes
121
120.
I
think
so
kubernetes,
because
oidc
has
kind
of
been
used.
In
a
quite
few
places.
There
was
the
support
added
to
make
kubernetes
acting
as
an
oidc
provider,
and
once
you
do
that,
there's
the
assume
role
with
web
identity
federation
api
in
aws,
which
allows
you
to
exchange
oidc
tokens
for
aws
credentials.
A
So,
given
that
kubernetes
can
absolutely
dc
provider,
we
can
make
that
kubernetes
cluster
trusted
for
aws,
and
then
we
can
then
have
the
ability
to
swap
service
account.
Kubernetes
service
account
tokens
for
im
world
credentials,
and
then
there
is
a
web
hook,
which
is
called
that
I
forgot
what
ursa
stands
for
yeah
there's
an
eks
pod
web
hook,
identity
thing
that
can
take
annotations
off
of
service
accounts,
to
exchange
them
for
iem
roles
and
that's
kind
of
what
this
is.
A
A
A
B
A
A
B
A
A
A
B
A
A
A
A
B
A
B
A
B
A
A
A
A
B
B
B
A
A
B
Yeah
yeah,
no,
no.
I
think
it
needed
some
time
to
pick
it
up,
but
obviously
there
is
a
pod
that
has
been
bound
to
a
node
that
has
been
provisioned
and
if
you
look
at
the
locks
you're
going
to
see
that
it
picked
up
r4
large,
so
that
was
kind
of
the
optimal
instance
for
the
workload
that
we're
looking
for.
B
B
B
B
A
B
A
B
A
A
A
Oh,
I
forget
his
name,
joe
jojo
someone.
Oh
my
god.
My
memory
is
terrible,
but
go
away
from
cluster
api
for
a
week,
and
this
is
what
happens
yeah.
So
we
have
had
some
conversations
about
doing
that
in
class.
I,
it
would
be
a
migration
because
you
know
with
people
we've
got
one
set
of
iem
permissions
and
they've
been
using
that
forever.
A
A
We
could
enable
cluster
api
provisioner
that
works
on
aws
through
and
carpenter,
wouldn't
need
any
permissions,
and
then
we
could
start
looking
at
how
to
support
vsphere,
for
example,
like
vsphere
would
be
quite
interesting
right
because
in
vsphere
you
can
you
basically
have
a
like
a
slider
like
a
moving
slider
for
the
mountain
memory
or
cpus.
You
can
almost
get
a
sort
of
fargate
type
experience
where
you
can
provision
a
single
node
for
that
single
pod,
which
has
exactly
the
right
sea
view
and
exactly
the
right
memory.
A
B
A
A
B
A
A
A
B
A
A
B
A
Yeah,
I
think
it's
probably
just
to
say
everyone's
clear.
I
had
some
conversation
with
some
users
in
earlier
in
this
week.
There
are
some
limitations
with
carpenter.
At
the
moment
I
mean
it
is
it's
a
fairly
early
stage
project?
So
still
I
mean
it's
ga
from
age
respective,
but
it's
still
an
alpha
api.
There
is
still
only
one
provider,
the
aws
one
but
yeah
just
be
aware,
like
pod
affinity,
pod
anti-affinity
is
not
yet
supported,
so
there
are
some
limitations
there.
B
I
mean
the
one
that
I
kind
of
most
commonly
here
is,
I
think,
currently
the
the
the
node
storage
that
is
provisioned.
It's
all
it's
kind
of
baked
to
20
gig.
Now
so
the
launch
template,
that's
using.
That's
used
it's
actually
having
that
predefined.
Obviously
you
can
get
around
it
by
specifying
a
custom
launch
template,
but
it's
currently
not
supported
in
the
provider
directly.
A
A
Okay,
so
there
are
limitations.
Just
beware:
the
scheduler
is
not
100
complete
well
today,
and
I
think,
maybe
probably
then
this
might
need,
if
it's
not
in
here,
which
probably
might
be
worth
making
that
clear
in
a
documentation
probably
like
what
are
the?
What
are
the
limits?
What
are
the
limitations?
What
does
work,
what
doesn't
work
just
so
it's
clear
to
you
end
users.
I
think,
because
otherwise,
this
just
for
my
own
sort
of
open
source
experience.
You
don't
make
that
clear.
A
B
A
B
B
It
for
quite
a
while
now
do
we
quickly
want
to
try
something
really
quickly
like
what
at
least
I
found
really
a
nice
feature
as
well.
So,
okay,
they
do
provide
a
finalizer
on
the
note.
So,
for
example,
if
you
go
to
the
console
and
just
if
you
try
to
delete
the
note,
it's
interesting
that
it's
actually
having
a
finalizer
on
it
and
it's
actually
trying
to
drain
the
note
like
gracefully,
which
is
kind
of
a
nice
feature
as
well.
B
B
A
Didn't
check
that
yeah
I
got
deleted:
okay,
cordon
node,
okay,
yeah
cool,
so
yeah,
so
that's
similar
functionality.
What
we
have
in
cluster
api
as
well
so
in
cluster
api.
If
you
delete
a
machine
then
it
would
start
doing
the
same
sort
of
thing.
I
guess
the
benefit
of
this
is
we
get
that
bin
packing
quite
quickly
as
well?
A
That's
pretty
nice
all
right!
Maybe
we
should
call
it
a
day.
I
think
I've
been
going
for
our
fifth
day.
I
think
that's
a
good!
Let
let
you
go
to
sleep,
and
I
can
also
I
mean
I've.
I've
had
multiple
monster
energies,
so
I'm
pretty,
unfortunately
not
being
able
to
sleep
but
yeah.
If
you've,
let
me
be
a
normal
youtuber
and
say
you
know:
if
you've
enjoyed
the
show,
then
click
click
like
we're,
not
sponsored.
A
B
No,
I
have
to
say
I
really
enjoyed
the
session.
Really
thank
you
for
having
me.
It
was
great
fun
kind
of
you
know,
doing
it
from
the
scratch,
and
maybe
you
know,
like
you
said
you,
you
haven't
really
had
an
experience
with
it,
so
it
was
really
nice
to
kind
of
get
across
all
those
bumps
that
you
know.
Maybe
users
would
usually
get
across
if
they
deployed
the
first
time
around
so
yeah
which
good
stuff.