►
From YouTube: OTel Me All About OpenTelemetry
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
Conduct
and
then
I'll
hand
over
to
reese
lee
developer
relations
engineer
at
new
relic
a
few
housekeeping
items
before
we
get
started
during
the
webinar
united
able
to
speak
as
an
attendee,
but
there
is
a
chat
box
on
the
right
hand.
Side
of
your
screen,
please
feel
free
to
drop
your
questions
there
and
we
will
get
to
as
many
as
we
can.
At
the
end.
This
is
an
official
webinar
of
the
cncf
and,
as
such
is
subject
to
the
cncf
code
of
conduct.
A
Please
do
not
add
anything
to
the
chat
or
questions
that
would
be
in
violation
of
that
code
of
conduct
and
please
be
respectful
of
all
of
your
fellow
participants
and
presenters.
Please
also
note
that
the
recording
and
slides
will
be
posted
later
today
to
the
cncf
online
programs,
page
at
community.cncf.io,
under
online
programs.
A
B
Thank
you
so
much
libby,
hello,
hello.
I
hope
everyone's
summer
is
off
to
a
great
start.
I
hope
it's
not
too
hot
or
too
wet.
Where
you
are.
Please
stay
safe,
of
course,
I'm
saying
happy
summer
as
I'm
in
a
sweater
I'm
in
the
northwest,
so
welcome
to
today's
cncf
live
webinar,
hosted
by
me,
risley,
and
thank
you
so
much
for
being
here
or,
if
you're,
watching
the
recording.
Thank
you
so
much
for
doing
so.
B
I
gotta
say
I'm
very
excited
about
my
title.
Oh
tell
me
all
about
open
telemetry,
the
current
and
future
state,
navigating
the
projects
and
getting
involved.
You
are
likely
familiar
with
it,
but
hotel
is
shorthand
for
open
telemetry,
which
is
why
I'm
so
stoked
on
the
session
title.
B
So
to
start,
I'm
going
to
take
you
through
our
agenda
for
the
session.
I
will
first
kick
things
off
with
a
few
introductions
and
then
we
will
get
into
the
current
and
future
state
of
the
projects,
navigating
the
projects
and
finally,
getting
involved
with
the
project.
We
should
also
have
some
time
at
the
end
for
some
q
a
for
any
lingering
questions
about
what
we've
covered
today.
B
B
B
I
previously
worked
directly
with
observability
end
users
as
a
technical
support,
engineer
and
that's
something
that
I
really
really
enjoyed
and
I'm
glad
that
I
get
to
continue
working
with
end
users
in
this
role.
I
also
enjoy
learning
from
and
working
with
project
contributors.
So
I
am
very
excited
to
share
this
presentation
with
you
today.
B
Also
real
quick.
I
have
a
tendency
to
talk
fast.
So
if
you
need
me
to
slow
down,
please
feel
free
to
write
it
in
the
chat.
That
will
also
be
a
reminder
for
me
to
slow
down.
So
please
do
so.
If
you
need
me
to
slow
down
before
we
get
into
the
meat
of
this
webinar,
I
just
want
to
set
the
stage
for
the.
B
Why,
behind
it
so
having
worked
with
end
users
directly
for
some
time
now,
and
also
seeing
what
came
up
from
discussions
and
meetings
at
year,
kubecon
that
was
just
held
in
spain
last
month
in
may.
Two
things
are
very
clear:
one
people
are
very
excited
about
open
telemetry.
They
want
to
learn
about
it.
They
want
to
know
how
to
use
it,
they
want
to
actually
use
and
adopt
it
within
their
organization,
and
a
lot
of
them
want
to
get
involved
in
some
way
or
another.
B
However,
most
people
don't
really
know
how
to
navigate
the
community
and
the
project,
for
example,
where
to
go
to
get
help
or
how
to
contribute,
or
even
what
to
contribute.
Two.
The
project
and
community
can
use
quite
a
bit
of
help
and
I'll
cover
this
in
more
detail
later
on
in
the
session,
including
not
just
how
to
contribute,
but
also
why
you
might
want
to
contribute
so.
Therefore,
the
purpose
for
this
webinar
is
twofold:
to
help
end
users
navigate
the
community
and
the
project,
and
also
to
encourage
contributions
to
the
project.
B
All
right,
so,
if
you're
watching
this
today,
you
likely
already
at
least
know
what
open
telemetry
is
so
I'll
just
do
a
brief
refresher
intro
here,
but
then
I
am
going
to
get
into
a
little
bit
more
detail
about
some
of
its
architectural
components
to
help
you
solidify
your
understanding
and
knowledge
during
the
navigating
the
project
section.
B
B
It
was
first
developed
in
2019
with
the
merging
of
two
competing
open
source,
instrumentation
projects,
open
tracing
and
open
source,
open
tracing
and
open
senses.
B
Also
as
important
as
it
is
to
know
what
open
telemetry
is,
it
is
also
important
to
know
what
it
is
not
open.
Telemetry
is
not
a
back
end
or
storage
solution.
It's
not
an
observability
platform.
It's
an
observability
observability
framework,
see
that's
what
I
mean
when
I
talk
too
fast.
Okay,
I'm
going
to
consciously
slow
down
now
open
telemetry
provides
instrumentation
standards
for
generating
telemetry
data,
but
it's
not
an
observability
solution
by
itself.
B
B
B
B
B
If
you
did
not,
I
want
to
give
a
shout
out
to
paul
bruce
who
is
an
oly
fest
organizer
and
who
is
very
passionate
about
observability.
He
put
together
a
pretty
detailed
rundown
of
the
event
on
his
blog
paul
s,
bruce
dot,
io
blog
and
I
just
realized.
I
did
not
include
that
in
the
slide,
but
let
me
know
if
you
need
the
link
again
and
I'll
share
it
with
you
at
the
end.
B
But
again,
that's
paul
s,
bruce
dot,
io,
slash
blog,
so,
as
you
can
see,
and
as
I'm
sure
you're
aware,
chase's
has
been
g8
for
a
while
now
metrics
is
quickly
getting
there
with
a
current
number
of
five
release
candidates,
and
this
is
just
since
it
was
announced
back
in
may
and
also
earlier.
I
shared
a
link
to
the
status
page
on
the
main
website,
so
that's
great
for
getting
high
level
updates,
but
it
is
recommended
that
you
check
the
read
me
in
the
specific
github
repos
for
more
detailed
information.
B
I
also
mentioned
baggage
earlier.
It's
not
included
in
this
table.
It
is
still
considered
a
signal
and
it
is
now
completely
stable.
Baggage
is
not
an
observability
tool.
It's
a
system
for
attaching
arbitrary
keys
and
values
to
a
transaction
so
that
downstream
services
may
access
them.
B
What's
new
and
upcoming,
so,
as
I
mentioned,
metrics
release
candidate
and
general
availability
or
j
releases
profiles
are
being
added
as
a
new
signal.
This
was,
I
believe,
also
just
announced
at
hotel
community
day.
B
Logging
ga
is
targeted
for
next
year,
so
that's
pretty
exciting
and
I
have
written
down
here,
instrumentation,
availability
and
quality.
So
there
is
an
effort
to
expand
the
availability
and
quality
of
open,
telemetry
instrumentation.
B
I
believe
it's
scheduled
for
the
summer,
but
of
course
things
are
subject
to
change,
so
I
would
keep
an
eye
on
the
documentation
for
updates.
So
this
work
includes
providing
instrumentation
for
a
wider
variety
of
important
libraries,
as
well
as
providing
testing
and
ci
cd
tools
for
writing
and
verifying
instrumentation
quality.
B
This
began,
I
want
to
say
last
month
in
may
so
very
new,
but
the
goal
is
to
develop
a
standardized
demo
application
that
is
jointly
written
in
stages,
starting
with
producing
metrics
and
traces.
B
This
is
so
the
reason
this
thing
came
about,
based
on
my
understanding
is
as
the
project
matures
and
customers
are
increasingly
looking
for
more
onboarding
guides,
so
they
can
try
the
tools
themselves,
there's
a
lot
of
demo
applications
by
multiple
vendors,
but
there
isn't
a
standardized
one
provided
by
the
community,
and
so
that's
what
the
sig
aims
to
do.
B
If
you're
not
aware
of
how
to
do
so
and
speaking
of
end
users,
the
end
user
working
group
has
been
working
hard
to
get
feedback
from
end
users
with
the
goal
of
providing
a
space
for
all
of
you
to
get
together
and
talk
about
your
experiences
and
share
feedback
with
each
other
and
challenges
that
you
face
with
using
open
telemetry,
whether
in
your
organization
or
just
on
your
own
stay
tuned
for
more
information
about
this,
as
it
is
still
being
developed.
But
again
I'll
cover
this
a
little
bit
more
later,
as
well.
B
Okay,
sorry,
I
got
distracted
by
by
the
chat,
okay,
okay,
so
now
we're
going
to
move
into
the
section
of
navigating
the
project
where
I
will
go
over
the
following
core
concepts
and
components:
the
community
and
a
few
of
its
components:
cigs
governance,
committee,
technical
committee
and
I'm
going
to
touch
a
bit
on
documentation
as
well
and
finally,
a
bonus
section
about
otops.
B
Oh
snap,
okay,
so
there
are
a
lot
of
moving
parts
in
open
telemetry,
so
I
want
to
take
some
time
to
kind
of
break
them
down
by
answering
the
question:
what
are
some
of
the
various
open,
telemetry
concepts
and
components?
B
The
terms
I've
listed
here
are
ones
you
will
hear
and
see
frequently
as
you
learn
about
and
use
open,
telemetry
understanding
what
each
one
refers
to
will
help
cement
your
knowledge
and
enable
you
to
effectively
navigate
the
project.
B
The
open,
cilantry
api
you'll
hear
apn
sdk
a
lot,
and
so
I
want
to
kind
of
differentiate
the
two.
So
the
open,
telemetry
api
provides
a
standard
way
to
collect
instrumentation
data.
It's
used
by
app
developers
and
library
authors
to
instrument
their
code
to
generate
telemetry
data.
B
B
B
B
B
So,
for
example,
http
or
database
calls
are
consistent,
regardless
of
which
platform
or
language
is
being
used.
So
if
a
python
application
calls
the
dotnet
application,
you
can
rest
assured
that
both
of
those
applications
will
conform
to
http
conventions,
for
example
the
http
dot
method
attribute,
which
is
used
to
specify
how
the
call
was
made.
For
example,
I
get
a
post
or
put
these
will
be
uniform
across
the
python
and
donna
applications.
B
For
example,
the
open,
telemetry
specification
or
spec
provides
blueprints
for
all
of
the
above
to
bring
standardization
across
all
languages.
For
example,
the
spec
defines
a
standardized
data
model
for
what
a
trace
is
what
an
exporter
should
do
and
what
is
required
to
create
a
resource.
B
Anyone
implementing
open
telemetry
can
expect
the
behavior
to
be
the
same
across
different
language.
Sdks
they
are
using.
The
caveat
here
is
that,
because
the
project
is
still
evolving,
actual
behavior
may
vary
depending
on
the
level
of
maturity
within
each
specific
language.
B
The
collector
it
is
a
standalone
service
provided
by
open
telemetry.
It
is
a
highly
configurable
system
for
processing
data
that
you
can
use
as
part
of
your
observability
strategy
with
open
telemetry.
B
I
do
want
to
note
that
to
export
telemetry
that's
generated
from
services
to
a
back-end
vendor,
you
can
either
one
use
the
sdk
to
configure
and
export
it
to
send
data
directly
to
your
backend
or
use
the
collector,
which
is
also
great
for
centralizing
configuration
and
performing
additional
data
processing.
B
B
Okay,
I
hope
everyone
is
doing
well
so
far,
I'm
going
to
continue
on
with
talking
about
the
sigs.
So
what
are
the
cigs?
The
community
is
organized
into
multiple
cigs
or
special
interest
groups.
They
exist
to
improve
the
workflow
and
to
more
efficiently
manage
a
community
project.
B
Each
sig
meets
regularly
over
zoom
and,
if
you're
unable
to
attend
any
meeting
meeting
notes
as
well
as
recordings
are
available,
and
there
exists
a
sig
for
just
about
every
component
of
the
project.
There
are
language
sigs,
some
of
which
are
broken
down
into
more
specific
ones.
For
example,
there's
a
sig
for
both
java
sdk
and
instrumentation,
as
well
as
jvm
metrics
dotnet
has
one
for
instrumentation
and
another
one
for
the
sdk.
B
There
are
two
governing
bodies
for
open
telemetry.
The
first
one
is
well.
I
guess
I
know
particular
order.
The
first
one
is
government's
committee.
All
positions
on
this
committee
are
elected
and
its
role
is
to
be
a
live,
responsive
body
that
can
refactor
and
reform
as
necessary
to
adapt
to
a
changing
project
and
community.
B
The
technical
committee
is
responsible
for
all
technical
development
within
the
open,
telemetry
project,
and
I
will
list
a
few
here:
setting
release
dates,
quality
standards
for
releases,
technical
direction,
github
reaper
management
and
etc.
B
So
the
technical
committee
recognizes
that
maintainers
of
specific
languages
or
sub-projects
have
significant
autonomy
over
their
sig
and
implementations.
So
the
committee's
focus
is
on
cross-project
or
disputed
concerns.
The
primary
goal
is
to
see
consensus
to
develop
an
appropriate
technical
solution.
B
What
about
documentation
so
documentation
as
you'll
hear
in
just
a
bit
is
actually
one
of
the
biggest
areas
that
the
community
needs
help
in
the
sig
that
oversees
documentation
is
the
communication
sig.
B
If
you
have
checked
out
the
docs
before
but
haven't
looked
in
a
while,
I
recommend
doing
so
as
there's
already
been
a
lot
of
improvements
to
the
structure
and
docs
themselves
over
the
last
couple
months.
B
I
also
want
to
note
that,
since
each
language
has
its
own
maturity,
level
and
contributors,
you
will
find
that
some
languages
have
more
comprehensive
documentation
than
others.
However,
there
is
currently
work
being
done
by
the
communication
sig
to
standard
site
to
standardize
the
docs,
one
of
which
is
creating
a
getting
started.
Template
and,
of
course,
if
you're
sending
your
open,
telemetry
instrumented
data
to
a
back-end
vendor
those
back-end
vendors
will
also
have
their
own
documentation.
That
might
be
helpful
for
you.
B
B
B
Some
examples
that
an
otep
should
be
used
for
our
additions
to
span
data
new
metric
types,
new
tracer
configuration
options.
B
On
the
other
hand,
they
do
not
need
to
be
used
for
things
like
bug,
fixes,
rephrasing
grammatical,
fixes,
typos,
etc
refactoring,
as
well
as
things
that
only
affect
a
single
language
or
implementation.
B
A
few
of
types
that
are
currently
open
are
support,
wheel,
user
monitoring,
events
in
open
telemetry,
add
sensitive
data
labels
and
add
remote
sampling.
So
just
to
kind
of
give
you
an
idea
of
what
the
what
has
been
proposed.
There
are
guidelines
in
the
github
repo
on
how
to
submit
an
otep.
If
anyone
here
is
interested.
B
B
B
So
there
are
many
options
available
to
you.
Cncf
slack
is
a
great
way
to
interact
with
the
community
and
other
end
users.
You
will
have
to
sign
up
for
an
account
with
slack
if
you
don't
already
have
one
yet
to
join
the
cncf
workspace
once
you
are
in
you
can
search
for
the
general
open,
telemetry
channel
or
if
you're
looking
for
assistance
with
a
specific
component,
just
type
in
hotel
dash
and
a
bunch
of
options
will
pop
up.
B
For
example,
you
have
hotel
dash
python
hotel,
dash
sampling,
ultil
dash
collector
and
people
are
generally
pretty
responsive
from
what
I've
seen
in
there.
There
are
also
vendor-specific
channels
if
you're
having
trouble
with
your
open
telemetry
instrument
data
in
the
back
end
vendor.
You
are
sending
your
data
to,
for
example,
there's
other
new
relic
or
they
might
have
their
own
community
slacks.
So,
for
example,
honeycomb
has
their
own
community
slack
as
well.
B
Alternatively,
you
can
also
go
to
otol-vender
github,
so
I
believe
most
of
you
are
probably
familiar
with
how
to
utilize
github.
I
personally
like
heading
there
to
search
for
issues
to
see
if
anyone
else
has
encountered
the
same
or
similar
issue
that
I'm
facing,
or
to
open
an
issue
if
it
hasn't
been
brought
up
before,
or
also
just
to
get
specific
component
updates.
B
B
The
plan
is
for
it
to
be
a
space
where
discussion
topics
are
generated
and
democratically
selected
by
the
group
at
the
start
of
the
meeting.
At
this
point
in
time,
an
invite
is
required
to
join
the
channel.
Please
reach
out
to
either
rin
mancuso
or
myself.
You
can
find
us
both
in
cncf,
slack
or
linkedin,
and
because
things
are
subject
to
change
and
delays,
keep
an
eye
out
in
slack
or
feel
free
to
reach
out
to
one
of
us
or
anyone
in
the
hotel,
dash
user
dash
research
channel.
B
B
First,
what
areas
need
help
so,
honestly,
everything
could
use
some
help.
There
is
so
much
to
do
within
the
community.
I
I
spoke
with
ted
young,
who
is
a
co-founder
of
open,
telemetry
and
documentation,
as
I
had
mentioned
previously,
is
in
need
of
a
lot
of
love.
So
if
you
want
to
do
non-code
contributions,
that's
a
great
way
to
get
involved
with
the
project.
The
php
sig
also
could
use
a
lot
of
help,
and
he
also
mentioned,
but
specifically
defining
semantic
conventions
and
maintaining
contributed.
B
Okay-
and
why
should
I
contribute
you're,
probably
thinking
so
I
can
sit
here
and
tell
you
why
you
should
contribute
with
like
a
bullet
point
list
or
something,
but
instead
I'm
going
to
share
some
quotes
from
project
contributors.
B
B
So
ted
young,
as
I
mentioned,
he
is
a
co-founder
of
open
telemetry
he's
also
the
director
of
developer
education
at
lightstep.
He
says:
implementors
have
one
view
of
the
universe.
End
users
have
another.
B
B
I
also
talked
to
jurassic
crowling,
who
is
a
maintainer
on
the
open,
telemetry
project
and
works
at
grafana.
He
had
an
interesting
perspective
that
I
really
appreciate
and-
and
I'm
excited
to
share
with
you
all
so
he
said
instead
of
listing
our
reasons
why
people
should
contribute.
He
would
rather
try
to
convince
companies
to
encourage
their
collaborators
to
contribute
on
company
time.
B
B
Sometimes
we
have
data
or
requests
from
actual
customers,
but
it's
not
the
same
thing.
Having
the
opinions
of
a
diverse
user
base
is
essential
for
the
project's
success,
so
that
last
bit
kind
of
ties
in
with
what
the
first
quote
that
I
shared
right.
So
the
quote
continues.
B
But
one
thing
I
see
companies
doing
wrong
is
just
telling
their
folks
to
contribute
without
a
strategy
in
mind,
so
my
advice
is
to
focus
on
the
areas
that
matter
to
the
company
with
a
plan
and
strategic
direction
if
they
can
get
measurable
goals
attached
to
the
company's
own
goal
so
much
the
better.
This
way
their
open
source
contributions
become
relevant
to
the
company.
B
I
also
want
to
add
here
that
he
is
aware
that
open
source
contribution
isn't
for
everyone.
There
are,
of
course,
going
to
be
developers
who
are
not
comfortable
with
having
their
work
being
visible
in
the
open,
and
companies
should
respect
that
as
well.
B
He
is
a
senior
open
source
architect
at
dynatrace,
so
he
says
I
love
working
in
open
source
because
its
global
nature
exposes
me
to
a
very
diverse
set
of
people,
ideas
and
opinions
that
would
otherwise
be
difficult
to
tap
into.
I
really
love
that
by
the
way-
and
he
goes
on
to
say.
I
also
especially
love
the
community
feeling
in
open
telemetry,
where
vendors
and
platforms
who
would
ordinarily
be
considered
competitors
can
work
together
to
improve
the
state
of
the
ecosystem
for
everybody
involved.
B
Here
is
a
quote
from
an
end
user,
who
has
also
contributed
to
the
ruby,
open,
telemetry
project
as
well
as
helps
his
company
adopt
open
telemetry
at
github,
arielle
valentine.
B
B
If
you
have
not
worked
for
a
remote
first
company
before
joining
an
open
source,
software
project
will
help
you
gain
real-world
experience,
which
I
think
is
a
really
great
point
to
add,
especially
for
those
of
you,
as
you
mentioned,
who
hasn't
worked
for
a
remote
first
company
or
just
kind
of
wants
to
stick
their
teeth
into
a
new
and
exciting
project.
B
Here
is
a
quote
from
an
end
user,
who
has
also
contributed
to
the
php
open,
telemetry
project.
He
had
a
few
points
to
make
here.
It
was
a
great
way
to
learn
about
php
stuff
from
experienced
people,
given
that
he
had
little.
B
B
Okay,
I'm
gonna
finish
it
out
with
one
last
one.
I
hope
you
all
are
enjoying
these
quotes.
This
one
is
from
henrik
rexed
and
I
think
it
sums
it
all
up
pretty
well
by
contributing
to
an
open
source
project.
You
will
learn
a
lot
from
amazing
engineers,
be
at
the
forefront
of
innovation,
and
if
the
project
is
a
success,
being
proud
of
all
the
work
done.
B
Okay,
so
maybe
you
are
maybe
I
have
intrigued
you
or
you're
already
interested
in
contributing.
How
can
you
contribute?
How
can
you
do
so?
So
there
are
multiple
ways
to
contribute.
It
really
comes
down
to
what
you're
interested
in,
of
course,
it
has
to
be
sustainable
and
something
that
works
for
you,
but
and
also
how
you
think
you
can
best
help.
B
I
do
want
to
mention
that
the
community
welcomes
both
code
and
on
code
contributions.
Some
examples
of
non-code
contributions
are
documentation,
blog
posts
and,
as
jurassie
from
early
pointed
out,
there
isn't
only
space
for
code
contributions.
Most
projects
would
love
a
more
professional
project
management
as
well.
B
So,
if
you're
interested
in
contributing
to
a
specific
part
of
the
project,
I
would
recommend
that
you
join
the
appropriate
sig.
You
can
also
sign
up
for
mailing
lists
and
also
attend
community
meetings
which
are
available
on
the
google
public
calendar.
They
also
have
other
two
other
public
calendars,
if
you
don't
like
google
calendar,
but
the
link
will
be
at
the
end
of
this
presentation.
B
Another
way
to
contribute
is
simply
by
sharing
your
feedback
and
experiences
about
using
open
telemetry
with
the
community.
I've
listed
two
channels
here:
otol
dash
user
dash
research
wow.
I
will
learn
to
talk
someday,
you
guys,
which
is
public,
and
there
is
also
an
invite-only
channel
that
I
mentioned
earlier
reached
out
to
myself
or
rin
mancuso.
B
I
believe
the
slide
deck
will
be
available
after
this.
In
any
case,
the
recording
will
be
so
if
you
need
to
to
go
back
or
feel
free
to
ask
in
the
channel.
Oh
okay,
perfect
libby
said
yes,
so
the
the
slide
deck
will
be
available
after
this
as
well
and
apparently
I
did
talk
quite
fast,
because
I
see
that
we
have
reached
the
q
a
so.
B
B
B
So
first
one
is
from
florent
florence.
Why
are
logs
behind
in
the
roadmap?
Jack
berg
has
answered.
Oh
thank
you.
So
much
dotnet
and
java
have
stable.
Metrics
releases
logs
are
behind
a
bit
because
open
telemetry
was
the
results
of
the
merging
of
open
traces,
open,
tracing
and
open
senses
which
were
comprised
of
the
trace
of
metric
signals
logged
in
at
new,
and
it
was
natural
to
focus
on
metrics
and
traces.
First,
oh
and
alan
west
says
added
on
to
that.
B
That
said,
donna
and
java
2
have
some
pretty
solid
support
for
logs
with
some
of
their
common
logging
frameworks.
Thank
you
and
okay.
Where
is
the
collector
running
april
back
inside
and
tyler
hellmuth?
Also,
I
just
wanna
mention
that
the
answering
thank
you
all
so
much.
This
is
so
great,
so
tyler
says
the
collector
is
a
standalone
solution.
It
can
be
run
many
different
ways,
but
is
never
part
of
the
app
itself.
B
B
You
can
always
feel
free
to
reach
back
out
to
me
if
you
think
of
anything
after
this,
which
I
know
often
happens
to
me,
and
otherwise
I
guess
I'll
hang
around
for
another
few
minutes
to
see.
If
anyone
has
any
other
questions
or
I
guess
everyone
can.
B
B
Like
anything
to
add
to
what
I
have
covered,
that's
also
very
welcome.
A
All
right:
well,
if
no
one
has
any
other
questions,
we
will
give
everyone
a
few
minutes.
A
Back
and
again,
all
of
this
will
be
posted
on
cncf.io
on
our
youtube
channel
you'll,
be
able
to
link
to
it
through
your
registration
link
and
thank
you
again
reese
so
much
for
your
presentation
and
for
your
time
and
thank
you
all
for
joining
us
for
another
cncf
live
webinar,
we'll
see
you
again
next
week
and
be
looking
soon
for
q3
calendar
openings,
so
everyone
stay
tuned
and
we'll
we'll
see
you
next
time.
Thank
you
again.