►
From YouTube: Using Red Hat Advanced Cluster Management and OpenShift GitOps to manage OpenShift Virtualization
Description
Learn about how you can use Red Hat Advanced Cluster Management and OpenShift GitOps to manage OpenShift Virtualization with Felix Matouschek.
Check out the key links below.
Blog: https://cloud.redhat.com/blog/using-red-hat-advanced-cluster-management-and-openshift-gitops-to-manage-openshift-virtualization
Advanced Cluster Management Documentation: https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.7
GitOps Documentation: https://docs.openshift.com/container-platform/4.13/cicd/gitops/understanding-openshift-gitops.html
Link to all manifests: https://github.com/0xFelix/gitops-demo
OCM Docs in regards to placement decisions: https://open-cluster-management.io/concepts/placement/#placementdecisions
A
Hello
and
welcome
to
the
video
version
of
the
using
Red
Hat
Advanced
cluster
management
and
openshift
gitups
to
manage
openshift
virtualization
block.
My
name
is
Felix
matoshek,
whether
you
want
to
separate
your
testing
and
production
environments,
improve
the
availability
of
your
applications
or
bring
your
openshift
clusters
to
the
edge
working
with
the
multi-cluster
environment
is
the
key
in
achieving
those
goals.
A
However,
managing
your
clusters
and
applications
at
scale
can
be
a
challenging
task.
Ideally,
there
is
a
single
source
of
Truth
which
determines
the
configuration
and
workloads
of
each
cluster
openshift.
Git
Ops
enables
you
to
do
that
by
storing
your
configuration
in
git
repositories
and
keeping
all
of
your
clusters
in
sync
automatically
did
you
want
to
manage
your
openshift
virtualization
virtual
machine
workloads
across
multiple
clusters,
while
using
a
single
source
of
truth
that
you
get
UPS
way?
This
video
will
show
you
how
you
can
do
that
with
red
hat
Advanced,
cluster
management
and
openshift
githubs.
A
So
what
is
Red
Hat,
Advanced
cluster
management
or
short
ACM
ACM
simplifies
the
management
of
multiple
clusters
by
offering
end-to-end
management,
visibility
and
control
of
the
whole
cluster
and
application
life
cycle.
It
acts
as
a
central
point
for
keeping
an
inventory
of
all
your
clusters
and
applications
and
enables
multi-cluster
and
multi-cloud
scenarios
such
as
deploying
the
same
application
across
clusters,
different
regions,
possibly
in
several
Cloud
providers.
A
It
uses
the
Hub
and
spoke
architecture
and
allows
the
targeted
distribution
of
kubernetes
manifests
across
clusters.
Before
we
go
on.
Let
me
explain
what
Hub
and
manage
clusters
are
The
Hub
cluster
is
the
cluster
on
which
ACM
is
running
on
it
acts
as
an
inventory
and
carries
out
all
management
actions.
A
It
is
usually
not
running
any
actual
workloads,
though,
still
possible.
This
run-on
managed
clusters
manage
clusters
are
kept
in
the
inventory
of
the
Hub
cluster.
They
can
be
created
and
added
to
the
inventory
directly
through
ACM.
Alternatively,
existing
clusters
can
be
added
to
the
inventory
as
well,
for
more
information
have
a
look
at
the
ACM
documentation.
A
While
changes
to
a
cluster
will
be
automatically
reverted
to
the
state
described
in
a
single
source
of
Truth
Reddit
openshift
get
Ops
is
ACI
CD
delivery
platform.
It
enables
declarative,
github's
workflows
and
allows
to
deploy
applications
on
demand.
It
monitors
the
live
state
of
clusters
against
the
desired
State
and
git
repository
and
keeps
them
in
sync.
A
It
builds
on
the
Argo
CD
project.
Therefore,
the
terms
openshift
kit,
Ops
in
agrocity
might
be
used
interchangeably
for
more
information.
Have
a
look
at
the
getups
documentation,
one
more
thing
before,
starting
with
the
demo.
Let
me
give
you
a
quick
primer
about
the
application
and
application
set
crds.
A
The
Argo
CD
application
is
a
custom
resource
definition
which
essentially
describes
source
of
manifests
in
the
Target
cluster
to
apply
the
manifests
to.
Besides
that
options
like
automatic
creation
of
namespaces
or
the
automatic
revert
of
changes
can
be
configured,
the
Argos
CD
application
set
is
the
crd
building
on
Argo
CD
applications
targeted
to
deploy
and
manage
applications
across
multiple
clusters,
while
using
the
same
manifest
or
Declaration.
A
It
is
possible
to
deploy
multiple
application
sets,
which
are
contained
in
One
Mono
repo.
By
using
generators,
it
is
possible
to
dynamically
select
a
subset
of
clusters
available
to
argocd
to
deploy
resources
to
in
this
demo.
We
are
going
to
use
application
sets
to
deploy
openshift,
virtualization
and
virtual
machines
to
multiple
clusters,
while
using
the
same
Declaration
of
resources
for
all
clusters
for
more
information
on
application
sets
see
the
Argo
CD
documentation.
A
A
A
A
A
A
Please
note:
Azure
works
for
this
demo
scenario.
Only
nested
virtualization
is
not
supported
in
production
environment
because
one
cluster
is
not
enough.
I'm
going
to
create
another
cluster,
just
repeating
those
steps
go
to
create
cluster
again,
click
on
azure
enter
the
name
of
the
second
cluster.
This
time
suffixing
it
with
a
dash
2.
A
A
A
A
A
Now
that
we
have
successfully
created
the
managed
cluster
set
binding,
we
need
to
create
a
placement
to
let
ACM
decide
which
clusters
should
be
made
available
to
githubs
for
the
sake
of
Simplicity.
The
placement
we
will
create
will
select
the
whole
manage
cluster
set,
but
at
once
use
cases
are
possible,
run
the
following
command
to
create
a
placement.
A
A
A
A
A
Now
that
we
have
assigned
our
clusters
to
environments,
we
can
finally
start
and
deploy
applications
to
them.
First,
let's
go
back
to
the
applications
list.
You
can
see
it's
still
empty.
No
applications
were
created
yet
openshift
virtualization
will
be
the
first
application
we
will
deploy
to
each
managed
cluster
with
the
help
of
an
application
set.
A
A
A
A
As
you
can
see,
two
new
applications
are
created
notice
how
the
health
state
of
the
created
applications
is
suspended.
This
is
because
the
created
virtual
machines
are
still
in
a
stopped
state
to
get
our
newly
created
applications
into
a
healthy
State.
We
need
to
start
the
virtual
machines
by
making
a
change
to
our
Repository
before
we
start
our
virtual
machines.
By
making
a
change,
let
me
quickly
explain
the
difference
between
the
virtual
machine
and
the
virtualization
applications.
A
Customize
allows
to
apply
customizations
to
an
application
depending
on
the
environment,
a
managed
duster
belongs
to
in
this
demo.
We
are
using
the
environments
we
assigned
our
managed
clusters
to
earlier
to
choose
the
right,
customize
overlays,
the
dev
and
the
prod
overlay
prefix
names
of
created
resources
accordingly.
A
A
A
A
The
application
is
synced
and
healthy.
Now,
and
the
virtual
machine
is
finally
running.
Let's
go
back
to
the
applications
View
and
see
how
all
applications
are
healthy
and
sync,
now,
finally,
to
verify
that
the
virtual
machines
are
running.
Let's
go
to
the
UI
of
one
of
the
managed
clusters
and
have
a
look
at
the
virtual
machine.
A
A
Acm
can
dynamically
select
a
subset
of
clusters
from
the
manage
cluster
set,
while
following
a
defined
set
of
criteria.
This,
for
example,
allows
to
schedule
virtual
machines
on
clusters,
with
the
most
resources
available
at
the
time
of
the
placement
decision
more
on
this
topic:
CD
open
cluster
management
documentation.
A
Now
that
the
demo
is
concluded,
let
me
give
you
a
quick
summary
of
the
things
we
did
in
this
demo.
We
set
up
a
hub
cluster
and
two
clusters
managed
by
ACM
to
deploy
applications
to
from
a
centralized
management
point,
as
example,
applications
we
deployed
openshift
virtualization
with
simple
manifests
and
a
virtual
machine
with
manifests
customized
by
customized.
A
A
This
is,
of
course,
only
the
tip
of
the
iceberg.
Building
on
this
setup
allows
you
to
customize
your
application,
sets
for
different
environments
like
development,
staging
and
production,
or
to
schedule
your
applications
based
on
custom
criteria,
for
example,
available
resources
with
advanced
placement
rules.