►
From YouTube: Octant Community Meeting - July 28th, 2021
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.
Feel free to add any discussion topic or question you may have to the agenda: https://hackmd.io/CzaPxtmXT_SW8nEpdwvGzw?view
A
There
you
go
hello,
everyone
and
welcome
to
our
octan
community
meeting
today
is
july,
28,
2021
and
well.
Remember
that
if
you
cannot
join
live,
you
will
find
the
recordings
in
the
youtube
channel
and
also
the
meeting
notes
are
moved
to
github
discussions.
We
try
to
keep
the
notes
for
the
last
two
meetings
here
in
hackendy
for
older
notes.
You
can
go
and
find
them
in
github
discussions
feel
free
to
add
yourself
and
in
the
organization
you
represent
to
the
meeting
agenda
and
well,
let's
go
to
status
updates
first
one.
A
B
Is
yeah
so,
as
david
said,
it's
planned
for
it
it'll
either
be
friday,
friday,
the
30th
or
monday,
the
second
and
yeah.
That's
it
the
a
lot
of
good
stuff
here
in
progress.
As
a
reminder,
our
theme
for
this
release
is
around
object,
status
and
and
improving
the
visibility
of
of
different
status
and
conditions
on
objects
and
and
making
things
just
a
little
bit.
B
You
know
more
friendly
and
easier
to
see
so
yeah
a
lot
of
good
work
happening
and
very
excited
about
the
outcome
of
this
release
and
yeah.
I
think
bro.
I
think
the
plan
is
to
probably
do
a
blog
post
that
does
an
overview
of
all
of
the
various
changes
that
that
we'll
ultimately
have
around
project
status
for
this
release.
B
So
you
should
should
see
a
summary
of
all
of
those
changes.
Sometime
probably
the
week
following
so
there's
the
week
of
the
release
would
be
the
following
week,
we'll
do
like
a
a
summary
update,
blog
post
type
thing
and
as
a
reminder,
it's
jumping
the
agenda
a
little
bit
that
there
is
no
community
meeting
in
next
week
and
yeah
most
of
the
team.
All
the
team
is
on
holiday
next
week,
so.
A
For
sure
yeah,
thank
you
so
much.
This
is
going
to
be
a
really
interesting
release.
You
know
it
will
be
really
helpful
for
users.
I
believe,
okay
next
item,
we
have
our
first
official
adapter
organization
what
it
means
you
know
we
know:
octan
is
used
by
by
many
developers
and
organizations
around
the
globe,
but
this
is
the
the
first
organization
who
has
publicly
shared
how
they
use
octant
and
they
have
sent
their
company
logo
to
be
added
to
the
adopters
file.
I
believe
the
the
tests
have.
A
A
What
will
happen
if
I
will
code,
but
I
see
that
all
checks
have
passed
and
we
will
have
the
information
from
there
sky
up
there,
who's
who
stares
kite.
There
is
a
top
technology
solutions
provider
with
headquarters
in
israel
and
also
offices
in
new
york,
and
they
use
often
in
a
daily
basis
and
also
their
customers,
use
often
to
be
able
to
debug
troubleshoot
in
general,
manage
kubernetes
environments.
A
That's
great,
okay,
I
don't
know
if
someone
has
a
comment
around
this
or
we
can
go
to
next
point,
we'll
be
displaying
container
image
manifest
by.
C
Milan
yeah,
I
can
go
next.
If
you
don't
mind
david,
can
I
share.
A
D
C
Cool
yeah,
so
this
is
a
pretty
old
pr.
I
just
wanted
to
give
a
quick
showcase
of
this
new
feature
coming
in
in
next
release.
C
C
It
kind
of
depends
on
on
a
image
order,
what
kind
of
manifest
they
they
will
choose,
and
there
is
a
really
good
tool
out
there
that
displays
all
that
in
information
for
images
it's
called
scorpio
and
basically
what
it
does
you
pass
in
the
image
and
it
can
give
you
the
the
image
manifest
back.
It
can
give
you
the
configurations,
layers,
all
kind
of
stuff.
It
can
also
copy
the
images
and
it's
doing
it's
inspecting
the
image
without
pulling
it
down,
which
is
pretty
cool.
C
Container's
image
go
package
and
I
end
up
using
the
same
package
to
display
image
information
inside
the
object.
So
the
way
that's
gonna
happen
now
is
inside
the
container
container
part
of
of
the
pod
overview
page.
We
always
display
the
image
and
image
id,
but
now
either
those
two
fields.
One
of
them
is
image
manifest
and
the
other
one
is
the
configuration
and
to
display
those
I'm
using
sam's
json
viewer,
because
those
are
json
files
and
so
basically
they're
just
displayed
the
way
they
are,
and
you
can
see
that
this
one
has.
C
You
can
see
what
schema
version
it
has.
You
can
see
all
the
manifests
for
each
manifest.
You
can
dive
in
and
see,
see
different
kind
of
information
and
things
even
more
interesting.
If
you
get
in
a
configuration
level,
you
can
see
the
config
for
that
image
and
cool
stuff
like,
for
example,
this
one
has
exposed
port,
80
and
environment
variables.
C
Like
conversions
and
and
things
like
that-
and
those
are
really
really
interesting
for
troubleshooting
and
discovering
problems,
because
you
know
sometimes
through
environmental
variables,
to
image
you're
supposed
to
pass
in
like
database
information
and
stuff
like
that,
and
if
that
doesn't
work
you
can
just
quickly
dive
in
and-
and
you
know
and
see,
what's
going
on
so
yeah.
So
this
is
using
the
json
viewer.
I
did
a
little
update
there,
so
you
can
display
them
a
collapse,
I
think,
by
default
they
should
be
collapsed
and
also
you'll
notice.
C
So
I've
been
testing
this
quite
a
bit
on
not
only
on
my
local
kind,
but
if
you
go
to
our
development
cluster
and
let
me
just.
E
B
C
Like
this
right
here,
so
the
information
that's
displayed
here
is
it's
it's.
It
varies.
C
The
information
varies
depending
on
the
on
the
image
type
on
manifest
type
or
and
on
on
on
image
itself.
So
you
can
see
this
one,
for
example,
even
has
the
others.
C
So
if
you,
if
you
have
some
issues
with
it,
you
can
find
the
other
and-
and
you
know,
contact
him
directly
and
again-
there's
exposed
ports,
so
this
totally
brings
different
level
of
troubleshooting
abilities
towards
them
because
as
a
developer,
sometimes
you
can't
hit
the
right
port
and
you
can
trace
the
information
all
the
way
down
to
image
to
manifest
or
you
can
find
out.
Oh
that
this
is
my
environment
variable.
I
need
to
use
and
things
like
that,
so
so
that's
pretty
much
all
I
get.
This
is
coming
up,
I'm
hoping
23..
C
It
depends
on
the
update
of
our
kubernetes
library
to
021,
and
once
that's
done
I'll
have
to
recreate
this
branch.
I
had
some
issues
with
importing
modules,
but
hopefully
all
that
lines
up,
so
they
can.
This
can
land
for
our
next
release.
D
This
is
awesome.
Milan.
I
really
really
like
the
using
the
json
viewer
and
being
able
to
expand
and
collapse
it.
I
have
two
thoughts
on
it.
One
is
the
green
text
in
the
dark
mode.
It's
a
little
tough
to
read.
C
D
So
I
don't
know
you
know,
I
don't
know
how
packed
into
the
json
viewer
that
is
or.
C
We
can
definitely
modify
that
css.
I
know
sam
did
a
little
bit
of
work
there,
but
I
can
definitely
expand
that
and
make
it
I.
I
absolutely
agree.
D
B
D
And
the
other
one
is:
would
there
be
some
value
to
and
expand
all
collapse
all.
B
C
B
Yeah
and-
and
I
would
say
that
like
that
is
definitely
something
where
I
would
consider
that
an
enhancement
to
the
existing
component.
So
if
you
go
to
look
at
it
and
you're,
like
that's
more
than
a
half
hour,
you
know
then
make
an
issue
and
we'll
add
it,
but
if
we
can
get
it
in
there
quick,
then
I
think
that's
a
big
win.
D
Yeah,
absolutely
I
agree
we
can.
We
can
always
make
another
issue
for
that.
A
A
Okay,
go
back
and
agenda.
Okay,
that's
great
okay
discussion
points.
First,
one
release
notes
enhancements.
You
know
when
it's
related
to
what
wayne
was
mentioning
at
the
beginning.
We
have
so
much
happening
in
this
release
that
we
will
need
more
context
for
users.
So
they
know.
Why
is
this
important?
What
how
how
it
changes
the
experience
and
troubleshooting
object
status
and
all
of
that,
so,
according
to
some,
you
know,
guidelines
from
the
open
source
office
here
from
vmware.
There
are
some
ways
to
make
release
notes
more
informational.
A
We
we
have
this
first
wrapper
with
what
will
be
a
template
for
release
notes,
hopefully,
from
this
release
and
the
upcoming
releases,
where
we
will
have
not
only
maybe
the
issue
title
and
number
and
handle,
but
also
a
description,
it
doesn't
have
to
be
a
full
article,
but
any
descriptions
if
it's
for,
for
example,
a
bug.
A
What
is
the
problem
or
the
behavior
these?
These
visual
fixes
addresses,
if
it's
an
enhancement,
basically
why
this
is
important
for
for
users,
you
have
some
reference,
for
example,
the
the
job
of
the
contour
theme.
These
are
the
release
notes
and
they
have
some
free,
stylish
sections
and
all
that
we
don't
plan
to.
A
You
know,
take
a
step
to
this
level
in
a
single
release.
No,
but
just
starting
to
make
those
release
notes
a
little
bit
more
information.
I
don't
know
if
cara
won't
feel
common,
something
there.
D
Oh
just
that
it
seemed
like
a
bit
of
a
heavy
lift
for
a
single
developer,
to
be
responsible
for
all
the
release
notes
and
to
be
able
to
understand
every
single
thing
that
had
been
you
know
checked
in
so
you
know,
each
engineer
should
be
intimately
familiar
with
the
two
or
three
issues
that
they
have
in
this
particular
release.
So,
towards
the
end
of
the
release,
they
should
be
able
to
write
a
quick
description
for
their
two
or
three
issues.
You
know
write
them
up
and
then
whoever
is
the
release.
D
B
Yeah,
so
we
we
do
this
now
we
just
kind
of
fell
off
the
the
the
practice
of
it,
but
we
have
a
process
for
all.
Pr's
technically
are
supposed
to
have
a
change
log
entry
and
that
change
log
entry
allows
the
developer
to
expand
and
provide
full
context
for,
above
and
beyond
what
the
commit
message
says
and
when
you
run
the
release
script,
it
processes
all
the
changelog
entries
out
into
a
single
markdown
file
that
can
then
be
kind
of
massaged
and
edited
as
needed.
B
D
Oh
yeah,
automation
for
the
win
for
sure
I
didn't
realize
that
that
was
already
automated.
So
yes,
as
long
as
the
change
log
entries
as
long
as
those
are
a
little
bit,
you
know
as
long
as
they
are
a
little
descriptive,
then
great
and
then,
as
soon
as
we
have
a
tech
writer
who's
joined
the
team,
then
they
can
massage
them
more
fully.
B
So
change
logs,
yep
and
then
and
there
will
be
an
unreleased
folder
yeah.
So
these
are
the
currently.
These
are
the
things
that
are
in
trunk
right
now
that
have
not
been
released.
Yet
most
of
them
will
just
have
like
a
a
short
summary
that
maybe
matches
the
commit
message,
but
we
can
just
make
a
an
effort
to
have
developers
put
in
more
useful
context
into
the
long
form
message
that
goes
in
here.
C
Just
a
quick
ux
point,
I
I
think
could
release
notes
should
either
be
brief
or
if
they
are
not,
they
should
have
like
a
summary
at
the
top
because
they
are
they're
meant
to
be
consumed
very
quickly.
You
know,
if
you,
if
you
are
upgrading,
let's
see
upgrading
your
dependencies.
You
just
want
to
glance
through
and
see
if
there's
something
important.
D
B
Points
yeah,
I
think,
I
think,
avoiding
getting
into
the
territory
of
a
released
blog
post
right
like
we
can
have
a
release,
blog
post,
which
is
rich
screenshots
walkthroughs,
all
of
that
like
long-form
stuff
and
then
yeah
keeping
it
here's.
Why
you
here's?
Why
you
care?
Here's
where
you
can
go
find
out
more,
if
you
maybe
still
aren't
sure
that
you
care
and
then
here's
the
short
form
notes.
F
A
F
B
Yeah,
that's
usually
one
of
those
things
that
the
person
who
generates
the
changelog
file
has
to
go
in
and
tweak.
We
can
start.
We
can
add
that,
as
part
of
our
review
process
to
make
sure
that
the
messages
are
using
the
the
correct.
B
A
C
Yeah-
and
this
is
an
interesting
one-
felipe-
and
I
were
programming
yesterday
on
this
issue-
showing
that
the
more
information
for
the
persistent
volume
claims
actually
showing
incorrect
information
for
persistent
claims,
and
we
discovered
an
interesting
thing
and
I
will
share
a
screen
oops.
C
It
I'll
show
you
the
whole
desktop
yeah,
so
so
this
is
our
code
for
displaying
status
and
it's
it's
kind
of
puzzling
and
I'm
not
sure
why
we're
doing
this
way.
But
you
can
see
basically
at
the
top.
C
Oh
there
we
go.
I
found
my
intel
g
all
right,
so
this
is
our
code
for
displaying
object,
status
and
you'll
see
we
have
a
different
lookup
functions
depending
on
on
a
basically
resource
state
and
later
on.
We
use
that,
and
there
is
a
piece
of
code
here
where
we
invoke
that
function
and
if
it's
not
present,
we
basically
say
this
and
I
think
that's.
The
problem
problem
is
because,
if
you
look
at
this
list,
there's
only
14.
C
Different
resource
types
we
register
for
and
for
everything
else
we
just
say
I
mean
I
think
that
a
more
prudent
thing
would
be
say
unknown
or
something
like
that.
So
that's
why
we
have
a
lot
of
greens
where
we
shouldn't
have
so
so,
and
I
worked
on
that
and
we
realized
well.
We
just
need
to
add.
You
know
thank
for
the
testimonial
claims
that
he'll
fix
the
issues
so
that
fixed
the
particular
problem,
but
keep
both
of
us
feel
like.
Oh,
maybe
we
should
do
for
all
the
resources.
C
C
B
Yeah,
I
think
this
gets
into
some
interesting
territory
specifically
around
the
fact
that
everything
we
do
is
typed
right
now
and
extending
things
like
status
or
extending
things
like
conditions
requires
that
we
add
to
our
list
of
well-known
types
so
that
we
can
go
and
and
look
at
that
status
object
or
that
condition
object.
B
B
Some
of
the
steps
around
doing
that
have
been
started
with
this
update
that
we're
making
to
the
conditions
table
where
you
know,
there's
actually
a
parse
conditions,
method
that
is
going
through
an
unstructured
object,
parsing
the
json
of
it
and
then
looking
for
a
specific
set
of
fields
and
if
it
finds
those
fields,
it's
it's
making
it
and
those
fields
are
formatted
how
it
expects.
Then
it
makes
the
assumption
that
those
fields
are.
You
know,
in
this
case
condition
dot
or
status
dot
conditions
right.
B
If
that
parses
out
as
a
as
a
slice
of
strings,
then
it
says:
hey
these
match
my
assumption
of
what
status
conditions
are,
and
I
think
we
can
do
a
similar
thing
for
other
parts
of
octants,
specifically
around
status
and
and
health
of
objects,
and
so
in
the
short
term.
I
I
think
you're
right,
I
think,
adding
you
know
extending
the
list
to
support
the
the
known
types
of
objects
that
have
well
that
are
well
formatted.
That
we
know
will
support
fetching
their
status.
B
It
makes
sense
to
add
those
there.
I
think
in
the
long
term,
we
probably
want
to
look
at
engineering
a
more
generic
solution,
that
you
know,
inspects
the
object
and
then,
if
it
finds
the
fields
that
it
needs
to
find,
then
it
says:
hey.
I
found
status
fields,
so
I'm
gonna
use
them.
C
Yeah
that
totally
makes
sense,
and
since
this
releases
you
know
stylus
around
would
be
good
to
do
the
first
step.
If
you
can
and
improve
this.
B
Yeah
yeah,
I
definitely
think
just
adding
extending
the
known
list
to
to
make
the
improvement
is,
is
perfectly
reasonable
solution
here,
because
that's
that's
the
way
the
world
works
now
in
octant,
so
yeah.
I
wouldn't
expect
us
to
try
to
engineer
the
generic
solution
here
so
yeah,
let's
say
move
forward
with
adding.
B
Yeah
so
so
this
came
up
as
a
result
of
some
work.
That's
being
done,
and
I
wanted
to
to
raise
it
here
so
so.
Currently
we
don't
have
we
kind
of
have
this
split
brain.
We
have
local
preferences
stored
in
the
electron
side
of
things,
and
then
we
have
server
side
state
which
is
tracked
while
octant
is
running.
An
example
of
this
is
like
your,
whether
you're
using
light
or
dark
mode,
or
the
number
of
results
that
show
up
in
a
table.
B
Those
are
those
are
stored
on
stage
on
the
octane
side
of
things,
so
we
kind
of
we
kind
of
like
decide
what
goes
where
we're
getting
to
this
interesting
spot
where-
and
I
think
it's
gonna
start
to
happen
more-
where
we
have
a
preference
that
we
wanna
set
and
we
want
it
to
be
configurable,
but
it's
used
in
the
runtime,
it's
used
in
the
server
side,
but
we
want
it
set
from
the
client
side.
B
This
example,
in
particular,
is
around
the
terminating
threshold
right
like
the
how
how
long
do
we
want
to
wait
before
we
show
some
extra
messaging
or
provide
some
prompting
to
a
user
when
something
has
been
stuck
in
terminating
for
an
extended
period
of
time
this
this
can
be
set
on
the
client
side,
but
then
we
want
to
persist
it
through
the
rest
of
of
octant
and
so
there's
kind
of
there's
kind
of
two
ways
to
to
do
this:
it's
either
to
create
a
preferences
state
manager
which
we
preload
with
this.
B
You
know,
whatever
we've
used
to
load,
that
state
is
also
what
we
use
to
update
that
state.
As
things
are
running,
the
other
option
is
just
to
commit
to
saying
like
hey,
you
know
we're
an
electron
application.
Octan
knows
where
the
file
system
is.
It
knows
where
the
files
that
electron
are
going
to
write
are-
and
we
just
read
it
direct
from
the
file
system
right
instead
of
instead
of
introducing
this,
this
state
manager
that
kind
of
acts
as
a
as
a
proxy
for
the
file
system
between
electron
and
octane.
B
So
I
don't
know
that
I
don't
really
have
a
strong
opinion
either
way.
One
definitely
changes
the
like
it
just
changes
kind
of
the
the
the
reading
directly
from
the
file
system,
one
we
already
do
it.
We
do
it
with
like
cube
configs,
for
example,
and
then
the
state
manager
one.
We
already
do
it.
As
I
pointed
out,
we
do
it
for
things
like
the
name
space
you
have
selected.
You
know
stuff
like
that,
so
we
already
do
both.
B
I
don't
have
a
strong
opinion
towards
one
or
the
other,
but
I
just
wanted
to
get
that
idea
out
there.
So
people
could
think
about
it
and
if
other
people
have
strong
opinions,
you
know
bring
them
up.
I
think
we
can
talk
about
it
now,
but
also
I
would
look
at
opening
a
discussion
in
github
discussions
to
go
through
some
iterations
of
pros
and
cons.
C
Yeah,
this
is
a
very
interesting
one
and
it
I've
seen
references
getting
really
complex
and
projects
I
worked
before,
so
it
would
be
good
to
to
make
a
good.
You
know
solid
foundation
to
to
build
this
on,
and
I
one
thing
I
would
definitely
advocate
for
is
is
having
a
single
source
of
truth
and
even
that
it
almost
doesn't
matter
where
it
is,
it
could
be.
C
Electron
store
could
be
on
the
backhand
side,
but
as
long
as
you
have
a
single
sort
of
truth,
it
definitely
makes
things
a
little
more
robust,
easy
to
maintain
and
and
expand,
and
to
add
to
you
to
to
what
you
said
when
we
we
also
have
on
a
client
not
only
we
use
electron
store,
but
if
you're
running
a
browser,
we
use
the
browser,
local
storage
for
that
instead
of
like
electron
stores.
So
so
currently
we
almost
have
those
depending
on
you
know
usage.
C
We
have
the
three
different
ways
of
doing
it.
I
mean
the
way
this
is
done
on
client.
It's
basically
inside
two
methods
that
decide
or
you
know
if,
if
I'm
in
electron,
I'll
use,
electrons
or
otherwise,
so
otherwise
I'll
use
browser
storage.
So
it's
not
that
complex,
but
it
would
be
good
to
consolidate
that
at
a
single
point.
B
Yeah
I
mean
long
term.
The
deprecation
of
the
cli
version
of
octant
is
going
to
result
in
us
no
longer
needing
to
support
both
the
electron
and
web
browser
states.
So
I
I
think
I
think,
for
this
conversation
we
can
just
focus
solely
on.
Does
this
live
on
the
electron
side?
Or
does
this
live
in
the
in
the
server
to
your
point
of
having
a
single
source
of
truth?
B
That
kind
of
leans
me
towards
it
being
on
the
electron
side,
because,
even
if
we
load
it
into
some
state
manager
on
the
server
side,
the
all
of
the
preferences
and
settings
will
be
happening
like
like
when
that
octan
server
goes
away.
Unless
it's
going
to
persist
the
file
somewhere
when
it
starts
back
up,
it
doesn't
know
any
of
those
settings
again.
So
it's
almost
as
if
it
naturally
kind
of
wants
to
live
on
the
electron
side.
C
C
A
Okay,
now
for
the
open
q,
a
I
was
having
a
conversation
with
a
user
from
canada
last
week
and
he
he
requested
a
feature.
I
asked
him
to
file
an
issue
but
he's
weird
to
create
it,
but
he
was
mentioning
it
would
be
great
if
octan
will
help
me
find
deprecated
resources
in
the
cluster,
and
he
then
pointed
me
to
a
sanitizer
tool
that
he
has
used
recently
with
good
results.
A
Pope
I
pope-
I
don't
know,
but
in
general
I
I
brought
up
this
here
as
a
question,
because
you
know
what
what
he
mentioned
led
me
to
think
about
the
upcoming
1.22
kubernetes
release
that,
as
far
as
I
understand,
is
going
to
deprecate
some
api
resources.
A
So
in
general,
is
this
something
that
we
should
pursue
in
octane.
What
do
you
think
about
this.
D
Idea,
I
was
going
to
say
the
same
that
maybe
this
is
a
plug-in
possible.
I
don't
know
why.
I
feel,
like
I've
run
into
this
one
recently.
Somebody
brought
up
popeye,
it's
pronounced
popeye
if
you're
interested.
D
Super
old
cartoon
character-
oh
yeah,
but
yeah,
maybe
maybe
a
plug-in,
but
I'm
just
not
terribly
familiar
with
it.
A
Yeah
more
like
yeah,
the
the
tool
is
maybe
an
example,
but
in
general
the
the
ability
to
find
deprecated
resources
in
the
cluster
is
something
that
we
see
a
place
for
it
in
octane
or.
D
A
good
for
a
good,
plugin
or
or
someone
can
make
a
proposal
for
it.
A
A
D
If
we
can
find
a
contact
at
popeye
who's
interested
in
writing
a.
A
E
Yeah,
so
I
guess
this
is
more
of
a
discussion
point,
but
this
is
something
I've
been
kind
of
running
into
a
bit
lately,
I'm
gonna
just
share
my
screen
real
quickly
to
kind
of
explain
exactly
what
this
is
about
hold
up
one.
Second,
I'm
not
able
to
share
my
screen
yet.
E
See
david.
E
Okay,
all
right
and
so
yeah.
So
basically
the
way
octane
works
it
inserts
this
kind
of
breadcrumb,
slash
navigation
element
at
the
start
of
pretty
much
any
asian
plugin,
which
is
useful,
but
not
always,
and
so
specifically,
for
example,
I
was
trying
to
make
a
new
page
here
and
it
automatically
inserted
this
home
kind
of
route
at
the
start,
and
I'm
not
entirely
sure
why
that
is
happening.
E
But
I
feel
like
this
isn't
necessarily
the
most
desirable
solution,
and
especially
if
there's
a
page
where
you
really
don't
need
a
title,
it
will
just
insert
content
like
this
at
the
start
as
well,
where
it
basically
just
displays
the
same
drop
down
twice.
So
this
is
obviously
useful
when
you're
using
the
core
auction
features,
and
there
are
lots
of
nested
hats
and
so
on.
But
if
this
is
just
kind
of
like
a
a
smaller
plug-in,
that's
a
module.
E
This
is,
I
feel,
like
gonna,
be
less
useful
and
it
also
kind
of
ties
into
something
I
noticed
in
general
about
octane
as
well.
Is
that
you'll
kind
of
see
the
same
content
three
times
in
in
certain
parts
of
the
application
which
I
feel
like
is
just
kind
of
redundant
because
we're
already
we
clicked
on
the
namespaces
page,
and
then
it
tells
us
that
yes,
we're
on
namespaces,
the
title
is
namespaces
and
the
title
of
the
table
is
namespaces.
E
So
I
feel
like
just
giving
a
lot
of
like
additional
flexibility
to
maybe
plug
in
authors,
but
also
to
you
know
the
octa
developers
in
general
to
enable
or
disable
this
like
kind
of
navigation
component,
when
it
makes
sense,
would
be
really
useful
in
terms
of
just
you
know,
granting
more
access
to
you
know
information
that
our
users
care
about,
and
especially
so.
E
This
is
an
example
of
an
embedded
iframe
and
it
actually,
you
know,
adds
a
bit
of
content
to
the
top
of
the
page
so
or
this
removed
you'd
be
able
to
fit
the
entire
iphone
in
which
is
kind
of
useful,
because
this
is
valuable
screen
real
estate
when
you're
embedding
an
entire
web
page
inside
another
one
already,
so
I
just
figured
we
might
as
well
have
like
a
bit
of
a
like.
E
You
know
a
few
questions
about
how
this
could
work
or
what
what
people
kind
of
think
about
it
to
kind
of
discuss
like
whether
this
is
something
that
would
be
worth
implementing
or
if
there
are
reasons
that
this
hasn't
been
implemented
yet
kind
of
that
kind
of.
C
D
D
C
C
So
I
you
know,
I
definitely
agree
with
your
second
point
and
that's
kind
of
been
so
point
for
me
as
well,
but
never
we
never
get
to
it.
So
we
should.
I
think
that
we
should
definitely
fix
that.
At
least
you
should
remove
one
of
those
so
that
that
is
definitely
a
no-brainer.
As
for
the
plug-ins,
so
the
way,
the
way
that
the
breadcrumbs
work
they
pull
all
the
links
from
the
navigation
entries
for
the
for
the
plugin.
C
So
as
you
registered
your
you
know,
navigation
entries
like
in
this
case,
you
have
a
home,
you
have
central
dashboard
and
it
just
goes
through
those
entries
and
creates
the
breadcrumbs,
and
on
top
of
that,
plugin
has
the
last
word
and
how
those
will
be
displayed.
C
So
if
you
as
a
plug-in
not
or
want
to
hide
them
all,
you
can
just
remove
that
list
and
it
will
never
show
up
so
so
this
is
how
it
works
currently,
and
it
can
definitely
be
extended
and-
and
you
know
maybe
you
and
I
can
work
on
that
and
see
what
would
be
the
best
way
to
to
make
it
a
little
more.
You
know
configurable,
especially
for
plug-in
authors.
D
Yeah
I
mean
I
definitely
see
that
there's
value
in
one
of
those
use
cases
where
you
showed
in
the
namespace
overview.
You
know,
there's
still
the
the
beginning
of
the
breadcrumb
still
has
a
drop
down
that
lets
you,
you
know
quickly
navigate
from
the
drop
down
so
like
there's
still
value
there.
Even
though
there's
that
triplicate,
you
know
showing
the
the
title
and
triplicate
so.
C
A
Okay,
there
is
no
other
q,
a
we'll
go
finally
to
the
community,
shout
outs
sunday,
yes,
left
blatant
created
as
or
send
his
first
pr
to
octet.
Thank
you
so
much
for
that.
We
really
appreciate
you
doing
this
once
on
this
small
conflict
in
a
file
I
believe,
is
fixed.