►
From YouTube: CloudNativeTV Fields Tested - Kubernetes
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).
B
A
A
All
right
everyone
we're
trying
this
again.
Let
me
know
how
the
quality
is.
Let
me
know
if
I'm
cutting
out
a
whole
lot,
it's
quite
possible,
but
we'll
try
this
one
more
time.
A
So
I
don't
know
what
you
all
caught
of
the
introduction
last
time,
but
this
is
fields
tested
and
I'm
castling
fields,
and
I'm
gonna.
A
I
put
this
in
earlier
because
we
were
having
so
much
trouble
and
I
went
over
the
code
of
contact
and
I
went
over
some
of
the
shows
that
you're
gonna
see
later
so.
I
just
want
to
give
another
brief
introduction
to
what
I'm
trying
to
do
here,
which
is
I'm
trying
to
give
give
everyone
a
chance
to
see
cloud
native
technologies
in
some
form
of
context.
A
A
I'm
gonna
skip
that
it's
inspired
by
thanks
pop
sorry,
I'm
I'm
such
a
mess
today,
first
stream.
A
So
my
goal
for
for
today
is
to
try
to
host
a
personal
blog
on
kubernetes,
which
we're
off
to
a
great
start
on
so
we'll
see
how
this
all
goes.
But
it's
inspired
by
this
tweet,
which
I
posted
on
twitter.
A
Hopefully
a
bunch
of
you
have
seen
it
before
where
someone
is
trying
to
create
a
sandwich
using
using
power
tools,
which
I
would
agree
kind
of
feels
like
what
hosting
a
personal
blog
on
kubernetes
seems
like
to
me,
but,
like
I
said
in
my
promo,
if
you
saw
that
what
good
is
an
opinion
without
empirical
evidence,
so
do
I
have
other
stuff
in
the
slide
deck.
I
don't
think
I
do
yeah
we're
just
going
to
tell
a
story
now.
A
So
thanks.
I
appreciate
all
the
support
so
much
everyone's
been
so
nice,
so
part
of
the
reason
that
I
wanted
to
do
a
personal
blog
on
kubernetes,
for
my
first
episode
was
because,
like
I
said
in
the
promo,
if
you
saw
that
I
tried
to
do
this
like
five
years
ago,
it's
a
very
different
experience.
I'll
tell
you
that
much
and
I
want
to
kind
of,
I
could
explain
why.
I'm
gonna
approach
it
the
way
that
I'm
gonna
approach
it
today,
but
I
think
it's
better
to
tell
a
story.
A
So
let
me
tell
you
about
why
I
tried
to
run
a
personal
blog
on
kubernetes
like
five
years
ago.
So
it's
end
of
2015
early
2016.
A
I
had
just
been
laid
off
from
my
first
job
in
the
tech
industry
rough
times,
but
it
was
okay
and
there
were
a
variety
of
circumstances
that
led
to
it
and
it
wasn't
unexpected
and
I
was
in
an
okay
place,
but
I
had
I
was
now
in
the
position
where
I
needed
to
be
looking
for
a
job,
and
I
had
gained
some
really
cool
skills
around
using
containers.
A
So
I
wanted
to
make
that
a
reality
and
make
it
happen,
and
I'm
a
computer
person
like
I
work
in
the
tech
industry
everybody's
talking
about
how
easy
it
is
to
build
a
personal
website.
All
the
time
I
feel
like
I
was
like
I
can
do
that
right,
further
backstory,
when
I
was
in
college,
I
actually
skipped
all
of
the
web
design
courses
through
a
variety
of
circumstances,
so
I've
never
done
any
web
development
at
all.
A
I
don't
know
the
first
thing
about
running
a
website
and
I'm
between
jobs
and
I'm
trying
to
run
a
personal
website.
I
know
a
little
bit
about
containers,
so
I'm
like
okay,
I'm
gonna,
run
a
personal
website
on
containers,
so
I
wanted
to
set
that
stage
for
you
and
from
that
starting
point.
We're
gonna
explore
running
a
personal
website
on
kubernetes
today.
So
the
first
thing
that
I
need
to
figure
out
as
someone
who
knows
a
little
bit
about
containers
and
absolutely
nothing
about
web
development
is
what
does
it
take
to
run
a
personal
blog.
A
So
I've
got
a
I've,
got
a
google
doc
up
here
that
I
thought
we'd
use
to
track
our
progress
in
trying
to
achieve
this
goal
today.
So
our
first
question
that
we
need
to
answer
is:
what
does
it
take
to
run
a
personal
blog
caslin
of
five
and
a
half
years
ago
had
no
idea.
So,
let's
just
google
running
a
personal
blog
site
and
I
think
the
the
results
today
are
going
to
be
at
least
similar
enough
to
what
I
want
to
what
I
saw
five
years
ago
yeah.
A
So
we've
got
this
recommendation
here
from
google
that
says
the
technical
setup
when
starting
a
personal,
wordpress
blog.
So
at
this
point
in
my
life
I
had
heard
of
wordpress.
I
think,
but
I
I
didn't
know
anything
about
it,
but
I've
heard
of
it
before
and
it's
mentioning
it
here
so
wordpress
seems
like
a
solid
choice.
A
There's
also
all
these
things
like
wix
and
squarespace
and
stuff
that
you
always
see
all
of
the
ads
for
on
youtube.
At
least
I
do,
and
so
you
could
do
something
like
that.
Let's
look
at
one
of
those,
maybe
well.
A
What
I
know
about
those
is
that
they
make
it
really
really
easy
to
run
a
website,
and
at
this
point
I'm
thinking,
but
I
want
to
learn
about
using
containers.
I
don't
want
to
just
take
something
that's
given
to
me.
I
want
to
do
it
the
hard
way
for
learning
purposes,
because
I
I
have
good
ideas
like
that.
So
so,
let's
just
look
up
wordpress
wordpress.
A
So
then,
I
find
this
thing
wordpress.com.
That
seems
like
a
good
place
to
start
says
that
41
of
the
web
is
built
on
wordpress
cool.
That
seems
like
a
very
reasonable
thing
for
us
to
try
to
build
a
website
with
then
I
don't
know
anything
about
it,
but
it
seems
like
a
good
place
to
start,
and
they
have
this
start.
A
Your
website
button,
which
I
wonder,
what
it'll
do,
if
I
click
on
it,
you'll
have
to
like
log
in
and
stuff,
but
what
I've
learned
since
at
least,
is
that
on
wordpress.com
you
can
make
your
own
personal
website
and
please
folks
in
the
chat.
I
would
love
to
hear
from
you
about
your
experiences
with
personal
blogs.
Are
you
all
running
personal
blogs?
Have
you
all
tried
to
run
it
in
kubernetes?
Before?
Did
you
do
something
like
this?
A
Please
tell
me
about
your
experiences,
because
mine
are
pretty
limited
and
we
would
all
love
to
hear
from
you.
So
what
I've
learned
about
wordpress.com
is
that
you
can
spin
up
a
website
really
easily
here.
It's
like
a
lot
of
the
other
sites
where
it
gives
you
really
nice
tools
for
spinning
up
a
website
really
easily.
A
Give
you
a
sense
of
what
I'm
looking
at
I've
heard
of
things
like
godaddy
and
and
domain
name
registrars
before
so
I
did
a
bit
of
research
and
looked
around
at
a
few
different
domain
name
registrars
and
I
bought
a
domain
name
planning
to
make
a
personal
website
out
of
it.
A
So
that
was
an
important
first
step
and
now
we
know
that
we
want
to
try
and
use
wordpress
for
our
personal
blog.
So,
like
I
said,
I've
got
a
little
bit
of
experience
with
containers.
I
want
to
see
if
I
can
run
wordpress
in
a
container.
That
seems
like
a
good
place
to
start
so
wordpress
docker
I've
been
doing
a
lot
of
docker
work
at
this
point,
so
I
was
pretty
familiar
with
docker,
then
less
so
now
I'd
say.
A
But
if
I
go
here,
we've
got
a
wordpress
image
on
docker
hub,
so
that
seems
like
I'll,
probably
be
able
to
run
a
docker
container
with
wordpress
in
it.
That's
pretty
good
start.
Let's
see
how
we
can
actually
do
that.
So
there's
this:
how
to
use
this
image
section,
which
you'll
probably
can't
see
at
all.
Let
me
zoom
way
in
and
close
this
and
make
this
a
bit
bigger.
A
I'll
make
this
even
bigger,
maybe
not
that
big,
so
we're
on
docker
hub
and
we've
got
this
wordpress
image
and
we're
trying
to
learn
how
to
use
it.
Now
that
I've
done
that,
I'm
going
to
open
up
a
terminal.
A
A
Oh
you're,
running
one,
but
it's
not
on
kubernetes.
Can
you
tell
us
a
little
bit
about
what
process
you
went
through?
I
would
love
to
hear,
because
I
have
an
idea
how
other
people
approach
this
problem,
so
we
know
that
we've
got
docker
installed
here,
that's
a
good
first
step.
I'm
gonna
maybe
make
this
just
a
little
yeah,
so
I
can
get
back
to
this
easily.
A
I'll
move
this
slightly
over
too,
so
I'm
going
to
try
to
run
this
docker
command,
because
that's
what
caslin
currently
and
caslin
five
years
ago
would
try
to
do
upon
looking
up
something
that
I
wanted
to
run
in
containers.
I
would
just
try
to
run
the
first
thing
that
I
so
if
I
try
to
run
this,
it
won't
find
the
wordpress
image.
So
that's
good.
It's
pulling
the
wordpress
image.
This
is
looking
pretty
good
where
so
I
found
a
container
image
to
run
wordpress,
and
now
it's
downloading
that
image.
A
A
So
at
the
time
when
I
was
trying
this,
I
was
pretty
familiar
with
docker
and
probably
had
set
up
a
few
docker
networks.
Oh
you
used
jekyll
cool.
Thank
you.
So
much
for
sharing
your
experience
allows
you
to
launch
a
pre-configured
blog
website
created
using
ruby
yeah.
I
hear
a
lot
of
good
things
about
jekyll.
A
A
Let's
see
what
else
we
have
in
the
information,
so
the
following
environment
variables
are
also
honored
for
configuring.
Your
wordpress
instance
we've
got
some
stuff
about
wordpress
db
host,
so
it
looks
like
we're
going
to
need
a
database
to
do
this,
which
is
interesting.
A
lot
of
people.
I've
I've
gotten
the
question.
Pretty
often
of
can
you
even
run
databases
in
kubernetes,
so
this
is
going
to
give
us
a
chance
to
check
that
out.
It
seems
like
which
it
is
spoilers.
It
is
so.
A
A
Docker
run
command.
Let's
actually
do
a
little
bit
more
thinking
about
this
one,
this
time
since
the
last
one
failed.
If
you'd
like
to
be
able
to
access
the
instance
from
the
host
without
the
container's
ip
standard
port
mappings
can
be
used.
So
this
one
is
saying:
I'm
going
to
run
a
wordpress
container
and
I'm
going
to
run
it
on
a
specific
port
on
the
machine
that
I'm
running
it
on.
So
that
sounds
pretty
good.
That
sounds
like
something
that
we
can
do.
A
So,
let's
try
that
I'm
going
to
come
back
over
here
and
I'm
going
to
do
docker
run.
Some
wordpress
is
fine
and
do
that
I
know
I
must
have
tried
this
earlier.
Rocker
ps,
tracker,
ps,
a
oh,
because
I
just
ran
that
other
command
and
it
failed.
It
actually
created
a
container,
but
it
didn't
work
out.
A
So
if
I
run
docker
ps,
I
don't
see
any
running
containers,
but
if
I
run
docker
ps,
a
which
shows
me
all
running
and
stopped
and
not
in
a
good
state
containers,
I
can
see
that
I've
actually
got
the
wordpress
container
that
I
tried
to
spin
up
still
and
it's
using
the
same
name.
So
it's
not
letting
me
create
the
container,
so
I'm
going
to
run
docker
rm,
yes
and
front
tip.
If,
if
you're
working
with
docker,
you
can
just
use
any
unique
string
from
the
container
id
to
refer
to
the
container.
A
So
if
I
run
this,
I
should
be
able
to
get
rid
of
that
container
cool.
So
now
my
wordpress
container
that
I
created
in
error
is
gone
and
now
I
should
be
able
to
run
this
new
wordpress
container,
that's
using
port
8080
and
at
some
point
today,
I'm
going
to
mess
this
up.
It's
very
important
when
running
docker
commands
to
use
dash
g,
at
least
in
my
experience,
because
dash
d
runs
the
container
in
detached
mode,
and
if
you
don't
do
that,
the
running
container
will
take
over
your.
A
A
Docker
ps
a
we
can
see
that
it's
running
if
I
run
docker
ps,
I
should
also
just
see
it
yep,
so
this
container
looks
like
it's
running
happily.
So
it's
running
on
my
local
host
on
port
8080.
880
is
the
local
host
port
and
80
is
the
port
in
the
container
that
is
being
mapped
to.
I
believe
I
always
get
that
mixed
up,
but
we
do
local
hosts
id
80..
A
A
So
our
first
question
to
answer
was:
what
does
it
take
to
run
a
personal
blog?
I
want
to
come
back
to
this
for
a
second
and
say
we
needed
a
domain
name.
We
talked
about
that
and
we
needed
to
decide
what
to
use
to
run
the
blog
which
we're
going
to
use
wordpress,
and
so
now
can
I
run
wordpress
in
a
container.
What's
my
next
question.
A
So
now
I
need
to
figure
out
how
to
run
a
database
container,
that
this
wordpress
instance
needs
and
a
nice
thing
in
this
docker
hub
entry
is
that
it
has
this
yaml
file
that
defines
what
you
could
use
for
docker
compose
to
tell
docker
spin
up
multiple
containers
for
me.
So
that
sounds
pretty
good.
A
Let's
just
try
this,
but
let's
see
what
we
have
in
it
first,
so
there's
two
services:
the
first
one
is
called
wordpress.
That's
what
we
want
to
run.
That
makes
sense.
It's
got
port
8080
80..
So
I'm
going
to
want
to
delete
that
container
that
I
already
have
running.
A
If
I'm
going
to
run
this
because
otherwise
it's
going
to
have
report
conflict,
it's
a
good
thing
to
to
back
out
at
first
your
blog
is
called
daemon
sets
nice,
it's
a
good
blog
name
and
then
there's
all
these
environment
variables
that
must
be
wordpress
stuff
looks
like
it's
telling
wordpress
how
to
connect
to
the
database,
information
about
the
database
db,
host
db
user
db,
password
and
db
name,
and
it's
got
a
volume.
A
So
when
I
tried
this
like
five
years
ago,
the
instruction
page
here
was
a
little
bit
different.
I
don't
think
it
had
the
instructions
to
create
this
volume,
but
since
at
the
point
where
I
realized
that
I
needed
to
create
a
database
container,
I
knew
about
docker
volumes,
so
docker
volumes
are
docker's
tool,
kind
of
for
using
persistent
storage
with
containers.
So
if
you
have
a
container,
that's
going
to
run
some
application
that
needs
a
volume.
A
Needs
to
have
persistent
storage
that
could
persist.
If
say
the
container
were
to
go
down.
You
would
still
want
to
keep
that
data,
then
you're
going
to
want
to
have
a
volume,
so
that
makes
total
sense
for
a
database.
We
probably
want
our
data
to
persist,
so
we're
going
to
create
a
volume
and
in
docker
land
you
can
specify
the
name
of
a
volume
and
then
where
it's
going
to
be
loaded
into
the
container.
A
So
in
slash
var
lib,
my
sequel,
which
I
assume
is
an
area
where
it's
important
for
my
sql
databases
to
have
persistent
storage,
we'll
set
up
a
volume
that
will
persist
even
if
our
container
ever
dies.
A
So
that's
good
and
then
we're
setting
up
one
for
wordpress
as
well,
I'm
kind
of
tempted
to
show
you
all
what
happens
if
you
don't
do
that
on
the
wordpress
side,
because
it's
pretty
interesting
but
we're
already
pretty
kind
of
behind
schedule,
and
I
want
to
get
to
running
this
on
kubernetes
without
taking
up
too
much
time.
So
I
think
I'll
just
try
running
this
compose,
so
I'm
gonna
docker
rm-f
83,
so
that
I
get
rid
of
that
wordpress
container.
I
was
running
earlier,
so
docker
ps.
A
A
A
Dot
yaml
that
sounds
reasonable
and
I'm
gonna
input
all
of
the
stuff
that
I
saw
on
the
docker
hub
page.
A
So
again,
this
gives
me
all
the
information
I
need
to
create
another
wordpress
container
with
environment
variables
that
are
apparently
important
for
wordpress
and
to
create
a
database
container
with
also
some
important
things
set
up
in
it
and
then
volumes
for
each
of
those,
so
that
storage
will
persist
across
restarts
and
things
like
that.
A
Yeah,
so
we're
going
to
want
to
run
docker
compose
dash
f,
give
it
the
name
of
the
file
and
then
up-
and
this
actually
has
been
changed
so
that
you
can
do
it
with
a
space
instead
of
has
its
own
command,
so
docker
compose
dash,
f,
wordpress,
docker.yaml
and
then
we're
gonna
up
that
okay.
So
now
we
see
that
docker
is
building
our
containers
that
we
defined
in
the
yaml.
A
Have
you
all
done
this
kind
of
stuff
before?
How
long
has
it
been
since
you
all
worked
with
docker,
I'm
curious,
it's
been
a
while,
since
I
worked
with
docker.
I
did
a
little
bit
of
exploration
before
this
to
make
sure
that
I
would
not
spend
the
whole
time
just
looking
at
docker
commands,
because
it's
been
so
long
since
I
used
it.
A
A
I
hate
it
when
I
do
that
this
is
bringing
back
great
memories,
I'm
glad
what
is
going
to
happen.
If
I
control
see
this
because
I
kind
of
want
my
terminal
back,
maybe
we
should
go
to
8080.
First
and
see
if
it's
up
and
see
if
this
worked
and
then
I'll
worry
about
getting
my
terminal
back,
so
this
is
from
before.
Let's
try
localhost
8080
again,
let's
reload
this
okay,
so
we've
got
wordpress
page
again,
that's
good!
A
Oh,
and
this
is
different.
You
see
so
last
time.
It
said
that
I
needed
to
connect
to
a
database,
but
this
time
it
seems
to
be
saying
that
I
I
imagine
that
I
have
the
database
already.
So
my
compose
should
have
worked.
I've
got
a
wordpress
container
running
and
I've
got
a
mysql
database
container
running
and
they
can
talk
to
each
other
awesome.
A
But
what
do
you
all
think
we're
getting
kind
of
short
on
time?
I
think
I
might
move
on
to
running
it
in
kubernetes.
That
sounds
good.
I
remember
the
first
time
I
ran
docker
compose
up.
It
was
magic.
I
agree
with
that
lucky.
A
How
long
has
it
been
since
you
worked
with
docker?
I
think
pop
is
asking
everyone
in
the
chat
for
me,
but
for
me
it's
been
like
five
years.
Yeah
run
it
in
kubernetes,
okay.
So
that's
what
we'll
do
next,
instead
of
messing
around
with
killing
containers
and
seeing
what
happens
with
the
persistent
volumes
and
things
we
can
always
explore
that
another
time.
So
I'm
just
going
to
control
see
this.
We
don't
need
these
containers
running
anymore
anyway.
It
says
that
they're
stopped.
A
A
A
A
I've
heard
great
things
about
kind.
I
hear
it's.
It's
really
good,
I'm
currently
using
docker
desktop
by
the
way
for
all
the
docker
stuff.
I
was
just
doing
really
nice
tutorials
for
that
too.
If
you
want
to
practice
your
docker
commands
like
I
did
so
this
should
be
pretty
much
the
same
thing
that
we
saw
in
docker,
but
now
it's
in
kubernetes
so
create
persistent
volume,
claims
and
persistent
volumes.
This
is
going
to
be
the
kubernetes
equivalent
of
docker
volumes
that
we
just
talked
about
a
little
bit
ago.
A
B
A
Have
to
go
no
worries,
but
I'm
gonna
try
to
do
this
relatively
quickly
and
kind
of
point
out
some
of
the
important
things
about
kubernetes
as
we
go
so
they're
wanting
to
spin
up
a
secret,
which
is
a
kubernetes
object
that
stores
a
piece
of
sensitive
data
which
you'll
can't
see
at
all.
Probably.
A
Like
a
password
or
a
key
since
1.14
cube,
ctl
supports
the
management
of
kubernetes
objects
using
a
customization
file,
so
you
can
create
a
secret
by
generators
in
customization.yaml,
add
a
secret
generator
and
customization.yaml
from
the
following
command.
You
will
need
to
replace
your
password
with
the
password.
You
want
to
use
okay,
so
this
is
we're.
Gonna
try
to
use
a
kubernetes
secret,
which
is
first
secret
data
to
set
up
a
password
for
our
mysql
instance
that
we're
gonna
run
in
kubernetes.
A
A
A
A
So
this
file
is
a
bit
longer
than
the
one
that
we
saw
in
docker.
Someone
said
I
get
hung
up
with
the
network
stuff
and
all
this
tech
me
too,
like
I
said
earlier,
the
command
that
made
use
of
docker
network
or
for
wordpress.
I
haven't
used
that
in
so
long,
oh
speaking,
of
which
not
even
using
my
nice
mic.
So
I'm
so
sorry
about
my
audio
quality,
which
hopefully
just
improved
significantly
kind
of
equals.
A
We
had
two
services
wordpress
and
mysql,
and
that
was
used
a
little
bit
differently
than
it's
being
used
here
here.
It's
a
kubernetes
manifest
so
we're
talking
about
the
kubernetes
object
of
a
service.
A
So
thankfully
I
know
this
now
because
I've
been
working
with
kubernetes
for
a
while.
But
I'll
tell
you
me
if
five
years
ago
did
not
so
we're
going
to
name
our
service
wordpress
mysql
and
we're
going
to
give
it
a
label
app
wordpress
and
then
so
we're
specifying
a
port
that
our
service
is
going
to
run
on
and
a
selector
app
wordpress
and
tier
mysql.
A
A
I
just
noticed
that
I
still
have
a
menu
up
okay,
so
it's
one
of
the
first
things
that
you'll
do
in
any
beginner
to
tutorial
in
kubernetes
is
you'll
spin
up
a
deployment
or
some
kind
of
pod
or
you'll
run
containers
and
kubernetes.
Basically,
that's
what
we're
going
to
talk
about
when
we
get
to
deployment,
and
then
you
use
the
service
to
actually
access
that
deployment.
A
I
still
love
and
use.
Docker
almost
every
day
use
the
same
approach
that
you've
demoed
docker
compose
for
quick
poc
and
then
followed
by
kubernetes
yeah
awesome.
I
love
to
see
that
that's
a
pattern
that
other
people
use.
I
find
it
really
helpful
to
understand
what
I'm
actually
doing
with
the
containers
and
how
I'm
actually
running
the
application
before
I
start
bringing
in
kubernetes
objects.
A
A
A
It
doesn't
actually
specify
the
type
of
service
explicitly
it's
been
a
while,
since
I've
made
a
service
manifest.
So
I
find
that
interesting.
I
guess
this
is
technically
a
node
port
one.
I
don't
know.
I
need
to
look
things
up
so
anyway,
we're
gonna
move
on
to
persistent
volume
claims
and
then
the
following
manifest
describes
a
single
instance
I'm
looking
to
see
if
there's
a
okay,
so
this
is
just
a
slightly
different
one.
A
So
this
is
a
persistent
volume
claim
and
it's
being
called
my
sequel
pv
claim:
wordpress
it's
getting
the
label
app
wordpress
and
then
it's
gonna
be
a
read,
write
once
volume
and
20
gibby
bytes
cool.
So
this
is
a
local
persistent
volume
claim.
I
assume
we
need
to
say
something
about
setting
up
an
actual
persistent
volume.
First,
so
mysql
wordpress
each
require
a
persistent
volume
to
store
their
data.
We
saw
that
in
docker
their
persistent
volume
claims
will
be
created
at
the
deployment
step.
Oh
okay,
so
maybe
it's
in
our
actual
deployment.
A
Yeah
there
you
go
volume,
amounts
and
volumes.
So
that's
where
we're
actually
defining
our
persistent
volumes.
So
in
kubernetes
it's
not
just
volume
like
it
wasn't.
Docker
you've
got
a
persistent
volume
and
then
you've
got
to
claim
that
persistent
volume
with
a
persistent
volume
claim
which
honestly
I
haven't
worked
with
in
a
while,
but
I'm
going
to
read
a
question.
A
Here's
my
silly
question.
Let's
say
you
didn't
have
a
great
guide
like
this.
How
do
you
know
what
keys
you
will
need?
On
the
left
hand,
side
do
those
match
up
with
something
the
keys
I
mean
are
like
oh
spec,
metadata,
spec,
etc.
I'm
not
sure
how
I
would
have
gone
about
knowing
how
to
use
or
knowing
that
I
need
them.
I
have
had
that
same
question.
I
will
tell
you
if
you
ever,
do
the
the
ckad
certified
kubernetes
application
developer
exam?
A
You
will
have
to
practice
that
a
lot
you'll
kind
of
get
a
sense
for
all
of
the
important
things
that
you'll
need
in
every
single
yaml
manifest
for
kubernetes.
Api
version
is
always
going
to
be.
There
kind
is
always
going
to
be
there,
because
it's
telling
you
what
kind
of
kubernetes
object
you're
going
to
create
this
first
metadata.
One
is
pretty
much
there
for
every
object,
because
you're
going
to
need
to
name
the
object
that
you're
creating
and
have
the
opportunity
to
give
it
labels
even
kubernetes
node
objects,
for
example,
have
labels.
A
So
you
have
to
get
a
sense
for
what
kubernetes
objects
are
and
what
kinds
of
yaml
components
are
are
applicable
to
those
kubernetes
objects
which
I
would
check
out
the
documentation
for
would
be
my
recommendation.
A
Yeah
someone
I'm
sorry
if
I'm
pronouncing
your
name
wrong,
very
sorry
is
saying
well.
For
the
most
part,
there
is
a
specific
pattern
to
the
spec.
You
specify
the
api
version,
object,
kind,
metadata
data
and
the
spec,
but
you
can
always
use
cube.
Ctl
drive
run
to
generate
yeah
cube,
ctl
dry
run
is
a
really
nice
tip
that
you'll
see
if
you
ever
practice
for
the
certified
kubernetes
administrator
or
certified
kubernetes
application
developer
check
out
certs
magic
with
sion.
Later
it's
a
big
tip
for
those
is
to
learn
how
to
use
cube.
A
Ctl
dry
run
to
generate
kind
of
a
base,
yaml
file
for
doing
this
stuff
cool
and
then
yeah,
okay,
making
sure
that
there
aren't
any
other
questions
good
good.
So
we've
got
a
persistent
volume
claim
here.
We've
got
a
service
definition
here
and
we
have
a
deployment
definition
here,
which
is
pretty
big
deployments,
can
do
a
lot
of
stuff,
so
deployment
is
how
we're
going
to
run
our
actual
containers
that
we
care
about
interesting.
So
we
have
both
the
wordpress
and
the
mysql
defined
in
the
same
deployment.
A
Definition
wordpress
dash
mysql
is
the
name
of
this
deployment.
This
makes
sense
so
we're
giving
it
a
label
app
wordpress
and
selector
match
labels
app
wordpress
tier,
my
sequel,
not
sure
what
that's
selecting
for
people
know.
Please
let
me
know
I.
A
Explore
that
more
strategy
type
recreate,
so
this
is
something
specific
to
deployments
it,
I'm
guessing
it
describes
what
will
happen
if
something
happens
to
the
containers
or
something
like
that,
I
would
have
to
actually
look
it
up
spin
up
a
kind
of
mini
cube
and
go
through
the
cave
stocks.
They're
super
useful
to
get
started
and
understand
aspects
of
the
yaml
very
useful,
cheat
sheet
very
nice.
A
And
then
I've
got
some
more
labels
here,
app
wordpress
here,
my
sql,
so
these
selector
labels
are
being
used
to
specify
which
pods
in
kubernetes
the
deployment
kind
of
owns.
We
don't
have
a
pod
spec
in
here
we're
not
specifically
saying
we're
making
pods.
A
A
And
then
we're
specifying
the
container
image
that
we
want
to
use,
which
is
my
sql
5.6
and
giving
it
a
name
environment
variable.
We
saw
this
one
before
mysql
root
password
and
then
we're
going
to
make
that
from
a
secret.
Like
we
talked
about
earlier
and
container
port
name,
my
sql
volume
amounts.
My
sql
persistent
storage,
mountain
path,
far
live
my
sequel
and
all
of.
A
A
Because
it's
got
this
separate
one
just
for
the
mic
just
for
the
wordpress,
so
this
is
quite
a
bit
more
text
than
we
saw
in
the
docker
one
and
we
have
honestly
quite
a
bit
more
stuff
for
running
things
at
high
availability
deployments
have
a
lot
of
tools
for
running
things
at
high
availability.
A
I
assume
that's
part
of
what
this
strategy
one
is
about.
I've
got
to
go,
look
that
up
again
and
then
a
common
thing
that
people
talk
about
with
deployments
is
doing
rolling
upgrades
deployments
have
really
cool
smarts
built
into
kubernetes,
for
that,
so
deployments
are
meant
for
being
able
to
run
things
in
a
highly
available
fashion,
as
are
the
persistent
volume
claim,
as
is
the
service.
A
So
we've
got
a
lot
of
really
nice
high
availability
tools
in
here
and
then
in
the
other
one
we've
got
a
service,
a
persistent
volume
claim
and
a
deployment,
so
we've
gone
over
kind
of
what
all
that
looks
like
great.
So
I
want
to
try
to
just
run
this.
A
A
It's
expected
it's
expecting
to
be
created
before
it's
executed.
I
thought
that
at
first
too,
something
like
this
would
work,
if
you
add
it
to
the
top
of
the
example
yeah,
so
you
can
specify
a
persistent
volume
separately.
I've
seen
that
done
pretty
commonly
in
specifying
a
storage
class
as
well
as
the
capacity
of
the
storage.
A
A
A
The
the
chat
might
not
let
you,
but
I
can
do
it.
Cool
apply
and
verify
get
secrets
verify
that
a
person
oh
see,
though,
verify
that
a
persistent
volume
got
dynamically
provisioned.
A
So
let's
try
this
I'm
going
to
go
ahead
and
curl
this
it's
kind
of
nice
that
in
the
kubernetes
documentation
the
examples
have
these
curl
commands.
Let
me
let
me
control
see
that
for
a
second
not
run
this
just
yet
there
we
go
and
ctrl
l
there.
You
go
much
cleaner,
much
prettier
easier
to
see
what
we're
doing
so,
I'm
going
to
curl
down
the
mysql
deployment.yaml
that
we
looked
through
and
then
I'm
going
to
curl
down
the
wordpress
that
we
looked
through.
A
A
Okay,
so
now
we've
downloaded,
I
created
an
episode,
one
folder,
and
then
I
just
put
everything
in
the
top
level.
Folder
I'll
move
all
of
this
stuff
later
so
we've
got
our
wordpress
deployment.yaml,
not
the
wordpress
docker,
that's
a
separate
thing
and
then
mysqldeployment.yml.
A
A
A
A
Yeah,
so
I
don't
have
a
cube,
ctl
setup.
I
think
it's
my
or
a
like
a
local
mini
cube
cluster
set
up
or
anything,
that's
kind
of
important.
So
let's
do
this,
I'm
going
to
open
what
we
just
talked
about
in
virtual
studio
code,
because
this
is
an
easy
tool
for
me
to
use
to
get
a
mini
cube
set
up.
So
there's
a
cloud
code
plugin,
which
is
a
thing
that
google
makes.
A
So
that's
how
I
know
about
it,
because
I
work
at
google,
but
it's
just
a
thing
you
can
use
and
it
can
help
you
manage
your
cube.
Config.
I've
got
like
this
old
cluster
in
here
that
doesn't
even
exist
anymore.
So
I
don't
care
about
that,
but
I
do
want
to
start
a
mini
cube
cluster.
So
I
went
to
cloud
code
and
visual
studio
code
and
then
I
hit
the
plus
button
in
the
kubernetes
thing
and
then
I'm
gonna
say
start
a
mini
cube.
Cluster
mini
cube
cluster
is
currently
stopped.
A
Let's
start
it
oh
look
down
here.
We
can
see
that
it's
spinning
up
a
mini
cube
cluster.
You
probably
can't
see
it
very
well
because
it's
super
tiny,
but
we
are
starting
up
a
cube
cluster
which
we'll
run
this
on.
That
should
be.
A
A
A
I
don't
know
how
long
this
will
take
so
I'll
just
wait
around
here
for
a
couple
more
minutes.
If
it's
not
done,
maybe
we'll
do
something
else.
A
A
But
once
that's
up
we'll
run
the
cube.
Ctl
apply
command,
basically,
which
might
be
a
little
bit.
Oh,
would
you
look
at
that?
A
A
Interesting,
I
haven't
actually
looked
at
the
docker
plugin
in
visual
studio
code,
but
you
can
see
like
all
the
containers
that
I'm
running
hey,
it's
mini
cube.
I
just
saw
a
new
one
come
up
in
docker.
Does
that
mean
well
creating
docker
container,
that's
pretty
cool,
so
we
can
see
in
the
docker
extension
of
a
visual
studio
code,
the
cloud
code
extension
creating
my
mini
cube
cluster.
A
I
got
excited
there
for
a
second
but
oh
well,
so
once
we
do
that
apply
verify
that
the
secret
exists.
So
it's
a
good
thing
that
we
ran
that
cat
command
from
earlier.
A
A
A
But
our
customization.yaml
does
have
both
the
secret
generator
and
the
resources
stuff
that
we
added
earlier.
So
that's
good.
A
Hopefully,
when
we
run
our
customization
it'll,
run
the
secret
generator
and
create
our
secret
as
well
as
running
our
deployment
dials,
so
it'll
run
everything
kind
of
like
dr
compose.
A
Oh,
it
finished
yay
so
we'll
see
if
I
can
do
this
quickly
cool
so
now,
I've
got
a
mini,
cube
cluster
up
and
running,
and
I
wonder
if
I
can
zoom
in
on
this
at
all.
Oh,
I
can
yay
wonderful,
I'm
gonna
close
this,
so
I'm
not
running
a
gke
cluster
right
now,
I'm
just
running
a
local
one
which
hopefully
isn't
sending
my
computer
into
a
tailspin.
A
So
you
can
see
all
the
deployments
that
we
have
running
all
zero
up
them
all
our
pods
all
of
our
services.
These
are
all
of
the
kubernetes
objects
that
we
might
be
running,
which
we
are
running
none
of
currently
in
our
default
namespace,
which
sounds
like
a
fine
place
to
run
stuff
to
me
cool.
A
Looks
like
I've
got
some
problems
with
my
visual
studio
code
setup,
so
I
might
not
be
able
to
run
this
here,
but
let
me
see
here
if
I
might
go
back
to
what
I'm
more
familiar
with.
Let
me
remove
context
under
cluster.
Do
you
want
to
delete
this
old
cluster
that
I
don't
actually
even
have
anymore
from
your
cube
config?
Yes,
I
sure
do
so
now.
My
cube
config
should
just
have
my
mini
cube
in
it.
A
A
Look
hey!
I'm
in
my
mini
cube
cluster!
So
now
I
should
be
able
to
run
this
from
the
command
line
which
I'm
more
familiar
with.
So
let's
do
that:
okay,
not
ks
or
ls.
I
always
like
to
check
where
I
am
okay.
So
now
I
should
be
able
to
run
that
cube.
Ctl
apply
command
that
we
were
looking
at
earlier,
which
is
right
here.
A
Okay,
I
created
a
secret
it
created.
So
the
thing
on
the
left
of
the
slash
here
is
going
to
be
the
kubernetes
object
and
then
on
the
right
is
the
name
of
that
object.
So
we've
got
a
kubernetes
secret.
We've
got
kubernetes
services,
we've
got
deployments
and
persistent
volume
claims,
but
I
don't
see
a
persistent
volume
created,
so
maybe
you're
right.
Maybe
we
do
need
to
add
that
to
this
this
tutorial,
maybe
that's
something
that
we
need
to
submit
as
a
book.
I
don't
know,
let's
find
out.
A
A
A
I
agree.
Mini
cube
via
cloud
code
is
really
nice,
so
it
does
look
like
it
actually
created
a
persistent
volume
dynamically,
which
is
great
to
know
yeah.
This
is
that's.
What
I
just
ran
is
cube.
Ctl
get
pv
right
here.
Hopefully
you
can
see
that
yeah
isn't
that
cool.
So
in
theory
this
should
work,
and
I
think
the
wordpress
and
mysql
should
already
be
up
and
running.
A
A
I
didn't
actually
look
at
it
in
the
wordpress
one
in
the
wordpress
service,
it
does
say,
type
load
balancer,
so
that's
not
going
to
work
out
so
well
on
minicube
is
it
load.
Balancer
is
really
nice
when
you're
working
in
a
cloud
provider,
because
generally
the
cloud
providers
have
a
really
convenient
default
on
plugins.
A
If
you
run
like
in
their
managed
services,
I
guess
is
the
better
way
to
describe
that
where
it'll
spin
up
a
load
balancer
in
the
cloud
for
you
so
running,
load
balancer
in
the
cloud
is
so
easy,
but
oh
okay,
so
the
response
should
be
like
this
wordpress
load
balancer
should
be
pending.
I
don't
expect
it
to
ever
have
an
external
ip,
because
we
don't
have
an
actual
load
balancer
in
front
of
this
load
balancer,
but
it
does
have
a
cluster
ip
and
it
is
up
on
a
node
port.
A
It
looks
like
fun
fact:
load
balancer
type
services
actually
require,
like
they
use
node
ports
to
do
what
they
do,
so
that
makes
total
sense
that
it
would
have
a
port,
even
though
it's
not
type
node
port.
I'm
saying
a
lot
of
words
that
people
might
not
understand
here,
but
there
are
several
different
types
of
services.
A
cluster
ip
service
means
this
app
can
talk
to
other
things
within
the
cluster.
A
A
load,
balancer
type
service
means
that
there's
a
load
balancer
of
some
type
that
you'll
use
to
get
access
to,
whatever
containers
you're
actually
running
on
kubernetes.
So
that's
what
we've
got
here
and
then
there's
a
node
port
type
service
in
kubernetes,
which
will
spin
up
an
actual
port
on
the
node
that
the
container
is
running
on
that
you
can
access
the
container
from
and
load
balancer
uses
that
so
we
should
be
able
to
access
this
on.
A
port
minicube
can
only
expose
services
through
node
port.
The
external
ip
is
always
pending.
A
So
I
don't
know
what
my
local
ip
address
for
my
mini
cube
is.
I
wonder
how
we
can
find
that
without
me
having
the
mini
cube,
command
line
tool
downsides
of
using
cloud
code
to
generate
a
mini
cube
cluster,
I
guess
but
then
once
we
do
that,
I
expect
that
we'll
be
able
to
see
this.
If
I
curl,
I
can't
curl
it
because
I
don't
know
what
the
ip
address.
A
How
do
I
find
out
what
the
ip
address
of
my
mini
cube
services?
Any
suggestions
for
what
I
should
look
up
here
are
most
welcome.
It's
also
almost
2
30,
so
I'm
gonna
try
to
get
off
of
here
soon,
but
I
at
least
want
to
try.
I
know
that
it's
running
in
kubernetes,
we
are
running
a
personal
blog
in
kubernetes,
but
we're
not
running
it
online.
A
We're
not
running
it
in
the
cloud,
we're
just
running
it
locally
and
I
don't
know
how
to
access
it
right
now,
yeah
the
pods
are
up,
so
we
know
that
it's
there,
but
I'll
have
to
figure
out
how
to
actually
access
my
mini
cube,
since
I
don't
actually
have
the
tool
installed
a
little
bit
later,
so
I
don't
want
to
keep
people
for
too
long
yeah
next
week.
We'll
do
part
two
and
and
finish
this
up.
A
So
thank
you
all
for
joining
me
today.
I
had
a
lot
of
technical
difficulties
and
I
appreciate
it
so
much
for
those
of
you
who
paired
with
me.
I
hope
that
you
learned
something
interesting
and
I
hope
that
next
time
will
be
a
lot
smoother.