►
From YouTube: 2021-04-07 meeting
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).
B
Good
morning
everyone
give
people
a
couple
minutes
to
file
in
here.
Elita
and
jana
were
unable
to
make
it
today.
So
they've
asked
me
to
kind
of
help:
m.c
no
wait!
No
jana
is
appearing
today.
Okay,
hello,.
B
Okay,
let
me
go
ahead
and
get
started.
You
know
the
the
first
issue
on
the
agenda
here
is
one
that
alelita
had
added
just
a
reminder
that
there
are
a
set
of
collector
bugs
or
issues
that
are
related
to
prometheus,
there's
a
link
to
an
issue
filter
at
the
collector
project.
If
anybody
has
a
bandwidth
or
understanding
of
these
issues
and
would
like
to
contribute,
that's
a
great
place
to
start
any
help
would
be
appreciated.
There.
B
This
is
going
to
form
the
basis
for
some
work
that
will
be
going
into
both
the
open
telemetry
operator
and
the
collector
in
order
to
enable
that
sort
of
horizontal
scaling
of
prometheus
scrape
targets
in
the
collector,
and
so
if
anyone
has
a
desire
to
review
that
and
comment
on
things
that
they
see
there
that
are
good
or
bad
or
could
be
improved.
That
would
be
appreciated
as
well,
and
then
work
will
start
flowing
from
there
from
that
proof
of
concept
into
the
collector
and
operator
code
bases
in
the
near
future.
C
Oh
it's,
it
was
just
me
declaring
that
I'll
be
adding
support
for
the
summary
type
end
to
end
so
from
the
receiver
to
the
two
different
exporters.
Yeah.
That's
just
it.
B
Okay,
I
think
that'll
be
it's
one
of
the
last
types
that
that
needs
to
be
supported
in
that
pipeline.
Is
that
correct?
B
We
do
counter
gauge
histogram
so
summary
and
then
dealing
with
up
metric,
I
think,
are
the
the
two
outstanding
ones:
cool
yeah.
C
So
a
metric
and
summary
are
left
and
yeah
thanks
to
brian
brazil.
I
don't
know
if
he's
in
this
call,
I
read
through
lots
of
his
blog
posts
and
I
used
one
of
his.
I
use
drop
his
drop
with
a
tutorial
from
something
else
to
help
me
get
there.
So.
A
C
B
Okay,
so
the
the
next
item
is
related
to
that
operator.
Collector
scaling
work
that
I
had
mentioned
as
part
of
the
discussions
of
what
we
wanted
that
operator
to
do
a
while
back.
It
was
discussion
of
a
desire
to
allow
users
to
utilize
the
the
same
configuration
crds
that
they
would
with
the
prometheus
operator.
The
the
service
monitor
pod,
monitor,
et
cetera,
and
while
looking
into
that,
I
found
that
the
code
that
takes
those
resources
and
generates
prometheus
configurations
out
of
them
is
not
exported
out
of
the
prometheus
operator.
B
It's
it's
internal
to
that
controller
package.
So
I
was
wondering
if
there's
anyone
from
the
operator
or
who
has
worked
on
the
operator,
who
would
know
whether
that's
something
that
would
be
susceptible
to
exposing
as
a
library
for
use
by
other
systems
that
want
to
take
a
service,
monitor
and
generate
a
script
config
from.
D
It,
I
don't
think
frederick
is
here
no
yeah.
B
D
E
I
think
that's
advice
initially,
that's
about
it.
B
Okay,
if
I
were
to
reach
out
with
the
kubernetes
slack
and
the
prometheus
operator,
dev
channels,
there
be
the
appropriate
place
to
ask
questions
about
this.
D
Prometheus
prometheus
def
do
we
have
an
operator.
F
We
have
an
operator
channel
in
cncf
slack,
you
can
check
it
out.
Was
there
one
of
the
cstf
slack
as
well,
so
the
the
kubernetes.
F
D
F
B
A
C
End-To-End
yeah
yeah,
so
it's
it's
just
super.
It's
supported.
Providing
support
for
that
type.
There's
an
open
bug!
There's
an
open
bug!
Wasn't
you
who
filed
it.
A
A
C
Okay,
sure
yeah
I'll,
find
it
and
put
in
the
dog.
Does
that.
E
A
Oh,
that's!
Fine.
If
you
have
a
bug,
I
can
just
take
a
look
at
it.
Just
put
it
there.
Thank
you
thank.
E
C
B
Okay,
I
think
if
we've
reached
the
the
end
of
the
agenda
and
there's
nothing
further
discussed,
I
don't
want
to
keep
everybody
hanging
around
when
there's
other
work,
we
can
be
doing
so,
give
a
quick
moment
for
anybody
to
speak
up
with
any
additional
things,
and
then
I
think
we
can
take
our
leave.