►
From YouTube: How to Install and get started with Red Hat Advanced Cluster Management for Kubernetes (ACM)
Description
In this stream, we will walk through how to install and do the first configuration for Red Hat® Advanced Cluster Management for Kubernetes (RHACM) on Red Hat OpenShift Container Platform.
Red Hat Advanced Cluster Management for Kubernetes includes capabilities that unify multi-cluster management, provide policy-based governance, and extend application lifecycle management. Extend the value of Red Hat OpenShift by deploying apps, managing multiple clusters, and enforcing policies across multiple clusters at scale.
0:30 Introduction
6:13 Slides Start
6:41 Hybrid / Multi Cloud Management is Hard
8:16 Kubernetes Adoption Leads to Multicluster
9:43 Where is the Growth in Cluster Deployments?
13:13 Reasons for Deploying Clusters
14:42 Multicluster Management Challenges
16:41 Key Personas
18:40 Introducing Red Hat Advanced Cluster Management (RHACM)
21:28 Unified Multi-Cluster Management
24:08 Policy Based Governance, Risk and Compliance
25:42 Advanced Application Lifecycle Management
26:54 Benefits
30:57 Architecture
35:55 Installation and Foundation
40:20 Role-Base Access Control
41:05 Slides End
41:06 Demo Start
43:07 Deploying through OperatorHub
47:24 Creating a Secret (Before Creating MultiClusterHub)
50:28 Create MultiClusterHub
57:44 Logging into RHACM
59:45 Creating a Cluster through RHACM (AWS provider)
1:08:48 Importing a Cluster
1:12:36 Applications in RHACM
1:21:08 Finishing Importing a Cluster & Reviewing the cluster
1:26:39 Multi-Cluster Application
1:28:44 Policy & Security (Governance & Risk)
1:30:33 Creating a Policy
1:36:23 Viewing Rule Violations
1:38:00 Visual Web Terminal
1:40:25 Search (Visibility)
1:44:26 Overview Page & Topology
1:45:45 Demo End & Closing Information
1:53:48 Q&A and Discussion
A
And
welcome
back
to
another
livestream
I
am
Chris
short
again
principal
Technical
Marketing
Manager
at
Red
Hat's
on
the
OpenShift
team.
I
am
joined
this
stream
by
the
one
and
only
the
very
heart
to
end
down
Jimmy
Alvarez
from
the
ACM
team.
The
advanced
cluster
management
team
here
at
Red
Hat
Jimmy.
Do
me
a
favor,
introduce
yourself
to
the
folks
to
tell
us
SOLAS.
You
know
your
background
a
little
bit
and
why
you're
the
right
person
to
talk
to
us
about
this
yeah.
A
B
Excellent
all
right!
Well
so
hello,
everybody
and
welcome
very
excited
to
be
here
and
be
doing
this
with
Chris,
be
hearing
very,
very
good
things
about
these.
These
two
extremes
so
pretty
excited
so
yeah.
As
Chris
said,
my
name
is
Jimmy
Alvarez
and
I
am
a
principal
product,
marketing
marketing
manager,
here,
Red
Hat,
a
hundred
percent
focus
on
Red
Hat,
advanced
management,
advanced
cluster
management
for
kubernetes.
So
we
have
some
pretty
good
stuff
for
you
today.
B
We're
gonna
walk
through
some
stuff.
We're
gonna
go
through
the
set
up,
so
you're
gonna
watch
me
kind
of
go
through
the
installation
of
the
product
and
we'll
talk
through,
hopefully,
some
of
the
some
of
the
things
that
are
kind
of
going
through
in
the
background
and
that
you
guys
kind
of
feel
it
and
see
it
and
then
we'll
go
and
configure
a
cluster
we'll
build
a
cluster
grenades
cluster
on
AWS
through
a
cm
of
course,
and
then
and
then
finally,
I
think
we'll
configure
some
applications.
A
So,
like
there's
I
mean
so
to
to
give
people
a
context
of
like
my
background
with
the
product.
So
far
is
I
participated
in
a
test
athon
little
more
than
a
month
ago.
I
feel
like
now.
Of
course,
it
was
healing
yeah
days
feel
like
years
now,
but
whatever
yeah,
so
the
attesa
thon
right
like
was
super
fun
for
me,
because
it
was
my
first
time
getting
hands
in
the
product.
Everybody
expected
there
to
be
bugs
and,
and
we
got
to
find
them,
we
got
to
identify
them.
A
We
got
to
help
fix
them
and
it
was
super
cool
and
super
entertaining
but,
like
my
eyes
were
like
boom
the
whole
time
I
was
playing
with
the
product,
because
I
just
saw
so
much
potential
and
all
the
things
you
can
do
and
there's
really
I
feel
like
I,
probably
more
than
just
three
facets
to
the
product,
but
like
three
big
pieces
of
the
product
right
like
there's
that
security
and
compliance
piece
right,
you
can
just
flip
a
switch
and
check
furnace
compliance.
I
feel
like
that's
pretty
cool
there
right.
It's
it's
huge.
It's.
B
B
That's
that's
in
our
policy
engine
is
very
flexible.
That's
the
biggest
thing
to
where
you
can
let
your
imagination
kind
of
wrong
while
and
you
can
create
policies
that
might
just
apply.
There
might
not
be
a
standard,
but
they
might
apply
it
to
your
organization
to
your
specific
needs
right.
That's
when
it
really
becomes
becomes
really
really
big
awesome,
so
kind
man,
yeah,
so
I'm
gonna
go
ahead
and
share
my
screen.
You
know,
I
have
a
couple.
Slides
I
know
that
most
people,
probably
like
oh
no
slice
with.
B
Listen
when
we're
when
you're
building
a
house,
so
you
just
don't,
go
and
build
a
house
right.
You
need
to
have
a
foundation
for
that
house.
This
is
the
foundation
there.
You
go
all
right,
so
I
got
a
few
things
here.
You
know
don't
mind
this
agenda,
it's
very
fluid
right,
but
we'll
go
through
it.
So
the
first
thing
that
we
want
to
kind
of
talk
a
little
bit
about
is
the
market
rents
right?
So
we
kind
of
touch
a
little
bit
on
this
earlier
when
we
were
talking
with
Chris.
But
you
know.
B
Obviously
you
see
the
trend
is
multi-cloud
being
able
to
have
the
ability
to
have
multiple
workloads,
whatever
they
might
be
in
your
data
center
or
whatever
it
might
be
on
another
of
prime
data
center
that
you
have,
or
even
in
the
public
cloud.
Obviously
we're
seeing
the
trend
is
it's
it's
it's.
It
has
been
doing
this
for
years.
This
is
not
even
just
like
a
you
know.
Containers
thing
this
is
just
you
know,
workloads
issue.
We
live
where
you're
able
to
kind
of
have
multiple
workloads
everywhere
and
being
able
to
manage
them
becomes
really
complex.
B
We
talked
about
you
know,
being
able
to
manage
these
and
have
standards
of
policies
across
all
of
them.
It's
also
complicated
right.
You
can
kind
of
see
here.
Some
of
these
results
from
the
survey
that
are
these
IDC
did
pre
coded.
This
is
2019.
These
numbers
are
probably
even
bigger
now
considering
all
of
this
situation
right,
as
we
all
know,
we're
all
working
from
home,
we're
all
you
know
there
is
this
trend
now,
where
you
know
more
and
more
stuff
being
moved
into
the
cloud
so
yeah
we
need
to
have.
B
B
So
you
know
whatever
those
might
be
for
disaster
recovery,
whatever
it
might
be
for
going
into
production,
it
doesn't
really
matter
they're.
You
know
the
trend
is
they're.
The
adoption,
obviously
of
kubernetes
is,
is
increasing
right,
kubernetes,
certainly
new
technology.
Around
since
2014
right,
I
mean
six
seven
years
now
right,
but
obviously
I
think
that
now
we're
starting
to
see
that
shift
from
like
Oh
is
the
wild
wild
west.
Everybody
can
do
whatever
they
want
with
her
with
the
kubernetes
deployment.
So
now
we're
starting
to
see
where
we
need
more
stanzas
around
it
right.
Yeah.
A
C
B
Exactly
exactly,
obviously,
you
know
it's
more
and
more
people,
it's
an
adoption
thing
right.
Obviously
it
reminds
me
a
lot
of
virtualization.
First
photography
came
around
it's
the
same
thing.
If
you
really
think
about
it,
if
you
eliminate,
you
know
the
fact
that
you
have
you
have
kubernetes,
you
have
virtualization,
you
have,
you
know
bare
metal,
you
know
probably
cloud
whatever
right.
The
problems
are
the
same
on
the
on
the
line.
Everything
is
exactly
the
same.
B
A
A
C
B
Exactly
and
and
and
you
know,
you
can
kind
of
see
that
in
in
this
slide
right
here
right,
so
so
you
can
kind
of
see
where
we're
kind
of
seeing
that
growth
within
the
cluster
cluster
deployments
right,
usually
everything
especially
with
kubernetes,
starts
from
a
deaf
team
right.
So
it
starts
with
a
need
from
a
developer
that
hey
I
need
to
build
this
application,
but
I
don't
want
to
go
through
and
wait.
You
know
a
week,
sometimes
a
month
to
get
an
infrastructure
to
be
able
to
deploy
this
right,
so
they
start
looking
for
alternatives.
B
What's
so
easy,
you
can
go
too
easy
to
sign
up
with
a
credit
card.
You
can
go
and
provision
kubernetes
clusters
all
day
right
or
you
can
do
also
a
virtual
machine,
whatever
you
can't
whatever
you
want,
but
obviously
you
can
kind
of
see
that
the
trend
starts
from
here
and
then
it
starts
moving
into
like
you
know,
oh
you
know
they
start
seeing
the
value
right.
So
then,
okay!
Well,
how
do
we
get
some
of
this
into
the
QA?
B
So
we
can
make
sure
that
before
we
go
into
production
right,
but
this
the
the
hesitation
from
a
lot
of
folks
is
going
from.
You
know
Devon
test
to
prod,
with
some
of
these
workloads
same
thing
that
we
saw
for
virtualization
again.
Is
it's
a
been
in
the
industry?
For
a
very
long
time,
I
saw
the
beginning
of
a
virtualization.
You
know,
as
a
matter
of
fact,
that
was
right
up
on
the
up
front
of
it.
B
You
know.
Obviously
there
are
multiple
reasons
why
you
want
to
kind
of
the
ploy
clusters
right.
We
talked
a
little
bit
about
these
right.
Anything
you
know
from
from
reducing
latency
to
application
availability
to
even
a
boy
vendor
locked
in
right.
This
is
a
big
big
topic
that
has
been
coming
more
and
more
and
more
right,
so
being
able
to
avoid
having
that
logged
in-
and
this
is
one
of
the
beauty
things
with
with
Red
Hat
right
being
that
we're
open
source,
you
know,
makes
things
a
lot
easier.
B
You
know
edge
deployments
right,
I
talk
a
lot
with
telcos.
This
is
their
next
big
thing.
Five
g
5g
was
it's
it's
a
very
much
evolving
technology
right
now.
You
need
a
lot
of
repeaters
everywhere
to
be
able
to
kind
of
even
remotely
get
people
close
to
those
speeds.
That
means
a
lot
of
little
deployments
everywhere,
right
with
with
kubernetes
clusters
running
on
the
background
running
those
workloads
right
for
those
towers
and
and
you're
gonna
need
a
lot
of
them,
so
the
edge
deployments
are
something.
B
That's
that's
again
we're
seeing
a
huge
uptake
on,
so
you
can
kind
of
see
here
some
of
these
obviously
disaster
recovery,
that's
something
that's
been
around
for
a
very
long
time.
You
know,
obviously,
a
lot
of
folks
go
through
that
as
well,
so
you
can
kind
of
see
all
of
all
of
these
kind
of
reasons.
Right-
and
so
you
know,
the
idea
here
is
is
to
you
know:
a
cm
can
help
you
with
your
deployments
with
doesn't
matter
what
state
you're
in
you
can
be
of
your
across
the
spectrum
yeah.
B
It
helps
you
across
the
spectrum.
You
can
just
be
like
hey
Liss,
and
I
have
you
know
five
six
clusters.
I
want
to
be
able
to
manage
them
in
a
single
point.
You
know
glass,
I
want
to
be
able
to
do
upgrades
I
want
to
be
able
to
just
just
manage
them.
We
can
help
you
there
right
that.
That's
we.
We
call
this.
B
The
crawl
walk
run
approach
right
where,
regardless
of
whatever
you
are
in
the
stage
right,
wherever
you
are,
the
developer,
just
kind
of
looking
for
you
know
having
all
your
clusters
and
being
able
to
kind
of
provision
them
and
manage
them
quickly
to
having
a
more
complex
environment
where
you're
starting
to
put
stuff
into
production
right,
and
you
want
to
have
policies
that
are
being
in
force
and
application
deployments
that
are
being
properly
done
to
the
final
you
know
and
all
stage,
which
is
the
hayver
multi-cloud
right.
That
is
the
and
all
like
hey.
B
B
A
B
C
B
B
Of
what
you
call
it,
regardless
of
what
you
call
it,
these
problems
are
the
same.
So
so
you
could
kind
of
see
that
trend
right.
So
we
talk
about
it
as
as
different
personas
right.
We're
trying
to
break
this
down,
because
obviously
different
personas
within
the
organization's
are
gonna,
have
different
needs
for
the
product.
So
you
know
in
the
case
sort
of
IT
operations
so,
like
a
knock
or
you
know
a
devops
persona
right
that
is
actually
looking
at
managing
those
clusters.
B
How
do
these
are
the
questions
that
they
ask
like
how
can
I
manage
these
clusters?
How
can
I
get
to
a
root
cause
of
a
problem
if
I
have
a
problem
right?
How
do
I
monitor
usage
right?
So
these
are
some
of
the
questions
that
they
that
that
these
personas
can
I
usually
kind
of
go
through
when
they
talk
about.
You
know
implementing
something
like
this
mm-hmm
from
an
SRE
perspective.
They
don't
care
about
monitoring,
they
don't
care
about
managing
those
clusters.
They
don't
care
about
that.
B
They
just
want
to
simplify
seeing
their
application,
how
they
can
manage
that
application
easier,
how
they
can
promote
code,
easier
right
and
and
basically
get
their
there
develop
and
much
more
accelerated
right
then
than
it
is
today.
So
that's
usually
what
the
Sree
kind
of
DevOps
persona
looks
like,
and
the
setups
persona
is
more
looking
at
the
security.
So
we
talked
a
little
bit
about
this
right.
The
the
security
persona
is
probably
the
least
liked
persona
within
an
organization,
because
it's
the
one,
that's
always
like.
Well
that
binary.
A
B
A
A
B
B
Yeah
regard
yeah,
nope,
nope
and
we've
seen
it
time
and
time
again
throughout
the
years
right
and
that's
more
organizations
kind
of
moving
to
the
cloud.
That's
the
biggest
concern
right.
What
happens
to
my
data?
What
happens
if
somebody
hacks
me
what
what
happens
right
so
this
is
why
it's
important
to
have
those
standards,
and
so,
with
all
of
that
said,
let's
talk
a
little
bit
about
advanced
cluster
manager
for
kubernetes
and
how
we
can
help
kind
of
solve
some
of
these
problems,
so
Chris
cannot
allude
to.
B
Obviously
we
have
the
three
main
use
cases
that
we
look
at.
We
try
to
simplify
this
and
make
it
as
easy
as
possible.
We
understand
that
what
we
see
having
you
know
it's
yet
another
product
to
have
within
your
data
center
is
yet
another.
You
know
thing
so
we
want
to
kind
of
simplify
it,
obviously
kubernetes
in
the
kinetics
technology.
It's
all
about
simplification
right,
it's
all
about
simplifying
work,
clothes.
It's
all
about!
You
know
kind
of
maximizing
your
resources
right.
B
We
want
to
do
the
same
with
this
product,
so
we
look
at
three
things:
the
multi
cluster
lifecycle
management,
the
policy
driven
governance
and
security
and
the
application
lifecycle.
So
we
talked
a
little
bit
about
all
of
those,
so
we'll
go
deeper
into
these.
The
thing
to
know
here
is
that
we
are
currently
tech
preview.
This
product
will
be
going
G
a
very
very
shortly
within
the
next
month.
B
A
B
Right
exactly
right,
so
so
that
you
know
we
just
wanted
to
make
sure
that
when
I
came
in
here,
I
had
enough
meat
in
the
bones
to
kind
of
give
you
guys
right.
That's
that's!
That's
the
pin
down
comment
so,
and
so,
if
we
look
at
you
know,
if
we
look
at
the
these
use
cases
and
we
start
diving
a
little
bit
deeper
right,
so
the
unified
multi
cluster
management,
as
the
name
States,
it's
all
about
having
the
centralized
location
where
you
can
have
all
of
your
kubernetes
clusters.
B
B
Obviously
you
know
the
best
functionality
comes
with
openshift
right
now
we
see
openshift
and
ECM.
Working
together
is
the
ultimate
the
ultimate
experience.
But
if
you
already
have
invested
in
some
of
these
older
open-source
kubernetes
clusters,
right,
like
like
I,
said
like
chicky
as
a
yes
eks,
there's
so
many
of
them
right,
you
can
have
them
out
there
and
you
can
manage
them
with
this
solution.
You
can
at
least
have
them
in
a
centralized
place.
You
can
look
at
them.
You
can
go
and
sort
through
resources
and
move
applications.
A
And
it's
it's
and
it's
important
to
point
out
right,
like
you
know,
OpenShift
runs,
you
know,
OpenShift
for
four
runs
on
this
runs.
This
version
of
kubernetes
eks
runs
that
version
of
kubernetes
IKS
runs.
Another
version
of
kubernetes
gke
runs
yet
another
version
of
kubernetes.
I
don't
think
there's
alignment
in
any
of
those
right
now
and
you
know,
having
you
know
the
capability
to
say
like
I
need,
you
know
kubernetes,
117
or
higher
because
of
this
application,
or
this
workloads
you
know,
needs
like
this
will
help
you
with
that.
B
So
like
FISMA,
NIST,
PCI
right
having
all
of
those
standards
out
of
the
box,
it's
a
huge,
huge
thing,
yeah,
a
matter
of
fact.
I
can
tell
you
with
confidence.
No
other
management,
kubernetes
management
product
out
there
does
this.
We
are
the
only
ones
right
now
that
have
this
type
of
visibility
into
the
policies.
B
B
Right
by
a
standard
right,
exactly
which
again,
it
kind
of
it
kind
of
just
furthers
the
problem
into
once.
Again,
you
you,
don't:
have
your
standards
you're,
just
kind
of
going
down
the
same
circle
again
right,
so
you're
gonna
come
back
to
that
same
spot
again,
because
that
security
person
is
gonna,
be
knocking
on
your
door.
Saying:
hey,
guess
what
these
policies
are
you
putting
in
place,
not
standards?
B
Once
you
already
build
it
right
being
able
to
kind
of
refer
back
to
your
github
right
in
and
just
pull
manifests
from
there
right
or
helm
charts
you
have
that
easy
of
use
and
easier
of
management
of
applications
and
visualize
it.
So
you
can
kind
of
see
here
in
this
in
the
slide
and
you
can
visualize
an
application.
You
can
visualize
each
individual
component
of
that
application
too.
So
you
can
quickly
pinpoint
an
issue
if
you're
having
it
within
an
application
or
scale
it
out
into
another
cluster
as
well.
B
B
All
friends
here
now,
so,
let's
talk
a
cm,
so
a
cm,
an
open
shift
as
we
talked
about
it.
Obviously
they
work
better
together,
so
ACM
itself
runs
on
top
of
OpenShift,
so
you
are
required
to
have
an
open
shift
cluster
for
the
3
to
5
or
above
in
order
for
you
to
be
able
to
to
run
ACM
and
how
do
we
help
open
shift
V
better?
So
we
touch
a
little
bit
about
this
in
the
beginning,
but
basically
these
are
the
four
main
things
that
we
that
would
kind
of
like
product
mission.
B
If
you
will
we're
looking
to
accelerate
the
development
or
to
production
being
able
to
have
more
open
shift
or
more
kubernetes
workloads
within
your
production
environment,
we
see
being
that
kubernetes
is
fairly
young.
A
lot
of
us
a
lot
of
organizations,
kind
of
look
at
it.
As
you
know,
it's
still
an
evolving
technology.
You
know,
there's
not
a
many
standards
out
there.
We
want
to
be
able
to
kind
of
celebrate
that
confidence
level,
because
we're
very
we
know
that
openshift
obviously
is,
as
I
mentioned,
it's
the
standard
when
it
comes
to
kubernetes.
B
So
we
want
to
be
able
to
kind
of
push
that
forward
and
being
able
to
kind
of
help
with
that
adoption
right
help
you,
as
a
consumer
kind
of
help
that
adoption
for
your
data
center
right
reduce
the
cost.
So
maybe
you
know
instead
of
having
kind
of
different
types
of
kubernetes
distros
right,
spread
all
over
the
place
right.
B
Why
not
just
standardized
or
even
better,
you
know,
maybe
reduce
some
of
that
operational
costs
by
having
more
stuff
either
on
pram
or
even
on
another
data
center,
whatever
the
case
might
be,
but
just
being
able
to
look
at
what
you
have,
and
perhaps
you
know
reduce
some
of
the
costs.
Maybe
I
don't
need
that
many
clusters
out
there
I
can
run
more
workloads
if
I
run
it
more
efficiently
right,
it's
all
about
being
efficient,
exactly.
A
B
Right,
increased
application
availability,
so
have
you
your
application,
be
more
available
old
time,
so
I've
been
able
to
distribute
a
Quaker
move
it
around
different
clusters
to
do
all
of
that
in
the
compliance
we
talked,
I
think
enough
about
the
compliance.
I
think
you
all
get
it.
We
just
need
to
have
standards.
I
mean
it's
just
the
way.
It
is
it's
just
the
way
of
the
world.
We
need
to.
A
B
B
A
B
We're
gonna
we're
gonna
talk
a
little
bit
about
some
of
the
architecture,
because
I
feel
like
this
is.
This
is
important
to
kind
of
kind
of
kind
of
touch
through
right.
That's
what
this
audience
wants.
Yeah
this
audience
know
one
the
marketing
marketing
stuff.
They
want
the
technical
stuff,
I
get
it
yeah
I,
get
it
yeah,
all
right
so
from
an
architecture
perspective.
So,
as
I
mentioned
earlier,
ACM
itself
runs
on
top
of
OpenShift
for
the
three
to
five
and
above
right.
B
The
way
works
is
that
we
install
through
the
operator
hub
so
you'll
see
that
you'll
see
that
today.
Obviously,
the
operator,
however,
has
become
the
standard
defacto
for
deploying
applications
within
an
open
shift
environment
right.
So
we
follow
that
same
suit.
We
deploy
what
we
call
a
hub
cluster,
so
within
that
hub
cluster,
there's
a
few
components
and
you'll
see
those
today
when
we
deploy
it,
but
basically
the
three
main
ones
that
we
cannot
look
at
right
is
there's
an
API
engine,
a
console,
obviously
that
you're
gonna
interact
with
and
a
CLI
once
you
deploy.
B
That
one
important
thing
to
note
is
that
the
whatever
OpenShift
cluster
that
you
had
opponenet
cm2
it
needs
to
be
just
for
a
cm
so
curly.
We
are
not
able
to
kind
of
share
workloads
within
this
cluster
with
other
applications
eventually.
Well,
we
we
have
in
the
Rome
app
to
be
able
to
connect
span
some
of
that
functionality,
but
not
not
as
it
works
today
and.
A
B
A
Gangster,
the
lackluster
potential
right,
yeah,
yeah,
no
yeah,
so
yeah
like
having
I
I,
completely
understand
the
need
for
the
the
standalone
nests
of
it,
but
I
also
would
appreciate
you
know
it
is
kubernetes
after
all,
right
like
if
I
could
throw
a
big
enough
cluster
at
it
and
I
could
run
everything
in
it.
Why
not
you
know
so?
Yeah
I
appreciate
the
roadmap
item.
Yeah.
B
Yeah,
and,
and
and
and
one
of
the
beauty,
the
beauty
of
this
is
that
obviously
you're
not
limited
to
running
this
on-prem,
so
so
Wow
yeah
yeah
well,
ACM
itself.
Is
it's
not
a
solution,
so
you
can't
go
to
like
cloud
or
ahead
comm,
which
is
our
SAS
portal
right
in
order
as
a
service
like
you
can
with
openshift
today,
you
could
order
an
open
shift
cluster
right
and
have
a
cm,
throw
a
cm
on
top
of
it
right.
So
this
can
run
in
any
cloud
anywhere
right.
You
can
run
on
either.
B
Yes,
Google
right,
they're,
all
half!
You
know
we
have
big
partnerships
with
all
of
these
clouds,
where
we
can
run
OpenShift
dedicated
and
we
can
just
install
a
cm
on
top
of
it
because
again,
it's
just
an
operator
hub
item
right,
so
you
just
install
it
that
way,
yeah!
So
that's
the
beauty
of
ACM
like
even
if
you
don't
have
the
own
primary
sources
to
get
going
today,
you
could
do
it.
You
know
in
a
public
cloud
yeah.
B
Obviously,
once
once
you
install
it
once
you
configure
it
right,
then
you
want.
Then
you
have
those
managed
clusters
right,
so
those
clusters
that
whatever
they
already
exist,
that
you
want
to
just
on
bore
or
import
into
a
cm
or
clusters
that
you
know
you
want
to
build
through
a
cm.
They
board
the
same
right.
They
become
what
we
call
the
manage
cluster
and
within
those
there's
a
few
things
that
we
deploy.
So
we
deploy
a
few
containers
and
and
you'll
see
through
when
we
go
through
through
some
of
that
stuff
right.
B
But
basically
we
deploy
a
few
containers
that
report
back
into
the
hub
right
and
kind
of
just
bring
in
to
within
the
hub
all
of
the
information
that
is
needed
in
order
for
us
to
manage
that.
So
you
know
that
is
basically
like
the
architecture.
From
from
from
a
cm
perspective
is
very
simple,
very
easy
we're
not
again,
we
did
not
want
to
change
a
lot
of
of
their
texture
and
kind
of
not
make
it
very
compliant
or
easy
to
work
with
open
shift
over
shivering
and
a
cm
together
right,
yep.
B
Not
that
it's
it's
a
lot
easier
to
run
it
just
because
of
this,
the
operator
bio
right,
so
you
can
kind
of
see
here
some
of
some
of
the
installation
and
we'll
walk
through
it,
but
just
at
a
high
level,
as
I
mentioned
403,
though
five
and
above
from
a
management
perspective
or
cluster,
so
clusters
that
we
can
manage,
we
go
back
all
the
way
to
3.11
so
think
about
this.
Here's
another
use
case
that
it's
kind
of
like
on
the
line
but
really
talked
about
I,
see.
A
B
B
A
B
B
B
B
B
You
can
kind
of
see
here
some
of
the
resource
requirements
right
so
obviously,
for
the
most
part,
we
kind
of
follow
the
openshift
kind
of
standards.
So
you
can
kind
of
see
here.
Obviously
the
the
three
master
workers.
That's
a
standard
that
that'll
be
ships
pass
from
four
to
four
and
above
so
we
follow
that
right
and
you
can
kind
of
see
the
resources
I'm.
Nothing,
nothing
crazy,
but
just
gives
you
an
idea
right.
A
Records
it's
just
it's
just
like
ansible
or
any
other
tool
right
like
how
much
you
manage
depends
upon
or
what
you
can
manage
depends
upon
the
workload
there's
a
thing
that
it's
being
managed
from
right.
So
if
you
need
to
manage
3,000
clusters,
this
minimal,
viable
resource
requirements,
probably
not
gonna
work
for
you
know
you
probably
manage
you
know
a
normal.
You
know,
average.
You
know
cluster
amount.
A
You
know
I'm
assuming
I'm,
not
sure
what
the
the
performance
testing
has
been
done
here
on
the
minimum
workload
or
how
many
clusters,
because
there's
so
many
variants
that
can
be
supported,
but
the
assumption
is
normal
numbers
of
clusters
get
supported
with
normal
numbers
of
resources
required.
Okay,.
B
Exactly
exactly
exactly
right
exactly
right,
so
you
know
we
talked
a
little
bit
about
the
manage
clusters
right.
You
can
kind
of
see
some
of
the
components
here
that
and
again
these
are
just
containers
when,
when
I
say,
components
is
just
containers
that
we
are
deploying
into
those
manage
clusters,
you
can
turn
it
on
and
off
within
the
ammo,
so
that
is
fully
dependent
on
on
what
you
want
and
what
you
like
and
what
you
want
out
of
the
product.
Obviously
you
know
the
more
stuff
that
you
turn
off.
B
The
less
the
product
can
do
right.
That's
always
right!
This
is
this
goes
back
to
ten
20
years
ago,
right
when
it
comes
to
agents
right,
it's
the
same.
Yeah,
yeah,
yeah
same
thing.
Here
right
we
have
some
role
based
access
control.
We
follow
very
closely
what
exists
today
within
open
shift.
So
obviously
you
know
open
ship
has
done
a
fantastic
job
at
integrating
with
you
know,
things
like
elda,
like
Active,
Directory,
right
and
all
of
these
standards
around
role
based
access
control.
B
So
what
we
did
instead
of
reinventing
the
wheel,
we
just
follow
what,
if
does
so,
you
can
see
some
of
the
roles
here.
Obviously
we
will
be
expanding
some
of
these
as
the
application
kind
of
grows
right
and
then
there
are
some
other
things
that
you
can
kind
of
see
here.
Some
of
the
role
access
based
controls
that
we
have
available
for
it.
B
A
A
B
A
B
A
A
C
A
A
C
B
Alright,
so
so
what
we're
gonna
do
is
go
to
the
operator
hub,
so
there
are
several
ways
that
you
can
deploy.
It,
obviously
a
cm.
You
can
deploy
it
through
a
CLI
if
you
so
desire
right.
So
if
you
want
to
do
like
a
mass
deployment
or
multiple
ACM
instances,
you
can
do
that
or
you
can
just
go
through
the
UI
for
the
simplicity,
I'm
gonna
go
through
the
UI
and
just
kind
of
show.
You
guys
that
so
you
can
kind
of
see
here
within
the
operator
hub.
B
B
Alphabetical
right,
but
you
can
kind
of
see
here
that
I
can
click
on
it.
You
can
kind
of
see
the
version
there
that
we're
at
so
as
I
mentioned
right
now,
we're
currently
on
tech,
preview,
tech
preview,
one
that
are
one
when
we
go
GA.
It
will
be
two
though,
but
you
can
kind
of
see
here
a
little
bit
of
the
information
about
it.
You
can
see
you
know
how
to
install
it.
What
the
providers
types
are
the
repositories,
the
containers
all
of
that
right.
So
if
I
go
ahead
and
click
install
okay.
B
Basically,
what
this
is
going
to
do
is
a
couple
of
things.
So,
first
of
all,
it's
gonna
install
itself
into
its
own
namespace,
so
you
can
either
build
your
own
if
you
have
very
specific
standards
that
you
want
for
your
namespace
or
you
can
just
let
it
install
into
what
it
wants
installing
which
is
open.
Cluster
advanced
management,
I'm
gonna.
Do
that
for
some
felicity
reasons
you
also
subscribe
automatically
to
the
update
channel,
so
the
beauty
of
having
operator
hub
is
that
you
no
longer
have
to
worry
about
updates
right.
B
So
when
there's
a
new
update
as
long
as
you
subscribe
to
that
channel
for
a
cm,
you
will
get
the
update.
You
will
get
the
update
automatically
right
and,
of
course
you
can
put
approvals
right
behind
it,
yeah
or,
if
you
don't
want
it
to
just
automatically
operate
right,
but
the
beauty
of
this
is
that
you
don't
have
to
kind
of
kind
of
hear
from
somebody
else
right.
You
just
can
you
can
go
over
here,
you
can
see.
Oh
I
have
a
release.
B
I
can
update
it
and
look
at
the
notes
and
everything
else
so
very
easy,
so
I'm
gonna
go
ahead
and
click
Subscribe,
and
so
the
moment
I
click
Subscribe.
A
couple
of
things
are
gonna
start
happening.
So
there's
a
couple:
there's
of
course
a
couple
of
workloads
that
are
being
deployed.
So
if
I
go
ahead
and
take
a
look
at
my
workloads,
I'm
a
pods
you're
gonna
start
seeing
that
there's
a
couple
of
containers
kind
of
coming
online
right.
B
So
obviously
you
know
we
have
a
few
things
that
we
install
on
top
of
just
a
cm.
So
if
you
look
at
the
install
operators
here,
we
we
also
install
at
CD
right.
This
is
a
specific
version
of
@cv
that
we
leverage
to
use
for
certain
things
right,
like
we're,
gonna
leverage
these
for
doing
a
che
right
at
some
point
and
a
few
other
customizations.
So
even
if
you
have
it
today,
you
you
know
it
will
automatically.
He
stole
his
own
version
within
his
own
namespace
right.
So.
A
B
C
B
And
look
at
the
pods,
we
have
six
running
pods,
nothing
pending.
However,
we
need
to
do
a
little
bit
of
extra
configuration
here.
We
need
to
go
into
your
provider,
API
for
the
multi
cluster
hub
and
I
need
to
create
a
multi
cluster
hub,
but
before
I
do
that
I
actually
need
to
go
ahead
and
create
a
secret.
So
obviously
you
know
in
order
for
us
to
pull
the
images
that
we're
going
to
be
deploying
into
some
of
these
clusters
right.
B
We
need
to
have
an
authentication
method
right
and
so
a
lot
of
the
secrets
will
come
directly
from
cloud
or
a
hakam.
So
within
cloud
array,
hakam
I'm
going
to
go
ahead
and
put
this
window
here
now
within
cloud
overhead,
comm
right,
I'm
logged
in
within
the
cloud
where
I
have
come
with
my
username
and
my
account
and
all
of
that
right,
I
will
go
into
their
open
shift.
Cluster
management
and
I'm
gonna
go
here
and
create
a
new
cluster,
then
pick
a
new
AWS
cluster
and
if
I
go
into
the
Installer
provided
infrastructure.
B
You'll
see
here
that
I
have
a
pool
secret
already
generated
for
me,
so
we're
gonna
leverage
this
pool
secret
and
use
it
for
ACM
to
be
able
to
go
out
and
pull
those
images
directly
right.
So
you
know
instead
of
having
to
go
to
access
or
ahead
calm
and
kind
of
configure.
All
your
you
know
all
your
entitlements
and
everything
else
once
you
already
are
entitled
to
a
cm.
You
just
need
to
go,
get
the
full
secret
from
cloud
or
Hakam
and
then
go
back
into
your
ACM.
B
Yeah,
you
know
it's
great,
it's
great,
it's
a
fantastic
product.
So,
if
I
go
into
my
secrets
and
I
go
and
select
an
image,
full
secret
I'm
going
to
go
ahead
and
give
the
secret
a
name.
So
whatever
you
want
in
this
case,
I'm
just
gonna
call
it
a
cm,
keep
it
simple,
and
this
is
going
to
be
I'm
gonna
upload,
a
configuration
file
in
this
case
I'm,
not
uploading.
Anything
I'm,
just
copying
and
pasting,
so
I'm
pasting
did
add
a
secret
pool
secret.
B
That
I
got
from
cloud
already
have
comm
and
put
it
in
here,
and
this
is
gonna.
Allow
me
to
again,
when
I'm
deploying
images
that
the
need
you
know
some
kind
of
like,
oh,
like
downloading
the
bits
right
to
be
able
to
deploy
them
into
another
another
cluster.
It's
gonna
use
this
secret
right.
So,
in
fact,
if
I
go
back
to
my
install
operators
and
I
go
to
my
multi
cluster
hub
now,
I
can
actually
create
my-mult
across
their
hub.
B
B
B
B
B
Once
we
do
this
you'll
notice
that
there's
a
few
more
pots
that
are
going
to
be
Stan,
she
ated
and
built.
So
what
we're
doing
here
is
you'll
see,
there's
a
couple
multi
cluster
hubs
that
kind
of
have
to
come
online
before
obviously
ACM
becomes
available.
So
this
is
gonna.
Take
you
know
a
few
minutes.
You
see
here,
for
example,
we're
creating
a
closed
container
for
certain
management.
Right
you'll
see
more
coming
here.
B
So
if
we
actually
kind
of
soar
by
pending,
we
have
one
an
API
server
right,
a
web
hook
right
so
you'll
see
all
of
these
containers
kind
of
coming
in
and
getting
kind
of
deployed
here
or
manager.
Nice
serve
management
right
exactly
so
boom.
There
they're
all
kind
of
coming
in
online
here,
and
so
this
is
gonna.
Take
a
few
minutes.
So,
oh
that's.
B
A
B
C
B
C
B
B
How
do
I
get
started
right,
especially
if
you're
kind
of
new
to
these
technologies
right
I,
always
you
know
I
feel,
like
you
know,
when
I
talk
to
people
that
that
are
looking
into
this
product,
the
first
thing
that
I
tell
them
is
is
make
sure
you
take
an
open
chef
course.
If
you
don't
understand
open
chef,
yeah.
C
C
A
C
A
A
B
C
A
B
A
Be
everything
that's
in
those
banners,
though,
is
gonna,
be
in
the
About
section
on
the
on
the
twitch
page.
So
if
you're
not
following
us
on
Twitch
we're
trying
to
hit
1000
subscribers
by
the
end
of
the
month,
if
you
haven't
looked
at
your
calendar
today
is
the
end
of
the
month.
It
is
noon
on
the
East
Coast
I
have
exactly
12
hours
to
get
12
more
followers.
Oh
that's
nothing
come
on,
but
this
has
been
a
journey
man.
This
has
been
yeah.
C
A
C
A
C
B
A
B
A
B
C
A
B
B
So
so
numb,
pending
all
of
our
our
a
pots,
are
all
up
and
running.
So
if
we
go
back
into
our
stall
operators,
everybody
is
happy
and
successful.
So
this
is
still
kind
of
finishing
up
some
stuff,
but
the
beauty
of
this
is
that
now
we
can
navigate
into
our
networking
and
look
at
our
routes
and
it
provides
us
multi
cloud
console
location.
So
now,
I
can
actually
click
on
this
and
within
a
few
seconds
after
I,
accept
all
my
security
risks
and
log
in
again
Baumer.
B
B
Oh
so
these
blocks,
so
so
as
I
mentioned
right.
The
the
important
thing
to
note
here
is
that
again
we
leverage
the
same
authentication
methods
from
your
open
shift
cluster
so
since
I
deploy
this
I'm
using
the
Q
value
in
account
really
bad
idea.
Don't
ever
use
this
account
to
do
this
I'm
just
using
it,
because
it's
easy
right
now
and
simple,
but
if
your
point
is
make
sure
you
have
your
permissions
kind
of
set
properly
right,
but
I'm
using
the
Q
admin
account.
B
I
was
able
to
log
in
because
you
saw
there
through
the
routes.
I
was
able
to
get
my
URL,
so
this
is
now
my
URL
for
my
ACM
instance-
and
you
see
here
this
four
blocks,
so
these
four
blocks
really
provide
you.
The
main
use
cases
that
we
talked
about
so
the
end
to
end
disability,
the
cluster
bicycled
application
life
cycle
and
the
governance,
risk
and
security.
So
all
of
these,
of
course,
are
gonna,
be
empty
I,
just
build
it
right,
so
let's
go
ahead
and
actually
go
and
add
a
cluster.
Also.
B
The
the
first
thing
that
I'm
gonna
do
is
kind
of
set
up
my
credentials,
so
there
is
what
we
call
the
provider
connections
right
in
the
provider.
Connections
is
where
we
keep
all
of
the
credentials
for
the
public
clouds,
so
in
this
case
I'm
just
going
to
go
ahead
and
build
something
into
AWS,
just
because
it's
wynaut
right,
it's
in.
B
B
B
That
close
we're,
not
that
close,
so
I
am
off
the
screen
here,
I'm
just
kind
of
going
through
and
publicly
getting
some
of
my
private
keys,
my
public
keys,
where,
as
a
sage,
my
cool
secret,
so
you'll
know
you
know
we'll
take
that
Poole
secret-
that
we
use
earlier
and
put
it
in
here
right
so
remember
when
we
pull
that
pull
secret
from
cloud
or
Hakam.
Well,
I
gotta
go
back
now
and
copy
it
again,
because
I'm
gonna
put
it
here
so
after
I
get
all
of
that
done.
B
Magically
boom
I
have
a
credentials
already
created.
Look
at
that.
It's
quick.
Of
course
you
can
have
multiple
credentials
for
multiple
different
clouds
right,
so
we
talked
a
little
bit
about
what
we
support,
which
for
google
cloud
asher
right.
So
the
main
the
main,
the
main
big
boys,
if
you
will,
and
so
let's
go
through
and
actually
create
a
cluster.
So
from
a
cost
perspective,
you
have
two
ways
of
doing
things:
you
can
either
create
a
new
cluster
or
you
can
import
an
existing
cluster.
So
we
talked
a
little
bit
about
this.
B
How
if
you
already
have
existing
clusters
that
you
have
already
built
whatever
those
might
be
eks
like
SG
KS,
whatever
it
is,
they
can.
You
could
come
in
here
and
import
right,
so,
whichever
the
case
might
be,
you
can
do
that.
So,
let's
go
ahead
and
create
a
cluster,
so
I'm
only
going
to
create
a
cluster
I
am
in
Florida,
so
I'm
gonna
call
it
FL
to
K
20
this
year
is
amazing
best
year
ever
not
and
then
I
need
to
provide
a
base,
DNS
domain
name.
B
So
a
DNS
name,
pretty
straightforward
I
mean
I,
hope.
I.
Don't
need
to
explain
this
if
I
do,
then
you
might
be
in
the
wrong
stream,
but
so
from
here
you
could
get
to
pick
your
distribution,
so
obviously
we
are
going
to
deployed
openshift.
So
currently,
when
we
create
a
cluster,
we
can
deploy
using
openshift
right.
So
you
can
see
the
three
main
clouds
that
we
support
here.
B
B
You
can
see
the
changes
number
two
you
can
take
all
this
yeah
mo
copy
it
and
keep
it
on
a
github
repo
ask
my
standards.
So
if
I
start
building
standards
for
clusters
that
I
really
like
and
instead
of
having
to
go
through
this
screen
and
select
all
your
standards
and
everything
else,
you
can
just
copy
and
paste
right
within
the
Rome
app.
We
have
developed.
We're
gonna.
Have
the
ability
to
do
this
now
from
a
github,
we're
gonna,
have
an
integration
to
github,
so
you'll
be
able
to
push
it
directly
from
the
product.
B
So
this
is
common
tusu
very
soon,
but
for
now
nice
cool
you
can
copy
and
paste
this,
which
is
pretty
easy
right,
will
select
my
credentials
so
the
credentials
that
I
build
and-
and
it
will
automatically-
cannot
put
those
kind
of
encrypted.
So
you
see
here
encrypts
all
but
puts
all
my
SSH
keys
and
everything.
B
Yeah
yeah
yeah
that
one
that
one
is
very
public
and
private
and
you
can
kind
of
remove
that
or
we
see
you
know
you
don't
have
to
put
that
there,
but
you
can
kind
of
see
here.
You
can
pick
what
region
you
want
to
build,
or
we
see
this
too,
given
that
we
are
using
AWS
right,
we
see
all
over
the
AWS
can
region
put.
B
B
A
B
Several
times-
and
so
you
can
also
pick
your
stones,
so
you
can
pick
your
stones
for
your
master
pools
so
notice
that
I
can
split.
Those
between
zones
put
multiple
zones
if
I
wanted
to
we're.
Gonna
have
three
master
nodes
billed
by
default.
Again,
as
as
we
talked
about
that's
just
a
default
for
openshift,
you
can
select
obviously
the
instance
type
again.
These
are
all
Amazon
terms.
Nothing!
Nothing
should
be
strange
here.
You
can
pick
how
much
the
root
storage
is
going
to
be.
B
This
is
just
gonna
be
an
example
cluster,
so
I'll
leave
it
at
default
and
okay
I
also
pick
the
same
information
for
your
worker
pool,
so
I
can
select
here
for
my
worker
pool.
What's
on
do
I
want
you
know
what
the
instance
types,
how
many
nodes
I'm
gonna
put
for
that
you
can
add
more
worker
pools
if
you
wanted
to.
So,
of
course,
you
can
do
more
here.
You
can
also
configure
your
network
II.
B
So
currently,
we'd
have
two
types
of
networking
that
we
support,
so
they
offer
shift
default
as
the
end
or
the
OB
end
for
kubernetes.
So
those
are
the
two
that
we
support.
Of
course
you
have
your
cluster
IPS
and
all
of
that
they
even
configure
I'm
just
leaving
all
of
this
for
the
faults,
and
then
we
have
our
purpose.
So
our
purpose
is
with
the
labels.
So
the
labels
really
allow
you
to
kind
of
identify
clusters
and
kind
of
kind
of
combine.
B
If
you
will
clusters
to
say
what's
the
purpose
of
this
cluster
so
say,
I
can
start
with
something
very
simple
like
this
is
going
to
be
for
my
purpose
of
a
development
cluster
right,
so
it
will
assign
a
label
of
environment
equals
def
what
that
means.
You
can
identify
it
and
build
that
within
the
product
and
we'll
we'll
use
this
environment
dev
later
on,
as
we
go
through
the
applications,
so
you
can
kind
of
see
how
we
can
move
some
of
them
into
it
right.
B
B
B
B
A
B
I'll,
take
it
exactly
exactly
it's
not
bad,
there's
also,
obviously,
the
capability
of
importing
a
cluster
an
existing
one
so-
and
this
is
kind
of
how
you
can
kind
of
see
here
what
we
were
talking
about
earlier
about
all
these
agents
are
in
or
containers
that
we
deploy
right.
So
obviously
you
have
to
specify
a
name
so
specify
the
name
I'm,
not
very
good,
with
names
as
you
can
see,
but
you
can
see
all
of
the
stuff
that
you
can
kind
of
turn
on
and
off
right
again,
the
more
stuff
they
turned
off.
A
A
A
B
C
B
I
go
right.
That's
it
simple!
From
configuration
perspective
from
the
labels.
Again,
you
can
specify
labels
here
once
again,
so
I
can
do
and
put
this
on.
My
my
environment
equals
dev
right
and
then
I
will
generate
a
command.
So
what
this
does
is
that
it
actually
gives
me
a
QC
TL,
apply
command
that
I
can
copy
here
and
go
back
into
a
cluster
that
I
already
have
and
execute
this.
So
I
can
own
Bor
this
cluster
right.
B
So
very
simple,
very
easy.
Once
you
do
that,
the
the
Foster
will
obviously
sit
in
a
pending
import
state
with
the
command
here.
So
you
notice
that
it's
a
it's
an
encoded
CID
command
right
with
Q
CTL
apply.
The
beauty
of
this
is
that
if
you
know,
if
you
you
don't
have
to
run
capacity
L,
you
can
run
OC.
If
you
wanted
to.
Oh
no.
C
B
Actually
apply
this
because
it's
pretty
much
the
same
thing,
so
you
know
you
have
the
ability
to
do
that
once
you
get
it
on
board
and
you'll,
be
able
to
see
all
your
notes
and
once
all
these
ages
kind
of
come
online
you'll
be
able
to
see
that
right.
So
that's
basically
creating
a
cluster
from
scratch
importing
a
cluster
right.
So
this
will
take
a
few
minutes
so.
B
A
B
A
B
A
A
B
C
B
C
B
Organizations
are
already
at
this
point.
There
already
have
some
kind
of
way
of
managing
clusters,
whatever
that
might
be
good
or
bad.
They
have
it,
but
they
don't
have
a
reliable
way
of
having
their
applications
and
seeing
their
applications
within
the
clusters
right
right.
So,
within
the
applications
we
have
two
screens,
we
have
an
overview
and
we
have
resources.
So
if
we
take
a
look
at
the
resources,
this
is
kind
of
how
we
start
to
build
an
application
right.
Yeah
and
the
application
is
composed
of
really
four
major
things.
B
So
we
have
obviously
the
application
definition.
So
that's
that's
a
yam
all
that
kind
of
defines
what
the
application
is.
When
applications
you
know
kind
of
lives
and
resize.
You
have
your
subscriptions.
So
if
you'll
take
a
look
at
the
subscription
itself,
it's
just
the
deployables
within
the
channels
that
allows
you
to
have
all
the
different
versions
right.
So
you
have
multiple
versions
or
multiple
applications
and
you
can
deploy
those
around.
If
you
want
it,
placement
rule,
as
the
name
kind
of
states
is
how
you
place
that
application.
B
So
in
this
case
you
can
place
this
application.
For
example,
if
you
wanted
to
remember
that
label
that
we
have
environment
equals
dev,
we
are
going
to
use
that
label
to
kind
of
place,
an
application
and
and
and
that's
how
you
kind
of
move
applications
around
within
clusters,
and
you
tell
them
what
where
it's
gonna
live,
and
then
you
have
your
channel,
so
the
channels
really
point
to
the
specific
repositories
where
the
kubernetes
resources
are
really
stored.
So
in
this
case
we
can
do
things
like
namespace.
We
can
do
the
helm
repo.
B
We
can
do
our
jet
bucket
or
give
up
right.
So
we
have
multiple
options
here
and
all
of
these
are
pretty
much
the
standards
or
have
been
the
standards
for
a
very
long
time
when
it
comes
to
kubernetes
right.
So
let's
go
ahead
and
actually
walk
through
building
an
application.
So
I
have
here
an
application
within
a
github
repo.
So
I
have
a
couple
of
example:
obligations
that
I
like
to
use
so,
for
example,
this
engine
injects
application,
don't
mind
my
pronunciation.
It's
a
Latino
thing,
you'll
see
here
the
llamo
of
all
of
that
application.
B
You
can
see
here
the
the
application
itself,
so
this
is.
This
is
just
a
raw
llamo
of
that
application.
So
you
see
here
at
the
top.
We
have
a
few
things
that
we
need
to
create
like
a
namespace,
obviously
we're
going
to
place
that
application
within
a
specific
namespace,
nothing
new
here,
there's
the
application
here
itself.
So
it's
got.
You
know
things
like
the
name
of
the
application.
B
What
namespace
is
going
to
be
placing
in
then
we
have
the
descriptions
that
we
have
the
placement
rule
right
where
in
this
case,
right
now,
I
have
it
just
place
it
on
every
cluster.
So
when
you
do
a
cluster
selector
with
the
open
brackets
like
this,
you
go
in
to
deploy
basically
that
application
on
any
available
cluster.
That's
within
the
manage
ACM.
Obviously
you
can
tweak
that
based
on
labels,
then
you
have
your
channel's,
the
deployables
itself
and
in
the
description
right
so
pretty
straightforward.
B
So
what
I
want
to
do
here
and
again
if
you
are
dealing
with
applications
with
the
kubernetes?
You
probably
already
have
this
you
most
of
this,
because
when
you're
building
applications
there's
pretty
similar
standards
that
you
use
for
this
right,
so
you
have
to
have
a
letter
definition
of
that
application
and
in
a
llamo
so
miles
right.
So
you
can
take
some
of
this
and
kind
of
convert
it
very
easily
to
be
part
of
a
cm
and
orb
or
your
application,
and
let
basically
a
CM
kind
of
manage
it.
B
So
the
first
few
things
that
I'm
going
to
do
is
create
the
namespaces
right
so
to
create
a
namespaces
within
a
cm.
We
go
into
the
top
here
this
plus
sign,
and
there
is
what
we
call
a
create
resource.
So
this
is
just
for
creating
resources.
Any
type
of
resources,
in
this
case
I'm,
going
to
select
my
target
as
my
local
cluster.
So
when
weather
point
or
doing
applications
or
I
for
the
most
part,
most
of
them
can
live
within
the
hub
cluster.
B
Of
course
they
just
the
definitions
of
them
will
live
there
right
and
then
the
deployables
and
everything
else
will
be
within
the
clusters
that
are
deployed
so
I'm
going
to
go
ahead
and
paste.
My
namespace
here,
I'm
gonna,
create
two
namespaces
I'm
gonna,
create
this
one.
Don
created
and
I'm
gonna
go
ahead
and
create
my
second
namespace,
which
is
an
SSH
and
paste
that
and
create
boom.
B
So
my
resources
are
now
created
now
I'm
going
to
go
ahead
and
create
a
new
application
and
you
can
actually
kind
of
create
the
namespace
automatically
within
this
application
screen.
I
just
kind
of
wanted
to
show
you
a
different
way
of
doing
it
right,
but
I
could
have
very
well
kind
of
taken.
All
of
this
part
of
it
and
just
kind
of
put
it
there
right
in
there
in
the
application
screen,
but
I
am
going
to
go
ahead
and
just
build
the
application
now.
B
So
I
am
going
to
copy
all
of
this
code
and
go
back
into
my
applications
and
create
my
applications.
So
all
of
them
doing
here
is
just
telling
it
what
the
API
version
that
I'm
looking
at
and
what
type
of
application
I'm
doing
the
labels
for
that
application.
The
group
where
that
application
cannot
live
in
the
description
for
and
what's
the
status
of,
right,
Christian
forward
yeah,
so
I
click
Save.
B
Now
everything
goes
away
now
after
a
few
minutes
in
the
background,
or
we
see
we
are
kind
of
going
through
and
kind
of
gathering,
all
of
this
all
of
the
application
kind
of
definitions
right
and
it's
gonna
build
an
application.
So
here
we
go
now
we
have
an
application
name.
So
obviously
the
application
name
is
we
have
built.
We
have
our
spaces,
and
now
we
can
start
building
all
of
our
resources
for
this
application.
B
So
if
I
go
back
into
I'm,
gonna
move
this
here
to
make
it
easier,
so
my
placement
rule
again
copy
and
paste
all
this
telling
it
here
is
all
of
my
clusters
are
gonna.
Get
this
application?
That's
it.
I
could
set
this
spec
to
just
look
at
a
specific
labels
if
I
wanted
to,
in
which
we're
gonna
do
here
in
a
little
bit
to
kind
of
show
you
how
that
works.
So
we'll
do
the
placement
rule
that
takes
a
few
seconds
to
kind
of
go
through
and
done.
B
Then
I'm
gonna
go
ahead
and
take
my
my
channel
right.
So
we're
pulling
it's
a
helm,
repo
that
we're
pulling
this
specific
application
right.
So
you'll
notice
here
that
it's
my
helm,
repo-
and
this
is
the
path
name
of
that
chart
that
I'm
pulling
from
pretty
standard
deployment.
Nothing
crazy
here
for
nine
chicks
and
then
finally,
I'll
grab
my
subscription
information
right.
B
So
I
have
I
created
my
channel
I
created
my
placement
rule
and
finally,
my
subscription-
and
you
can
see
here-
this
is
my
ascription
to
the
channels-
and
this
is
the
placement
reference
trysil
to
my
placement
rule
and
what's
the
name
of
that
placement
wall
done
just
like
that,
I
have
created
an
application.
Oh.
C
A
B
A
A
B
A
B
Exactly
I
mean
that's,
that's
the
that's
the
biggest
thing
that
you
get
also
from
us
right
that,
obviously
we
have
all
of
these
wonderful
other
products
that
we
can
integrate
with
right.
So
you
know
very
soon
we're
gonna
have
cost.
We
also
gonna
integrate
into
the
cost
management
within
cloud
where
I
have
calm
answer
all
right,
so
we
have
all
these
other
eco
tools
that
are
part
of
the
ecosystem
within
Red
Hat
that
we
want,
we
will
integrate.
A
B
The
cost
is
going
to
be
huge
because
that's
a
big
pain
point
right
now
with
a
lot
of
customers
right
because
they
don't
they
don't
really
know
some
of
the
costs
associated
with
some
of
these
workloads.
So
all
right
so
Chris
this
is
Chris's.
Cluster
mine
is
still
kind
of
creating
here's.
The
beauty
of
this
notice
that
it
automatically
it
assigned
me
Dan.
A
B
Knows
that
it's
an
Amazon
right,
it
already
knows
that,
or
we
see
I
gave
it
that
environment
equals
dev
right.
It
already
knows
that
it's
a
openshift
right
automatically,
so
it
read
all
of
this
information.
It
also
gives
me
their
address.
The
cluster
API
address,
as
well
as
the
console
URL
so
now
I
can
actually
go
ahead
and
click
on
this
URL
and
be
able
to
kind
of
see
the
console
which
I
don't
know
is
right.
B
B
Big
deal
no
big
deal,
I
mean
it's
it's
there.
It's
obviously
everybody
can
see.
You
can
also
do
things
like
upgrade
it.
So
one
thing
that
I
also
detected
is
that
hey,
listen,
you're,
a
four-door
4.3,
there's
an
upgrade
available
for
you
right.
So
when
I
click
on
that
it
takes
me.
Where
do
you
want
to
go?
Which
version
do
you
want
to
go
so
fancy?
So
you
can
go
to
whichever
raishin.
You
have
basically
subscribe
to
your
channel
too
right.
B
So
my
OpenShift
instance
is
subscribe
to
the
latest
and
greatest
so
you
can
see
here.
I
can
take
it
all
the
way
to
photo
4.9
so
pretty
awesome.
We
can
also
see
all
of
my
notes,
so
you
can
see
the
notes
that
I
have
available
so
I
have
three
masters
and
two
worker
nodes.
What
are
the
instance
types
they're
running
all
us
east?
That's.
B
B
So
yeah
pretty
simple,
just
like
that
right,
you
can
see
very
easy
to
kind
of
either
create
your
clusters
or
import
your
clusters
pretty
straightforward
right.
So
if
we
go
back
to
my
manage
applications
here
and
I,
look
at
my
applications.
Look
at
this
when
I.
Look
at
my
application
now.
Wait
a
second
isn't
that
the
cluster
that
I
just
want
bought
it
from
from
Chris.
Look
at
that.
B
It
already
determined
right
that
I
already
have
these
two
clusters:
I
have
one
that's
been
built
and
one
that's
already
built,
and
it's
currently
going
and
deploying
that
application,
because
I
created.
Obviously
you
saw
my
placement
rules
that
I
said
basically
deploy
this
everywhere
and
so
right
now
is
working
through
in
the
point
that
application
automatically
once
it
deploys
that
application.
It's
gonna
paint
everything
that's
needed
for
that
application
within
that
cluster.
B
So
think
about
think
about,
if
you
have
an
application-
and
perhaps
you
have
a
CSUN,
where
your
application
sees
a
little
more
traffic,
that
I
normally
would
think
about
how
quickly
you
can
expand
that
application
once
you
already
have
it
here,
you
can
expand
that
application
and
actually
increase
your
workloads
immediately
right
without
having
to
wait.
It's
pretty
amazing,
pretty
cool,
and
you
can
kind
of
see
here
my
placement
rule.
B
B
B
Yeah
yeah
absolutely
and
it
makes
it
it
makes
it
so
much
easier,
so
notice
by
default.
I
have
some
policies
already
kind
of
built
here
right
out
of
the
box
right.
Sorry,
I,
clicked
back
my
mistake:
yeah
I
click
I
tap
my
mouse
just
quickly,
and
you
know,
if
you
haven't
noticed,
I'd
really
like
to
talk
with
my
hands,
so
sometimes
I
kind
of
touched
things
what
I'm
not
supposed
to
so
anyways,
so
you
can
see
here
we
can.
Basically,
this
is
the
overview
pane.
B
You
can
kind
of
see
and
break
this
down
either
by
categories
or
bystanders.
So,
whichever
way
you
wanna
you,
you
want
to
slice
the
pie,
you
can
also
look
at
filters,
so
you
can
apply
a
specific
filter,
so
think
of
this
as
your
landing
page
for
all
your
policies,
right
yeah,
you
can
see
here
that
I
have
all
of
my
some
of
these
policies
already
created
by
the
fault.
Some
of
these
policies
are
pretty
standard
type
of
policies
like
a
certificate
policy,
a
namespace
policy
I'm,
looking
at
the
policies
of
my
own,
the
rules,
etc.
B
Right,
and
so
we
have
two
types
of
remediations.
Where
we're
building
policies
we
have
either
an
inform
or
an
enforce,
so
inform
is
shows
what
it's
going
to
do
is
actually
inform
you,
hey.
You
have
a
problem
with
this
specific
cluster.
You
need
to
address
it
right.
It
won't
actually
fix
it
for
you
and
force
it
will
actually
go
and
actually
fix
that
issue.
For
you
automatically
the
moment,
you
select
your
policy
right.
I
don't
have
any
violations
right
now.
Obviously
my
clusters
are
still
again.
B
My
I
just
boarded
that
closer
from
the
Chris
gave
me
I
have
my
other
one,
that's
being
built
right.
It's
gonna
take
a
few
seconds,
but
let's
walk
through
creating
a
policy
so
to
create
a
policy
spray
standard
notice
again
the
same
theme
throughout
the
whole
product.
We
have
llamó
available
everywhere
right,
so
you
can
kind
of
see
here
all
over
yeah
moe
I
can
very
easily
copy.
This
paste
it
into
my
github
repo,
but
let's
say
I'm
going
to
go
ahead
and
build
a
policy.
B
I'm
gonna
build
a
policy
for
my
default
space
namespace.
You
can
see
here
some
of
the
specifications
that
we
provide
out
of
the
box
right.
So
anything
from
the
certificate
policy
to
namespace
specific
namespace,
specific
parts
that
might
need
to
exist
specific
role
bindings
in
role
definition.
So,
if
you're
looking
for
having
specific
roles
within
your
kubernetes
clusters
that
you
need
to,
you
must
have
you
can
create
a
policy
around
that
right.
In
this
case,
I'm
just
gonna
start
with
a
certificate
policy.
B
B
A
B
Is
it
is
and
and
and
they
could
get
very
complicated,
very,
very
quick,
yeah?
The
good
thing
about
this
is
that
we
are
ever
so
changing
and
we
are
adding
more
and
more
policies.
We
will
also
have
a
standard
git
repo,
where
you
can
go
and
pull
policy
samples
just
like
I
pull
an
application
example.
Just
now
same
thing,
gonna
have
all
of
that
available
for
you
to
kind
of
build
all
these
policies
right,
because
we
don't
want
to
limit
you
to
the
standards
that
we
offer
out
of
box.
B
We
want
you
to
kind
of
implement
your
own
standards.
If
there
are
certain
specific
things
that
your
cluster
must
have,
then
you
can
go
and
define
those
there
as
well,
so
I'm
gonna
also
do
a
cluster
binding.
So
you
can
do
the
cluster
binding
a
couple
of
different
ways.
You
can
bind
this
by
a
specific
cloud,
so
if
obviously
I
have
all
my
clusters
right
now,
I
am
alone.
I
can
bind
it
to
that.
B
I
can
mine
it
to
my
labels,
so
my
environment
equals
dev
or
by
bender
right
or
by
me,
so
you
can
define
that.
Whichever
way
you
like,
in
this
case,
I'm
just
gonna,
keep
it
with
my
environment,
equals
that
and
so
notice
here,
that
you
have
the
ability
to
enforce
or
inform
that
policy
so
by
the
fault.
I
always
leave
it
as
inform
when
I'm
creating
policies,
because
I
want
to
make
sure
that
you
know
I
I
see
this
violations
before
I
actually
go
and
change
them
right
pretty
soon.
B
We
will
be
implementing
some
kind
of
approvals
for
this
too
right
now,
it's
just
kind
of
open
without
really
necessarily
having
approvals
right,
but
we
will
have
approvals
here
very
shortly
cool.
So
just
like
that,
I
created
a
policy
right.
That's
going
to
look
at
my
my
certificate
for
my
default
namespace
right.
So
obviously
this
is
gonna.
B
Take
a
little
bit
to
kind
of
go
through
and
kind
of
scan
it
right
and
see
if
I
have
any
kind
of
violations,
but
you
can
also
see
the
yamo
of
that
violation
here,
so
that
same
yeah
mala
we
saw
earlier
when
we
were
building
it.
I
can
go
in
here
and
kind
of
click.
The
edit
button
and
I
can
change
my
remediation
action.
B
For
example,
if
I
wanted
to
or
I
can
change
any
kind
of
configuration
within
here
and
submit
it
so
very
easy
to
kind
of
change
and
move
these
policies
boom,
look,
it
already
found
a
problem
with
your
cluster.
So,
of
course
your
cursor
is
already
not
compliant.
So,
let's
see,
let's
see,
why
is
not
compliant?
B
B
B
We
can
see
here
that
the
API
version
for
the
specific
it's
it's
compliant
there,
but
it's
not
compliant
for
this
policy.
Example
Oh
certificate
policies,
the
certificates,
policy
yeah,
it's
not
compliant,
so
you
can
kind
of
go
through
and
actually
fix
it
right.
So
we
can.
We
can
actually
make
this
and
enforce
and
actually
fix
it
right.
Look
it
just
became
compliant.
B
B
So
it
took
a
second,
but
now
it's
it's
it's
compliant,
so
you
can
see
one
from
red
to
green,
so
it
took
a
second
there,
but
you
can
kind
of
see
here
again
what
those
violations
that
is
kind
of
looking
for
right
and
I
have
you
know:
I
have
another
environment
here
that
has
a
few
more
clusters
and
cluster
violations.
So
let's
kind
of
show
you
that
that
way,
you
can
kind
of
see
this.
B
But
if
I
look
at
my
governor
risk
here
for
these
clusters,
I
see
I
have
a
lot
more
violators
in
here
right.
You
can
actually
see
here.
I
can
see
what
some
of
the
this
violations
are.
So
you
can
see
what
my
clusters
are
when
the
rule
violation
is
right.
So
this
is
a
policy
certificate
violation
right
if
I
go
deeper
into
it.
So
if
I
go
into
the
the
clusters,
you
can
see
what
it
shows
you
each
individual
cluster
that
actually
has
a
violation.
B
So
you
can
see
you
know
and
what
those
violations
are
right.
So
you
can
actually
see
the
policies
and
see
what
those
violations
within
that
those
rules
are
so,
for
example,
in
this
case,
for
this
namespace
policy
I'm
having
they
should
have
a
prod
it,
then
that
prod
portion
of
that
is
missing
right.
That's
a
policy
that
I
created
just
through
can,
as
a
as
an
example,
we
can
see
also
a
role
binding
policy.
B
Here
we
have
a
specific
role
that
we're
missing
right,
so
it
gives
you
that
visibility
into
your
clusters
at
around
all
these
policies.
Right
and
again,
you
can
let
your
imagination
roam,
while
here
as
far
as
policies
and
how
what
kind
of
policy
pretty
cool
alright.
So
that
is,
policies
now,
there's
two
more
things
and
I
think
we're
kind
of
getting
towards
the
end
here,
but
there's
two
more
things
that
I
kind
of
want
to
talk
about,
and
that
is
the
visual
web
terminal.
B
So
the
visual
web
terminal,
you
can
either
open
it
within
the
Chrome
browser,
so
I'm
going
to
just
open
it
here
as
the
name
States,
it's
a
visual
web
terminal,
so
you
can
actually
perform
OC
and
cube
CTL
commands
from
here.
One
of
the
first
things
that
I
like
to
do
about
this
because
I'm
all
about
the
darkness
so
I
like
to
set
my
dark
right
and
we
all
love
this
pretty
standard
I
can
actually
do
things
like
cube
CTL
get
namespaces.
B
It
can
show
me
all
of
my
namespaces
they're
available
for
my
cluster
and
the
beauty
of
this
is
that-
and
this
is
why
it's
called
visual
right
I
can
actually
go
and
click
into
this
and
it
will
automatically
generate
the
command.
So
you
can
kind
of
see
here
at
the
bottom.
It
generated
that
command
for
me,
and
it
brings
me
all
of
those
resources
within
that
namespace.
So
I
can
see
what
my
me
resources
are.
So
you
can
see
here.
I
have
three
pods.
B
If
I
click
on
those
pods,
it
shows
me
what
those
pods
are.
I
can
go
and
click
on
those
and
see
specific
conditions.
I
can
also
see
what
those
containers
inside
of
it
are
right.
So
you
can
kind
of
see
here
the
logs
for
that
specific
container,
so
think
about
when
you're
trying
to
troubleshoot
any
issue
within
your
kubernetes
environments
right
how
awesome
it
is
to
just
be
able
to
kind
of
we
are
leaving
the
tool.
B
B
B
This
is
part
of
the
visibility
type
of
use
case
that
we
talked
a
little
bit
about
for
the
IT
operations
perspective
right.
So
if
you
wanted
to
kind
of
look
and
see
how
many
resources
have
I
have
available
for
a
specific
cluster
right,
so
I
can
actually
go
through
and
see
creating
the
last
hour,
so
I
can
see
all
of
the
resources
that
have
been
created
within
the
last
hour.
Obviously
this
is
a
brand
new
environment.
I
created
a
bunch
of
stuff
with
everything
from
scratch.
Look
at
this.
I
can
see
all
of
my
resources.
C
C
B
B
Acm
resource
at
that
point,
and
so
now
one
that
once
it
became
and
they
see
him
then
then
you
can
kind
of
see.
All
of
that
and
again
you
can
see
here
all
of
the
things
that
we
can
kind
of
look
through
right.
So
we
can
look
at
you
know
finding
resources
where
the
kubernetes
is
very
complicated,
I
mean
you
can
see
all
of
these
things
that
we
have
created
within
the
past
hour
and
again
it's
it's
unbelievable
right.
I
can
see.
All
of
my,
for
example.
Let
me
pick
one
here:
I,
don't
know.
B
Right,
so
you
can
actually,
it
will
actually
maximize
this
and
show
you
all
of
the
related
images
and
you
can
go
and
click
on
those
resources
and
go
dive
deeper
and
look
at
the
yeah
mo.
So
this
was
probably
about
about
example,
but
let's
see
if
I
can
find
a
good
example
being
able
to
see
those
resources
but
think
about
being
able
to
kind
of
look
at
and
modify.
So,
let's
look
at
a
replica
set,
for
example,
more
for
the
cluster.
You
can
see
here
all
of
you,
yeah
mo.
B
You
can
actually
go
and
edit
this
directly.
So
if
you're
troubleshooting
issues
for
applications
or
clusters
or
anything
like
that,
the
search
is
a
really
powerful
tool
to
be
able
to
kind
of
soar
through
and
and
kind
of,
go
through
all
the
noise
right,
because
there's
a
lotta
noise
within
kubernetes
right.
If
you
want
to
sake
and
look
at
the
color
workloads,
you
can
kind
of
see
all
of
the
workloads
that
are
available.
I
can
see
all
of
my
related
endpoints.
For
example.
B
I
can
see
all
of
my
related
clusters
related
parts
right
and
you
can
actually
create
all
these
searches
so
notice
that
this
is
just
like
a
free
one,
a
free
form,
but
it's
like
a
filter
based
feel.
Then
you
can
kind
of
select
multiple
filters
and
apply
these
filters
and
kind
of
build.
Your
search
that
way
we
provide
you
with
three
main
searches.
We're
gonna,
obviously
have
more
and
more
as
the
product
kind
of
expands
and
grows.
B
You
can
also
save
your
own.
So
if
you
create
your
own
policy
and
you'd
like
to
have
your
own
policy,
you
can
go
ahead
and
create
and
save
that,
and
it
would
be
a
policy
here,
but
you
can
have
obviously
all
those
save
searches
here
so
say
if
I
want
to
see
all
the
clusters
within
my
local
cluster
right.
So
all
my
resources
within
my
local
cluster,
it
will
show
me
all
of
that
they're.
B
So
fantastic
used
to
be
able
to
kind
of
see
all
of
that
so
so
yeah
that
it's
a
pretty
good
overview
here
of
ACM.
You
can
see
here
the
the
overview
page
now
as
I
started
to
kind
of
build
it
out.
So
when
we
first
kind
of
started,
obviously
we
have
like
a
clear
view
of
the
what
we
had
obviously
have
anything.
B
B
So
it's
just
another
way
for
you
to
be
able
to
kind
of
go
through
and
kind
of
navigate
there.
You
can
also
see
the
topologies,
so
not
only
the
topology
from
the
application
perspective,
but
also
the
topology
of
the
clusters.
So
you
can
take
a
look
at
my
topology
on
my
def
cluster
right.
You
can
see
my
applications
say
my
select
my
application
here
right
and
still
kind
of
working
through
I
started
right.
B
It's
about
35
minutes
ago
that
it's
starting
and
it's
deploying
all
of
that,
and
then
you
can
kind
of
see
all
of
my
policies
as
well
right.
You
know
whenever
I
select
those
policies-
and
you
can
kind
of
see
it's
just
a
visual
representation
of
that
right,
yeah,
so
pretty
straightforward,
pretty
easy,
yeah
I
think
you
know
I.
Think
I
think
this
is.
This
is
a
an
amazing
product
that
really
will
really
help
you
to
kind
of
be
able
to
kind
of
kind
of
get
that
control
over
your
kubernetes
environment
and
your
multi
clusters.
Yeah.
C
A
Read
that
that
we
thought
that
we'd
have,
you
know
some
few
large
clusters
and
it's
kind
of
evolved,
and
you
know
the
way,
the
not
the
ease
and
the
way
we've
been
able
to
make
testing
on
kubernetes
a
little
bit
faster.
The
the
multi
cluster
thing
has
become
a
big
deal
because,
instead
of
just
having.
C
C
A
Exactly
where
your
money
is
being
wasted
or
could
potentially
could
be
gained,
it's
gonna
be
a
really
really
awesome
hat
on
when
that
gets
a
year.
Wow
but
yeah
having
this
pane
of
glass
to
manage,
not
just
clusters,
but
applications
as
well
as
compliance
is
vital
right,
like
things
get
convoluted
and
confusing
very
quickly.
You
saw
that
just
with
two
clusters,
we
had
hundreds
of
images
available
to
us
yeah.
C
A
Know,
and
and
and
if
if
we
need
a
search
function
across
all
of
our
clusters,
something
like
that
doesn't
natively
exist
right,
we're
knitting
in
native
kubernetes
land
right,
like
you're,
putting
together
a
string
of
commands,
essentially
at
that
point
right
and
and
you're
hoping
you
get
all
the
outputs
correct
when
you
pull
all
those
api's.
So
having
azm
in
your
environment,
I
think,
is
a
very
wise
decision
having
something
along
the
lines
of
policy
management.
I
think,
is
a
even
wiser
decision,
because
the
application
yeah.
B
A
If
you
want
your
applications
to
be
managed
consistently
across
an
entire
fleet
of
clusters,
as
well
as
having
policy
applied
to
it,
but
that's
that
is
a
bear
right
like
doing
that
on
your
own
is
going
to
be
a
bear
and
potentially
rife
with
mistakes.
So
you
know
having
a
cm
here.
It's
got
your
back
right
like
it's
gonna
tell
you
what's
up
if
something's.
A
B
C
B
Feel
like
I
feel
like
Joe
Rogan
now,
but
but
yeah.
We
we
have
this
videos
that
we're
putting
out
please
subscribe
to
the
channel.
It's
called
Red
Hat
videos
and
we
have
the
advanced
cluster
management
playlist.
That
kind
of
covers
some
of
the
stuff
that
we
talked
about
today
from
this
delation
to
putting
your
clusters
application
lifecycle
policy
overview.
We're
gonna
be
coming
out
with
more
videos
like
api's
and
how
to
interact
with
api.
So
you
extend
the
product
outside
of
what
we
provide
right.
A
B
A
B
C
A
And
you
know
hit
parts
and
pieces,
please
feel
free
to
you
know
like
if
you
want
Jimmy
or
somebody
else
or
anybody.
You
know
someone
on
the
ACM
team
to
come
on
a
demonstrate
policies
better
or
you
know
we
already
had
the
suggestion
of
having
a
stream
on
using
ACM
to
migrate
to
forex
right
like
definitely
to
find
somebody
to
help
me
with
that
Jimmy.
If
you
go.
B
C
A
B
A
Were
six
people
away
from
hitting
a
thousand
y'all
six
people
away
from
hitting
a
thousand
he's
hit
that
heart
button?
That's
all
I'm
gonna
be
doing
today
is
like
asking
and
begging
and
bleeding
people,
because
today
is
the
last
day
of
June,
and
we
are
so
so
so
close
yeah.
So
like
I'm,
super
excited
and
folks
in
chat
that
are
talking
about
Go
Go
is
actually
one
of
the
few
languages
that
I
know
and
was
able
to
pick
up
without
having
a
big
CS
background
at
all.
A
A
A
One
out
there,
the
up-and-comer
is
rust.
These
days,
I
hear
more
about
rust,
everyday.
It
seems
like
so
yeah
or
we're
out
here
we're
here
to
help
you
with
whatever
runtimes
and
applications.
You
need
awesome,
so
Anna
Randolph
says
they
are
only
one
hour
and
30
minutes
away
from
July
1st,
so
Narenda.
If
you
could
get
six
people
to
forget
that
happening
in
the
next
30
minutes,
I
could
probably
take
the
rest
of
the
day
off.
A
A
Is
it
better
to
do
things
with
vanilla,
Kate's
versus
OpenShift
ballerina?
Has
it
been
on
the
rise
ballerina
I
heard
about
a
few
years
ago?
I
think
it
was
cute,
calm,
20
18
s
kind
of
when
they
hit
their
peak
I
feel,
like
maybe
I,
don't
know
it's
it's
out
there.
It's
useful
I'm
not
going
to
knock
it
or
anything,
but
it's
not
widely
adopted
like.
B
Besides,
looking
at
the
ability
of
obviously
what's
going
to
be
developed
for
that
platform
later
down
the
line,
you
also
got
a
look
at
the
support
ability.
What
kind
of
support
do
you
have
yeah
having
an
opus,
an
open-source
community?
It's
fantastic?
Obviously
we
have
that
but
being
able
to
kind
of
pick
up
the
phone
and
when
there
is
a
major
outage,
a
major
problem
it
kind
of
plays
into
it.
So
when
you're
evaluating
different
type
of
communities,
different
type
of
you
know
competitors
that
exist
out
there.
B
You
want
to
make
sure
that
you
also
look
at
this
ability.
What
kind
of
support
do
I
get
with
this
right
right?
Because
if
you
don't
have
support,
you
can
have
the
best
distribution
out
there,
but
we
know
how
quickly
this
market
moves
yeah.
If,
if,
if
you
don't
have
new
features,
new
implementations
new,
then
what
like
you're
gonna
stay
still
and
then
you're
gonna,
be
you
know,
within
six
or
months
to
a
year,
you're
gonna
be
looking
at
migrating
to
something
else.
So
right
you
got
it.
B
A
You
know
I,
think
you
know
we
have
multiple
answers
of
the
vanilla,
kubernetes
question
Jaffar
pasted
the
best
answer,
I
think
to
the
the
question
which
is
his
Enterprise
kubernetes
blog
post
there's.
There
is
so
much
to
clout,
Vernon
applications
in
a
cloud
native
manner
that
just
kubernetes
is
never
enough
right.
Like
that's
just
the
beginning,
right
like
when
Kelsey
Hightower
says:
kubernetes
is
not
the
destination,
he
is
100%
correct
and
you
know
that
is
the
kubernetes
is
just
the
beginning.
A
It
is
a
bunch
of
API,
has
any
animal
that
created
control
plane
for
you
to
manage
applications
and
workloads
and
sort
of
infrastructure
services
right
like
so
there's
so
much
that
you
can
just
do
with
kubernetes,
but
if
you
go
and
you
install
vanilla,
kubernetes
from
like
github.com
slash,
kubernetes
kubernetes
or
I
spend
plenty
of
my
time.
You're
not
gonna,
get
monitoring
you're,
not
gonna,
get
logging
you're,
not
gonna,
get.
You
know
like
a
clear
life
cycle.
Migration
path
forward
right,
like
push
button
upgrades,
aren't
a
thing
right
like
it's.
A
A
But
if
you're
really
trying
to
get
started
with
I
want
my
applications
running
in
containers
on
a
cloud
native
workload
and
and
and
moving
fluidly
flow
out
clusters,
and
things
like
that,
you're
gonna
need
a
shortcut
and
the
best
shortcut
on
the
market
right
now
is
read
that
open
shift.
Then
I
can
say
that
in
all
honesty,
because
it's
my
opinion
and
I
dip,
eclis
don't
lie
to
people
so
yeah,
there's,
there's
a
reason:
I
work
at
Red,
Hat
for
kubernetes,
stuff
and
and
not
anyplace
else.
A
A
B
C
A
Jamie,
thank
you
so
much
for
joining
us.
Everyone.
Thank
you
so
much
in
chat
today
the
chat
is
so
lively.
Today
everybody
joining
us
live
everybody
that
followed
us.
You
know
this
is
probably
the
last
broadcast
before
we
hit
a
thousand
followers.
So
how
about?
Oh?
How
about
it's
you?
On
top
of
gates?
We
have
plenty
of
shirt.
We
have
a
service
mesh
product
on
top
of
openshift.
A
B
A
B
A
A
You
know
all
of
this
has
been
bootstraps,
and
you
know
just
kind
of
you
know
we're
very
much
in
start-up
mode.
I
have
a
meeting
I
think
you
know
later
this
week
with
somebody
that
is
a
redhead
er
that
has
like
a
really
popular
redhead
or
twitch
channel
like
on
their
own
and
like
emailed
me.
The
other
day
is
like
Chris
there's
like
a
bunch
of
things,
you're
doing
wrong.
A
A
People,
like
you
know
what
was
a
Jeff
Garlin.
He
put
out
a
blog
yesterday
about
you
know
what
he
learned
from
doing
a
live
YouTube
series
because
he's
taken
the
coronavirus
time
to
do
ansible
training
for
free
on
his
youtube
channel.
Oh
yeah,
yeah,
so
yeah,
so
like
all
that
ansible
training
is
out
there
for
free
on
his
YouTube
page,
but
yeah
he
put
out
there
he's
like
I,
am
NOT
going
to
change
over
to
being
like
a
YouTube
rockstar
any
time
soon
keep
your
day
jobs.
Kids!
It's
not
going
to
make
you
money.
C
C
A
C
A
B
I
mean
there's
always
there's
more
than
one
way
to
skin
a
cat
right
every
time.
So
it's
it's.
Why
would
you
choose
one
to
the
other?
That's
a
very
like
generic
question.
We
need
to
you
know
kind
of
look
into
see.
Okay,
what
exactly
is
you're
trying
to
migrate
within
that
opens,
I
mean
if
you're
just
trying
to
migrate
workloads
and
yeah
sure.
But
you
know
if
you
have
applications,
you
want
to
have
more
standards.
You're
gonna
have
then
that's
where
we
come
in
right.
So.
C
A
B
B
We
lived
as
a
feature
within
MCM,
and
so
it
made
more
sense
as
we
look
at
you
know,
kind
of
the
portfolio
and
kind
of
rationalizing
and
making
things
more
seamless
between
the
companies
to
bring
ACM
into
the
Red
Hat
side.
Because,
obviously
you
know
we
had
OpenShift
a
managed
over
shift,
so
it
made
it
made
sense
to
just
have
it
be
part
of
our
portfolio
right?
Sorry,
so
what's
the
difference
between
the
two
currently
or
we
see
nothing,
we
basically
took
MCM
from
from
you
know.
B
We
took
that
feature
that
existed
within
MCM
and
brought
it
as
an
individualized
product
within
the
Red
Hat
world
and
so
MCM
when
you
took
MCM
you're
talking
about
more
management
at
even
higher
level,
so
you're
talking
about
managing,
not
only
your
your
kubernetes
for
close
but
you're.
Also
talking
about
managing
your
utilization
you're
talking
about
managing
your
bare
metals,
everything
right
so
MCM
is
this
huge
tool
that
manages
like
overall,
like
a
bunch
of
other
things
outside
of
just
kubernetes.
B
So
that's
the
main
difference
there
that
you
know.
If,
if
you
are
a
customer
of
IBM
today
and
and
have
MCM,
then
great,
you
already
have
a
cm
right,
awesome
right.
Otherwise
you
know
you
can
just
buy
the
product
standalone
from
us.
So
it's
just
about
choices,
it's
about.
If
you
have
one,
if
you
need
more
at
a
higher
level
kind
of
management
like
again
looking
at
your
whole
data
center
right,
no
just
a
portion
of
it,
then
then
yeah
and
see
it
might
be
the
right
product
for
you.
B
A
C
A
So
I
think
the
the
I
mean
this
is
where
I
think
the
IBM
acquisitions
already
kind
of
paid
off
for,
read
and
write
like
anyway,
you
know
having
the
multi
cluster
application
man
or
having
the
multi
cluster
management
tool
by
itself
or
something
you
already
need
it.
But
when
you
look
ahead,
Oh
ACM
is
not
just
multi
cluster
management.
It's
application
management,
it's
policy
management.
It
is
cluster
management
and
it
is
all
on
one
pane
of
glass.
A
A
A
And
I,
are
you
know,
we've
been
it
ready
for
you
know
about
the
same
amount
of
time,
and
you
know
talking
to
they're,
just
ACM
folks
that
I
have
I
feel
like
they've
been.
You
know,
welcomes
very
graciously
because
we
do
understand
the
situation
that
they
were
in
right,
like
acquisitions
are
not
fun
and
if
all
the
sudden,
you
have
to
move
companies,
that's
weird
and
unexpected.
B
A
A
outsi
run,
run,
see
and
cata
containers
see,
run
and
run
CRO
CI
compliant
image,
specs
I
guess
cata
is
too
now,
but
see
run
is
written
in
C
run,
C
is
written
and
go
see,
run
is
for
those
high
performance,
computing
workloads
run
C
is
the
typical
default
container
engine
or
container.
You
know
man
and.
C
A
Ter
engine
under
the
hood
of
most
containers
these
days
build,
is
a
tool
to
build
containers.
Yes,
red
head
made
that
it
is
open
source
but
is
not
specific
to
open
shifts.
Open
shift
can
run
any
OC.
I
compliant
container
out
there,
so
whatever
engine
you
want
to
throw
at
it's
whether
you're
managing
your
containers
at
pod,
man
or
docker,
those
are
all
OCI
compliant.
You
can
throw
them
at
open
shift
and
they
will
work
just
fine
yeah.
A
So
if
you
have
any
questions
about
container
runtimes
feel
free
to
reach
out
to
me
at
chris
short
on
twitter,
see
short
at
Red
Hat
comm
I
can
provide
you
container
information
all
day
long
general
info.
At
this
point,
eg
I
have
an
overshift
cluster
C
ICD,
deploy
to
e
KS
segment,
seamlessly
bill
detect
on
pipeline
to
help
you
with
that.
That's
the
best
general
info
I
can
give
you
on
this
stream.