►
From YouTube: Okteto Walk Through
A
Everyone,
my
name,
is
Kenny
Johnston
I'm,
director
of
product,
covering
the
op
stages
here
at
get
lab.
I
wanted
to
do
a
walk-through
today
of
octet
Oh
Montero
is
a
tool
that
enables
local
development
to
kubernetes
environments,
so,
instead
of
having
to
build
and
create
your
own
mini,
cube
or
other
environment
locally,
in
order
to
test
your
changes
in
how
they
would
actually
run
in
a
production,
kubernetes,
environment
or
I,
guess
a
realistic,
kubernetes
environment,
you
can
have
octet,
oh
create
a
cluster
for
you
and
it
kind
of
forwards.
A
A
My
zoom
window
set
up
correctly
I
will
say:
I've
done
this
I've
done
this
walkthrough
that
I'm
about
to
do
for
a
go
app
previously,
and
so
some
of
the
things
like
installing
a
CLI,
our
CLI
octet
osceola,
are
already
going
to
happen
and
creating
an
account
in
octet,
o
I've,
already
created,
and
so
there'll
be
a
couple
of
those
places
where
I'm
going
to
follow
the
instructions.
But
it'll
it'll
appear
like
I've,
already
done
it
and
that's
cuz
I
have
okay.
So
first
thing
you
do
install
the
CLI.
A
A
Okay,
I
didn't
actually
say
anything
bill
because
it
already
had
been
self
okay,
so
I've
got
that
installed
now
I'm
gonna
do
a
potato
login
I
logged
me
in
because
I'd
already
had
an
account
that
I'd
connected
with
my
github
account.
Here
it
is
kids
Johnston
his
name
space
already
created
and
I'm
locked
it
all
right.
What's
the
next
thing,
Doc's
tell
me
to
do.
A
Took
the
fact
that
I
had
had
a
namespace
already
created
here,
and
that
includes
a
cluster
and
basically
like
downloaded
all
the
credentials
for
that
cluster
into
my
on
my
local
machine
and
gave
me
a
kind
of
cube,
cube,
kubernetes
config
file
that
I
can
use
for
access.
Okay,
so
updated
contexts
gave
me
all
that
stuff.
Okay
added.
A
To
my
config
file
and
set
it
as
the
current
one
just
to
make
sure
I
should
do
coop
CTL
get
all,
and
that
won't
tell
me
there
any
resources.
No
resources
found
that
I
am
in
the
right.
Namespace
go
viously,
hide,
keep
CTL
applied
or
installed
download
a
sample
app.
Ok,
so
this
step
three
I've
done.
It
involves
getting
and
so
I'd
go
app,
deploying
it
and
then
seeing
that
any
remote
and
then
doing
some.
This
remote
development
part.
B
A
A
Okay,
so
this
is
actually
going
to
deploy.
It
looks
like
it
created
a
deployment
called
blog
and
a
service
called
blog.
Okay,
both
of
those
were
pretty
great.
So
now
we
are
going
to
use
the
dev
version
of
the
ruby
sample
app.
We
just
deployed
as
our
remote
development
environment
to
do
that,
I'm
going
to
do
a
teto
up.
A
A
A
So
this
is
just
telling
me
that
my
look
whole
environment
I-
can
get
all
there
okay,
so
our
tarot
up
starts
the
remote
development
environment,
which
means
this
there's
no
loops.
My
one
we're
done
with
that
one.
Okay,
so
total
means
that
file
synchronization
is
created
and
the
remote
shell
is
started
in
your
loving
environment.
They'll
test
on
your
application
is,
if
you
run
your
local
machine,
so.
A
B
B
A
A
A
A
B
B
B
B
A
A
A
B
A
A
A
A
B
A
A
Would
continue
to
get
this
traffic
Oh
No?
Okay?
So
when
you
do
that
the
live
environment
is
no
longer
available,
just
using
my
or
my
environment
and
I
guess
you
could
set
those
up
in
octet,
oh
okay!
So
it's
up!
What
happened
is
that
container
I
went
there
with
file
synchronization?
Anything
that's
changed
is
getting
forward
back
to
me.
B
A
A
A
A
B
A
A
A
A
You
could
get
your
debug
tools
locally.
That
would
be
pretty
cool.
You
have
vs
code
debug
so
that
you
would
immediately
have
to
add
breakpoints
and
instead
of
running
it
I
mean
to
run
it
locally
on
a
locally
configured,
Korean
cluster,
you
running
it
on
the
remote
or
teto
cloud,
but
get
all
of
your
local
debug
tools.
That's
pretty
cool.
B
A
A
Maybe
everybody
else
is
doing
the
same
thing
and
I'm
just
seeing
differently,
because
the
it
was
routing
my
traffic
I.
Imagine
that's
what's
going
on
so
for
me,
I
always
had
the
same
URL
if
I'm
in
a
local
dev
mode,
I
get
traffic
forwarded
to
and
synced
to
a
new
container
for
my
development
and
then
but
the
production
traffic
is
still
going
for
everyone
else
to
this
site
and
then
I
can
turn
off
local
dev
and
see
my
own
environment
locally.
A
A
A
B
A
Ste
activating
my
development
environment,
so
that
connection
is
no
longer
there
and
it's
back
to
production
right
now.
Okay,
so
that's
kind
of
the
workflow
you
would
want
to
go
through.
You
would
work
on
your
development
environment.
Do
arc
teto
up
work
until
it
was
in
the
state
that
you
wanted.
Do
an
octet.
Oh
push!
Push
that
to
your
production
environment.
You
know.
You'd
also
wants
to
store
it
and
source
control
somewhere
or
if
you
didn't
want
to
push
it,
you
just
wanted
to
move
back
to
the
production
environment.
A
You
could
say
octet,
oh
down,
and
it
would
go
back
to
using
what
was
what
was
last
pushed
to
that
environment.
So
I
think
that
would
be
the
workflow
you
would
use
here,
and
then
you
also
get
the
local
debug
tools,
which
is
pretty
cool
customize
it.
Let's
see
what
else
they
say
you
customize
it
anything
else.
I
can
do
in
this
UI.
A
You
can
destroy
environments,
yeah,
so
pretty
straightforward.
It
does
give
you
a
nice
workflow
for
developing
in
local
environments.
I
think,
instead
of
doing
today,
push
you
would
want
to
commit
your
code,
but
you
could
do
it
without
sinking
any
changes
to
your
local
repository,
which
seems
a
little
dangerous.
You
wouldn't
be
doing
any
tests,
but
yeah
you
could
publish,
but
I
think
for
a
purely
development
experience
having
a
local
having
a
remote
cluster
that
you're
sinking
changes
to.
A
So
you
can
really
quickly
get
feedback
into
how
your
application
looks
and
performs
as
a
kubernetes
deployed
application,
so
say,
you're
trying
to
test
your
kubernetes
manifests
in
other
configuration
files.
You'd
be
able
to
do
that
really
quickly,
as
opposed
to
having
a
game,
have
a
mini
queue
installed
and
not
really
know
how
and
having
a
good
sense,
but
not
having
as
much
immediate
feedback
into
whether
your
application
is
building
and
performing
correctly.
So
a
really
cool
tool
super
interesting,
especially
from
a
from
a
developer
development
experience
perspective.
That's
why
I
have
thanks
everybody.