►
From YouTube: Layer5 Community Meeting (Oct 30th, 2020)
Description
@Hashicorp Consul v1.9 release overview by @blakecova. Jose Castro shows off the new community calendar.
A
A
A
Oh
yeah,
it
yeah
you
know
last
week
was
worse
for
sleep.
Some
of
us
were,
and
some
of
you
on
the
call
were
probably
well
recording
some
cube,
cube
contacts
I'll
you
know
hear
some
advice.
Don't
not
only
don't
wait
to
the
last
day
to
record
your
talk,
but
don't
wait
until
the
evening
of
the
last
day,
especially
if
you
have
two
talks
to
record
it
didn't
yeah
anyways
last
week
was
worse,
so
I've
got
I've
gotten
some
sleep
since
then,
but.
A
A
A
C
A
A
All
right,
fair
enough,
good
deal,
everyone,
that's
on
the
call
should
have
access
to
this
doc,
there's
a
link
to
the
doc
in
the
chat.
If
you
don't
see
it,
you
know
say
something:
if
you
don't
see
it,
I
don't
know
that
we've
shown
some
of
the
work
that
the
community
members
here
have
done
recently
on
the
this
community
page.
A
There
are
two
meetings
that
are
listed,
that
we
are
maintainers
within
or
that
we
spend
a
lot
of
time
in
and
so
a
lot
of
things
that
are
done
in
this
community
end
up
being
in
those
two
discussed
in
those
two
cncf
calls,
and
so
hence
they're
listed
here.
But
but
this
is
a
nice
reference.
That's
that's
nice,
while
I'm
giving
a
general
update
like
this
I'll
also
say.
A
A
A
A
Good,
okay,
if
you
don't
toss
your
name
in
while
someone
else
is
giving
a
talking
I'll
toss,
your
name
in
and
I'll
put
a
nice
little
made
up
last
name
next
to
you
just
as
a
forewarning,
so
you
don't
have
to
put
your
name
in.
But
if
you
do,
there's
a
couple
reasons
why
we
put
it
in
there.
One
is
to
well
it's
it's
about
to
be
what
pratik
is
going
to
talk
about
in
some
respects.
It's
about
doing
things
openly.
A
Maybe
you
said
something
maybe
didn't
that
counts.
Maybe
it's
contributing
some
code
like
maybe
it's
writing
some
documentation
filing
a
bug
providing
feedback
going
and
talking
about
the
work.
The
projects
that
are
going
on,
like
like
being
engaged,
comes
in
all
different
forms.
I've
been
disappointed
in
a
number
of
other
communities
where
it
was
really
only
code
that
was
counted,
and
I
thought
that
that
was
a
miss.
B
All
right,
so
am
I
audible
what
okay
sure.
So
this
is
just
a
general
kind
of
thing
which
you
want
to
talk
about
over
here,
which
is
the
first
last
week
we
were
checking
our
slack
stats
like
how
much
our
community
is
being
active
and
we
had
around.
If
you
see
in
the
community
meeting
dock,
we
had
around
2900
messages
last
week
on
you,
so
that's
good.
B
We
would
like
you
to
be
more
public
and
just
use
all
the
channels
we
have,
whether
it's
measuring
whether
it's
mystery,
ctl
or
even
general,
or
newcomers
channel
that
you
ask
your
doubts
over
there
and
anyone
would
come
and
like
solve
your
doubt
so
yeah.
We
would
like
to
see
that
80
percent
of
all
messages
that
we
are,
eighty
percent
of
all
the
messages
being
game
should
reduce
to
a
smaller
number
and
people
get
more
active
in
public
channels,
so
yeah.
Why
are
we
doing?
B
This
is
because
we
want
everybody
to
learn
more
like
when
we
have
a
discussion
over
some
topic
like
we
had
the
discussion
in
general,
like
in
the
general
channel
today
that
how
you
know
somebody
was
having
a
doubt
over
how
to
push
something
like
that
to
push.
He
was
having
some
doubt
with
it
and
like
lee
and
josh
jumped
in
and
explained
him
all
the
steps
that
he
needs
to
do
in
order
to
correct
his.
B
B
A
If
you
will
that's
actually
part
of
what
happens
when
discussions
are
public
people
have
a
sense
or
have
an
opportunity
to
chime
in
and
and
a
sense
of
ownership
and
and
literally
ownership,
and
so
I
for
me,
like
I
don't
maybe
it's
just
important
to
have
like
this
this
first
one,
and
that
is
learning,
is
a
real
theme
of
what
goes
on
here.
There's
a
lot
of
tech,
a
lot
of
languages,
a
lot
of
tech
and
for
as
much
as
I
like
to
think
that
I
know
I
could.
A
A
I
learned
that
in
aws
api
gateway,
you
can
go
and
reconfigure
your
routes,
change,
how
you
know
your
config
of
what
you
want,
aws
api
gateway
to
do,
and
it
looks
like
all
of
the
settings
are
there
and
accepted,
and
but
unless
you
go
over
to
the
hidden
ui
menu
that
says,
deploy
api,
it
might
take
you
about
12
hours
of
troubleshooting
to
figure
that
out
so
anyway.
The
point
is:
don't
be
embarrassed
about
learning,
because
everyone
here
is
learning
and
so
the
more
questions
you
ask
publicly
the
faster
we'll
all
move.
A
Oh
very
good,
next
topic,
I'm
jose,
who
I
don't
know
that
he's
on,
but
he
had.
We
just
talked
about
the
calendar,
and
so
that
was
nice
and
then
hashicomp
was
had
here
two
weeks
ago,
a
couple
of
new
products
and
some
whiz-bang
features
in
console,
one
nine,
and
so
we're
fortunate
that
layer,
five
has
partnered
with
hashicorp
and
we're
fortunate
that
actually
we
had
a
couple
of
new
hashicorp
folks
join
this
week
in
the
community,
but
also
that
blake
has
been
a
long-standing
member
and
pretty
active
and
so
blake's.
A
Also
the
one
of
the
console
product
managers
whose
responsibilities
are
is
the
one
whose
responsibility
is
over
consoles
service,
mesh
functionality
and
roadmap,
and
so
blake
really
happy
to
hear
from
you
today.
I
figured
that
the
community
could
well
the
one
that
blake
actually
there's
some
updates.
I
don't
know
that
we've
conveyed
to
you
about
the
console
adapter.
I
know
that
we've
spoken
about
various
enhancements
that
it
needs
to
have.
It
has.
A
I
think,
since
the
last
time
that
we've
spoken
on
the
adapter,
it
has
been
overhauled
and
it
has
a
lot
more
functionality.
It's
it's
not
one.
Nine
compatible
or
we
haven't
tested
that,
but
it
is
in
a
much
better
place,
which
is,
which
is
good,
that
was
kind
of
a
blocking
factor.
I
think
for
some
of
the
things
we
were
looking
to
do.
C
Yeah,
I
actually,
I
saw
some
of
the
pull
requests
on
that
and
saw
that
it
was
updated
from.
I
think
it
was.
It
won't
only
able
to
deploy,
console
1.5
before
and
so
now
I
believe
it
was
184
or
one
eight
one
of
the
the
latest
production
version
before
the
latest
beta.
So
that
was
great
to
see.
I
really
appreciate
a
person
who
in
the
community
who
contributed
to
updating
that.
C
I
think
I
provide
some
comments
on
the
pr
some
pointers
to
kind
of
how
to
best
configure
console
but
glad
to
see
that-
and
you
know
I
know
we
definitely
have
some
customers
who
have
been
looking
at
mesheri
for
multiple
things.
They
want
to
do
primarily
for
benchmarking,
and
so
they
were
pretty
excited
to
see
that
now
that's
updated.
They
can
use
it
and
deploy
a
console
and
do
some
of
their
testing.
So
that
was
really
great.
A
I'm
glad
that
we
were
speaking
about
this
because
I
just
just
recalled
yesterday
had
a
new
connection
on
linkedin.
That
was
asking
if
I
could
give
him
a
set
of
slides
on
the
difference
between
istio
and
console,
because
he
wants
to
use
them
internally
to
help
facilitate
a
decision.
And
so
so
that's
kind
of
a
timely.
C
Is
it
beta
currently
or
it
is
yep,
it's
beta?
So
let
me
share
my
screen
and
I'll
start
with
kind
of
talking
through
the
latest
announcement
for
one
at
nine.
What
some
of
these
features
mean
and
then
what
the
the
path
is
to
ga,
and
so
you
know,
as
leah
mentioned,
we
had
hashikank,
which
is
our
user
conference.
C
The
first
one
is
what
we're
calling
application
aware
intentions,
and
what
this
is
is
intentions
in
console
are
the
authorization
policies
that
you
can
configure
to
define
which
applications
within
the
service
mesh
are
allowed
to
talk
to
other
apps.
So
I
think
istio
calls
these
authorization
policies,
for
example
very
similar
and
how
they
worked
in
the
past
with
console
is
that
they
were
all
based
off
of
service
identity.
C
1.9
now
brings
that
we
have
now
the
mix
of
identity
based
and
application,
aware
intentions,
and
so
for
the
application
aware
you're
able
to
define
intentions
which
match
off
of
things
in
the
http
request,
like
the
path,
header
and
method
and
define
complex
policies
to
allow
very
you
know:
granular
access
to
services
and
different
endpoints,
and
so,
like
here's,
an
example
of
these
service
intentions.
I
should
highlight
maybe
another
change
that
we
made
is
before
these
con.
C
It
was
just
a
very,
very
simple
interface
and
you
would
have
kind
of
this
one
intention
per
source
and
destination
that
you
want.
What
we
ended
up
doing
is
moving
these
into
what
we
call
config
entries.
So
this
is
how
all
of
the
other
layer,
7
routing
within
console,
is
handled.
It's
more
of
a
document
format
similar
to
something
like
yaml
and
then
you
know,
gives
you
a
way
to
for
multiple
sources,
keep
that
and
kind
of
track
that
in
one
file.
C
C
C
And
what
this
allows
you,
you
know
from
an
operator
or
application
developer
perspective-
is
to
have
a
consistent
way
that
you're
defining
your
security
policies
for
both
tcp
and
http
applications
and
then
having
all
of
that
enforced
by
the
service
mesh.
Instead
of
having
to
maybe
handle
some
of
that
enforcement
directly
within
your
application.
C
So
that
was
the
the
first
big
feature
and
we've
got
a
number
of
documents
on
how
to
use
and
deploy
that
there's
an
actual
guide
for
actually
walking
through
and
learning
how
to
to
use
these
intentions.
I
definitely
recommend
checking
that
out.
That's
over
on
our
learn
the
hashicorp.com
website,
the
other
big
feature
that
we
announced
is
service,
mesh
visualization,
and
so
what
this
provides
is
a
within
the
console
ui.
C
We
now
give
you
a
topology
view
showing
you
how
your
services
are
configured
within
the
service
mesh
which,
for
a
given
service,
say
app,
which
services
are
dependent
on
it
from
a
downstream
perspective
and
then
what
is
it
in
turn
dependent
on
was
what
upstreams
does
it
need
and
then
show
you,
the
health
and
availability
of
those
service
dependencies,
and
this
just
makes
it
easier
for
operators
one
to
determine
once
they
deploy
their
apps.
Did
they
properly
stitch
everything
together
and
then,
if
everything
is,
you
know
connected
with
the
right
dependencies
again?
C
What's
the
health
and
availability
of
those
we
also
built
on
this
to
also
include
metrics,
so
we
zoom
out
a
little
bit
here.
We
have
a
a
plugable
metrics
interface,
the
the
first
driver
that
we
have
for
that
supported
is
using
prometheus.
But
if
you
configure
console
now
to
talk
to
your
prometheus
instance,
you
can
get
real-time
metrics
for
services
and
their
communication
within
the
service
mesh,
and
so
this
again
helps
as
you're,
maybe
troubleshooting,
something
within
your
environment.
C
You
don't
have
to
go
back
and
forth
between
your
grafana
dashboard
and
console
you're
able
to
get
one.
You
know
one
view
here
within
console
of
the
configuration
and
then
the
communication
between
services
and
then,
if
you
need
to
drill
down
and
look
at
more
historical
data,
then
you
would
click
this
link
here,
open,
metrics
dashboard.
It
would
go
launch
you
into
your
grafana
instance,
where
you
can
look
at
more
either
metrics,
more
in-depth
or
again
the
historical
data
there.
C
So
the
other
big
change
that
we
introduced
is
custom
resources
for
kubernetes.
Sorry,
I
have
a
question
here
in
the
chat.
I
want
to
make
sure
I
get
to
it.
Oh
awesome,
visualization
sounds
great
yeah.
It's
pretty
exciting.
A
lot
of
people
definitely
like
that
that
feature
so
custom
resources
is
another
big
change.
C
I
was
showing
some
of
the
config
examples
earlier
of
deploying
you
know
configuration
entries
so
again
I
mentioned
this
is
how
you
manage
layer,
7
configuration
within
console,
there's
multiple
different
config
entries
for
doing
routing
splitting
and
then
service
resolving,
and
you
can
see
some
of
the
examples
here.
If
I
go
under
the
router,
they
look
similar
to
the
examples
I
showed
before
right,
but
this
is
not
in
a
kubernetes
environment.
C
Oh
excuse
me.
This
is
not.
Let
me
scroll
down
a
little
bit.
We
have
examples
down
here
so
now
you
can
see
you
know
this
is
a
example
of
a
proxy
defaults,
config
entry,
but
right
directly,
in
line
with
your
other
yaml,
you
could
define
that
the
console
configuration
this
example
we're
actually
bypassing
some
of
or
exposing
some
other
paths
through
the
proxy
outside
of
the
authorization
or
intention
checks
that
the
proxy
normally
has.
C
If
I
go
down
a
little
more
like
here's
that
in
intentions,
example,
I
was
showing
earlier
now
in
in
yaml
form,
so
none
of
the
fields
or
anything's
changed.
But
again,
this
allows
you
within
kubernetes
to
keep
all
of
this
now
config
in
line
with
how
you
normally
deploy
things
and
then
interact
with
it.
How
you
normally
would
so
you
can
actually
go
over
to
a
terminal,
real
quick
and
you
can
do
things
like
get.
You
know
service
intentions.
Oh
excuse
me,
my
sharing
is
paused
because
I
was
not
sharing
my
entire
screen.
C
C
C
So
there
are
also
tutorials
for
that
on
our
website.
So
if
you
go
to
again
learn
to
hushcorp.com
full
tutorial
on
managing
using
crds
to
manage
resources
within
console
and
then
one
of
the
last
kind
of
larger
features
we
introduced
was
added.
Support
for
deploying
console
on
openshift
openshift,
obviously
is
kubernetes,
but
there's
some
slight
differences
in
that
platform
versus
vanilla
kubernetes.
C
It
runs
with
a
little
more
strict
security,
you
know,
constraints
and
policies
and
then
what
a
standard
kubernetes
distribution
has,
and
so
we
just
had
to
you-
know,
update
the
helm
chart
to
accommodate
for
those
things.
But
now,
if
you
want
to
deploy
console
on
open
shift
the
helm
chart,
the
latest
version
of
the
helm
chart
is
validated
with
openshift
4.x.
C
C
To
be
honest,
I'm
not
so
familiar
with
opa
and
constraints,
but
what
the
intentions
is
is
that
is
actually
utilizing
envoy
our
back
rules
under
the
hood,
so
in
previous
versions
of
console.
What
we
did
is
we
had.
We
would
configure
envoy
with
with
an
xdox
z
filter,
so
that
it
made
a
callback
to
a
local
console
agent
to
check
whether
or
not
connections
should
be
allowed
and
now
on
this
release,
we're
actually
removing
that
callback.
C
C
C
One
of
them.
You
were
working
on
synchronizing
health
checks
from
pods,
liveliness
and
readiness
probes
into
consoles,
so
that
that
health
is
accurately
represented,
and
then
this
last
feature
listed
here,
it's
a
little
vague,
but
what
this
essentially
is
is
in
very
large
environments.
We've
changed
the
communication
protocol
between
the
console,
servers
and
clients
to
make
it
more
efficient,
allowing
you
to
greatly
reduce
cpu
and
bandwidth
utilization,
and
so
in
environments
with
you
know,
tens
of
thousands
or
thousands
of
nodes
they
can
see.
C
C
The
first
apis
at
this
impacts
are
apis
for
service
health
and
availability,
but
we're
looking
to
expand
that
out
over
time
and
then,
hopefully,
all
of
consoles
api
endpoints
will
will
utilize
this
more
efficient
communication
model.
So
I
think,
you'll
see
a
little
more
to
come
in
this.
Probably
things
are
a
little
more
exciting
and
make
this
feature.
The
value
of
this
feature.
Click
over
time.
C
Like
you
recall,
the
tech,
that's
been
used
for
the
streaming
yeah,
so
we
basically
changed
from
our
our
own
kind
of
rpc
mechanism
between
clients
and
servers.
Now,
that's
all
using
grpc
and
using
protobufs
in
order
to
send
that
data
across
versus
before
it
was
encoded
with.
You
know,
I'm
not
entirely
sure
I'm
drawing
a
blank
there,
but
is
it,
but
it
doesn't
matter
because
that
was
the.
C
Yeah,
so
that's
all
I
had.
I
definitely
want
to
be
conscious
of
time,
but
I
will
put
some
links
here
in
in
the
community
doc
for
some
of
the
documentation
that
I
share
tutorials
and
things
like
that.
So
if
you
want
to
kick
the
tires
on
console,
you
know
I
definitely
recommend
checking
those
out
and
please
give
us
feedback.
This
console
1.9
is
currently
in
beta,
and
so
you
know
there
might
be
a
few
bugs
or
things
lurking
here
or
there,
but
test
it
out,
give
us
feedback.
B
C
A
Yeah,
that's
true,
or
and
or
there's
an
opportunity
in
there
for
measuring,
makes
that
pretty
fat
pretty
quick
like
and
the
ability
to
do
different
sample
apps.
You
know,
potentially
on
the
on
top
of
the
console.
It's
not
it's
an
opportunity
to
leverage
measuring
in
that
way.
That's
another
potential.
There.
C
C
Question
so
everything
that
we
released
in
1.9
is
all
in
open
source.
We
didn't
actually
have
any
any
price
features
in
this
release.
You
know
we
may
in
other
releases,
but
really
we
felt
things.
These
were
things
that
were
generally
applicable
to
any
user
of
console.
Typically,
in
the
enterprise
platform,
we
try
to
solve
things
that
are
organizational
problems
or
introduce
features
that
solve
organizational
problems
or
issues
at
scale
right
so
like
if
you
have
20
or
30
federated
data,
centers
you're,
probably
running
this
in
production,
for
you
know
a
sizeable
organization.
C
There's
you
know
features
that
we
have
on
that
front.
That
would
help
you
more.
You
know
better
manage
those
federations,
for
example,
but
something
like
metrics
something
like
intentions.
Anyone
from
the
smallest
console
deployment
to
the
largest
console
deployment
would
want
those
things,
so
that's
all
generally
applicable
across
the
board.
A
C
Hopefully,
soon
not
directly
at
the
moment,
I
think
we
have
a
number
of
things
that
we're
we're.
Looking
at,
I
would
say
very
broadly,
it's
you
know
we
are
looking
at
further
improving
our
ux
and
deployment
on
platforms
like
kubernetes
or
even
just
in
general
kind
of
improving.
You
know
the
ux
usability
of
certain
features
that
are
already
exist
within
console,
so
I
think
there
are
some
other
things
we're
looking
at
as
well,
but
you
know
to
be
honest,
we're
currently
in
the
planning
phase
for
the
next
release.
C
C
C
So
if
console
doesn't
bubble
up
something
as
a
first
class
config,
you
have
a
way
to
insert
that
that
configuration
that
you
need,
but
even
that
is
the
ux
around.
That
could
be
a
little
bit
better.
So
I
think
we're
looking
at
you
know
I
would
say
ways
to
improve
some
of
that
ux.
So
if
something's
not
in
console,
you
have
an
easier
way
to
add
those
features,
or
we
also.
C
Yeah,
so
that's
why
it's
kind
of
not
the
most
recommended
it.
It
requires
you
to
know
how
to
configure
envoy
directly
right,
you're
passing
the
an
envoys
json
configure
thing.
So,
if
you're
using
a
filter
or
a
parameter,
that's
deprecated
in
the
next
envoy
release,
then
that's
kind
of
on
you
to
do
the
testing
and
validation
of
that
across
upgrades.
Whereas
when
we
surface
features,
if
there's
changes
to
envoy
config,
like
you
know,
using
a
v2
filter
and
then
going
to
v3
or
changes
in
parameters,
we
would
handle
that
backwards
compatibility.
C
A
A
A
C
Yeah
yeah.
Definitely
please
invite
me
to
know
that
you
know
I've
attended
a
number
of
the
smi
community
meetings
and
personally
try
to
keep
a
pulse
on
just
what's
going
on
with
with
that
community,
and
that
spec-
and
I
know
others
from
hofstra
corp
and
particularly
from
the
console
team-
have
attended
those
as
well.
C
I
know
at
the
moment
we
you
know
console,
has
a
experimental,
sli
controller
and
has
only
really
support
for
the
traffic
spec
or
traffic
access.
I
think
specification
that
they
have
so
it's
fairly
limited,
but
you
know,
I
think,
we're
we're
broadly
trying
to
keep
tabs
on
the
traction
that
smi
is
getting
and
you
know
we'll
look
to
invest
in
it
kind
of
based
off
of
that.
I
think
at
least
for
what
we
see
from
our
user
community
and
from
our
customers
is
in
the
past.
There
wasn't
as
much
interest
in
smi.
C
I
think
it's
starting
to
pick
up
a
little
more,
maybe
part
of
that
other
service
mesh
is
also
adopting
it
and
it
kind
of
gaining
a
little
more
credibility
or
whatever,
if
you
will
but
yeah.
Definitely
please
invite
me
to
that.
You
know
we
would
look.
You
know,
look
forward
to
see
if
there's
opportunities
for
us
to
increase
our
support
for
that.
A
A
C
Yeah,
I
was
actually
just
gonna
comment
on
that,
so
we
are
targeting
around
the
week
of
november.
I
think
12th
or
14th,
so
just
a
couple
couple
weeks
out,
but
it
really
again
depends
on
what
we
uncovered
during
this
testing
period.
There's
already
a
number
of
bugs
or
issues
that
we
identified
so
we'll
have
a
beta
two,
hopefully
sooner
rather
than
later,
and
then
you
know
an
rc
candidate
and
then
ga
is
roughly
the
pattern
we
followed
in
the
past
so
expect
similar
for
this
release.
C
Yeah,
thank
you,
I
mean.
Obviously
I
I'm
just
here
telling
you
about
them
right.
The
credit
goes
to
our
team
and
you
know
a
lot
of
very
talented
folks
who
were
able
to
make
these
things
a
reality,
so
we're
definitely
excited
about
them.
A
lot
of
hard
work
went
into
making
these
and
releasing
them,
and
you
know
we
looking
forward
to
you
know,
hearing
more
feedback
from
our
community
and
obviously
you
know
more
stories
about
how
people
are
actually
using
and
benefiting
from
these.
A
Well,
all
right!
Well,
the
next
item
here
is
is
the
notion
that
there's
an
industry
analyst
firm
amalgam,
similar
to
gartner
451
forester,
had
recently
done
a
well
an
analysis
around
kubernetes
and
inclusive
of
service
meshes
specifically,
and
so
I
thought
I
would
highlight
it
because
we
always
try
to
highlight
the
fact
that
work
that
that
your
that
you
all
are
doing
in
the
community
gets
highlighted,
and
so
we
will.
I
will
work
with
amalgam
to
see
if
we
can
have
a
controlled
distribution
of
the
write-up
which
talks
about
measuring
it.
A
A
Okay,
yeah,
you
know
jesus
is
not
on
so
then
I'll
I'll
mention
what
these
are.
So
it
was
two
weeks
ago,
a
week
ago,
about
two
weeks
ago,
there
was
an
event
held.
This
is
the
second
time
that
we
have
held
this
or
participated
in
this
event
here,
which
is
an
it's.
An
open
source
conference
held
in
well
physically
last
year,
was
held
in
guadalajara
and
this
year
virtually.
A
But
jesus
was
an
attendee
of
the
first
year's
workshop,
which
was
on
istio
and
is
back
this
year,
and
now
he
he
hosted
half
of
the
workshop
this
year,
and
it
was
about
introducing
individuals
to
measuring,
to
go
and
to
react
into
the
technologies
here
and
beginning
to
help.
People
contribute
to
open
source,
and
that
seems
to
have
been
very
successful
because
there
are
any
number
of
pages
in
mesher's
documentation
that
are
now
translated
to
spanish,
which
is
great,
and
so
jesus
was
calling
for
another
translation
working
session
and
so
and.
A
D
A
D
You
all,
and
my
name
is
roloff
martinez.
I
am
from
guadalajara,
mexico
and
this
place
that
calls
event
was
hosted,
and
currently
I
am
software
developer
at
rackspace,
I'm
working
with
golang
and
kubernetes
and
a
little
bit
with
javascript.
So
I
think
that
I
can
contribute
into
the
imagery
project
with
these
languages.
D
A
E
E
A
Nice,
I
know
that's
super
interesting,
yeah
there's,
I
think,
looking
forward
into
the
future
just
a
lot
of
a
lot
of
possibility
there,
particularly
around
exactly
what
you
were
saying.
It's
like
when
you're
able
to
enable
developers
with
ease
you
know
easier
access
to
harness
that
the
power
of
the
network,
like
that
yeah
I'm
getting
excited
just
having
you
talk
about
it,
actually
welcome
thanks
for
jumping
in
a
couple.
What
time
is
it
so
we
got?
You
know
five
minutes
left.
A
D
A
I
was
talking
about
not
exactly
the
same,
but
image
hub
itself
as
a
sample.
App
is
a
rip-off
of
docker
hub,
like
you
know,
intentionally
just
a
a
very
simple
application
that
doesn't
actually
work.
Actually
it
was
I
mean
it,
I'm
sorry,
it
doesn't
actually
do
do
anything.
It's
a
sample
app,
but
but
we'll
talk
about
this
on
the
docker
blog.
Why
was
I
bringing
this
up?
A
A
The
focus
of
this
messaging
isn't
so
much
the
mechanics
by
which
the
messages
are
sent.
That's
already
a
lot
of
that's
grpc,
but
it
is
focused,
probably
around
error
codes
and
ensuring
that
there's
a
central
collection
of
error
codes
that
are
well
described
and
leveraged
consistently
across
each
of
the
components.
A
So
with
that,
I'm
trying
to
think
real
quick
if
we've
got
anything,
we've
got
a
demo
coming
up
from
adolfo
next
week,
we've
got
the
smi
conformance
meeting
to
engage
in
earnestly
and
then
one
other
actually.
So
it's
really
good
that
we
mentioned
this.
There
is
another
specification,
the
smp
spec
that
is
being
advanced
kind
of
in
context
of
the
service
mesh
working
group
inside
the
cncf
and
it's
meeting.
A
But
yeah
good
to
call
out,
because
I
know
that
we're
to
have
a
number
of
newcomers
on
this
week's
on
this
wednesday's
call.
So
I'm
excited
about
more
traction
on
this
spec.
So
anyway,
if
you're
interested
the
meeting
link
and
everyone
anyone's
welcome
to
come,
the
link
to
that
meeting
is
in
the
calendar
that
we
were
showing
earlier.
So
that's
it.
I
think
it's
go
go
forth
and
have
some
candy.
I
guess
nice.
Okay,
thanks
all
well
same
time.
Next
week
talk
to
you
all
soon.