►
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
Intro: Kubernetes SIG Apps - Adnan Abdulhussein, VMware & Matt Farina, Samsung SDS
Kubernetes SIG Apps covers developing, deploying, and operating applications on Kubernetes with a focus on the application developer and application operator experience. In this session we will focus on the Workloads API (e.g. Deployments, StatefulSet, DaemonSet, Job etc.), the Application CRD, and the supporting elements to make application developers and operators successful with Kubernetes. That includes using the Kubernetes API to run your workloads and leveraging Kubernetes resources to develop Kubernetes native applications.
https://sched.co/UajF
A
A
So
it's
it's
just
kind
of
that
major
organizational
unit
within
kubernetes,
because
there's
too
much
for
any
one
or
two
or
even
small
group
of
people
to
do
you
have
to
have
different
groups
and
a
structure
for
them
to
work
together
and
we'll
walk
through
what
sig
Apps
is,
but
it's
actually
part
of
the
kubernetes
development
process
at
owns
code
and
things
like
that,
so
hi,
I'm
matt
and
with
me
adnan.
We
are
two
of
the
chairs
of
cig
apps.
A
The
other
two
are
Ken
and
Janet
they're
here
today,
but
they're,
obviously
not
in
this
session
and
the
chairs,
we
kind
of
oversee
the
process
and
the
meetings
that
we
have
and
things
of
that
nature.
So
if
you
need
to
get
a
hold
of
somebody,
if
you're
looking
for
how
to
getting
engaged
or
where
to
go
with
the
gaps,
the
chairs
are
in
kubernetes
a
gaps
are
the
place
to
go.
Are
the
people
to
go
to
when
you
need
that
kind
of
thing
so
I'll
ask?
A
Has
anybody
ever
been
to
one
of
these
kubernetes
a
gap
sessions
before
an
intro
or
any
of
those
things,
or
are
you
all
new
all
right?
That's
a
good
place
to
start
so
I'm
actually
going
to
start
a
little
bit
like
in
the
beginning
where
how
we
came
about
with
this,
and
so
if
you
actually
go
back
to
kubernetes
back
in
the
beginning,
and
this
is
kubernetes
1.0,
the
very
first
part
of
kubernetes
and
as
you
can
see,
this
is
back
in
2015.
A
If
you
look
here,
this
is
the
packages
directory,
and
this
is
where
the
controllers
are,
and
so,
when
you
think
about
things
today,
like
stateful
sets
deployments
all
of
those
things
they
came
later.
When
kubernetes
came
out,
we
didn't
have
those
things
we
didn't
have
those
messages.
We
had
a
very
simple
thing
called
the
replication
controller.
It's
still,
there
don't
use
it,
but
that
was
where
kubernetes
came
from.
A
It
didn't
have
a
lot
of
the
experience,
the
the
complexity,
the
ability
to
do
things
you
had
to
do
a
lot
of
this
yourself
or
futz
around
with
it
to
make
it
work,
and
if
you
go
back
shortly
thereafter,
this
helm,
the
package
manager
came
out
and
it
was
there
to
help
package
up
configuration,
and
so
you
could
share
it,
and
so
very
early
on.
This
is
the
first
version
of
how
much
hasn't
been
in
stable
form
for
years,
and
you
know
this
was
very
early
on.
A
It
was
one
of
the
very
first
tools
to
help
you
share
code,
share
configuration
and
to
deal
with
those
applications,
and
what
does
that
application,
interface
and
lifecycle
look
like
so
kubernetes
started
out
without
much
to
it,
and
we
noticed
there
was
a
problem
and
there
was
talk
of.
How
do
we
do
this?
How
do
we
improve
on
the
experience?
How
do
we
learn
what
how
you
can
improve,
with
the
configuration
of
what
should
you
do
and
that's
when
sig
app
was
born
and
it
was
born
shortly?
Thereafter?
You
see
this
is
just
five.
A
Six
months
after
helm
came
out,
we
were
watching
everything
we
started
talking.
We
came
out
with
us
and
we
said
we
need
a
way
to
deal
with
running
applications
in
kubernetes.
The
experience
isn't
great.
How
do
we
improve
it,
and
this
is
actually
the
original,
the
very
first
charter,
so
you
speak.
It's
a
special
interest
group
to
deal
with
operating
applications,
and
these
are
the
things
we've
worked
out.
How
do
you
discuss
it
right?
A
You
won't
see
things
about
owning
code
or
anything
like
that,
because
it
started
with
this
idea
that
there's
a
problem
and
how
do
we
get
together
to
figure
out
that
problem
and
work
together
to
try
to
solve
it
to
improve
things?
Now,
if
you
fast
forward
to
today,
things
have
changed
quite
a
bit.
This
is
the
current
charter.
You'll
see
that
we
we
have
a
scope,
we'll
recover
the
developing,
deploying
and
operating
of
applications.
A
So
we
cover
a
bunch
of
things
now
it's
we
also
have
code
binary
services
and
we're
gonna
actually
talk
about
what
those
are
in
just
a
minute,
the
different
parts,
but
that
we
own
things.
In
fact,
if
you
look
at
the
code
base
today,
you'll
see
stateful
set
you'll
see
some
of
the
other
things
we're
gonna
cover
in
a
minute,
but
you
also
see
something
else
in
here.
You
see
that
we
talked
about
both
the
application,
developer
and
the
operator,
and
if
you
look
at
that
as
personas,
you
actually
see
those
as
two
different
roles.
A
Somebody's
gonna
take
an
application
and
package
it
up.
They
may
package
up
their
own
application
or
they
may
package
up
somebody
else's
right
if
I'm
gonna
take
post
crusts
or
my
sequel
and
I'm
gonna
go
operate,
that
in
the
cluster
I'm
operating
somebody
else's
application,
but
I
can
also
do
something
where
I
write
an
application
and
it
grabs
events.
A
And
then,
when
those
events
happen,
I
spin
up
jobs
to
go,
do
something
and
my
application
works
as
an
app
talking
to
the
kubernetes
api
to
spin
up
kubernetes
things
and
there
I'm
an
app
developer
building
tools
that
natively
take
advantage
of
parts
of
kubernetes,
and
so
there's
that
too,
and
there's
these
kind
of
different
use
cases
out
there,
depending
on
what
you're
gonna
do.
And
so
we
we
try
to
deal
with.
B
Thanks
Matt,
yes,
so,
as
matt
said,
figs
are
the
organizational
unit
in
kubernetes
that
own
code,
so
in
sick
apps.
You
might
be
familiar
with
some
of
these
things.
We
own
deployments,
daemon
set
stateful
sets
so
things
in
the
apps
AAPI
group,
as
well
as
the
batch
API
group,
so
con
job
and
jobs
and
a
few
other
things
like
pod
disruption,
budgets
and
a
few
other
api's
as
well.
The
other
thing
we
also
own
is
documentation
around
these
api
groups.
B
So
this
is
also
one
area
that
we
continually
need:
investment
in,
so
where
we
want
to
make
changes
to
a
kubernetes
api,
whether
it
be
a
core
API
or
a
completely
new
API.
Like
all
other
SIG's,
we
go
through
the
cube,
Nettie's
enhancement
proposal
and
essentially
a
kept
event.
Certainly
just
involves
the
high-level
overview
of
the
change
that
you're,
proposing
and
motivations
for
that
change
and
then
detailed
design
on
how
how
that
change
will
actually
be
implemented,
as
well
as
the
test
plan
and
graduation
criteria
for
promoting
that
change.
B
Eventually,
I'd
want
to
get
that
to
a
ga
release
and
deprecated
any
previous
or
older
versions
of
that
API.
This
process
works
well
and
has
worked
well
in
the
past,
but
we're
trying
to
improve
it.
One
big
issue
with
this
process
is
that
we're
tied
to
the
Cuban
Isis
release
cycle.
So
every
time
we
want
to
make
a
change
feature.
We
have
to
wait
right
now.
B
The
cube
nephew's
brew
cycle
is,
is,
is
every
quarter,
so
we'd
have
to
wait
three
months
before
new
versions
of
that
API
can
go
out
so
that
that
introduces
a
lot
of
kind
of
a
lot
of
time
into
making
those
changes.
So
what
we're
trying
to
leverage
now
is
this
new
process
that
takes
that
users
see
our
DS
and
custom
controllers
to
start
prototyping
out
ideas.
B
So
this
way,
if
we're
developing
a
new
future,
we
can
iterate
on
it
outside
of
core
I,
see
IDs
in
control
and
kind
of
build
up
usage
as
a
third-party
extension.
And
then,
if
we
get
enough
users
that
are
interested
in
this
new
feature
or
API,
we
can
then
we
can
consider
it
as
a
candidate
to
to
be
eight
to
enter
core.
B
B
Another
thing
that
we're
looking
at
working
on
in
cig
apps
is
the
execution
hook
controller,
so
this
wasn't
kept
that
just
got
approved,
and
originally
it's
a
proposal
from
six
storage
and
the
specific
use
case
there
is
for
the
volume
snapshot
api's
need
a
way
to
in
order
to
take
application
consistent
backups.
They
need
a
way
to
quiesce
a
non
crius
application
state.
B
So
how
can
you
get
involved?
Well
see?
Gaps
meets
every
other
Monday
at
9:00
a.m.
Pacific
time
post
cube
con
I.
Think
the
first
meeting
that
we
have
coming
back
is
the
second
of
December
for
previous
meetings.
You
can
go
to
the
company's
YouTube
channel
and
their
there
you'll
find
a
sagacity
meeting
playlist,
which
has
all
of
the
probably
meetings
that
happened
and
then
also,
if
you
go
to
the
cubemetricks
community
repo
here,
you
can
find
the
stakeouts
folder
and
there
you'll
find
links
to
the
YouTube
channel.
B
You'll
find
a
link
to
our
meeting
agenda
dock,
where
you
can
add
things
to
the
agenda
prepare
prior
to
meetings
to
discuss.
You
also
find
links
there
for
slack
and
the
mailing
list
and
other
areas
that
you
can
get
involved
in
and
then,
since
you're
here
at
cube,
con
do
check
out
the
deep
dive
tomorrow,
which
will
be
hosted
by
the
two
other
co-chairs
can
and
Janet
where
they
will
be
going
over
a
code.
Walkthrough
of
I
think
the
cron
job
controller.
B
So
that
would
be
a
good
idea
if
you're
interested
in
in
getting
more
involved
and
actually
contributing
code
to
the
gaps.
That's
a
great
place
to
go
and
kind
of
learn
more
about
how
controllers
are
developed,
so
I
kind
of
mentioned.
Documentation
is
a
big
face
that
we
need
a
lot
more
help.
Mat
kind
of
pointed
out.
Some
great
areas
that
that
we
can
start
working
on
so
one
is
in
in
the
workloads
concepts
documentation
here.
There
isn't
really
a
good
way
to
to
get
an
overview
of
all
the
workloads
api's.
B
So
if
we
had
a
page
here
that
kind
of
gave
a
brief
intro
into
all
the
different
controllers
and
different
use
cases,
that
would
definitely
be
a
really
good
change
and
then
the
other
one
here
is
instigates
of
while
ago
I
think
about
a
year
ago,
we
came
together
and
came
up
with
a
set
of
labels
that
are
recommended
to
use
in
your
deployments
or
in
your
resources,
and
a
lot
of
the
examples
that
we
have
in
some
of
the
tutorials.
Don't
actually
make
use
of
these
labels.
B
So
this
is
another
area
that
we
could
improve.
We
could
actually
go
and
update
some
of
those
example.
We
add
more
files
and
add
some
of
the
recommended
labels
that
we've
defined,
as
well
as
just
updating
some
of
the
image
that
those
animals
are
pointing
to
they're,
just
pretty
old
and
then
code
code
wise,
as
I
mentioned,
as
there's
a
lot
of
opportunity
there
to
contribute.
We
have
a
lot
of
bugs.
B
If
you
go
to
the
Cubans,
given
F
user
repository
you'll
find
in
the
issues
there,
you
can
filter
by
the
gaps
and
you'll
find
all
the
issues
that
are
related
to
the
core
web
loads
api's.
One
area
that
we're
specifically
trying
to
improve
right
now
is
the
cron
job
API
and
we're
trying
to
get
that
to
GA.
B
So
there's
a
ket
currently
open,
specifically
for
cron
job
and
what
needs
to
be
done
to
get
that
to
GA
and
that's
somewhere
that
we're
that
we
really
need
help
with
and
then,
of
course,
there's
all
the
ecosystem
projects,
so
application,
CRE
and
controller,
which
I
mentioned
any
execution
hook.
These
all
need
work
and
I
need
some
more
input,
so
there's
repositories
for
those
as
well
that
you
can
go
and
get
involved
in
and
then
I
think
we'd
be
remiss
if
we
didn't
mention
some
of
the
amazing
ecosystem
tuning.
B
That's
out
there,
so
things
like
helm,
flux,
telepresence,
notary
and
all
the
other
great
ecosystem
tools
that
we've
seen
and
demoed
in
see,
gaps,
keep
building
amazing
tools,
keep
coming
to
see,
gaps
and
endeavouring
those
and
just
just
come
to
the
gaps
and
tell
us
how
you're,
deploying
and
managing
applications.
That's
really
what
we
want
to
hear
it.
Ultimately,
that's.
A
Flux,
it
is
a
project
that
originally
came
out
of.
We've
works.
Yes,
sorry,
he
wanted
the
question
in
him
like
so
the
question
was:
what
is
the
the
arrow
here
and
that's?
We've
worked
flux
and
they
recently
broke
it
away
from
we've
works
and
turned
it
into
a
CNC
F
sandbox
project.
In
fact,
when
we
talked
about
more
tools
here
rather
than
picking
some
vendor
tools
to
point
out,
these
are
all
other
CN
CF
projects
that
you
can
use
in
your
applications
in
some
way
shape
or
form.
Yes,
I.
D
B
A
D
A
Me
ask
you
a
question,
then.
What
kind
of
things
do
you
want
to
write
for?
Are
you
looking
to
run
applications
inside
of
kubernetes?
Are
you
looking
to
leverage
kubernetes
native
api's
to
do
interesting
things
and
I'll?
Tell
you
this
one
of
the
other
projects
and
it's
escaping
me.
It's
the
build
tool.
A
What
they
do
is
they
will
spin
up
jobs
based
on
events
and
then
those
jobs
will
go,
execute
something
right,
and
so
they
receive
events
from
an
eventing
system
and
then
their
application
running
in
the
background
spins
off
a
job
to
go
deal
with
each
of
those
events
and
a
job
as
a
type
of
kubernetes
object.
Okay,
are
you
look?
What
kinds
of
things
are
you
looking
to
do
all
of
the
above
specific
things,
I.
D
Want
to
try
and
keep
the
question
focus.
Oh
sorry,
if
it
was
too
broad,
yes,
I'm
thinking
of
an
app
that
I
want
to
write
for
my
organization,
and
it
wasn't
obvious
where
what
what
to
hang
it
on
where
I
should
live.
It
feels
a
little
restricted
to
run
it
on
one
machine.
I
may
be
a
cron
job
would
be
a
good
example,
so
it
gets
scheduled
and
runs
at
the
cluster
level.
A
D
A
Anybody
else
in
here
not
familiar
with
Morgan
Omega.
Okay,
so
I'll
give
a
brief
on
this.
Then
so
at
Google
they
use
I,
guess
I
would
call
it
they
call
it.
The
data
center
is
a
computer
and
then
inside
of
there
they
have
essentially
clusters
and
they
treat
a
cluster
as
a
single
computer,
and
then
their
system
is
or
go
now.
Cooper
Neddy's
is
kind
of
descended
from
that.
They
took
the
lessons
learned
and
did
it
so
when
you
think
of
kubernetes,
don't
think
of
it
as
a
computer.
That
manages
a
bunch
of
servers.
D
A
Tend
to
do
things
around
people
who
want
to
develop
applications
that
are
directly
against
the
kubernetes
api
or
those
who
want
to
run
applications
in
it,
and
so,
if
you
want
to
run
something
like
a
deployment
which
is
normally
a
stateless
app
or
if
you
want
to
run
what
we
call
a
stateful
set,
that's
where
you're
gonna
run
something
that
deals
with
state
and
you
have
to
care
about
state
location
and
restarting
things
with
state
like
post
cross,
my
sequel,
something
like
that.
We
deal
with
those
kinds
of
things
and
then
how
do
you
operate?
A
Those
inside
of
kubernetes
we've
got
different
configuration
files
to
describe
your
application,
because
kubernetes
does
things
in
a
declarative
way.
You
tell
it
how
you
want
things
to
be,
how
you
want
it
to
run,
and
then
kubernetes
tries
to
make
that
so,
and
so
we've
got
different
configuration
files
depending
on
the
type
of
thing
you
want
to
run
and
the
data
kubernetes
needs
to
have
describe
to
it.
D
A
Know
this
is
confusing,
so
one
of
the
things
you
can
do
is
before
we
talked
about
documentation.
I
will
jump
way
up
there,
there's
documentation
here,
and
you
probably
can't
read
it
very
clearly,
but
on
the
left
side
here
it
says
in
the
concepts
area
there
is
workloads
and
that's
what
we
call
it
in
kubernetes.
If
you
come
down
here,
there's
controllers
not
organized
for
our
well.
Let
me
tell
you,
but
you're
gonna
see
things
like
deployment.
Stateful
sets
a
cron
job
at
the
bottom.
A
What
I
would
suggest
doing
is
going
and
looking
at
those
and
reading
the
description
at
the
top
of
each
of
those,
because
it's
gonna
tell
you
about
the
kinds
of
situations
that
it
can
handle
and
then,
if
you
say
this
one's
for
me,
I
want
to
try
it
there's
an
example
in
there
that'll
tell
you
how
to
go
about
doing
it.
That's
how
you
coop
control
the
CLI.
How
do
you
use
that
on
you
know,
so
you
can
point
that
at
a
kubernetes
cluster
and
then
you
can
try
it
and
see
what
happens.
B
Definitely
check
out
the
and
again
kubernetes
is
hard,
like
all
these
concepts
are
quite
difficult
for
someone
who's
completely
new
to
it.
It's
a
it's
a
lot
to
take
in,
but
we're
trying
to
improve
the
documentation
to
just
make
it
more
relevant.
So
things
like
the
tutorial
which
focus
on
just
getting
you
know
like
the
example
guestbook
application
up
and
running
on
keep-net
see
that's
a
great
place
to
go
and
look
at
if
it's
your
first
time,
looking
at
kubernetes.
E
B
Do
you
have
any
insight?
I
have
some
polls
of
this
so
right
now
the
application
CID
is
still
in
beta
I.
Think
the
goal
really
is
to
get
it
to
a
stable
API
and
then
and
then,
ideally,
we
just
need
to
get
more
people
using
it,
and
then
once
we
have
more
people
using
it,
we
can
gauge
whether
it
makes
sense
to
contribute
as
a
as
a
core
API
I
realized.
That's
a
bit
of
a
chicken
and
egg
situation,
because
it's
harder
to
get
people
using
it.
B
E
A
Kubernetes
I
think
we
talked
about
this
process
right.
This
is
one
of
the
things
that
sega
architecture,
one
of
the
other
special
interest
groups
worked
through
that
deals
with
us,
and
you
know
it
used
to
be.
The
process
was
right:
you'd
introduce
something
new
to
kubernetes
and
you'd
iterate
on
it
as
part
of
kubernetes,
and
they
decided
they
didn't
want
to
do
that
anymore
and
so
as
part
of
the
new
process.
In
order
for
it
to
land
inside
of
kubernetes
itself
in
a
release,
they
wanted
to
actually
become
popular
work.
A
A
large
group
of
people
want
to
use
it
and
have
it
included.
Otherwise,
it
can
just
be
installed
as
a
separate
third
party
controller
or
as
part
of
a
distribution,
and
so
we're
kind
of
at
the
point
right
here
where
we're
iterating
in
the
CRTs
and
controllers,
and
we
probably
need
some
more
people
to
drive
it
more
to
increase
the
popularity,
the
person
who
was
originally
driving.
A
It
moved
on
to
do
something
else,
and
it's
probably
languished
a
little
bit
since
then
and
I
know
you
care
about
this
because
heck
this
came
out
of
a
lot
of
the
work
you
did
a
year
or
two
ago,
and
so
it
probably
needs
somebody
to
really
start
driving
it.
Just
because
we've
had
a
little
bit
of
a
void
in
leadership
recently
because
of
some
stuff
moving
around.
A
That's
the
honest
answer:
if
you
want
to
get
involved-
or
you
know
somebody-
please
send
them
our
way
and
we
will
help
them
get
ramped
up
to
start
driving
this
a
little
bit
better.
But
in
order
for
it
to
ship
with
kubernetes
itself,
it's
probably
going
to
need
to
get
a
little
bit
of
popularity
out
of
it.
Okay
and
I'm
happy
to
talk
to
you
more
about
this.
Afterwards,
because
I
would
love
to
see
this
happen,
we
had
a
question
over
here.
I.
F
F
B
So
there
was
a
contributor
summit
yesterday,
I'm
sure
you
can
go
back
in
time,
but
there
is
a
contributor
summit
at
every
cube
con.
So
maybe
you
can
attend
one
of
those
next
time,
but
there's
also
the
deep
dive,
which
is
a
great
place
to
go
just
start
learning
about
some
of
the
controllers
in
say
gap
specifically
and
then
from
there
on
just
try
and
get
more
involved
in
the
meetings.
B
A
F
A
Some
of
the
practical
things
might
be,
there
is
I,
think
it's
in
the
community
repo
there's
a
contributors
guide
and
the
contributors
guide
walks
you
through
so
kubernetes,
because
it's
a
big,
complicated
project
with
so
many
people
who
work
on
it.
We
have
a
lot
of
kubernetes
isms
things
that
you
you
run
into
like
what
are
the
different
pots,
and
what
do
they
do?
A
There's
a
contributor
guide
that
will
walk
you
through
and
kind
of
explain
what
all
of
these
insider
tribe
things
we
have
are
when
you
want
to
go
contribute
for
the
first
time,
so
I
would
suggest
going
in
taking
a
look
at
that.
It's
it's
a
useful
guide.
That
explains
a
lot.
The
next
thing
is
a
little
as
it's
going
to
depend
on
where
you're
gonna
go.
A
If
you
want
to
go
after
something
like
the
application,
CRT
I
would
suggest
going
after
the
code
and
looking
at
Kuby
builder
Kuby
builder
is
one
of
the
other
sub
projects
of
kubernetes.
That's
under
sig
api
machinery
that
lets
you
build
controllers
and
that's
actually
used
to
build
the
application,
CRT
and
controller,
and
so
you
can
go
look
at
that
project,
there's
even
a
documentation.
A
It
is
a
book
kind
of
thing
where
you
can
go,
read
how
to
use
it
and
that'll
help
you
get
into
the
application
controller,
because
then
you'll
understand
how
it
works
and
if
you
want
to
go,
contribute
and
there's
opportunities
to
contribute
to
it.
If
you're
talking
about
a
core
controller,
those
are
a
little
bit
different
because
there
haven't
been
generated,
they've
been
kind
of
hand
curated
and
for
that
I
would
probably
suggest
going
to
the
deep
dive.
A
F
C
B
B
A
A
The
application
CRD
consumers,
if
we
can
build
it
in
popularity,
there's
a
lot
of
opportunity
here.
For
example,
you
can
have
something
like
there's
a
bunch
of
dashboards.
If
you
go
down
to
the
shore
flow,
the
floor
show
you'll,
see
vendors
with
dashboards
things
like
octant,
which
VMware
has
worked
on
or
kubernetes
dashboard,
and
you
can
now
take
this
metadata
that
you
have
in
a
cluster
and
you
can
start
to
visualize
it
and
there's
a
lot
of
interesting
things
that
you
can
do,
because
you
have
that
metadata
together.
A
In
fact,
if
you
know
that
maybe
helm
and
of
you
know
how
three
is
working
on
something,
and
you
see
something
organized
that
way,
you
could
start
to
orchestrate
things
like
delete,
commands
things
like
that
as
well.
There's
a
lot
of
opportunity
just
to
have
that
metadata
available
and
then
start
to
act
on
it.
So
it's
not
just
for
those
tools.
It
provides
a
a
cross
tool
capability,
helm
understands,
held
them
stuff
right.
Other
tools
understand
their
stuff.
How
do
we
make
that
work
across
tools
and
that's
where
the
application
CRD
provides
an
opportunity?
So.
A
And
so,
for
example,
I'm
sorry
I'm
jumping
on
there,
but
the
controller
itself
provides
a
health
check
and
that
health
check
can
actually
look
at
all
of
the
things
so
say:
WordPress
right,
WordPress
has
maybe
a
deployment.
That's
running
WordPress
and
a
stateful
set.
That's
running
your
database
like
Maria
DB
right.
Do
you
want
to
check
each
of
those
for
State,
or
can
you
hit
the
application
CRT
and
say
what's
the
status?
H
Hey
Nick
Mitchell
from
IBM,
thanks
for
all
the
great
work
on
this,
so
I've
been
working
with
the
six
CLI
over
the
past
couple
of
months,
with
some
lightweight
visual
tooling
for
enhancing
the
CLI
just
curious,
whether
you
guys
have
established
a
Doozer
otta
features
that
you
might
need
from
a
visualization
standpoint.
That
would
help
with
application
development
is
that
is
there
resources
that
I
can
sort
of
tap
for
that
or
should
I
just
join
the
discussion
and
worketh
working
out
is
with
discussion.
B
It's
a
good
question:
yeah
I,
don't
know
that
we
kind
of
this
specific
me
around
UI
tuning
there's
a
few
different
things
that
we've
discussed
and
take
out
the
four.
So
you
know
more
recently
we
had
often
demoed
in
the
past.
We
obviously
had
things
like
the
kinetic
dashboard,
demoed
and
other
tools,
but
yeah
I.
Don't
think
that
we've
kind
of
had
a
working
group,
that's
like
defining
what
a
UI
perspective
of
document
looks
like,
but
up
definitely
something
that
we'd
be
interested.
It's
got
or.