►
From YouTube: Octant Community Meeting - July 1, 2020
Description
July 1, 2020
Agenda
Dependabot added!
Experimental Typescript Plugin
Component documentation live on https://reference.octant.dev/
Open Q&A - add your questions here
Should Octant save an uploaded kubeconfig?
Yes. We will figure out details of what that looks like. Sam to write doc.
A
All
right,
hello
and
welcome
everybody
to
the
July
first
octant
community
meeting
today
we're
going
to
go
through
so
a
few
quick
things
on
the
agenda
and
I'm
also
going
to
show
some
experimental
stuff
that
I've
been
working
on
around
plugins
after
we
talked
last
week,
I
spent
the
weekend
messing
around
with
stuff.
So
first,
let
me
share
my
screen
and
we
will
get
into
you.
A
A
I,
don't
know
if
there's
really
anything
else
to
add
to,
then
we
haven't
enabled
it
for
the
front
end.
Yet
we
we
plan
to
be
doing
that
I
think
the
goal
there
is
to
do
a
manual
Rev
of
all
of
our
current
fronted
dependencies
then
turn
on
depend
a
bot
so
that
they're
kind
of
all
already
at
the
latest
and
probably
move
it
into
like
a
weekly
cadence.
A
So,
yes,
that
is
all
that's
all
happening
now.
So
that's
good!
The
next
thing
is
or
did
anyone
anyone
I
know
Scott
and
Sam
did
the
work
to
set
up
that
depend
about
stuff,
so
they
might
have
had
something
to
add
No,
okay.
So
the
next
thing
on
the
agenda
is.
This
is
workaround
that
Sam
has
been
doing,
which
is
the
upload
of
a
cute
config,
and
one
of
the
questions
that
was
posed
is:
should
octant
save
the
cube
config
somewhere
after
it's
uploaded,
and
if
so,
what
should
that
look
like
so
Sam?
B
Think
that
challenge
here
really
is:
what
is
the
user
expectation
going
to
be,
because
I
would
also
make
an
assumption
that,
if
they're
deploying
in
cluster
I'd
have
it
I'd
have
that
expectation
that
the
cube
config
would
already
be
set
up
like
they
wouldn't
be
uploading?
A
cute
config
in
real
time
into
an
instance
of
occupant,
that's
deployed
in
cluster
and,
moreover,
we
probably
want
to
set.
B
A
way
so
then,
once
a
queue
pick
has
been
established,
we
can't
upload
another
one
to
overwrite
it
and
so
I
think
it's
probably
a
little
too
early
to
jump
into
things
like
naming
conventions
and
whether
it
should
save
like.
So
maybe
we
should
probably
start
discussing
on
what
this
would
look
like
for
the
case
of
an
application.
In
other
words,
if
baktun
was
running
as
an
electron.
C
B
B
A
I
think
so,
yeah,
and
and
as
for
like
I,
mean
I,
know,
I.
Think
it's
okay
to
get
into
conventions
a
little
bit
I
think
achtung
could
just
right
cute
config
to
the
standard,
folder
and
tag
it
with.
You
know
shocked
in
the
similar
way
that
other,
like
plugins,
do
and
other
tools
do
when
they
create
their
cube.
Configs.
They
they
just
prefix
them
or
append
them
with
with
who
made
it
octa
could
could
do
that.
The
other
thing
is:
is.
B
Okay,
well,
there
are
a
yeah,
so
if
we
establish
that
we
for
an
Electra,
not
we
do
need
to
save
it
somewhere,
we
can
probably
I
can
write
up
a
doc
that
or
just
a
few
cases
like
what,
if
they
would
have
opted
in
a
regenerated
to
keep
config
and
then
all
of
a
sudden
say
doctor
can't
find
to
keep
config
again
what
happens
and
then
yeah.
So
I
think
there
are
some
general
there
yeah.
So
guess.
A
Establishment
patterns
that
we
have
like
right
now,
it's
we
still
have
all
of
the
global
session
global
queue,
config
everything's,
everything's
passed
around
and
one
big
config
object.
All
of
that's
gonna
have
to
get
extract
it
out.
We're
gonna
have
to
create
interfaces
around
that
we're
gonna
have
to
we're
probable.
I
mean
I.
Imagine
that
what
will
likely
happen
is
that
we
will
have
to
like
paths
inbound
in
to
octant
one
for
when
you're
running
it
locally
and
one
for
ruins
running
in
cluster,
and
those
things
will
just
be
different.
B
No
I
was
just
saying
the
whole
pass
remind
me
about
like
how
I
think
the
lens,
apparently
at
one
point
they
had
a
set.
They,
they
have
a
version
that
runs
in
cluster,
but
they
were
two
different
projects.
They
called
it
something
else.
They
were
two
different
code
bases
and
I.
Don't
know
if
this
is
something
that
we
even
want.
You
entertain
I
mean.
A
That's
that's.
That's
one
of
the
conversations
that
Brian
I've
been
having
is
is
octant
and
cluster
is
still
octant
right.
What
like
what
is
like
cuz,
because
the
idea
behind
octant
is
this,
this
very
fast
local
dev
tool
that
can
use
informers
and
and
and
fill
a
bunch
of
memory
with
all
of
this
information.
C
B
C
C
C
A
Don't
think
so,
that's
a
that's
a
pretty
standard.
The
reason
I
mean
the
reason
that
stare
is
because
it's
it's
the
standard
practice
for
most
CLI
tools
and
tools
that
interact
with
kubernetes.
They
respect
the
coop
config
environment
variable
as
well
as
being
able
to
pass
in
cute
config,
so
I,
don't
I
think
we
would
still
treat
that
in
the
same
way.
We
do
now
sounds
good.
A
A
Milan
did
so.
Sam
did
a
bunch
of
the
initial
groundwork
for
this
and
then
and
then
Milan
and
Sam
did
a
lot
of
the
porting
over
to
storybook,
and
then
Milan
did
all
of
the
finalization
and
adding
code
examples,
and
generally
just
just
adding
all
the
the
docs
and
stuff
like
that
for
this.
So
it
was
a
lot
of
work.
Bye-Bye
Salem
alarm
to
get
this
in
place,
but
it
is
a
very
useful
tool
for
not
only
for
developing
octave
views
but
just
plug
there's
as
well.
We've
been
talking
about
it
for
the
last.
A
This
is
the
go
code
that
you
would
use.
There's
there's
a
color
scheme.
Here's
the
color
scheme
is
weird,
so
it
looks
like
there's
things
missing
and
stuff,
but
so
the
nice
thing
about
this
is,
if
you
were
writing,
doing
things
in
go.
You
could
come
in
here
and
you
copy
this
block
out
and
paste
that
in
and
and
see
the
results
of
that
and
then
on.
The
canvas
itself,
which
we've
shown
before
is
a
little
syntax
area.
That's
fine!
Let's
skip
that!
A
One
go
to
the
you
can
go
over
to
the
knobs
and
and
and
make
changes,
and
they
should
render
in
real
time
on
the
screen.
Like
that,
I
see
a
came,
see
and
I
could
add
it.
I
think
I
could
just
add
another
another
point
in
here.
If
I
could
type
correctly
that
work
like
that,
maybe
oh
yeah
I,
don't
know
how
to
use
this
graph.
Is
it's
fine
these?
These
are
all
the
same
components
that
we
support.
Nokton.
We
even
are
able
to
get
some
of
the
things
like
the
editor
component
loading
up.
A
So
we
encourage
everyone
to
look
at
this
and
take
advantage
of
it.
Report
bugs
that
you
find
report
usability
issues
that
you
find
the
goal
here
is
to
kind
of
make
storybook
to
the
comprehensive
documentation
source
for
octant,
both
for
all
for
all
of
our
components
and
and
all
of
the
eventually
all
of
the
plug-in
development
documentation.
Everything
will
happen
right
through
storybook,
so
thank
you,
Sam
Ilan,
for
all
your
hard
work
on
that.
It's
really
it's!
It's
really
awesome.
A
A
A
A
We
are
looking
at
solutions
for
that
kind
of
solve
all
of
those
problems,
but
still
enable
people
to
write
plugins
easily
and
quickly,
and
one
of
the
things
we
are
currently
experimenting
with
is
a
typescript
loader
for
plugins
and
I
just
want
to
show
that
real
quick,
because
it
is
it's
something
that
I
think
will
get
people's
brains
going
about
potential.
So
if
we
I
pull
up
octants,
let's
see,
let
me
do.
A
A
A
But
it's
able
to
connect
to
and
and
call
the
same
internal
services
and
client
calls,
and
things
like
that
that
plugins
do
now.
The
benefit
here
is
that
it
takes
away
the
current
problem
that
some
folks
have
brought
up
to
us
about
needing
to
recompile
a
binary
for
every
single
platform.
It
also
fixes
the
problem
of
plugins
needing
octant
needing
to
be
stopped
and
the
plug-in
needing
to
be
stopped,
and
then
a
new
binary
put
in
place
and
then
octant
restarted
to
get
plug-in
changes
to
present
themselves.
A
So
the
development
pattern
for
doing
that
is
not
very
nice.
You
have
like
it's
a
lot
of
control,
see
it's
a
lot
of
killing
out
of
things
and
then
and
then,
even
if
you
have
set
up
some
type
of
filesystemwatcher
to
stop
and
reload
things
for
you.
If
your
plugin
throws
an
error
because
it's
a
actual
like
spawned
process-
and
it's
not
cleaned
up
properly,
it
can
be
out
there
running,
holding
on
to
memory
holding
on
to
ports
and
I've.
A
The
nice
thing
about
this
is,
you
can
also
so
it's
not
just
limited
to
the
predefined
components.
So
if
we
extend
our
capability-
and
we
say
we
want
to
be
able
to
support
the
status
of
this
plug-in
right-
we
can
save
that
now
we
see
that
status
is
is
available
to
us
and
we
could
go
back
to
our
to
our
pod
and
there's
no
status
entry,
because
we
haven't
added
that
section
to
the
handler
yet,
but
we
can
create
a
new
section,
add
in
status,
naked
status.
A
Currently
there's
no
component
implementations,
so
what
I've
been
doing
is
I've
actually
been
using
our
our
storybook
page
to
go
in
and
grab
out
the
Jason
examples
and
then
paste
them
in
where,
where
you
would
expect
to
actually
have
a
component
library
available
to
you.
But
this
will
truly.
This
will
work
for
all
of
the
printer
printer
configurations
as
well
as
adding
in
cabs.
A
It
doesn't
do
modules
yet
and
it
doesn't
have
the
ability
to
well.
The
reason
it
doesn't
do
modules
is
because
it
doesn't
do
flexbox,
but
all
of
that
is
currently
getting
added
to
this
experimental
branch
that
I
just
been
hacking
on
on
the
weekends
and
will
we
release
it
as
under
a
feature
flag
or
as
part
of
just
alongside
existing
plugins
we're
not
going
to
change
or
remove
existing
plugins
for
in,
like
anytime,
soon
we're
just
we're
just
getting
people
prepared
and
trying
to
get
ideas
out
and
in
place.
A
So
I
just
wanted
to
show
this
I
had
shown
the
team
earlier
in
the
week
a
different
example:
this
one's
a
little
more
refined
the
the
convention
here
for
the
typescript
would
be
to
export
default
a
class.
The
class
implements
this
octant
plug-in
interface
and
by
implementing
that
interface,
you
now
the
typescript
library
will
type
check
for
you.
A
So
if
you
are,
if
you're,
not
in
compliance,
you
kind
of
you
know
already
that
your
JavaScript
probably
won't
run
correctly,
and
then
the
other
benefit
is
that,
when
were
when
we're
transpiling
this
from
typescript
to
es5,
we
use
that
same
octant
typescript
file
to
check
it
in
the
octant
side
of
things,
so
that
we
can
actually
report
back
to
you
the
line
where
the
error
happened.
So
you
know
if
there
was
some
error
here
on
on
like
this,
my
18
right,
we
would
actually
be
able
to
say
like
bad
line.
A
18
of
your
plug-in
is
bad
and
then
one
other
thing
that
the
reason
I
have
these
lines
down
here
is
because
traditionally,
logging
in
plugins
is
a
was
awful
and
getting
it
to
work.
Right
was
a
matter
of
making
sure
you
had
like
the
correct
incantation
of
of
some
crazy
logging
things.
So
what
I
wanted
to
show
was
that
we,
you
can
see
this.
A
A
A
A
One
of
the
one
of
the
caveats
on
this
is
that
for
it
like,
if
you
want
to
use
something
like
rxjs
or
you
wanted
to
use
something
like
grab
the
kubernetes,
j/s,
client
library
and
use
that
you
would
have
to
use
something
like
roll-up
or
web
pack
to
to
combine
all
of
those
files
into
a
single
JS
file
before
octant
could
run
it.
The
reason
is,
is
because
well,
the
reason
is
because
we
don't
want
to
have
to
deal
with
your
JavaScript
node
modules
and
p.m.
A
set
like
like
you,
give
us
es5
JavaScript
or
you
give
us
a
typescript
file
that
implements
our
interface
and
we'll
run
it,
but
we
don't
want
to
be
in
the
in
the
business
of
packaging
up
some
crazy,
get
repo
full
of
JavaScript
so
which
I
think
I
think
is
reasonable.
I
think
it's
reasonable
to
say
that
if
you
want
to
use
extra
packages
you
have
to
web
pack
or
roll-up
and
and
I
have
created.
I've
already
has
some
some
rough
documentation
about
like
what
web
pack
settings
and
want
roll-up
settings.
A
A
Okay,
look.
Thank
you.
Everyone,
oh
I,
will
say
this
for
folks
who
I
know
we
get
some
people
who
watch
it
later.
The
this
week,
most
of
the
oxen
team
is
gone
later
in
the
week.
So,
if
you're
on
slack
looking
for
us
and
need
help
with
stuff
that
might
be
spotty
coverage,
just
a
heads
up
well,
thank
you.
Everybody.