►
From YouTube: Octant Community Meeting - April 22, 2020
Description
April 22, 2020
Agenda
Release 0.12 happening right now.
0.12 changes
What’s Next?
Electron Application
Auto-Updating
Desktop Launching
Windows users rejoice.
YAML Editor
First pass of simple editing ability.
In-Cluster
Continuing to work on this problem.
Removing global context as we identify it.
A
B
Yeah,
it
is
happening
right
now,
as
we
as
we
are
talking.
The
the
button
has
been
pushed
and
looks
like
everything
is
running
successfully,
so
the
the
binary
assets
should
be
available
shortly
and
yeah.
It's
there's
a
lot
of
changes
there.
So
it's
a
lot
of
there's
a
lot
of
new
UI
stuff
that
you'll
see
specifically
around
the
navigation
and
the
vertical
nav
that
we
have
been
demoing
and
showing
over
the
last
couple
weeks.
B
Yeah
is
there
so
many,
so
many
good
things
in
here
the
log
streaming
that
we
demoed
in
the
previous
week,
which
now
for
those
who
weren't
there
for
that
the
logging
now
used
to
send
a
big
aggregation
of
all
of
the
logs
every
5
seconds
in
a
polling
fashion.
We
would
go
fetch
them
from
the
API
and
and
reload
them
into
the
UI,
and
now
we
just
connect
up
and
and
stream
in
a
similar
fashion
to
what
you're
used
to
when
you
do
a
cube.
B
Ctl
get
Logs
with
the
follow,
so
uses
less
API
resources
and
less
front-end
resources
to
kind
of
just
sit
and
follow
that
that
that
stream
waiting
for
actual,
writes,
yeah,
just
lots
of
good
stuff.
In
this
release,
a
lot
of
prep
work
around
getting
ready
for
what's
coming
up
next,
which
is
around
the
electron
app.
B
We,
the
navigation
stuff
that
we
put
in
place,
was
needed
so
that
when
you're,
using
the
electron
app,
which
will
not
have
the
standard
browser,
web
interface
can
still
navigate
around
and
and
move
throughout
the
application
and
a
convenient
and
very
straightforward
way.
So
the
new
navigation
and
combination
with
the
breadcrumb
work
should
allow
for
a
fairly
easy
transition
over
into
the
electron
app
öktem
itself
is
just
now
more
usable
and
and
user-friendly
when
it
comes
to
moving
around
the
application.
B
There's
a
whole
lot
less
of
needing
or
feeling
compelled
to
go
up
into
the
the
browser
Chrome
to
get
things
done.
So
those
are
all
very,
very
positive
changes.
We
also
added.
There
was
one
other
thing:
I
wanted
to
call
out.
What
was
it?
I
had
notes:
I've
lost
them
in
a
sea
of
Windows,
but
there
was
I'm
pulling
up
the
release,
notes
right
now,
so
I
can
see
if
I
can
find
it,
because
I
wanted
to
call
it
out.
B
It's
a
pretty
neat:
oh
yeah,
two
things:
Sam
added
a
kind
of
a
first
pass
of
a
network
policy
viewer.
So
now,
if
you
have
network
policies-
and
you
go
and
take
a
look
at
your
iPad,
your
resources
you'll
see
those
I.
Don't
have
a
screenshot
available
right
now.
I
think
there
might
be
one
in
the
actual
issue
in
813,
so
we
can
maybe
pull
that
up.
B
I'm
checking
right
now,
but
yeah,
so
that
was
that
was
something
that
Sam
had
put
in
there
and
it
was
a
good
just
a
good
something
that
people
been
asking
for
for
a
long
time.
Yeah.
There
is
a
couple
screenshots
in
there,
so
so
yeah.
You
can
now
see
your
network
policies
it
there.
You
go
yeah
pretty
straightforward.
B
So
but
that's
a
that's
a
nice,
a
nice
thing
that
people
have
been
asking
for
so
that's
in
there
and
then
the
other
one
that
that
was
a
big
big
win
for
us
was
the
actions
the
the
table.
Data
great
actions
is
what
called
so
that's
something
that
Brian
added.
We
demoed
that
briefly
I
think
was
it
last
week
or
the
week
the
community
meeting
before,
but
for
those
who
weren't
there
for
that.
That
is
on
the
actual
table
view
when
you're
the
gridview
when
you're.
B
Things
like
that
that'll
now
be
supported
by
that
action
column,
which
ties
into
the
ability
to
now
create
objects
which
people
been
asking
for
for
a
long
time
and
that's
now
available
in
the
and
all
of
the
service
interfaces,
so
plugins
can
can
create
objects.
Some
a
lot
of
good,
a
lot
of
good
things,
they're
around
just
enhancements
that
people
been
asking
for
for
a
long
time
and
work.
That's
setting
us
up
for
some
of
the
future
work
that
is
to
come.
All
of
the
changes
are
broken
down.
Oh
I
do
want
to
call
it.
B
The
the
the
there
is
a
plugin
API
change
that
is
breaking
if
you're
using
actions.
So
if
you,
if
you've
created
a
plug-in
and
your
plugin,
is
using
actions
the
there's
an
breaking
API
change
around
how
we
handle
the
action
requests.
Specifically,
there
is
an
action
name
attached
to
the
action
request.
All
of
that
is
documented
in
the
go
dock
for
the
change.
You
can
see
it
there.
You
can
there's
an
example
usage
all
in
the
documentation.
B
B
B
Yeah
I
can
I
can
I
can
do
both
of
those
things.
I
can
get
the
the
little
animation
we
have
in
the
readme,
updated
and
I
can
also
go
ahead
and
create
just
a
small
YouTube
clip
that
similar
to
the
one
we
have
now,
where
we're
walking
through
all
of
kind
of
the
the
top
tier
options
and
showing
the
different
phases
of
the
UI
I
can
create
a
new
one.
That
does
that.
That
would
be
fantastic,
yeah.
C
B
B
So
moving
on
to
what's
next
so
we've
been,
we've
been
talking
about
these
items
for
a
while
now
and
I,
just
wanted
to
kind
of
circle
back
to
them,
highlight
them
and
give
everyone
kind
of
some
insight
into
you.
What
we're
going
to
be
working
on
kind
of
where
our
focus
is
going
to
be
and
what
you
can
expect
coming
down
the
coming
down
the
pipe.
B
So
the
electron
application,
which
is
has
been
on
our
been
on
our
timeline
for
a
while
now
it
was,
it
was
really
essentially
blocked
by
the
new
navigation
stuff
and
now
that
that
navigation
is
in
there,
we
can
really
go
and
attack
this
and
bring
it
up
to
feature
parity.
Get
those
features
in
there
like
auto,
updating
and
desktop.
B
Launching
you
know,
desktop
launchings,
especially
for
Windows
users,
is
something
that
will
make
the
experience
a
whole
lot
better
right
now
for
those
who
don't
use
Windows,
if
you
download
octant,
put
it
on
your
desktop
and
double-click
it
on
a
Windows
machine,
you
get
an
error
that
says
this
is
a
command
line
application
and
that's
it.
So
that's
your
experience
on
Windows
right
now.
It's
really
bad,
so
this
will
fix.
All
of
that.
Make
it
a
lot
better,
but
also
the
important
part
here
is
that
we'll
get
into
the
auto
updating.
B
That
Sam
wrote
a
proposal
for
which
we
have
accepted
and
merged
and
so
we'll
be
doing
a
whole
revamp
of
our
of
our
CI
CD
system,
which
will
support
the
ability
to
do
auto,
update
through
the
electron
application,
in
a
way
that
we
are
confident
and,
and
things
are,
are
working
well,
some
we're
very
excited
about
that
work.
It
it
really.
It
really
gets
us
to
the
moving
in
that
direction
towards
the
one
data
that
we
were
working
towards.
So
the
next
thing
of
that
is
the
llamo
editor.
B
We're
gonna
do
a
first
pass
of
just
a
simple
edit
ability,
but
don't
know
fully
what
this
gonna
look
like.
Yet
it
will
be
a
very:
it
will
be
a
very
stripped
down
version
of
edit,
probably
just
taking
the
current
readme
read-only
view,
allowing
it
to
go
to
a
edit
view,
probably
showing
the
highlighting
the
lines
that
have
changed
since
you
flipped
it
to
edit
view
and
then
providing
a
save,
slash,
update
button
that
that's.
B
That
is
going
to
be
probably
the
extent
of
the
first
pass
of
editing
with
the
yamo
editor,
but
it
will
be
considering
right
now
there
is
none.
It
will
be
a
huge
step
in
the
right
direction
and
I
think
it
will
make
often
a
lot
more
useful
for
many
many
people
I
know
for
myself
what
I'm
using
octant
one
of
the
big
things
that
I
wish
I
could
do
is
just
make
really
simple
edits
to
some
of
my
ammo,
especially
I'm
iterating
quickly
on
something
like
a
custom
resource.
B
It
would
be
really
nice
to
be
able
to
just
be
in
there
and
and
make
those
changes
very
quickly,
hit
the
Save
button
and
not
have
to
toggle
out
and
reapply
and
all
of
the
things
that
I
have
to
do
now
and
then
the
other
focus
is
going
to
this
is
this.
Is
this
is
in
here
not
so
much
that
you
should
expect
to
see
this
functioning
fully
anytime
soon?
This
is
in
here
just
to
kind
of
give
folks
a
general
overview
of
that.
B
We
are
thinking
about
this
problem
and
that
we
are
frequently
addressing
things
that
block
us
from
running
octant,
effectively
and
efficiently
in
cluster.
We
are
when
we
are
thinking
about
how
we're
engineering
things
and
then
later
how
we
move
on
to
programming
those
things
we're
doing
it
in
a
way
that
is
allowing
us
to
run
in
cluster
and
we're
refactoring
things
when
we
identify
them
that
are
currently
stuck
with
a
global
context
or
make
assumptions
about
where
octant
is
running.
B
B
We
essentially
octant
on
the
back
end
as
an
API
that
is
encapsulating
the
kubernetes
api
and
then
surfacing
that
information
to
a
UI
using
a
common
language,
in
our
case
adjacent
stream
that
jason
stream
is
there,
so
that
we
can
put
any
UI
on
top
of
it
that
we
want.
So
when
we
are
eventually
in
cluster.
The
same
browser
UI
that
you
use
octant
with
now
is
will
be
what
you'll
see,
and
so
the
work
that
we're
doing
now
is
removing
some
of
the
assumptions
that
we
made
about
where
octant
is
running.
B
It's
really
not
most
of
the
work
is,
is
around
that
not
so
much
any
work
around
needing
to
make
things
accessible
from
different
parts
of
the
API
we've
already.
We've
already
have
a
well-defined
internal
and
external
API
that
these
these
UIs
are
using,
and
that's
really
that's
really
it.
For
the
for,
what's
coming
up,
next
is
expect
to
see,
and
and
as
for
like
dates,
and
when
these
things
are
going
to
be
available.
B
The
the
electron
application
is
something
that
we're
gonna
really
focus
on,
so
that
we
can
move
into
this
kind
of
auto-updating
phase
of
octant.
Where
then,
as
new
things
and
as
features
and
as
fixes
are
released,
we're
able
to
get
them
pushed
out
and
get
updates
in
place.
We
when
I,
say
auto-updating
what
I
mean
is
just
to
just
to
clarify
on
that.
B
Moving
to
the
next
version
is
yeah,
I,
say
I'm
like
Windows,
where
it
just
like
does
what
it
wants.
Whenever
it
wants
so
yeah,
we
won't
be
doing
that.
So
auto
updating
will
be
there
in
a
in
a
opt-in
capacity
where
you
will
will
do
a
new
release.
It'll
be
on
github
of
the
application
will
see
that
release
URL
and
it
will
say,
hey,
there's,
there's
a
new
release.
Do
you
want
update
so
and
that's
that's
it?
That's
all
I
have
for
this
for
this
meeting.
A
B
B
C
Think
there
is
one
minor
change
where,
with
way
we
do
our
navigation
now
we
would
lose
access
to
a
nested
plugin
path,
or
at
least
it
wouldn't
be
visible
from
the
UI
I.
Don't
know
how
many
users
that
actually
affect,
but
we
made
the
decision
to
just
move
forward
with
the
navigation.
Just
overlooking
that,
because
you
just
really
weren't
sure
how
many
people
were
doing
that
see
I
think
that's
yeah
I
think
that's
really.
It.