►
From YouTube: Octant Community Meeting - September 1st, 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
B
B
Appreciate
that
you
are
here,
let
me
start
sharing
my
screen
for
the
folks
that
are
joining
here
from
soon
all
right
meeting
controls
there
you
go.
Thank
you.
Notifications,
okay,
like
every
other
community
meeting.
Remember
that
our
agenda
is
open.
If
you
have
questions,
need
help
or
have
ideas,
feel
free
to
add
it
to
the
agenda
and
also
consider
adding
your
name
and
organization
to
the
attended
list.
So
we
can
connect
with
you.
After
the
meeting
for
a
past
meeting
notes,
they
have
been
migrated
to
github
discussions.
B
B
Well,
first
of
all,
getting
to
know
better
you,
your
you
are
user.
B
B
We
want
to,
you,
know,
keep
improving
the
tool
and
keep
extending
it
to
you
know
to
cover
additional
use
cases
and
even
with
our
the
best
of
our
intentions,
there's
no
better
source
of
ideas
and
feedback
than
from
our
user
base.
So
please
consider
adding
details
to
this
discussion.
You
just
need
to
add
it
as
a
submit
an
answer
here.
Using
this
format.
We
even
provided
an
example
from
a
current
user
organization
who
already
provided
their
details
and
if
you.
B
B
Check
my
audience
is
body
when
I
move
my
hands
away
from
the
make
it
improve.
Okay,
how
about
the
audio
now?
C
C
Okay,
let
me
share
up
octant,
okay,
everyone
seeing
octa
right,
good,
okay.
So
what
I'm
demoing
today
is
the
ability
to
dynamically
load
go
plugins.
Javascript
plugins
have
had
this
capability
for
a
while,
but
the
globe
go
plugins
as
well
have
always
required
a
hard
stop
and
restart
of
octant.
So
you
can
see
right
now.
I
have
no
plugins
installed.
C
So
we'll
go
back
to
this
this
page
here
and
what
I'm
going
to
do
is
in
a
command
line
terminal
that
you
currently
can't
see,
I'm
just
going
to
build
the
octant
sample
plugin
and
once
I
do
that
it
will
you'll
kind
of
you'll,
just
see
it
pop
up,
so
that
command
is
running
and
you
can
see
the
sample.
Plugin
has
popped
into
our
menu
here
and
also
our
extra
details
and
tabs
from
the
plugin
are
there.
C
If
I,
if
I
remove
the,
if
I
just
remove
the
binary,
that's
that's
currently
there
so
I've,
I
just
rmd
it.
You
can
see
that
it's
gone,
it's
gone
from
the
list,
it's
also
no
longer
listed
as
installed,
I'm
going
to
go
ahead
and
actually
reinstall
it
now,
because
the
next
thing
I
want
to
show
is
so
running
the
build
to
get
it
installed.
So
imagine
you
have
some
automated
process.
That's
just
building
your
plug-in
anytime.
You
make
a
change.
C
So
with
that
in
mind,
what
we
can
do
is
then
in
the
actual
sample,
plugin
itself.
I'm
gonna
do
this
right
now
you
can
see
it
says
from
plugin
on
there
I'm
going
to
change
that
to
just
say
demo
from
plugin,
I'm
going
to
save
and
I'm
going
to
rebuild
and
install
the
plugin,
and
what
happened
is
that
now
pops
up
demo
from
plugin,
it's
all
reloaded.
C
The
other
nice
thing
is
that
if
you
just
so
that
that
was
just
overriding
the
binary,
if
you
rename
the
the
the
plugin
like
in
the
folder
it
will,
you
know,
stop
and
restart
it,
given
its
new
name
that
doesn't
impact
the
actual
data
that's
displayed
here.
What
it
does
is
just
make
sure
that
the
process
management
is
looking
at
the
right
binary.
So
when
octant
does
shut
down
and
and
is
looking
for
processes
that
it's
in
control
of
the
the
executable
name
and
the
actual
process
name
all
line
up.
C
So
if
I
move
this
plug-in
right
now
in
my
plug-in
folder,
you
see
it
goes
away
and
comes
back.
I
can
also
you
know,
overwrite
it
with
a
with
just
a
completely
different.
You
know
completely
different
plugin,
and
now
it's
just
gvk
sample
plug-in
that
that
I
have
so
yeah.
That's
that's
kind
of
that's
kind
of
it.
It's
it's
if
you
develop
plug-ins
and
you
work
with
plug-ins.
C
This
is
this
is
something
that
I
know
folks
have
been
wanting
for
a
while
around
the
go
plugins
and
it
is,
it
is
quite
useful,
so
yeah,
that's
that's
kind
of
it.
E
That's
very
cool
I
feel,
like
our
demos,
could
benefit
from
peanut
gallery
sound
effects
like
ooh
yeah.
B
D
C
C
I
think
that's
something
we
could
actually
just
add
to
some
type
of
helpers
or
or
hacks
package,
or
something
like
that
too
easily
you
just
you
know,
watch
watch
for
changes
in
the
directory,
rebuild
the
plugin
and
and
overwrite
the
old
one,
and
it
just
stops
and
reloads
and
so
yeah,
it's
it's
very
responsive.
You
know
I
I
I
was
playing
around
with
it
and
kind
of
just
making
like
rapid
changes.
You
know,
save
build
type,
rapid
changes
and
they
they
show
up
almost
as
fast
as
I
can
all
tab
over.
C
B
C
Oh
and
one
last
thing
to
call
it
so
so
this
the
reason
we're
doing
this
is
yes
to
to
make
things
better
for
plug-in
authors,
but
also
to
eventually
have
plug-in
management.
First-Class
support
for
plug-in
management
in
the
ui.
So
now
that
the
the
now
that
the
binaries
that
get
placed
into
the
folder
and
and
all
of
that
is
being
handled
and
looked
at
by
the
octant
process
itself,
the
ui
around
this
is
much
more
simple.
It's
it's
you
know,
delete.
C
You
know
upload
to
the
folder
delete
from
the
folder
and
and
octane
just
does
the
right
thing
so
expect
the
the
plugins
module
that
we
currently
have
to
get
some
updates
soon,
around
being
able
to
upload
plugins
through
octane
delete,
you
know,
delete
plugins
through
octane.
We
don't
really
have
a
mechanism
to
say
like
pause,
this
plugin,
which
is
something
that
I
think
will
eventually
add,
there's
no
issue
or
request
for
it,
but
I
think
the
moment
we
have
plug-in
management
within
the
system.
C
I
can
definitely
see
people
wanting
to
you
know,
install
a
bunch
of
plugins
and
then
go.
You
know
turn
that
one
off
for
now,
because
I
don't
really
care
about
it
or
or
turn
version,
one
of
that
plug-in
off
and
turn
version
two
of
that
plug-in
on.
I
could
definitely
see
that
being
a
thing
that
folks
would
want
to
do
so.
C
C
You
know
essentially
unregistering
everything
without
actually
deleting
the
the
binary
there.
That
would
be
possible.
There
is
no
good
mechanism
to
say
this.
Plugin
has
been
paused
and
if
you
restart
octant,
don't
reload
it
the
so
it
would
be
a
runtime
type
pause,
at
least
for
now,
but
anyway,
that's
yeah
ui,
coming.
A
Yes,
on
the
note
of
ui,
I
think,
just
with
the
way
that
the
angular
applications
worker
doesn't
have
access
to
the
file
system.
So
I'm
wondering
if
this
will
be
the
first
case
where
we
have
like
the
ui
is
only
an
electron,
only
feature.
C
Yes,
yeah
plug-in
management
being
able
to
delete
and
add
plug-ins
will
be
electron
only
there's
just
no
way
to
do
it
through
the
through.
What
we
currently
have
is
the
browser
view,
but
long-term
octant
is
going
to
be
an
application
that
is
electron
only
anyway.
So
people
still
using
the
webview
as
a
crutch
will
eventually
have
to
come
to
terms.
B
Absolutely
I
think
it's
my
queen,
that's
great
now
with
the
starboard
vlogging
update.
This
is
exciting,
really.
A
Yeah
sure,
do
you
mind
if
I
share
a
screen
for
this
one
excellent.
A
Boom
sure
screen
all
right
sure
take
the
whole
desktop
all
right.
Does
this
look
visible,
maybe
a
little
larger.
A
A
Better,
okay,
excellent,
okay
cool,
so
this
is
going
to
be
based
on
a
lot
of
the
work
that
daniel
talked
about
last
community
meeting.
So
I'm
not
gonna
go
through
too
much
of
the
details,
just
re-watch
his
video,
if
you're
interested
in,
like
the
motivation
for
a
lot
of
these
changes.
A
But
essentially
a
lot
of
this
is
just
work
to
catch
up
with
a
lot
of
the
additional
work
that
octet
has
put
in
since
the
initial
release-
and
I
suppose
we
just
haven't
been
doing
a
good
job
of
broadcasting
out
some
of
these
quality
of
life
changes,
and
so
some
of
these
existing
plugins
aren't
using
these
changes.
So
I
decided
to
just
take
it
upon
myself
to
implement
them
and
make
a
pr
that
being
said
it
does.
This
is
a
good
exercise
because
it
also
exposed
some
of
the
integration
type
stuff.
A
That
is
a
little
buggy
and
developer
experience
things
on
our
plugin
api,
which
aren't
necessarily
the
best.
So
there
are
some
lessons
to
be
learned
from
this
exercise,
so
I'll
just
go
through
some
of
the
quick
changes.
A
The
first
one
is
that
octant,
for
I
think,
since
the
last
couple
of
releases
that
they're
able
to
use
to
add
add
in
objects
like
plugins
can
change
the
object
status
of
any
object,
meaning
you
have
these
icons
that
go
green
check
mark
for
okay
and
then
it's
got
a
warning,
yellow
and
then
it's
got
a
error
red,
and
so
the
idea
here
is
that
these
say
this
nginx
pod.
A
It's
got
the
starboard
plug-in
already
loaded,
and
I
think
I
already
have
the
scans
pre-run.
So
it's
already
got
the
scans
and
you
can
see
here
that
it
says
it's
got.
35
critical
vulnerabilities,
so
the
expectation
then,
is
the
status
to
be
in
an
airing
state,
and
so
here
we
can
see.
Okay,
now
our
critical
high
vulnerabilities
and
it's
just
set
in
a
way
where
I'm
saying,
if
it
has
any
critical
vulnerabilities,
it'll,
just
be
in
a
narrow
state.
A
So
though
this
logic
can
be
talked
around,
maybe
but
essentially
the
core
id
is
the
mechanism,
that's
there
and
we
can
use
it
moving
on.
There
is
also
the
idea
that
previously
anything
that
was
under
this
audit
reports,
tab
was
just
inside
of
this
summary
page,
which
made
it
look
super
busy
and
somewhat
difficult
to
work
with
so
now.
This
auto
reports
just
gets
its
own
page,
it's
fairly
fairly,
straightforward
move.
A
You
just
grab
the
content
and
just
plop
it
over
a
new
thing,
so
this
single
starboard
plug-in
is
actually
making
this
audit
reports
tab
and
there's
vulnerability
tabs,
and
then
I
have
the
sample
plug-in
app.
That's
just
hanging
out
to
the
extra
pot
details,
and
so
in
this
audit
reports,
tab
we've
changed
a
lot
of
the
existing
work.
A
Where
I
think
like
at
some
at
the
time
that
this
plugin
is
written,
it
used
a
lot
of
markdown
components
as
just
a
hack
to
get
around
things
that
were
possible
with
our
components
at
the
time,
namely
being
like
generation
of
some
of
these
icons.
So
it
turns
out
that
still
wasn't
working
currently
on
0.23,
so
the
the
pr's
are
ready
up
for
this,
but
essentially
what's
happening
is
that
these
are
not
using
a
markdown
component
anymore.
A
These
are
using
text
components
and
it's
setting
the
icons
as
they're
supposed
to
be.
We've
added
some
manual
sorting
to
the
status,
just
an
example
of
how
to
do
it.
There
was
like
a
minor
nitpicker
in
the
demo.
I
don't
know
if
y'all
caught
it.
It
was
very
quick
but
like
I,
I
made
a
mistake
where
I
set
some
css
overprides
globally
and
it
turned
these
white
in
light
mode.
But
now
this
is
fixed,
so
our
pagination
buttons
are
visible
again.
A
So
that's
that
it's
not
too
particularly
exciting,
and
then
also
you
can.
You
can
also
see
there
are
some
rough
edges.
I
wrote
in
the
meeting
notes
like
the
big
one
being
like.
Oh
you,
you
octan
itself
says
the
pod
is
okay,
because
octane
is
looking
for
this
pod
running
and
saying
it's
okay,
but
then
we
also
have
this
additional
status.
So
maybe
the
logical
thing
to
do
is
like
have
like
a
the
highest
error.
State
win
so
like
I
would
no
longer
show
whatever
component
is.
A
This
is
injected
from
the
okay
status,
but
only
things
from
the
critical
status
or
the
error
state.
So
that's
I
mean.
So
that's
kind
of
a
nice
to
have,
and
we
can
kind
of
see,
there's
made
like
something
something
a
bit
more
to
be
desired,
with
the
with
the
signposts
ui
and
being
able
to
match
the
child,
but
not
a
hard
deal
breaker
and
probably
for
the
most
exciting
thing,
at
least
in
my
opinion,
is
let's
say
you
have
the
starboard
thing
set
up.
A
You
install
the
crds,
but
previously
it
was
a
starboard
scan.
So
octane
has
since
then
implemented,
write
capabilities
and
this
concept
called
action.
So
if
you
want
to
actually
start
a
scan,
this
is
and
I'll
actually
start.
So
this
is
a
creating
q
hunter
report.
So
this
is
kind
of
the
same
problem.
I've
had
a
lot
of
other
plugins
where,
if
you
dispatch
a
workload
that
takes
a
non-trivial
amount
of
time
and
by
non-trivia
I
mean,
like
maybe
like
say
like
more
than
10
seconds
and
like
upwards
of
a
minute.
A
What
ends
up
happening
is
that
you
can
have
these
things
pop
up,
but
you're
kind
of
guessing
how
long
it
takes,
and
I'm
I'm
running
this
on
a
desktop
with
a
fairly
beefy
pro
compute
resource.
So
this
took
like
maybe
20
seconds,
but
on
a
larger
cluster.
A
I
could
expect
this
to
take
longer
and
I
just
haven't
quite
figured
out
a
good
ui
to
show
that
it's
still
working
on
it
with
kubernetes
being
declarative
so
like
this
is
actually
just
a
crv
and
so
we're
just
waiting
for
the
crd
to
be
created
to
generate
this
report.
So
I'm
not
sure
about
this
one
like
either
the
crd
does
exist
or
does
not
exist,
or
maybe
there's
certain
hooks
that
we
can
do
to
show
progress
capture
as
it
goes
through.
A
But
for
the
time
being,
I
just
written
this
bit
as
an
example
that
that
you
can
trigger
actions
and
that
you
can
actually
generate
these
reports
natively
from
within
octane
and
sort
of
get
away
from
the
patterns
of.
Oh
here's,
a
command
line
command
to
do
this
particular
thing
you
might
want
to
do
and
so
like
for
something
that
hasn't
run
the
reports.
Yet
you
can
kind
of
see
the
same
pattern
propagate
out
to
this
audit
report
by
using
config
audit
reports
and
also
those
vulnerability
reports.
A
So
this
can
this
pattern
essentially
can
be
reused
and
something
that
might
be
more
interesting
out
of
this
pattern
is
that
maybe
we
should
be
creating
hooks
on
our
like
an
additional
plug-in
api
service,
where
we
can
add
additional
actions
from
plugins
to
just
do
these
things
at
a
glance,
so
I'm
just
gonna
scan
using
conf.
You
know
just
can't
stand
using
that
config
audit
or
scan
using
cubehunter
or
whatever,
whatever
trivia,
whatever
tool
it
might
be
to
do
it
so
that's
kind
of
it.
I
will.
A
I
have
this
code
locally,
I'll,
probably
push
it
up
to
a
for
I'll
push
up
this
branch
today
to
a
maya
fork,
but
I
won't
actually
pr
this
code
until
0.2
for
comes
out
since
it
won't
quite
look
this
way
yet
on
0.23.
A
So
that's
about
it.
Any
questions,
comments
or
anything
else
that.
D
C
D
B
B
Okay,
I
brought
up
this
here
just
to
check
real,
quick.
The
current
progress
on
the
upcoming
dot
24
release.
So
I
don't
know
if
wayne
or
someone
else
would
like
to
sure
briefly
about
this.
C
C
Some
of
the
things
that
we
were
hoping
to
get
done
for
this
release
are
going
to
be
pushed
out
to
the
as
a
follow-up
release,
and
that's
mainly
some
of
the
ui
around
managing
plugins,
and
there
was
a
couple
other
things
that
we,
oh,
the
documentation,
we're
gonna
do
that
as
a
focused
sprint
to
kind
of
revamp
all
of
our
all
of
our
docs.
C
So
the
I
think
the
there's
there's
one
outstanding
issue
that
I
that
we
might
do
a
short
we
have
to
discuss
it
as
a
team
and
figure
it
out.
My
my
opinion
is
is
that
there
are
two
issues
in
our
to-do
list.
One
is
there's
a
panic
with
the
the
yaml
viewer
and
that
I
think,
should
be
fixed
as
part
of
a
release,
and
there
is
a
there's
another
one
in
the
list.
Oh
where's,
that.
C
Yeah
2798
is
the
panic
and
then
there
was
there's
another
one.
Maybe
I
didn't
add
it
to
0.24.
C
Sorry,
I'm
trying
to
find
it
yeah,
so
I
think
anyway,
the
the
release
itself
we're
in
a
good
we're
in
a
good
spot.
We
have
some
prs
in
flight
today
that
are
kind
of
the
the
major
outstanding
body
of
work.
So
there's
a
better
logging
from
luis.
C
There
is
custom
icons
from
felipe
there's,
some
documentation
updates
from
sam,
and
there
is
the
plugin
management
or
the
the
plug-in
reloading
for
go
plug-ins
that
I
just
demoed
that
are
that
are
all
in
review
and
eminent
there's,
also
a
whole
host
of
of
small
fixes
and
and
paper
cuts
that
that
sam
addressed,
so
you
just
demoed
from
the
starboard,
as
as
the
as
the
platform
for
demoing
those.
So.
C
Yeah
we're
I
mean
we're
in
a
good
we're
in
a
good
spot.
Will
we
cut
it
today
is
probably
a
better
question.
Potentially
I
I
think
I
think,
depending
on
how
the
reviews
go
and
and
what
shakes
out
there,
we
we'd
be
looking
at
a
at
a
at
a
late
like
afternoon,
pacific
time
evening,
eastern
time,
release
or
potentially
tomorrow,
for
for
actually
we
might
get
the
assets
together
this
evening
and
then
publish
them
tomorrow,
but
yeah.
I
think
we're
in
a
good
spot.
B
B
Well,
I
don't
know
if
another
comment,
the
discussion
point
I
just
wanted
to
share
briefly
with
the
community,
because
I
found
some
users
out
there
also
kind
users.
D
B
You
know
without
using
plugin,
because
well
you
actually
connect
okay,
there's
a
kind
plug-in
with
some
base
features
right
now,
for
those
of
you
who
are
probably
not
aware,
pine
is
a
nice
project
that
allows
you
to
run
kubernetes
cluster,
where
the
nodes
are
not
vms
but
actual
docker
containers,
so
that's
kubernetes
in
docker,
so
the
the
kind
plugin
well
I've
been
using
it
using
it
for
a
while,
and
it's
interesting
because.
B
Can
do
it
from
the
time
command
line,
but
it
tonight
to
have
all
these
step-by-step
process
here
I
don't
know
the
number
of
workers
which
are
basically
containers.
The
version
is
important
and
then
all
the
networking
details-
and
you
know
the
api
server
address-
there
are
some
considerations
for
that
in
the
in
the
kind
documentation
fill
in
these
fields,
and
there
are
so
the
the
probably
yeah
the
feature
gates,
which
are
basically
features
that
you
can
turn
on
or
off
and
the
coordinate
is
cluster.
B
You
can
do
it
right
from
the
cluster
creation
here,
that's
the
current
status
of
the
login.
There
are
some.
You
know
nice
to
have
features
that
there
is
that,
I
believe
was
sam,
oh,
what
it
here
and
according
to
what
you
were
mentioning
it's
similar
than
what
we
see
in
other
plug-ins
up
here.
B
We
see
get
a
new
cluster,
there's
no
clear
way
to
find
what's
happening
during
the
process
right
besides
context
change,
so
for
for
those
of
you
kind
users
out
there
considering
using
the
often
plugin
for
kind-
and
you
know
let
us
know
your
your
thoughts,
picture
requests
and
of
course,
prs
are.
Welcome.
A
Oh
yeah,
I
have
a
few
words
about
the
kind
plug
in
itself
so
like
it
was
originally
created
to
help
out
with
the
ephemeral
container
work
on
octane
like
it
was
like.
I
haven't
really
like
my
scope
of
this
workflow
is
very
limited,
and
so
I'm
definitely
interested
in
hearing
like
what
specific
things
people
are
using
kind
for
that
might
be
trickier
than
just
oh
kind,
create
cluster
right
so
like,
for
example,
like
we
see
like
that
whole
networking
section
like.
Why
are
people
making
these
configuration
changes?
A
What
use
cases
are
those
that
is
something
that
I'd
prefer
to
have
better
knowledge
of
before
implementing
more
features
in
the
future.