►
From YouTube: KBE Insider (E11): Idit Levine
Description
KBE Insider interviews Idit Levine, founder and CEO of Solo.io. Idit is also an evangelist and practitioner of DevOps. In this KBE Insider episode we’ll focus on how Idit got started as a contributor to open source projects such as Kubernetes, Istio, and Envoy. We’ll also ask her to share her path to becoming a founder and any advice for future founders and contributors of open source projects.
KBE Insider is hosted by Langdon White, Clinical Assistant Professor of Computing and Data Sciences at Boston University, and guest co-host Josh Wood, Developer Advocate at Red Hat. KBE Insider lets you reach people deeply involved with the Kubernetes community, hear what they have to say, and engage with Kubernetes experts from across the globe.
A
Who
is
the
excuse
me
the
ceo
and
founder
of
solo?
And
if
you
would
like
to
well,
let
me
introduce
josh
wood,
real,
quick
and
say
hey.
You
know,
thanks
for
coming,
as
I
often
say,
with
red
hat
people,
titles
and
groups,
and
all
that
changed
so
often
that
I'd
like
you
to
introduce
yourself
so
josh.
If
you
want
to
introduce
yourself
and
then
we'll
talk
to
id.
B
C
C
Yeah
sure
so
I
mean
I'm,
as
you
mentioned,
I'm
the
founder
and
ceo
of
solo
and
sola
is
a
company
that
honestly
making
it's
not
that
different
than
red
hat
we're,
making
open
source
project
simpler
to
consume
right
and
then
actually
that's
what
openshift
and
red
hat
is
doing
as
well.
But
we
are
focusing
more
about
networking,
so
the
project
that
we
are
involving
is
project
like
sto,
which
is
a
service
mesh
or
project
like
celium,
which
is
a
kind
of
like
a
cni.
C
So
that's
the
work
that
we
are
more
doing
and
and
again
the
idea
is
just
to
make
it
way
more
accessible
for
people
make
sure
that
they
will
be
able
to
consume
it
work
more
about
the
user
experience
and
how
to
basically
be
able
to
really
fit
it
to
each
organization,
organization,
structure
and
people
and
honestly
just
make
it
easier
to
consume.
So
that's
not
that
different
than
what
you
guys
think.
I
guess.
A
Yeah
yeah
totally
I
mean,
and-
and
that's
in
my
opinion
right
I
mean
that's
really
what
a
vendor
brings
to
the
table.
A
lot
of
the
time
right
is
that
you
know,
is
how
can
I
make
it
a
little
bit
easier
to
consume,
for
you
know
the
typical
enterprise,
you
know,
or
you
know
sometimes
you
know
the
big
thing
that
red
has
always
offered
is
you
know
indemnification
which
can
be
harrowing
for
a
lot
of
corporations,
so
it's
really
kind
of
important.
C
B
C
Exactly
on
the
you
know,
docker
just
came,
and
I
think
that
you
know
I
was
in
the
first
dockercoin.
So
I
think
that's
where
kind
of
like
it's
make
me
excited
about
open
source,
so
I
was
in
dockercon.
I
was
doing
a
lot
of
work
with
docker,
no
solomon
hike
very,
very
well
and
then,
basically,
when
they
war,
let's
say
it
started
between
kubernetes
and
cloud
foundry
and
mesos.
I
was
actually
really
active
in
all
those
community
and
then
yes,
I
mean
that's
basically
what
we
did.
C
D
C
C
A
A
Really
kind
of
miss,
I
say
that
all
the
time
about
subversion
is
like,
I
really
wish
it
did
like
kind
of
the
sub
module
thing
and
git
is
like
well,
you
know,
but
in
subversion
it
did
a
much
nicer
job
and
I'm
just
you
know
it's
like
I
missed
that
I
doesn't
mean
I
don't
want
to.
I
want
to
go
back
to
subversion
by
any
stretch
imagination,
but
I
do
miss
that,
like
one
piece.
C
Yeah,
I
think
that
what
cloud
foundry
did
really
really
well
is
the
user
experience
I
mean.
I
think
this
is
still
something
that
is
missing
a
little
bit
from
kubernetes,
not
sure
why,
honestly,
I
know
that
that
k
negatively
was
a
intent
to
create
something
like
that,
but
it's
still
it's
it's
not
it's
not
yeah.
It's
not
it's
not
as
great
as
cloud
foundry
was,
but
honestly,
that's
the
only
thing
that
I
think
I
will
take
from
there.
C
D
C
Think
that
also,
in
my
opinion,
generally
someone
working
in
the
open
source
quite
a
lot.
I
think
that
one
of
the
problem
that
was
there
is
that
the
way
the
community
was
operated
was
a
little
bit
different
than
kubernetes
or
any
other
open
source
that
I
know
in
order
to
commit
something
you
have
to
create
to
do
these
things
called
dojo
right,
which
is
honestly
it's
it's
a
huge
barrier
in
order
to
be
part
of
a
community,
and
you
know
they're
not
just
going
to
get
your
pull
request
unless
you
were
in
this
dojo.
C
C
Is
the
fact
that
the
exceptions
expected
like
people
who
ever
want
to
help
like
please
do
right?
We
want
you
to
join
right
and
I
think
that
in
club
founders
was
a
little
bit
different.
It
was
more
like
we
will
choose
release
these
people
and
we
will
they
will
have
to
do
it
our
way,
which
I
think
honestly
created
a
little
bit
of
issue.
C
B
In
user
experience,
that
is
the
end
result
of
their
outputs
right,
like
in
kubernetes
there's
a
whole
lot
of
openness
and
a
whole
lot
of
folks
can
be
chefs
in
a
very
large
kitchen
and,
and
that
has
a
lot
of
great
outcomes
but
like
if
you
can't
tell
I'm
sort
of
hinting
at
an
opinion
I
have
here.
But
I
wonder
if
you
agree
it's
like
in
a
way
that
that
more
close
nature
of
the
cloud
foundry
ecosystem,
maybe
led
the
end
result
for
the
user
to
be
a
little
more
focused
a
little
easier
to
digest.
C
Of
course,
because
I
can
tell
you
that
I
wanted
to
contribute-
and
it
was
very
hard
for
me
because
I
never
passed
the
daughter
right
and
I
I
never
went
just
because
that
was
wasn't
my
job
right
now.
I
wasn't
sending
by
emc
to
do
the
dojo,
so
that's
very,
very
limited
because
you
know
I
can
code
and
it's
a
shame
that
they
I
couldn't
influence.
C
So
I
think
that
that's
a
huge
barrier.
I
think
that
also,
if
you
think
about
it,
let's
be
honest
right
I
mean
a
lot
of
the
contribution
to
going
to
an
open
source.
Usually
is
people
that
that's
their
focus
at
work?
Right
I
mean
red
hat
is
paying
the
money,
but
those
guys
are
dedicated
to
kubernetes
and
they're
doing
whatever,
whatever
they
need
there.
I
think
that
that's
extremely
different,
you
know
so
so.
C
First
of
all,
that's
where
most
of
the
configuration
but,
as
I
said
to
you
like
I
mean
as
company
like
solo,
we
be
also
doing
this
right,
we're
basically
contributing
wherever
we
can.
So
the
question
is,
you
know
if
you're
thinking
about
the
experience
of
cloud
foundry,
if
I
was
solo
right
now,
would
I
actually
send
you
know
my
people
right
now
to
a
week
or
two
weeks?
I
think
it
was
way
more
than
a
week
right.
C
I
wish
it
was
a
week
or
something
like
a
month
or
something
kind
of
like
training
somewhere
in
a
location
of
a
dozen
should
have
to
be
in
san
francisco,
safe
to
be
with
everybody
to
have
to
be
performing.
I'm
just
not
sure
that
this
is
something
that
I
would
as
a
startup
do
honestly.
So
it's
really
limited
to
you,
who
is
this
company
that
can
focus
on
this,
and
that
will
be
the
big
organization
that
honestly
can
do
that.
So
you
know
yeah
you're
losing
a
lot
of
good
at
the
end.
A
So
I
know
solo
is
kind
of
more
generally
focused
on
kind
of
networking
at
large
right.
But,
as
I
recall
right,
you
started
kind
of
in
the
service
mesh
space
and
I'm
kind
of
curious.
What
is
it
about?
Like
kind
of
the
service
mesh
idea
is
like
was
attractive
to
you,
that
kind
of
said,
hey.
I
should
go
and
make
this
better.
C
Yeah,
so
I
mean
I
mean
honestly
to
me
when
I
started
the
company
and
I
look
at
the
market
right
because
it's
very
depending
on
the
time
right,
if
I
would
probably
do
the
company
I
don't
know
five
years
ago,
probably
I
will
do
also
orchestration
or
something
like
that.
So
when
I
got
them
and
started
the
company,
basically
by
trying
to
figure
out
what
would
be
the
next
problem,
that
people
will
have
right,
I
mean
okay,
so
we
already
know
it's
the
people
using
docker
right
or
container
in
general.
C
We
already
know
that
now
everything
moving
from
analytic
to
micro
services.
In
that
point,
I
even
bet
it
wasn't
that
clear
in
the
market,
yet
that
kubernetes
will
be
these
things
that
will
win
it
all.
So
now
the
question
is:
what
will
be
the
people
problem
and
to
me
it
was
very
simple:
if
you're
taking
something
that
is,
you
know,
but
one
binary,
one
big
binary
and
cut
it
to
pieces.
Somehow
you
need
to
reassemble
them
right,
I
mean
eventually
it
should
look
like
one
application.
C
A
C
That
no
one
can
come
in
the
middle,
because
now
everything
is
over
the
wire
and
the
last
one
is
observability
right,
honestly,
there's
so
many
replication
and
when
the
request
is
coming,
it's
seriously,
like
a
murder
mystery
to
figure
out
what's
going
wrong.
So
when
I
looked
at
all
of
this,
I
said:
okay,
that's
obviously
the
problem
that
people
will
need
to
solve.
When
I
looked
around
there
was
the
concept
already
of
service
mesh.
It
came
from
the
buoyant
guy
linkadi,
basically,
but
it
was,
it
wasn't
well
implemented.
I
will
be
honest.
C
It
was
the
first
buoyant.
You
know
the
best,
the
first
implementation
of
linker
d,
honestly,
like
ins
in
service
mesh.
There
is
this
concept
of
site
car
which
hopefully
will
go
away
soon,
but
it
is-
and
I
think
that
in
in
buoyant
or
link
first
linker,
they
we
call
it
side
bus
because
it
was
so
you
just
yeah.
C
A
C
But
but
actually
the
implementation
wasn't
great,
so
that
was
the
first
option
and
the
second
option
sto
just
was
announced
basically,
and
when
I
looked
at
this
again,
there
was
a
lot
of
stuff
that
I
liked
it
made
a
lot
more
sense,
but
there
was
also
some
decision
that
I
was
kind
of
like
questioning,
for
instance,
this
mixer
thing
that
every
time
that
the
request
is
coming,
you
need
to
do
kind
of
like
a
round
three
for
a
grpc
server.
That
doesn't
make
any
sense
to
me
on
the
request
part.
C
I
I
think
that
you
know
crest
latency
is
extremely
important,
so
I
kind
of
accepted
and
said
well,
that's
interesting!
That's
something
that
probably
is
going
to
the
better
solution,
but
it's
yeah.
It
will
take
a
long
time
until
we
get
there.
So
this
is
why
we
basically
started
first
on
the
gateway,
then
moved
to
the
mesh,
then
extending
to
cnn.
You
know
basically.
B
C
A
Yeah,
I
mean,
I
think
you
raise
a
really
good
point
right,
which
is
that
you
know
what
a
lot
of
people
don't
realize
is
that
as
soon
as
you
start
getting
into
any
kind
of
service
oriented
architecture,
whether
we
call
it,
you
know
soa
or
we
call
it
microservices
or
you
know,
even
you
know,
there's
lots
of
other
ones.
The
core
about
right.
The
the
challenge
starts
to
become
is
like
okay.
Now
I
got
all
the
little
pieces
now.
A
How
do
I
you
know
how
to
put
them
back
together
again,
and
so
I
think,
for
the
audience
right.
It's
kind
of
like
service
mesh
is
a
a
big
part
of
that
glue
and
how
you
how
you
bring
it
together,
and
I
think
you
know
the
other
point
I
really
want
to
highlight
too,
is
that
observability
factor
you
know.
I
worked
on
a
system
that
actually
used
com
over
http
many
many
years
ago,
and
we
we
actually
built
our
own
observability
as
well,
because.
C
B
C
A
lot
of
others
right,
aws
and
others
and
they're
all
basically
coming
in
you
know
in
the
first
kind
of
like
meeting
on
the
onboarding
they're
telling
us
the
same
thing.
The
reason
they
join
is
because
they
try
to
build
it
on
the
other
companies
and
if
they
had
service
mesh,
it
would
make
their
life
way
way
simpler.
So,
honestly,
it's
kind
of
like
a
very
good
validation
for
us.
A
A
You
know,
and-
and
you
know,
if
you
go
back
to
the
the
soap
soa
days
right-
I
mean
they
tried
to
do
the
same
thing
except
it
was
all
very
top
down
right
and
you
know,
and
with
the
micro
service,
you
know
it's
all
very
bottom-ups,
but
you
know,
and
so
it
gives
you
a
you-
can
do
a
piecemeal,
but
you
still
are
trying
to
solve
the
same
problem
at
the
end
of
the
day.
Yeah.
B
I
I
think
that
that
issue
of
sort
of
the
the
technology
at
the
service,
which
is
an
answer
to
this
proliferation
of
services
and
a
way
of
addressing
that
problem,
like
sort
of
leads
me
into
so
I
have
this
basic
understanding
of
that
concept,
both
behind
service
meshes
generally,
what
you're
doing
at
solo.I
o?
How?
How
do
you
connect
that
to
that?
B
First
bit,
we
were
talking
about
like
user
experience
and
developer
experience
like
what
what
are
the
real
improvements
in
developer
experience
of
a
service
mesh,
because
if
I
could
phrase
it
in
a
joke
as
as
a
developer
or
a
guy
who
talks
to
developers
a
lot
the
the
way
you
could
improve
service
mesh
ux.
For
me,.
C
Yeah,
no,
so
exactly
exactly
what
you
described,
I
mean.
I
think,
that
the
reason
there
is
service
away
service
mesh
is,
as
you
said,
is
basically
to
say:
you
know
you
missed
the
developer,
focus
on
the
business
development
and
business
logic,
and
you
let
us
the
idea
of
the
sre
or
the
organization
to
basically
come
with
all
those
policy
and
make
sure
that
it's
secured,
that
it's
observed
that
it's
everything
that
you
need.
I
think
that
so
that's.
C
What's
the
purpose
of
service
right
back
on
the
day,
I
said
that
it's
like
virtualize,
that
from
the
user
right
I
mean
all
the
ideas
to
take
it
away.
I
think
that
a
few
things
so,
first
of
all,
if
you're
looking
at
the
way
the
api
of
those
projects
are
happening,
I
don't
think
that
that's
coming,
you
know
the
persona
idea
of
who
is
actually
using
it.
Who
should
know
about
that?
It's
something
that
is
really
messed
right.
C
I
think
that
one
of
the
things,
for
instance,
that
we
built
to
our
product
is
basically
understanding
that
the
people
that
is
doing
the
application
and
other
people
who's,
basically
configuring
it
sometime
and
in
each
organization,
by
the
way
it's
different.
There
is
a
lot
of
customer
of
us
that
actually
are
more.
You
know
the.
C
And
they're
actually
interested
and
kind
of
like
do
it
all.
But
oh
we
have
startup
that
honestly,
you
don't
have
choice
in
that
point,
you
don't
care
you're!
Writing
the
code,
you're
running
it
you're
doing
whatever
right
and
there's
people
that
it's
totally
abstract.
They
don't
even
know
that
there
is
cluster
behind
this
thing.
So
I
think
that
it's
very
the
different.
The
question
is:
who
is
this
organization?
C
The
way
we
build
a
product
is
there
is
the
concept
of
work
space
that
I
do
know
that
this
concept
is
actually
coming
right
now
to
the
kubernetes
ecosystem,
which
is
great,
which
is
basically
the
ability
of
look
again.
Why
are
we
doing
all
of
this?
Why
there
is
open
shift
and
why
there
is
kubernetes
and
why
there
is
vm?
Why
there
is
all
of
this
all
together,
eventually
we're
trying
to
do
one
thing,
and
these
things
is
basically
careful
piece
of
your
infrastructure
and
delegate
it
to
the
application
thing.
C
C
Right
go
for
it
and
do
it,
but
there
will
be
team
that
I
will
not
trust
too
much,
and
maybe
all
I
want
to
do
is
tell
them.
You
know
you're
only
in
charge
of
the
writ
rise
and
and
and
the
timer.
That's
all
that's
all
I
want
you
to
do
so.
We
build
it
to
our
portal.
It
basically
has
the
concept
of
workspace.
You're.
C
So
so
that's
that's
pretty
pretty
strong
and
that
way,
honestly,
it's
fitting
to
every
organization,
because
you
can
decide
who
can
do
what
and
in
what
level
you
can
decide
if
they're
pushing
the
configuration
to
the
local
clusters,
which
usually
I
don't
think
you
should,
because
you
need
to
do
a
github
or
you
can
actually
do
it
to
the
management
cluster.
But
basically,
all
of
this
is
built
very
nicely
with
the
user
experience
that
way
that
you
will
know
the
developer
will
know
what
they
need
to
know
right.
You
can
come
with
your
own
crd.
C
The
cd
is
way
more,
simpler
way
more,
you
know
friendly,
so
it's
kind
of
like
another
layer
that
we
built
on
top
of
the
service
mesh,
which
is
make
it
more
accessible,
but
also
you
know
taking
configuration.
You
know
multi-tenancy
and
multi-clusters,
which
I
think
still
today
is
not
honestly
very
great
in
this.
B
B
Before
I
don't,
I
don't
want
to
take
us
too
far
off
into
that
into
like
the
little
details
of
this,
but
I
am
interested
in
something
so
right
now
you
mentioned
the
workspaces
effort
in
kubernetes
as
sort
of
an
augmentation
of
the
name
space
which
is
like
this
classical
term
in
the
industry
for
defining
a
virtualized
space
of
you
know
dedicated
to
a
user
or
a
process
or
a
view
of
a
file
system
on
plan
nine.
What
what
is
the
difference
between
the
name
space
in
the
workspace
or
a
better
question?
B
Really
more
specific
for
you?
It
is
what
what
does
a
workspace
mean
in
in
your
product
like
okay,
you,
you
just
mentioned
the
disconnect
as
sort
of
like
istio,
maybe
not
designed
for
this
kind
of
environment,
we're
building.
On
top
of
that,
how?
What
is
what
does
the
workspace
mean
for
a
developer
using
it?
It
is
configurability
of
my
view
of
the
world
and
how
much
I
need
to
know
about,
and
what
else
is
like
sort
of
virtualized
into
that
workspace.
C
Yeah,
so
I
mean
basically,
you
know
as
an
admin,
you
basically
see
everything
right,
then
you
can
basically
create
a
workspace
and
workspace.
Basically,
as
I
said,
is
a
grouping
of
namespace
in
different
cluster,
potentially
right,
it
doesn't
have
to
be
on
the
same
cluster
now
once
you're
grouping
it.
You
need
to
tell
me
first
of
all,
who
is
the
user
that
can
use
it?
What
are
you
delegating
to
and
what
they
can
and
cannot
do?
Where
is
the
default
configuration
namespace
right?
Where
should
they
push
into
configuration
and
so
on?
And
that's
it?
C
I
mean
basically
now
what
it's
meant
is
that
there's
an
admin?
I
can
see
everything
right,
including
a
beautiful
graph
and
everything
that
you
can
see,
and
you
need
all
the
policy
all
the
stuff
that's
attached
to
it.
We
have,
for
instance,
graphql
into
the
mesh.
We
build
it
into
sto.
So,
oh
envoy,
so
basically
you
can
see.
You
know
the
policies,
the
schema,
whatever
it's
all
the
big
management
that
you
need,
but
as
a
work
you
know
workspace
admin,
a
works
or
workspace
user.
C
When
you
log
in
you're
only
going
to
see
your
workspace,
you
can
even
plugable
to
make
a
decision
if
you
even
want
to
show
them
that
there
is
a
cluster
or
or
service
mesh.
Potentially
they
shouldn't
even
know
about
that
right
and
then
the
other
thing
is
the
idea
of
catalog.
So
you
know
right
now.
Maybe
I
trust
my
team,
so
I
will
tell
them:
hey
yeah,
you
can
you're
responsible
for
everything.
Well,
I
can
say
you're
responsible
only
for
retry
and
and
timeout,
but
I
can
even
do
it
more.
C
I
can
basically
say
I
don't
trust
you
at
all.
You
guys
crazy.
All
I
wanted
you
to
do
is
basically
I
will
give
you
basically
a
three
option.
You
can
do
timeout
five
time
or
ten
and
time
on
15..
That's
all!
I
trust
you
to
do
and
then,
as
a
user,
it's
basically
a
catalog
like
seriously.
They
can
come
and
choose
this
policy.
So
that's
number
one.
The
biggest
one
which
I
think
is
very
interesting,
is
the
future
of
import
and
export.
C
So
let
me
give
you
an
example:
we
have
a
big
huge
customers
like
youtube's
customer
right,
60
data
center,
the
biggest
destroyer
of
sto
running
in
the
world
today,
right
thousands
of
instances
of
sdo
and
on
that
organization,
it's
built
from
a
lot
of
team,
a
lot
of
groups,
and
you
know
huge
organization
that
they
bought
right.
So
it's
like
imagine
like
the
biggest
organization
that
you
are.
You
probably
can
guess
you,
but
anyway
they
have
one
billing
system,
that's
what
they
have
so
like
in
all
that
organization.
They
have
one
building.
C
So
that's
one
workspace,
but
they
want
the
other
team
to
actually
consume
it.
So
basically
we
have
the
concept
of
import
and
export,
so
you
can
take
a
workspace
and
basically
export
a
service
which
is
the
billing
service
and
that's
where
we
embed
a
developer
portal.
So,
basically,
when
you
actually
exported
it,
the
other
team
can
see
it.
They
can
click
at
the
the
tile.
They
can
see
the
dock.
They
can
ask
an
api
key
or
whatever
else,
they're
using
and
basically
onboard
them
in
the
stuff
inside
the
organization
right
and
basically
leverage
that.
B
C
Just
thought
about,
for
instance,
what
developer
portal,
meaning
that
concept,
for
instance
right!
That's
what
it
means
I
mean
somehow
you
want
to
consume
this
all
those
great
services.
So
again
we
did
a
lot
of
that
kind
of
work,
and
I
think
that
yeah,
it's
really
really
make
it.
You
know
exciting
for
people
and
you
mentioned
developer,
which
is
very
important.
What
is
the
user
developer?
But
honestly,
we
are
not
selling
to
the
developer
right.
C
We
are
selling
to
the
sre
or
the
it
or
the
platform
owner
or
the
open
shift
owner
right,
so
when
we
are
selling
it
to
them
honestly,
also
their
user
experience
needs
to
be
better
because,
honestly,
it's
hard
to
manage
it's
not
an
easy
thing
to
do
right,
for
instance,
today,
if
you
wanted
to
consume
it
sto,
you
need
to
do
n
minus
one,
which
is
basically
mean
that
you
need
to
upgrade
your
system
every
six
months.
Let's
say
honestly,
this
is
not
the
way.
C
I
I
don't
see
the
our
user
doing
it.
I
mean
right.
We
have
a
lot
of
open
source,
hey
openshift
user,
and
I
can
tell
you
they're,
not
upgrading.
Every
six
months
so
now
the
question
is
what
how
we
can
help
them
and,
for
instance,
for
our
product,
it's
n,
minus
four,
plus
we're
bringing
all
the
patches
and
cves
all
the
way.
Basically,
you
know
to
n
minus
four,
so
even
that
little
thing
right,
which
is
minor
or
you
know,
maybe
they
want
phipps
compliance.
C
Maybe
they
want
arms
because
they
want
to
save
money
only
that
by
itself
the
life
cycle
offers
to
install
upgrade
only
that
by
itself.
I
think
it's
extremely
powerful
and,
as
I
said,
we're
doing
exactly
the
same
thing
right
now
with
psyllium,
because
in
the
nutshells
we're
in
application.
Networking
right
I
mean
this,
you
know
it's
also
something
that
we
care
about,
and
we
can
do
some
interesting
defense
in
in
depth
because
we
basically
own
the
layer,
4
and
the
layer
7.
A
Yeah
we
should
talk
about
rel
adoption
at
some
point,
yeah
that
that
can
be
a
slow
activity.
So
I
know
you
wanted
to
talk
a
little
bit
about
what's
going
on
with
envoy
and
what
solo's
been
doing
with
envoy-
and
you
know
I
was
kind
of
thinking
here.
We
we
talk
a
little
bit
more
about
kind
of
forward-looking
stuff,
and
so,
if
you
could
tell
us
a
little
bit
about
what
you've
been
doing
with
the
invoice
proxy,
that
would
be
cool.
C
C
It
was
clear
to
me
that
it
would
take
long
long
time
until
they
will
get
it
right.
So
for
the
meantime
I
said.
Okay,
obviously,
I
do
believe
that
these
things
is
going
to
be
everywhere
one
day.
So
what
can
I
do
for
them
and
I'm
a
startup
right?
I
need
to
figure
out
how
eventually
to
create
a
product.
C
I
can
just
sit
down-
and
you
know
say
sure,
five
years
and
do
away
so
what
I
try
to
figure
out
is
that
what
I
can
build
that
I
honestly
I
can
sell
today
and
today
is
five
years
ago,
but
will
make
us
very
attractive
and
service
mesh
is
going
to
be
everywhere
and
I
bet
on
the
proxy
proxy
was,
you
know,
might
get,
got
it
right
from
the
first
go,
it's
not
surprisingly,
because
it
was
building
it
a
few
times
before
that.
So
when
I
saw
that
I
said,
okay,
that's
really
really
powerful.
C
This
is
the
thing
that
honestly
maturity
was
running
in
you
know
in
lyft
already
right
in
production
for
a
few
years
before
so
I
said
and-
and
I
really
like
the
fact
that
it
was
different
than
anything
else
like,
for
instance,
comparing
to
engine
inc
so
ho
proxy.
It
was
an
api
event
and
you
will
be
able
to
customize
it
because
there
is
what's
called
the
filter
chain,
so
you
can
put
your
own
logic
and
so
on.
So
I
was
honestly
really
really
important
to
us.
C
C
It
will
take
time
to
for
this
thing
to
come
to
come
to
place,
but
if
I
will
be
able
to
run
android
production
and
get
familiar
with
this,
get
it
better
make
sure
that
it's
working
scale
it.
That
will
give
me
a
huge
benefit.
So
what
I
did
is
I
started
with
the
api
gateway
market.
I
basically
target
the
ap.
I
get
my
market
and
said:
okay,
that's
a
market
that
honestly
nothing
changed
to
date.
C
I
will
say
honestly
the
only
thing
that
changed
there
is
basically
the
messaging
on
the
marketing
like
it's
basically
become
between
instead
of
api
gateway
to
api
gateway,
four
micro
services,
but
that's
what's
the
only
change
honestly
so
so
we
basically
build
the
best
api
get
to
the
api
gateway
that
I
will
want
to
run
in
production.
You
see
our
debase
consist,
you
know,
like
think
about
it
right
we
were
changing
the
world
with
devops.
We
were
doing
container
and
kubernetes,
and
all
this
exciting
thing,
and
then
you
know
what
I
want
to
run.
C
D
C
Great,
so,
every
time
that
I
try
to
describe
what
we're
going
to
do,
I
said
you
know
we're
gluing
we're
gluing,
so
it
was
the
best
word
I
found
and
therefore
we
changed
it
to
ooo,
but
that's
the
reason
we
call
it
the
way
we
call
it.
So
we
started
with
this,
which
was
really
good.
The
advantage
that
it
gave
us
is
to
number
one
we're
running
android
for
production,
probably
better
longer
than
anybody.
I
mean
not
lifting
guys,
but
you
know
what
I
mean
like
you
know.
We
know
envoy,
we
saw
it
in
stress.
C
We
saw
it
in
huge
stress.
You
know
most
likely
using
a
product
everywhere
right
now
on
the
get
way
even
forget
about
the
mesh,
so
I
I
felt
that
that
gave
us
a
lot
of
tooling
to
see.
What's
what
can
be
wrong?
How
do
you
upgrade
the?
How
do
you
manage
that
with
honestly?
It's
the
best
experience,
and
the
second
thing
that
I
think
it
was
really
really
good
for
us-
is
that
we
work
with
a
lot
of
the
customers
and
solo
has
a
lot
of
customers.
C
C
So
android
is
the
ability
to
have
the
filter,
as
I
said,
and
each
filter
is
basically
a
c
plus
plus
asking
code,
which
means
that
you
can
leverage
a
lot
of
those
libraries,
so
graphql
by
itself
is
very
complex,
c
plus
plus.
I
think
it's
really
really
complex,
now
merge
them
together
and
make
sure
that
it
will
scale.
C
And
now
you
have
basically
two
hop
every
time
because
it
should
go
from
the
proxy
and
then
it's
going
to
these
things
that
they
built
in
node.js.
Usually
honestly,
not
the
greatest
thing
that
I
really
want
to
see
in
my
infrastructure,
so
we
basically
kind
of
like
united
it
together
and
teach
andrea
to
speak
graphql.
C
C
A
It's
really
really
really
really
really
really
really
cool
yeah,
you
kind
of
touched
on
a
little
bit
but,
like
you
know-
and
I
noticed
you
know-
solo
is
kind
of
investing
in
in
graphql
like.
Why
should
I
care
about
graphql
like
what
is
what's
interesting
about
it?
You
know
it
feels
a
little
to
me
like
writing.
Sql
in
javascript.
You
know,
like
you
know
where
what
is
it
what's
it
for,
in
your
opinion,.
C
C
So
you
know
we
went
to
gitlab
right
at
the
github
and
basically
try
to
collect
all
this
data.
If
we
couldn't
use
graphql,
we
should
actually
needed
to
do
a
bunch
of
res
kind
of
like
query
to
everywhere,
and
that
would
be
really
really
hard
because
you
need
to
merge
and
then
you
write
a
lot
of
logic
and
so
on.
Instead
of
it,
we
just
ask
one
question
right:
in
graphql
boom
we
got
all
the
data,
it
saved
us
a
lot
of
time.
So
that's
us
right.
We
are
not.
You
know.
That's
not!
C
You
know
that's
just
an
example
of
use
case
but
think
about
people
that
all
what
they're
doing
it's,
basically
writing
a
ui
ui
application
or
you
know
basically,
so
if
you
think
about
it,
the
amount
of
the
work
that
they're
doing
by
merging
data
by
collecting
it
and
the
performance
of
getting
all
this
data
and
then
merge
it
on
the
server.
So,
honestly,
it's
really
really
hard
or
worse.
The
either
can
do
it
on
the
client
side
or
they
need
to
go
to
the
server
people
and
say:
hey.
C
Can
you
head
these
things
again,
which
is
more
complexity
and
now
go
figure
out?
Maybe
the
backend
engineer
is
busy
and
you
cannot
do
that.
So
all
this
process,
honestly,
it's
very,
very
annoying
and
and
just
slowing
down
your
team.
So
I
think
that
the
advantage
of
graphql
is
honestly
and
the
tooling
that
the
community
is
running
build
around
it.
Is
that
it's
damn
simple,
like
everybody
can
do
it,
they
can
do
it
really
quick.
C
It's
not
only
me
honestly,
the
reason
we
did
it
is
because
we
heard
it
from
the
customers
and,
if
you
look,
I
don't
know
just,
for
instance,
of
the
trending
of
google,
you
know
go
google
and
check
how
many
people
looking
for
rest
versus
graphql
boxes.
You
will
see
it's
like
a
zoop
right
people
very,
very
interesting
in
graphql.
C
A
Yeah,
like
like,
like
with
many
things,
it's
funny
because,
as
I
recall,
right,
ql
has
actually
been
around
for
quite
a
long
time
and
I
used
to
use
it
with
graphing
databases,
so
it's
kind
of
like
sometimes
when
something
starts
being
used
kind
of
slightly
differently.
I
have
to
kind
of
like
re-wrap,
my
brain
around
it
right,
because
you
know
I
used
to
use
it
this
way,
and
now
people
are
doing
something
different
with
it
so
yeah,
so
I've
been
playing
around
with
it
a
little
bit
yeah.
A
I
definitely
the
the
ability
to
kind
of
connect.
Information
together
that
doesn't
normally
go
together
in
your
data
mart
or
whatever
is
a
huge
advantage,
and
you
know
the
fact
that
that
so
many
tools
like
solos
are
kind
of
like
almost
like
natively
processing
it.
That
makes
a
another
huge
advantage
to
it.
You
know,
I
think,
all
the
databases,
starting
to
be
all
the
things
you
know
so
like
a
database.
C
D
C
C
A
Like
the
security
and
the
performance
and
all
the
stuff
which
you
know,
if
you
have
kind
of
that,
you
know
a
front-end
ui
developer
now
doesn't
have
to
go
and
figure
out
how
to
securely
access
each
of
those
or
rate
limit.
You
know
because
some
of
them
are
more
expensive
than
others.
You
know
et
cetera,
et
cetera,
right.
D
A
C
A
A
Yeah,
I
mean,
I
think
you
know
it
really
kind
of
opens
up
your
ability
to
kind
of
hire
as
well
right,
because
you
know
as
soon
as
you
don't
have
to
have.
You
know
every
junior
engineer
worrying
about
security
right
or
that
kind
of
thing.
You
know.
That's
it's
risky
to
have
junior
engineers
worrying
about
security.
You
know
they
need.
That's
where
you
get.
You
know
you
get
better
at
it
with
experience
right.
A
C
I
mean,
basically,
you
know
it's
the
difference
of.
Are
we
trusting
people
to
for
to
remember
to
do
this,
or
are
we
just
going
to
make
sure
that
it
will
be
forced
by
the
mesh,
and
I
think
that
yeah
it's
better
to
to
make
sure
that
the
people
who
know
what
it
is
will
take
responsibility
for
that
yeah.
B
A
A
We
will
generally
be
a
much
happier
set
of
campers
right,
so
the
other
one
that
I
wanted
to
ask
you
about
is
just
because
I
I
also
see
it
very
much
on
the
horizon
and
not
a
lot
of
play
is
web
assembly.
You
know
I
was
talking
to
a
friend
of
mine
about
it
the
other
day
and
he's
like
oh
yeah,
it's
gonna
take
over
the
entire
earth.
You
know
it
will
be
the
hot.
You
know
the
hottest
thing
since
sliced
bread.
A
C
B
C
The
layer
where
it
started
is
basically
the
browser
and
it's
making
a
lot
of
sense
right.
I
mean
they
were
the
reason
they
started.
It
is
because
I
think
it's
the
mozilla
team
and
the
reason
is
they
wanted
to
allow
people
to
create
something
that
is
extremely
extremely
fast
right,
so
you
don't
have
to
write
only
javascript.
C
This
is
great
technology
because
the
way
they
build
it
because
of
that
functionality
there
is
a
lot
of
advantage
here.
First
of
all,
you
can
write
it
in
a
lot
of
language
and
it's
translating
to
a
lower
level
code.
Second
of
all,
it's
dynamically
loaded
to
the
browser,
which
means
that
you
can
dynamically
load
it
to
somewhere
else
and
the
last
one
is
basically
the
fact
that
it's
sandbox
it's
basically
contained.
C
You
know
the
envoy
right
and
add
logic,
and
I
think
that
that
web
assembly
was
really
nice,
because,
basically,
what
they
were
thinking
is
that
what
you
there's
a
similar
functionality.
You
need
to
make
sure
that
it's
not
going
to
take
down
the
envoy.
You
need
to
make
sure
so
it's
have
to
be
contained.
It
needs
to
dynamically
below
to
envoy,
because
you
don't
want
people
to
recompile
envoy
and,
and
ideally
we
want
them
to
do
it
in
any
language
they
want,
but
the
performance
should
be
close
to
native.
C
C
But
a
few
things
happen
in
the
market,
and
this
is
very,
very
interesting
in
my
opinion.
So
this
is
I'm
just
going
to
kind
of
like
come
again.
It
started
in
the
browser
we
brought
it
to
android,
but
there
is
a
lot
of
other
people
that
are
trying
to
replace
docker
or
container
deal
with
econo
do
with
this.
So
I
think
again,
three
different
reasons.
Right
I
mean
in
the
browser.
It's
make
a
lot
of
sense
and
it's
using
it's
fantastic
and
envoy.
C
Well,
we'll
talk
about
it
in
a
second,
because
there
are
some
issues
in
the
in
as
a
containers.
Honestly,
I
don't
think
that
the
benefit
will
be
too
big.
You
know
like
think
about
why
docker
did
catch
versus.
I
don't
know
other
technology
or
like
unicorn,
that
we
tried
to
do
before
the
the
reason
is
because
people
will
change
all
the
market
only
if
the
benefit
is
huge.
So,
like
you're
saying
well,
I
will
need
to
to
pay
a
price,
for
instance,
create
a
tooling
for
debugging
or
something
like
that.
C
But
I
know
that
when
I
will
do
that,
I
mean
you
know
we'll
get
to
the
best
experience
ever
and
it
will
be
fantastic.
That's
why
docker
catch
right.
It
was
10
times
better
than
vm.
When
we
came,
for
instance,
with
unicorn
people
said
well,
we
already
have
docker
yeah,
it's
a
little
bit
faster,
yeah,
it's
a
little,
but
who
cares?
Should
I
right
now
reinvent
everything
because
of
it
doesn't
make
any
sense,
but.
A
C
Exactly
exactly
so
to
me,
you
know
it's
exactly
the
same
idea
with
wasan
is
that
makes
sense
to
make
watson
run
instead
of
container
yeah.
Maybe
sometimes
there
is,
but
honestly
it's
not
that
it.
You
know
what
I
mean:
it's
like
you're,
not
getting
dramatically
better
performance
you're,
not
getting.
Why
that's
a
question?
I
will
ask
myself,
so
I
don't
think
honestly
personally,
I
believe
this
is
not
something
that
I
know
people
working
on
this
and
excited
about
it.
C
C
What's
going
on
in
the
market,
you
know,
as
I
said,
wasn't
quite
a
lot
of
excitement
specifically
for
stuff
like
like,
like
the
web
browser
as
well
as
as
envoy,
but
in
order
that
to
be
very
good
in
envoy,
we
need
dueling
and
unfortunately
there
were
some
changes
that
happened
right,
for
instance,
mozilla
team,
I
think,
was
laid
off
and
a
lot
of
them
went
to
and
other
places
so
a
lot
of
the
contributors.
Suddenly,
you
know
less
focus
on
this.
There
was
a
lot
of
politics
involved
and
so
on.
C
B
C
Is
that
going
to
be
the
next
thing
that
happening?
I
mean
it's
a
good
technology,
it's
defensive!
The
community
will
stand
up
together
and
put
the
things,
but
right
now
I
don't
see
a
lot
of
work
done
there,
like
specifically
on
any
part-
and
that's
worry
me
because
it
feels
to
me
that,
even
though
that's
an
a
nice
idea-
and
you
just
don't
know
that
a
lot
of
people
using
it,
which
is
a
problem
if
you're
not
using
it-
you
don't
know
where
it's
the
problem
so.
A
D
C
Go
and
decide
that
we're
making
it
successful
again,
as
I
said
like
we
are,
I
don't
know
if
you
remember,
but
when
we
announced
web
assembly
support
for
android
we,
actually
we
were
the
user
experience.
We
created
that
docker,
like
two
links
and
so
on.
The
thing,
as
I
said,
is
that
there
was
a
lot
of
promising
but
less
implementation.
So
it's
getting
it's
getting
better,
but
honestly,
just
too
slow.
That's
the
problem
that
I
have
you
know
like.
We
talked
about
the
ability
to
write
in
every
code.
But
honestly,
you
know.
C
And
there's
not
a
lot
of
people
working
on
this.
So
to
me,
that's
my
warriness.
Is
someone
who's
looking
at
the
side
and
show
I
don't
know
that
it's
going
as
fast
as
I
hope
it
to
go,
and
eventually
I
know
if
it's
not
it's
just
going
to
be.
Oh,
you
know.
No
one
really
doesn't
that's
what
will
happen
no
in
android.
Specifically,
I
think
that
in
the
browser
is
they're
there
to.
C
Different
use
cases,
so
that's
my
opinion,
a
personal
opinion,
I
think
in
general
what
people
trying
to
build
in
every
organization
is
basically
plug-in.
So
I
think
that
this
thing
that
is
more
sexy
right
now
is
ebpf.
It's
not
that
different.
It's
basically
plug-in
to
the
operator
system,
but
it's
good,
because
if
you
think
about
it,
a
lot
of
the
stuff
that
we
like
a
lot
of
the
stuff
that
we're
building
always
start
at
eye
level
because
it's
easier
to
implement
and
then
we
optimize
it
as
low
in
the
stack
as
we
can.
C
A
C
A
A
little
kind
of
sidebar
we
actually
talked
to
liz
rice
about
ebpf
in
episode,
seven,
if
you
want
to
go
back
and
watch
it
for
anybody,
who's
wants
to
hear
more
about
that.
I
think
webassembly
is
also
super
interesting,
like
on
the
kind
of
envoy
level,
because
I
mean
who
doesn't
want
dynamically
loading
libraries
that
are
replaceable
on
the
fly
you
know
like.
That
seems
like
a
very
strong
feature,
so
I
really
like
them
in
the
envoy.
A
I
think
they're
really
interesting,
but
I
I
hear
you,
the
the
community
has
to
kind
of
be
there
for
it
right
and
it
needs
to
be
that
you
know
kind
of
the
uses
of
it
need
to
be
more.
You
know
somebody's
most
important
components.
You
know
we
need.
We
need
a
bunch
of
people
who
are,
you
know,
kind
of
mainlining
that
tool
chain
as
part
of
their
deployment.
Otherwise,
you
know,
there's
not,
there's
not
enough
focus
on
it.
B
A
Yeah
all
right,
so,
let's
see
moving
to,
I
don't
know,
did
you
have
more
questions
about
that
josh?
Or
do
you
want
to
move
on
to
something
else?
Okay,
cool,
all
right,
so
we
we
do.
You
know,
I
think
we
should
ask
right
it's
like.
So
how
has
your
experience
been
as
a
kind
of
a
community
member
and,
as
you
know,
kind
of
trying
to
run
this
startup
and
you
know
and
launching
it
off
the
ground?
A
And
you
know-
and
it
sounds
like
quite
successfully-
you
know
and
doing
that
in
kubernetes
community
is
is
it
is
it
embracing,
like
is
the
organ?
Is
the
community
embracing
concepts
like
people
doing
startups,
or
is
there
a
certain
amount
of
you
know,
fear
of
capitalism
or
you
know?
Is
there
have
you
found
a
nice
happy
medium
there?
What's
the
how's
that
experience
been
as
being
a
community
member
and
also
trying
to
run
this
successful,
startup.
C
Yeah,
I
think
I
think
that
the
community
itself
is
awesome
and
kubernetes
and
I
think
that's
what
make
it
so
successful.
I
think
that,
as
always,
there's
the
people
who,
as
community
members,
are
having
a
blast
and
doing
great
and
very
accepting
and
doing
awesome
and
there's
their
cooperation,
that
they
can
be
less
nice.
But
I
think
this
is
fine.
I
mean
in
the
nutshells.
I
think
that
the
kubernetes
ecosystem
is
great.
I
mean,
as
I
said
here,
they
are
so
welcoming
and
so,
including
and
and
everything
that
we
can
do
so.
C
I
mean
to
me
personally,
and
it's
not
only
I
mean
kubernetes
is
one
of
the
environment.
I
mean
the
other
one
is
st
all
right
I
mean
the
community.
There
is
insanely,
good
and
awesome
envoy
community
right.
We
are
a
big
part
of
this
and
psyllium
right
I
mean
psyllium
right
now
is
becoming
a
cncf
product
like
every
good,
produ
honestly
project,
that
being
successful,
you
need
to
have
more
than
one
profile
and
selling
it.
C
Otherwise,
it's
basically
their
product,
it's
not
the
community,
so
I
think
you
guys
know
that,
but
solo
is
selling
psyllium
and
we
enhancing
quite
a
lot
and
excited
about
that
a
lot,
because
I
think
it's
going
to
give
us
another
layer
that
we
can
you
know
optimize
the
mesh
and
optimize
the
application,
networking
and
so
on.
So
so
to
me,
the
communities
are
great.
I
mean,
as
I
said
to
you,
I
mean
it's
interesting,
because
each
of
them
is
different.
C
Right
I
mean
sto
from
the
beginning
was
very
you
know,
inclusive
like
very
interesting
and
getting
new
people
and
just
help
and
and
be
together.
I
think
android
the
same
thing.
I
think
that
kubernetes,
that's
what
I
saw
as
well.
I
think
that
you
know
syllabus
is
a
new
community,
so
this
would
be
interesting
because
mainly
right
now
it's
less
than
women
people.
C
A
To
say
yeah
yeah
well,
I
think
we
should
probably
wrap
it
up
there
and
you
know,
but
thanks
so
much
for
you
know,
sharing
your
thoughts
with
us.
You
know.
I
really
appreciate,
like
I
said
that
the
whole
point
of
the
show
right
is
to
get
some
insight
from
people
are
kind
of
in
the
trenches
and
and
working
on
the
stuff
about
what
you
think's
gonna
happen
next
and
I
I
really
do
think
you've
been
able
to
share
that
with
us.
So
I
I
really
appreciate
it.
B
Indeed,
indeed,
I
want
to
extend
my
thanks
to
you
for
joining
us
as
well.
I
really
enjoyed
the
some
of
the
kind
of
breakdown
of
how
you
thought
about
your
forward
analysis
of
the
space
that
you
ended
up,
building
a
company,
and
I
thought
that
was
actually
quite
revelatory
really
interesting.
So
thank
you.
Oh.
A
All
right,
so
we
wanted
to
invite
tam,
who
is
our
community
manager
for
kubernetes
by
example,
and
we
we
went
back
and
forth
on
on
pronouncing
her
last
name
and
I'll,
say
yen.
If
I
recall
correctly,
and
so
we
just
wanted
to
show
off
kind
of
one
of
the
learning
paths,
that's
on
kubernetes
by
example,
that
is
coming
out.
Is
it
out
or
is
it
or
should
be
out
by
now.
A
As
we
used
to
say
on
openshift
tv
on
all
our
different
shows,
you
know
on
the
show
we
kind
of
live
in
the
future
and
so
we're
never
quite
sure
where,
where
the
real
world,
if
it's
caught
up
or
not
yet
so
yeah.
So
I
have
clicked
the
share
button.
But
I'm
not
sure
if
it
is
sharing
to
the
actual
stream.
C
A
A
A
D
Yeah
so
first
you
know
some
of
the
audience
numbers
that
may
not
know.
Cue
by
example,
is
a
free
learning
community
site,
so
it's
designed
so
that
you
can
learn
by
example.
So
if
you
go
to
cubeexample.com
linkedin
and
then
I
can
walk
you
through
some
of
our
new
stuff
so
right
now
we
have
15
learning
paths
and
we
introduced
five
at
kubecon
a
couple
weeks
ago.
D
So
since
yeah,
so
that's
all
of
our
stuff
right
now,
which
is
pretty
extensive
and
then,
if
you
know
all
of
our
learning
paths
are
developed
by
contributors
and
there's
a
mix
of
content.
So
there's
hands-on,
guided
exercises
so
that
you
can
learn
by
doing,
and
then
there
are
video
tutorials
that
you
can
learn
by
watching.
So
right
now,
since
this
show
was
on
sort
of
a
smash,
let's,
let's
click
on
the
istio
fundamentals
track
yeah.
D
So
that's
a
new
track
that
we
announced
a
couple
weeks
ago
shout
out
to
andrus
hernandez
bermudez
from
mexico
city
for
creating
this
new
content
for
us.
But
there's
a
couple
guided
exercises
and
a
couple
lectures
that
you
can
go
in
and
learn
everything
that
you
want
to
learn
about
istio
and
it's
some
really.
D
A
Right
right,
I
think
at
least
for
me:
that's
my
preference
anyway,
like
you
know,
it's
funny
the
I
do
a
lot
of
video,
but
I
actually
like
to
read
stuff.
So
you
know,
although
ascii
cinema
is
very
very
cool,
if
you
haven't
checked
that
out,
which
lets
you
actually
cut
and
paste
from
the
videos
which
makes
things
handy.
D
A
B
D
D
D
D
A
So
you
can
also
do
the
local
version
box
too
right,
but
I
think
change
names
so,
but
yeah
you
can.
You
can
also
download
that,
but
mini
cube
is
really
quite
nice
and
quite
easy
and
pretty
easy
to
plug
ins
into.
I
was
just
experimenting
with
it
over
the
weekend
because
I
haven't
used
it
in
a
while
yeah.
So
that's
pretty
cool.
B
D
Yeah
absolutely
and
then
a
new
feature
that
we
launched
so
definitely
after
each
learning
path
is
a
beyond
kbe
section
where
you
can
find
links
to
like
repos
and
prerequisites,
but
something
that
we
recently
launched
and
you're
just
on.
It
is
our
kbe
community
forum,
it's
beta
right
now,
but
yeah.
If
you
click
into
it,
it's
a
live
forum.
You
could
start
a
discussion.
C
D
A
D
A
D
Really
soft
putty
that
I'm
wearing
right
now
so
yeah,
first,
three
people
so
I'll,
look
out
for
that
yeah!
So
that's
all
the
new
stuff,
we're
always
looking
for
feedback.
We
release
every
at
every
coupon.
So
kubecon
eu
was
our
last
release
and
then
our
next
release
will
be
at
cubecon,
north
america
in
october,
so
we're
planning
for
new
content
and
new
features
for
the
site,
but
we'd
love
to
hear
what
you
know.
The
community
would
like
to
see.
A
Yeah
and
basically
there's
a
there's
a
key
to
watching
live
right
is
that
you
know
now.
Now
you
have
a
chance
of
of
entering
the
contest
and
being
first,
you
know
and
getting
you
know,
swag
is
always
the
you
know,
always
the
most
important
cool.
So
should
we
wrap
up
the
show
there
and
and
call
that
an
episode.