►
From YouTube: 008 Developer Portal for Istio
Description
A developer portal is a necessary piece of technology when facilitating access to services running in your architecture. In this talk, we'll see how the Developer portal for Istio evolves to support more and more workflows and technologies to enable self-service, policy automation, and API security deep within a mesh.
A
A
I'm
joined
today
with
marco
schmidt,
marco,
is
our
glue
portal
leader.
We
have
a
bunch
of
technical
leads
for
all
our
products,
as
well
as
some
of
our
major
features
of
those
products
and
they
lead
the
team
as
well
as
leading
the
technical
effort.
You
can
find
him
on
the
solo.
I
o
community
slack
at
marco
as
well
we'd
love
to
hear
from
you
please
reach
out.
Don't
be
shy.
A
First,
a
poll
I'd
like
to
learn
a
little
bit
about
your
current
usage
of
glue
and
the
glue
portal.
So
we're
going
to
take
a
few
seconds.
Please
indicate
to
us
if
you're,
currently
a
glue
edge
user
and
a
portal
user
or
number
two,
I'm
currently
a
glue
edge
user,
but
I
don't
currently
use
the
glue
portal
and
number
three.
If
you
don't
use
glue
edge
nor
glue
portal.
If
you're
new
to
solo,
I
o
in
general.
A
Please
choose
number
three
we'll
give
you
a
few
seconds,
and
this
is
pre-recorded,
so
I'm
going
to
feign
surprise
a
few
more
seconds.
Well,
that
was
very
interesting
results.
I
think
that
take
that
back
to
the
product
team,
today's
agenda
for
the
talk
again
we're
going
to
be
talking
about
a
developer
portal
for
istio.
Why
you
need
it?
A
It
is
a
ui.
Don't
get
me
wrong.
There's
an
admin
ui!
There's
a
developer!
Ui
you'll
see
both
those
use
cases
in
both
those
roles,
but
it's
more
than
just
a
ui.
It's
a
kubernetes
native
service.
We
built
it
using
crds
so
that
it
works
with
your
command
line.
With
your
ops
workflow,
with
your
with
your
cooper,
existing
kubernetes
talents,
anything
that
you
can
do
on
a
kubernetes
object.
You
can
do
in
the
portal
in
the
command
line,
our
back
on
environments
and
so
on
and
so
forth.
A
You
heard
a
lot
about
the
rise
of
istio
in
this
conference.
Why
istio
is
so
popular
the
growth
of
istio?
I
want
to
specifically
talk
about
the
rise
of
sdo
in
the
context
of
why
you
need
a
portal
for
istio.
Some
of
you
might
say.
Well,
I
have
istio
on
my
cluster
on
all
my
clusters.
Do
I
really
need
a
developer
portal
for
this?
My
developers
use
the
you
know
the
cli:
they
don't
they
don't
ever
they're,
never
going
to
use
a
ui.
They
don't
need
that
discovery.
A
A
A
Other
common
service
meshes
might
have
other
different
use
cases,
but
istio's
growth
or
command
of
this
market
is
only
going
to
grow,
and
you
see
that
in
the
google
trends
that
red
line,
that
momentum
is
for
istio
as
soon
as
it
dropped
it
just
took
off.
I've
been
in
this
market
again
for
over
six
years,
when
people
were
talking
about
kubernetes
versus
docker
versus
mesos
versus
core
os
fleet
and
a
bunch
of
other
orchestration
tools,
and
you
saw
the
same
type
of
breakout
growth.
You
saw
kubernetes
land.
A
There
was
some
early
adopters
like
myself
and
others
that
were
interested
in
it
and
evangelized
it,
and
it
just
took
off.
So
this
is
istio
that
red
line
versus
some
of
the
competitive,
open
source
initiatives
or
products
out
there-
and
I
didn't
want
to
put
their
names
in
there
because
I
didn't
want
to
drag
them
through
the
mud.
A
But
you
could
actually
see
that
istio
is
by
far
trending
in
the
right
direction
and
we're
obligated
in
every
talk
about
cloud
native
to
have
a
kelsey
hightower
quote
it's
actually
contractually
obligation,
as
well
as
something
that's
just
in
in
the
book
of
cloud
native.
So
I
love
kelsey,
and
these
are
two
great
quotes
of
his-
that
I
just
wanted
to
put
out
there
to
help.
You
understand
and
wrap
your
head
around
istio
in
case
you
don't
use
it
yet,
and
that
is
istio
is
to
envoy
what
kubernetes
is
to
docker.
A
A
You'll
understand
why
you
need
istio
in
comparison
to
to
envoy
one
is
the
basic
building
blocks
for
much
larger
and
grand
system
of
your
distributed
of
your
distributed
system,
and
another
great
quote
that
I
found
of
his
is
istio
is
also
the
glue
it
should
be
glo
between
envoy
and
platforms
like
kubernetes
great
istio
has
one.
Why
do
I
need
a
developer
portal
for
istio?
A
I
have
all
my
services
hooked
up:
they
all
communicate
to
each
other.
They
communicate
in
ways
that
I
never
thought
were
possible.
Mutual
tls.
You
have
cross
cluster
communication.
Why
do
I
need
this
api
management?
Well,
I
have
a
bunch
of
different
services
all
with
different
apis
and
potentially
different
api
types.
A
That's
hard
to
control,
that's
hard
to
break
into
different
different
products
that
I
can
then
show
and
give
to
my
customers,
my
partners
and
my
developers
even
internally,
and
so
you
want
to
be
able
to
catalog
those
apis
in
your
own
branding.
You
want
to
be
able
to
slice
them
and
dice
them
into
whatever
product
and
release
them
or
version
them
in
a
way
that
you
see
fit
based
on
the
environment
based
on
cluster
based
on
the
type.
A
The
next
thing
is
like
you
don't
want
to
always
have
the
developer
coming
to
you
for
apis
or
how
you
you
know
how
you
get
to
them.
What's
the
end
point
and
so
on
and
so
forth,
so
you
want
to
make
it
self-service
for
developers,
you
might
have
developers
outside
of
your
organization
from
partners
or
customers,
and
you
want
to
make
it
so
that
they
could
get
into
the
portal
or
wherever
you're,
keeping
this
catalog
and
start
trying
the
apis
out.
A
B
A
You
want
to
be
able
to
control
the
usage
and
monetization
is
key
for
that.
Now,
there's
going
to
be
a
bunch
of
different
features,
we
talk
about
both
in
past
releases
and
future
releases,
but
this
is
this
is
how
you
can
think
about
why
you
would
want
to
implement
api
management
and
the
developer
portal
for
your
istio
cluster.
It's
really
going
to
accelerate
your
adoption
of
cloud
native
apis
by
by
10x.
A
So
what
is
in
glue
at
glue
portal
for
istio
and
edge
specifically?
Well,
we
have
the
self-service.
We
have
traffic
control,
we
have
authentication,
we
have
open
api
as
well
as
grpc,
which
you'll
see.
Today
we
have
the
custom
branding
and
you'll
see
some
in
that,
although
we'll
use
generic
brands,
the
cloud
native
architecture,
which
I
talked
about,
where
we're
using
kubernetes
crds,
so
that
it
works
with
your
your
existing
skill
set
as
well
as
your
git
ops,
workflow,
and
then
that
istio
and
glue
edge
support
as
well.
A
Let
me
introduce
you
to
the
glute
portal,
your
developer
portal
for
glue
edge
as
well
as
istio.
A
goop
portal
sits
in
front
of
istio.
It
sits
in
front
of
blue
edge
and
you've
heard
about
glue
edge
2.0.
So
all
these
things
are
merging
together
and
it
really
abstracts
that
apis
and
services
from
those
clusters
into
an
easy
to
read
catalog
that
is
self-service
for
your
developers
that
they
could
test
out
those
apis
instantly.
A
If
you
have
sdo
you're
saying
oh,
I
could
already
reach
those
those
services.
I
could
already
reach
those
apis.
Of
course,
you
can
but
putting
a
portal
in
front
of
it,
putting
those
abstractions
a
product,
environment
and
so
on,
helps
you
slice
and
dice
those
services
and
give
it
to
different
users
based
on
their
role,
based
on
whether
they're
a
partner
based
on
whether
they're
internal
developer.
It
helps.
B
A
What
are
the
portal
enhancements
that
you're
going
to
see
today
you're
going
to
see
a
little
bit
of
what
existed
in
the
portal
previous
to
glue
edge
1.7?
A
lot
of
you
are
new.
I
want
to
make
sure
that
you
are
introduced
to
the
portal
in
general,
but
we're
here
also
to
talk
about.
What's
going
to
be
in
the
portal
in
the
next
two
weeks,
we
have
a
release
candidate
for
glue
edge
1.7,
which
is
available
now
go
download
it
test
it
out,
but
also
that
is
going
ga
at
the
end
of
march.
A
Previously
we
supported
api
keys,
we've
expanded
that
and
then
we'll
talk
about
making
your
apis
public
or
require
users
to
log
in
so
that
they
can
read
the
apis,
read
the
documentation,
but
then
actually
to
try
them
out
or
use
them.
You
have
to
require
them
to
sign
in
because
you
want
to,
you
know,
prevent
distributed
denial
of
service
and
other
other
things
with
that.
I
want
to
talk
a
little
bit
about
why
grpc.
A
A
Well
you've
seen
this
with
a
lot
of
technology
development
over
the
years
you
have
something
that
has
been
released.
That
is
getting
a
wide
adoption
and
then
larger
companies
start
to
see
some
of
the
limitations
in
that
wide
technology.
Even
if
it
covers
most
the
use
cases,
there's
maybe
different
ways
you
want
to
do
things
or
different
edge
cases
and
where
better
technology
would
be
more
well
suited,
and
so
that
that's
what
happened,
that's
what's
happening
with
rest,
it's
still
extremely
popular
again.
The
growth
is
not
bounded
in
any
way.
A
You
can
see
more
and
more
rest
apis,
but
you
saw
companies
like
google
and
facebook
think
about
this
a
little
bit
differently
and
want
to
do
it
a
little
bit
differently
and
when
that
happens,
what
tends
to
happen
in
the
market?
Is
that
you
see
this
accelerated
adoption
because
there's
a
much
wider
use
cases
there's
different
ways
of
thinking
about
it
and
just
newer
technologies
that
enable
really
cool
things.
You
saw
this
with
big
data.
You
saw
this
with
containers
when
kubernetes
was
released.
A
A
You
see
them
all
over
the
place,
all
over
aws
and
all
the
cloud
providers,
but
look
at
the
yellow
line
and
look
at
the
red
line
graphql,
which
originally
came
out
of
facebook
to
address
some
of
the
shortcomings
of
rest
as
well
as
grpc
that
came
out
of
google.
You
see
also
that
breakout
growth
of
those
two
technologies
as
well,
so
I
don't
want
to
have
our
users
of
the
portal
choose
between
rest
and
graphql,
graphql
and
grpc.
A
A
We
now
have
grpc
you'll
see
that
today
and
then
tomorrow
the
figurative
tomorrow
will
have
graphql
and
glue
portal.
I
want
to
remind
you
is
not
just
a
developer
portal
for
istio.
It
is,
and
that's
great
and
I
don't
think,
there's
any
other
developer
portal
for
seo,
but
it
is
also
the
only
enterprise
grpc
portal
in
the
market
that
I
know
of
there's
other
open
source
efforts,
but
if
you
want
something
that
has
support
that
has
grpc
next
to
rest,
this
is
the
only
up.
A
B
Okay,
so
I
am
going
to
go
through
a
quick
demo
and
I
I
will
focus
on
how
group
portal
can
help
you
iterate
on
the
design
of
your
apis,
together
with
the
developers
that
consume
them,
and
also
how
you
can
use
it
to
automatically
configure
your
gateway
via
the
istio,
ingress
gateway
or
blue
edge.
So
I'm
going
to
start
the
demo
from
the
perspective
of
the
api
producer,
so
the
administrator
of
glue
portal-
and
I
have
a
kubernetes
cluster
here
with
istio
installed.
You
can
see
that
I
have
my
istio
ingress
gateway
there.
B
I
also
have
glue
portal
installed
and
I
have
deployed
two
simple
applications:
a
rest
application
and
a
grpc
application
so
that
we
can
use
them
as
examples
I'm
going
to
log
into
my
admin
dashboard
and
I'm
going
to
start
by
importing
api
definitions
in
the
system.
So
api
docs,
how
we
call
them
are
the
building
block
for
glue
portal.
These
represent
your
api
specifications
and
I'm
going
to
start
by
defining
a
rest
api
daw.
B
I
have
a
service
that
is
serving
an
open
api
specification
on
an
end
point
and
I
can
point
glue
portal
to
that.
So
that
it
can
automatically
fetch
the
specification
and
parse
it,
and
now
it's
available
in
the
system,
you
can
see
that
we
have
four
operations
here.
The
next
step
is
to
define
an
api
product,
so
an
api
product
is
a
way
of
bundling
internal
apis
together,
so
that
you
can
expose
them
to
your
external
users
as
a
single
homogenous
api
on
which
you
can
apply
policy
uniformly.
B
So
I'm
going
to
call
this
api
product
pet
store,
I'm
going
to
give
it
a
nice
image
that
will
show
up
in
the
portal
and
I'm
going
to
create
an
initial
version.
Let's
really
say
a
working
progress
version,
calling
it
v0,
I'm
telling
the
system
where
to
route
traffic
to
in
this
case.
This
represents
a
kubernetes
service,
I'm
also
going
to
apply
a
custom
label,
a
tag,
working
progress
tag
just
to
show
that
the
api
is
evolving
and,
to
begin
with,
I'm
only
going
to
add
three
operations.
B
Also,
my
service
has
four
available,
we'll
see
in
a
second.
Why
I'm
doing
that
and
my
api
product
is
ready.
So
you
can
see
that
I
have
my
e0
defined
here
and
next
step
to
publish
my
api
is
to
add
it
to
an
environment.
So
an
environment
is
basically
a
domain
that
you're
exposing
on
your
gateway,
and
this
is
where
a
glue
portal
will
start
generating
configuration
for
your
gateway
to
expose
those
routes.
B
So
in
this
case
I
have
two
environments
and
in
an
environment
I
can
apply
policy
to
an
api
so
for
the
integration
environment,
I'm
not
going
to
define
any
off
policies,
because
I
want
users
to
be
able
to
freely
test
the
apis
and
for
the
production
environment.
Instead,
I'm
going
to
enforce
trade,
limited
authentication
policies.
B
B
So
I'm
going
to
add
my
v0
pet
store
to
the
portal
and
then
I
need
to
update
my
user.
So
I
created
a
user
here
to
represent
an
external
developer
and
I
need
to
give
them
access
to
the
api.
So
I'm
going
to
do
that
and
they
already
have
access
to
the
portal.
Okay.
So
now
I
should
be
all
set
to
navigate
to
the
portal
and
switch
to
developer
persona.
B
So
this
is
the
portal
home
page.
You
can
see
that
it
shows
the
styles
that
we
find
here
and
you
can
really
easily
customize
the
portal,
so
I'm
going
to
show
a
simple
example.
So,
for
example,
if
I
want
to
change
you
know
the
color,
the
primary
color
of
buttons,
I
can
make
that
change
here
and
it
immediately
propagates
to
the
ui.
B
So
and
you
can
customize
the
portal
in
a
lot
of
different
ways.
You
can
provide
your
own
custom
style
sheets
so
that
you
can
customize
the
css
of
the
portal
completely.
You
can
add
static,
pages
or
dynamic
pages,
so
you
can
really
make
it
out
to
be
the
portal
that
fulfills
your
needs.
So
now,
let's
log
into
the
portal,
with
the
credentials
that
I've
shared
with
my
developer,
it's
the
first
login.
So
it
will
prompt
me
to
update
my
password
and
once
I've
done,
that
I
can
see
the
api
that
I
just
published.
B
You
can
see
that
you
can
filter
it.
I'll
show
it
when
we
have
a
couple
more
apis,
but
we
can
see
that
we
have
our
three
operations
and
the
developer
can
see
all
the
necessary
information
to
consume
this
api
and
they
can
also
test
it.
So
now,
let's
say
that
I
realize,
as
a
developer,
that
I
also
need
another
endpoint
one
that
allows
me
to
list
all
the
pets
in
my
pet
store
and
not
only
to
retrieve
them
by
id.
B
So
they
would
convey
that
feedback
to
the
api
developer
and
as
a
as
a
glue
portal
admin.
I
can
come
back
to
my
product
and
I
can
define
a
new
version
starting
from
v0
the
blueprint
I
can
create
v1
and
let's
assume
that
the
api
is
going
to
be
stable.
So
I'm
going
to
add
a
stable
tag
and
for
v1
I'm
going
to
add
that
extra
operation
that
I
already
had
included
in
my
service
in
a
real
world
use
case,
you
would
probably
deploy
a
new
version
and
update
your
spec.
B
So
now
that
I
have
defined
my
service,
I
can
update
my
environment
to
publish
that
next
to
my
v0
pet
store.
So
I'm
going
to
add
the
one
rest
pet
store,
and
now
it
should
be
available
in
the
portal
ui.
So
you
can
see
that
I
can
filter
by
the
custom
tags
they
have
defined.
Now,
if
I
try
the
v1
of
my
api,
I
see
the
endpoint
that
I
requested
and
it
allows
me
to
list
all
my
pets.
B
This
was
the
rest
api
and
I
also
want
to
show
the
gopc
api
support
that
we
recently
added.
So
to
that
end,
I
already
created
an
api
doc
that
uses
reflection
to
pull
the
specification
for
my
grpc
service
directly
from
my
service,
so
I
have
reflection,
enabled
and
I'm
able
to
introspect
the
service,
and
you
can
see
that
I
can
detect
all
the
operation
and
also
the
operation
types.
I've
also
already
defined
an
api
product
for
this
service,
so
you
can
see
that
this
looks
very
similar
to
the
rest.
B
So
I've
added
the
grpc
service
and
I
need
to
give
my
user
again
update
my
user
to
give
them
permission
to
see
that
api.
We
don't
want
them
to
accidentally,
have
access
to
something
we
didn't
intend
to,
and
once
I
have
updated
the
permissions
for
my
user,
I
will
be
able
to
see
my
grpc
application
here
again.
I
can
filter
here
in
case
I
have
a
lot
of
apis.
I
can
filter
out
only
the
ones
that
I'm
interested
in
in
this
case.
It's
the
grpc
one.
B
You
can
see
that
how
chris
mentioned
like
the
look
and
feel
is
exactly
the
same.
As
for
the
rest
api,
you
can
see
all
your
services
defined
on
your
server
all
the
methods
defined
for
all
those
services
and
also
you
can
see
all
the
different
types
that
you
need
to
provide
as
inputs
and
that
you
look
at
as
outputs
when
you
execute
a
remote
procedure
call
and
similarly
to
the
rest
api.
I
can
test
the
api,
so
here
I'm
going
to
not
filter.
B
So
I
get
all
my
pets
and
you
can
see
that
I
get
all
my
pets
via
the
grpc
api
as
well.
So
now,
let's
say
that
I
decided
that
the
v1
pet
store
rest
api
is
ready
for
production,
so
I
want
to
promote
it
to
the
production
environment
and
add
authentication
to
it.
So
what
I
need
to
do
is
very
similar
to
what
I
already
did.
I
just
add
my
d1
pet
store
application
to
the
production
environment
and
I'm
going
to
define
what
we
call
a
usage
plan.
B
So
a
user's
plan
is
what
defines
an
often
a
rate
limit
policy,
so
we
already
had
api
key
support.
We
recently
added
oauth
support.
That
means
that
only
api
requests
that
have
a
valid
oauth
access
token
will
be
allowed
to
make
it
through
to
the
api.
So
I'm
going
to
call
this.
Give
this
plan
a
name
basic
auth-
and
I
have
dex
deployed
to
my
cluster
dex-
is
an
openid
connect,
identity
provider
that
implements
the
oauth2
specification.
B
B
B
Okay,
once
again,
once
this
is
done,
I
need
to
go
back
and
update
my
user
to
give
them
access
to
the
new
api
and
also
to
the
usage
plan.
I
need
to
do
this
because
you
can
have
multiple
usage
plans
with
different
policies
and
rate
limits
for
a
single
api,
and
you
might
want
different
users
to
have
access
to
different
rate
limits.
Let's
also
make
sure
that
I
have
published
my
api
to
the
portal.
B
So,
yes,
let's
publish
the
production
api
to
the
portal
as
well.
Okay,
now
switching
back
to
the
developer
persona,
you
can
see
that
now
I
have
a
production
version
of
my
pet
store,
so
I
can
switch
to
using
the
production
version.
Now.
If
I
test
the
api,
you
will
see
that
I
will
get
a
403
error
because
it
didn't
provide
any
credentials.
B
B
This
will
authenticate
the
portal
application
and
now
I
can
execute
a
request
and
get
a
200,
and
at
the
third
request
I
will
get
a
4.29
because
I've
been
rate
limited
according
to
my
usage
plan
now
this
concludes
the
demo.
One
thing
I
want
to
mention
is
that
you
can
the
apis
are
behind
a
login,
but,
as
chris
mentioned,
there's
also
an
option
to
make
the
apis
publicly
available
and
users
will
need
to
log
in
only
to
provision,
credentials
and
yeah.
This
concludes
my
demo.
A
Thank
you,
marco
and
again
everything
that
you
saw
all
done
by
crds.
You
could
do
that
with
your
kidops
workflow,
which
is
cli.
You
really
love
wrangling
with
yaml
until
there
I
don't
want
to
eat
too
much
into
the
question
time.
We
will
take
questions
at
the
end.
We're
going
to
talk
a
little
bit
about
the
roadmap,
though,
because
I
want
to
show
you
all
the
goodies
that
are
coming
for
the
glue
portal
now.
These
are
initiatives
they're,
not
specific
features
that
we're
working
on.
A
You
could
think
of
them
more
as
insights
that
we
gathered
from
our
user
base
and
customers
and
synthesize
this
into
work
streams
that
may
take
several
quarters
or
even
the
entire
year,
but
we
are
working
fast,
so
I
think
you'll
see
most
of
this
by
the
end
of
q2.
The
first
up
is
multi-cluster
support.
This
is
a
widely
requested
feature.
A
This
is
also
something
that
we
are
currently
working
on
right
now,
as
part
of
just
the
larger
effort
to
integrate
with
of
glue
meshes
as
well
as
the
glue
edge
2.0
increase,
increase
api
types.
You
saw
us
adopt
grpc
and
have
a
similar
workflow
in
ux
to
rest
using
open
api
there's
other
api
types
out
there
we
mentioned
graphql
and
there's
a
graphql
go
ongoing
right
now
for
for
glue
edge
and
so
you'll
see
it
dropped
there
first.
A
But
I'd
like
to
get
that
into
the
developer
portal
as
well
monetization.
This
is
something
that
we're
going
to
spend
a
lot
of
time.
Next
quarter
working
on.
We
don't
have
any
modernization
in
the
portal
right
now,
modernization's
a
big
topic.
There's
plans
like
gold,
silver,
there's
usage
plans,
we're
going
to
start
working
on
that
very
soon
and
so
you'll
see
something
dropping
q2
self
service.
We
have
a
lot
of
self
service
capability
right
now
in
the
glue
portal
developers
can
come
in
use
your
idp,
your
existing
idp.
A
You
could
actually
do
a
workflow.
If
you
have
octa
octa,
has
a
self-service
workflow,
so
you
can
set
that
up
with
glute
portal
as
well.
So
all
that
is
is
well
and
good.
There's
some
features
and
some
refinements
and
some
ux
and
some
documentation
that
we'd
like
to
get
around
self-service
to
make
it
easier
for
your
you.
The
user
security-
this
is
a
perennial
topic
for
us.
A
We
are
an
enterprise
company,
we've
delivered
https
in
the
portal,
as
well
as
the
apis,
and
we're
going
to
continue
to
be
very
concerned
about
security,
cbe,
scannings
and
whatnot
as
we
develop
the
product
and
then
expanding
edge
integration.
We
get
a
lot
of
requests
of
the
type
of
I
could
do
this
in
glue
edge.
Can
I
do
this
in
the
portal
and
we'd
like
to
answer
to
that?
To
always
be
yes
or
most
of
the
time
be?
A
This
is
just
another
way
of
looking
at
the
roadmap
broken
down
into
what
we're
delivering
this
quarter.
What
we're
delivering
next
quarter,
we're
very
agile
here,
you'll
see
that
when
you
join
the
slack,
please
join
the
slack.
The
slack
channel
is
specifically
for
portal.
Specifically,
I
take
user
feedback
very
seriously.
If
you
have
a
request,
we're
going
to
try
to
deliver
that
as
as
soon
as
as
soon
as
possible
that
we
could
do
with
our
other
engineering
efforts
going
around.
A
A
Okay.
What's
the
next
steps,
you
love
this
talk,
I'm
glad
to
have
you
here.
What
do
you
do
now?
Go
download
the
new
glue
edge
1.7,
it's
right
now
in
a
release
candidate.
It
will
be
ga
in
a
couple
of
weeks.
Ask
us
for
a
key
and
try
out
the
portal
we'd
love
to
have
your
feedback.
We'd
love
to
you
know.
Have
you
try
out
the
new
features
join
the
slack
channel,
not
just
glue
slack
sorry,
solo
solo.
A
I
o
slack,
go
and
join
the
glue
portal
channel,
specifically
again
we're
very
interactive,
I'm
in
the
channel.
You
could
dm
me
directly
and
I'd
love
to
hear
from
you
a
new
new
to
the
glue
portal
in
general.
You
never
touched
it
or
you
want
to
get
your
hands
on
it.
Another
way
to
do
that
is
through
these
workshops.
We
have
one
at
the
last
day
of
solo
con.
A
If
that
is
full,
which
probably
is
don't
worry,
just
sign
up
for
the
wait
list.
We're
gonna
have
another
workshop.
I
promise
you
and
we'll
invite
you
to
that,
and
you
can
go
to
that
one.
I
think
all
the
workshops
had
like
100
seats
and
they're
they're
all
wait
listed,
but
maybe
some
people
dropped
then
either
way,
just
sign
up
sign
up
for
the
sign
up,
get
what
you
listed,
we'll
we'll
be
in
touch.