►
Description
- Documentation: https://docs.gitlab.com/runner/configuration/autoscale.html
- Blog post: https://fotoallerlei.com/blog/post/2020/autoscaling-gitlab-runners-on-hetzner-cloud/post
- CI autoscaling research: https://gitlab.com/gitlab-org/gitlab-runner/-/issues/27061
- docker-machine direction in GitLab: https://gitlab.com/groups/gitlab-org/-/epics/2502
- Hetzner Cloud curated lists: https://github.com/hetznercloud/awesome-hcloud
Workaround for Docker problem. runners.machine - MachineOptions
"engine-install-url=https://releases.rancher.com/install-docker/19.03.9.sh"
A
It's
almost
already
my
legacy
monitor.
A
C
C
So
you
probably
want
to
start
with
again
a
short
introduction
around
and
then
we
might
just
figure
out
what
to
do
or
what
to
talk
about,
and
I'm
asking
how
is
the
weather
in
lower
austria.
D
Snowy,
so
my
name
is
michael
wagner:
I'm
a
product
manager
and
a
software
engineer
at
a
company
called
zkw,
so
we
build
headlamps
for
the
automotive
industry
and
I
specifically
built
high
performance
computing
apps
we
see
plus
plus
so
cfd
engines,
raytracer
and
so
on
and
yeah.
So
I
would
hand
it
over
to
niklas.
D
B
Yeah,
my
name
is
citrus
meats,
I'm
a
detect
hero.
Currently,
I'm
working
as
a
senior
devops
engineer
for
company
called
swelty
we're
doing
a
lot
of
interesting
stuff,
so
we're
doing
a
lot
of
stuff
with
compliance
mostly,
and
I
doing
only
the
hot
topic,
so
I
do
blockchain
and
also
on
trivenitas.
So
I
mostly
like
to
do
the
fun
new
stuff
yeah
and
I
really
like
to
contribute
every
week
here.
A
I'm
david,
I
I'm
from
puppet
currently
with
all
the
branding
that
I
can
cram
into
a
video
background.
I
I'm
a
senior
engineer
on
the
content
team
responsible
for
all
the
puppet
content,
all
the
supported
puppet
content
on
the
forge
and
as
a
tech
lead
just
being
the
responsible
for
everything
technical.
I
guess
you
could
say
from
yeah.
C
Okay,
I'm
the
crazy
one
who
brought
everyone
together
here.
It's
been
10,
10.5,
10
and
a
half
months
now
with
gitlab
yeah
and
I'm
kind
of
trying
to
figure
out
what
we
can
talk
about.
What
we
can
learn
from
us
and
I
have
to
be
honest.
I
have
no
idea
how
we
bumped
into
each
other
gary,
but
maybe
you
wanna
wanna,
kick
off
and
introduce
yourself.
E
Okay
yeah,
so
I'm
gary
bell,
I'm
senior
developer
and
tech
lead
at
a
company
called
e-cigarette
direct.
We
sell
their
products
online
in
the
uk,
slightly
controversial
industry
for
some,
but
there
we
are.
I've
got
the
php
background
and
that's
what
we
build
our
platform
on
and
you
know,
use
git
lab
for
all
of
our
pipeline
stuff,
so
unit
testing
we're
gonna,
integrate
the
deployments
for
the
new
platform
in
the
next
couple
of
months
and
yeah.
E
I
I
love
gitlab
as
a
product,
so
I
blog
quite
a
lot
about
it
and
hopefully
can
guide
people
into
using
it
and
moving
away
from
other
solutions
just
because
I
think
it's
the
right
one
for
for
me
and
probably
a
lot
more
and
we'll
have
bumped
into
each
other
michael
on
twitter,
either
something
I
I
shared
or
some
comment
I
made
you
know
once
I
got
up
and
running
with
gitpod.
C
E
Yeah,
I
think
I
was
given
it
given
access
to
it
about
a
week
before
it
went
public,
so
that
was
pretty
interesting.
So
I
was
very
keen
to
get
up
and
running
with
that
and
had
a
blog
post
ready
to
go
and
then
giftpod
got
in
touch
and
said
we
haven't
done
the
press,
release
hover
saws
for
this.
Can
you
hold
off
a
couple
of
weeks?
It's
like.
Oh,
I've
got
a
complete
exclusive
and
I'm
not
allowed
to
use
it.
E
So
no,
it
was.
It
was
great
to
to
sort
of
get
introduced
to
those
guys
as
well,
and
I've
got
another
git
pod
post
coming
out
beginning
of
february,
I
started
you
know,
went
through
the
process
of
setting
up
a
completely
greenfield
project
with
just
to
sort
of
see
what
it's
like
for
somebody
just
starting
out
on
projects.
Is
it
a
viable
option
for
people
that
way
and
had
some
good
interactions
with
christian
that
get
pod
with
that.
C
That's
it's
great.
I
think
there
is
a
docker
rosenheim
meetup
which,
which
also
covers
gitport
and
rootless
and
and
other
things
coming
up
also
in
february.
I
just
don't
have
to
link
handy
now
and
I've
seen
that
max
joined
us
yeah.
C
No
worries
we
just
did
a
short
introduction
round,
which
means
say,
hi
and
who
you
are.
C
F
Max
yeah,
I'm
a
systems
engineer
from
germany.
I
recently
moved
to
berlitz
yeah.
I
work
at
sys11.
It's
a
company,
doing
managed
hosting
and
managed
kubernetes,
so
my
day
is
usually
spent
working
on
kubernetes
and
my
afternoons,
my
evenings,
often
as
well,
but
more
private,
stuff
and
private
projects.
I
hack
on
yeah
yeah.
That's
what
I
do.
C
Okay
nicholas:
do
you
want
to
try
the
hetzner
provisioning.
B
B
It
connects
around
yeah.
Let
me
check
I'm
not
so
prepared
right.
C
Now
give
me
one
minute
so
sorry
for
like
making
this
an
adventure-
maybe
maybe
the
others
have
a
suggestion
to
to
try.
So
one
of
the
ideas
was
to
like
install
gitlab
and
autoscaling
runners
and
try
how
things
work
or
not
work,
but
we
could
also
dive
into
yeah
anything
ci,
cd
or
best
practices
or
ops,
trace.
A
Can
you
can
you?
Can
you
give
me
a
quick
overview
of
how
the
auto
scaling
runners
would
work?
I
I
don't
necessarily
need
to
see
them
in
action,
but
just
like
how
do
I
spend
my
money
using
those
I
we're
we're
actually
running
into
the
problem
where
on
our
github
installation
or
on
our
github
pro
account
from
puppet.
We
are
running
into
the
limits
of
their
runners
and
I
I
just
want
to
know
how
how
we
can
do
that
better.
A
Yeah,
I
don't
care
like
if
I
want
to
make
it
better
with
github.
I
know
who
I
need
to
talk
to
internally
to
spend
more
money,
but
I
would
like
to
know
how
how
the
git
lab
action,
the
git
lab,
auto
scaling
runners
work,
because
that
that
sounds
a
lot
more
like
what
I
would
want.
C
Yeah
there
are
so
one
one
thing
you
can
do
is,
for
example,
you
use
the
docker
machine
executor,
which
which,
for
example,
spins
up
additional
virtual
machines
with
the
runner
pre-installed
in
aws
or,
for
example,
an
openstack,
and
there
is
also-
and
there
is
a
blog
post
from
max
actually
which
I'm
currently
trying
to
find.
C
Perfect
and
as
a
shameless
plug
yeah,
that's
nice.
I
I've
seen
you've
reposted
it
to
to
dev.t.o
as
well
so
yeah.
Let
me
let
me
share
my
screen.
We
have
this
picture
no,
this
window
so.
F
Okay,
yeah,
I
can
try,
it
has
been
a
while
it
worked
so
good.
I
don't
need
to
spend
any
time
on
debugging.
It
actually
give
me
a
second.
F
B
It
jumps
from
the
topic
that
they're
using
for
auto
scaling
the
docker
machine
and
doctor
machine
has
a
plugin
mechanism,
so
you
can
drop
in
your
own
drivers
and
by
default
the
detail
burner
doesn't
provide
free
hits
now
driver.
So
this
is
the
reason
why
you
need
to
get
in
different
images
of
official
declared
runner
image.
C
B
C
A
And
basically,
just
to
that
that
we
were
talking
about
right,
I
think
basically,
when
gitlab
triggers
aci
run,
it
would
go
to
that
docker
machine
thing
and
say
hey.
I
need
some
compute
to
run
this,
this
ci
run
and,
and
that
will
then
use
that
driver
to
get
a
machine
from
hetzner
and
and
execute
that
ci
right.
B
C
The
the
general
idea
is
that
you
can
like,
when
there's
lots
of
traffic
and
lots
of
chops
in
in
the
queue
that
you
spin
up,
additional
virtual
machines,
and
you
also
shut
them
down
afterwards,
and
one
thing
we
did
in
the
past
with
openstack
was
also
to
define
offline
times.
So,
basically,
the
idle
time
of,
like
you,
have
only
one
virtual
machine
over
the
weekends,
because
nobody
does
anything
over
the
weekend,
which
also
can
help
reduce
the
cost.
F
F
C
B
B
C
Yeah,
but
still
I
I
think,
I'm
using
this
or
this
somehow
for
my
personal
blog
and
also
for
for
a
different
hosting
thing,
and
for
me
it
was
like.
Oh
I'm
clicking
there
and
something
spins
up,
so
I
was
not
auto
provisioning
it
and
the
nice.
C
The
really
nice
thing
was
that
it
has
built-in
monitoring
or
like
simple
graphs,
to
see
cpu
and
io
and
and
things
like,
because
I
was
migrating,
a
blog
and
actually
a
forum,
and
I
was
was
not
sure
how
how
it
would
perform-
and
I
just
picked
and
said:
okay,
two
cpus
and
and
some
ram
would
be
totally
fine
and
it
doesn't
cost
that
much
so
it's
really
affordable
in
comparison
to
some
years
ago,
where
it
was
like
dedicated
host
or
something
else.
Oh,
I
it's
20
euros
a
month.
C
D
B
C
F
Yeah,
I
use
the
terraform
provider
from
hetzner,
so
developed
upstream
by
hezna
itself,
and
I
use
the
ansible
module
as
well.
It's
also
developed
by
hezna
and
their
csi
driver
and
the
controller
manager,
so
the
the
two
links
at
the
top
top
of
integrations
as
well.
So
you
need
to
use
them
if
you
want
some
more
native
kubernetes
support
on
it.
F
B
I
know
a
guy,
he
was
a
really
true
rapper
about
terraform
and
juventus
also,
and
it
was
yeah
I'm
I
probably
am
ready.
So
we
do
everything
live
and
we'll
see
how
it
goes.
C
That's
the
spirit.
Okay,
then
I
just
I
stopped
sharing.
C
If
you
leak
anything,
I
will
tell
you.
B
No,
no
I'm!
I
think
I
will
be
no
better
prepared,
because
I
do
it
on
a
different
monitor.
So
this
time
it
shouldn't
be
happening.
I
prepared
for
most
important
stuff
yeah
literally
because
we
were
talking
a
little
bit
about
the
architecture
and
we
could
probably
follow
much
slightly.
I
want
to
do
this.
B
Let
me
check
something:
okay,
so
because
you
asking
about
the
architecture
lately,
what
what
can
be
done
is
I
use
this
repository
right
now
on
github
from
appdarwin,
because
he
has
a
simple
diagram
right
now
and
it's
really
the
same
on
every
other
cloud.
So
what
we
will
do
now
is
probably
we
will
use
the
default
cloud
to
have
our
repository
and
connect
our
runner
there
and
literally
what
we
now
do
is
to
create
a
simple
instance
that
can
spin
up
these
vms.
B
B
You
can
see
there
are
no
servers
in
here
and
I
will
click
now
through
the
ui
literally
and
do
it
so
what's
really
cool,
we
could
also
do
it
in
terreform
or
something
like
else,
but
first
of
all
we
do
it
like
live
yeah
probably
can
choose
nova
locations,
so
we
will
probably
go
into
a
german-based
rotation
to
know
back
to
to
michael,
so
that
we
are
really
near
to
him
and
having
a
low
latency.
B
What
is
really
cool
in
the
meantime,
hetzner
has
pre-warmed
vms.
So
if
you're
using
the
standard,
vms
so
ubuntu
or
something
like
all
these
with
thunder
sign
literally,
you
will
get
them
really
fast
because
they
will
be
deployed
in
under
10
seconds.
So
it's
really
cool
for
doing
development
on
on
different
machines.
Yeah
so,
and
we
will
start
with
a
small
machine
because
we
don't
need
a
so
big
machine
for
that,
because
this
machine
needs
only
be
intended
to
spin
up
all
the
firms.
B
C
B
So
then,
I
need
to
get
access
to
the
machine
slowly.
This
is
probably
I
hope
this
is
the
fifth
standard
user
there
yeah
and
now
I'm
in
my
machine.
So
this
is
everything
I
need
to
do
so,
there's
nothing
on
it.
So
an
autocrat
is
there
probably
so
the
next
step
would
be
to
install
docker
a
better
way
of
that
is,
instead
of
using
it
right
now.
In
this
way,
let
me
check
how
to
minimize
it
again
and
you
can
also
provide
on
the
boots.
B
So
when
you're
creating
a
new
machine
open
it
creating
a
new
machine,
you
can
also
provide
a
cloud
in
it
configurations
that
will
do
all
the
steps
that
you
need
to
do,
for
example
like
automatically
creating
the
users
installing
docker
out
of
box,
so
that
you
have
an
immutable
instance,
and
you
can
work
right
out
of
the
way
on
that.
But
now
we
need
to
install
docker.
B
I
didn't
do
this,
okay,
so
right
out
of
works,
we
will
now
install
and
we
don't
need
to
update
old
versions.
So
we'll
get
him
back.
B
Let
me
know
where
my
terminal
yeah,
I
would
also
don't
need
sudo
right
now,
because
we
are
inserting
the
certificates.
B
B
Probably
in
the
next
cafe
also,
we
could
have
a
five
minute
declare
auto
station
runner
all
the.
B
We
are
currently
doing
so
afterwards.
We
install
all
these
patches
that
are
required,
so
these
are
packages
mostly
for
getting
the
right
software
checking
the
software
and
so
on.
We
can
now
executing
the
script
to
get
the
gpg
key
so
that
we
can
verify
that
the
packages
are
now
reliable,
yeah.
We
don't,
we
won't
check
it
literally
now
we
add
the
repository
of
docker
to
that
and.
B
Okay,
now
we
should
be
able
to
install
docker,
so
we
don't
need
to
set
it.
B
B
Cross
I'm
looking
for
the
link
from
max
okay.
I
got
it
nice,
so
everything
is
in
place.
We
have
docker
now
and
we
can
now
connect
it
literally
so
hopefully
are
doing.
Is
that
her
compose
no
package
these
days?
B
B
C
Yeah,
but
can
you
try
that
would
be
interesting
if
it
works.
C
B
B
B
Yeah
so
now
we
will
create
the
runner.
F
B
Mostly,
what
is
here
so
we
will
use
the
volume,
so
it
will
create
in
folder
destroyed
headset
config
that
we
need
to
handle.
The
okay
now
worries.
B
And
I
will
explain
in
the
meantime
mostly
what
is
interesting
about
all
the
runners
right
now
they
are
using
all
docker
machine,
but
docker
machine
is
mostly
not
maintained
anymore.
It
will
be
maintained
from
detailed
right
on
now
to
use
this
federal
machine
binary,
but
doctor
machine
was
intended
or
invented
by
docker,
but
it
dodger
itself
won't
maintain
the
structure
machine
mechanism
anymore.
So
now,
when
we
are
jumping
into
the
container,
hopefully
is
this
something
yeah?
B
We
can
jump
into
that.
I
have
a
bottle
of
that
and
trying
to
start
with
the
process.
Okay,
probably
we
can
now
see
here's
now
of
inner
process
and
we
can
see
that
it
runs
as
the
user
did
lab.
B
So
don't
use
a
privileged
user
for
that,
but
all
this
stuff
is
run
as
privileged
interesting
yeah
and
literally
what
I
want
to
show
you
when
you,
when
you
type
machine,
I
think
yeah
they're,
using
these
commands
literally
to
control
all
the
stuff
they
wrapped
this
into
the
clap,
stuff
and
howard,
can
see
the
driver
that
are
currently
active.
B
B
And
by
default
the
virtualbox
driver
will
be
pinned
up,
but
when
you're
now
asking
for
a
specific
driver,
for
example
for
the
for
the
headset
driver,
it
will
show
us
the
sub
commands
that
we
actually
use
for
the
headset
stuff.
So
but
I
don't
know
how
the
driver
is
called.
It
could
be
something
like
this
that
all.
B
So
the
doctor
machine
driver
that
your
machine
will
ask
in
the
headset
cloud
api
we'll
create
a
vm
will
put
on
all
the
steps
that
we
are
doing
now
by
hand.
Will
docker
machine
do
automatically
for
us?
Okay
and
vegeta
lebron
instructs
the
crew
machine
to
use
it.
So
this
is
the
concept
behind
the
auto
scaling.
B
Mostly
probably
it
should
be
now
that
the
user-
it's
not.
B
Because
now
you
can
see
also
these
message:
hey,
it
doesn't
in
the
default
path
and
all
the
drivers
are
prefixed
with
docker
machine
dash
driver
and
just
for
binary,
it's
really
the
same.
B
They
don't
have
special
any
outputs.
I
here
you
can
see
it
so
now
you
can
see
that
all
the
commands
that
we
are
currently
use.
These
are
the
special
commands
that
can
be
used
by
the
little
browner
to
instruct
also
hexner,
to
do
special
things
and
they
will
be
reflected
also
into
the
into
the
conflict.
Comma.
Mostly,
when
you
are
looking
into
the
part,
we
will
copy
this
from
the
blog
post.
So
I
need
to
know
where,
to
put
it,
I'm
in
the
container
right
so.
F
B
And
right
now
you
can
also
see
here
the
the
command
for
machine
options,
and
this
is
the
same
options
that
we
can
use
from
the
help
that
we
saw
before
so.
For
example,
here's
now
the
api
token
that
we
put
in
which
type
and
so
on.
B
B
Okay,
now
we
need
two
things.
We
need
the
api
token,
so
we
can
fetch
this
api
token
from
the
headset
side.
So
when
we
are
going
into
security
api
tokens,
we
will
generate
an
api.
I
think
we
need
read
and
write
access
because
yeah
we
need
to
create
resources,
so
we
need
also
to
have
right
access
and
gitlab.
B
In
and
now
the
last
missing
part
is
we
need
to
get
the
access
token,
and
probably
we
need
also
to
update
the
url.
B
We
will
do
it
right
now
with
declared
from
chrome,
because
it's
easier
in
terms
of
I
don't
want
to
set
up
right
now.
I
do
have
also,
but
we
can
use
it
afterwards
and
reduce
that,
because
I
need
dns
and
more
complex,
so
we
will
get
the
club.com
and
probably
on
github.com.
We
don't
have
the
options
to
use
sharedrunner,
so
we
design
for
all
our
environments
for
all
the
instances
that
the
users
are
currently
used,
because
the
clip
is
currently
providing
us
those.
C
You
can
totally
go
there.
You
have
permissions.
B
Yeah
mostly
so,
then
we
can
see
it,
and
I
hope
I
don't
export
anything
yeah,
it's
okay.
So
when
we
clicking
when
we
are
clicking
on
settings
the
icd,
we
have
now
the
option
to
install
group
runners.
So
this
is
the
stuff
where
that
we
need
to
put
into
our
little
runner
config
and
mostly
what
will
happen
afterwards.
Every
project
and
everyone
can
contribute,
can
use
these
runners.
We
have
an
also
different
option
would
be
to
do
this
on
a
project
level.
B
So
when
we
are
clicking,
for
example,
on
our
general
project
and
there
we
want
to
run
some
ci
drops,
we
could
go
also
to
settings.
Nci
cd
then
also
run
us,
and
you
see
here
is
a
different
token,
because
it's
a
specific
runner
only
for
this
project
and
yeah,
but
we
will
use
it
from
the
group.
So
we
go
back
use
this
from
the
group.
B
B
Okay,
yeah,
probably
now
we
can
check
the
docker
container
that
probably
don't
get
the
changes
directly.
B
E
E
B
Mostly
the
dash
v,
what
it
will
do
is,
it
will
removes,
also
managed
volumes
from
docker.
So
if
you
want
to
clean
up
your
docker
compose
file
automatically
with
all
the
volumes
attached
to
that,
you
can
use
fedex
v,
but
it
doesn't
work
for
bind
mount.
So
our
head
start.
Config
is
still
there,
because
it's
not
a
managed
volume
from
butter,
and
now
we
should
probably
see
him
a
lot.
It
works.
E
B
C
B
B
Yeah,
the
promise
is
a
different
one.
I
think
it's
I
forget
this.
We
have.
We
need
to
do
an
important
step
lately.
B
This
token
that
we
are
currently
using
is
not
viton
that
will
need
for
x's.
So
in
this
space
for
totem
in
line
10,
the
number
is
the
x's
token,
but
the
token
that
we
are
currently
receiving
is
the
registration
token.
So
what
we
need
to
do,
we
need
to
redisturb
the
runner
first.
It's
also
mentioned
in
the
blog
post.
I
overskipped
this
so
to
do
that
we
need
to
run
the
register
mode.
B
Now
it
will
append
it
yeah:
okay,
okay,
that's
nice
autoscaler,
so
we
will
provide
some
state
texts.
Mostly.
I
really
like
to
do
this.
I
try
to
crosstalk
to
see
that
better
in
the
ui
and
then
we
say
doctor
machine.
B
D
B
B
B
B
And
I
need
to
add
this
take
so
it
will
use
to
select
the
runner,
because
when
we
don't
do
this,
it
would
use
the
jobs
from
from
it
would
use
for
shared
runners
from
gitlab,
and
we
want
to
use
our
own
literally.
B
And
probably,
let's
check
heads
now
and
there
you
see
now
for
each
job
literally
and
all
runner
will
be
spin
up.
B
B
Locked
think
some
res,
but
not
the
buddha
blot,
so
you
would
see.
I
can't
show
you
in
the
meantime.
I
can
show
you
something
before
I
forgot
it,
because
I
talked
about
the
topic
that
it
uses:
structural.
B
B
And
now,
when
we're
attacking
doctor
machine
press,
you
can
see
now
the
machines
are
also
there
and
for
easy
jumping.
You
can
now
do
docker
machine
ssh
and
you
are
now
on
the
runner
machine
and
you
can
see
probably
you
know
all
the
jobs.
B
B
Now,
okay,
do
is
currently
do
some
preparations
in
the
background
because
the
job
doesn't
start
it.
So
let's
wait
and
the
ci
when
our
first
container
will
spin
up,
but
this
is
the
main
idea
behind
auto
stealing,
so
it
uses
literally
docker
machine
to
execute
auto
scaling.
B
B
E
B
To
use
it
there's
an
interesting
topic
about
that
that
I
would
want
not
to
mention
really,
I
think,
there's
an
issue
about
that.
How
the
future
of
vegeta
lebron
deployments
will
probably
change.
I
need
to
check
with
issues
one
minute.
B
More
so
because
let
me
check
now
where's
my
yeah,
so
here's
visually.
E
B
Also
open
it,
which
would
be
true
so
there's
an
autumn,
because
this
auto
stating
worked
for
most
of
the
customers,
but
it
doesn't
have,
for
example,
it
doesn't
have
out
of
a
box.
It
could
be
not
cross
effective
in
terms
of
okay.
You
need
to
run
it
at
least
one
hour
on
headstart
cloud,
but
probably
my
jobs
take
only
10
minutes
or
something
like
how
can
we
do
a
better
effectiveness
of
all
the
jobs?
B
All
the
stuff
is
certainly
right
now
mentioned,
but
current
the
current
state
is
that
detail
uses
the
shared
runner
for
itself.
So
all
the
shared
runners
that
you
are
using
are
also
using
the
docker
machine,
auto
driver.
There
are
also
some
window
runners
out
there
and
mostly
it
sees
it
will
be
maintained.
B
You
can
also
do
I
read
a
lot
of
stuff.
You
can
probably
also
do
it
with
having
senior
runners
on
auto
scaling
groups
on
each
of
these
club
providers
and
spin
it
up,
but
on
your
own,
but
these
outer
stadium
alternate
faded
up
is
really
easy
to
use
mostly,
but
it
seems
that
it
will
mostly
continued
currently
an
other
alternative.
B
If
you
want
to
scale
your
runners
is
that
you
use
two
anita's
for
it
on
some
parts
so
for,
if
you
have
simple,
builds
like
web
applications
building
or
something
like
that,
kubernetes
is
also
fun
yeah,
but
there's
also
you
can
check
it
also
because
I
think
invitative
runner
repository
this
information,
which.
B
C
B
B
B
B
B
B
Now
this
is
an
interesting
topic,
because
now
you
can
also
see
here
now
the
provisioning
steps.
What
it
really
do
is
like
it's
connected
via
sh.
It
will
spin
up
ubuntu,
mostly
and
then
installing
docker
copying
the
certificates
and
some
there
are
currently
some
problems
of
setting
up
for
certificates
on
the
docker
daemon.
F
B
It's
a
long
time
ago,
when
I
do
this,
it's
like
when
it
one
time
when
it
works,
I
don't
touch
it
anymore,
yeah
and
it
also
reduces
like,
like
mark
said
it
reduces
my
cost
from
60
euros
a
month
to
3
euros
or
something
like
that.
So
because
I
don't
have
so
many
workloads
that
needs
to
be
run.
Sadly,
I
need
only
on
some
time
and
for
this
auto
standing
really
great
in
terms
of
also
saving
costs,
not
that
I
need
to
have
a
many
feet
off
runners.
I
need
only
runners
on
some
point.
B
Yeah,
that's
true:
it
depends
on
the
use
case.
Yeah.
Really,
if
you
are,
if
you
are
sitting
on
your
company,
you
are
bare
metal.
Probably
then
it's
easier
in
terms
of
cost
effective
that
you
use
in
your
machines,
but
if
you're
in
a
cloud
environment
where
you
have
only
where
on-demand
is
expensive,
more
expensive
than
running
it
right
in
long-term,
when
running
on,
demand
and
long-term
is
really
expensive,
then
autosteering
could
be
a
good
way
to
solve
this
problem.
B
F
F
B
I
remember
because
right
it's
right
now,
interesting
when
I
run
docker
also
in
didn't
mode
in
gitlab,
I
don't
try
to
update
docker
with
every
update
anymore,
because
I
need
to
fix
it
every
time
again.
So
it's
quite
weird
so
currently.
For
me,
the
newest
version
also
not
working
okay.
So
then
I
restart
the
runner
again.
B
B
C
There
is
there
are
some
people
watching
right
now
and
they
will
try
it
as
well.
I
just
I'm
linking
your
blog
post
in
the
in
the
video
description
as
soon
as
possible.
C
B
Pipeline
and
most
important
check
if
the
servers
are
still
running,
delete
them
by
hand
to
them
because
they
aren't
controlled
anymore
and
then
you're
wondering
why
your
price
gets
high.
D
B
B
B
F
F
F
E
B
And
you
accept
yeah,
but
that's
really
the
essential
meaning
of
vegetables.
So.
B
And
it's
straightforward,
mostly
so
most
much
through
blog
posts,
it's
very
easy
to
do
this,
and
probably
you
also
can
do
this
on
your
own.
D
B
Now,
there's
a
kvm
driver,
but
it's
not
maintained
anymore.
Essentially,
okay,
it's
like
mostly
doing
this
stuff
on
bare
metal
is
more
like
tinkering.
So
it's
all
like,
like
my
favorite
naming
of
this,
it
smell
like
duct
tape
programming,
so
we're
using
duct
tape
for
everything
everything
works,
but
it
works
in
the
end.
It
was
also
scalable
for
the
use
case
that
we
had,
but
currently
was
this
approach.
I
wouldn't
do
this
anymore.
B
But
it
depends
so
the
library
that
I
mentioned
is
here:
it's
the
doctor
machine
driver
for
that.
B
B
F
C
I
think
there
are
ideas
about
writing,
writing
additional
custom,
executors
and
and
like
integrations,
but
it's
really
hard
and
yeah.
You
cannot
drop
something
which
is
used.
I
don't
know,
maybe
in
in
lots
of
installations,
although
all
over
the
world
for
now
it's
reliable
and
I
think
we
have
three
patches
inside
so
basically
technically,
it's
a
fork
somehow,
but
still
there
are
some
bugs
which
cannot
be
fixed.
As
far
as
I
know,
so
we
need
a
long-term
solution,
which
is
should
be
the
the
epic
discussion
to
follow.
D
E
B
But
most
important
like
every
technology,
you
should
choose
it
by
the
logo
and
docker
machine
has
a
really
cool
loader.
So
this
is
the
original
loader
of
docker
machine.
B
C
Yes,
thanks
a
lot
for
like
diving
into
this,
it's
great
to
to
see
that
it
works
so
lots
of
motivation.
Probably
we
can
either
install
a
gitlab
server
next
week
or
leave
it
as
a
home
exercise
to
patricia
hi.
C
F
It's
more
like
I
wanted
to
ask
you
about
a
future
topic,
but
maybe
just
after
we've
only
if
we
are
finished
with
the
outer
scaling
stuff.
B
C
F
The
original
reason
why
michael
asked
me
or
invited
me
to
this
meeting
like
a
year
back
or
half
a
year
back,
I
don't
know,
was
because
we
talked
about
k3s
on
hetzner
on
twitter
and
after
christmas,
I
started
to
hack
a
lot
of
errors
on
this
and
I
now
have
a
gitlab
pipeline
which
uses
where
you
just
give
your
hetsner
api
key
and
an
ssh
key,
and
it
will
use
terraform
to
create
vms.
F
Okay,
I
don't
think
we
should
do
all
of
it
in
one
session,
because
it's
quite
a
lot
at
least
if
you're
new
to
terraform
and
new
to
ansible
and
new
to
kubernetes.
Then
it's
a
bit
hard
to
do
all
the
stuff
in
an
hour
or
so,
but
we
could
start
with
the
terraform
and
ansible
stuff,
for
example,
and
then
another
week
install
yeah
kubernetes
in
it.
E
E
F
F
Yeah
exactly
yeah,
maybe
we
should
start
asking
hetsner
for
a
sponsored
account
where.
C
He's
supposed
to
vms
yeah,
I
think
lucas
cameling,
I
think,
has
retweeted
my
tweet
already
so
he's
he's
watching
or
maybe
watching
yeah
I'll
ask
him.
F
C
I
I
think
we
have
a
deal
to
be
honest.
So,
let's,
if
you
need
anything
till
next
week,
just
ping
me
otherwise,
thanks
for
everything-
and
I
would
say
we
say
bye
to
youtube
now,
write.