►
From YouTube: S205 - .NET Core Microservice Development Made Easy with Azure Dev Spaces - Lisa Guthrie
Description
Distributed architecture allows your applications to scale, but how do you build it? It can be difficult or impossible to run a large microservice-based application on your dev workstation, but using mocks for pieces of the application can introduce problems when you go to integrate your code. Azure Dev Spaces can help! In this session, we'll look at using .NET Core with Dev Spaces to make your development and testing experience better.
A
You
have
lots
of
micro
services
that
allow
you
to
scale
and
allow
you
to
grow
into
a
really
large
dev
team
without
stepping
on
each
other's
toes,
but
it
can
be
really
hard
to
manage
that
from
a
developer
perspective,
you
can't
even
run
a
large
cloud
native
application,
the
entire
cloud
native
application
on
your
local
development
workstation
and
as
your
teammates
are
making
updates.
It
can
be
really
challenging
to
keep
things
in
sync
or
keep
your
your
mocks
or
your
stubs
in
sync,
with
the
actual
application.
A
So
this
is
where
we're
we've
introduced,
Azure
dev
spaces
to
help
with
a
lot
of
these
challenges.
Azure
dev
spaces
is
an
extension
to
azure
kubernetes
service
and
at
the
heart
of
a
droid
dev
spaces.
Is
this
concept
of
a
shared
IKS
cluster
for
team
development.
You
can
create
this
cluster.
You
and
your
teammates
can
all
collaborate
and
run
your
application
within
this
shared
cluster.
A
This
gives
you
a
lot
of
benefits.
It
allows
you
to
onboard
new
team
members
with
really
minimal
setup.
You
don't
have
to
install
docker,
you
don't
have
to
install
helm.
You
don't
have
to
clone
your
entire
repository
and
know
about
all
the
dependencies
that
your
dependent
services
have.
You
can
simply
install
an
extension
for
Visual,
Studio
or
Visual
Studio
code
or
there's
also
a
command-line
interface.
You
can
mix
and
match.
A
A
You
don't
have
to
write
stubs,
keep
those
in
line
with
what's
going
on
with
the
actual
production
services.
If
your
teammates
make
an
update
to
another
service,
then
you
see
those
changes
right
away.
They
can
put
them
into
the
team
cluster
as
well,
and
you
don't
have
to
synchronize
code
or
rebuild
the
service
or
anything
like
that
when
your
service
calls
their
service,
you
automatically
see
the
latest
version
of
that
service.
That's
running
in
your
shared
cluster,
so
let's
take
a
little
bit
of
a
closer
look
at
how
this
works.
A
So
you've
got
your
development
workstation
and
when
you
press
f5,
you
can
run
that
code
that
you've
been
working
on
up
in
an
IKS
cluster
that
is
enabled
with
dev
spaces
that
has
had
a
dev
spaces
controller
created
on
it,
and
you
can
iterate
very
quickly.
We've
made
a
lot
of
optimizations
to
make
this
process
as
fast
as
possible.
So,
for
example,
if
you
just
make
a
simple
change
to
an
HTML
file,
we
don't
go
through
and
completely
rebuild
the
container
image.
That's
running
that
application.
A
We
simply
put
that
that
updated
file
up
and
map
that
into
the
container
that's
already
running,
and
you
see
those
changes
right
away.
Similarly,
we
don't
rebuild
the
container
if
you
just
edit
server
code
like
Java,
Script
files
or
c-sharp
files.
We
just
rebuild
that
particular
code
and
then
map
that
into
the
running
container,
the
only
things
that
really
force
us
to
tear
down
a
or,
if
you,
for
example,
change
a
docker
file
or
a
helm
chart
or
something
else
that
really
changes.
The
way
that
that
container
is
deployed.
A
Also,
your
teammates
can
be
using
the
same
cluster
and
going
through
this
exact
same
process
with
running
their
code
up
in
the
cloud,
and
you
all
benefit
from
having
access
to
what
you're
all
working
on
now.
One
question
we
get
is
is:
is
this
how
we
is
this?
How
I
deploy
to
production
as
well?
And
the
answer
is
no.
We
see
this
as
really
being
part
of
that
development
process.
Eventually,
when,
through
this
iterative
process,
you
get
to
the
point
where
you
feel
like
you
have
code,
that's
that's
really
ready
to
go
on
to
production.
A
A
Another
feature
that
really
helps
with
collaboration
is
the
concept
of
spaces.
So
here
you
can
see
a
diagram
of
small
micro
services
based
applications.
There's
three
micro
services
that
make
up
this
application.
Web
front-end,
employee
search
and
my
Web
API
they're
communicating
with
each
other,
and
you
can
see
that
there's
a
URL,
a
public-facing
URL
that
you
can
use
to
access
this
application.
Now.
A
A
This
does
not
replace
the
version
of
employee
search.
That's
running
up
in
the
team's
default
space.
Susie
has
her
own
version
that
she
can
edit
that
she
can
live
debug
and
so
on,
and
she
gets
her
own
endpoint,
her
own
public
endpoint.
As
you
can
see
in
this
diagram,
it's
the
the
URL
of
the
main
application,
but
prefixed
with
Susie
the
name
of
her
space
and
dot
s
when
requests
come
in
to
the
application
on
that
endpoint.
What
happens
is
that
dev
spaces
looks
the
the
request
comes
into
the
web.
A
Front-Ends
service
dev
spaces
looks
to
see
if
there's
a
copy
of
web
front-end
that's
running
in
Susie's
space,
because
it
sees
that
Susie
in
the
URL,
and
it
knows
that
it
needs
to
look
in
Susie's
space
for
of
a
copy
of
that
service.
In
this
case,
there
is
no
copy
of
web
frontend
running
in
Susie's
space,
so
dev
spaces
will
direct
that
request
to
the
web
front-end
service
running
in
the
team
space
in
the
default
space.
Now,
if
web
front-end
calls
out
to
employee
search,
dev
spaces
goes
through
that
same
process.
A
It
sees
that
Susie
header
attached
to
that
request,
and
it
looks
to
see
if
there
is
a
version
of
employee
search
running
in
Susie's
space.
Now,
in
this
case,
there
is
there's
that
copy
that
Susie
is
working
on,
so
it
will
automatically
redirect
that
request
to
Susie's
version
of
employee
search.
This
is
a
second
end
point,
so
if
Susie's
version
is
completely
broken
or
if
she's
live
debugging
it,
so
the
service
is
not
responding.
At
that
particular
moment.
A
All
of
Susie's
teammates
can
still
access
the
team's
version
of
that
service
at
the
normal,
my
app
URL,
what
Susie's
doing
in
her
space
does
not
affect
them
at
all
and
then.
Similarly,
if
employee
search
calls
out
to
my
web
api,
then
dev
spaces
looks
to
see
if
there's
a
version
of
my
web
api
running
in
Susie's
space
in
this
case
there's
not
so
again
it
redirects
back
to
that
the
version
that's
running
in
the
team
space
so
really
important.
A
Here,
it's
not
that
Susie
has
every
copy
of
every
service
running
in
her
space
in
this
shared
cluster.
She
only
has
the
services
that
she's
working
on
that
are
directly
impacting
her,
so
she
sees
updates
right
away
to
all
the
other
services.
If
somebody
were
to,
if
I,
if
I'm
working
on
that
web
front-end
service
and
I
have
some
updates
to
web
front-end
and
I
put
those
in
the
team
space,
then
again,
Susie
will
will
automatically
see
those
updates.
She
doesn't
have
to
rebuild
my
version
of
web
front-end
or
anything
like
that.
A
It's
just
that
when
she
comes
in
on
her
Susie
endpoint,
she
will
see
my
updated
version
of
web
front-end,
so
this
can
really
help
with
finding
problems
that
might
normally
be
caught
further
down
the
line
in
integration
testing.
It's
very
very
easy
to
get
these
services
up
and
running
in
the
team's
cluster,
and
then
you
can
start
to
uncover
some
of
these
problems.
A
All
right
so
here
I
have
a
very
simple
web
application
that
I've
built,
and
you
can
see
that
there's
an
about
page
here
and
it
lists
out
the
members
of
the
development
team
that
built
this
website-
and
you
know
this
page
is
pretty
ugly
I,
don't
really
like
the
formatting
of
these
names
and
they're,
not
in
any
sort
of
order
or
anything.
So
I've
made
a
few
updates
to
this
website
in
order
to
show
the
names
in
alphabetical
order
and
also
in
a
nicely
formatted
bulleted
list.
A
So
if
I
take
a
look
at
this
code,
the
the
employee
names
are
actually
coming
from
a
back-end
web
api
and
my
web
front-end
code
calls
this
employee
search
api
built
by
my
teammate
susie
to
get
the
names
of
the
developers.
Well,
this
employee
search
service,
it's
actually
it's
a
no
js'
service,
I'm
a.net
developer
and
I
don't
even
have
the
nodejs
workloads
or
whatever
I
need
and
installed
on
my
machine
so
I.
A
And
my
code
is
going
to
call
out
to
that
mock
service
and
bring
back
the
data
and
then
format
that
nicely.
So
this
is
great.
I
can
see
that
I've
got
a
nice
bulleted
list
here,
rather
than
that
ugly
formatting
that
I
had
before
plus
all
of
these,
these
names
are
now
alphabetized
based
on
last
name,
so
Martin
and
appears
at
the
top
and
going
down
to
Simon
here
at
the
bottom,
alright
great.
So
my
codes
working,
but
of
course
this
is
with
a
mock
so
before
I
check
in
this
code.
A
I
would
want
to,
of
course
change
that
to
actually
make
a
call
out
to
my
the
the
service
that's
running
in
IKS,
so
that
when
I
deploy
this
service
into
my
IKS
cluster,
it
makes
that
proper
call.
So
I'll
go
ahead
and
save
this,
and
today
this
might
be
where
my
development
process
ends.
Maybe
I
check
this
code
into
source
control.
My
CI
CD
process
kicks
in
maybe
deploy
the
code
to
a
test
environment.
A
Maybe
there
are
some
automated
tests
that
run
against
it
or
maybe
I
have
the
opportunity
to
test
it
manually,
but
I'm
kind
of
done
at
this
point.
I
can
all
I
need
to
do
is
check
in,
but
with
subspaces
I
have
another
option.
I
can
very
quickly
take
this
code,
which
I
know
is
destined
to
run
in
IKS
and
with
just
a
few
clicks.
I
can
run
it
live
in
aks.
So
let's
see
how
that
works.
I'm
gonna
change.
A
Here
I'm
gonna
have
my
aks
cluster
name
here.
This
is
my
team's
shared
aks
cluster,
where
I'm
working
and
where
all
my
teammates
are
working
as
well
and
I
can
also
choose
a
space
here
now.
It
so
happens
that
the
updates
to
this
about
page
are
being
tracked
in
users
story,
one
two,
three,
four,
five
six,
so
what
my
team
has
done
is
create
a
space
specifically
for
that
user
story.
A
It's
a
child
of
this
default
space.
So
thinking
back
to
the
diagram,
I
showed
if
any
of
the
services
that
comprise
this
application
are
not
running
in
that
user
story
space,
then
dev
spaces
will
automatically
use
the
versions
of
that
service
that
are
running
in
that
default
space.
But
if
there
are
any
updated
services
in
this
user
story
space,
then
that's
what
will
be
used
instead.
A
I'll
also
just
highlight
a
little
change
that
I
made
to
this
code.
In
order
to
enable
all
of
this,
you
can
see
that
this
code
here
propagates
a
HTTP
header,
called
a
zds
route,
as
when
a
request
comes
in
to
dev
spaces,
enabled
space,
then
if
there
is
a
prefix
to
that
URL.
So,
for
example,
the
Susie's
is
that
we
saw
in
the
diagram
before
it
pulls
off
that
prefix
and
it
sticks
it
in
this
AZ
DS
route
as
header.
A
So
then,
as
the
request
propagates
throughout
the
different
services
in
the
system
that
header
propagates
as
well
and
that's
how
dev
spaces
knows
that
this
request
originated
on
Susie's
endpoint
or
on
user
story.
One
two,
three
four
five
six,
and
it
knows
which
services
to
direct
that
request
to
based
on
that.
So
it's
really
important
that
when
I
do
make
a
request
out
to
another
service,
I
make
sure
that
I
propagate
this
header
as
well
in
my
code,
so
that
the
routing
works
correctly.
A
But
aside
from
that,
this
should
be
ready
to
go
in
dev
spaces.
All
I
have
to
do
I
again:
I,
don't
need
to
have
docker
installed
locally
I,
don't
need
to
build
a
container
image.
I,
don't
need
to
create
a
container
registry
or
anything
like
that.
I,
just
press
f5
in
visual
video
I've
got
the
only
thing
that
I
did
need
to
install
was
the
visual
studio,
kubernetes
tools.
Extension,
that's
the
one
special
thing
that
I
have
installed
over
and
above
just
visual
studio
15.8,
and
that's
what
what
gives
me
this
functionality.
A
So
you
can
kind
of
see
in
the
output
window
here
that
dev
space
is.
It
is
synchronized
my
code
up
to
the
cluster
and
it's
going
ahead
and
it's
building
the
container
image
while
it
does
that
I'm,
just
gonna
pull
up
the
kubernetes
dashboard
here
and
just
show
you
a
little
bit
of
what's
going
on
behind
the
scenes,
OOP.
That
space
is
a
little
too
quick
for
me.
There
we'll
come
back
to
that.
A
Let's
take
a
look
at
what's
going
on
in
Corona
and
kubernetes
itself,
so
here
I
am
in
the
kubernetes
dashboard
standard,
kubernetes,
IKS
stuff
here
and
I
am
specifically
in
the
default
namespace,
which,
if
you
remember,
is
that
that
root
namespace
for
the
shared
team,
cluster
and
I've
got
a
bunch
of
stuff
running
in
here.
There's
web
front-end,
which
is
this
service
that
I've
been
have
modified
the
code
for,
but
there's
employee
search
as
well,
of
course,
and
there's
a
couple
of
other
services
as
well
running
in
here
in
the
default
namespace.
A
If
I
click
on
the
namespace
list
here,
you'll
also
see
that
there's
just
a
standard,
kubernetes
namespace
called
user
story,
one
two,
three,
four:
five:
six,
and
if
I
click
into
user
story,
one
two,
three
four
five
six
see
what's
running
in
here
and
there's
web
front-end,
and
you
can
see
that
that
was
just
just
started
a
minute
ago
that
when
I
pressed
f5
in
Visual
Studio-
and
it
looks
like
my
teammate
Susie-
has
also
been
updating
that
employee
search
service.
So
she's
got
a
version
of
that
running
here
in
this
user
story,
space.
A
The
other
two
services
that
you
saw
running
in
default
and
again
it
could
be
two
it
could
be
20.
It
could
be
200
depending
on
your
application.
Those
are
not
running
in
this
user
story.
Space
they're,
not
they've,
not
been
updated
as
part
of
this
user
story.
So
if
web
front-end
or
employee
search
make
any
calls
to
those
services,
they'll
go
back
back
to
the
versions
of
those
services
that
are
running
in
default,
all
right.
So,
let's
see
how
this
all
came
together.
A
So
here's
my
updated
about
page
and
I
can
see
that
my
my
I've
got
my
nice
bulleted
list
now
of
employee
names,
but
there's
something
wrong
here
and-
and
this
is
kind
of
subtle,
but
when
I
looked
at
it
before
when
I
looked
at
it.
In
my
when
I
was
running
it
locally
here,
the
the
named
list
of
names
was
sorted
by
last
name,
so
Simon
Winther
appeared
at
the
bottom
and
now
Simon
went
there
is
somewhere
here
in
the
middle.
So
for
some
reason,
that
alphabet
is
alphabetization
is
not
working.
A
This
is
kind
of
a
subtle
bug
and
you
know
maybe
we've
got
an
integration
test
that
checks
for
to
make
sure
that
things
are
alphabetize
correctly,
but
that
would
be
a
very
easy
thing
to
miss
and
remember
the
only
change
that
I
made
in
my
code
was
switching
from
using
that
the
stubbed
service
that
returned
my
my
stubbed
out
JSON
data
to
using
the
actual
live
employee
search
service.
So
I've
got
an
inkling
here
that
there
may
be
some
sort
of
an
incompatibility
here
between
my
updated
web
front-end
service
and
the
updated
employee
search
service.
A
That
I
could
see.
My
teammate
Suzy
has
has
put
into
our
user
story
space.
Oh
one,
other
thing,
sorry
that
I
should
have
highlighted
here
is
the
URL,
so
the
URL
for
the
the
standard
of
the
the
original
version
of
the
site
was
just
web
front-end
and
then
the
usual
IKS
stuff.
Afterwards,
the
the
way
that
I
got
to
my
updated
code
was
that
I
prefixed
that
URL
with
user
story,
one
two,
three,
four,
five,
six
s
all
right
so
great!
This
is
great.
A
We've
identified
a
bug
that
normally
it's
just
taking
me
a
few
minutes
to
run
and
see
this
bug.
Normally.
This
would
be
a
whole
long
process
of
waiting
on
builds
and
c
SED
and
so
on.
So
it's
great
that
I've
identified
it,
but
as
your
dev
spaces
even
goes
one
step
further
and
provides
you
the
ability
to
much
quickly
figure
out
exactly
what's
going
on
with
this
bug.
A
Now
the
downside
here
is
that
if
my
teammate
Susie
wanted
to
test
out
her
employee
search
service
or
wanted
to
do
anything
with
that
version,
that's
running
in
the
user
story
space.
She
she
wouldn't
be
able
to
come
through
web
frontend
right
now,
because
of
course,
I'm
live
debugging
it.
What
I
could
do
is
create
a
child
space
of
that
user
story.
Space
maybe
called
Lisa
and
run
just
this
service
in
that
Lisa
space
and
then
I
could
live
debug
it
all
day.
A
Long
Susie
could
still
get
to
the
the
user
story,
version
of
the
application
running
at
the
user
story,
URL
or,
of
course,
to
the
team's
version
running
at
the
default
URL,
but
maybe
I've
communicated
with
her
to
let
her
know
that
I
I
need
to
do
this
real
quick.
Hopefully
it's
just
a
quick
bug
and
let's
see
what
we
can
do
here,
all
right,
so
when
I
clicked
on
about.
Of
course,
it
made
another
call
into
this
code.
I
am
now
broken
into
the
debugger
and
I
am
live
debugging
this
service
running
in
kubernetes.
A
If
I
look
at
full
name
here
now,
folium
should
have
the
first
name,
and
we
did
this
split
on
comma
on
the
Kama.
It
was
expecting
a
list
of
employee
names
that
were
in
the
format
last
name,
comma,
first
name
but
and
it
should
have
put
Peters
last
name
into
the
zero
spot
and
Peters
first
name
into
the
one
slot,
but
it
looked
like
it
didn't
do
that.
In
fact
it
looks
like
maybe
the
format
of
this
data
has
changed
so
rather
than
employee
here
being
set
to
Toth,
comma
Peter.
It's
it's
peter,
toth,
comma.
A
If
I
go
back
and
looked
at
my
stub
data,
I
can
see
that
it
was
Toth,
comma
Peter,
so
here's
the
problem
is
that
employee
search
has
apparently
changed
the
the
format
that
it's
using
to
return,
that
employee
name
data
to
me
and
my
code
just
needs
to
be
updated
in
order
to
to
to
accommodate
that.
So
I'll
just
go
ahead
and
continue
here.
A
When
this
comes
back,
I
can
just
really
quickly
stop
debugging
and
I'll
just
change
this.
This
will
be
a
little
bit
quick
and
dirty,
but
I'll
just
change
it
to
be
a
space
delimiter
and
then
I'll
I'll
switch
all
these
zeros
to
ones
and
ones
to
zeros.
That
explains
why
the
the
alphabetization
was
off
because
it
was
alphabetizing
based
on
the
full
name,
so
like
peter
toth,
rather
than
just
Toth.
Alright,
this
looks
good
I'm,
still
gonna
I.
A
Think
I'm,
just
gonna
still
have
a
trailing
comma
there
at
the
end
of
the
the
name,
but
I
will
we'll
just
at
least
make
sure
that
that
I've
identified
the
right,
the
right
problem
here,
I'm
gonna,
warn
you
I've
been
having
DNS
issues
today
and
I'm
a
little
little
concerned
because
it
said
in
my
output
window
here
that
the
DNS,
the
Public
DNS
name,
was
pending
registration.
Okay,
so
it's
it's!
It's
not
pulling
up
here.
A
I'll,
take
a
question
and
we'll
come
back
to
it
and
see
if,
if
that
DNS,
the
Public
DNS
end
point
has
gotten
properly
registered.
Let's
see
so,
we've
got
a
question
that
Microsoft
promotes
chaos,
which
Orchestrator
is
better
to
create
a
microservices
solution
as
your
service
fabric
or
aks.
That's
a
great
question,
and
it's
one
that
we
got
a
lot
and
I
guess.
The
answer
is
both
would
be
my
answer.
A
It
really
depends
on
what
you're
trying
to
do
each
both
aks
and
kubernetes
in
general
and
service
fabric
have
different
strengths,
and
so
certainly
with
aks.
A
lot
of
people
like
that
kubernetes
is
open
source
and
that
there's
a
great
community
around
kubernetes.
A
lot
of
improvements
that
are
being
made
within
that
community,
where
sometimes
we
see
people
leaning
towards
service
fabric
or
preferring
service
fabric,
is,
for
example,
if
you
have
legacy
windows,
applications
running
on
the.net
framework,
you're,
not
ready
or
maybe
you're,
not
able
to
migrate
to
dotnet
core
and
linux.
A
You,
you
don't
really
have
any
options
there
on
a
chaos
today,
aks
is
Linux
only
that,
of
course
implies
dotnet
core
from
a
development
perspective.
So
so
we
see
a
lot
of
people
looking
at
service
fabric
when
they're
in
that
situation.
Service
fabric
also
has
some
additional
features,
such
as
stateful
services
that
appeal
to
two
people,
just
depending
on
what
what
their
application
needs
and
what
some
of
the
requirements
are,
so
they
they
definitely
coexist.
A
There
they're
both
wonderful
orchestration
platforms
and
we're
seeing
tremendous
adoption
in
both
spaces,
but
there's
there's
just
some
differences
depending
on
what
you're
trying
to
do
and
what
some
of
your
preferences
are
all
right.
Let
me
see
if
our
our
dns
has
come
back
here.
No,
unfortunately,
has
not
come
back
to
show
that
the
update,
but
hopefully
you
got
the
picture
that
that
I
was
able
to
very
quickly
run
that
my
code
in
IKS
I
was
able
to
really
do
a
full
end-to-end
test
across
my
application.
A
So
not
just
my
service
running
with
data
that
I
had
massaged
myself,
but
actually
using
data
calm
from
other
services,
and
you
can
imagine,
if
maybe
the
answer
here
rather
than
me,
updating
my
code
was
perhaps
to
go
to
my
teammate,
Susie
and
say
hey.
Why
did
you
stop
returning
data
in
the
comet
delimited
format?
If
Susie
were
to
update
her
code?
I
would
see
those
updates
right
away,
and
that
would
be
another
solution.
Besides.
Just
besides
me
updating
my
code,
there
are
any
other
questions.
I
can
take.
A
Those
I
will
also
switch
back
to
my
slide
deck
quickly
here
and
I
just
wanted
to
make
sure
to
put
up
the
the
URL
for
our
documentation
on
dev
spaces.
So
just
a
word
on
sort
of
where
we're
at
dev
spaces
is
currently
in
public
preview.
So
you
are
welcome
to
go
out.
You
can
try
everything
that
you've
seen
here
today
and
everything
that
you
need
to
get
started
is
at
this
akms
slash
get
a
zds
URL.
A
We
do
have
tutorials
for
dotnet,
which
I
know
is
really
interesting
for
this
audience
or
what
this
audience
is
probably
going
to
be
mostly
interested
in
and
again,
you
can
either
use
Visual
Studio
as
I
was
showing
today
or
you
can
use
Visual
Studio
code
with
dotnet
core.
In
addition,
we
do
have
first-class
support
for
nodejs
and
for
java
java
is
just
recently
announced,
or
we
just
recently
put
that
support
out
there.
A
So
you're
some
of
the
first
to
know
about
that,
and
what
I
mean
by
first-class
support
is
everything
that
you
saw
me
doing
here
today
with
being
able
to
live
debug
services
and
press
one-click
from
Visual
Studio
or
Visual
Studio
code
to
get
code
up
and
running
in
kubernetes.
There
is
also
a
command-line
interface
for
dev
spaces
and
that
can
be
used
with
any
language.
So
we
we
don't.
A
But,
for
example,
if
you
had
a
go
app
and
you
already
have
a
docker
file
for
it
and
you've
already
created
a
home
chart
or
gotten
it
up
and
running
in
kubernetes,
you
can
use
those
artifacts
to
to
run
that
application
in
dev
spaces
as
well
and
to
get
all
of
the
routing
features
there.
So,
as
you
saw
in
my
demo,
I
said
that
I
had
this.
A
The
service
that
I
was
interacting
with,
which
was
a
node,
app
and
I,
didn't
have
to
ever
build
that
or
run
that
it
was
just
running
up
in
my
cluster,
and
the
same
goes
for
absolutely
anything
that
you
can
run
in
an
IKS
cluster
yeah,
so
definitely
check
out
the
documentation
here.
If
you're
interested
in
playing
around
with
dev
spaces,
we've
got
quickstarts
and
tutorials
to
walk
you
through
the
whole
process.
Oh
I'll
wait
a
few
more
minutes
to
see.