►
Description
Don’t miss out! Join us at our upcoming event: KubeCon + CloudNativeCon Europe 2023 in Amsterdam, The Netherlands from April 17-21. Learn more at https://kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.
Carry Your Legacy Apps Into a GitOps World - Chandler Wilkerson, Red Hat
GitOps promises a future where all infrastructure is code, but what about all these legacy applications that have to be kept running while DevOps teams build that future? Enter two CNCF Incubator projects, KubeVirt and ArgoCD! ArgoCD brings tested code control workflows to bear in managing infrastructure, while KubeVirt introduces virtual machines to the Kubernetes ecosystem. This session will demonstrate using ArgoCD to bring up KubeVirt, and bring virtual machines along for the ride while running a version of Bookinfo with mixed VM and containerized microservices. After this session, you’ll be well positioned to bring even your legacy services into a GitOps workflow.
A
So
kind
of
back
to
the
idea
of
virtual
machines
fitting
within
the
gutops
model-
and
you
know
just
the
fact
that
they
do
have
kind
of
lives
of
their
own.
There
is
there.
There
are
some
things
that
you
can
change
about.
A
VM
live,
but
not
very
many,
and
so
you
know.
Obviously
we
have.
We
check
all
the
boxes,
except
for
the
last
one,
where
we're
reconciling
so
in
the
case
of
the
demo
that
I'm
going
to
run
at
the
end
of
this
I'm
using
Argo,
CD
and
kubert
by
Downstream.
A
So
right
now,
I
ran
my
demo
with
openshift,
and
so
it's
openshift
virtualization
openshift
get-offs,
but
the
reality
is
both
of
those
products
are
under
the
hood.
Just
the
the
downstream
of
an
upstream
Community
in
covert
and
Argo
CD,
so
the
desired
State
being
expressed,
declaratively
is
handled
by
covert
the
state
being
stored,
is
handled
by
Argo
CD
and
pulling
it
automatically
from
The.
Source
I
actually
have
a
GitHub
repo
that
I'll
share
later
now
the
thing
about
the
state
being
continuously
reconciled.
A
We
have
some
things
that
the
virtual
machine
is
going
to
control,
but
not
allow
you
to
change
while
the
virtual
machine
is
running,
and
so
there
there
is
some
intent
on
providing
things
like
memory,
expansion,
and
you
know
hot
plugable
cores
and
things
like
that,
but
it's
just
not
quite
there
within
kubernetes
in
a
way
that
will
make
it
easy
to
do
within
covert
and
so
right.
Now.
All
of
these
resources
are
something
that
are
immutable.
A
Once
you
create
a
virtual
machine,
you
can
actually
you
can
change
them,
but
you
can't
change
them
for
the
running
virtual
machine.
So
the
one
thing
that
we
really
can
get
in
and
reconcile
is
the
state
which
you
can
have
is
running
or
stopped
or
or
actually
several
State
hints,
like
you
know,
run
until
end
and
restart.
A
You
can
run
a
farm
of
virtual
desktops
using
kubernetes
cluster
and
then,
basically
by
you,
know,
kind
of
borrowing,
your
authentication
and
your
disk
space.
From
some
other
network
service.
You
can
run
those
pretty
nicely
ephemerally.
Another
great
example
is
killer.
Coda
killer
code
is
a
group
that
took
over
after
katakota
from
O'reilly
shut
down
and
they
allow
you
to
do
a
quick
deployments
of
virtual
machines
that
either
run
like
Ubuntu
images
or
even
small
kubernetes
clusters
and
they're,
essentially
just
a
quick,
disposable
VMS
for
teaching
scenarios.
A
A
So
the
the
other
side
of
that,
though,
and
the
subject
of
the
talk,
is
when
we're
talking
about
Legacy
applications
and
so
for
a
legacy
VM.
This
is
something
that
is
not
stateless,
you're
going
to
have
some
State
between
runs.
You
may
have
internal
configuration
management
like
through
puppet
or
ansible,
or
something
like
that.
That
maintains
the
state
of
the
virtual
machine
separate
from
what's
going
on
in
the
coupe
cluster
and
as
I'm
hoping
with
the
thrust
of
this
talk.
A
So
with
this
over
here
on
the
left,
we
have
a
Legacy
virtual
machine
and
it's
running
for
services
and
in
interest
of
full
disclosure
I
completely
crib.
This
example
from
the
istio
project.
This
is
their.
You
know
how
to
do
a
service
mesh
in
kubernetes
project
and
they
start
with
microservice
deployments,
and
so
I
went
backwards
to
get
a
nice
demo
and
so
I'm
going
to
be
working
backwards
for
the
for
the
rest
of
the
presentation.
A
So
starting
off
with
the
virtual
machine
that
is
running
all
these
Services,
you
can
put
it
into
the
kubernetes
cluster
and
you
can
and
I'm
realizing
that
I
am
starting
to
overload
things.
So
it's
it's
running
VM
services
on
the
virtual
machine
and
you
have
Cube
service.
Sorry,
kubernetes
Services,
pointing
at
different
aspects
of
the
virtual
machine.
One
of
the
nice
things
about
running
a
virtual
machine
is
a
pot
in
a
pod.
Is
that
you
can
treat
it
as
any
other
pot.
A
A
And
here's
the
front
face
of
the
actual
application
itself,
so
I'll
point
out
a
couple
of
things
on
on
this
because,
as
you
modernize
sometimes
you
also
want
to
you
know,
add
features
and
so
right
now
the
title
of
this
one
is
book
info
Legacy.
You
can
see
here
in
the
very
light
gray
text
in
the
black
bar.
A
We
have
star
ratings
for
for
this
book,
They're
they're,
all
in
black
and
right
now
we
have
just
kind
of
a
generic
publisher,
name,
publisher,
a
and
I'm
pointing
those
out
because
of
course,
I'm
going
to
be
changing
those,
and
so
here's
the
git
Repository
I'll,
just
kind
of
go
through
and
look
at
the
two
tags
that
I
have
and
so
I'm
I
was
running
through
this
demo
and
essentially
I
had
all
the
code
in
the
repository
and
just
in
order
to
record
the
demonstration.
I
just
ran
back
in
time.
A
And,
of
course,
the
Argo
CD
application
is
pointing
at
that
Dev
tag,
so
I'm
going
in
and
I'm
just
doing
a
refresh
and
then
the
rest
of
it's
hands
off.
There's
auto
sync
going
on
and
Also,
let's
see
and
there
you
can
see
that
the
deployment
popped
up
for
the
product
page
and
now
you
can
see
as
soon
as
we
get
a
refresh.
The
name
of
the
page
has
changed
now:
you're
you're
working
from
the
microservice,
but
this
part
this
part
over
here
with
the
details
and
the
stars.
All
those
are
still
on
the
VM.