►
From YouTube: SIG Instrumentation 20200917
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
Welcome
everyone
to
today's
edition
of
the
sig
instrumentation
regular
bi-weekly
meeting.
It
is
thursday
september
17th
and
let
me
just
get
a
copy
of
the
agenda
which
I
will
paste
in
the
chat.
If
I
can
find
it
thanks
everybody
for
joining
us
for
those
who
are
unaware
or
for
those
who
will
be
watching
the
recording.
We
now
have
a
new
passcode
as
part
of
the
zoom
kubernetes
policies,
so
everybody
is
using
a
passcode
of
five
sevens.
A
That
is
seven
seven,
seven,
seven
seven,
our
invites
have
all
been
updated
and
links
and
whatnot.
But
if
you
have
trouble,
that
is
probably
why
first
item
on
the
agenda
today,
I
had
something
on
here
about
talking
about
kept
targeted
for
120..
A
I
don't
know
if
we
want
to
talk
about
other
things
before
that,
because
that
might
be
kind
of
long,
and
I
don't
want
that
to
take
up
the
whole
meeting
but
we're
in
a
new
release
cycle.
We
need
to
know
what
caps
we're
planning
on
doing
or
con
for
this
release
cycle.
So.
B
I'm
not
sure
we
necessarily
need
to
discuss
all
of
them
here.
Maybe
I
I
think
I
saw
david.
You
were
planning
on
working
on
some
things.
Could
you
make
sure
to
re-ping
people?
If
you
need
another
review
on
anything,
I
I
wasn't
sure
what
state
those
were
in
yeah.
Maybe.
D
Now
I
need
to
reach
out
to
daniel
again
and
get
him
to
look
at
the
tracing
cup,
I'm
actually
hoping
to
put
together
a
little
mini
demo
for
them.
So
I've
been
working
on
that
a
little
bit,
yeah
I'll,
poke
them
and
make
sure
that
moves
forward.
A
A
Got
like
seven
caps
on
the
backlog,
I
put
a
link
in
the
the
agenda.
A
I
would
also
throw
it
in
the
chat
here
and,
like
I
think,
basically,
all
of
them
other
than
maybe
tracing
I
have
like
looked
at
recently,
so
I
mean
some
of
them
are
definitely
like
not
ready
to
go
ahead
like
there
was
at
least
one
that
was
just
not
complete
the
last
time
I
reviewed
it,
but
I'm
curious
like
because
you
know
the
the
release
team
is
going
to
start
chasing
us
down
in
terms
of
what
we
want
to
include
in
the
upcoming
release,
especially
given
that
this
release
is
supposed
to
be
like
focused
on
stability
more
so
than
usual,
because
there
were
a
lot
of
test
problems
with
the
last
release.
B
I
would
say:
let's
go
ahead
with
the
other
agenda
items
and
then
take
whatever
time
we
have
left
to
iterate
over
these.
A
Okay,
great,
let's
do
that.
I
had
a
thing
on
here
to
follow
up
on
the
end-to-end
test,
flakiness
and
the
state
of
the
blogging
add-ons.
Some
folks
have
been
assigned
things
there.
Do
you
have
any
report
back
on
that.
D
D
But
the
problem
was
that
the
cubelet
was
the
master.
Cubelet
was
being
slow
in
creating
the
mirror
pods.
So
even
though
the
cluster
was
fully
functional
and
up
and
running
and
those
containers
were
running,
we
weren't
able
to
find
their
pod
objects
because
the
mirror
pod
hadn't
been
created.
Yet
so
I
just
added
in
a
retry
mirror:
pods
should
be
registered
fairly
quickly.
D
Also,
it
seemed
to
be
because
our
test
was
being
run
at
the
very
beginning
of
the
test
suite.
So
we
were
the
first
ones
to
try
and
test
our
functionality,
and
so
we
hit
that
race
condition,
but
it
hasn't
flaked
in
the
past
five
days
since
the
fix
was
merged.
So
I
closed
the
issue.
A
That's
great
and
then
I
think
there
was
at
least
one
assigned
to
merrick.
Do
you
have
any
updates
on
that
one
like
stackdriver
stuff,
I
think.
E
E
A
Okay
makes
sense
great,
and
then
I
think
there
was
one
more
and
I'm
worried
that
we
assigned
it
to
han
and
han
is
like
not
in
right
now,
because
he's
out
on
paternity
leave.
Let
me
double
check
that
one
yeah.
A
B
A
I
pulled
up
the
issue.
The
issue
says
it's
assigned
to
han,
so
the
test
flake.
A
B
I
mean
you
can
assign
it
to
me
for
now.
If
I
don't
find
enough
time
for
it,
then.
B
A
A
Sorry,
it
is
hard
to
try
to
run
the
agenda
and
also
take
notes
at
the
same
time
if
people
want
to
go
ahead
and
like
throw
notes
in
the
the
one
that
I
just
pasted
in
there
frederick,
that's
the
one
I'm
going
to
reassign
to
you
and
then
you,
if
you
want
to
res
or
if
you
want
to
put
notes
on
the
one
that
you've
worked
on,
that
would
be
great
lily.
A
Next
agenda
item
is
what's
going
on
with
kate's
prometheus
adapter
frederick.
I
reminded
him
of
this
and
we
totally
filed
an
issue
to
migrate
it.
So
I
don't
know
where
that's
at
yet,
but
it's
happening.
C
Yeah
serge
is
now
working
on
it,
sergius
he's
working
on
it
to
migrate
and
to
finish
the
migration.
So
far,
it's
only
him
and
the
owners
file
as
the
project
was
inactive.
So
he
added
me
temporarily,
as
I
have
the
most
knowledge,
at
least
in
our
team.
But
if
anyone
else
is
interested,
it
would
be
great
to
get
more
contributions
on
it,
but
we're
definitely
looking
into
investing
more
time
into
it,
but
yeah.
A
C
Yeah
we
added
him
as
well
he's
not
interested
from
last
from
what
I
understood
too
fully,
but
he
is
definitely
added
in
the
oh,
I'm
gonna
mispronounce
this
in
the
past
owners.
What's
it
called.
A
C
You,
yes,
yes,
I
always
read
it,
but
never
pronounce
it
so
he's
added
on
there
definitely.
A
C
Yes,
pre-release,
though,
so
we
finally
managed
to
merge
all
the
braking
changes
and
it
has
a
lot
of
braking
changes
so
make
sure
to
have
a
look
at
the
change
log.
It
should
be
complete
enough,
but
if
there's
anything
missing,
let
us
know
either
on
slack
or
on
github,
but
it
would
be
great
if
people
can
try
it
out
and
yeah
just
report
back
if
there's
anything
broken
or
wrong
or
just
in
general
or
good
really.
So,
if
it
works,
that's
a
good
indicator
as
well.
C
A
Okay,
let's
circle
back
on
caps,
maybe
I
would
be
helpful
if
I
share
my
screen
with,
like
all
of
the
backlog
of
the
cap
issues.
A
A
Okay,
can
everyone
see
my
screen?
Is
it
big
enough?
A
Okay?
So
this
is
kind
of
why
I
wanted
to
go
over
this
we've
got,
I
think,
like
seven
open
issues
for
caps
right
now
and
a
bunch
of
them
are
like
tracked
yes
from
like
they're
kind
of
fallen
over
to
this
milestone,
but
it's
not
clear
if
they're,
actually
in
progress
or
not,
and
so
like.
I
just
want
to
get
sort
of
a
better
idea
of
where
all
of
these
are
at
what
we
actually
want
to
target
for
120.
A
All
of
these
five
have
the
actual
120
milestone
on
them.
These
ones
don't,
but
there
seems
to
be
a
lot
of
interest
in
getting
them
done
so.
B
At
yeah,
which.
A
A
Yes,
yeah,
I
guess
let's
come
up
to
date
on
this
one.
F
A
Yes,
oh
now
it
has
119
too
remove
milestone.
I
don't
know
how
this
works.
I
will
just
let
somebody
else
worry
about
that.
Okay,
so
david,
what's
going
on
with
tracing.
D
I
need
to
ping
daniel
again.
I
think
it
would
help
if
I
implemented
part
of
it
just
to
show
them
that
it's
the
code
changes
are
pretty
minimal.
D
A
It
looks
like
for
this
one:
we've
got,
we
need
to
fix
up
the
cap
and
make
sure
that
there
are
like
test
plans
and
whatnot
before
the
enhancement
freeze.
So.
A
Great
structured
logging,
the
ongoing
adventure.
C
A
For
alpha,
it's
got
lots
of
nice
check
boxes
here,
which
is
great,
so
is
the
plan
to
put
this
in
beta
for
120.
A
Okay,
yeah,
so
we're
not
sure
if
this
one
we're
planning
on
getting
this
done
before
the
enhancement
phase.
G
Yeah,
I
would
definitely
need
some
help
with
with
like
yeah
scoping
the
work,
and
maybe
someone
like
I
could
have
implementation,
but
I
could
definitely
not
don't
have
time
to
fully
organize
it
like.
In
previously,
we
had
over,
like
10
or
15
contributors
with
a
lot
of
new
contributors,
and
that
was
really
like.
G
A
Okay,
that
sounds
good
to
me.
I
can
maybe
help
with
the
scoping,
but
probably
not
the
implementation.
A
A
New
unique
logging
metadata
into
key
kubernetes
logs.
What
is
that
all
about?
I
don't
think
I've
seen
this
one.
A
D
A
I
see
yeah
I
well
I
mean
we've
still
got
like
what
a
few
weeks
a
couple
of
weeks
before
the
enhancements
freeze,
so
it's
possible
that
this
will
get
into
a
better
state
before
then.
A
I
don't
know
what
the
owner
is
planning
on
this
one.
I
think
I
gave
that
feedback
like
yeah
a
week
ago
and
there
haven't
been
any
updates
since
then,
and
the
release
teams
also
said
the
same
thing.
So
you
know
if
folks
want
to
go
and
do
all
the
work
like
I'm
not
going
to
stop
them
from
doing
the
work.
I'd
be
happy
to
see
it
in
120,
but
you
know
it's
it's
either
going
to
make
it
or
it's
not
so.
D
A
Okay,
I'm
gonna
suggest
like
assuming
that
the
cap
is
actually
completed
and
approved
we'll
target
120,
otherwise
we're
gonna
go
for
one.
A
A
Okay,
so
I
guess
we've
got
three
more
to
take
a
look
at
here.
I
reviewed
this
one
recently.
A
I'm
going
to
wait
for
clayton
to
respond
on
this
one
because
I
think
there's
a
lot
of
feedback.
That's
happened
on
that
the
pr
for
the
cap.
I
think
it
looks
relatively
good,
but
it's
just
a
matter
of
getting
everything
together
to
do
that
implementation.
So
I'm
gonna
leave
that
with
clayton.
B
A
Yeah,
like
it
was
just
missing
like
it
was
like
small
sort
of
nitpicky
things
I
think
so,
like
you
know,
it
just
needs
to
go
through
the
review
process
and.
A
A
F
Yeah
so
so
I
guess
I
can
say
a
few
words
about
those
two.
So
there
was
no
no
like
significant
progress
on
both
of
those
recently,
but
those
are
definitely
something
that
that
we
would
like
to.
A
Okay,
so
I
know
that
this
one,
I
think,
has
already
all
been
merged
and
whatnot,
so
I
can
set
this
one:
the
milestone
to
120.
A
But
for
the
for
this
one,
I
took
a
look
at
this,
so
this
cap
is
currently
in
progress.
It
has
not
been
merged
or
approved.
Yet
I
think
this
one
there
was
still
like
it
needs
more
reviews
and
potentially
needs.
Like
some
some
updates
said
yeah.
It
looks
like
folks
have
taken
a
look
at
this
recently
so
other
than
me.
A
I
don't
know
if
all
of
this
has
been
addressed
yet,
but
I
would
say
that
this
one
potentially
could
target
120,
but
I
think
the
cap
needs
to
be
like
merged
as
like
provisional
before
we
can
do.
A
A
Okay,
then
we
got
through
them
all
and
we've
got
five
minutes
left
so
see
that
wasn't
so
painful.
I'll
just
add
this
comment
to
this.
A
E
A
I
hope
nobody
has
any
like
secret
caps
that
they
want
to
like
sneak
in.
You
know
like
last
second
catching
us
all
by
surprise.
I
mean
if
you
have
a
secret
cap,
I
mean
that's
cool,
I
like
secrets,
but
I
will
not
be
able
to
approve
it
so.
A
Lots
of
headshaking
no
does
anyone
want
to
say
hi.
A
Well,
given
that
we
have
no
other
business,
we've
done
our
kep
review.
It's
great
to
see
everybody
I'm
going
to
stop
the
recording
and
thanks
for
joining
us
today,
I'll
see
some
of
you
hopefully
in
the
triage
meeting
next
week,
and
if
not
the
sig
meeting
in
two
weeks
thanks,
everyone.