►
From YouTube: Octant Community Meeting - October 7th, 2020
Description
Octant community meeting is held weekly. We discuss and talk about the current state and future of Octant, demo upcoming features and releases, and preview new ideas we are considering for Octant.
Meeting agenda: https://hackmd.io/CzaPxtmXT_SW8nEpdwvGzw?view
A
A
All
right,
thank
you.
Everyone
for
coming
to
the
october
7th
2020
community
meeting
octon
community
meeting
today
we're
going
to
cover
some
like
what's
coming
up
with
the
new
release
and
also
we're
gonna
talk
about
some
design
stuff.
I
don't
know
if
isha
and
lindsay
want
to
go
first,
if
they
have
other
meetings
they
need
to
run
to
or
if
they
want
to
hang
out
for
the
for
the
upcoming
release.
Talk.
A
Great
well,
then,
we'll
we'll
get
right
into
it
and
we'll
start
talking
about
this
upcoming
release.
So
we
have
got
a
bug,
fix
release
coming
out.
It's
0.16.1
lots
of
lots
of
good
bug,
fixes
here,
a
lot
of
people
right
after
odd
16.
Most
of
these
were
reported
as
new
things.
There's
a
couple
regressions
in
there
that
are
getting
fixed
and
just
some
some
quality
of
life
stuff,
that's
kind
of
been
hanging
out
for
a
while
that
we've
managed
to
get
in
here.
A
That
was
the
issue
where,
if
you
were
viewing
some
res
something
that
wasn't
a
resource
in
the
cluster
and
you
switch
namespaces
so
like
say
reviewing
events,
you
switch
namespaces.
You
get
redirected
back
up
to
the
namespace
overview
for
the
thing
you
just
switched
to.
Instead
of
seeing
the
new
events
for
the
namespace
you
switch
to,
so
we
sam
fixed
that
now
also
like,
if
you're
in
a
plug-in
menu
things
like
that,
you
switch
name
spaces.
It
doesn't
bounce
you
up
to
this
completely
different
context,
so
got
that
fixed.
A
There
was
a
security
issue
in
that
version
that
was
fixed
where
they
started
to
use
the
security
context
and,
as
a
result,
the
behavior
that
was
being
depended
on
broke,
which
was
you
could
just
put
html
into
a
markdown,
and
it
would
render
so
we've
explicitly
enabled
that
option.
Now
you
can
flag
your
text
component
as
trusted
content,
and
so,
if
you
use
markdown
with
the
trusted
content
flag,
then
it
will
render
html
script
tags
still
will
not
work
they'll
be
flagged
as
unsafe
and
and
show
up
as
such
in
the
output.
A
As
a
result
of
that,
our
own
internal
page,
our
not
found
page,
the
back
link
on
that
is,
is
broken,
but
we're
going
to
be
fixing
that
differently,
because
we're
going
to
be
using
the
electron
method
for
going
back
so
that
won't
really
matter
to
us.
Log
scrolling
stays
focused
when
switching
containers
or
follows
that
it
was
bouncing
back
up
to
the
top
client
id
is
now
part
of
action.
Request.
A
A
So
if
you
were
just
rendering
out
a
plain
content
response
with
like
a
card
in
it
a
lot
of
times
the
breadcrumb
title
generation
wasn't
there,
but
then
you
would
add
a
tab
and
it
would
show
up
so
sam
fixed
that
we
fixed
the
yaml
highlighting
which
got
broken
when
we
moved
the
yaml
apply
into
modal
and
then
we've
also
addressed
the
default
listener.
Address
is
now
127.0.0.1
instead
of
localhost.
A
So
this
just
ensures
that
pretty
much
universally
127
is
is
available
wherever
you
go
so
and
so
that
is
what's
coming
out
in
the
next
release,
there
might
have
been
something
I
missed
sam
or
milan,
I'm
not
sure,
but
if
I,
if
I
did
it'll,
be
in
the
release,
notes
and
so
yeah,
I
really
want
to
say
thank
you
to
sam
on
this
sam.
I
think,
did
all
of
these
except
one
I
think
so
it
was
he
he.
He
went
really
hard
on
on
the
bug
fixes,
and
it
was
really
great.
A
A
All
right
cool,
so
moving
on,
I'm
gonna
stop
the
share
for
a
minute.
We
have
design
stuff
to
talk
about
design,
design,
design,
all
sorts
of
design,
so
isha
and
lindsey
are
here
to
introduce
themselves
and
kind
of
talk
about.
What's
going
to
be
happening
with
some
of
the
upcoming
design
efforts
for
octant.
C
Hi
I'll
just
I'll
go
first
and
then
I'll
introduce
isha
who's
going
to
be
leading
the
research
and
design
for
command
this
week
all
right
this
month,
I'm
lindsay
akaneki,
I'm
based
in
toronto,
and
I
am
the
product
design
lead
for
the
developer
management
program
and
I
am
working
with
isha
to
do
some
baseline
user
and
workflow
discovery.
Research
work
over
the
next
couple,
four
weeks.
C
In
addition
to
that,
we
hope
to
look
through
some
of
the
most
important
ux
fixes
that
we
can
get
to
to
get
some
quick
iterations
in
there.
While
we
do
this
research
work
to
help
improve
the
user
experience
in
opt-ins,
but
what
we're
looking
for
from
the
community
is
your
feedback,
so
we
are
looking
for
some
participation
from
you
all
to.
If
you
to
talk
to
us
about
some
of
your
pain
points.
C
Some
general
feedback-
and
we
hope
to
in
the
next
week,
have
a
further
defined
proposal
on
github
that
we
can
reference
for
you
all
to
look
at
how
we're
progressing
through
this
research
over
the
next
couple
weeks
and
there
you'll
find
how
to
contact
isha
and
myself
and
start
this
ball
rolling.
For
getting
some
of
these
feedback
cycles
going
for
you
all
so
I'll
pass
it
off
to
isha
to
introduce
yourself.
B
Thanks
lindsey
for
the
overview
hi
everybody
I'm
misha,
I
was
previously
on.
I
don't
know
if
you
use
contours,
but
I
was
previously
on
the
concourse
team
and
I
worked
on
another
ci
cd
tool
with
an
organization
and
now
I'm
here
to
help
support
some
of
the
research
for
opt-in.
Like
lindsay
said,
we
are
looking
for
everyone's
feedback,
so
in
the
next
couple
weeks
in
the
octant
channel,
look
out
for
links
to
like
surveys,
we're
looking
to
have
like
one-on-one
discussions
with
you
all.
B
So,
if
you're
interested
it's
a
great
opportunity
for
you
to
share
how
you're
using
octent
and
to
give
us
some
feedback
on
how
we
can
improve
it.
So
just
watch
out
watch
out
for
that
in
the
channel.
We're
still
getting
everything
together,
but
we're
looking
forward
to
talking
with
all
of
you
and
getting
some
feedback.
A
C
A
Awesome
excellent,
so
yeah,
like
I
said,
keep
an
eye
out
for
that
kind
of
stuff.
I
imagine
it
will
come
in
the
form
of
on
the
slack
channel
and
github
issues
and
and
looking
for
feedback
there
so
and
if
you're
interested
before
any
of
that
stuff
gets
posted
if
you're,
if
you
know
that
you're
gonna
be
interested
in
providing
feedback,
feel
free
to
reach
out
before
you
see
anything
and
we'll
we'll
get
you
in
touch
with
everybody
and
yeah
start
to
start
to
capture
some
of
your
your
input,
so
the
next.
A
D
D
So
hopefully
you
guys
have
some
feedback
for
us,
but
the
basic
issue
we
were
trying
to
so
is:
our
navigation
was
just
getting
a
little
too
big,
especially
in
a
compressed
mode
when
it
was
collapsed,
so
the
the
two
things
will
you
will
notice
right
away
that
at
the
very
top
there
is
no
more
collapse,
expand
button
and
also
at
the
bottom.
We
remove
the
theme
switch
button
and
they
are
not
available
right
now
by
default.
Eventually,
we
will
put
those
in
preferences,
but
right
now
you
can
access
them
using
the
keyboard
shortcuts.
D
There's
a
couple
shortcuts
I
created.
So
if
I
do,
toggle
navigation
is,
and
so
the
the
new
navigation
still
supports
the
collapse
state.
It's
kind
of
similar
to
the
way
it
used
to
be
it's
just
much
shorter,
there's
not
not
as
many
items
in
the
list
as
it
used
to
be,
and
on
the
left
side
we
have
modules
and
we
expanded
modules
a
little
bit
compared
to
the
old
one
previously
mo.
D
We
only
had
two
or
three
modules
and
they
were
separated
by
separators
and
now
each
plugin
has
its
own
module,
so
plugin
orders
can
use
that
to
to
build
a
little
more
rich
uis,
and
this
is
the
only
problem.
I
don't
like
right
now,
if,
as
a
plug-in
user,
you
don't
specify
the
icons
we
use
default,
icons,
which
is
home,
so
that's
probably
not
the
best
choice
but.
D
So
if
you
are
out
there
plug-in
order,
please
use
icons,
and
so
even
in
compress
mode
they
will
show
up.
So
that
is
pretty
much
it.
I
think
this
is
ready
to
go
unless
there's
any
more
feedback
that
we
received.
So
I'm
opening
it
really
for
discussion.
If
you
guys
have
anything
that
stands
out,
please
let
us
know
I'm
ready
to
to
do
pr
on
this.
As
soon
as
we
released
released.
D
A
A
D
C
D
D
A
D
A
D
C
I
gave
my
point,
though,
adding
some
sort
of
reference
to
like
this,
like
what
we're
nesting
from
so
it
being
the
jacket
jenkins
like
plug-in
and
then
nothing
underneath
it,
because
the
highlight
there
on
the
left-hand
side.
I
know
that's
clarity,
ui's
way
of
highlighting
with
that
band
on
the
left-hand
side
to
the
icon,
but
it
is
kind
of
hard
to
see
that
highlight
because
it's
so
close
to
the
edge
of
the
browser
right.
C
D
C
Oh,
go
ahead.
Sorry,
go
ahead.
Lindsey
I
was
gonna
say
we
could
comment
on
the
issue
as
to
like
some
recommendations
to
try
like
ish,
and
I
can
look
through
clarity
and
kind
of
highlight
some
suggestions.
The
question
I
have,
though,
is,
do
you.
Would
you
rather
get
the
pr
in
for
this
release
or
like?
What
is
your
timing
on?
What
do
you
think
yeah.
A
D
D
B
B
Yeah
this
one
okay,
so
you
can
cover
and
see
it.
I
think
I
would
actually
like
some
feedback
from
the
community
members
on
the
call
regarding
this
I'm
wondering,
instead
of
relying
on
icons
like,
why
would
you
rely
on
icons
instead
of
text,
because
there's
there's
these
like
high
level
navigation
on
the
left,
some
sub
navigation
on
the
right
like?
Could
you
just
make
it
text
and
have
it
like
drill
down
kind
of
like
how
it
is
right
now.
B
Maybe
I
can
like
mock
it
up
and
show
you,
but
I
think,
relying
on
icons
to
create
some
issues,
because
people
don't
always
understand
what
icons
are.
It
might
be
a
little
bit
harder
for
accessibility,
so
I
actually
like
hinder
being
able
to
navigate
through
through
the
sidebar
if
it's
like,
everything's,
hidden
behind
an
icon,
and
I
have
to
go
through
the
extra
burden
of
like
hovering
over
the
icon
to
see
what
it
is
on.
Both.
D
B
B
D
Now,
that's
that's
a
great
comment.
I
I
I'm
on
video
on
that,
but
I
can
explain
to
you
why
why
we
decided
to
to
do
it
this
way.
There
are
a
few
reasons.
One
is
a
space
and
then
especially
in
the
expanded
view,
if
you
have
a
lot
of
text
in
both
it,
it
feels
that
there
is
a
little
too
much.
That's
like
right
now.
A
A
The
we
we
do
have
a
desire
to
enable
custom
like
svg
icons.
There
too,
so,
like
our
our
plan,
is
to
to
build
out
icons
that
convey
exactly
what
that
thing
is
without
really
having
to
to
like
know
that
the
speedometer
icon
is
for
namespaces
and
the
suitcase
icon,
like
they're,
just
not
great
icons
right.
So
it's,
I
think,
that's
part
of
it
too.
D
Right
and
one
thing
that
we
tried
is
we
try
to
use
both,
and
I
have
that
summary
recorded.
I
think
both
icon
and
text
underneath
and
that
that
was
a
little
better
from
the
information
point
of
view,
but
it
looked
a
little
messy,
so
you
know
there's
trade-offs
there
and
I'm
definitely
open
to
to
try
using
only
labels.