►
From YouTube: Create Visually Compelling Developer Experiences for Kubernetes... - Ivan Towlson & Ralph Squillace
Description
Join us for Kubernetes Forums Seoul, Sydney, Bengaluru and Delhi - learn more at kubecon.io
Don't miss KubeCon + CloudNativeCon 2020 events in Amsterdam March 30 - April 2, Shanghai July 28-30 and Boston November 17-20! Learn more at kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects
Create Visually Compelling Developer Experiences for Kubernetes on VS Code - Ivan Towlson & Ralph Squillace, Microsoft
Great command-line developer tools are widely available for the Kubernetes ecosystem, but fabulous visual developer environments are coming along more slowly, hindering uptake among application developers who are new to container orchestration or who prefer visually rich development environments. This session will show how to build upon the free Kubernetes extension for the open-source Visual Studio Code (VS Code) editor to provide your own custom, developer-oriented experience for use with any kind of Kubernetes cluster. We’ll show how you add to the behaviors and views in the VS Code k8s extension and demonstrate several different extensions built on it, each illustrating a different way to make Kubernetes application development easier, faster, and more effective for an ever-wider array of developers. You’ll leave empowered to create your own new visual experiences for Kubernetes.
https://sched.co/MPXc
A
Good
morning,
everyone
I
great
crowd.
Thanks
for
coming,
my
name
is
Brian
Boram
I
am
your
track
host
for
today,
I
am
gonna,
do
very
little
other
than
to
introduce
your
speakers.
I
do
want
to
say,
I.
Think
V
s
code
is
incredibly
cool.
It's
a
little
biased
there.
Maybe
so
let
me
introduce
Ivan
Tolson
and
Ralf
Squillace.
B
B
So
the
conventional
wisdom
in
the
Copernicus
community
is,
and
indeed
in
in
a
lot
of
the
Linux
community,
is
the
developers,
love
command
lies
engineers,
love
command
lines
because
they
can
be
really
productive
with
them.
They
can
rattle
out
these
arcane
incantations.
They
can
string
them
together
into
batch
scripts.
Life
is
good,
but
it
neglects
a
significant
constituency.
Not
everybody
is
adept
with
all
the
tools
that
that
we
are
adept
with
all
that
many
or
that
the
the
elite
developers
are
adept
with.
B
So
command-line
tools
sometimes
fall
short
of
gooeys.
In
several
ways,
one
of
them
is
discoverability
the
ability
to
sort
of
see
what
options
you
have.
The
reason
that
we
have
window
I
menuing
systems,
for
example,
is
so
that
people
can
discover
commands
incrementally,
rather
than
having
to
figure
them
out
through
a
help
system
or
by
trial
and
error,
or
by
reading
documentation.
B
Gooeys
can
help
with
visualization,
with
seeing
relationships
between
things
even
get
the
supreme
command
line
tool.
The
supreme
obscure
command
line
tool
comes
with
get
K,
because
sometimes
people
just
need
to
see.
What's
going
on
and
gooeys
can
often
be
more
context-aware
they
can.
They
can
integrate
things
in
a
way
that
one
part
of
the
workflow
is
aware
of
their
iPod
workflow.
That
you're
focusing
on
this
particular
thing.
The
time
command
lines
are
often
quite
stateless.
B
B
And
so
this
is
a
comment
from
Brendon
one
of
the
the
founders
of
kubernetes
now
works
at
Microsoft,
but
from
the
the
blog
post,
announcing
the
1.0
of
the
protocol
that
tell
you
about.
This
is
again
tying
with
this
theme
of
democratizing
kubernetes
engineering,
making
it
accessible
to
everybody
not
just
to
those
to
do.
The
expert
practitioners.
B
B
And
if
you
don't
live
only
on
the
command
line,
you
don't
do
your
kubernetes
work.
You
don't
live
on.
You
should
be
able
to
do
things
in
your
editor.
You
should
be
able
to
if
you,
instead
of
having
to
do
kubernetes
solely
on
the
command
line,
you
should
be
able
to
do
that
in
redditor
as
well,
and
now
you
can,
though,
conditions
apply.
B
And
that
link
will
take
you
to
some
where
you
can
install
it
if
you
are
using
vs
code,
so
we
have
built
a
an
extension
for
Visual
Studio
code.
You
can
that
you
can
install
from
marketplace.
It
is
fully
open
source
100%,
open
source
I
can
show
you
the
code
actually
I'm
not
going
to
show
you
the
coaxes,
the
some
of
it
bit
ugly,
but
I
can
show
you
that
you
can
raise.
You
can
raise
bugs
against
us
and
people
do
we
take
pull
requests
and
I
say
all
of
that
source
code
is
available.
B
B
It
works
with
any
kubernetes,
it
is
driven
off
your
Cube
config,
it
uses
cube
cuttle
or
one
of
those
inferior
tools
like
cube
control
or
cube
cuddle
or
QB
kutol,
and
a
little
bit
is
done
with
the
javascript
api.
But
again
these
are
all
open-source
components.
They
are
all
cloud
agnostic,
kubernetes,
core
components.
B
There
are
no
cloud
specific
components,
apart
from
things
that
are
used
for
specific
aesthetic,
provisioning
like,
for
example,
merging
a
cloud
config
into
a
cube,
config
or
creating
a
cluster,
or
anything
like
that.
So
obvious.
There's
some
cloud
bits
there,
but
the
the
core
of
it
all
of
the
work
you
do
on
a
day
to
day
operation
by
operation
basis,
that
is
all
pure
kubernetes
Huntington,
open
source,
100%
cloud
agnostic
and
it
integrates
with
SharePoint.
B
Alright.
So
what
does
this
mean
for
you
as
engineers?
It
means
you've
got
some
which
is
now
context
to
where
it
can
look
at
the
the
project
that
you're
working
on
and
make
assumptions
based
on
that
it
can
operate.
It
knows
what
you're
working
on
it
can
deal
with,
that
we've
built
it
so
that
it's
version
away.
So
if
you've
got
multiple
kubernetes
clusters
of
different
versions,
it
can
pull
down
the
right
version
of
cube
cuttle
to
work
with
any
given
cluster,
which
makes
life
a
bit
easier.
B
If
the
clusters
spanner
significant
range
of
versions
its
where
common
toolchain,
so
it
knows
about
git
and
docker,
and
it
can
use
that,
for
example,
to
move
through
version
history
to
synchronize
with
your
cluster
or
to
build
stuff
in
the
background,
so
that
you
don't
worry
about
doing
the
multiple
steps
and
it
is
tossed
where
it's
aware
of
some
of
the
the
common
tasks
at
a
higher
level
than
those
individual
git
or
cube.
Cuttle
c'mon.
B
So
that
come
up,
can
people
see
that
okay
I
can't
make
a
whole
lot
bigger
unfortunate
without
losing
too
much
screen
space,
but
hopefully
that
will
be
alright
with
people.
So
where
you
can
see
there
is
we've
got
a
cluster
view
on
the
the
left
hand,
side
listing
all
of
the
clusters
in
my
cube,
config
and
the
active
one
I
can
expand.
I
can
start
to
browse
through
some
of
the
stuff.
B
That's
on
it,
for
example,
I
can
see,
but
I've
got
an
engine
X
deployment
there
and
if
I
open
that
up,
I
can
see
the
the
pods
underneath
that
or
I
can
click
on
the
deployment
itself
and
I
can
bring
up
the
corresponding
yeah
mall.
So
this
gives
us
a
very
quick
way
of
looking
around.
What's
in
the
cluster
and
looking
at
some
of
the
the
resources
that
are
there.
Looking
at
some
of
the
details.
B
For
example,
if
I
want
to
I've
got
here
a
very
simple
application
that
reticulating
splines,
which
is
an
important
task,
and
at
the
moment
what
I've
got
for
that
is
a
JavaScript
file
and
a
docker
file.
I've
not
created
a
yeah
more
manifest.
I've
not
created
I've,
not
even
built.
Well,
I
stay
in
that.
I
have
already
built
it,
but
this
is
that's
just
a
save
time.
So,
for
example,
I
can
do
a
kubernetes
run
on
that
and
it
will
look
at
what
am
I
working
on?
B
B
This
is
very
network
dependent
demo,
so
and
I
will
then
create
a
deployment.
I
will
do
a
cute
cuddle
run
on
that,
using
that
image
that
has
been
pushed
and
if
I
now
go
back
to
the
to
the
viewer
and
do
a
refresh,
and
you
can
see
I've
now
got
that
demo.
Workspace
coming
up
and
I
can
start
to
work
with
that.
B
I
can
sort
of
dive
into
the
pods,
for
example,
and
I
can
very
easily
follow
the
the
logs
that
are
being
emitted
from
there
for
exam
for
diagnostic
purposes,
and
you
can
see
those
as
the
as
the
supplies
get
articulated
that
takes
over.
We've
also
got
an
experience
for
a
richer
experience
for
filtering
logs,
and
you
know
filtering
and
managing
your
logs,
though
that
currently
doesn't
work
on
the
live
stream.
It
only
works
on
the
if
you
do
a
show
logs,
but
it's
still,
it
can
be
useful.
B
If
that's
what
you
you
need-
and
we
can
also
again,
if
you
want
to
do
Diagnostics
on
it,
we
can
very
quickly
terminal
into
it,
and
it's
figured
out
it's
just
testing
what
shells
are
available
on
there
and
I
think
bash
should
be
on
there
yep.
So
it's
in
third
bash
and
for
example,
I
can
now
do
a
LS
and
I
can
see
what's
been
deployed
into
that
and
obviously
I
can
do
further.
But
the
work
in
there.
B
Another
thing
that
we
can
do,
which
again
is
sometimes
a
little
bit
of
a
fiddly
work
like
the
command
line,
is
port
forwarding,
where,
if
I
want
to
port
forward
into
there,
I
can
just
right
click.
There
don't
do
any
mucking
around
with
copying
of
names.
I
can
just
click
port
forward,
it'll
prompt
me
for
which
ports
I
want
to
forward,
and
it
will
then
just
do
it.
B
B
Let's
grab
a
different
one.
Let's
find,
let's
find
one
of
these
pods.
So
again,
I've
got
some
tools
that
can
help
you
navigate
around.
For
example,
this
is
a
pod
that
was
created
by
a
as
a
result
of
a
job
and
I
can
control
click
on
that
to
navigate
to
the
job
that
job
was
created
by
a
cron
job
and
I
can
again
navigate
to
the
parents.
You've
got
these
little
convenience
features
to
help.
You
find
your
way
around.
B
B
B
That
and
then
I
can
do
a
K
diff
and
that
will
compare
against
the
lively
Amal
in
the
cluster.
Then
you
can
see
well,
okay.
Some
of
this
is
nonsense,
because
it's
just
metadata
that's
been
added
as
a
result
of
the
deployment,
and
it's
not
interesting,
but
I
can
see
there.
There
is
an
actual
diff
I
can
see
that
what
I've
got
locally
is
out
of
sync
with
the
cluster
and
if
I
was,
for
example,
debugging
is
also
kubernetes.
B
B
B
We've
also
got
a
feature
where
you
can
take
again
a
live
object,
right-click
that
and
convert
that
to
a
helm,
template
and
you'll
see
I've
got
a
chart
in
there
and
you
can
see
it's
put
in
some,
so
it's
templated
some
of
the
boilerplate
stuff
and
from
this
point
on
you
can
go
edit
it
and
make
it
a
fully
functioning
helm
template
with
all
the
parameterization
that
you
need
ivenn.
If.
C
You
show
one
more
time
if
you
would
show
that
one
more
time
just
one.
Another
quick
point
is
that,
although
that's
very,
very
useful,
especially
yeah
because
helm
is
common
but
helm
is
also
not
used
by
other
people,
if
you
go
ahead
and
click
the
little
arrow
next
to
the
helm,
repose
you'll
find
that
that
vanishes
down
at
the
bottom
and
gets
out
of
your
way
as
well.
So
you
have
a
an
easy
way
to
select
your
visible
portion
of
your
working
environment,
yeah.
C
B
B
B
We've
got
this
very
specific,
cube,
cuttle
command
that
we
use
all
the
time.
Even
though
nobody
else
does,
we've
got
this
cloud.
We
want
to
build
provision
from
or
and
I
know.
This
doesn't
apply
to
any
of
you,
but
we've
got
this
super
special
set
of
conventions
and
table
layouts
and
secrets,
and
so
on,
which
defines
our
project
structure
and
how
we
do
everything
which
is
carefully
encoded
in
four
thousand
three
hundred
and
sixty-one
lines
of
bash.
C
B
B
Call
me
an
old
fuddy-duddy,
but
so
you
live
in
your
world.
You
live
in
a
world
specific
to
you.
You
customize
your
editor
in
a
way
that
specific
to
you
and
you
run
kubernetes
in
a
way
that
is
specific
to
you
to
your
team,
to
the
tools
that
you
use
to
the
industry
that
you
work
in
to
the
workflows
that
you
use
in
your
workplace
to
the
way
you
layout
projects
to
your
conventions.
B
B
You
can
write
extensions
that
encapsulate
things
that
your
team
does.
You
can
write
extensions
to
encapsulate
tools
that
you
use
or
that
you
write
and
provide
to
the
community.
You
can
write
extensions
that
are
useful
to
people
working
in
your
industry.
You
can
write
extensions
that
are
specific
to
your
workflows
or
your
project
layout
and
your
commissioning
capsulate
your
team's
knowledge
that
encapsulate
that
4360
one
line
bash
script,
because
that
way
we
can
scale
this
stuff
a
lot
better
than
everything
has
to
funnel
through
me
or
other
maintainer
of
the
project.
B
B
So
Red
Hat
have
implemented
they've
they've,
just
released
I
believe
a
the
OpenShift
Connect
for
Visual
Studio
code,
which
is
a
whole
bunch
of
utilities
for
working
with
open
shift
clusters
and
they've
integrated
that
with
a
kubernetes
extension.
So
the
OpenShift
clusters
will
be
visually
distinguished
and
will
show
things
using
OpenShift
terminology
like
projects
and
routes
rather
than
namespaces
and
ingresses
and
stuff
like
that.
B
So
that
will
give
you
kind
of
app
that
customized
view
of
those
openshift
clusters
there's
an
extension
for
linker
D,
the
linker
D
Service
mesh,
which
allows
you
to
you
can
very
easily
right-click
las
doce.
Is
this
cluster
ready
for
linker
D?
If
so,
I'll
going
to
right
click
I'm
going
to
install
it?
And
you
can
view
the
the
meshed
components.
B
And
there's
an
extension
I'm
told
by
Ralph,
is
of
supremely
high
quality.
I
wrote
this
one:
we've
we've
scope,
which
is
it's.
It's
really
neat.
So
with
this
one
you
can,
you
can
install
we've
scope
from
its
helm
chart
so
you've
got
a
cluster.
You
just
right-click
install
we've
scope
and
you
can
also
jump
you.
B
B
C
B
To
I
had,
if
he's
adding
value,
that's
what
they
do,
alright,
so
we're
going
to
kick
off
we're
going
to
try
to
write
a
a
vs
code
extension
in
the
in
the
last
ten
minutes
of
this
talk-
and
this
is
actually
I
started
doing
yesterday,
because
I
got
frustrated
with
some
that
wasn't
in
the
the
core
extension
I
didn't
have
a
way
to
right-click
a
deployment
and
go
I
want
to
expose
this
as
an
external
service.
I
just
I
just
want
to
get
my
nginx
thing
out
to
the
outside
world.
B
B
B
B
B
B
All
right,
so
that's
saying
that
this
extensions
going
to
depend
on
the
core
extension
because
it's
gonna
it's
going
to
sit
in
the
tree.
So
it's
actually,
if
you
want
to
have
this
you've,
got
to
have
the
core
extension
first.
Imagine
if
somebody
goes
great
I
want
to
expose
services,
then
it
will
drag.
Then
they
install
this
from
marketplace
and
it
will
drag
in
the
core
extension
if
they've
not
had
that
already.
B
B
Fair
enough,
all
right,
so
that's
how
did
there
we
go?
So
that's
added
the
the
NPM
package,
all
right
so
now
I'm
going
to
go
into
the
extension
or
no
I
can't
do
that.
Yet
so
I'm
going
to
need
to
so
the
the
template
generates
a
sample
command
which
says
hello
world
and
that's
not
quite
what
I
want
to
achieve.
I
mean
it's
nice,
it's
polite,
but
it's
not
actually
what
I
want
to
do
so.
I'll
just
create
a
I'll,
define
a.
C
One
thing
to
note
here
is
normally
in
example,
code
which
isn't
generated
here:
you'll
find
a
little
bracket
that
makes
it
obvious
you
know,
being
like
a
little
Open
bracket,
close
bracket
that
will
make
it
obvious
you're
supposed
to
replace
it.
In
this
case
it
actually
says
extension
dot
something
you're
supposed
to
replace
that
with
your
extension
name.
So
it's
an
easy
thing
to
sort
of
bang
your
head
against.
When
we'll
see.
If
we
can
get
that
boilerplate
change.
B
Now,
because
this
one
sits
on
something
in
the
tree,
I
need
to
tell
Visual
Studio
code
where
it
sits,
so
I
need
to
tell
it
basically
what's
kind
of
the
the
the
view
context
what'swhat's
the
identify
of
a
thing
that
it
should
be
displayed
against,
so
I'm
gonna
say
that
the
expose
command
is
added
to,
and
this
is
a
bit
of
an
incantation.
You
all
noticed.
C
B
All
right
and
for
the
time
being,
I'm
just
gonna,
say
I'm
going
I'm
still
gonna
say:
I
just
want
the
the
expose
command
to
display
the
hello
world
box,
so
I
can
make
sure
I've
not
messed.
Anything
up
like
I,
did
every
time.
I
practice
this
demo,
so
I
can
run
this
in
the
debugger
I.
Just
do
that
I,
press,
f5,
ok,
I!
Guess
you
you're
on
some
kind
of
crazy
other
box
yeah,
because
everyone
here
uses
Windows
right.
C
B
Alright,
so
you
may
need
your
debug
key
might
be
different
in
all
different
operating
systems,
but
on
Windows,
it's
f5,
but
it's
also
it's
against
a
standard
debug
command
for
Visual
Studio
code.
So
if
I
can
go
to
a
deployment,
let's
have
a
look
here.
There's
nginx
all
right
through
that
exposes
external
service.
I've
got
a
hello
world,
so
I've
managed
to
hook
up
a
command
to
the
tree.
Does.
C
That
make
sense
so
far
just
be
clear.
That
was
what
maybe
four
or
five
minutes
of
explication.
So,
if
he's
doing
this
on
the
on
his
own,
he
does
the
exploiting
explication
on
his
own
I've,
been
on
a
video
chat
with
him
when
it
does
this,
but
in
reality
it's
about
a
minute
two
minutes
to
get
your
stuff
up
and
running.
B
All
right
now,
in
reality,
I
actually
need
to
know
which
thing
which
service
I'm
going
to
expose
so
Visual
Studio
code.
When
you
do
a
right-click,
a
context,
menu
thing
in
a
tree,
vs
code
will
give
you
an
object.
That
represents
the
thing
that
was
right,
clicked
to
launch
the
command.
Now.
I,
don't
know
much
about
that
thing,
because
I've
I'm
on
the
outside,
looking
in
so
I'm
just
going
to
have
to
figure
out
what
it
is.
B
It's
all
going
fantastically
alright,
so
I,
don't
know
what
BS
code
is
gonna,
throw
at
me,
but
I
do
know
that
I
can
ask
the
kubernetes
extension,
which
is
where
it
came
from.
I,
can
ask
the
community's
extension.
What
the
hell
is
this
thing?
What
is
this
crazy
thing?
The
vs
code
is
giving
me
so
now.
I
need
to
use
the
cavalettis
extension
API
import
star
as
Kate's
from.
B
B
Yet
I'm
going
to
do
some
really
fancy
error
handling
by
just
dumping
user
out
of
the
command
as
I
say
this
you
can.
You
can
build
better
user
experiences
around
this
and,
oh,
my
goodness,
you
should
so
I
now
want
to
ask
the
extension
to
resolve
that
command
target.
I
want
to
know
what
it
is.
So
that's
going
to
tell
me
if
it's
a
node
in
the
tree
and
by
node
it
means
a
node
in
the
visual
tree.
B
B
And
the
user
in
place
gets
better
and
better
the
closer
I
get
to
running
out
of
time.
There's
our
command.
That's!
Looking
good!
Now.
I
need
to
run
that
so
now,
I
can
again
ask
the
extension
for
bit
of
help
on
this
Const
KC
equals
Cates,
dot
extension
dot,
cube,
cuttle,
dot,
the
one
and
again,
if
not,
KC,
dot,
wait
it's
not
available
and
we'll
just
return
and
now
constant
results
equals
K,
CFA
dot,
invoke
command,
CMD.
B
C
C
So,
okay,
who
raised
their
hands
for
not
first
time
but
the
interesting.
So
first
of
all,
you
are
right
and
you
should
come
to
the
booth
afterwards,
so
we
can
walk
through
this
again
and
you
can
torture
him
directly.
That
would
be
such
great
pleasure
for
me
to
the
point
where
I
might
pay
you,
but
the
interesting
thing
is
also
that
it
shows
you
immediately
the
debugging
ability
for
even
catching
the
simple
errors
right
away
so
that
you
can
immediately
iterate
turn
around
and
do
it
again.
Oh.
B
B
C
Show
you
that
it's
open,
but
we'll
let
you
go
thanks
for
having
a
look,
we're
gonna
roll
down
to
the
Microsoft
booth.
If
you
want
to
come
down
there,
we're
gonna
go
through
all
of
the
extensions
Steve
with
red
hat,
we'll
have
the
open
ship
stuff
at
his
booth.
You
can
see
that
we've
will
show
the
weave,
linker,
D
and
we'll
code
up
new
fun
things.
So
thank
you
very
much.
Thank
you.