►
Description
How often do you release new versions of your microservices deployed in OpenShift? At Dynatrace, 600+ developers release new features and functionality on a bi-weekly basis. This allows us to match the speed of the cloud and quickly react to this fast-changing technology landscape.
How cool would it be to get this fresh doze of monitoring automatically deployed to your OpenShift clusters?
In this talk, we are going to explore how you can operate your monitoring solution with zero manual effort in large-scale environments. Join this session if you want to learn about best practices for monitoring OpenShift with Dynatrace.
A
A
A
So
we
are
dynaTrace,
we
do
this
twenty
six
times
a
year,
so
we
do
have
a
team
of
six
hundred
plus
developers
releasing
every
two
weeks.
New
features,
new
capabilities
that
are
available
for
our
customers,
and
so
we
started
out
in
2011
with
releasing
only
two
major
releases
per
year
and
when
2016
came
came
along,
we
were
able
to
do
26
major
releases
of
our
dynaTrace
sauce
offering
and
do
13
major
releases
per
year
of
our
dynaTrace
managed
of
our
dynaTrace
managed
offering.
A
So
we
are
full
fully
engaged
to
to
our
DevOps
journey
and
we
are
going
towards
no
ops
culture
with
within
our
organization.
And
let
me
ask
you
another
question,
so
how
cool
would
it
be
if
you
got
this
fresh
dose
of
monitoring
automatically
deployed
to
your
openshift
clusters,
so
I'm
very
proud
to
introduce
today
the
dynaTrace
one
agent
operator?
A
So
you
may
have
heard
Chris
Morgan
talk
about
the
operator
concept
during
the
keynote
in
in
the
afternoon,
and
it's
it's
very
great
so
before
diving
into
the
details
of
the
one
agent
operator,
let's
have
a
step
back
and
talk
about
operators
in
kubernetes,
so
like
Chris
Morgan
described
it.
Operators
in
kubernetes
allow
you
to
put
operational
knowledge
into
software
operators
are
available
since
2016
and
allow
you
to
automate
tasks
that
have
to
be
done
manually
by
humans.
A
Otherwise,
and
last
week
during
cube
con,
the
operator
framework
was
announced
which
provides
developers
with
an
operator
SDK,
but
also
with
a
lifecycle
management.
So
with
the
operator
framework,
it
is
now
easier
to
build
and
provide
an
operator,
and
dynaTrace
is
one
of
the
very
first
partners
to
have
such
an
operator
for
the
dynaTrace
one
agent
ready.
A
A
So,
let's
have
a
closer
look
at
the
value.
Add
the
one
agent
operator
brings
to
you.
So
the
diner
is
one
agent
operator,
on
the
one
hand,
manages
dynaTrace
one
agent
deployments,
so
the
operator
allows
you
to
roll
out
the
one
agent
onto
your
OpenShift
cluster
notes,
and
it
also
allows
you
to
control
in
a
very
fine-grained
way
to
what
notes
the
one
agent
should
be
deployed.
A
So
in
in,
like
one
sentence,
the
one
agent
operator
ensures
that
you
are
monitoring
your
openshift
cluster
with
the
latest
and
greatest
one
agent
version,
and
as
of
today,
the
one
agent
operator
source
code
is
also
available
on
a
github
repository.
So
if
you're
interested
in
the
details,
how
to
how
we
built
the
one
agent
operator
check
out
the
github
repository
and
you're
also
invited
to
contribute
to
engage
into
a
discussion
with
us,
so
just
check
out
our
github
repository
and
speaking
of
github
repository
and
in
source
code
of
the
one
agent
operator.
A
Let's
talk
about
the
details,
how
it
actually
works.
So
in
a
first
step
or
on
the
one
hand,
side,
the
one
agent
operators
operator,
watches
out
for
custom
resources
of
type
one
agent.
The
one
agent
operator
also
takes
care
of
one
agent
deployment
via
a
daemon
set.
And
last
but
not
least,
the
one
agent
operator
updates
the
one
agent
to
the
latest
version
available
and
therefore
the
one
agent
operator
constantly
queries
the
dynaTrace
API
to
check.
If
there
is
a
new
version
available
for
a
given
deployment.
A
A
So
I
have
prepared
a
short
video
that
will
show
you
or
that
will
show
how
the
one
agent
this
operator
is
rolled
out
to
an
open
shift
cluster
and
what
you
ultimately
get
when
the
one
agent
has
been
deployed
to
the
open
shift
cluster.
So,
let's
quickly
switch
to
the
video.
So
what
you
see
here
is
as
a
first
step.
We
do
clone
the
one
agent
operator
get
repository
to
have
it
also
available
on
the
machine.
A
We
then
follow
the
guidelines
that
are
available
on
the
github
repository
to
install
the
one
agent
operator
you
just
copy
and
paste
all
the
commands,
and
then
we
check
the
deployment
we
check
if
the
parts
that
we
are
looking
for
are
available.
In
that
case,
we
are
looking
for
the
dynaTrace
one
agent
operator.
A
If
it
is
available
and
as
you
can
see,
it
is
available
on
the
cluster
and
then
we
again
check
for
the
pots.
So
for
the
pots
there,
the
one
agent
operator
is
already
ready,
but
some
further
pots
are
still
kind
of
like
spun
up.
So
we
do
the
check
another
time
and
wait
when
the
pots
come
to
play,
and
then
we
finally
see
that
all
the
pots
are
available.
A
And
now
we
switch
to
the
related
dynaTrace
environment,
where
we
do
have
set
up
a
multi
cloud
environment
and
then
we
focus
on
the
openshift
nodes.
And
then
we
see
that
we
are
currently
in
an
unmonitored
state.
But
if
we
do
a
reload
and
be
a
little
patient,
then
we
see
that
now
the
OpenShift
nodes
are
available
in
the
dynaTrace
environment.
A
So
we've
seen
how
easy
it
is
to
deploy
the
one
agent
operator
now,
let's
think
about
what
it
means.
So
from
our
perspective,
and
also
when
talking
to
Chris
Morgan,
we
think
that
operators
and
the
one
agent
operator
so
having
dynaTrace
together
with
a
rat
head
OpenShift,
it's
like
the
foundation
for
a
no
ops
tourney,
and
it
it
also
is
a
big
big
first
step
towards
self-driving
IT.
So
it
focuses
on
automation.
So
we
are
dynaTrace
think
that
automation
is
key.
A
A
That
is
a
perfect
step
in
that
direction,
and
I
already
mentioned
that
you
should
definitely
head
over
to
your
booth.
But
what
you
also
should
do
is
you
should
definitely
check
out
the
dynaTrace
free
trial,
because
we
also
think
that
seeing
is
believing
so
try
it
out
for
yourself,
maybe
use
the
one
agent
operator
to
deploy
the
one
agent
onto
your
open
shift
cluster
and
check
it
out.
For
for
your
own
environment,.