►
From YouTube: SIG Instrumentation 20230119
Description
SIG Instrumentation Bi-Weekly Meeting - Jan 19th 2023
A
Hello
and
welcome
to
today's
edition
of
Sig
instrumentation,
it
is
Thursday
January,
19th,
2020,
three
wow
new
year.
New
release
and
I
believe
our
first
topic
on
the
agenda
today
is
kept
planning
for
the
127
release.
B
Sure
we
have
three
caps
I,
think
we
have
two
of
mine
and
one
of
David's
they're
all
going
to
Beta.
So
we
we
should.
We
can
be
probably
pretty
quick
about
this
because
also.
C
Promoting
graduation
do
we
yeah
I
was
gonna
say
we
might
have
a
few
other,
so
the
the
one
that
I
did
on
the
agenda
is
about
given
migration.
Okay
I
will
try
to
get
the
camping
before
cap.
Freeze,
okay,
that
might
be
tight,
and
we
have
I
think
two
other
yeah
when
I
used
to
follow
up
with
Clayton
about
like
the
resource,
metrics
resource
limit
and
request
metrics
from
the
scheduler
that
needs
to
graduate
to
stable.
C
We
want
it
to
make
sure
that
it
was
used
before
great
graduating
it,
but,
like
I've
made
some
migration
so
now
it's
been
used,
so
we
should
be
able
to
make
that
stable.
Now,
I
need
to
check
up
with
Clayton
again,
okay
and
the
other
one
yeah
I
don't
know
the
other
one
would
be
the
configuration
for
the
garden
HD
enforcement
like
when
we
can
opt
out
some
of
the
metrics
if
they
are
unbounded,
so
that
needs
to
graduate
to
better
I.
B
Yeah,
okay,
so
here.
A
I
can
sorry,
I
was
gonna,
do
it
and
then
I
don't
know
how
to
share
things
on
a
Mac,
because
it's
not
showing
me
a
thumbnail,
so
I
was
worried.
I
would
share
the
wrong
thing.
Okay,.
A
Sure
I
just
wanted
to,
let
me
I,
will
give
you
a
link
to
share.
Maybe
I
want
to
make
sure
that
we
just
like
look
at
everything
and
because
we
have
like
a
lot
of
issues
open
I'm,
gonna,
put
it
in
the
edge
and
rather
than
the.
B
Chat
shouldn't
we
go
over
issues
in
our
triage.
A
No,
no,
not
issues
like
the
issues
and
the
enhancements
which
represent
enhancements.
We
have
like
a
login,
so
I
think
it's
worth
like
going
over
them.
B
B
A
B
A
B
B
B
C
The
idea
would
be
to
like
that
would
be
a
way
to
be
able
to
close
the
original
cap
about
the
events
that
is
blocked
by
the
fact
that
we
cannot
migrate
all
the
communities
components
today
to
the
new
API.
So
the
idea
is
to
prepare
a
plan
to
actually
be
able
to
do
that,
because
it's
not
possible
today
and
maybe
after
a
while,
it
should
be
possible.
B
A
C
C
C
A
Oh,
we
can
change
the
graduation
criteria,
I
mean
it's.
A
B
C
The
original
Kip
is
like
nearly
stable,
like
the
feature
is
stable,
but
not
the
cap.
The
cap
isn't
better
still.
Why.
A
B
B
C
B
A
B
B
Okay,
next
is
mine,
extends
stability
classes,
I
have
a
PR
for
this.
I
have
reduced
scope.
B
A
Silly
question
yeah
I
haven't
done
a
like
enhancements
review
now
for
a
year.
I
know
that
the
release
team
has
changed
the
process,
a
bunch.
How
do
we
as
chairs
Mark
caps
for
the
upcoming
release
that,
like
we
won.
B
A
B
B
No,
but
let's
see
look.
A
I
see
there's
one
for
the
cubelet
opentel
tracing,
there's
a
lead
up
to
then
label
on
that,
but
I
don't
see
it
on
the
other
stuff.
A
They're
two
weeks
out
from
like
I.
A
A
Yeah,
it's
weird
that
the
thing
to
remove
it
is
remove
label,
but
this
one
is
just
a
slash
command.
Well,
that's
handy,
okay,
so
we
want
to
do
that
also
for
see.
B
B
B
A
A
Okay,
so
event:
API
migration,
we're
gonna,
opt
in
for
127.
B
Dependent
Health,
slis
I've
updated
the
thing
in
fact
there's
a
PR
which
has
already
completed
this
for
the
beta
stuff.
We
have
contextual
logging.
Is
this
still
going
on
or.
A
A
B
B
B
A
A
B
B
C
We
wanted
to
graduate
let's
release,
but
we
didn't
get
enough
time,
but
most
likely.
B
A
C
Yeah,
that's
what
she
told
me
yeah,
but
right
now
at
least
I
made
the
changes
in
Keepsake
metric.
Like
now,
we
advertise
the
new
metrics
instead
of
the
old
one
from
from
group
State
metric
and
I.
Did
it
also
like
all
artists
punch
who
is
doing
it
in
kubernetes
mix
since
which
is
like
the
project
we
have
for
permutus.
A
So
I
think
I
see
there
was
some
confusion
about
this
yeah
that
one
was
like.
The
cap
was
beta
as
of
I.
Think
121,
because
I.
A
B
Okay
redesign
event
API:
this
is
the
one
that
you're
this
is
done
right.
Should
we
close
this.
B
C
B
B
B
B
C
Yeah,
we'll
go
pretty
quickly
on
it,
so
essentially,
like
I
had
I
was
reviewing
a
PR
that
was
adding
metrics
recently
about
the
time
it
takes
for
I,
think
cubelet
to
update
the
status
of
the
node.
Well,
I
keep
I,
don't
remember
which
components
it
was
a
famous
cubelete
and
I
was
like
well.
C
These
people
have
the
knowledge
about
how
much
time
is
considered
too
long
for
the
updates
and
the
fact
that
they
don't
like
provide
an
alert
out
of
the
metric
that
they
are
adding
is
kind
of
a
loss
for
us
in
general
because,
like
they
have
the
knowledge
about
the
actual
threshold
that
should
be
advertised
and
like
we
are
not
providing
them
a
way
to
actually
like
share
an
alert
with
like
the
community
in
general
and
I
was
thinking
that
maybe
it
could
be
great
for
us
to
look
into
ways
to
enable
contributors
to
add
alerts.
C
C
We're
using
Prometheus
client
but
like
what
I'm
saying
is
like
not
mixing
that
can
be
necessarily
consumed,
but
at
least
like
some
kind
of
documentation
that
can
be
shared
on
how
to
use
particular
metrics
to
produce
salads
I.
Don't
really
care
about
the
format
of
the
alert
in
the
end,
but
more
about
like
the
content
of
it.
At
the
end
of
the
day,
when
you
produce
an
alert,
you
are
actually
using
the
metric
that
is
being
produced
by
kubernetes.
So.
B
B
B
B
Moving
this
SLO
scalability
threshold,
it's
the
official
website
because
it
should
be
on
the
official
website,
and
so
while
we
are
doing
this,
we
can
also
add
the
stuff
that
you
are
talking
about.
Yeah.
That's.
C
B
C
More
when
it's
about
thresholds,
like
particular
thresholds
in
terms
of
yeah,.
B
Yeah
so,
okay,
great,
let
me
let
me
merge
my
PR
first
and
then
we
can
get
to
it.
Call
for
mentors
is
the.
C
Next
topic:
that's
another
topic,
so
I
just
studied
the
document,
yet
we
need
to
share
it,
but
like
with
French,
we
started
looking
into
ways
to
add
a
mentorship
program
inside
of
the
Sig,
and
the
first
step
would
be
to
try
to
find
mentors
in
various
areas
of
the
code
base.
That
would
have
a
bit
of
time
to
actually
onboard
people
and
follow
up
on
them
on
certain
issues.
C
B
B
This
after
you
share
the
doc
yeah
yeah
I
will
do
that
yeah.
So
let's
move
this
to
the
next
time
and
then
you
can
make
the
dock
yeah
sounds
good
and
then
we
can
read
the
doc
and
then
we
can
figure
out
what
people
are
signing
up
for
yep,
because
we
have
five
more
minutes
and
then
Elena
still
has
one
more
issue.
B
A
Sorry
I
didn't
realize
we're
already
on
it
hooray,
so
I
was
still
updating
labels
and
enhancements
I
wanted
to
provide
an
update
on
what's
going
on
with
usage
metrics
collector,
because
we
pushed
out
the
code
and
I
have
been
spending
much
of
the
week,
setting
up
CI
getting
stuff
working.
B
A
So
we
have
code
hooray,
we
have
CI
running,
which
is
mostly
what
I've
been
working
on.
So
maybe
let
me
share
also
our
test
grid,
which
I
am
excited
about
because
I
just
deflaked
all
of
the
tests
last
night.
Let's
see
also
I've,
got
that
on
the
agenda.
A
So
yeah
the
code
is
now
up.
Folks
can
take
a
look
at
it.
We
have
CI
I'm
gonna
make
a
mailing
list
announcement
as
well.
The
one
thing
that
I
was
kind
of
waiting
on
I
was
hoping
to
have
a
kickoff
meeting
for
the
sub
project
like
separate
from
the
regular
Sig
instrumentation
meeting.
So
we
could
just
spend
the
half
hour
focused
on
this
project
and
it'll
be
a
recorded
meeting
not
during
our
regular
slot.
A
So
I
was
just
trying
to
get
a
hold
of
some
of
the
contributors
who
had
previously
expressed
interest
and
get
like
an
idea
of
what
time
works
for
them
before
I
schedule,
something
and
announce
it.
So
I've
been
waiting
to
hear
back
from
Katrina
and
Han
I
know.
You
said
some
folks
at
Google
were
interested
as
well.
Yeah.
A
I'm
thinking
of
probably
like
either
next
week
or
the
week
after,
between
10
to
11
Pacific,
do
you
think
that'll
work.
A
Okay,
yeah
I
wanted
to
make
sure
it
wasn't
too
late
for
like
folks
that
might
be
in
either
East
Coast
or
Europe.
I
am
on
the
westest
coast,
so
but
yeah
code
is
here
and
oh
the
other
thing
that
I'm
working
on
now
it's
a
lot
of
like
you
know,
the
Machinery
behind
like
getting
the
repost
set
up.
A
I
am
not
sure
how
to
publish
Docker
images
to
I
know.
Our
new
registry
is
registry.case.io.
I
couldn't
find
any
documentation.
A
C
Know
it's
better
than
before,
like
before
we
are
keeping
a
googler
one
specific
googler
to
create
an
actual
Google
group
for
this
project
like
it
was
so
messy,
but
nowadays,
like
it's,
automating
I
will
share
that
link
with
you
and.
A
A
So
yeah,
if
anybody
has
any
questions,
I'd
be
super
happy,
I,
think
Phil,
Whit,
Rock
who's
been
most
actively
working
on
the
code
he's
out
of
the
office
today.
Otherwise
I
would
have
asked
for
him
to
be
here,
but
really
glad
that
you
know
this
is
kind
of
chugging
along
definitely
looking
for
new
contributors
and
interest,
so
I
will
schedule
a
meeting.
A
I
just
need
to
kind
of
get
an
idea
of
what's
a
good
time
for
people,
so
I,
don't
accidentally
schedule
a
meeting
that
nobody
can
attend
and
I'd
love
to
talk
more
about
it.
There
awesome
that's
all
from
that.
B
B
B
Yeah
also
just
just
a
reminder:
cat
freeze
is
coming
up
on
the
10th
of
February.
So
if
you
guys
have
any
ideas
for
how
to
improve
instrumentation
in
kubernetes,
the
10th
of
February
is
the
deadline
for
getting
your
cabin.