►
From YouTube: Octant Community Meeting - May 20, 2020
Description
May 20, 2020
Agenda
Current
Release 0.14 next week
Electron experimental preview
Migrating component documentation to Storybook
Rethinking Resource Viewer
https://calendly.com/wwitzel3/octant-office-hours?month=2020-05
A
Hello,
everyone
and
welcome
to
the
octan
community
meeting
today
as
May
20th
2020
and
for
the
agenda.
Today
we
are
going
to
talk
a
little
about
the
next
release,
some
experimental
previews
and
things
like
that.
I'll
share
my
screens,
you
all
can
see
the
agenda
and
then-
and
if
you
want
to
add
something
of
course,.
A
B
So
we've
decided
that
we've
got
quite
a
few
good
bug
fixes
and
some
improvements
that
we
wanted
to
go
ahead
and
cut
a
release.
It's
been
a
little
bit
since
the
the
13
bug
fix
release
went
out
so
we're
just
trying
to
there's
one
outstanding
issue
this
week
that
we
want
to
wrap
up
around
HBA
printers.
B
We
made
some
modifications
to
our
dependencies,
which
resulted
in
us
now
no
longer
having
to
pay
in
a
specific
version
of
some
kubernetes
imports,
which
is
great
for
plugin
authors,
because
now
they
can,
just
you
know,
run,
go
mod
and
and
things
pull
down
what
they
need
to
pull
down,
and
everything
works.
There's
no
longer
this.
These
pin
dependencies
on
on
these
specific
hashed
version
of.
B
It
was
true:
Burnett
ease,
IO,
/qu,
/
Nettie's
imports.
We
were
using
so
now.
We
actually
just
use
tag
releases
of
Clank,
oh
and
and
kate's
io
imports
for
anyway,
it's
all
there
and
working
really
well
now
so
plugin
authors
will
notice
an
improvement
and
will
also
no
longer
have
that
mismatch.
There
was
a
there's.
There
was
an
open
issue
of
quite
a
while
ago,
where
they
were.
B
Someone
was
writing
a
plugin
for
I
can't
river
went
Sam
commented
on
recently,
but
to
point
out
that
this
is
or
actually
closed
it
recently
to
point
out
that
we
fixed
it
so
yeah,
it's
it's
there's
no
most
of
the
stuff
going
into
o
dot.
14
is
bug.
Fake,
is
and
back-end
work
and
some
foundation
work
for
some
of
the
newer,
more
fun
things
that
we're
going
to
be
doing
in
the
following
release
so
expect
that
early
next
week
by
the
next,
our
goal
is
to
have
it
out
before
or
by
the
next
community
meeting.
B
B
B
We
experiments
with
that
and
got
some
some
stuff
building,
and
then
we
revisited
taking
a
look
at
the
style,
electron
library
which
has
like
a
bundler
and
some
other
tools
built
into
it,
but
it
also
has
tight
integration
with
go
so
the
benefit
here
is
that
we
can
now
directly
from
go,
have
our
PC
with
our
electronic
application.
So
this
branch
is
up
right
now.
We're
testing
through
some
things,
it's
very
experimental,
but
it
will
be
landed
in
master
behind
a
build
flag.
B
So
folks,
who
want
to
experiment
with
it,
will
be
able
to
do
so
very
soon.
It
will
not.
We
will
not
be
making
a
nightly
of
this
any
times.
Well,
we
will
eventually
but
like
right
now
it's
just
not
it's
very
early
so
but
I
just
wanted
folks
to
know
that
that
is
going
to
be.
There
is
something
that
you'll
be
able
to
start
experimenting
with.
We
encourage
anyone
who
is
interested
in
the
electron
application.
B
Version
of
octant
to
clone
master,
run
the
build
and
try
it
out
and
definitely
open
issues
that
you
run
into
as
your
as
you're
using
it,
so
that
that'll
be
in
there
very
soon
within
the
probably
today
or
or
tomorrow
will
be
merging
that
in
for
folks
to
start
looking
at
some
very
exciting.
A
another
really
neat
feature
that
so
we
talked
last
week
about
the
component.
Documentation,
work,
Sam
did
a
small
demo
and
we
showed
kind
of
where
that
was
so.
B
There
was
some
overlapping
work
being
done
around
story
book
that
was
actually
further
along
than
I
knew
about,
so
we
are
going
to
be
taking
the
work
that
we
did
for
the
plugin
documentation
and
moving
it
over
to
storybook.
It
just
makes
more
sense
to
use
storybook
it's
it's
a
first,
it's
a
tool
that
a
lot
of
people
are
more
familiar
with.
B
Second,
it
actually
gives
us
a
few
more
things
for
free
that
we
don't
get
in
the
current
iteration
of
the
plug-in
documentation
and
so
and
we're
just
all
around
it's
a
better
it'll,
be
a
better
experience
for
folks.
So
there'll
be
a
slight
little
delay
of
the
plug-in
Docs,
as
we
re
kind
of
recreate
some
things
over
in
storybook,
but
it's
mostly
just
kind
of
that
unfun
work
of
copying
and
pasting
and
making
some
edits
more
than
then
coming
up
with
all
of
the
material
originally
like
we
did
the
first
time.
B
So
it
should
not
be
an
effort
that
takes
too
long,
but
it
just
it'll
be
one
that's
kind
of
a
little
a
little
boring
but
important.
So
we
will
get
that
completed
here
very
soon
and
I
suspect
the
my
personal
goal
will
be
to
try
to
make
sure
that
the
new
component
documentation
is
going
live
at
the
same
time
where
sometime
next
week,
when
we're
putting
the
release
out.
So
so
that's
it
for
that
and
the
next
thing
I
think
Milan
was
going
to
discuss
our
approach
to
rethinking
the
resource
viewer.
D
D
You
know
we
were
trying
to
make
this
little
coulomb
up
a
little
prettier
or
a
little
different,
but
we
decided
we're
just
gonna
step
back
and
rethink
the
whole
thing
just
to
make
that
image
accurate
as
possible,
which
is
a
pretty
hard
problem.
If
you
look
around
I,
don't
think
there's
a
tool
out
there
that
currently
shows
the
good
image
of
a
cluster
or
multiple
clusters
and
along
those
lines,
we
were
hoping
to
achieve
a
little
better
user
experience.
More
interactivity
use
this
as
a
navigation
element.
D
They
kind
of
have
a
little
bit
of
that
right
now
we
show
some
details,
but
not
too
much
and
in
the
same
time,
if
we
wanted
to
make
this
feasible
to
develop,
because
when
you
deal
with
graphs
like
this,
it's
really
easy
to
make
make
it
really
hard
to
develop
it.
Because
you
know
link
those
boxes
may
be
simple,
but
in
complex
cluster
that
it's
not
so
easy.
So
I
kind
of
step
back
and
spend
some
time
on
that,
and
here
is.
D
Here's
a
buyer
model
that
I
came
up
with,
as
you
can
see,
the
biggest
difference
is
we
are
not
showing
her
a
hierarchy
of
components
as
much
as
how
how
they're
come
connected
and
also
we
try
to
contain
resources
inside
their
parent
resources.
Like
you
can
see,
the
pod
is
owned
by
the
percocet
by
deployment
and
so
on,
and
at
the
same
time
we
showed
the
links.
So
why
is
this
part
using
that
service?
Well,
it's
a
list
that
we
have
a
selector
inside
the
pod
and
sorry
selector
in
service
under
the
label
in
part.
D
So
basically
the
bait.
The
guiding
principle
has
been:
let's
try
to
show
the
map
of
a
cluster,
because
if
the
we
do
a
lot
of
things
for
very
advanced
users,
we
show
you
know
all
all
the
stuff
inside
the
cluster
we
showed
llamó
for
each
component
and
so
on,
but
for
the
for
the
novice
user
that
maybe
has
just
deployed
the
cluster
and
has
problems
finding
the
things
inside
there.
D
This
this
approach
would
look
better
and
we
think
that
if
you
can
create
the
map
of
components,
that's
well,
you
know
help
us
help
them
find
their
way
around.
So
this
is
a
kind
of
markup
and
I'll,
probably
shared
this
and
chat,
and
some
of
the
behaviors
that
we
want
to
achieve
a
list
of
here.
I
don't
want
to
go
through
all
of
them,
but.
D
This
is
kind
of
guiding
principle
and
based
on
that,
I
already
started
doing
a
little
bit
of
work.
Trying
to
prototype
you
trying
to
make
a
proof
of
concept,
because
the
worry
is
that
you
know
if
you
have
a
complex
layout,
this
may
go
out
to
hand
pretty
easily
and
there
no
reason
that
this
should
only
show
one
Costa
Rica
have
a
different
so
like
come
at.
You
should
be
able
to
zoom
out
to
see.
Oh
I
have
another
deployment
here,
and
this
deployment
maybe
has
a
conflict
map.
It
is
using
the
same
service
account.
D
D
This
is
just
that
you
know
my
model.
We
should
be
able
to
put
all
CSS
and
stars
on
top
of
that.
So
idea
is
just
to
investigate
the
feasibility
of
this
approach.
Is
it
possible
to
do
it
and
if
so,
Danna
will
probably
just
see
it
further
and
put
some
design
on
top
of
it
and
maybe
use
some
of
this
design?
That
truss
has
already
done
and
try
to
add
that
to
this
model.
B
Yes,
sir,
so
I
I
have
a
question.
Have
we
thought
about
I?
Think
I
asked
you
this
before
and
I
was
just
wondering
again
the
in
the
case
where
we
have
multiplied
the
replicas.
That
here
is
3
and
there's
pods
that
are
in
different
states
or
have
different
statuses
like
failed
and
successful
or
or
running,
and
maybe
there's
a
is
there
a?
Is
there
any
thoughts
about
how
we're
going
to
be
displaying
that
they're
going
to
be
overlays
is
going
to
be?
Is
that
information?
That's
gonna,
be
more
often
object
status
like
what's
the?
D
So
the
idea
is
that
to
have
different
layers-
and
you
know
one
of
the
layers
may
be-
you
know
those
connections.
Maybe
they
don't
want
to
share
them
all
the
time
or
another
layer
can
be
status,
so
maybe
we
can
show
them
the
green
red
indication
on
top
of
it,
maybe
even
some
kind
of
Donna
chart
or
it
it's
totally
possible
at
at
some
point.
D
Maybe
we
can
even
try
to
show
the
charts
inside
here
like
them,
maybe
spark
charts
in
the
background
of
a
bar,
that
you
can
see
like
a
CPU
consumption
in
last
24
hours
and
stuff
like
that.
So
you
know
is
similar
to
the
way
a
legend
is
displayed
here.
Maybe
we
can
have
like
a
set
of
different
layer.
Selectors
really
can
turn
those
layers
on
and
off.
B
A
B
A
B
So
I
office
hours,
I
was
hosting
them
on
Thursday
I've,
moved
them.
I
had
a
bunch
of
meetings
that
got
created
recently,
four
on
Wednesday,
so
I
just
moved
my
office
hours
to
Wednesday.
So
now
all
my
meetings
are
on
Wednesdays,
so
folks
can
take
advantage
of
those
by
going
to
I'll
put
the
link
into
the
into
the
agenda
here.
There's
a
link
go
to
you
it's
there
and
if
you
go
to
that
link,
you'll
see
there's
spots
open
every
Wednesday
and
you
can
reserve
them
there's
one
spot
left
for
today.
B
If
you
wanted
to
reserve
one
today,
but
yeah
there,
every
Wednesday
will
probably
be
just
reminding
folks
periodically.
It
seems
it's
it's
one
of
those
things
with
office
hours.
If
you
remind
people,
they
use
them
and
if
you
don't
remind
people,
they
forget
they're
there.
So
we'll
remind
people
until
it
becomes
annoying,
but
they
are
yeah.
It's
available
for
all
all
sorts
of
questions.
General
octant
help
general.