►
From YouTube: Octant Community Meeting - March 11, 2020
Description
March 11, 2020
Agenda
Moved logger to pkg. Octant does not require importing internal to build plugins
Revisting client-go version #766
Added remaining components to unmarshal
Open Q&A - add your questions here!
Does Octant have plans to support a graph component? #765
A
To
the
cloud
alright,
hello,
everybody
welcome
to
March
11th
2020
octant
community
meeting
I
I've
gone
this
hole
since
they'll,
basically,
since
the
last
community
meeting,
so
we're
gonna
whip
up
an
agenda
here
and
put
some
items
in
it
as
we
go
along,
so
nothing
set
right
now.
So
if
you
have
questions
that
would
be
good
because
then
I
could
stop
stalling.
A
We
we
got
some
so
I
was
I
was
reviewing
PRS
that
were
done
over
this
last
week
and
there's
some
good
changes
that
got
put
into
place.
I
saw
that
the
the
the
logger
interface
that
Jordan
was
was
moving
over
to
package
that
got
moved
over
and
merged
in,
so
that
that
should
make
things
a
little
bit
easier
for
plugins.
A
The
my
changes
for
the
ammo
editor
to
convert
it
to
Monaco
were
merged,
while
I
was
gone,
and
then
there
was
a
follow
up
PR
to
address
some
of
the
issues
that
Sam
found
during
reveal.
Brian
got
those
in
place
and
we
got
that
all
merged
in
so
and
the
current
master
is
the
ya
mole
viewer,
which
is
still
read-only,
is
now
using
the
Monaco
as
the
backend.
There
was
a
good
group
effort
from
Elan
helped
on
that
say
and
helped
on
that.
Brian
helped
on
that.
A
A
A
This
is
it's
related
to
our
dependencies,
but
what
it
does
is
it's
essentially
causes
of
conflict
when
there
are
other
other
other
imports
that
you
want
to
use
to
build
out
a
plug-in
that
also
use
client
go
in
our
pit
and
want
a
specific
version
or
want.
The
latest
version
are
replaced.
Directive
is
overriding
that
and
then
causes
a
ambiguous
import,
so
this
is
related
to
an
issue
that
was
open
in
a
while
back
yeah.
This
is
related
to
this
k8
api
compatibility
issue
that
we've
had
outstanding
for
a
while.
A
We
are
the
likely
solution
would
be
in
that,
as
as
we
start
to
get
closer
to
a
1.0
for
that,
which
really
is
only
important
for
the
plug-in
API
will
pin
ourselves
to
and
say
we
support
this
range
of
kubernetes
versions
officially,
and
then
master
obviously
evolved
on
that.
But
the
idea
will
be
a
1:1
back
one
forward
type
support,
so
we
will
we
in
that
example,
we
would
be
supporting
you
know
one
dot.
A
If
the
current
release
was
like
1.14,
we
would
want
we'd
be
targeting
to
try
and
make
sure
we're
supporting
1.13,
1.14
and
whatnot
50
right
now.
There
is
no
official
support
around
what
API
versions
we
support,
but
that
is
due
to
the
fact
that
we're
not
at
a
stage
of
1.0
yet
or
getting
even
really
like,
where
we're
working
towards
it,
but
we're
not
there
yet.
So
we
will
definitely
be
figuring
out
those
details
as
we
before
we
do
a
1.0,
but
that's
where
that's
where
that
stands.
A
Oh
and
yeah
that
we
finished
up
the
components
to
unmarshal,
so
the
new
editor
component
can
be
unmarshal
so
that
can
be
used
by
plugins
as
well,
and
the
remaining
outstanding
components
were
added
to
the
unmarshal
list.
So
everything
that
we
that
we
currently
support
or
everything
that
we
want
to
currently
support
plugins
to
be
able
to
do
they
can
now
do
I.
Think,
though,
I
think
there's
a
few
exceptions
that
they
cannot
do,
which
is
port,
forwarding
and
terminal
windows,
is
that
right,
Sam,
yeah.
B
A
A
And
then
so,
that's
it
for
the
agenda.
That's
where
we're
marching
towards
no
marching
but
we're
looking
at
a
release
here
soon.
There
was
some
things
that
we,
if
you
can
see
below,
and
the
March
4th
agenda,
we
talked
that
the
Monaco
yamo
viewer,
the
logging
interface
CR
DS
and
the
terminal
tab
being
moved.
I
think
the
only
one
left
is
the
is
the
terminal
tab.
A
C
A
Know
I
really
yeah
it's
it
was
it
was.
It
was
great
progress.
I
everyone
did
a
great
job.
I
just
came
back
to
a
bunch
of
work
being
done,
which
was
pretty
awesome,
so
I
didn't
have
to
do
anything
and
everything's
better,
so
I,
I'm,
gonna,
move
on
to
the
open
Q&A
unless
Milan
or
Sam
had
anything
else
or
Michael
had
anything
else.
They
wanted
to
add
before
that.
A
So
the
does
oxygen
have
plans
to
support
a
graph
component.
Yes,
eventually,
we
would
like
to.
We
would
like
to
have
some
type
of
visualization
component
in
place.
I
think
what
that
looks
like
now
is
just
as
adding
components
to
our
existing
library.
That
would
allow
folks
to
then
build
out
a
graph
UI
I.
A
You
want
it
to
do
right
now,
where
they're
very
much
targeted,
we
have
some
visualization
in
there.
The
donut
graph
is
one
that
we
needed
for
the
work
flow
workloads
of
you.
So
as
we
need
them,
we
add
them.
We
will
absolutely
accept
pull
requests
if
you're
looking
for
specific
visualizations
that
aren't
available-
and
you
want
that
component
in
octant-
and
it's
something
where
you
just
don't
see
it
then.
A
A
A
A
No
I'll
find
it
and
put
it
in
the
agenda
there.
There
was
someone
who
was
writing
a
plugin
I
believe
this
for
Tecton
and
what
they
they
were
leveraging.
The
fact
that
we
have
a
graph
is
graph
is
that
we
have
a
graph
is
component
and
you
can
use
that
in
your
plugins
to
draw
basic
graphs,
like
you
know,
like
tags
and
stuff,
like
that,
you
can.
You
can
use
that
to
do
to
do
that.
A
C
A
Yeah
here
we
go
so
this.
This
is
what
I
was
looking
for.
Thank
you
Michael.
This
is
a
so
this
person
here
is
using
our
graphics
component
to
render
some
graphs
in
there
and
their
plugin.
This
was
this
is
a
issue
they
were
having
with
it,
not
working,
but
we
were
able
to
get
it
to
render,
and
so
we,
you
do
have
access
to
a
graphics
component
in
octant,
and
that
is
currently
right
now.
A
Here's
the
example
of
how
it
renders
out
under
the
under
its
own
tab,
so
not
time-series
data
visualization,
but
it
is
a
little
more
visualization
than
I.
Think
a
lot
of
people
know
about
because
this
is
a
very
well-documented
that
we
have
this
component,
but
yeah
you
can.
You
can
do
stuff
like
that.
A
That's
it
really
I,
don't
that
yeah!
Everyone
did
some
great
work
this
week
and
we're
we're
moving
right
along
and
I
would
expect
us
to
to
be
able
to
do
an
official
release
early
next
week,
barring
any
outstanding
horrible
things
with
moving
the
terminal
tab,
which
very
well
could
happen,
but
hopefully
not.