►
From YouTube: CloudNativeTV Cloud Native Classroom - Tinkerbell
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hello,
everybody
welcome
to
the
first
episode
of
my
fancy
new
show
on
cloud
native
tv.
This
is
cloud
native
classroom.
My
plan
for
these
is
to
go
through
the
cncf
sandbox,
because
there
are
a
ton
of
projects
in
the
sandbox.
I
don't
know
what
most
of
them
do.
I
think
most
people
don't
know
what
most
of
them
do
and
I
think
most
of
the
projects
would
like
people
to
understand
what
they
do
and
why
they're
useful.
I
am
going
to
be
coming
at
this
from
like
a
very,
very
beginner
approach.
A
So
if
you
kind
of
only
barely
know
what
kubernetes
is-
or
you
mostly
know
what
kubernetes
is,
but
you
definitely
don't
know
what
any
of
these
like
ancillary
tools
are.
This
is
the
one
for
you
before
we
start.
I
have
to
say
that
this
is
an
official
cncf
live
stream,
which
means
that
we
are
bound
by
the
cncf
code
of
conduct.
A
This
pretty
much
boils
down
to
be
nice
to
each
other.
You
know
be
be
decent,
don't
say
anything
crude,
don't
be
a
jerk,
be
chill.
We
can
see
anything
that
you
type
in
the
twitch
chat
and
we
also
will
be
responding
to
it
live.
So
if
you've
got
questions
go
ahead
and
ask
I
am
kat
cosgrove
and
today
we're
going
to
be
talking
about
tinkerbell.
A
B
Sure
thing
for
those
who
don't
know
me,
my
name
is
jason
datiborus,
I'm
currently
with
equinix
metal
working
in
the
developer
relations
group.
There
building
out
a
lot
of
the
integrations
that
we
have
for
different
things,
including
kubernetes,
and
what
we're
going
to
be
talking
about
today,
which
is
the
tinkerbell
project.
A
B
Yeah,
so
folks
that
are
dinosaurs,
like
me,
might
remember
that
in
the
past
almost
everybody
had
their
own
little
data
center.
I
remember
the
first
job
that
I
had
was
a
small
cell
phone
retailer
and
we
had
a
you
know
a
room
in
our
main
headquarters
office
that
hosted
the
servers
for
all
of
our
web
applications
or
and
our
pos
system,
and
things
like
that.
A
Okay,
so
we're
we're
trying
to
modernize
something
that
has
been
around
for
like
not
not
really
not
a
literal
eternity,
but
an
eternity
in
like
in
I.t
terms.
It
doesn't
feel
like
it's
been
that
long,
but
it
has
absolutely
been
that
long.
So
tinkerbell
does
this
how
and
also
like.
Why
would
you?
Why
would
you
want
to
do
this
like
what?
What
is
the
use
case?
Why
is
this
better.
B
B
Because
if
you
look
at
like
the
bare
metal
provisioning
space,
a
lot
really
hasn't
changed
over
the
past
few
decades.
A
lot
of
the
a
lot
of
the
same
projects
exist
for
doing
things
like
pixie
booting,
which
is
basically
being
able
to
network
boot
the
hardware
and
and
install
an
operating
system.
Things
like
that.
B
So,
for
example,
tinkerbell,
isn't
one
real
monolithic
project.
It's
not
just
one
binary
that
you
install
there's
actually
several
different
microservices
that
handle
different
parts
of
kind
of
the
provisioning
life
cycle,
and
the
idea
there
was
is
that
you
can
leverage
existing
infrastructure
that
you
have
and
only
use
the
components
that
you
care
about
and
kind
of
the
core
of
that
is
the
tinkerbell
workflow
engine
itself,
and
you
know,
while
the
first
thing
that
the
tinkerbell
docks
say
is
you
know
bare
metal,
provisioning
engine,
it's
actually
really
more
general
purpose
than
that.
B
If
you
look
at
the
core
workflow
engine,
there's
a
worker
component,
there's
a
server
component
that
tells
the
worker
component.
What
to
do
you
know
in
the
general
use
case?
Yes,
you
can
use
it
for
provisioning
infrastructure
and
putting
an
operating
system
on
it
and
de-provisioning
it,
but
you
can
also
do
other
things
like
ad
hoc
tasks
on
infrastructure
that
you
have
around.
B
You
can
kind
of
power
on
infrastructure
and
have
it
sitting
there
waiting
ready
to
install
something
for
you.
You
can
periodically,
you
know,
go
out
and
use
it
to
automate
installing
new
bios
updates
on
all
of
your
infrastructure
systems
and
and
things
like
that,
it's
really
more.
You
know
at
the
core
of
it.
It's
really
just
this
idea
of
having
you
know,
hardware
defined
and
being
able
to
go
off
and
tell
that
hardware
to
do
something
so.
B
Exactly
but
if
we
led
with
that,
I
think
it
would
cause
a
lot
more
confusion
because
it's
like
well.
What
do
I
need,
like
you
know
this,
this
workflow
environment
for-
and
you
know
you
needed
to
do
these
complicated
tasks
like
provisioning,
bare
metal
infrastructure
and
there's
some
fun
things
that
we
can
get
into
about
what
that
enables.
A
Well,
that's
that's
rad!
I
assumed
it
was
just
installing
an
os.
So
now
now
we've
all
learned
something
so
there's
still
like
a
ton
of
like
legacy,
applications
that
are
running
on
like
the
the
old
school
bare
metal
that
probably
want
to
try
to
like
move
into
the
year
of
our
lord
2021
and
sprinkle,
some
kubernetes
on
it,
and
so
tinkerbell
is
kind
of
a
way
that
helps
enable
doing
that,
but
allows
them
to
keep
their
old
bare
metal
roots.
B
A
B
Your
hardware
and
kubernetes,
if
you
don't
absolutely
need
to-
and
you
know
it's
always
a
trade-off-
it's
you
know,
there's
a
trade-off.
Whichever
way
you
go,
there
are
some
benefits
to
having
that
virtualization
layer,
but
there
are
also
some
drawbacks
to
it
as
well.
So
you
know
there
are
some
really
cool
things
that
we
can
do
around
automating
the
infrastructure.
B
The
possibilities
are
almost
endless.
We
we
have
these
things.
You
know
each
of
these
workflows
can
be
broken
down
into
distinct
actions
and
one
of
the
things
that
we
did
relatively
recently
was
we
built
out
what
we're
calling
an
artifact
hub
and
or
not
artifact,
of
an
action
hub
built
on
the
cncf
artifact
repository,
and
you
can
actually
find
some
pre-defined
actions
that
are
available
to
use
there.
Oh
cool,
you
know,
or
you
can
define
your
own
actions
at
the
end
of
the
day.
B
A
A
Everybody
pay
your
technical
writers
more,
please,
but
I
do
start
by
reading
the
docs,
but
I
can't
actually
learn
something
unless
I
like
try
it
and
the
the
term
bare
metal
sounds
scary
and
it
sounds
like
it
involves
specialized
equipment.
Is
there
any
do?
I
need
specialized
equipment
to
like
actually
try
tinkerbell
myself
or
like
how
do
I?
How
do
I
do
this?
How
do
I,
if
I
wanted
to
mess
with
this
later
today?
How
do
I
do
that.
B
So
currently,
if
you
go
to
the
documentation,
there's
a
section
in
the
documentation,
that's
called
setting
up
tinker
bell
and
there
there's
a
couple
of
different
ways
to
to
go
about
it.
They're
both
hosted
in
a
repository
under
the
tinkerbell
organization,
called
sandbox
and-
and
the
idea
is-
is
that
we
take
all
of
the
various
different
components
we
test
them
together
at
known
versions,
so
that
you
can
have
that
reproducible
type
of
environment.
B
There's
one
that's
based
on
vagrant
that
allows
you
to
basically
spin
it
up
on
on
a
laptop
or
something
like
that.
We're
working
on
kubernetes,
automated
kubernetes
based
deployment.
So
if
you
do
have
a
kubernetes
cluster
already
and
you
want
to
try
it
out
there,
you
can
deploy
all
the
components
there
and
it
you
know,
because
we
are
a
part
of
equinix
metal.
A
B
A
B
Yeah-
and
I
mean,
if
you're
trying
to
do
something
a
little
bit
more
complicated
like
set
up
the
demo
environment
for
like
the
cluster
api
provider,
it
takes
a
little
bit
longer
because
you
have
to
make
some
tweaks
to
things
to
be
able
to
make
sure
that
the
kubernetes
bits
can
talk
to
the
the
vagrant
bits
and
things
like
that.
But
you
know
the
whole
idea
was.
B
A
So
for
somebody
who
has
like
very
a
little
bit
of
experience
with
kubernetes,
assume
we're
talking
to
a
student
here,
a
little
bit
of
experience
with
kubernetes
they're,
my
age
or
younger,
I'm
31,
so
they
have
probably
never
actually
touched
a
bare
metal
deployment
before
they
don't
they
barely
know
what
that
is.
They
might
not
know
what
it
is
at
all
where,
where
would
you
say
that
somebody
should
get
started,
learning
about
bare
metal
as
a
concept
and
tinkerbell
specifically,
is
there
like?
B
You
know
showing
demos
you
know
going
through
the
basic
content
for
it
and
all
of
that,
but
really
we're
trying
to
make
it
possible
so
that
you
can
actually
run
this
on.
Whatever
you
have
tinkerbell
is
compatible
with
both
x86
and
arm
64.,
so
cool,
I
I
know
some
folks
have
actually
gotten
it
running
with
some
raspberry
pies
in
their
environment.
You'll
need
a
pie
for
to
be
able
to
do
the
network
booting
needed
for
it.
My.
A
B
A
B
Yeah,
there's
there's
definitely
better
things
that
you
can
do,
especially
with
some
of
the
high-end
nooks
that
do
have
the
management
interfaces
and
things
like
that.
But
no
you
definitely
don't
need
that.
One
of
the
things
that
we
did
recently
was
originally
the
the
operating
system
component
that
we
had
that
enables
the
hardware
to
run
the
worker
and
be
able
to
run
the
workflows.
B
We
called
it
oc
operating
system,
installation
environment.
It
was
about
a
four
gigabyte,
os
image
that
you
had
to
download
so
exactly,
and
that
also
meant
that
you
know
you
needed
four
gigabytes
of
at
least
four
gigabytes
of
memory,
just
to
run
right.
The
os
image
to
be
able
to
do
anything.
We've
recently
built
out
a
smaller
alternative
to
oc.
B
That
would
call
hook
because
we're
trying
to
keep
with
like
the
tinker
bell
kind
of
nomenclature
and
that's
actually
built
using
a
linux
kit
from
docker,
and
that's
enabled
us
to
build
an
os
environment
that
can
run
the
tinkerbell
worker
in
under
a
gig
of
memory.
I
think
it's
about
like
400
megs,
or
something
like
that.
Oh.
B
A
B
Is
when
tinkerbell
was
originally,
you
know
put
out
there?
The
idea
was
is
to
take
the
best
practices
that
we
learned,
building
out
the
equinix
metal
platform
make
that
available
for
everybody
else
and
with
that
came
some
of
the
for
better
or
worse
legacy.
That
comes
along
with
that,
so
that
oc
environment
contains
a
lot
of
tools
and
a
lot
of
things
to
enable
the
things
that
the
ways
that
we
had
done
previously.
B
So
all
of
the
bits
to
be
able
to
do
bios,
update
management
and
all
of
the
hardware
support
for
all
the
various
things
that
we
need
were
all
pre-compiled
into
that
os
image.
And
when
we
started
building
out
this
alternative
hook,
we
were
able
to
leave
a
lot
of
that
behind
and
push
the
idea
that
you
do
more
of
that
with
actions
or
some
other
mechanism
with
tinker
bell.
B
So,
in
my
opinion,
it's
a
really
interesting
time
because
we've
gone
beyond
the
official
release
of
tinker
bell
and
now
we're
getting
to
the
part
where
we
can
figure
out.
You
know
what
do
other
folks
outside
of
equinix
need
and
and
what
are
they
looking
to
do
with
tinkerbell?
How
do
we
enable
that
and
additionally,
how
do
we
improve
our
internal
platform
at
the
same
time?
And
how
do
we
drive?
You
know
enabling
those
changes
through
the
tinkerbell
project,
so
we're
we're.
A
Cool
for
the
people
watching
on
twitch.
If
you
have
questions
you
can
throw
them
in
the
twitch
chat
and
we
will
we
will
see
them.
We
have
one
question,
let's
say
I'm
interested
in
contributing
code
and
I
want
to
get
into
helping.
How
do
you
go
about
helping?
There
are
several
repos.
It
would
be
nice
to
know
how
people,
with
more
experience
than
me
kind
of
get
the
initial
push
or
some
momentum.
A
A
So
that's
a
that's
a
good
question.
Contributing
is
an
important
thing
to
do
with
open
source,
especially
with
like,
with
really
young
projects
like
like
this
one
people
typically
do
want
outside
help.
So
please
do
that,
but
I
get
it
that
it
is
kind
of
like
it's
daunting.
It's
it's
a
really
daunting
task.
You
may
feel,
like
you
are
potentially
going
to
step
on
somebody's
toes
or
you're
embarrassed
about
the
quality
of
your
code,
even
though
you
shouldn't
be
I'm
sure
your
code
is
great
it.
A
It
can
be
kind
of
scary
to
do
that,
when
I
started
contributing
to
open
source,
I
started
with
documentation
changes
as
a
newbie.
That's
that's
always
something.
That's!
That's
really
really
valuable,
like
just
go
through
a
quick
start
guide
for
something
and
anything
that
doesn't
like
if
you,
if
you
can't
actually
get
something
to
run
following
the
instructions
as
written
make
a
note
where
things
differed
or
where
things
weren't
clear
enough
and
then
maybe
open
a
pull
request
with
those
changes.
That's
how
I
started,
but
specifically
with
tinkerbell.
I
will
leave
that
to
jason.
B
Yeah,
I
think
everybody's
path
is
probably
going
to
be
a
little
bit
different.
You
know
we
definitely
encourage
the
the
docs
first
approach
for
for
folks
who
are
comfortable
with
that.
I
think
there
are
other
approaches
as
well,
so
we
have
a
bi-weekly
community
meeting
that
we
have
and
there's
a
google
mailing
list,
and
I
can
dig
that
up
to
make
sure
that
that
makes
it
into
the
show
notes
as
well.
B
We
also
hope
that
you
know
we
have
some
issues
that
are
on
the
various
repositories
you
know
marked
in
a
way
that
indicates
that
they're
help
wanted
or
potentially
good
for
first
users.
You
know
some
folks
just
want
to
kick
the
tires
with
things
and
and
see
how
they
work.
It's
perfectly
fine.
Just
to
come
in.
B
You
know
head
first
with
the
pull
request,
just
expect
that
if
you
do
go
that
way
that
you
may
get
pushed
back
on
the
approach
that
you
took-
and
I
don't
expect
anybody
on
the
tinkerbell
project
would
be
overly
that's
what
I'm
looking
for
abrasive
about
it.
But
you
know
they're
generally
going
to
want
to
have
a
conversation
around.
You
know,
what's
the
what's
the
best
path
forward
and
it
might
not
necessarily
be
your
first,
you
know
first
idea
when
you're,
when
you're,
starting
out
with
that
way,.
A
Yeah,
and
from
like
a
purely
like,
how
do
you
do
this
perspective?
The
overwhelming
majority
of
open
source
projects?
I
think
all
cncf
projects
are
required
to
have
this
there's
a
contributing
dot,
md,
there's
a
contributing
markdown
file
that'll
go
over
the
actual,
like
required
steps
and
processes
involved
in
contributing
to
the
project.
A
There
are
also
cncf
ambassadors
that
are
always
willing
to
help
too,
but
tinkerbell
is
really.
This
was
my
first
choice
because
it
is
something
that
is
it's
bare.
Metal
is
interesting
and
that
it's
it's
very
old
and
it's
still
a
thing,
and
it's
it's
a
thing
even
in
like
very
aggressively
modern
places
like
kubernetes.
A
A
B
Support
different
things,
because
different
types
of
pixie
implementations
in
practice
are
very
different,
so
you
need
to
be
able
to
support
things
like
a
legacy.
Boot
p
protocol
to
be
able
to
make
sure
that
you
can
get
the
infrastructure
up
to
a
bit
where
you
can
install
a
common
pixie
environment
like
ipixie
to
be
able
to
you
know,
use
a
common
workflow
from
that
point,
and
and
just
the
way
that
you
know
different
things
just
vary
slightly
when
you're
dealing
with
hardware
versus
virtual
things.
B
B
B
B
A
B
Yeah,
so
basically
pixie
is
stands
for
pre-boot
execution,
environment,
and
the
idea
is,
is
that
it's
a
way
to
sit
there
and
initialize
an
operation
and
to
be
able
to
boot
the
system.
So
you
don't
necessarily
have
to
in
the
old
days.
You
would
actually
go
to
a
data
center.
You
would
plop
a
cd
into
a
cd-rom
driver
even
further
back
floppy
disk
in
and
install
your
operating
system.
That
way,
pixie
booting
is
basically
a
way
to
boot.
B
A
Cool,
thank
you.
We've
we've
kind
of
inherited
a
lot
of
like
like
super
old
terminology
over
over
the
decades
now
of
of
computing
that
that
sticks
around,
because
it's
still
you
know
it
still
exists,
but
we've
we're
so
far
removed
from
its
origins
that
sometimes
we
just
like
we
keep
using
these
words,
but
don't
necessarily
explain
them
as
well.
I'm
really
bad
about
that,
and
it's
something
I
try
to
like
keep
an
eye
on
with
myself.
So
I
don't.
A
I
don't
use
too
much
too
much
jargon,
but
I
think
it's
really
cool
that
tinkerbell
is
kind
of
bringing
this
legacy
way
of
doing
things
into
the
modern
world,
because
people
still
want
to
do
bare
metal
provisioning
like
it
is
absolutely.
It
still
has
a
use
case,
but
it's
been
something
that's
kind
of
fallen
out
of
the
limelight
over
the
last
decade,
or
so
I
remember
before,
like
cloud
computing
became
as
ubiquitous
as
it
is
now
it
was.
A
B
Well-
and
it's
interesting
because
coming
from
you
know,
environments
where
there
has
been
some
type
of
infrastructure
run
before
I've
been
in
places
where
there
was
no
infrastructure
management
and
everybody
did
everything
manually,
yeah
and
then
you
know
it
generally
be
became
who's.
Your
infrastructure,
vendor
of
choice,
use
their
software
to
kind
of
automate
some
of
these
things
or
on
the
open
source
side.
You
might
have
something
like
cobbler
or
something
like
that.
B
That
made
it
somewhat
easy
to
provide
pre-configured
options
for
what
you
want
to
do
at
boot
time,
but
made
it
a
little
bit
more
difficult
for
you
know
being
able
to
automate
some
of
the
infrastructure,
and
there
have
been
some
other
projects
that
have
come
in
and
out
during
the
during
the
period.
I
think
the
thing
that
really
drew
me
to
tinkerbell,
though,
was
the
idea
that
we
don't
necessarily
need
to
be
a
monolithic.
B
You
know
entity,
you
don't
need
to
adopt
necessarily
all
of
the
project
to
be
able
to
consume.
It
and
kind
of
you
know
for
lack
of
a
better
word
modernize
your
workflows
in
a
data
center.
You
can
hopefully
just
be
able
to
pick
the
bits
that
you
need
and
consume
things
like
the
workflow
engine
and
rely
on
your
existing
dhcp
systems
for
providing
that
functionality.
B
If
you
want
that-
and
you
know
from
my
perspective,
trying
to
build
out
some
higher
higher
order
like
cluster
api,
you
know
that's
very
appealing,
because
you
can
tell
people
hey,
you
can
make
use
of
this
in
your
environment
without
necessarily
having
to
rip
and
replace.
You
know
all
of
the
existing
infrastructure
management
that
you
have
for
everything
else
in
your
data
center.
A
Yeah
we
want
a
little
bit.
We
want
a
little
bit
more
control
now
and
tinkerbell.
It
sounds
like
gives
us
some
extremely
fine
grain
control.
We
have
another
question:
do
you
want
to
answer
this
before
we
go?
Do
you
have
a
little
bit
more
time?
Okay,
I'm
still
kind
of
fuzzy
on
this
so
like
how
I
might
use
aws
or
gcp,
etc,
to
manage
how
my
application
should
run.
A
B
B
So
you
know
you
could
do
the
same
things
like
being
able
to
scale
your
application
to
meet
whatever
type
of
hardware
capacity
you
have.
Obviously,
unlike
a
you
know,
most
modern
cloud
providers,
you
couldn't
treat
that
capacity
as
nearly
infinite
from
your
perspective,
you're
going
to
have
some
type
of
hard
limit,
but
you
could
leverage.
You
know
that
scaling
capability
or
you
can
leverage
things
like
automating.
Your
upgrade
workflows
in
a
similar
way
that
you
could
do
with
that
cloud
infrastructure.
A
Cool,
well,
that
is
about
all
the
time
we
have.
I
really
appreciate
you
coming
to
teach
me
about
this.
This
thing
that
I
didn't
know
anything
about
and
teaching
the
people
watching
about
this
thing
that
maybe
they
didn't
know
anything
about,
so
it
sounds
like
tinkerbell.
It's
bare
metal
provisioning,
but
it's
also
more
than
that.
It's
whatever
you
want
it
to
be.
It
sounds
like
which
is
pretty
cool.
A
Thank
you.
You
have
been
great
viewers.
You
have
also
been
great.
Thank
you
for
asking
questions,
make
sure
to
follow
the
channel
so
that
you
get
a
notification
when
we
go
live
next
there
are
shows.
Every
weekday
tomorrow
is
caslin
fields,
running
fields
tested
and
she's,
going
to
be
deploying
a
personal
blog
on
kubernetes,
which
is
one
of
my
favorite
flavors
of
demo.
A
A
Maybe
it's
over
engineering,
but
also
it
is
a
practical
example
of
how
to
use
a
tool
to
do
something
familiar.
So
thanks.
Everybody
we'll
see
you
tomorrow.
I
will
see
you
personally
week
after
next,
because
my
show
is
every
other
week
so
make
sure
you
follow
us
on
twitch
and
if
you
want
to,
you
can
also
follow
us
on
twitter,
also
at
cloudnativetv.