►
From YouTube: Istio Contributor On-boarding
Description
On-boarding guide for new contributors to get started with the Istio community done as part of the Platform One initiative to encourage open source participation.
A
A
So
when
we
started
putting
this
together
a
couple
of
weeks
ago,
I
reached
out
to
some
open
source
projects,
starting
with
istio
and
key
click,
a
few
and
istio.
They
were
like
by
far
the
most
receptive.
So
I
am
super
super
excited
to
have
a
couple
of
the
a
couple
of
the
the
working
group
leadership
from
istio,
so
I'm
going
to
switch
over
to
so
you
can
see
them
as
well
and
gentlemen.
The
the
the
the
floor
is
yours.
Welcome.
B
C
Hello:
everyone
thanks
jason
and
welcome
to
all
futuristic
contributors,
I'm
the
co-founder
and
chief
architect
of
aspen
mesh.
I've
been
long-time
contributor
to
sto,
I'm
currently
a
member
of
the
sto
technical
oversight
committee
and
recently
elected
to
student
committee.
So
we're
really
excited
to
have
everyone.
Whoever
is
going
to
watch
it
live
or
come
on
later,
and
I
think
brian
is
going
to
start
you
down
the
right
path
by
telling
you
how
you
can
contribute
easily
to
histo
yeah
brian
you're,
going
to
take
it
away.
Yep.
B
Thank
you,
jason
and
raj,
okay,
so
quick
table
of
contents,
we're
going
to
talk
about
deploying
istio,
high
level
architecture,
developing
locally
issues,
pull
request,
process,
potential,
focus
areas
and
then
links
the
goal
of
this
is
to
be
somewhat
interactive.
So
there's
plenty
of
room
for
questions
and
that
sort
of
thing:
okay,
so
deploying
istio.
B
A
B
A
B
B
C
Do
before
you
jump
to
that
step,
brian
since
bran
is
an
expert
and
probably
does
this
10
times
a
day.
We
just
have
to
make
sure
that
you're,
actually,
you
actually
have
access
to
a
running
kubernetes
cluster
and
that
running
kubernetes
cluster
needs
to
be
in
the
supported
versions
that
istio
has
for
that
particular
release.
So
do
you
want
to
show
that
where
we
store
that
information.
C
C
A
C
B
C
A
You
know
that
the
the
the
config
for
it
and
he
he
freaked
out
because
we
showed
a
secret
on
a
live
stream
and
he
just
killed
the
cluster
right
there
in
the
middle
of
demo.
So
and
all
of
a
sudden,
the
the
cluster's
just
gone
and
he's
like
he's.
Like
I'm
sorry,
I
panicked
a
little
bit.
I
I
deleted
the
cluster,
I'm
like
no
biggie,
we'll
just
put
up
another
one.
B
B
C
A
Absolutely
so
we
like
so
we
we
had
this
idea
for
the
hackathon
pretty
recently
and
it
just
kind
of
threw
out
there
and
there's
a
lot
of
excitement
within
the
organization
and
with
our
vendors
and
customers
around
getting
involved
in
open
source.
So
I'm
just
going
to
keep
pushing
people
to
you
know
towards
these
different
projects
that
we're
using
to
make
them
all
better.
A
So
yeah
we'll
see
how
many
you
know
from
the
original
list
of
you
know
about
100
signed
up
to
the
20
that
registered
to
the
you
know
those
that
are
watching
and
watching
the
videos
who
get
involved.
You
know
I
I
fully
expect
to
stick
out
of
attrition,
but
we're
just
gonna
keep
pushing
and
then
keep
you
know,
keep
giving
shout
outs
these
different
projects,
and
you
know
if
we
get
one
contributor
a
week
great,
we
get
one
a
month
great.
C
A
So
because,
because
we
are
and
anybody
who's
halfway
interested,
this
could
look
at
p1.dsop.io
about
the
different
services
we
provide.
So
we've
built
out
as
a
team,
a
set
of
hardened
dod
approved
containers
that
are
that
are
secure,
good
base
containers
and
then,
from
there
we
built
another
project
called
big
bang
and
big
bang
is
all
the
infrastructures
code
and
configurations
code
that
is
used
to
stand
up.
Essentially
the
85
solution
for
get
ops,
so
we're
using
tools
like
argo,
cd
and
we're
you
know
and
we're
using.
C
A
And
you
yeah
we're
using
all
you
know
your
your
node.js
for
developers.net
core
for
developers,
so
you
know
the
developers
out
of
the
box
get
pipelines
so
that
they
only
have
to
worry
about
code.
Now,
that's
not
guaranteed,
because
there's
still
things
we
haven't
touched
in
that
85
percent.
But
the
end
goal
is
that
we
can
automate
all
the
things
and
development
teams
that
get
on
the
platform.
One
can
just
worry
about
their
code
and
we're
getting
there
one
step
at
a
time.
A
So
I'm
I'm
involved
with
a
team
that
works
with
oncoming
projects
to
figure
out
where
the
gaps
are.
So
we
build
out
automation,
pipelines
things
that
nature,
but
istio
is
a
major
part
of
that
in
so
much
as
you
know,
for
doing
mtls
and
things
of
that
nature
and
handling
all
of
our
ingress.
So
we're
a
huge
fan
of
the
project
which,
when
you
all
responded
and
you
know
responded,
I
was
really
excited
to
have
you
on,
because
this
is
one
of
the
cooler
projects.
That
is
part
of
this.
A
C
B
B
C
B
B
So
seo
is
made
up
of
a
couple
of
different
components.
It
used
to
be
made
up
of
far
more,
but
in
one
six
I
believe
it
was
simplified
to
really
b2
components.
You
have
the
istio
proxy
component,
which
is
a
wrapper
around
envoy,
plus
some
istio
customizations,
and
then
you
have
the
sdod
compliant
inside
of
sdod
is
pilot,
citadel
and
galley.
B
B
So
you
have
a
directory
for
pilot,
a
directory
for
galley
a
directory
for
security,
which
is
actually
what
citadel
is
called
initially,
but
that's
where
the
citadel
code
is
and
all
of
those
links
are
right
here.
All
of
the
components
except
for
envoy
are
written
in,
go
envoy's,
written
in
c
plus
plus
there's
new
functionality.
B
B
Okay,
so
getting
started
in
istio.
First,
you
need
to
sign
the
cla.
You
can
do
that
really
at
any
point,
but
the
cli
needs
to
it's
the
license
agreement
that
you
have
to
sign
in
order
to
make
a
contribution
to
istio
so
probably
better
to
confirm
that
you're
willing
to
accept
that
before
you
try
to
make
changes
and
figure
out
that
you're
not
willing
to
yeah.
C
Yeah
just
one
thing
here:
it's
really
important
to
make
sure
you
have
this
iron
out
coming
from
you
know
from
my
past
experiences.
Sometimes
organizations
have
stricter
policies
around
what
projects
you
can
contribute
to
and
which
people
in
the
organization
your
organization
can
contribute
to
them.
Good
thing
about
the
st
automation
is:
if
you
don't
have
your
cls
signed
it
won't.
B
Yep,
so
the
next
part
is
forking.
The
repository
we
have
our
github's
documentation
for
forking
repositories
is
linked
here.
I'm
assuming
a
lot
of
people
know
how
to
fork
repositories
already,
but
it's
there
and
then
clone
your
forked
repository
using
git
clone
so
that
you
have
the
code
local,
create
a
branch
for
your
changes
based
off
of
the
master
branch
in
istio.
B
We
also
require
make
lint,
and
occasionally
you
see
a
message
about
make
gen,
which
creates
automatically
generated
configuration
like
you
might
have
changes
to
the
installation
profile
which
requires
make
gen
in
order
to
update
those
files
to
be
able
to
run
there
are
any
user
facing
changes.
I'm
at
a
release
note
so
there's
a
file
that
gets
added
in
each
pull
request.
B
So
we
have
a
system
here.
These
are
the
document
docs
for
it
right
here,
but
we
have
a
system
here
which
will
take
a
yaml
file
contained
in
the
notes
directory
and
it
will
automatically
generate
release
notes
when
it
comes
time
to
do
a
release.
So
it'll
say:
hey
here's,
the
previous
release,
here's
the
current
release.
Let's
find
all
the
changes
in
between
and
let's
generate
a
release.
Note
so
you'd
say
here's
any
documentation
that
needs
to
be
linked
in
this
release.
B
Note
here's
what
the
changes
if
it
affects
upgrades,
then
you
can
add
a
comment
here
and
if
it
affects
security,
then
you
can
add
a
comment
there
as
well
and
then
yeah
there's
more
documentation
here,
but
that's
a
high
level
of
it
once
the
changes
are
ready,
open
a
pull
request.
Depending
on
the
area
of
the
code
change,
the
appropriate
work
group
will
be
selected
as
a
reviewer
from
the
code
owners
file,
so
github
lets
you
create
these
files
called
code
earners
and
the
level
it
goes
in
a
hierarchy.
B
B
That's
an
example:
we've
got
tests
that
run
something
to
make
sure
make
gen
is
run
basically
make
sure
that
everything
passes
into
your
code
looks
good
before
it's
merged
once
this
is
or
if
you're,
not
a
member
of
the
istio
community.
Yet
then
an
istio
member
will
have
to
give
an
okay
to
test,
which
is
just
a
git
label,
after
which
all
of
your
tests
will
run
and
github
will
give
you
a
message
saying:
hey.
This
hasn't
been
done
yet
add
that
label
real,
quick.
C
Very
quickly,
if
you
don't
mind
me
saying
something,
so
this
is
something
that
some
new
developers
or
new
contributors
often
get
hung
up
on,
so
they'll
be
waiting
for
the
test
to
run
and
they'll
come
back
and
they'll
feel
like
nobody's
paying
attention.
It's
nothing
like
that.
We
from
the
community
who
are
maintainers
and
leads
in
various
groups.
We
get
on
an
average
hundred
plus
emails
from
github
a
day,
so
it
sometimes
gets
lost
in
the
noise
yeah.
C
C
B
B
Okay,
istio
welcomes
contributions
in
really
anything
that
would
help
the
project,
documentation,
writing
features
and
tests.
Answering
questions
on
discuss
status,
uri,
io
and
slack
discusses
issues
forum
to
come
and
ask
questions,
release
testing,
so
we've
got
the
1.8
release
coming
up
soon.
We've
got
a
whole
spreadsheet
of
tests
that
were
that
need
to
be
done
before
the
release
goes
out
so
help
with
that
would
be
greatly
appreciated.
Finding
and
filing
bugs
resolving
issues.
There's
a
whole
number
of
different
things.
B
C
One
minor
note
here,
brian,
so
if
you
are
starting
to
work
on
any
issue
which
is
help
wanted
first
thing
you
should
do
is
add
a
comment
and
make
sure
that
the
story
or
the
issue
writer
still
is
seeing
that
issue
or
they
want
it
fixed.
Because
often
you
know
it's
open
source
project
people
create
issues
and
the
labels
might
not
be
correctly
attributed
or
they
go.
Stale
second
reach
out
to
any
of
the
working
group
leads
so
and
for
most
of
the
issues.
C
If
they
have
been
triaged,
you
will
see
which
working
group
is
assigned
to
it,
so
you
can
just
do
at,
and
the
working
group
alias
and
you
will
get
attention
you
can
ask
them.
Is
this
issue
still
valid
and
then?
Secondly,
you
can
also
ask
them
what's
the
best
way
to
solve
it?
So
some
of
those
steps,
sorry,
brian,
just
one
more
thing-
I
would
always
recommend
doing
that
for
any
open
source
project,
not
just
sto
make
sure
you
know
that
issue
is
valid
and
make
sure
you
know
the
right
ways
to
fix
it.
B
Just
expanding
on
this
real
quick,
I
clicked
on
the
help
wanted
link
that
I
had,
and
this
is
an
example
of
one
of
the
issues
you
can
see
on
the
side.
It
has
a
label
environments
area,
slash
environments
on
it.
So
if
you
go
to
the
environment,
slack
channel
or
ask
an
environment
work
group
lead,
then
somebody
will
help
you
out
with
that
we're
all
friendly.
We
don't
bite.
B
Okay,
so
another
idea
is
documentation
tests,
so
one
project
that
we've
been
working
on
in
seo
for
the
last
couple
of
releases
is
we
have
on
our
website.
We
have
a
whole
bunch
of
documentation
and
we
have
a
framework
that
will
actually
go
through
and
execute
those
steps
and
make
sure
the
output
looks
reasonable
and
try
to
automate
testing
so
that
somebody
doesn't
have
to
come
in
and
manually
test
that
to
make
sure
it
works.
B
B
Which
provides
documentation
on
yeah
how
to
write
an
automated
test
for
our
docs.
It's
designed
to
be
fairly
high
level,
so
you
don't
necessarily
have
to
know,
go
or
anything
else.
It
produces
a
bash
script
and
tries
to
make
it
easy
for
somebody
who's
familiar
with
the
documentation
to
write
a
test
versus
somebody
who's
an
advanced
programmer.
C
Yeah-
and
this
is
a
really
cool
automation
step
that
we
have
in
the
community,
I
would
be
both
excited
and
grateful
if
folks,
who
are
contributing
for
the
first
time,
take
this
up
and
specifically
for
dog
testing
the
test
and
release
working
group
and
the
documentation
working
group.
Both
of
these
working
groups
can
help
you
get
started
if
you've
got
if
you
need
some
help
or
if
you're
stuck
so
reach
out
to
them.
A
A
Yeah,
it's
somebody
who,
who
is
is
very,
very
documentation
interested
because
you
have
docs
a
product
in
my
world.
You
know
anything
that
anything
that
can
you
know,
coincide
the
docs
with
the
project
in
such
a
way
that
we
know
that
the
docs
are
correct
and
we
know
that
the
scripts
that
we
show
off
in
the
docs
are
still
correct.
This
is
a
huge
win
in
my
in
my
book.
B
If
you
go
to
the
istio
io
repo,
our
documentation
is
in
content
en
or
en
for
the
english
language.
We
also
have
support
for
chinese
and
brazilian
portuguese
as
well,
which
translators
are
also
appreciated,
so
under
docs
you
have
all
of
these
individual
documentation
examples.
So
if
I
go
to
tasks-
and
I
go
to
say-
observability
distributed
tracing
jaeger,
okay,
so
index.md,
that's
your
documentation.
B
B
A
Yeah,
my
my
I
was
mentioning
this
morning.
We
did
our
kind
of
intro
to
contributing
open
sources
as
you're
going
through
the
getting
started
docs
when
it's
broken,
because
these
things
happen
go
ahead
and
fix
it.
Like
that's
a
that's
a
big
part
of
getting
started,
the
project
is
learning.
How
do
other
people
ingest
the
project
for
the
first
time
and
if
it
doesn't
make
sense
to
you,
it's
not
going
to
make
sense
to
the
person
behind
you.
B
C
Yeah,
you
know
I
mean
I'm
the
co-founder
of
aspen
mesh,
so
we
have
an
onboarded,
so
many
people,
one
of
the
things
I
do
for
onboarding
is
you
have
to
pass
the
bit
on.
So
the
newest
hire
make
sure
you
are
on
boarding
the
next
person
and
your
documents
that
you
have
are
up
to
date.
So
it's
pretty
similar
similar
to
that
new
contributors,
make
it
better
for
the
next
ones.
Yeah.
B
B
A
A
A
I
I
love
to
I
love
to
join,
so
I
do
a
lot
of
live
coding
as
part
of
part
of
streaming
and
make
a
lot
of
mistakes,
and
I
think
my
regular
line
is
I'm
just
not
a
smart
man,
and
it's
just
it's
just
too.
It
just
proves
out
to
be
true
over
and
over
and
over
again
because
most
of
the
mistakes
I
made
I've
made
a
million
times.
It's
just.
I've
made
them
new
again
today.
C
Yeah,
you
know
so
two
things
brian,
you
need
to
stop
sharing,
so
I
can
share
and
I
totally
echo
what
jason
just
said.
In
fact,
I
stopped
doing
live
demos
all
together,
even
for
all
the
conference
presentations.
I
do.
I
actually
take
snippets
of
configuration
and
outputs
if
I
want,
because
primarily
I
don't
think
I'm
smart
enough
in
front
of
a
big
count
to
do
things
correctly
and
secondly,
it
never
freaking
works.
Oh.
C
C
Is
that
better
yep?
Oh,
I
have
a
big
monitor
so
sometimes,
when
I
share
my
screen,
things
get
a
little
wonky
all
right.
So
basically,
I'm
gonna
do
the
same
thing.
That
brian
was
trying
which
is
follow
the
institute
documentation
here
to
easily
install
istu
in
your
cluster
and
basic,
and
if
we
have
time
I
will
try
to
install
some
sample
application
and
get
traffic
going
all
assuming
that
the
demo
gods
are
with
me.
So
first
thing
I'll
ensure
I
have
the
right
version
of
kubernetes.
C
C
If
I
go
to
the
platform
support,
this
is
in
the
supported
window.
So
that's
good.
So
the
next
step
here
is
follow
this
guide
like
it
says
it
says,
download,
install
sto,
deploy
the
sample
application
open
the
application.
So
this
page
is
for
someone
who
just
want
to
play
with
this
to
you
quickly:
it's
not
for
getting
a
production,
ready
version
of
sto
that
configuration
and
that
documentation
live
somewhere,
but
today
we're
just
going
to
do
a
demo.
So
I'm
going
to
follow
this,
so
I've
copied
this
once
this
is
running.
C
C
I
have
the
istio
one,
seven
three,
as
you
can
see,
and
I
also
have
a
latest
version
of
a
studio-
that's
why
you
saw
that
ugly.
Looking
this
thing,
so
all
our
builds
nightly
get
converted
into
they
get
converted
into
artifacts
that
developers
like
us
can
use.
So
I
was
working
on
a
feature
yesterday,
which
I
wanted
to
see
how
it
works,
and
that's
why
I
have
this
thing:
anyways.
We
are
not
going
to
use
that
for
you
just.
C
C
I
will
follow
the
export
command
to
set
up
my
path.
So
now,
if
I
do
a
steer,
ctl
version,
it
says
that
my
client
version
here
is
173
and
I
don't
have
any
student
in
parts
in
h2
system.
Obviously,
since
I
have
an
install
list
here,
all
right
moving
forward,
this
is
the
simplest
command
and
the
simplest
way
to
get
started
with
this
sdo.
C
You
use
istio,
ctl
install
and
you
set
up
a
profile
in
this
case
we're
going
to
use
the
demo
profile
and
there
you
go
it's
up
and
running
so
first
thing
it
will
do
over
here.
Is
it
detects
whether
you
have
a
third-party
chart,
authentication
enabled
in
your
kubernetes
cluster
or
not?
In
my
case?
I
don't
have
it
enabled
so
it
falls
back
to
first
party
chart
and
then
automatically
creates
the
right
configuration.
C
This
often
bites
people,
if
you
are
not
using
your
ctl
based
install
but
using
your
own
installation
methods.
You
have
to
make
sure
that
the
configuration
maps
to
this
requirement
right
so
it
has
installed
istio
core
stod,
egress
gateways
and
ingress
gateways.
And
again
this
is
just
a
demo
installation,
a
demo
profile.
So
if
you
don't
need
an
egress
gateway
in
your
environment,
you
don't
have
to
install
it
or,
if
you're,
using
something
else
for
ingress.
For
example,
if
you're
using
gen,
x
or
big-ip
donate
it
don't
install
it
all
right.
C
So
it
has
completed
the
installation
like
it
says,
but
obviously
we
don't
trust
your
ctl.
So
what
we're
gonna
do
is
look
at
what
it
installed.
So
if
I
go
to
steer
system
and
do
get
pods
there,
you
go
so
just
around
us
around
a
minute
ago.
It
installed
these
three
pods
and
they're
all
up
and
running.
So
so
far,
brian
I'm
already
ahead
of
where
you
were
so
that's
a
good
sign.
C
C
Most
of
the
early
customer
support
issues
that
I
used
to
handle
were
I
installed
istio.
I
installed
my
application
in
a
name
space,
but
then
the
site
sidecars
were
never
injected
and
the
reason
is
you
haven't
labeled
your
namespace,
so
you're
not
going
to
make
that
mistake.
Today
we
label
the
namespace.
C
There
you
go
so
you
see
my
other
kubernetes
system.
Namespaces,
they
don't
have
this
label.
Is
your
system
obviously
has
that
disabled,
because
that
will
be
like
an
inception.
Kind
of
a
thing
is
to
use
injecting
into
its
own
control
inputs,
and
that
won't
be
a
happy
day
and
in
the
default
name
space
you
have
injection,
enabled
very
cool.
So
now
I'm
gonna
go
and
install
a
sample
application.
The
sample
application
that
we
use
in
sdo
is
book
info.
C
It
has
a
bunch
of
applications
that
talk
to
each
other
and
kind
of
mimic,
a
fake
bookstore,
an
online
bookstore
which
has
reviews
and
bunch
of
other
ratings
in
it.
So
let's
do
that,
so
it
went
ahead
and
created
all
these
service
accounts,
deployment
and
services
in
the
default
name
space.
So
if
I
now
look
at
what's
happening
in
my
default,
namespace.
C
There
you
go,
I
see
that
the
pod
is
initializing
for
these
applications
and
they
were
just
created.
So
if
I
hit
this
again,
hopefully
things
will
start
converting
to
running.
There
are
two
key
things
here
to
make.
Sure
first
is
before
you
run
your
next
steps
or
the
demo
make
sure
all
these
parts
actually
get
to
the
running
state.
C
So
I'm
gonna
wait
until
all
of
them
are
that's
good,
and
the
second
thing
is:
if
you
see
this
says
two
out
of
two,
even
though
these
pods
actually
only
have
one
container
in
the
manifest
the
sidecar
injector
automatically
added
the
sidecar
proxies
in
it,
and
that's
why
they
have
two
containers.
So
if
I
go
into
it
and
get
one
of
these
pods
and
do
a
dash
o
yamu.
C
C
The
deployment
only
mentions
one
container:
that's
why
we
call
it
the
automatic
side
con
injection,
basically
it's
watching
for
all
parts
to
be
created,
and
then
it
intercepts
that
request
and
injects
the
second
container,
which
is
the
side
car
proxy.
So
there
you
go,
we
have
our
parts
running.
We
have.
We
have
those
parts
with
the
sidecar
injected.
Our
control
plane
is
actually
working.
So
the
next
step
here
is
to
generate
some
traffic.
C
That
we
often
ship
with
aspen
mesh
and
aspen
mesh
container
and
aspen
mesh
customers,
so
I'm
gonna
just
run
a
book
info
traffic
generator
and
apply
it.
So
now
I
should
see
that
there's
a
new
part
coming
up,
which
is
the
traffic
generator
pod.
This
traffic
generator
is
configured
to
hit
the
product
page
service
and
generate
some
traffic.
There
you
go
so
it's
up
and
running.
C
C
C
Traffic
generator
there
you
go
so
it's
hitting
the
product
page
and
you're,
seeing
a
web
page
being
rendered
in
html
and
javascript.
Everything
is
on
the
screen
instead
of
the
browser,
so
you
don't
see
a
pretty
gui,
but
this
basically
validates
that
your
traffic
is
working.
Your
istio
control
pin
is
working
and
your
data
plane
has
the
side
cross
proxy
injected
and
the
traffic
is
working
as
you
would
expect.
C
A
C
All
right,
what
do
you
think
brian?
We
should
just
deploy
the
gateways
yeah.
That
sounds
good
to
me
all
right.
So
the
next
step
here
is
basically
deploying
some
story:
sources,
sdo
gateway
and
virtual
service,
so
that
the
traffic
from
outside,
which
is
from
my
browser,
can
hit
the
sq
ingress
gateway
and
then
get
routed
to
the
booking
for
applications.
C
Let
me
do
that,
so
those
are
created,
I'm
going
to
do
an
sdo
ctl
analyze
here,
institute
and
analyze
is
a
set
of
analysis
tools
which
can
run
against
your
configuration
and
make
sure
that
your
configuration
is
as
expected,
often
misconfigurations
in
an
sdo
cluster
lead
to
all
sorts
of
problems.
So
this
is
one
of
the
tools
which
I
always
recommend
people
to
run
in
the
ci
or,
if
you're
debugging,
anything
with
stu.
That's
the
first
thing
you
do
run
and
analyze
and
see.
What's
going
on
all
right.
C
C
C
And
then
hit
product
page
boom,
we
have
access
to
our
booking
for
application.
This
book
info
application
has
three
rating
service
which
the
list
your
site
cards
will
automatically
load
balance.
So,
if
I
do
a
refresh,
you
see
different
outputs.
Basically,
one
of
the
rating
servers
does
not
give
any
ratings.
The
other
one
gives
five
ratings
another
one
it
gives
four
or
I
think
the
color
is
different,
something
like
that.
Like
brian,
I
don't
remember
what
they
do.
Yeah
it's.
C
Yeah,
you
can
see
that
I
don't
do
these
demos
very
very
often,
so
I'm
not
that
familiar
with
the
sample
application,
but
this
is
it.
We
went
through
this
documentation
and,
as
you
can
see
in
few
easy
steps
you
were
able
to
install
sdo.
You
were
able
to
verify
that
the
control
pin
is
running
you're,
able
to
inject
the
side,
cars
in
your
applications
and
you're
taking
benefit
of
sto
configuration
to
route
traffic.
B
D
B
A
A
C
A
A
You
know
finished
up
some
things
hanging
out
hanging
out
in
the
ether,
so
tomorrow
we're
either
gonna,
be
talking
to
more
open
source
projects,
or
maybe
we'll
actually
walk
through
together
and
actually
see
if
we
can
get
a
couple
of
these
going
from
a
kubernetes
perspective
from
a
cncf
perspective
and
actually
go
through
what
it's
like
to
be
a
contributor
on
a
project
for
the
first
time
to
get
things
running.
So
you
all
have
a
great
evening
and
we'll
see
you
tomorrow,
bye
now.