►
From YouTube: SIG Instrumentation 20210429
Description
SIG Instrumentation Bi-Weekly meeting, Apr 29th 2021
A
A
A
The
release
cycle
is
a
little
bit
changed
this
time
around,
because
we're
moving
to
a
15
release.
Sorry
15
week
release
cycle
this
year,
which
means
three
releases
and
we
are
going
to
move
enhancements
freeze
a
little
bit
earlier
and
so
we're
gonna
have
a
longer
time
to
write
code
yay,
so
enhancements
freeze
is
may
13th,
so
we'll
spend
a
little
bit
of
time
going
over
enhancements
today
and
code.
Freeze
is
thursday
july
8th
test.
A
A
I
think
I
put
it
on
the
agenda,
but
I
don't
know
if
I'm
the
right
person
to
talk
about
this.
I
will
summarize
very
briefly,
which
is
that
lumiere
filed
an
issue
against
k,
log
flagging
sig
instrumentation,
saying
that
it
was
initially
owned
by
sig
arch.
It
was
moved
over
to
sig
instrumentation,
but
the
owner's
files
in
k
log
do
not
reflect
the
sig
instrumentation
ownership,
which
I
don't
necessarily
agree
with,
because
dimms
is
a
member
of
sig
instrumentation
in
part
because
of
his
involvement
in
k
log.
A
B
E
A
Oh
yeah,
we've
got
actually
it's
it's
a
very
fair
point,
because
there
are
some
very
outdated
approvers
on
k-log
like
some
folks
who
haven't
contributed
in
quite
a
while.
So
we
might
want
to
clean
that
up.
I
don't
know
that
we
necessarily
went
through
k
log
as
part
of
our
annual
report.
So
I
guess
that's
a
to
do
for
us
who
should
be
responsible
for
that.
B
A
F
C
A
B
A
A
A
A
A
A
So
that's
no
problem,
so
yeah
we've
got,
we've
got
a
few
net
news
and
then
I
think,
while
working
through
blogging,
we'll
probably
be
coordinating
what
we're
doing
on
structured
logging.
I
think
we
still
are
supposed
to
own
the
cap
until,
like
you
know,
they're
fully
chartered
and
we
can
transfer
it
over
to
them.
So
maybe,
let's
talk
about
that
one
last.
Is
there
anybody
here
to
talk
about
this
custom,
metrics
router.
C
A
Oh
no,
no
so
so
let
me
tell
you
about
the
new
process,
because
every
release
there's
always
a
new
process.
Luckily,
this
releases
new
process
is
actually
probably
easier
than
last
releases
because
there
are
less
emails
involved.
There's
now
a
spreadsheet
that
we
put
all
of
our
hand
enhancements
in
and
in
fact
maybe
I
can
go
find
the
spreadsheet.
A
C
A
They
just
might
be
confused
in
terms
of
the
the
problem.
Is
we
don't
really
have
I've
encountered
this
with
another
thing,
for
I
got
flagged
to
do
a
prr
review
for
cluster
life
cycle.
People
think
that,
like
anything,
that
needs
a
design
dock
has
to
go
through
the
cap
process.
But
if
it
doesn't
touch
anything
in
tree,
then
I
don't
think
that's
really
the
case.
So
if
that
one's
gonna
be
out
of
tree,
then
to
do,
I
guess
would
see
if
they
can
add
a
design
dock.
C
B
A
A
C
A
A
A
E
A
Great,
I
can
definitely
do
that,
and
I
think
that
sounds
like
a
totally
reasonable
plan.
I
mean
you,
don't
have
to
have
a
cap
to
continue
working
on
things
that
have
already
been
accepted
and
we
just
need
a
plan
to
actually
get
it
graduated.
So
I
guess
that
leaves
us
with
this
cap,
which
I
think
is
a
stretch
and
what
we're
gonna
do
with
structured
blogging
for
this
release
david.
Have
there
been
any
updates
on
this
guy.
F
A
Should
I
optimistically
add
this
one
with
the
hope
that,
like
you
know,
there's
gonna
be
excuse
me
issues
that
will
need
to
be
resolved,
but
should
I
add
this
just
with
the
hope
that
it'll
be
yeah
looks
like
four
days
ago.
Should
I
add
this
one
with
the
hope
that
we'll
get
a
chance
to
approve
it
and
if
not,
it
just
slips.
G
A
G
A
G
A
A
D
A
A
A
A
A
A
H
So
if
we
to
like
do
a
small
summary
we're
looking
into
adding
open
telemetry
tracing
into
etcd,
and
if
that
doesn't
land
by
mid-may,
then
it
will
land
in
3
6
at
city
which
will
be
in
a
year
or
so.
So
I
think
that
if
there's
any
either
like,
if
anyone
wants
to
really
do
that,
maybe
we
can
join
forces
and
try
to
get
that
in
before
code
freezing
that
city.
C
H
So
the
release
that
the
tracing
stuff
would
land
in
would
be
three
five.
The
current
one
is
three
four
and
that
there
is
code
freeze
for
that
mid-may
end
of
may,
with
the
release
being
cut
in
august
autumn
time,
we're
trying
to
work
on
getting
releases
more
frequently,
so
that
should
be
coming
up
soon,
hopefully,
but
yeah
it's
more
like
do.
Do
we
think
we
can
wait
as
kubernetes
for
another
year
or
so,
or
would
we
like
to
speed
things
up.
A
H
Yes,
that's
my
thinking
as
well
like
we
are
trying
to
work
on
issues
to
get
our
releases
out
like
that
city
releases
out
more
frequently
and
there's
a
bunch
of
open
issues
before
that
city
gets
to
there,
but
I
think
that
having
tracing
and
it
would
then
land
right
when
api
server
tracing
should
be
beta.
I
guess
so
that
would
align
nicely
with
the
three
five
release
as
it
takes
a
while
before
kubernetes
adopts
but
yeah.
E
A
Do
it
that's
that's
kind
of
where
I'm
at
for
people
who
are
not
familiar
with
this
sort
of
delay
in
release
uptake
just
this
is
based
on
some
data
that
I've
seen.
I
think
there
were
surveys
that
showed
that
currently,
the
widest
used
release
of
kubernetes
is
116.,
so
we
are
releasing
122
and
the
biggest
version
is
116.,
which
is
quite
old.
A
F
H
F
H
H
Yes,
yes,
yes,
it
does.
That
was
our
like.
That
was
the
discussion
I
had
with
sam
that
maybe
we
could
have
it
under
a
flag
and
not
enabled
by
default
at
all,
at
least
for
one
release
for
the
three
five.
If
we
managed
to
get
it
in
that
one
and
then
that
way,
we
know
that,
like
any
possible
resource
problems,
we
might
have
with
open
telemetry
or
things
like
that.