►
From YouTube: SIG Instrumentation 20210304
Description
SIG Instrumentation Bi-weekly meeting March 4th 2021
A
A
B
B
B
So
as
far
as
what
has
been
done,
we
actually
do
have
a
bunch
of
these
that
have
been
merged,
which
is
great,
and
we
have
a
bunch
of
these
that
have
lg
tms
that
just
need
an
approver.
So
I'll
go
pester.
Someone
about
that.
We
also
have
a
lot
of
these
that
are
currently
waiting
on
the
author
to
fix
them
and
there's
two
things
that
are
not
specifically
like
a
structured
log
change
to
like
note
here.
B
So
one
is
adding
the
tool
for
verification
to
ci
and
the
other
is
fixing
the
panic,
because
currently
the
flag
doesn't
work
so
yeah.
Apparently
we
accidentally
them
earlier
in
the
release,
and
so
now
we
need
to
fix
them.
So
that's
kind
of
the
status
of
this
and
david.
I
don't
know
if
you
still
have
node
approver
powers,
but
for
anything
that
you
do,
I
might
pester
you
to
go
and
start
approving
things.
D
B
F
E
C
B
C
B
C
B
B
E
E
C
C
B
E
E
We
can
like
this
was
put
into
beta
because
it
was
pointed
out
as
a
big
problem
in
alpha,
and
secondly,
if
we
like,
we
need
time
to
like
would
be
best
that
when
we
ga
we
have
already
deprecated
the
fla
the
flags,
that's
that
or
like
deprecation
may
be
removed.
The
flags
that
are
will
not
be
supported
in
future,
so.
B
B
E
E
I'm
I'm
worried
that
the
distract
like
json
logging
will
not
be
usable,
so
we
could
like
here's
the
problem.
The
cap
touches
two
things
like
migration
and
json.
So
without
this
json
is
useless
technically,
because
you
cannot
use
anything
aside,
the
verbosity,
so
you
cannot
set
verbosity
per
module.
You
cannot
send
it
to
file
if
you
use
it.
B
B
C
A
E
B
B
But
we,
I
don't
think
we
can
put
like
there-
should
not
be
much
more
here
like
we
just
need
to
go
through
the
rest
of
this
list,
so
we
have
a
an
issue
for
that.
We
have
the
thing
for
that
which
is
the
cubelet.
This
is
a
to
do
that
I
will
try
to
either
take
or
assign
someone
to
and
then
what
so
mary.
I
think
you
added
this
about
the
end
to
end
test
scenario.
E
B
A
B
A
Mean
like
these
things
kind
of
have
to
happen
when
a
project
is
big
right,
so
I
guess
we'll
need
to
just
figure
our
way
around
it
and
the
people
who
were
approvers
in
there
before
aren't
gone
right.
So
I
have
a.
I
have
a
good
relationship
with
forget
how
to
pronounce
this
name,
but
one
of
their
approvers,
no,
the
other
one.
Yes,
I
forget
one
of
the
two
people
who
were
approvers
for
the
v2.
B
I
think
it's
okay
for
us
to
own
this
stuff.
As
long
as
we
have
approver
access-
and
we
like-
I
don't
want
this
to
just
get
dumped
on
us
because
I
don't
think
most
of
us
have
any
familiarity
with
the
code
base
and
there
are
existing
people
who
did
own
it.
And
so
I
don't
want
to
like
volunteer
and
say,
like
yeah,
of
course,
we'll
own
your
code
and
they
all
run
away.
C
A
Yeah,
so
the
the
exciting,
exciting
thing
about
this
tag
is
also.
This
is
the
first
time
that
we'll
be
using
automated
performance
tests
on
kubesave
metrics
lily
has
been
working
really
hard
on
automating
these
with
six
scalability.
So
I
mean
said
that
she's
not
here,
but
shout
out,
because
that
was
had
been
on
our
list
for
probably
years.
A
E
A
C
B
C
G
G
The
the
main
strength
is
just
where
helpers
cracked
correct
the
issues
of
running
the
scheduler
performance
test,
so
the
first
one
is
that
we
use
this
to
want
to
support
the
histogram
metrics,
but
in
the
upstream
we
change
that
some
metrics
from
historical
histogram
vector,
but
the
supporting
code
is
not
updated
properly,
so
this
first
first
one
is
for
that
and
the
first
one
unconditionally
returns
the
first
index
his
screen,
which
is
not
incorrect,
which
is
not
correct.
The
second
one
is
that.
G
G
C
A
F
C
A
D
D
B
D
That
it
looks
like
etcd
was
able
to
resolve
some
of
the
issues
they
were
having
with
their
with
bumping
their
grpc
version.
So
I
think
they
got
it
to
like
it's.
Not
it's
not
all
the
way
solved.
So
I
I
it
might
be
enough
that
I
can
actually
implement
this,
but
I
would
have
to
use
a
slightly
older
version
of
open
telemetry,
which
is
unfortunate
because
a
lot
of
changes
have
come
in
since
then,
but
it
for
alpha
quality.
I
think
it'll
be
all
right,
but
yeah.
A
B
Okay,
so
I've
added
a
comment
just
so.
The
release
team
is
not
in
the
dark
on
what's
going
on
there
that
covers
tracing,
it
sounds
like
you
know,
we
might
slip
another
release,
but
it's
in
better
shape
than
it's
been,
which
is
good.
You
know
not
a
lot
remaining
metric
stability.
We
know
what
we
need
to
do
structured
logging.
We
know
what
we
need
to
do.
I
picked
clayton
about
this
one
there
to
graduate
to
beta
it's
just
a
matter
of
basically
updating
the
docs
we
don't
currently
have
like.
B
We
got
rid
of
the
phase
beta
on
metrics,
like
we
only
have
alpha
and
stable,
so
we
don't
need
to
like
bump
that
or
anything
like
that.
So
it's
really
just
a
dock
change
for
this
one
and
like
more
benchmarking,
I
guess
this
one
is
being
tracked
by
sig
security,
and
I
guess
the
only
one
we
got
left
is
metric.
Cardinality
enforcement.
I
know
there's
a
pr
up
for
that
han.
Is
that
making
good
time.