►
From YouTube: Octant Community Meeting - Feb 5, 2020
Description
February 5, 2020
Agenda
0.10.1 released
bug fixes
Update to Angular 9 blocked by next Clarity release
Move to Github Actions WIP see #627
Plugin Epic (Polychrome) #613
Electron Epic (Denali) #550
[jonas] Plugins page on octant.dev will be created shortly
A
Hello,
welcome
to
the
February
5th
octant
community
meeting
welcome
everybody.
We
are
got
some
good
stuff
on
the
agenda
today.
We're
gonna
be
talking
about
some
bug,
fixes
all
I'd,
say:
I'm
talked
about
some
of
the
action
stuff
that
we
recently
worked
on
and
will
give
these
folks
some
updates
on
or
moved
to,
angular
9
and
some
movement
on
the
electron,
app
side
of
things,
as
well
as
some
movement
on
the
plug-in
side
of
things.
So
first
I
will
just
start
with
the
Godot
10.1
release.
A
A
There
were
some
issues
where
the
API
would
be
kind
of
spammed
if
you
lost
credentials
and
things
like
that,
so
we
got
that
in
there
we
also
fixed
some
type
of
thank
you
to
I.
Don't
know
how
to
say
that
github
username,
but
thank
you
to
that
person
who
fixed
the
typo
on
our
go
module
that
was
causing
the
go
install
of
our
build
script
to
network,
so
that's
very
appreciated
and
then
just
some
other
minor.
Some
minor
fixes
that
y'all
can
see
in
the
list
there.
A
So
some
race
condition
stuff
fixed
up
by
CM
and
brian
addressed
some
of
the
issues
around
reload
and
cube
configs
when
there's
changes.
So
that
was
a
pretty
successful
bug
fix
release.
I,
don't
think
we'll
do
another
bug
fix
release
in
about
ten
unless
something
crazy
turns
up,
but
it's
likely
that
we
won't
have
another
one
until
about
11,
but
that's
a
good
time
to
remind
folks
that
we
do
have
nightly
builds
that
get
generated,
so
you
can
always
check
out.
A
What's
currently
in
the
repo,
let's
see
the
angular
9
stuff,
so
yeah
we
were
angular.
9
is
in
the
late
released,
Canada
I
believe
we
talked
about
the
civil
s,
communicating
so
part
of
there's
a
there's,
a
whole
process
in
place
for
octant
to
be
being
migrated
over
to
be
running
inside
electron.
There's
also,
some
integration
of
the
Monaco
editor
into
octant
happening.
It
will
replace
the
existing
yam
will
read.
Only
of
you
know
the
the
current
most
up-to-date
version
of
the
Monaco
editor
wants.
A
Typescript
3.7,
plus
angular
8
does
not
work
with
typescript
3.7,
so
we
were
looking
at
upgrading
to
angular
9.
We've
ran
into
some
issues
with,
so
the
the
front-end
framework
that
we
use
for
styling
is
the
clarity
framework.
It's
not
quite
that
they
have
an
open
issue
and
they
are
working
towards
getting
ready
for
the
angular
9
release,
but
clarity
does
not
fully
support
angular
9.
A
Yet
so
we
are
waiting
for
the
next
clarity
release
to
then
continue
our
efforts
to
upgrade
to
angular
9,
which
will
then
unblock
us
to
get
the
latest
Monaco
editor
in
place,
and
so
that's
that's
kind
of
where
that's
all
that
it's
just
some
some
dependencies
blocking
some
things
that
were
that
we
wanted
to
take
care
of
some
nothing.
It's
just.
It
has
afforded
us
the
time
to
move
on
to
some
other
things
which
we'll
talk
about
after
I.
Let
see
him
talk
about
the
work
that
was
done
with
github
actions.
B
Sure
so
we're
finally
moving
to
github
actions,
and
this
one
is
going
to
be
pretty
big
because
for
a
while,
our
CI
pipeline
has
been
split.
It
use
something
called
drone
which
is
a
container
native
CI,
and
then
we
also
use
circle
CI,
because
we
have
a
separate
pipeline
for
end-to-end
testing
that
requires
setting
up
a
cluster
in
CI
and
long
story
short.
B
If
you
want
to
set
up
a
kind
cluster
in
something
it
can
set,
a
container
you'd
have
to
expose
the
docker
host
and
for
a
lot
of
these
free
AI
services,
they
just
don't
let
you
do
that
so
we're
fairly
limited
in
our
choices
for
CI
pipelines,
but
hopefully
get
up.
Actions
help
alleviate
some
of
this.
And
if
you
actually
take
a
look
inside
our
old
drone
configuration,
we
have
a
lot
of
stuff.
That's
just
packaged
in
parallel.
B
That
could
be
just
split
out
into
your
own
pipelines,
stuff,
like
linting
stuff,
like
checking
out
auto-generated
code
and
making
sure
those
are
okay.
So
we're
going
to
remove
those
as
a
separate
pipeline
and
we
don't
have
to
worry
about
it
in
our
build
and
release
process
and
hopefully
not
have
exceedingly
long
CI
pipeline
runtimes
that,
if
you're
trying
to
get
feedback
on
very
quickly,
it
doesn't
become
really
frustrating
and-
and
lastly,
we're
also
going
to
get
back
caching
for
our
CI
pipelines.
B
This
is
more
of
a
VMware
thing,
but
because
all
of
our
open
source
projects
they
share
the
same
sort
of
build
credits
like,
for
example,
circle
CI.
It
turns
out
that
we
exceed
our
usage
quota
for
having
our
container
caches.
So
as
a
result,
none
other
projects
can
actually
cache
their
containers
right
now,
and
so
what
we'll
do?
What
we'll
actually
get
back
with
our
move?
To
get
up
actions
is
to
be
able
to
get
that
caching
mechanism
and
hopefully
speed
up
a
lot
more
of
these
container
download
times
and
hopefully
just
get.
B
These
builds
less
than
two
minutes,
for
you
know
from
basically
tests
to
build
time,
so
we're
pretty
much
down
to
rebuilding
our
release
pipeline.
So
hopefully
we
can
get
that
online
by
the
end
of
the
and
go
through
the
test
run.
You
might
get
a
ping
for
say:
hey
we're,
gonna,
try
out
a
test
release
so
get
pinged
on
that.
No,
it
likely
would
just
be
a
draft
at
least,
but
we
won't
be
releasing
a
binary
for
real
to
test
this
out.
All
right.
That's
it.
A
In
exam,
so
the
next
thing
up
is:
we've
created
a
plugin
epic
with
and
we've,
given
it
the
project
name
polychrome.
This
is
an
epic
that
is
going
to
be
tracking
our
progress
towards
getting
the
plug-in
system
to
version
one.
So
this
kind
of
contains
all
of
the
pre-existing
issues
that
have
been
created
around
plugins
feature
request,
bugs
documentation,
issues,
things
like
that,
and
we're
going
to
start
working
through
a
lot
of
these
in
this.
A
Some
of
those
already
I
think
believe
the
logs
component,
and
there
was
another
one
I
think
it
was
annotations,
are
you
know
before
they
were
not
usable
within
the
plugins
and
and
that's
been
updated
and
fixed,
so
we're
we're
kind
of
working
on
making
the
interfaces
that
are
exposed
to
plugins
consistent
making
any
changes
area
that
we
need
to
to
ensure
that
we're
wrapping,
not
exposing
public
properties
but
wrapping
things
with
interface
methods.
So
that
way,
we're
not.
We
no
longer
have
to
break
the
API
that
you're
using
when
you're
writing
plugins.
A
The
only
thing
you
need
to
do
is
just
get
the
public
package
of
for
octant,
plugins
and
and
that
you
don't
need
all
of
the
internal
and
all
of
the
private
things
so
yeah.
So
if
you're
interested
in
plugins
that
this
is
the
epic
it's
613
and
github,
please
check
it
out.
If
you
see
something
on
there
or
if
you
don't
see
something
on
there
add
an
issue.
A
Is
more
of
like
an
epoch
to
track
it
probably
over
the
next
cut?
Most
of
the
issues
here
will
probably
end
up
in
the
next
release,
but
this
this
will
be
a
long-standing
epic
to
kind
of
track
it
until
we
hit
like
until
we
actually
say
we're,
versioning
the
plug-in
system
right
now.
This
is
this
is
v1.
This
epoch
is
going
to
be
used
to
track.
All
of
that
ok
sounds
good,
and
so
are
there
any
questions
on
that
hi.
D
A
It's
basically
just
to
give
it
some
character,
and
you
know,
give
us
something
to
reference
when
we're
writing
up
documentation
when
we
want
to
be
referring
to
like
the
grand
scheme
of
things,
instead
of
always
having
to
specifically
call
out
the
the
detail
of
a
project,
we
could
just
refer
to
these
code
names.
Okay,
thank
you
all
so.
Yeah
I
believe
you're,
the
one
who
submitted
the
fix
for
the
go
module,
update,
yeah.
C
And
I
got
one
more
question,
so
one
of
the
things
that
we
want
to
do
for
octant
is
to
build
out
a
plugins
page
on
octant
undead,
but
right
now
we
have
the
topic,
often
plugins
or
octan
plugin
rather,
and
we
want
to
create
a
nice
plugin
page.
Do
you
want
to
hold
off
on
that
until
this
work
is
done
or
I
mean
we
already
have
a
few
existing
plugins
that
you
have
created
and
the
community
members
have
created?
I
can
just
list
those
for
now.
Yeah.
A
I
think
I
think
listing
those
plugins
is
perfectly
fine.
The
yeah
I
think
that's
a
good.
That's
a
good
first
step,
I
think
likely
we'll
probably
end
up
with
some
type
of
more
official
process
for
plugins
and
and
where
they,
you
know
how
they
get
listed
and
all
of
that.
But
for
now,
if
we
just
want
to
manually
list
out
the
ones
that
we
know
about,
and
then
people
can
open
issues
if
they,
if
they
desire
that
their
plugin
get
listed.
There.
A
All
right
in
a
similar
kind
of
similar
topic,
they're
done,
but
the
project
anomaly,
which
is
converting
octant
to
an
application.
That
is
the
work
to
get
the
the
main
container
for
octants
to
no
longer
be
a
web
browser
and
to
be
well
to
be
electron,
which
is
a
custom
chrome
of
of
a
web
browser.
So
Bryan
has
started
some
of
the
initial
work
on
that.
A
lot
of
it
was
just
reorganizing.
Our
angular
imports
moving
modules
around.
A
So
when
you
see
some
of
these
PRS
coming
across
that
are
just
kind
of
shuffling
files
and
and
making
some
updates
the
that
work
is
just
kind
of
to
lay
the
foundation
for
the
move
to
an
electron
app.
Currently
we
have
pyaare
up,
which
is
it's
about
to
get
merged,
which
is
the
electron
apps
tub
we
and
we
may
have
merged.
Yes,
we
actually
it
is
merged.
A
It
is
currently
all
of
the
it's
basically
just
the
existing
octant
functionality,
wrapped
in
electron,
we
haven't
started
the
process
of
really
going
through
and
modifying
any
of
the
UI
or
components
yet
to
be
more
to
take
advantage
of
what
we
can
do
with
electron
so,
and
that
includes
like
some
changes
to
navigation
and
status,
bars
and
and
adding
menus,
and
things
like
that.
So
right
now,
this
is
just
a
frame
both
of
these
projects
coexists,
so
they
they.
A
They
live
in
the
repo
side
by
side,
and
they
can
be
worked
on
independently
that,
and
that
is
due
to
the
the
moving
files
around
work.
That
Brian
did
so
as
we
as
we
continue
to
progress
on
this.
The
that
epic,
that
I
mentioned
I,
believe
it
was
five
550
that
one
will
continue
to
stay
around,
and
so
we
have
fully
moved
octant
over
to
the
electron
container.
A.
E
C
E
A
A
So
so
we
will
be
able
to
in
the
case
where
there
is
no
coop
config
actually
be
able
to
provide
the
option
to
just
upload,
one
which
you
can
technically
do
now
in
a
browser,
but
it
is
not
of
as
nice
of
experience,
especially
when
you
get
into
pads
that
involve
shared
file
systems
mounted
across
networks,
and
things
like
that.
The
browser
really
can
sometimes
have
a
hard
time
with
file
names
and
file
paths
and
uploading.
Those
correctly
so
anyway
yeah
same
way.
It
works
now,
nothing
nothing.
There
will
change.
Okay,.
A
So
the
intention
is
to
run
octant
as
an
application.
Some
some
folks
do
run
octant
as
an
application
in
a
container
and
then
and
then
forward
via,
like
X
forwarding
or
something
like
that.
But
right
now
it
is.
It
is
a
browser-based
application.
So
there
is
a
there's.
Some
there
is.
A
lot
of
folks
are
interested
in
maybe
running
it
as
a
server-side
thing,
but
it
is
not
designed
to
be
server-side
the
way
we've
the
way
we
collect
information
from
the
API
and
the
way
we've
setup
it
to
work
with
your
cue
config.
A
D
It
will
act
as
an
edge
for
the
the
end
user
to
connect
to
it
and
you
can
have
multiple
users
connect
to
the
same
octant
application
instead
of
I
had
to
install
one
application
hitting
the
cluster
or,
like
my
colleague,
who
is
quite
a
connect
to
the
same
cluster,
would
connect
from
his
desktop
client
to
the
cluster.
Still
be
multiple
network
calls
involved
right,
I'm,
trying
to
understand
the
design
behind
this
approach.
Yeah.
A
So
the
intent
is
that
the
octant
is
a
simple
application
that
works
with
your
local
cube
config.
So
it
has
the
exact
same
permissions
that
you
have
via
your
your
cube
config.
If
you
deploy
octan
into
the
cluster
in
that
method,
everyone
who
connects
to
it
has
the
exact
same
permissions
as
whatever
that
global
cube.
Config
is
so
since
it
since
it
functions
in
that
way.
There's
not
much
difference
between
and
the
way
octant
works
with
informers.
A
It
uses
informer
cache
to
load
data.
So
if
you
have
multiple
clients
of
octants
all
using
the
same
cube,
config
talking
to
Cooper
nettie
server,
they're
all
going
to
be
hitting
the
same
Informer
cache
when
they're
loading
the
data
so
so
they're
the
the
amount
of
overhead
really
is
just
what
it's
sending
back
to
the
clients
and
those
clients.
Are
you
still
have
to
send
the
data
back
to
the
clients
so
yeah?
It
doesn't.
A
A
So
the
the
recommendation
that
we
have
for
folks
who
want
to
run
it
in
a
way
that
is
where
it's
easily
distributed,
is
to
just
have
folks,
just
like
any
other
dev
tool,
have
folks
install
it
locally
and
then
share
a
cute
config
via
one
pass
or
LastPass,
or
some
type
of
secure
file
sharing
tool.
The
same
way
that
a
lot
of
people
share
configurations
and
just
share
the
cute
config
that
you
desire
to
connect
to
octant
with
all
of
the
folks
who
who
need
it.
D
A
D
Okay,
so
how
maybe
I'm
expect
re
into
for
one
more
questions
are
here
notes
right?
How
is
this
different
from
what
there
are
some
other
products
or
enterprise
offerings
like
tons
of
Mission
Control?
It
has
some
management
view
right,
and
then
this
octant
and
I'm
trying
to
get
the
difference
between
often
being
the
management
platform
anton
zoom,
isn't
ntral,
also
being
the
management
platform
so
I'm.
What
is
the
difference
between
these
two
products,
which
looks
similar
to
me
from
the.
A
End-User
right
yeah,
so
octant,
isn't
really
a
man
platform
and
I
think
that's
that's.
The
main
difference
octant
is
is
is,
is
a
primarily
a
developer,
focused
tool
to
help
kind
of
give
you
some
insight
into
what's
happening
with
your
workloads
in
your
cluster
as
as
a
developer.
Who
is
changing
things
and
working
on
things
and
trying
to
understand
how
all
these
things
are
connected?
It
also
again
in
its
nature,
it
just
runs
on
a
desktop
right,
it
doesn't
run
in
cluster
and
it
doesn't,
it
doesn't
have
any
type
of.
A
D
A
Focused
know
you,
so
you
can
use
it
to
connect
to
your
production
cluster,
but
but
we
are,
we
are
current.
Our
current
focus
is
is
really
on
on
getting
developers
and
operators
the
ability
to
see
what's
happening
in
their
clusters
and
understand
how
all
of
their
workloads
and
services
are
functioning
using
it
on
a
production.
Cluster
is
something
that
people
do.
There's
no
danger
in
that.
It's
not
it's,
not
it's
not
only
for
for
dev
clusters
in
that
way,
but
a
lot
of
the
area
of
focus
right
now.
A
C
F
A
B
B
E
I
think
why
don't
I?
We
were
going
to
chat
after
this
so
and
if
it's
kind
of
what's
gonna
hold
you
guys
up
me
working
on
this
I
thought
it
was
going
to
be
an
easy
change
and
it's
is,
it
may
be
out
of
my.
It
may
not
be
under
my
fingertips
to
do
it
immediately.
So
if
it's
gonna
hold
you
guys
up,
you
can
move
me
on
for
that
and
take
care
of
it
and
I
can
try
to
find
some
other
Bo
Frank
hanging
fruit
to
attack
as
well.
I.
A
Don't
think
it's
holding
us
up
at
all,
we
and
we
just.
We
just
want
to
make
sure
that
you
don't
feel
so
stuck
that
your
debt,
you
you're
just
gonna
like
but
I,
can't
do
it,
because
I
I
think
we
can
between
Sam
and
I.
We
can
definitely
help
you
through
it,
because
yeah
getting
stuff
and
like
initially
kind
of
getting
your
mind
into
octants
and
all
of
the
corners
and
how
it
works
is,
can
be
a
can
be
a
long
process.
So
you
shouldn't
feel
bad
at
all.
E
Thank
you
I.
It's
also
the
added
combination
of
that
I'm
new
to
the
team
that
I'm
on
I'm
fairly
new
to
kubernetes,
and
it's
you
know
it.
It's
a
it's
a
it's
just
a
culmination
of
a
lot
of
things
and
I'm,
not
I'm,
not
where
I
want
to
be
at
the
moment
with
it,
and
hopefully,
I
can
learn
enough
to
actually
get
moving
forward
on
yeah.
A
G
A
G
A
H
Anything
no
I,
I,
don't
have
anything
I,
just
wanna
say
thank
you
all
for
for
turning
very
quickly
there
0.10,
but
one
release.
So
I
was
a
great
execution
on
our
end
and
materially
impacts,
one
of
our
customers
gpmc.
So
that's
that's
good,
but
those
so
materially
impacts
more
than
a
few
folks
in
the
community
which
reacted
to
those.
So
thank
you
for
the
quick
turnaround.
Thank
you
for
being
diligent
and
doing
all
the
work.
I
don't
have
anything
specific
on
today.