►
Description
SoloCon 2022:
[Lightning Talk] Istio Lifecycle Management with Gloo Mesh
Speaker:
Jahvon Dockery
Software Engineer, Solo.io
Abstract:
Dive in to how Gloo Mesh can be used to install and upgrade Istio in your managed clusters.
Track:
Community and Open Source
A
Hi
there
and
welcome
to
today's
lightning
talks.
I'm
rose
savelle
and
I
work
on
community
and
education
here
at
solo.I
o
and
I'm
excited
to
welcome
our
first
lightning
talk
speaker
for
the
day.
So
please
help
me
extend
a
warm
welcome
to
javon
dockery,
who
will
be
sharing
information
about
istio
life
cycle
management
and
glue
mesh
over
to
you.
Javon.
B
Thanks
for
the
introduction,
hello,
everyone,
as
rose
mentioned,
my
name
is
javon
dockery,
I'm
a
software
engineer
here
at
so
I
o
I'm
on
the
blue
mesh
team
and
today
I'll
be
talking
about
seo
life
cycle
management
using
glumat.
Specifically
before
I
talk
about
or
I'm
planning
on
going
into
a
demo
before
I
do
that.
B
I
just
want
to
give
an
overview
what
this
feature
is
and
the
motivation
behind
why
we
built
this
so
the
main
motivation,
as
many
of
you
have
probably
experienced
managing
seo
installation
and
upgrades
it's
pretty
hard
and
the
folks
over
here
at
solo,
really
wanted
to
just
simplify
that
process
for
our
users.
So
one
of
the
big
things
and
one
of
the
big
focuses
we
had
with
creating
this
feature-
was
trying
to
simplify
the
process
for
installing
and
upgrading
seo
for
people
who
are
new
to
seo.
B
So
there's
a
few
complications
with
installing
and
upgrading
seo,
including
the
fact
that
there's
a
few
ways
of
doing
it
there's
a
lot
of
different
configuration
options
that
you
may
have
when
you're
installing
a
co.
I
mean
we
really
wanted
to
make
that
like
introduction
to
sdo
a
lot
easier
for
people
new
to
seo,
but
we
also
wanted
to
maintain
the
ability
for
people
who
are
familiar
with
seo
to
have
as
much
flexibility
in
terms
of
how
they're
configuring
their
installation
using
glue
mask
so
we're
using
a
very
familiar
seo.
B
Installation
api,
the
issue
operator,
which
I'll
talk
about
in
a
little
bit.
But
with
those
two
points,
the
main
thing
that
we
really
wanted
to
do
is
just
abstract
away.
A
lot
of
the
complicated
details
and
processes
around
doing
an
installation
and
upgrade
so
in
the
end.
It
will
essentially
just
look
like
a
user
will
provide
a
configuration
for
glue,
mess,
will
configuration
and
make
sure
it's
installed
in
all
your
designated
clusters,
while
also
providing
some
of
that
flexibility.
As
I
mentioned,
to
configure
seo
in
whatever
way
that
you
would
like.
B
This
side
here
is
just
showing
an
overview
of
like
how
this
works
so
users,
all
of
you,
would
essentially
create
an
issue.
Lifecycle
manager,
custom
resource,
which
is
a
google
maps,
custom
resource
definition
and
you'll
pretty
much
create
that
so
that
the
glue
match
management
server
within
your
management
cluster
can
pick
that
up
what
the
glue
mesh
management
server
will
essentially
do
once
it
has.
However,
many
seo
lifecycle
manager
crs
you've
created.
B
It
will
determine
what
needs
to
be
done
in
each
of
your
workload
clusters,
so
that
can
be
an
installation
that
can
mean
upgrade,
and
then
the
glue
mask
glue
mask
agent
within
all
of
your
workflow
clusters
will
essentially
take
that
installation
specification
and
make
sure
that
it's
installed
within
that
local
cluster.
So
all
the
resources
and
making
sure
that
all
the
configurations
are
set
up
as
well,
and
that
reconciliation
will
just
continue
to
happen.
B
So,
first
I
want
to
show
you
just
I.
As
I
mentioned,
we
have
our
glue
mask
management
server.
So
in
this
case
this
enterprise
networking
agent
in
my
management
cluster,
is
our
management
server.
As
you
can
see,
I
also
have
a
glue
mask
enterprise
agent.
So
that's
the
agent.
I
also
have
that
deployed
in
my
management
cluster,
and
I
have
a
second
cluster
that
I'm
also
using
here
so
within
this
cluster.
B
Specifically,
I
only
have
this
enterprise
agent
and
what
I'm
going
to
do
I'll
show
you
the
configurations
now,
but
essentially
what
I'm
going
to
do
is
I'm
going
to
tell
new
mesh
the
amendment,
I'm
installing
this.
In
my
main,
I'm
going
to
install
this
in
my
management
server.
In
my
the
glue
mesh
name
space
and
I'm
essentially
saying
I
want
to
install
in
my
remote
cluster,
to
simplify
this
process,
I'm
only
going
to
install
assuming
my
remote
cluster
and
I'm
going
to
provide
two
separate
types
of
installation.
B
B
And
once
you
apply
that
in
your
cluster,
we
will
make
sure
that
we're
updating
so
we'll
see
once
that's
applied.
We
can
see
if
this
was
actually
accepted
by
blue
mesh.
One
neat
thing
about
what
we're
doing
here
with
managing
we.
We
can
see
the
stages
accepted.
We
see
the
tag
and
everything,
but
one
neat
thing
that
we're
doing
before
or
before
we
try
to
do
the
installation
process
is
we're
trying
to
validate
some
of
the
configuration
that
you
pass
in.
B
So
one
nice
thing
that
we
can
do
now
is
folks
here
at
solo,
have
learned
a
lot
of
best
practices
like
separating
your
gateways
from
your
control
plane.
So
if
we
do
see
some
of
those
things
like
you're
installing
your
gateway
alongside
your
control
plane
in
the
same
as
the
operator
spec
will
give
you
well,
this
will
not
be
accepted,
we'll
reject
it
and
we'll
give
you
a
message
saying
like
hey,
you
should
break
those
out.
B
B
One
thing
to
note
is
for
our
patch
upgrade
so
going
from
1114
to
111.7.
We
are
essentially
doing
an
in-place
upgrade
we'll
talk
about
carry
upgrades
in
just
a
second,
but
that's
something
that
can
also
be
overwritten.
If
you
don't
want
to
do
in
place,
upgrades
for
your
patch
upgrades
or
any
of
these
small
changes,
but
we
can
see.
B
B
Yep
we
can
see
that
we're
now
using
one
eleven
seven
and
this,
as
I
mentioned
it,
upgraded
that
version
in
place.
If
I
do
want
to
say,
if
I'm
doing
a
minor
upgrade,
so
I'm
going
from
111
to
seo
version,
112.
googmesh
will
be
able
to
determine
that
based
off
of
what
change
you
made.
As
I
mentioned
to
this
issue
operator,
so
I'm
going
from
111.7
now
I
want
to
go
to
1
12
istio.
B
B
But
yeah
so
we're
keeping
track
of
the
state
of
the
canary
insulation,
and
then
we
also
have
our
active
installation.
So
with
this
change,
we
did
not
make
any
changes
to
anything
for
our
previous
installation.
We
pretty
much
just
created
a
another
installation
right
alongside
your
111
installation
for
our
112,
and
we
should
be
able
to
see
this
now.
I
think
it
should
have
been
enough
time.
B
If
we
get
all
of
our
deployments,
you
can
see
we
have
our
111
ingress
gateway
and
our
111
cod,
alongside
of
our
112
ingress
gateway
and
cod,
and,
as
I
mentioned
with
our
installation
process,
we
are
making
sure
that
pretty
much
as
you
make
changes
to
your
seo,
lifecycle
manager
we're
determining
what
type
of
upgrade
we
need
to
do.
But
if
you
want
there's
additional
configuration
options,
you
can
provide
on
your
seo
lifecycle
manager
to
force
it
to
always
use
canary
upgrade.
B
Getting
a
little
close
to
time,
so
I'm
going
to
switch
over
back
to
this
presentation
to
just
talk
about
what's
coming
in
the
future.
For
this
feature,
so
currently,
as
you
saw,
we
can
do
an
up
installation.
We
can
do
patch
upgrades
minor
version
upgrades
also,
if
you're
changing
configurations
within
your
su
operator,
spec,
all
those
things
will
be
cascaded
and
also
handled
by
this
upgrade
process.
Some
of
the
configuration
changes
might
trigger
a
canary
upgrade
some
might
just
be
in
place.
B
So
if
you
already
have
installed
seo
on
a
cluster,
you
can
you'll
in
the
future,
be
able
to
use
glue
mask
to
upgrade
that
that
version
of
sdo,
using
the
same
configuration
that
you
already
have
installed
in
your
cluster,
so
say
you
use
this
steel
cutter
to
install
111
in
the
future.
You
should
be
able
to
bump
up
to
sto112
using
blue
mesh,
and
all
your
configurations
will
try
to
discover
all
your
configurations
we'll
make
sure
that
we're
validating
that
all
with
you,
of
course,
but
glue
mesh
will
completely
handle.
All
of
that.
B
I
o
production
profile
and
then
that's
all
that
you'll
have
to
specify,
since
the
that's
the
hope.
So,
as
I
mentioned
early
on,
we
really
just
want
to
simplify
this
process
for
people,
but
also
you'll
still
even
with
those
profiles,
as
you
may
know,
you'll
still
be
able
to
have
that
flexibility
of
configuring
things
more
specifically
outside
of
that
scope.