►
From YouTube: 2022-03-01 CNCF TAG Observability Meeting
Description
* OpenCost / KubeCost
* Observability Personas
* Open Source News (new effort announced)
B
A
B
D
D
C
B
C
C
So
we've
got
a
a
couple
of
things
lined
up
for
today.
Unfortunately,
hubble
sends
their
regrets,
but
they
will
be
joining
us
on
the
15th
fairly
review.
In
addition,
pixie
lab,
who,
who
presented
just
under
a
year
ago,
is
gonna,
give
an
update
on
what
they've
been
up
to
for
the
last
year
coming
up
on
march
15th.
C
Okay,
right
so
on
the
15th
dixie
we'll
be
giving
an
update
of
what
they've
been
up
to
for
the
last
roughly
almost
a
year
since
they
last
presented
and
hubble
who
was
going
to
present
today
sends
the
regrets
and
is
postponing
until
the
15th,
but
we're
expecting
a
fairly
deep
dive.
You
know
on
the
order
of
half
an
hour
of
about
hubble,
which
is
a
fairly
mature
project.
C
A
Matt
how's
it
going
yeah
the
I
was
here
last
time
and
I
briefly
brought
up
open
costs,
which
is
cube's,
cube,
costs,
open
source
project,
I'm
jacqueline
salinas,
I'm
director
of
marketing
and
community
for
cube
cost,
and
today
it
here
is
webb
brown.
He
is
cube's
cost
ceo
and
we
wanted
to
give
you
an
overview
of
open
cost
because
we
are
actually
going
to
be
well.
A
D
Hey
everyone
thank
you
for
for
having
us
really
excited
to
share
about
this
new
open
cost
effort.
I've
got
a
handful
of
slides
that
are
dead,
simple.
Stop
me
at
any
point,
but
can
also
do
questions
at
the
at
the
end
and,
like
jackie
mentioned,
I'm
one
of
the
co-creators
of
kubecost
and
now
one
of
the
like,
you
know,
co-creators
of
of
the
open
cost
project.
So,
first
just
a
really
quick
background.
Like
you
know,
why
are
we
doing
this
and
what
we
see
is
you
know
as
kubernetes
adoption
is
growing.
D
D
So
that
is
what
you
know,
drove
us
to
launch
the
kubecos
open
source
project
and
now
what
is
you
know
becoming
the
open
cost
project?
So
you
know
we
talked
about
the.
Why
a
little
bit,
but
what
in
the
world
is
open
cost
so
open
cost
is
you
know
really
two
things
one
exists
today
and
one
is
just
being
created.
The
first
is
the
core
data
models
and
cost
allocation
engine
from
the
cost
project.
D
So
this
is
already
open
source.
Today
it
is
it's
used
by
thousands,
a
team
of
teams
actually
managing
a
couple
billion
dollars
of
spend
currently,
and
it
provides
real-time
cost
visibility
across
any
dimension
in
a
kubernetes
cluster
or
set
of
kubernetes
cluster.
So
you
can
look
at
cost
by
pod
service.
You
know:
label
annotation,
et
cetera,
et
cetera,
like
very
tight
support
with
the
major
three
cloud
providers,
so
azure,
gcp
and
aws,
and
there
open
open
costs
or
this
allocation
engine
would
do
things
like
support.
D
You
know
any
enterprise
discount
or
spot
or
iiri's
or
savings
plan.
All
the
like
complexity
of
you
know
the
many
different
billing
skus
that
are
out
there
and
then
it
would
also
support.
You
know
on-prem
kind
of
bring
your
own
custom
pricing
sheet
to
where
you
can
say
you
know,
set
an
hourly
rate
of
your
nodes
or
disk.
You
know
cpu
et
cetera,
et
cetera
by
default.
It
like
is
coupled
really
tightly
with
prometheus
teams,
run
it
with.
You
know:
thanos
cortex.
You
know
m3
like
a
range
of
solutions.
D
Basically,
all
it
needs
is
a
like
prom
ql,
you
know
endpoint
for,
like
you
know,
building
it's
its
models
and
just
exposes
all
of
its
metrics
on
a
slash,
metrics
endpoint,
so
it
can
be
used
for
you
know,
alert
manager.
You
know
grafana,
you
know
custom
kind
of
like
you
know,
metrics
that
are
derived
from
cost
and
cost
efficiency
metrics.
D
So
that's
part,
one
again,
that's
used
by,
like
you
know,
thousands
of
teams
today
it
is
currently
branded
as
the
coupe
cost
cost
model,
but
would
become
part
of
the
core.
You
know
open
costs
project,
and
secondly,
is
you
know
what
we've
seen
from
you
know?
Working
with
you
know
hundreds,
if
not
a
thousand
plus
teams
at
this
point
is
that
there's
still
a
ton
of
ambiguity
in
terms
of
like
actually
measuring
cost.
Like
you
know,
how
do
you
handle
shared
resources?
D
D
You
know
a
lot
of
the
teams
that
we
work
with
today.
Had
you
know
different
approaches
to
solving
these
problems
with
typically
like
homegrown
solutions,
oftentimes
in
grafana
dashboard
before
we
started
working
with
them?
So
we've
just
started
this
open
spec
we're
working
on
it
with
a
handful
of
partners.
It
is
a
you
know,
0.0.3
which
we're
like
actively
iterating
on
now,
but
we
view
this
as
a
really
valuable
piece
of
the
open
cost
effort
which
is
again
just
trying
to
help.
D
You
know
facilitate
standards
when
it
comes
to
actively
measuring
costs,
because
there's
both
tons
of
complexity
and
lots
of
of
ambiguity.
So
a
little
bit
of
background
on
us
aj,
who
is
the
co-creator
of
you,
know
coupe
costs
and
now
open
costs.
Both
of
us
were
at
google
for
about
half
a
decade
before,
starting
this,
we
were
working
on
these
kind
of
same
sets
of
problems
originally
on
internal
tooling,
a
jay
also
worked
on
google
cloud
stuff
and
I
worked
on
devtools.
D
D
So
you
know:
where
are
we?
Where
are
we
going
so
jackie
mentioned
in
the
process
of
submitting
this
for
cncf
sandbox
project
which
we're
you
know
super
excited
about?
We
want
to
invest
a
lot
in
the
community
and
you
know
do
everything
we
can
to
to
be
great
contributors
and
are
excited
about.
You
know
partnering
with
others,
and
we
view
it
as
like.
D
Have
a
lot
of
you
know,
intersection
and
again
that,
like
the
majority
of
our
users,
are
running
prometheus
and
cortex
and
and
thanos
today,
but
also
feel
like
you
know,
we
could
still
learn
a
ton
from
this
community
when
thinking
about
these
broader
observability
problems
so
I'll,
stop
there
again
super
quick
rundown
on
open
cost
and
you
know
tangentially.
You
know
coupe
costs
happy
to
share
more
on
on
any
part
of
this.
B
D
Yeah,
so
it
is
all
this
software
to
run
this
model.
So
what
it
looks
like
is,
it
would
go
and
say
and
happy
like
come
back
with
more
architecture
but
like
it
would
detect
that
you
are
on,
say
an
eks
cluster.
It
would
go
and
fetch
ek
or
aws
billing
for
you.
It
would
then
build
this
model
and
expose
these
metrics
on
a
slash.
D
Metrics
endpoint,
the
the
open
source,
doesn't
ship
with
a
prometheus,
but
if
you
point
it
at
a
prometheus
service
address,
it
would
then
build
all
these
data
models
and
expose
all
of
the
apis
needed
to
say
what
is
the
cost
of
a
named
base,
a
service,
a
cluster,
a
pod,
a
container
etc
so
yeah
it
is.
It
is
a
working.
You
know,
piece
of
software
that
you
know
exposes
data
on
these
apis
and
also
has
a
simple
ui.
I
would
say
at
a
high
level
like
analogous
to
maybe
the
prometheus.
You
know
console.
D
We
do
across
this
and
the
community
home
chart.
I
would
estimate
between
50
and
100
contributions,
cool
and
and
yeah.
So,
like
you
know,
thousands
of
teams
using
it
in
in
like
their
production
environment.
One
one
thing
to
point
out
is
that
coupe
cost.
Today,
while
we
have
a
community
version,
which
is
just
like
a
bundled
version
of
open
source,
we
also
then
have
like
enterprise
products.
On
top
of
it
yeah,
you
know,
settle
and
license
those
independent
of
everything
here.
E
D
E
D
Really
common
features
would
be
like
you
know
our
back,
so
let's
say
you've
got
you
know,
12
different
clusters
and
you
have
teams
or
departments
allocated
by
so,
like
you
know,
name
space,
you
want
certain
teams
to
be
able
to
see
only
their
cost
data.
Now
that
would
be.
You
know
one.
That's
common
and
you
know
integrating
with
say,
like
you
know,
sso
and
saml,
to
do
that.
D
Another
would
be
working
with
teams
to
do
like
long-term
metric
retention
get
that
set
up.
So
if
you
have
like
either
use
a
thanos
that
we
help
you
deployed
or
you
have
an
existing,
you
know
cortex
or
thanos
deployment.
We
would
work
with
you
to
like.
Have
you
know,
365
day
look
backs
in
your
large
scale,
enterprise
environment,
to
like
really
help
you
tune
that
and
then
all
the
like.
You
know,
support
and
services
that
come
with
that
so
like
when
you
roll
this
cost
data
out
to
your
finance
team,
we're
there
to
support
you.
E
That's
interesting
one
step
by
step
so
number
one.
You
would
provide
this
by
tenant,
it's
almost
the
same
concept
as
a
grafana
enterprise,
metrics,
okay.
Second,
what
you
just
mentioned!
You
would
keep
this
on
the
kind
of
cortex.
In
this
case
I
assume
on
bacon
such
as
s3,
so
you
just
set
up
some
retention
time.
This
is
what
your
software
does
and-
and
lastly,
you
mentioned
so-
you
would
provide
this
information,
for
example,
to
some
departments
based
on
what
reporting
solution,
or
you
just
do
some
different
extractions
different
way
to
extract.
D
Yeah
great
question:
so
a
combination
of
either
like
exporting
csv,
you
know
from
our
front
end
or
maybe
even
just
taking
you
know,
screenshots
of
reports
on
the
front
end.
Also,
like
you
know,
a
lot
of
teams
will
just
hit
the
apis
that
are
the
same
as
the
open
source
apis
and
extract
that
to
like
some
metering
or
billing
system
that
they
have
internally,
sometimes
other.
You
know
tooling,
like
you
know,
in
their,
you
know
like
devops
workflow,
something
like
lens
marantis
or
you
know,
d2,
iq
systems,
etc.
E
D
Push
it
yeah,
so
we
so
our
like
the
open
source
project
can
run
in
kind
of
two
different
ways.
One
would
be
kind
of
agent
mode,
just
which
is
what
you
said.
So
it's
like
you
know,
go
and
fetch
all
this
billing
data
and
then
tell
you
the
cost
of
a
node
disk
load,
balance
or
et
cetera,
et
cetera,
and
that
would
just
be
expose
those
metrics
on
a
slash,
metrics
endpoint.
You
know
you
can
consume
those
in.
You
know
any
prometheus
cortex.
E
D
Yeah,
absolutely
there
should
be
a
github
link
on
that
page.
But
let
me
just
drop
here
here
is,
and
so
we
would,
you
know,
as
part
of
the
like,
you
know,
submission
process.
We
would
move
this
to
an
open
costs
repo.
You
know
we
would
rebrand
this.
We
would
like
change
the
readme,
but
this
is
kind
of
what
is
largely
the
like
core.
C
I
have
an
additional
question,
so
does
the
cost
model
today
or
do
you
plan
to
cover
such
things
as,
like
you
know,
bulk
buying,
compute,
early
or
various
discount
plans,
which
can
quite
substantially
change
the
raw
costs?
That
would
be
reported
for
say,
like
you
know,
instance,
whatever
cost
this
much.
D
Yeah
great
question,
so
it
does
support
it.
It's
actually
supported
more
easily
with
our
like
our
open
source
helm
chart
which,
if
you
go
to
like
you,
know,
github.com
coupe
costs.
You
know
lives
there.
So
so
we
absolutely
support
that
on,
like
community
version
of
coupe
costs,
I
do
think
we
have
a
decision
to
make
as
a
community
around
what
exactly
we
support
in
the
open
cost
effort,
whether
it's
like
just
like
you
said
matt,
all
of
the
you
know
crazy
enterprise
discounts
that
can
you
know,
vary
widely
across
the
cloud
providers.
D
So
you
know,
I
think,
torn
so
and
part
of
why
I
think
it's
an
open
question
in
our
eyes
is
that
that
requires
like
a
cloud
integration
with
your
billing
data
right
versus
open
cost.
Today,
you
literally
just
like
you
know,
helm,
install
or
you
know,
deploy
a
pod
and
it
just
detects
that
you're
on
again
a
gta
cluster
and
then
pulse
gcp
pricing.
D
D
I
may
want
to
learn
a
little
bit
more,
and
this
would
also
also
probably
be
more
kind
of
the
expertise
of
our
team,
and
you
know
like
co-founder
here,
but
but
yeah
absolutely
should
you
know
should
not
have
any.
You
know
major
issues
not
aware
of
any
like
you
know
real
limitations
and
obviously,
like
you
know,
everything
is
deployed
with
you
know:
read-only
access,
you
know.
E
C
D
Definitely
and
we've
got,
we've
got
a
road
map
dock
on
there,
which
you
know,
that's
that's
part
of
it,
but
I
think
one
of
the
big
ones
that
I
see
in
the
short
term
is
actually
around
kind
of
part.
Two
of
this,
which
is
the
spec
we're
really
excited
about
you
know
just
getting
community
voices
involved
in
you
know
creating
a
standard.
D
Here
I
mean
again,
we
just
see,
like
we've,
probably
seen
a
hundred
different
ways
that
teams
have
like
implemented
this
and
ultimately
it's
like
the
cost
of
a
container
is
not
like
how
to
measure
the
cost
of
a
container
is
not
agreed
upon
across
the
community.
I
see
that
as
like
a
super
valuable
first
milestone,
and
then
I
think
we
can
build
a
ton
on
top
of
that.
But
beyond
that,
you
know
see
an
opportunity
for
us
to.
D
C
D
Yeah
so
we'd
support,
like
you
know,
aks
eks,
you
know
gke
and
then,
like
you
know
any
you
know
roll
your
own.
You
know
cops,
you
name
it
like
clusters
on
those
environments.
More,
like
you
know,
the
the
ibm
clouds
and
the
oracle
clouds,
and
you
know
digital
ocean
I'd,
love
to
see
us.
You
know
the
project
support,
you
know
in
the
near
term.
D
You
know
so
that's
a
one
thing
I
would
say
this
is
maybe
a
little
outside
the
box,
but
one
thing
that
our
team
is
really
interested
and
passionate
about
is
kind
of
like
the
the
energy
impact
of
this
project.
Right
so,
like
you
know,
the
carbon
emissions
like
footprint
is,
you
know
closely
tied
to
the
actual
financial
cost?
D
D
Yeah,
so
google
and
some
of
their
and
I'm
actually
can't
claim
to
be
like
an
expert
here
in
monitoring.
You
know
co2
emissions,
but
google
exposes
ratings
by.
I
believe
it's
still
by
like
dc
and
not
and
but
potentially
by
a
z
today,
where
you
know
they
es
especially
like
essentially,
I
suppose,
a
carbon
rating.
D
So
we
believe
that
could
be
like
a
valuable
input
to
say
again
the
cost
of
like
resources
consumed
in
those
environments
and
like
use
that,
as
a
you
know,
like
an
index
or
multiplier
to
to
like
scale
that
across
different
environments,
but
ultimately
be
coming
up
with,
like
you
know,
for
every
say,
cpu
hour
or
gpu
hour.
Here
is
like
the
carbon.
C
Cool
and
again
one
of
my
last
questions,
I
guess:
how
can
people
engage
like?
Do
you
have
open
meetings?
What's
your
governance
model?
Is
there
documentation
for
new
contributors
that
might
want
to
might
want
to
either
provide
some
of
their
real
life
experience
or
engineering
time?
Or
what
have
you.
D
Yeah
great
great
question
and
jackie
can
share
more
here,
but
going
to
be
doing
a
lot
more
with
this
like
contribution,
you
know,
of
course,
open
costs
et
cetera,
but,
like
you
know,
on
the
documentation
side
we're
actively
working
on
the
spec
now
so
that
is
like.
I
just
want
to
make
one
call
out
that,
if
anybody's
interested
in
contributing
there,
you
know
making
a
bunch
of
progress
as
we
speak,
but
yeah
a
lot
more
to
come
on
governance.
Jackie,
not
sure
if
you
want
to.
A
Look
it
up
that
I
can
drop
in
our
notes
of
how
to
start
contributing
to
open
cost,
but
absolutely
that's
like
the
other
reason
why
we
also
want
to
get
pretty
integrated
into
the
cncf
and
kubernetes
community
is
because
we
see
a
lot
of
that
persona
overlap
in
these
communities
and
then,
like
web
mentioned.
You
know
one
of
the
things
that
we
also
want
to
be
able
to
help.
As
a
as
as
a
member
of
these
communities
is,
can
we
start
standardizing
some
of
these?
You
know
practices.
D
C
C
D
Yeah,
you
know
hand
wavy
for
sure,
but,
like
I
feel
like
we're
on
a
track
to
be
at
like
a
1.0
kind
of
this
summer.
So
it's
called,
like
you
know,
late
late,
q2,
early
q3,
you
know
have
probably
like
you
know,
five
or
so
five
or
six
or
so
partners
in
there
like
actively
contributing
to
it
now
so
like
well,
very
much
welcome
feedback
but
yeah
relatively
early
days.
But
I
feel
like
we're
making
fast
part
of
this
awesome.
C
C
Thank
you.
Thank
you.
Thanks
for
coming
and
and
if
you'd
like
as
things
move
along,
and
you
know
assuming
you're
into
the
sandbox,
you
know
feel
free
to
come
back
for
a
more
technical,
technically
focused
deep
dive
either
to
this
meeting
or
we
could.
We
could
make
it
happen,
async
and
post
the
video
for
you
so
yeah.
That
sounds
awesome.
D
D
F
F
F
How
can
how
can
some
of
the
the
project
leaders
kind
of
better
engage
these
personas
or
kind
of
grow
their
projects
by
targeting
new
personas?
That
kind
of
aren't
currently
being
kind
of
reached
out
to
for
a
particular
project?
So
so
yeah
that's
kind
of
kind
of
the
high
level
goal
of
of
this.
Of
this
effort.
I've
been
kind
of
taking
the
lead
in
terms
of
getting
things
started
so
back
in
august.
So
like
pre
pre
cube
con
north
america.
F
I
kind
of
did
a
bunch
of
interviews
and
reached
out
to
a
bunch
of
tag
members
just
kind
of
get
a
sense
of
what
their
persona,
what
their
role
is
and
and
their
current
company
and
like
kind
of
what
their
interaction
is
with
open
source
and
some
of
these
cncf
projects
and
yeah.
So
I've
I've
done
nine
interviews
so
far
and
kind
of
across
kind
of
a
range
of
different
companies
somewhat
some
that
are
more
like
enterprise
like
oracle
and
then
some
that
are
like
more
kind
of
more
new.
F
F
These
efforts
back
up
once
things
quiet
down
a
bit,
it's
kind
of
been
a
crazy
start
to
the
year,
but
but
yeah,
if
you're
interested
in
helping
out
or
kind
of
helping
do
any
of
these
interviews
or
contributing
in
any
way
just
yeah
feel
free
to
ping.
Me
there's
also
like
the
an
issue
started
in
the
github,
but
I
have
like
a
list
of
I
think
I
put
in
the
in
the
issue
like
list
of
questions.
F
But
these
are
just
some
of
the
high
level
goals
they
have,
and
I
guess
anti-goals
they
have
so
I
won't
go
through
all
of
them,
but
you
can
kind
of
get
a
sense
for
what
they're
going
for
here
and
just
for
visibility.
These
are
the
target
personas
that
they've
come
up
with
so
far
that
are
supposed
to
kind
of
cover,
all
the
all
the
use
cases
and
all
the
kind
of
potential
personas
that
would
engage
with
any
of
the
cncr
projects
across
the
entire
landscape.
F
So
a
lot
of
these
titles
like
well,
I
mean
there
some
of
them.
I
you
know,
I
don't
you
don't
see
as
often
in
observability,
but
I
think
I
think
we
can
kind
of
use
them
as
like
a
starting
point
and
then
kind
of
go
from
there
and
and
then
the
two
that
are
currently
being
worked
on
are
the
platform
engineer,
persona
and
then
the
cloud
security
engineer
or
architect
persona
and
that
that's
kind
of
determined
by
the
subcommittee.
F
And
but
you
know
these
are
the
other
ones
they
want
to
get
to
at
some
point
and
just
to
give
you
an
example
of
what
the
end
the
end
product
of
this
would
look
like
at
least
for
right
now,
I'm
sure
it'll
change.
This
is
just
kind
of
the
initial
stage,
but
this
is
this
is
an
example
of
one
of
the
cards.
F
You
know
various
personas
will
get
assigned
to
different
projects
so
that
the
project
owners
in
those
communities
can
know
like
how
better
to
how
best
to
like
tailor
their
work
around
these
personas
and
how
best
to
like,
engage
with
them
to
hopefully
grow
the
communities
building
like
increased
engagement,
all
those
things
so
so
yeah.
So
that's
that's
kind
of
the
update
here.
That's
I
don't
really
have
too
much
more.
F
Actually
it's
pretty
kind
of
short
and
sweet,
but
since
since
these
efforts
are
already
being
kind
of
ongoing,
I
was
I
do
want
to
kind
of.
I
want
to
keep
doing
the
interviews
and
getting
collecting
information
and
research
on
mayan
from
the
observability
side,
but
kind
of
wanting
to
wait
until
things
are
a
little
bit
more
fleshed
out
and
like
established
with
this
subcommittee
project,
so
that
I
can
like
kind
of
leverage
the
work
they've
been
doing
since
the
goal
is
to
hopefully
standardize
these
across
the
landscape.
G
Are
you
planning
to
then
analyze
the
various
interviews
to
extract,
for
example,
on
the
personas,
the
type
of
platform
engineers?
They
are?
Obviously
the
I
mean
it's
if
at
one
minute,
it's
very
logic,
I'm
looking
for
more
health
metrics
on
the
platform
looking
at
the
logs
on
putting
or
events
on
kubernetes,
to
help
me
to
diagnose
how
my
platform
is
behaving,
so
that
will
be
the
the
signals
or
the
type
of
interests
for
that
type
of
personas
compared
to
a
pure
application
owner.
G
Who
is
pretty
much
interesting
on
how
fast
is
the
methods
functions,
the
the
the
the
throughputs
going
on
my
services
and
so
on?
So
I
think
there
is
from
I
mean
from
from
what
I
know,
there's
different
interests
and
different
priorities
depending
on
the
role
of
those
each
personas.
Are
you
planning
to
go,
then,
on
that
road
say
highlighting
the
areas
that
more
makes
more
sense
for
that
particular
type
of
personas?
Or
is
it's
mainly
to
to
report
global
statistics
on
on
who
is.
F
I
think,
for
the
purposes
of
our
tag,
we
can
then
take
some
of
these
personas
that
they'll
have
kind
of
built
out
and
then
like
specialize
them
more
for
our
own
purposes,
just
for
the
the
observability
based
projects
and
then
that
and
then,
when
that
and
when
that's
ready
to
go
then
yes,
I
will.
I
will
then
pull
from
like
interviews.
C
Yeah
I
I
can
provide
a
little
context
from
last
year
as
well.
You
know
we
found
ourselves
in
some
of
the
meetings
last
year
and
even
recently
you
know
you
know
talking
about
you
know,
so-and-so
would
like
this,
or
this
would
be
useful
for
for
this
person
or
that
person,
and
we
didn't
really
have
a
common
vocabulary.
C
So
you
know
gibbs
kind
of
jumped
in
last
year
and
started
to
try
to
provide
some
some
structure
and
shape
around
this
and
then
late.
Last
year
the
business
value
sub
committee
launched
a
similar
effort,
as
mentioned,
and
I've
provided
a
link
to
our
february
first
meeting
from
a
month
ago,
where
catherine
paganini
came
and
gave
an
overview,
a
brief
overview
of
the
business
value
subcommittee
as
well
as
some
of
those
other
other
efforts
and
if
folks
aren't
familiar
they're
they're
building
a
matrix
of
all.
C
You
know
to
taking
the
cncf
landscape,
which
is
you
know
that
that
massive
arch
eye
chart
and
trying
to
kind
of
go
through
sector
by
sector
or
subsection
by
subsection
to
provide.
You
know
more
comparison
and
one
useful
thing
that
my
highlight,
which
I'll
dredge
up
in
a
few
minutes
to
the
notes
as
a
comparison
of
all
of
the
open
sourcing
dresses
that
are
currently
there.
So
comparing
you
know
nginx
to
this.
To
that
to
that
you
know
you
know,
for
that
section.
F
Yeah,
but
I
think
it'll
be
helpful
once
like
the
projects
will
have
like
they'll,
maybe
even
little
icons
at
some
point
when
these
are
a
little
bit
more
established
of
kind
of
which
personas
relate
most
closely
to
those
projects.
You
know,
I
think,
that'll
help
people
that
are
new
to
the
cncf
are
looking
to
you
know
start
using
a
cncr
project,
they'll
be
able
to
see
kind
of
where
how
it
aligns
with
their
with
with
what
they're
wanting
and
their
needs
and
their
goals
based
on
the
personas
that
are
tied
to
them.
F
So
it'll
kind
of
help
with
that,
because
I
think
there's
there
is,
there
are
so
many
projects
now.
So
it's
kind
of
hard,
for
you
know
someone,
that's,
maybe
not
as
familiar
with
like
with
some
of
the
land,
with
the
landscape,
to
like
know
where
to
start
and
which,
how
one
project's
different
than
the
other.
So
this
this
will
hopefully
help
with
some
of
that
longer
term.
F
But
yeah,
if
you,
if
you
would
like
to
speak
with
me
to
like
kind
of
get
so
I
can
get
some
more
insight
on
like
kind
of
like
how
your
role
fits
into
your
greater
org
and
with
the
cncf
like.
I
would
love
to
set
up
some
time
and
then,
if
you
know,
if
you
are
interested
in
helping
out
as
well
like
definitely
let
me
know.
C
I
would
encourage
people
also
to
reach
out
to
your
professional
networks
like
if
you
have
someone
in
mind
who's
been
looking
for
a
way
to
engage.
That
might
not
be.
You
know,
writing
code,
but
but
more,
you
know
providing
domain
expertise
or
insight
into
what
motivates
them,
what
their
goals
are.
What's
important
to
them,
et
cetera.
Please
do
make
some
connections.
C
C
C
C
G
So
the
idea
is
to
produce
10
minutes
videos
really
on
a
regular
pace.
And
then,
if
you
need
more
details,
I
have
another
youtube
channel
where
I
can
provide
more
details
on
the
technology
itself.
But
the
idea
of
this
format
of
video
is
more
about
sharing
the
news
on
the
latest
news
of
the
open
source
world.
So
that's
why
the
the
biggest
challenge
that
I
have
as
of
now
is
to
get
the
news,
because
I'm
able
to
search
everywhere.
G
So
if
you
have
a
source
of
data
source
that
are
is,
is
suitable
and
that
we
that
it
could
be
reliable
for
for
this
project.
Please
share
it.
So
then
I
I
could.
I
could
use
it
and
and
build
the
content
from
there.
Yeah
thanks
gibbs,
I'm
working
with
michael
on
this
one,
so
that
is
obviously
a
great
source
for
that.
We're
gonna.
G
G
I'm
looking
mainly
for
observability,
but
but
again
we
can
be
very
more
on
the
cloudiness
space
not
necessary
on
observability,
but
if
there
is
any
solution
that
could
help
you
to
administrate
your
cluster
in
a
smarter
way
or
or
to
manage
your
auto
scaling
or
whatever.
So
I
think
it
deserves
to
be
promoted.
Because
again,
the
success
of
the
project
depends
on
how
many
people
people
is
actually
using
it.
Yeah.
B
C
B
C
Back
story
so
so
about
half
a
year
ago,
we're
about
to
we're
about.
We've
been
we're
about
to
engage
with
the
community
sites
that
the
cncf
supports,
and
so
we
have
a
youtube
channel
and
sort
of
licensed
from
the
tvc
to
be
creative
and
and,
however,
we
like
so
so,
henrik
actually
has
a
really
cool
youtube
channel.
Today,
I'm
going
to
put
it
in
the
notes
called:
is
it
observable,
backed
by
some
github
repos?
C
So
you
can
follow
along
and
I've
been
going
through
some
of
some
of
henrik's
work
from
the
last
year
and
it's
fascinating
and
awesome,
and
so
I
think
the
thought
would
be.
This
might
be
something
that,
in
the
context
of
the
tag
we
could
have
sort
of
a
regular
cadenced
pulse
of
sort
of
a
curated
set
of
what's
happening.
A
D
A
So
I
grew
that
program
and
I
do
love
to
produce
content.
So
actually
that's
how
henry
and
I
knew
each
other
is
from
our
podcast
day
so
happy
to
contribute
there.
I'm
have
like,
but
that's
why
I
was
asking
all
these
questions,
because
it
is
important
for
us
to
just
figure
out
like
how
do
we
intake
people's
ideas
and
how
do
we
just
spread
the
news
within
our
own
networks
and
say:
hey
like
if
you've
got
observability
news?
This
is
like
where
you
should
be
submitting
it
so
yeah.
C
We
need
engineering
too,
but
there's
opportunities.
You
know
across
a
wide
variety
of
disciplines
to
contribute-
and
I
think
that's
that's
one
place
where
I
think
we
can
set
an
example
for
for
the
community
and
some
of
the
other
tags
as
well
to
bring
in
these
other
disciplines
that
are
very,
very
much
needed.
A
Yeah
totally,
but
a
quick
question
for
the
tag
observability
do
we
have
a
document
on
for
like
non-technical
contributions,
because
that
also
sometimes
it's
like
most
people
when
they
think
of
open
source,
they
always
think
of.
Oh
that's
like
a
technical
type
of
contribution,
and
it's
so
not
true.
Like
you
mentioned,
we
need
event
coordinators.
We
need
content
producers.
We
need
editor
like
copy
editors,
all
this
type
of
stuff,
so
I
think
the
kubernetes
community
has
already
a
document.
That's
like
how
to
do
non-technical
contributions.
A
C
I
completely
agree:
I
can
link
you
to
talk
about
it
last
fall
but
feel
free
to
make
an
issue
in
our
repository
and
drive
it.
I
mean
you
know
it's
a
it's
an
open.
You
know
the
tags
in
general,
you
know.
I
say
this
a
lot
and
I'm
probably
like
a
broken
record
of
folks
that
have
been
here
before,
but
you
know,
there's
really
two
main
missions
right.
One
is
to
advise
and
inform
the
toc
on.
C
You
know,
gaps
and
opportunities
in
the
ecosystem,
but
you
know
the
other,
perhaps
even
larger
portion.
That
makes
the
first
one
possible
is
to
bring
together
vendors
and
users,
cloud
providers
and
and
folks
from
from
from
all
stripes
and
walks.
So
we
can
kind
of
come
together
in
this
forum
and
that
is
by
definition,
multi-disciplinary
and
quite
broad.