►
Description
Kubernetes, Metadata and You [I] - Liz Rice, Aqua Security & Gareth Rushgrove, Puppet
The combination of CI/CD tools and Kubernetes means we can set up a pipeline for deploying code changes as they happen, triggering a container image build and a rolling update to pull the new image. But what about changes that are about the application and how it should run, rather than the code itself?
This talk will explore tools and approaches for managing application metadata alongside the application code. We will look at:
- The importance of metadata to managing modern Cloud Native systems
- Built-in metadata capabilities in Kubernetes like ConfigMaps, Annotations and Labels
- Ways of making a deployment self-describing as part of a CI/CD workflow
- Using metadata to make the life of Kubernetes operators easier
- Examples of open source tools (like Manifesto, Lumogon and Skopeo) which work with Kubernetes ecosystem metadata
About Liz Rice
Liz Rice is the Technology Evangelist with container security specialists Aqua Security, and also works on container-related open source projects including manifesto and kube-bench. She has a wealth of software development, team, and product management experience from working on network protocols and distributed systems, and in digital technology sectors such as VOD, music, and VoIP. When not writing code, or talking about it, Liz loves riding bikes in places with better weather than her native London.
About Gareth Rushgrove
Gareth Rushgrove is a principal software engineer at Puppet. He works remotely from Cambridge, UK, building interesting tools for people to better manage infrastructure. Previously he worked for the UK Government Digital Service focused on infrastructure, operations and information security. When not working he can be found writing the Devops Weekly newsletter or hacking on software in new-fangled programming languages.
Join us for KubeCon + CloudNativeCon in Barcelona May 20 - 23, Shanghai June 24 - 26, and San Diego November 18 - 21! Learn more at https://kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy and all of the other CNCF-hosted projects.
A
Alright,
let's
get
started
so
thank
you
so
much
for
coming
and
joining
us
this
afternoon.
Gareth
and
I
will
be
talking
about
kubernetes
metadata
that
you
can
use
alongside
key
vanities
and
what
that
metadata
can
do.
For
you.
My
name
is
Liz
I
work
with
container
specialists,
company
called
aqua
security
act.
I
have
a
booth
downstairs,
so
you
more
than
welcome
to
come
and
chat
with
us
at
any
point
over
the
next
couple
of
days.
B
B
This
talk
I'm,
it's
hopefully
the
thing
you've
come
along
see
and
we're
gonna
talk
a
bit
about
like
well.
What
do
we
mean
by
metadata?
It's
in
the
title.
People
have
probably
heard
of
it,
but
what?
What
do
we
actually
mean
at
a
pretty
fundamental
level
and
we're
gonna
talk
about
what
relevant
features
kubernetes
has
for
manipulating
and
managing
and
using
metadata,
and
we're
gonna
touch
a
little
bit
about
well.
Why
we
care?
B
Hopefully
that
sounds
interesting,
so
we
will
start
out
with
dying
again
like
the
least
COO
metas.
Bit
of
the
talk
like
what
is
metadata
and
so
heading
to
the
dictionary
is
always
a
good
idea.
It
says
metadata
data
that
provides
information
about
other
data,
which
is
pretty
abstract,
but
it
is
about
like
having
information
about
things
you
already
care
about.
B
B
The
librarians,
because
if
anyone
knows
the
librarian
they're
obsessed
with
metadata
and
libraries,
are
cool,
so
let's
go
there.
The
sort
of
this
sort
of
understanding
metadata
paper
breaks
it
down
into
three
sort
of
main
areas
and
you
sort
of
got
descriptive
metadata,
and
this
is
something
that
describes
is
it's
for
the
purposes
of
discovery
and
identification,
and
so
thinking
about
the
sort
of
those
resources
and
committees.
Well,
how
do
I
find
services
that
relate
to
this
part
of
my
organization
are
using
this
technology?
B
Structural
metadata
is
a
button,
it's
a
grouping
of
things,
so
maybe
this
deployment,
obviously
you've
got
direct
relationships
between
a
deployment
and
a
pod,
but
you
might
have
a
number
of
different
deployments
that
really
make
a
concept
of
an
application,
and
these
things
are
all
running
like
having
some
metadata
that
groups,
those
together
sort
of
structural
metadata
and
finally,
administrative
metadata,
providing
some
information
to
help
with
management
and
some
Yellin.
Well,
when
was
it
created?
Maybe
you
want
to
react
to
something
being
I.
B
B
Different
tools
can
write
method
that
different
tools
can
read
metadata.
If
we're
all
doing
that
in
the
same
place
with
shared
schemas
and
other
bits
pieces,
we
can
build
quite
Interop
all
tools
without
direct
integration,
and
that's
really
good
from
like
replacing
tools,
fighting
lock-in
but
building
an
interoperable
ecosystem.
B
A
Community
supports
labels.
The
documentation
tells
us
that
labels
are
key
value
pairs
that
are
attached
objects.
Things
like
pods
they're,
very
much
intended
to
be
identifying
those
objects.
They're
supposed
to
be
meaningful
to
you
as
somebody
who
is
operating
kubernetes.
The
system
itself
doesn't
do
anything
with
these
labels.
A
The
other
kind
of
metadata
the
community
supports
is
annotations,
and
this
is
much
more
sort
of
free
form.
Data
of
your
choice
that
you
can
attach
to
a
resource
pretty
much
anything
you
want
can
go
into
an
annotation
examples
of
things
you
could,
and
this
is
by
no
means
exhaustive,
exhaustive
information
about
the
the
software
that
you're
running
you
could
have
links
or
references
to
things
related
to
that
resource,
perhaps
links
to
where
the
logs
go
or
where
the
audits
go.
A
A
Here's
another
example
where
we've
got
it's
an
ingress
and
it's
got
some
information
about
time
out
configurations
essentially,
and
that
can
be
useful
to
you
as
a
human
being
to
be
able
to
see
what
is
the
you
know
when
should
this
time
out?
How
long
should
this
go
before
it
would
time
out,
you
might
be
sort
of
saying
to
yourself
yeah,
but
how
do
you
know
this
actually
matches
what
the
software
knows,
because
this
is
like
annotation
data?
Is
it's
not
part
of
the
code
itself?
A
A
B
A
So
we've
looked
at
em
some
existing
tools
and
features
that
help
us
with
metadata
the
arts.
What
they
cover
at
the
moment
is
what
we've
talked
about
so
far
covers
information.
You
can
build
into
your
images
and
information
that
you
can
associate
with
your
software
and
when
you
deploy
it,
but
there
are
obviously
a
whole
bunch
of
other
stages
that
software
can
go
through
between
those
two
points
and
examples
of
the
kind
of
things
that
happen.
Post
build,
but
probably
pre-deployment.
A
Things
like
whether
or
not
a
piece
of
software
has
been
approved
for
deployment,
whether
or
not
it's
passed
tests
and
vulnerability
scan
reports.
All
of
these
things
have
to
be
associated
with
a
specific
build
of
software.
You
can't
have
a
test
report
sort
of
just
floating
about
between
different
builds.
It
has
to
be
associated
with
a
specific
bit
and
this
information
could
change
over
time.
A
Vulnerability
scanning
is
a
really
good
example
where
a
piece
of
software
doesn't
change,
but
a
new
exploit
could
be
discovered
and
it
turns
out
it
existed
in
that
image
that
you
already
had.
So
the
vulnerability
scan
report
could
change
after
the
fact
of
the
build.
So
these
are
examples
of
cases
where
the
kind
of
current
tooling
doesn't
really
allow
us
to
manage
and
manipulate
metadata.
B
But
why
do
we
care
who's
it
for
and
sort
of
thinking
about
communities?
Other
as
where
are
the
platform,
and
the
really
are,
though
there
are
different
types
of
users
who
I
actually
use
communities,
but
a
part
of
this
bigger,
broader
community
and
not
who
were
going
to
be
using
it
just
as
part
of
their
job
they're,
not
as
interested
in
it
to
come
to
Austin.
B
It's
just
something
there,
but
waiting
that
there's
not
really
a
really
widely
agreed
set
of
sort
of
user
personas
our
roles
at
the
moment
within
the
community,
and
so
this
is
a
bit
of
a
side
sort
of
story
because
will
then
come
back
to
why
we
care
and
in
the
same
context
of
metadata
a
moment
and
so
I
ended
up
speaking
to
a
number
of
people
about
this.
Instead
of
saying,
oh
there's,
not
a
group
there's
not
a
shared
agreement
yet
batchi.
B
What
do
other
people
think
I,
think
I
know
what
I
I
think
and
a
number
of
people
sort
of
responded
and
replied
and
I'm
not
gonna,
read
tweets
out.
That's
really
boring,
but
it
was
pretty
similar
to
how
we'd
been
talking
about
it.
This
idea
of
actually
there
being
three
sort
of
distinct,
sometimes
overlapping
roles.
B
Unless
you
bring
luminaries
down,
then
I
get
across,
but
the
actual
the
may
management
aligning
in
structure
they
may
not
do
they
might
be
on
the
other
side
of
a
credit
card,
there
might
be
a
service
provider,
a
cloud
provider
there's
actually
just
running
this,
for
you,
you've
got
the
application
developers
I'm
people
who
actually
are
they're
writing
applications.
They're.
Writing
Java
they're,
writing,
nodejs,
they're,
writing,
Python
they're
writing,
rails
applications.
They
just
want
them
to
run.
B
They
might
not
care
that
whether
it's
on
connected
or
not,
they
shouldn't
have
to
care
unless
they're
actually
going
to
do
fancier
things,
but
they
do
want
to
benefit
from
joined
and
so
I'm
joined
up
understand
with
certainly
the
Atmos
other
platform
operators
and
I.
Think
that-
and
this
is
something
that's
been
talked
about-
a
little
around
the
stock.
B
You
make
these
community
yeah
Michael
in
the
room
and
like
this
concept
of
application
operators,
actually
people
who
are
probably
going
to
be
more
familiar
with
committees
and
other
sort
of
platform
tools,
they're,
probably
the
types
of
people
who
are
looking
at
by
actually
held
packaging
or
case
on
it
or
higher
level
tools
for
configuration
management
within
Corinthians.
There
are
lean
to
set
standards
for
others.
B
They
might
be
there
operating
the
application
on
the
top
of
the
platform,
not
installing
committees
and
in
some
organizations
that
might
be
the
same
people
and
in
others,
in
some
teams
within
large
organizations
among
the
same
people
and
or
it
might
be
very
distinct,
actually
organizations
completely
and
often
when
it
comes
to
some
metadata.
It
allows
us
to
facilitate
communication
between
these
different
teams.
Groups
where
they're
not
sharing
the
same
tools,
because
they're
not
doing
the
same
jobs,
they're,
not
caring
about
the
same
things,
but
you
invariably
do
want
information
passed
from
one
to
another.
B
A
So
the
first
example
is
this
idea
of
wanting
to
change
who
the
support
contact
is
so
as
an
application
operator.
You
want
to
know
that
somebody
is
going
to
come
and
sort
out
problems.
There
are
many
ways
to
solve
this
problem,
but
this
is
a
kind
of
an
interesting,
interesting
use
case.
I
think,
and
the
key
thing
here
is:
we
want
to
change
who
the
support
contact
is
without
redeploying
software,
so
we're
going
to
use
a
tool
that
I've
been
working
on
called
manifesto.
A
Now
the
idea
behind
manifesto
is
you
have
these
container
images
and
they're
stored
in
the
registry?
The
image
is
actually
made
up
of
a
bunch
of
data
blobs
and
we're
saying
we
want
to
associate
some
arbitrary
metadata
with
a
particular
image
and
the
idea
we
hit
upon
was
why
don't
we
actually
store
that
metadata
and
data
blobs
inside
the
registry,
along
with
the
image
itself?
So
that's
what
Manifesto
does,
and
it
also
puts
together
a
little
image
that
does
the
mapping
between
which
particular
image
has
which
particular
bit
of
metadata
okay.
A
So
this
is
where
it
also
turns
into
audience
participation.
There
is
a
really
really
crappy
website
that
I
have
written
here.
Please
feel
free
to
you've
loaded
reload.
It
keep
hitting
that
particular
IP
address
I'll,
just
say
that
a
few
more
time
so
that
you
have
time
to
forget
that
IP
address
fifty
two
one:
seven
zero
three.
Ninety
two
one
you're
doing
that
and
so
well
earlier
on.
A
So
the
idea
is
true
burner
sees,
is
using
health
checks
to
look
at
the
state
of
this
pod
and
it
will
restart
that
pod
if
it
fails,
and
it
will
fail
because
it's
designed
to
be
really
crap
and
and
at
a
certain
point
it
will
hit
crash,
sneak
back
off
status
and
at
that
point
we're
going
to
say
no
things
are
really
bad.
Somebody
should
come
and
pay
attention
to
this
website,
so
the
contact
details
are
associated
with
the
image
which
has
been
deployed
in
the
pod
and
that
twini
our
app
that
I
just
started.
A
It's
the
core
part
of
it
is
essentially
when
it
detects
that
it's
using
key
petal
to
look
at
the
state
of
the
pod
and
if
it
sees
crash
leaf
back
off
state,
has
been
reached.
It
will
run
manifesto
on
whatever
the
images
for
the
pod
to
get
the
contact
information
and
send
a
message
to
Twilio.
You
need
to
be
refreshing
that
webpage
I.
A
B
A
A
A
Come
on
it
just
takes
a
little
while
to
actually
do
this
update
into
the
registry,
it
will
fit
there.
We
go
okay,
it's
finished
right
and
now
we
have
to
also
wait
for
the
failure
timeout
to
to
give
up
it'll
eventually
say
that
it
could
be
alerted
again,
keep
hitting
refresh,
keep
hitting
refresh.
We
need
it
to
fail
one
more
time
and
eventually,
hopefully
the
alert
will
come
to
me
instead
of
Gareth
I.
A
A
A
A
Okay,
the
next
demo
uses
some
different
uses
manifesto
and
another
different
tool,
and
this
is
about
keeping
up
to
date
with
security
vulnerabilities.
So
we
all
need
to
be
aware
of.
You
know.
The
latest
exploits
that
have
been
discovered
and
we
need
to
keep
our
deployments
patched
with
up-to-date
code
went
on
the
British
get
discovered
there
is
a
project
called
graph.
Is
anybody
heard
of
graph?
A
Is
a
few
hands
we
had
so
grow
face
was
started
by
Google,
open
sourced
by
Google,
and
it's
essentially
an
API
for
storing
managing
querying
metadata
related
to
software
packages,
not
just
container
images.
It
could
be
machine
images,
it
could
be
all
sorts
of
all
sorts
of
things
and
the
core
concepts
in
graph
is
our
notes
and
occurrences.
So
a
note
tells
you
about
a
thing.
For
example,
a
particular
vulnerability
vulnerabilities
are
identified
as
a
standard
way
of
identifying
them
with
what's
called
a
CVE,
a
common
vulnerability,
enumeration
I
think.
A
So
what
that
stands
for
so
every
vulnerability
has
one
of
these
CVE
codes
and
ingre
fayus
terminology.
There
would
be
a
note
for
any
given
CV
that
we
might
know
about
and
an
occurrence
Maps
a
note
to
a
software
entities.
There
might
be
an
occurrence
for
an
image
saying
that
that
image
has
this
particular
vulnerability
within
it
Angra
face
lets.
A
A
You
got
credit
so
that
will
reformat
the
scan
report
into
notes
and
occurrences
and
I've
also
been
working
on
making
manifesto
take
alternative
kind
of
back-end
storages
for
for
metadata,
where
the
idea
is
that
you
can
use
manifesto
to
manipulates
graffia
s--
databases
as
well,
and
then
we
can
run
these
kind
of
powerful
graph
as
queries
over
the
data.
That's
been
stored.
A
A
So
this
is
aqua
and
I'm.
Just
going
to
add
three
to
one
is
kind
of
well,
it's
a
very
old
version
of
that
I
know
has
quite
a
lot
of
vulnerabilities
in
it.
So
there's
a
scanning
process
there-
and
here
we
go
just
in
time
to
see
the
scam
completed
and
the
reformat
er
has
just
created
a
bunch
of
notes
and
occurrence
files.
A
A
Yeah
so
I
have
now
got
package
vulnerability
data
and,
if
I
run
the
get
there
will
be
tons
of
it's
loads
of
data
there,
but
I
can
also
do
things
like
this
is
kind
of
the
graph.
A
is
format
API,
where
I
can
say
can't
find
my
cursor
there.
It
is
I
am
basically
saying
tell
me
about
all
the
occurrences
related
to
the
note
about
this
particular
CVE.
A
A
It's
my
dented
find
by
its
digest,
rather
than
a
particular
label,
which
begins
one
nine
one
four
and
if
I
go
back
in
here,
I
can
just
verify
it's
probably
a
bit
small
to
see
but
down
here
there
is
the
dhaka
digest
and
it
does
indeed
begin
one
nine
one
four.
So
that
was
the
right
metadata
for
the
rights
image
stored
in
graphics.
If
you're
interested
in
prophase,
there
is
a
buff
this
evening
about
it
and
there's
also
a
meeting
on
Friday
morning
about
it
here.
A
A
This
is
one
that
I'm
not
actually
going
to
demo
just
sort
of
due
to
time,
but
there
is
well
Kelcey,
basically
put
together
Agra
face
tutorial,
which
does
this
particular
admission
control
pattern.
As
an
application
operator,
there
may
be
things
that
I
want
to
check
for
before
software
is
allowed
to
run.
In
my
deployment,
the
admission
control
pattern
is
basically
saying
before
you
actually
go
ahead
with
the
deployment
validate
that
some
standards,
whatever
it
is,
we
want
to
check
for
in
the
metadata
has
been
complied
with.
B
Okay,
so
one
of
the
things
about
metadata
is
it
being
so
light
so
I,
guess
piecemeal,
different
types
met
different
purposes
is
that
you
can
have
lots
of
it.
That's
unrelated,
but
often
you
can
build
really
interesting
things
by
combining
different
sources
of
metadata.
So
you
know,
we've
got
a
quick
example
and
again
like
the
similar.
Some
of
them
are.
These
are
illustrative
of
the
types
of
things
you
can
build
really
easily
on
top
of
metadata,
so
as
an
application
operator,
so
that
I
can
help
teams
in
audience.
B
I
want
to
know
what
software
packages
different
teams
are
using.
So
I'll
use
a
tool
and
I
write
on
at
work,
but
the
Khalu
Megan
Percy
a
tool
for
scanning
running
containers
and
collecting
actually
all
sorts
of
different
metadata
from
different
sources
about
them.
So
it
grabs
a
bunch
from
the
docker
API,
as
well
as
from
actually
what's
inside,
that
container
what
my
packages
happen
to
be
there.
B
What
content
that
happens
to
be
there
like
all
good
tunes,
yeah,
actually
just
outputs
a
lot
of
data
and
it's
sort
of
a
low-level
tool,
that's
useful
to
build
things
on
top
of
more
than
a
fancy.
End
user
type
thing.
First,
part
of
the
pumps,
the
end
users
type
thing
which
actually
covers
a
lot.
More
than
containers
limit
guns
are
so
low
level
component
on
public
discovery,
which
is
something
that
some
my
colleagues
work
on
at
work.
So
the
two
bits
of
metadata
I'm
so
interested
in
for
this
to
solve
this
problem.
B
Oh
well,
committees
labels.
They
provide
me
a
mechanism
to
be
to
store
things
and,
in
this
case,
I'm
going
to
store
a
busy
a
mapping
between
deployments
and
the
team
that
manages
them
and
having
those
in
labels
is
also
handy
because
you
can
I
can
filter
that
I
can
use
any
of
the
community
sort
of
native
tools.
Go!
B
Oh,
which,
like
give
me
all
the
logs
from
that
team,
give
me
the
deployments
from
that
team
when
I'm
talking
to
him,
that's
quite
handy
and
Ludwig
on,
provides
being
metadata
about
packages
in
the
containers
which
are
in
the
pods,
which
we've
created
by
the
deployments,
as
they
I'm
not
quite
gone
of
time.
I
think
looking
at
the
clock
to
actually
run
through
this
demo,
but
this
is
sort
of
the
output
and
there's
just
a
couple
of
ein
again,
like
small
Python
scripts.
Sort
of
ten
lines
also
occurred
each.
B
If
you
want
to
have
a
look
at
them,
the
links
will
be
don't
try
and
type
that
out,
but
now,
obviously
this
will
show
the
slides
later,
but
you
can
end
up
with
a
table
like
this
where
this
this
actually
lists
you
and
you
run
this
against
your
communities
cluster.
It
collects
data
from
these
different
sources
and
says
Watchi.
These
are
all
the
packages
software
packages
that
we
found
across
the
entire
set
of
containers
running,
and
these
are
all
the
different
versions.
B
These
are
how
many
times
we
found
them,
and
these
are
the
teams
that
using
them-
and
obviously
you
might
chop
and
change
this
in
different
ways.
You
might
combine
different
sources
of
data,
but
the
thing
there
is
just
how
easy
it
is
to
do
if
you
have
good
metadata
to
build
high
level
tools.
That's
quite
actually
like
interesting
questions
and
you
probably
wouldn't
invest
in,
but
this
isn't
big
enough
to
be
an
application
on
its
own.
But
it's
easy
and
simple
two
buildings
on
top
of
metadata.
B
This
one
I
should
hopefully
have
time
to
dive
into
you
one
of
the
sort
of
things
that
will
probably
come
to
minds.
Well,
what
about
metadata
quality?
It's
fine
to
say:
oh,
oh
great,
I
can
I
can
filter
all
of
the
deployments
by
team
or
route
back
packages
to
the
right
team
or
oh
yeah,
like
routes
pages
to
the
right
support
contact.
But
what,
if
well,
they
haven't
bothered
to
add
that
data,
so
they
haven't
actually
added
the
label
for
team.
B
They
haven't
actually
included
any
data
about
a
support
contact
or
how
I
should
someone
should
be
paged
that
start
of
the
sort
of
building
things
on
top
of
metadata
starts
to
fall
down,
because
the
responses
won't
I
like
in
that
example
with
the
table.
Well,
it
would
be
missing
some
teams
that
might
be
doing
something
bad
and
if
it
was
a
paging
thing
well,
actually
the
page
goes
into
the
eve.
B
There
are
no
one
cares
what
the
application
is
down
and
if
that
sounds
bad,
so
actually
having
a
way
of
enforcing
actually
having
standards
around
will.
Yes,
you
have
to
do
these
things
and
the
reality
is
a
word
document
or
like
for
modern
people.
I
marked
down
file
and
a
git
repository
saying,
like
you,
must
have
these
labels
isn't
enough.
It's
likely
a
like
something.
It's
a
starting
point.
B
B
You
point
out
a
config
file.
You
point
to
a
bunch
of
tests,
you
have
assertions
and
they
will
pass
or
fail,
and
it's
on
a
fairly
straightforward.
I'll
show
this
working
in
a
second
and
you
actually
write
tests
in
skylark,
which
is
basically
a
Python
dialect
firm
that
become
embedded
in
tools.
So
this
is
a
test
to
actually
ensure
the
configs
actually
do
have
a
label
for
T
and
again
like
saying
watch
e.
If
it's
a
deployment
grab
the
labels
assert
that
the
labels
contain
team
or
fairly
straightforward.
B
Using
someone
else's
computer
so
and
I
happen
to
have
the
test
that
we
just
saw
in
a
test.
Folder
obviously
takes
a
uniform
and
I've
got
I've
also
got
a
deployment,
so
the
deployment,
if
you're
eagle-eyed
bitty,
has
the
labels
team
team
sure
that
you
comment
it
out.
So
this
this
is
actually
not
a
good
deployment.
I
don't
want
this
deployment
to
pass
through
my
CI
pipeline.
B
We
get
a
warning
we
get
saying.
Well,
actually
this
doesn't
contain
team
labels
do
not
contain
team,
the
applicants,
weather
and
obviously
that
should
fail
with
a
nonzero
access
code,
so
I
like
from
it
you'd
put
this
into
a
pipeline
and
it
would
not
work.
It's
going
to
tell
you
earlier
that,
like
no
I'm
not
going
to
deploy
this
until
you
fix
that,
so
let's
go
fix.
It.
B
B
B
B
How
easy
is
to
build
things
on
top
of
metadata
and
the
types
of
things
you
can
do
and
coming
back
to
those
sort
of
those
personas
as
well,
and
if
you
are,
if
you
do
sort
of
fit
into
the
sort
of
the
committees
operator,
I,
think
about
what
metadata
would
make
debugging
a
platform
problem
easier
like
what
like
that's
one
of
the
times.
You
really
want
those
sort
of
that
does
tools
and
that
the
ability
to
ask
questions
across
your
infrastructure
and
discover
just
the
right
thing,
not
everything
else.
B
What
would
make
that
easier
as
an
application
developer
like
at
start
adding
metadata
to
your
applications,
and
there
probably
is
a
time
where
you've
added
too
much,
but
that's
probably
not
to
start
with
and,
like
that's
a
problem
for
another
day,
start
adding
metadata.
You
like
whoever's,
running
an
application,
whether
it's
you
or
someone
else
well.
Thank
you
later
and
I
think
this
is
the
sort
of
that
the
application
operator
will,
let's
start
talking
about
tools
that
start
talking
about
schemas.
B
Let's
start
talking
about
interoperability
and
solving
like
the
problems
for
application
developers
and
for
operators,
and
some
of
your
metadata
provides
a
really
super
flexible
platform
for
building
useful
tools
on
top
of
and
I.
Think
with
that
metadata
we
can
make
managing
Coomassie
systems
and
deploying
to
correcting
systems
easier
and
more
pleasurable,.