►
Description
Join us for Kubernetes Forums Seoul, Sydney, Bengaluru and Delhi - learn more at kubecon.io
Don't miss KubeCon + CloudNativeCon 2020 events in Amsterdam March 30 - April 2, Shanghai July 28-30 and Boston November 17-20! Learn more at kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects
Operators simplify management of complex applications on Kubernetes. They are usually written in Go and require expertise with the internals of Kubernetes. But, there's an alternative to that with a lower barrier to entry. Ansible is a first class citizen in the Operator SDK. Using Ansible frees up application engineers, maximizes time to automate and orchestrate your applications, and doing it across new & existing platforms with one simple language. Here we see how.
A
B
B
Yes,
you
are
good
to
go
okay,
great
excellent,
so
we're
going
to
be
covering
today
is
you
know
just
a
little
bit
of
background
about
what
are
operators
for
those
who
may
not
be
as
familiar
and
why
you'd
want
to
use
them?
And
then
why
would
you
want
to
use
ansible
to
build
them?
And
how
do
you
even
do
them?
So
you
know
why
would
you
want
to
build
them
using
a
spool
because
you
know
isn't:
isn't
ansible?
B
So
what
most
a
lot
of
people
don't
realize?
Is
that
really
ansible
and
kubernetes
are
quite
a
natural
fit
and
have
a
lot
of
similarities
in
a
number
of
ways?
You
know
both
of
them
help
make
hard
things
easier
through
automation
and
orchestration
and
they're
both
very
active,
widely
used
open-source
projects,
and
last
year
we
were
I
think
we
were
six
and
seven
on
the
github
octo
verse
report
when
it
came
out
for
activity.
So
we
were,
you
know
the
kubernetes
and
ansible
projects
were
right.
B
There
neck-and-neck
in
the
you
know
in
the
top
ten,
so
we
both
have
very
vibrant
communities
working
together
to
solve
common
problems.
You
know
we
have
cube
con
coming
up
and
you
know
it's
going
to
be.
You
know
from
I'm
hearing.
You
know
twelve
thousand
people
gathering
there
I'll
be
there
in
the
Red
Hat
booth
for
any
of
you
who
want
to
stop
by
and
say,
hi
I'll
be
talking
about
this
there
and
the
other
thing
is
that
they
both
use
Yammer
to
describe
this
desired
state
of
the
world.
They're
both
desired
state
engines.
B
What
you
do-
and
this
is
something
I
hopefully
I'll-
be
able
to
show
you
in
the
demos
that
you
could
template
eyes
this
your
definition
files
and
how
you
had
you,
deploy
and
manage
things
in
kubernetes
if
inlining,
the
definition
file
like
I
showed
in
the
last
slide.
Isn't
your
thing?
You
can
also
do
something
like
this.
B
In
fact,
a
lot
of
people
do
this,
and-
and
we
actually
have
it,
set
up
this
way
in
our
demo
operator
that
I'll
show
later
you
can
keep
the
definition
file
separately
as
a
template
or
as
a
yeah
Moe
file
and
read
them
right
into
your
your
playbook
and
feed
them
into
the
kate's
module
to
get
passed
on
to
the
kate's
api.
So
it's
a
nice
little
piece
of
syntactic
sugar.
You
can
use
to
manage
your
files
differently.
If
you
don't
want
to
keep
a
a
playbook,
keep
all
this
in
a
playbook.
B
You
can,
you
know,
keep
it
separately
as
files
and
manage
them
accordingly,
alright.
So
that
was
a
little
bit
of
the
similarities
that
there
are
between
kubernetes
and
ansible
and
how
they
can
work
together.
You
know,
let's
do
a
quick
review
of
what
our
operators,
what
our
kubernetes
operators
for
those
who
may
not
be
as
familiar
with
it
or
just
to
set
some
context
here.
B
But
what
do
you
do
when
you
have
to
use
state
when
your
application
needs
this
special
handling
and
in
how
you
manage
upgrades?
How
you
manage
scaling
events,
how
you
manage
failures,
things
of
that
nature.
Kubernetes
cannot
in
and
of
itself
capture.
All
of
that
operational
knowledge
in
order
to
manage
that
application,
and
that's
where
operators
come
in
because
staple
you
know
that
that
statefulness
is
hard
and
is
unknown
to
kubernetes
and
operators.
Let
you
bring
that
extra
smart
to
what
kubernetes
can
do
so
like
say,
operators
are
there
to
manage
complex,
kubernetes
applications.
B
They
can
encode
this
human
operational
knowledge.
They
can,
you
know,
handle
things
such
as
patches
upgrades.
You
know,
scaling
events,
things
of
that
nature
and
to
do
it
in
a
kubernetes
native
way
that
we
can
just
you
know,
do
it
right
on
the
cluster
itself,
so
these
operators
are
purpose-built
for
your
specific
applications
and
services
to
give
kubernetes
that
XR
smart
and
to
not
just
handle
installing
and
setting
up
your
application,
but
do
all
the
day
management
of
what
happens.
You
know
managing
the
entire
lifecycle.
B
So,
without
without
operators,
what
happens
is?
Is
we
get
and
we
have
these
special?
You
know
these
stateful
applications
that
require
this
extra
extra
knowledge,
expecially
handling
you,
you
end
up
in
a
reactive
mode,
without
operators
that
you
have
to
continually
check
for
anomalies
or
for
events
happening
in
your
cluster
and
alert
a
human
if
something
happens
so
that
they
can
respond.
So
one
of
your
operators
has
to
deal
with
possibly
intervening
and
it
could
be,
it
could
take
them
minutes
could
take
them
hours.
B
It
may
require
them
getting
up
in
the
middle
of
the
night
to
deal
with
this
stuff.
So
that's
less
than
ideal.
With
an
operator
you
get
to
be
more
proactive,
you
can
you
know
because
it's
running
on
the
cluster
and
it
is
continuously
adjusting
for
that
optimal
state
and
monitoring.
What
is
the
the
current
state
of
what's
happening
on
the
cluster?
It's
able
to
react
within
seconds
and
make
the
adjustments
and
perform
the
operations
needed
to
keep
the
application
healthy
and
running
as
expected.
B
B
Then
the
operator
itself
is
just
a
controller,
and
that
has
two
special
parts
to
it
or
or
two
functions
going
on.
One
is
for
the
controller
to
watch
events
happening
on
the
kubernetes
cluster,
for
the
resources
that
your
application
is
using
and
then,
when
something
does
occur,
to
do
something
called
a
reconcile
loop
and
what
a
reconcile
does
is
is
take
the
actions
necessary
to
get
the
application
in
the
desired
state.
It
should
be
in
when
the
state
changes,
and
so
it
so
what's
happening.
B
According
to
the
operational
knowledge
that
you
fed
into
it,
so
the
operator
just
to
take
a
step
back
for
a
second
here.
Operators
are
part
of
come
from
the
operator
framework.
This
is
something
that
core
arrests
began
and
then,
when
they
joined
the
Red
Hat
family
we've
continued
to
invest
in
and
and
advance
further.
There
are
three
parts
to
this
operator
framework
this
this
toolkit
to
build
and
manage
operators
on
any
kubernetes
cluster.
This
is
all
I
should
have
mentioned
this
earlier
on.
B
B
So
there
are
three
parts
to
it:
I'm
going
to
be
talking
mostly
from
here
on
out
about
the
operator
SDK,
which
is
what
you
would
use
to
build
your
operators
and,
and
specifically
the
part
of
the
operator
SDK
I'm
gonna
be
talking
about,
is
the
ansible
part
that's
built
built
into
that?
There's
also
implementations
for
doing
it
and
golang,
of
course,
and
then
also
of
some
limited
stuff
you
can
do
with
helm.
B
That's
what
there's
that's
there
for,
but
we're
gonna
be
focusing
on
the
operator
SDK
part
from
here
out,
but
that's
what
makes
up
the
operator
framework
it's
out
there
and
all
that
is
of
course,
we're
RedHat.
It
is
open
source
and
can
be
found
at
this
github
repo.
You
see
at
the
bottom
of
my
slide.
B
B
Well,
okay,
so
the
idea
is
we're
taking
a
lot
of
the
same
principles
that
have
gone
into
anta
Bowl
in
general
and
traditional
IT
space,
whether
it's
it's
it's
cloud
or
networking,
or
bare
metal
or
Windows
machines,
with
the
idea
of
making
things
easier
to
do
so.
Taking
this
the
you
know
doing
powerful
things
in
a
very
simple
way,
and
so
in
this
case
here
we're
trying
to
make
it
easier
to
deploy,
manage
these
kubernetes
applications,
but
do
it
in
that
nance
ansible
native
way.
B
This
will
let
you
iterate
faster
and
it'll,
make
maintenance
easier.
So
you
can
focus
your
time
on
other
things
that
require
your
attention
that
cannot
be
as
easily
handled
as
what
we
can
do
here,
as
I
already
showed.
Is
it
uses
declarative
state
definitions
just
like
Kate's
itself,
and
you
can
template
all
that
which
can
make
things
much
more
repeatable
and
reusable
than
the
standard?
Tooling,
that's
out
there.
So
it
can
really.
B
You
know
help
you
do
get
more
out
of
all
the
the
great
things
that
kubernetes
and
and
and
cloud
native
systems
can
do.
As
I
mentioned
earlier.
There's
three
ways
that
the
operator
framework
lets
you
develop:
operators,
there's
helm,
but
Helm's
limited
to
only
doing
what
you
see.
There
is
phase
one,
the
basic
installation,
ansible
and
golang
those
those
two
types
you
can
do:
the
entire
lifecycle
of
operators.
It's
one
of
the
things
that
I
get
a
lot
as
I
talk
to
customers
and
and
and
at
events
and
conferences.
B
A
lot
of
people
think
that
well
I'm,
somehow
going
to
be
limited
if
I
use,
ansible
and
I
really
need
to
use
golang
and
and
what
we've
found
is
in
the
people
that
are
writing.
Operators
with
ansible
is
that
that
that
it
can
do
pretty
much
everything.
There
is
going
to
be
that
very,
very
what
we
believe
small
edge
cases
where
you
really
need
to
get
into
the
and
and
very
closely
control
what's
happening
on.
B
The
cluster
indicates
API,
where
you
then
may
need
to
move
to
using
golang
itself,
but
for
the
vast
majority
of
use
cases
that
we've
seen
out
there,
ansible
has
been
able
to
handle
them
all
and
go
across
and
do
the
entire
lifecycle
of
that
an
operator
needs
to
manage
all
right.
So,
let's
take
a
little
bit
of
a
closer
look
at
how
an
operator
written
in
ansible
looks
so
this
is
a
another
version
of
the
a
diagram.
I
showed
a
little
bit
earlier
and
what's
different
is
that?
B
B
So,
for
example,
it
provides
a
reverse
proxy
and
that
proxy
takes
the
calls
coming
from
your
ansible
automation
and
adds
owner
references
to
it
and
that's
to
make
sure
that
garbage
collection
works
correctly.
It
does
a
fair
bit
of
aggressive
caching
so
that
you,
don't
you
know,
pound
your
Cates
API
proxy,
too
hard
and-
and
you
know,
essentially
create
a
denial
of
service
attack
on
your
own
kubernetes
cluster.
So
it's
doing
a
lot
of
things
like
that
and
that's
actually
written
and
go
so
it's
a
very,
very
efficient
operator
going.
B
The
other
thing
that
this
is
do
is
that
when
the
container
initializes
it
is
reading
in
that
watches
file,
so
it
knows
what
it
is
looking
for.
So
at
that
point
that
binary,
when
it
sees
that
an
event
happens,
it
will
then
look
at
what
was
defined
in
the
watch's
file
and
then
run
the
ansible,
playbook
or
role
that's
been
defined,
for
it
take
the
response
coming
back
from
ansible
itself
and
then
pass
that,
along
to
the
custom
resource,
to
update
the
the
status
of
your
of
your
operator.
So
events
are
happening.
B
B
All
right,
so
that's
that's
how
ansible
operators
work
developing
them
can
be.
You
know
quite
easy
and
we've
tried
to
make
this
as
frictionless
as
possible.
So
there's
a
few
steps
that
you
have
to
take
here.
You
can
get
the
operator
SDK
I,
said
completely
open
source
tool,
it's
available
through
a
number
of
different
ways:
I'm
using
a
macbook
here,
I
used
homebrew
to
install
my
copy
here.
So
what
you
do
to
get
started
is
use
the
operator
sdk
to
do
a
new
and
hand
it
a
few
pieces
of
metadata.
What
is
the
operator
itself?
B
B
One
thing
I
want
to
stress.
I've
said
this
once,
but
I
wonder,
I
think
it's
worth
repeating
again
here
is:
this
is
a
native
part
of
the
operator
SDK.
This
is
not
a
plug-in
or
some
extra
thing
that
you
need
to
add.
When
you
install
the
operator
SDK,
you
get
this
right
right
out
of
the
box.
So
at
this
point
what
will
happen
and
I'm
going
to
show
this
to
you
in
a
moment
in
in
the
demo?
Is
this
will
build
out
an
entire
project
for
you?
B
Not
only
will
it
create
the
skeleton
of
a
of
a
roll
to
write
your
ansible
automation,
but
it
will
also
create
deploy
files
for
you.
It
will
create
build
file
for
you.
It
creates
basic
tests
and
molecule,
which
is
a
testing
framework
for
ansible
content,
creates
a
whole
bunch
of
really
nice
things
that
really
get
you
up
and
running
quickly
to
developing
the
operator.
So
at
that
point
now
you
have
a
project
ready
to
go.
You
just
need
to
write
your
automation
with
ansible.
B
Whatever
those
steps
are
often
it's
going
to
be
using
the
kate's
module,
which
is
pretty
and
now
pretty
much
a
like
cube
control,
but
with
some
extra
ansible
things
to
it.
So
anything
you
can
do
with
a
cube
controller,
even
the
OC
command.
If
you're
an
open
shift
user.
You
can
use
that
module
for
to
get
things
done.
So
you
write
your
automation.
B
You
then
have
to
define
your
watch
file,
the
actually
in
all
actuality,
that
new
command
creates
a
watches
file
for
you,
based
on
the
inputs
you've
given
it
sometimes
you
don't
even
have
to
touch
the
watch's
file,
but
if
you
do
there's
already
one
started,
it's
a
pretty
straightforward,
small
little
gamma
file
that
you
have
to
edit
very
straightforward
thing
to
use
and
and
and
manage
at
that
point
you
have
your
automation,
ready
to
go.
You've
run
your
tests.
You
feel
good
about
what
you
want
to
do.
You
Ren
run
this
build
command.
B
It's
a
very
it's
actually,
a
very
shallow
thing.
That's
been
added
for
convenience,
but
at
this
point
everything
gets
assembled.
It
takes
your
ansible.
Automation
takes
a
lot
of
different
a
base
image
that
has
all
the
necessary
dependencies
of
Python
and
ansible
ansible
runner,
some
things
like
that,
bundles
it
all
up
into
a
container
that
now
you
can
deploy
to
your
kubernetes
cluster
through
any
means.
It's
just
it's
at
that
point
itself.
It's
the
container
ready
to
go.
You
do
not
need
to
install
anything
special
on
your
cluster.
You
do
not
have
to
use
OpenShift.
B
So
to
taking
a
step
back
and
I've
been
talking
about
this.
But
again
it
is
worth
repeating.
This
is
the
anatomy
of
an
ansible
enabled
operator
what
you
see
in
the
white.
As
for
all
you
that
would
are
developing
an
operator
with
ansible.
That's
the
part
that
you
are
responsible
for
creating
the
roles
or
the
play
books
and
the
watches
file
and
managing
that
everything
you
see
in
that
gray
box
you
get
for
free
using
the
ansible
operator
SDK
when
you
do
the
build
command.
So
those
are
all
the
things.
B
B
A
I'm
quite
impressed
as
well
yeah,
so
so
there's
one
question
in
the
chat
that
I'm
going
to
try
and
answer
alive
while
you
getting
set
up
here,
I
attend
Sood
said,
is
one
new
controller
created
for
each
entry
in
a
watch
file
with
the
ansible
operator
or
just
one
controller
for
the
entire
watch
file.
I
understand.
B
A
A
A
A
B
A
A
See
you
let
me
know,
handle
multiple
events
to
reconcile.
Yes,
Carlton
I
can't
handle
multiple
events
that
can
watch
for
multiple
events
to
reconcile.
It
creates
the
CR
D,
so
you
can
have
it
essentially
watch
for
it
watches
for
any
event
to
happen
on
the
group
version
of
the
kind
for
the
CR
D
and
then
triggers
as
a
result.
So
it
doesn't.
You
know
multiple
events
and
reconciliation,
loops.
B
Okay,
so
I'm
gonna
keep
moving
on
here
since
I
hate
typing
life
I've
been
running
this
through
so
the
first
thing
I'm
going
to
do
here
in
the
foreign
is
show
you
how
easy
is
and
what's
in
a
project
when
you
use
the
operator
SDK
to
do
a
new.
So
this
is
the
line
that
you
saw
in
my
slides
just
a
couple
minutes
ago,
where
we're
doing
the
new
I'm
creating
something
called
a
null
operator,
because
it's
not
going
to
have
anything
in
it.
B
B
So
I
now
have
this
directory
loop
here,
where
we
have
a
bill
to
deploy
a
molecule.
That's
the
testing
framework
that
I
talked
about.
We
have
a
roles
directory
in
the
watches
file.
So
let's
take
a
quick
tour
here.
What's
in
there
in
the
build
we
get
a
docker
file.
We
also
get
a
docker
file
in
a
shell
script
that
helps
you
run
your
tests.
So
when
you're
working
locally
and
trying
to
work
this
stuff
out,
you
have
something
there
to
you
know
to
speed
things
up
under
deploy.
B
We
have
a
number
of
manifests
that
can
be
used
with
kubernetes
that
gets
built
out
for
doing
things
like
you
know,
setting
up
your
roll
roll,
binding
service
account
and
also
the
the
CR
D
and
the
custom
resource
itself,
so
you
could
just
feed
them
right
into
cube,
control
and
get
something
up
and
running
very
quickly
here
and
then
I'll
show
you
what's
under
the
role,
so
any
of
you
that
are
familiar
with
ansible.
You
see
you
have
what
looks
like
a
starter
role
here
of
something
that
you
can
write.
B
So
again,
it's
trying
to
make
it
really
easy
for
you,
and
then
we
have
the
watch's
file
here
that
it
generated
for
so
we
see
the
group
group
version
kind
based
on
the
the
input
that
we
gave
it,
and
then
we
see
that
it
is
calling
the
role
null
that
it
created
for
us
again
you
could.
This
is
just
a
starter,
so
you
can
add
more
entries
to
the
questions
that
were
being
asked
to
have
habit
watching
multiple
resources
and
calling
you
could
have
multiple
role.
B
B
B
Just
so,
you
can
follow
along
and
get
an
idea
of
what's
happening,
but
also
get
a
sense
of
the
power
of
operators
and
how
ansible
can
help
manage
these
type
of
things
when
you
need
to
coordinate
multiple
pods
and
services
and
things,
and
what
we've
come
up
here
with
is
a
scalable
caching
service
and
there
are
two
components
to
it:
we're
using
memcache,
which
has
been
around
a
really
long
time.
It's
you
know:
it's
general-purpose
distributed
memory.
Caching
system
for
database
calls
api's.
Like
said
it's
been
around
a
while
it's
very
generic
in
nature.
B
B
Facebook
makes
extensive
use
of
memcache
to
this
day,
so
they
created
a
project
called
McGruder
and
Makaurau
terse.
It's
in
the
front
end
it's
a
memcache
protocol
router
and
it
can
help
scale
memcache
deployments
in
that
all
type
of
extra
distributed
functionality
like
connection
pooling
flexible
routing,
is
a
whole
lot
of
things.
You
can
do
with
it.
So
what
we're
doing
here
is
we're.
B
A
Okay,
sorry,
that's!
Why
trying
to
be
here
and
filling
in
that
air,
so
I
think
I've
got
all
the
questions
answered.
If
you
feel
like
your
question,
is
not
answered,
please
react
or
rephrase
if
you
feel
like
I've
dismissed
your
question
unnecessarily.
I'm.
Sorry,
this
isn't
a
place
to
talk
about
github
issues
yeah.
A
So
the
I
think
one
of
the
questions
that
might
be
remaining
I
understand
that
you
can
use
ansible
to
manage
gates
clusters
like
queue
cuttle.
Yes,
you
can
yes
the
case
module
can
allow
you
to
do
that.
You
can.
You
know
Tim
showed
earlier
in
the
presentation
using
the
ants
will
look
up
plugin
to
deploy.
You
know
any
kind
of
Cooper
day's
resource
via
you
know.
You
know
lookups.
A
B
A
A
B
B
So
what
I
did
here
is
just
to
speed
up.
The
time
is
I've
taken
a
lot
of
the
the
roll
roll
binding
service
account
deployment
files
that
were
generated
and
I
put
them
into
one
file
here.
Mik
router
operator,
I'm
gonna,
run
that
here
and
now
we've
created
the
custom
resource
definition,
the
role,
the
role
bonding,
all
that
stuff
I
just
said
here.
So
if
I
go
back
actually
what
I
should
have
done
is
this.
B
B
I
actually
should
have
shown
you
what's
in
this
here.
So
what
I
do
is
I
created
a
file
ahead
of
time
and
all
I
did
here
was
I
added
the
a
custom
resource,
Colma
Crowder
I,
given
it
the
name,
my
cache
service
default
namespace
is
going
to
have
a
memcache
pool
size
of
two
pool
size
is
replicated
instead
of
sharded.
That
was
something
I
built
in,
so
that
I
can
control
what
what
type
of
pool
setup
I'm
using.
So
what
I'm
gonna
do
now
is.
B
Use
that
file
to
deploy
things
and
what
I
get
when
I
do
that
is:
oh
what'd
I
just
do
where'd
it
go
all
right
there
cuz
they
needed
a
second
all
right,
so
just
by
creating
that
custom
resource
that
one
API
call.
We
now
see
that
we
have
a
McGruder
instance
up
there,
which
is,
which
is
that
first,
my
cache
service
there.
B
The
second
line,
the
second
pod
that's
listed
there
and
I-
got
to
memcache
nodes
that
came
up
right
away
and
it
created
all
the
necessary
services
and
deployment
and
replica
sets
out
there
to
make
this
stuff
work
and
run.
So
now
we
have
an
entire
caching
service
ready
to
go
now.
Let's
see
here
if
I
can
get
a
little
fancy
into
some
of
the
questions
that
were
put
out
there.
What
I
took
was
trying
to
do
earlier
today
is
I
started,
creating
a
playbook
to
template
eyes
that
last
step
that
you
saw
here.
B
So
what
what
I
did
was
I
created
a
I
took
that
file
and
I
put
in
Jinja
two
templates
of
variables
in
there.
So
I
can
control
things
and
I
could
roll
out
multiple
of
these
cache
servers
services
under
different
names
or
namespaces,
or
give
it
different
pool
sizes.
So,
let's
in
this
case
try
and
do
increase
the
size
of
the
pool,
so
I'm
just
going
to
do
this
in
the
command
line.
You
could
have
done
this
using
something
like
ansible
tower
or
there's
a
whole
bunch
of
other
ways.
B
I
could
have
been
feeding
us
in,
but
for
simplicity,
I'm
using
the
command
line.
So
I
have
ansible
running
on
my
machine
I'm,
going
to
call
the
play
book
that
I
wrote
and
I'm
going
to
tell
it
to
give
me
a
pool
size
of
pool
size
of
three
will
do,
let's
see
here
if
I
get
this
right,
so
our
playbook
just
ran.
B
B
One
of
the-
and
this
is
a
this
is
a
generic
thing
about
I
should
have
mentioned
about
operators
in
general,
not
just
with
ansible
here,
but
it
can
really
help
you
enforce
policy.
So,
if
you
are
like,
we
need
three
nodes
in
memcache
and
someone
comes
along
and
is
doing
things
manually
and
doing
things
that
they
probably
shouldn't
be
doing.
What
happens
is
that
this
can
help
enforce
that.
So
let's
say
I
kill
someone
I'm,
you
know
not
following
policy
I'm
an
operator
and
I
go
in
there
and
I
decide.
B
I
want
to
take
down
a
pod.
At
this
point,
what
happens
is
the
operator
is
monitoring
and
says:
hey
I'm
supposed
to
have
three
memcache
nodes
in
my
pool?
That's
the
policy
here.
What
happens
is
is
that
we
see
that
the
the
pod,
the
the
one
that
was
in
that
I
deleted,
was
brought
right
back
up
by
the
by
the
operator.
That's
out
there.
B
B
Give
it
a
second
did:
I
there
we
go.
We
now
see
that
we
are
getting
these
CN
CF
services
coming
up
and
now
we've
been
able
to
repeatably
very
quickly
rolled
out
a
new
instance
of
our
service,
so
we're
seeing
all
of
the
in
this
case.
I
didn't
change
the
pool
size,
so
we
got
the
default
of
two
memcache
nodes
coming
right
up,
and
you
know
it's
created
the
deployment
and
the
service
for
that
that
memcache
and
again
this
is
all
just
using
the
basic
template.
B
Ansible
allows
for
in
order
to
very
quickly
adjust
and
redeploy
in
a
repeatable
way.
What
we're
doing
on
our
what
we're
doing
on
our
cluster
and
then,
let's
say
the
last
thing
I
will
show
is:
let's
say:
okay,
we
use
that
we
want
to
get
rid
of
it.
I
created
a
variable
called
state
and
if
I
change
that
to
absent
that
should
then
bring
down
the
stack.
A
B
I'm
calling
the
Cates
module
there
I
have
the
state,
where
I'm
that
variable
that
I
used
in
the
last
step
and
then
I'm
calling
the
template
file
that
I
had
and
feeding
that
in
as
the
definition
that
goes
off
to
the
the
Cates
API.
So
it
was
a
pretty
pretty
small
basic
playbook
I
could
have
done
more
for
if
it
necessitated
it.
But
in
this
case
one
task
was
enough:
yeah.
A
I
think
you
know
I
I,
think
I
said
this.
Every
time
you
and
I
have
been
the
same
room
together
talking
about
this
one
of
the
hardest
problems
we
have
in
demonstrating
operators
in
general.
Is
that
like
we're
trying
to
do
something
that
managers
state
and
potentially
like
status,
and
all
these
other
different
things
but
package
it
up
into
this
tiny
little
demo
and
that's
oftentimes
very
hard
to
do?
Even
we
did
a
workshop
at
ansible
fest
a
couple
weeks
ago.
A
B
A
B
Well,
it's
it's
that
the
replication
set
would
know
right,
bring
the
pod
back
up
itself
to
so
yeah
I
guess
what
I
should
have
done
is
changed.
The
I
think
if
I
would
have
changed
the
replications
that
the
operator
would
have
kicked
in
to
snap
it
back
to
what
it
should
have
been.
That
probably,
would
have
been
the
I
believe,
the
the
more
accurate
demo
yeah.
A
B
So
I
think
what
they
mean
is
like
in
this
case
I'm
just
feeding
I
was
speeding
them
in
through
the
command
line.
I
could
have
put
them
in
a
file
that
was
checked
into
to
github
and
fed
them
into
the
playbook,
for
example,
or
if
you
were
using
something
like
you
know,
plug
at
aw
expert
hour.
You
could
have
put
that
you
could
have
built
them
right
into
the
job
template
itself,
so
there
are
a
number
of
different
places.
B
A
A
B
B
Yeah,
and
so
what
I
have
here
is
like
I
highlighted
one
of
the
areas
where
I
had
a
default.
So
if
I
don't
set
that
variable
it'll
default
to
my
cash
service,
if
I
would
have
taken
a
little
bit
more
time
and
I
probably
should
I
could
have
created
us
as
a
role
and
use
the
defaults
file
in
there
or
var
file
in
there
to
make
this
template
a
little
less
verbose
itself
and
also
make
that
easier
to
edit
in
the
future,
especially
if
I
had
a
lot
of
different
defaults.
B
A
A
Right,
like
ansible
in
the
operator
sdk
is
fairly
new
right,
so
just
the
the
the
the
presence
of
it
is
within
the
past
year
I
mean
we
just
started
it
when
I
joined
Red,
Hat
last
June,
so
yeah
so
yeah
I
mean
this
is
relatively
brand-new
stuff.
So
the
fact
that
is
not
in
like
production
use
cases
or
you
know
open
source
use
cases
is
not
surprising
because
we
have
done
like
just
recently
started
the
talking
about
it.
If
the.
B
Of
examples
just
say
you
remind
you
know
the
this
question
reminded
me.
The
the
question
from
Lucas
remind
me
that
I
had
a
couple
more
slides
here.
Yeah
definitely
check
out
operator
how
I,
oh.
This
is
just
ready
to
use
operators
that
have
been
put
out
there
by
the
community
they're,
not
necessarily
by
ansible
I,
think
a
lot
of
them
are
actually
golang,
but,
but
still
it's
something
you
should
be
made
aware
of,
and
also
as
you
create
your
own
is
that
you
could
contribute
them
here.
B
The
other
couple
other
things
to
mention
is
for
those
of
you.
Looking
for
more
information.
Some
of
these
links
already
had
in
there
there's
ansible
comm
slash.
Operators
is
a
good
jumping-off
page
to
other
resources
and
then
also
there's
the
or
framework
getting
started
guide.
That's
out
there
and.
B
You
know,
group
repose,
but
there
is
an
Etsy
operator,
that's
that
was
done
by
our
team
when
they
were
developing
the
operator
SDK
to
validate.
How
far
can
we
push
this
thing
as
this
thing
as
feature
complete
as
we
want
it
to
be
and
if
you're
looking
for
another
simple
operator
very
you
know
the
related
to
what
we
were
just
doing.
There's
a
memcache
operator
that
you
can
find
here
under
the
operator
framework
organization.
A
A
A
B
B
A
Were
looking
so
someone's
asking
for
examples
of
upgrading
memcache
versions,
I
would
say,
like
there's
tons
of
examples
of
upgrading
memcache
on
ansible
galaxy
galaxy
Ansel
com.
That
is
the
place
for
people
to
share
roles,
and
you
can
take
those
roles
and
then
reuse
them
in
your
ansible
operator,
and
that
would
be
just
close.
The
Q&A
window
that.
A
B
B
A
How
do
kate
secrets
and
Ansel
vault
secrets
play
along
together?
They
really
don't
they're
kind
of
two
different
things
you
can
use
them
both
in
this
use
case,
but
I
would
recommend
sticking
with
the
Kate's
secrets
for
now
and
using
those
inside
your
cluster,
as
opposed
to
trying
to
expand
in
sablevulpe
things
on
the
floor.
B
A
A
All
right
you
so
I
really
like
we
need
multi-threaded,
Q&A
and
zoom,
but
we
are
at
the
top
of
the
hour
yeah
everybody
I'm.
Very
sorry.
If
I
didn't
get
to
your
questions,
please
feel
free
to
reach
out
to
Tim
or
myself
Twitter
github
email,
and
we
will
be
sharing
this
webinar
at
CNCs
that
IO,
slash,
webinars
and
come
see
us
at.