►
From YouTube: Octant Community Meeting - June 17, 2020
Description
June 17, 2020
Agenda
Supporting ALB Ingress Controller. Are there more? #987
Table string filters #986
CRDs in cluster overview #981
SubjectAccess work continues
Plugin updates being discussed
portable acorss platforms
reloadable, removable, all of uables
findable, json structure to identify plugin locations
CNCF Webinar on Octant happening June 17th at 4PM ET / 1PM PT, led by Wayne
More Storybook Demo
Sandbox
Open Q&A - add your questions here
Plugin hosted out of the cluster as an addon? A completely remote plugin.
Eventually. The new plugin runtime is going to be gRPC.
A
All
right
welcome
everybody
to
the
June
17th
octant
community
meeting
we're
gonna
go
over
kind
of
a
couple:
things
that
are
landed
and
master
they've
been
working
on
talk
about
some
of
the
longer
term
work
that
we
have
been
continuing
to
do,
and
also
REME
ention,
the
webinar
that
we
have
coming
up
today.
So
with
that
I'll
get
started
so
that
we
got
an
issue
reported
for
the
ingress
controller
for
alb
ingress
controller.
A
This
was
reported
by
billy
sham
brook
and
sam
took
a
look
at
this
and
we
have
come
up
with
a
fixed
fort
that
we
are
going
to
we're
gonna
just
build
in
support
for
this
special
use
of
annotations
and
labels
or
values
within
amazon,
so
that
everything
will
just
kind
of
function.
The
way
it's
intended
to,
and
there
was
a
PR
up
for
this
that
got
approved,
and
then
we
had
some
more
discussion
on
it
and
decided
that
we
wanted
to
just
have
first-class
support
for
this
item.
A
We
were
originally
thinking
about
just
making
it
function,
as
is
kind
of
passing
on
doing
the
backend
look
up
and
we
would
implement
the
object,
status
and
config
information
that
comes
out
of
these
annotations
is
a
plugin,
but
right
now
the
plug-in
model,
for
that
would
be
there's
not
a
great
place
for
people
to
discover
plugins.
So
they
wouldn't
even
know
that
they
need
this
plug-in
until
they
ran
into
a
failure.
So
we
decided
to
go
ahead
and
just
implement
this
as
native
support
in
octane
and
we'll
revisit.
A
A
This
AWS
alb
ingress
controller,
there's
a
special
markup
that
you
can
do
where
you
use
this
service
name
and
service
port
with
the
use,
annotation
information
and
Amazon
will
then
go
and
use
these
annotation
entries
to
perform
this
SSL
redirect.
So,
since
that
service
name
is
not
a
real
service
and
octants
attempts
to
build
a
resource
viewer
and
look
up
these
services
in
the
backend,
this
was
failing
when
you
attempted
to
view
or
load
this
ingress
into
any
of
the
resource
viewer
trees.
A
So
this
issue
will
be
corrected
very
soon,
thanks
to
Sam
and
well
well,
the
next
release
will
include
that
we're
not
going
to
do
it
a
dot
release
for
the
next
release
will
do
a
full
arm
release
because
that's
going
to
include
the
story
book
updates.
The
some
new
features
with
table
filtering
that
I'm
about
to
talk
about,
and
the
new
CRD
overview
cluster
overview
stuff,
which
I'm
about
to
talk
about
as
well,
so
moving
on
to
the
table
string
filter.
So
this
was
a
PR
that
came
in
from
sir
Sir
Joey
from
Belgium.
A
Iii
will
learn
how
to
pronounce
that
name.
I
promise.
This
was
the
ability
to
add
filtering
to
our
data
good
columns.
So
currently
there
was
no
filtering
flow.
So
if
you
had
long
lists
of
things,
you
would
end
up
with
this
view
that
you're
seeing
here,
where
you'd
have
to
page
through
at
the
bottom,
or
extend
the
list
out
and
scroll
up
and
down.
So
this
is
a
free-form
string,
filtering
that
happens
on
the
front
end.
A
It
allows
you
to
type
in
and
and
filter
down
anything
that's
in
the
name
column
for
a
given
data
grid,
I
believe
it's
for
every
column
in
the
data
grid,
yeah
every
column,
so
that
feature
will
be
in
the
in
the
next
release,
but
it's
also
it's
merged
into
master
now.
So
it's
part
of
the
nightly
build,
which
is
a
good,
a
good
temperature,
remind
folks
that
if
you
head
over
to
the
Occident
main
oktin
page-
and
I
read
me-
you'll-
find
a
link
to
our
nightly
builds,
which
is
radio.
A
The
third
new
feature
that
was
added
well,
I,
guess
the
first
one
was
affixed
but
also
features
bug
bug
han
sment.
The
third
item
that
was
added
was
the
cluster
overview.
We
added
the
actual
listing
of
CR
DS
in
cluster
over
you,
so
Brian.
This
close
that
a
whole
host
of
issues
that
we
had
about
not
showing
CR,
DS
and
and
how
updating
some
of
the
printer
patterns
that
were
using
and
and
moving
away
from
consolidating
some
of
our
code
that
was
converting
unstructured
to
concrete
types.
A
We
had
it
kind
of
peppered
throughout
the
whole
project.
So
this
kind
of
cleaned
up
a
lot
of
those,
and
so
now
the
CR
DS
are
listed
on
the
on
the
cluster
overview.
Page
and
I.
Think
I
have
I,
mean
I.
Think
I
have
a
heavy
box
at
running,
but
let
me
see
if
it
if
it
has
any
CR
DS
in
it,
I
think
it
does
just.
A
Have
to
move
it
from
the
browser
I
have
it
on
to
this
browser
lets,
go
kloster
overview
yeah.
So
here
in
the
cluster
overview
you
can
see.
This
is
this.
Is
the
section
we're
talking
about
so
now?
There
is
the
list
of
CR
DS
that
are
currently
installed,
and
you
can
click
through
on
them
and
find
any
find
out
the
information
that
is
available
for
those
kind,
the
list
and
all
of
all
the
information
you
would
expect
to
find
out
about
a
CR
D
so
that
that
was
added
by
by
Brian.
A
My
build
that
I'm
running
right
here
is
the
current
release
build
so
it
doesn't
have
or
the
the
an
old
master
build.
Not
the
current
release
build
so
can
see.
It
doesn't
have
those
those
filters
yet,
but
they
are
there
and
the
so
that
so
that's
it
for
the
current
list
of
new
features
that
we've
been
working
on
and
it
just
in
this
last
week
and
then
I
wanted
to
circle
back
to
some
of
the
items
that
were
brought
up
in
the
previous
week.
So
I'm
still
working
on
the
update
to
our
subject
access.
A
There
was
some
internal
shifting
and
moving
of
things
at
VMware,
which
is
the
company
I
work
for,
and
so
I've
been
kind
of
getting
acclimated
to
new,
a
new
group
and
and
lots
of
meetings,
and
things
like
that.
So
this
work
kind
of
stalled
a
little
bit
during
during
late
last
week
and
earlier
this
week,
but
I'm
picking
that
back
up
tomorrow
and
to
remind
folks
the
subject.
Access
work
is
the
work
that
is
going
into
us
collecting
and
building
a
profile
of
what
you
have
access
to
in
a
cluster
at
at
log.
A
Essentially,
what
is
log
in
time
or
in
the
case
of
öktem
right
now
start
time.
Those
two
things
are
soon
to
be
separated,
and
this
allows
us
to
then
navigate
you
through
octant.
Without
the
issue
of
showing
you
a
bunch
of
things,
you
don't
have
access
to
or
us
getting
a
bunch
of
unauthorized
errors
from
the
cluster
and
trying
to
retry,
watches
and
retry
and
list
falls
over
and
over
and
over
the
current
method.
A
We
have
support
backing
off,
but
it
is
something
where
we're
explicitly
checking
with
each
request,
so
we're
moving
away
from
that
model.
To
a
kind
of
an
access
cash
model
or
an
access
lookup
model,
where
we
will
fetch
this
information
periodically
from
the
cluster
and
update
any
of
the
of
the
maps
for
what
you
have
access
to
and
we'll
also
be
able
to
allow
the
user
to
refresh
this
and
and
clear
it
out,
but
we'll
also
be
able
to
and
we'll
also
be
able
to
prompt
users
win
something
they
previously
had
access
to.
A
They
no
longer
have
access
to
you
in
the
case
of
configuration
files
being
changed
or
credentials
being
expired.
Things
like
that,
so
it
opens
up
a
lot
of
ways
that
we
can
now
notify
the
user
of
kind
of
what's
happening
and
have
a
more
friendly
experience
for
for
you,
as
you're,
navigating
through
your
cluster
you're,
not
going
to
be
clicking
on
a
lot
of
things
that
don't
work.
A
Moving
on
to
plugins,
so
the
plug-in
updates
are
being
discussed
and
the
main
goals
here,
I'm
actually
going
to
edit
this.
While
we
talk
so
there's
some
live
notes,
the
main
goals
of
the
plugin
updates
are
to
make
plugins
portable
across
platforms
right
now.
There
has
to
be
built
for
each
specific
platform
that
you
want
to
run
them
on.
A
So
that's
that's
one
of
the
goals.
Another
goal
is
to
make
them
reloadable
right
now
you
have
to
stop
and
start
octants
if
plug-in
changes,
or
you
want
to
install
the
new
one
or
you
want
to
remove
one.
We
want
the
ability
for
them
to
be
reloadable
removable,
all
all
of
the
all
of
the
bubbles
so
anyway,
so
we
and
then
the
third
item
is
that
we
want
them
to
be
able
to
be
easily
accessed
like
easily
find
them.
A
A
You
know
in
real
time
is
the
function
of
that
is
not
what
we're
concerned
about
it's
the
ability
to
consume
some
JSON
structure
that
tells
octant
where
it
can
go
and
find
plugins
whether
they
are
just
anywhere
doesn't
matter.
That's
so
that's
that's
the
main
goal
so
actually
we'll
call
this
JSON
structure
to
identify
plug-in
locations.
B
Yeah
I
mean
in
K
native
I'm,
looking
at
implementing
something
called
a
proof
of
concept.
Name
is
a
manual,
but
it's
it's
hints
for
things
like
open
shift
or
GCP,
or
some
other
UI
renderer.
That
gives
hints
on
how
to
show
a
CR
D
in
the
first-class
way
that
it
would
like
I.
Think
one
of
the
spec
values
is
a
slider.
Then
there's
hints
on
say,
like
this
field
is
a
slider
with
this
range
and
right
now
most
of
these
companies
do
this
in
annotations
yep.
B
But
one
of
the
other
goals
is
a
way
to
help
discovery
of
what's
available
in
your
cluster
and
it
kind
of
occurs
to
me.
I
have
one
point:
I
want
to
ask
about.
The
group
thinks
around
plugins
and
so
and
then
this
leads
in
so
it'd
be
interesting.
If
the
plug-in
was
able
to
actually
like
be
hosted
out
of
the
cluster
as
some
sort
of
installable
add-on
and
I.
Don't
know
what
you
think
about
that.
B
But
if
that
was
the
case,
then
you
could
also
use
the
CRD
manual
thing
to
discover
that
something
actually
does
support
a
nokton
plugin.
And
then
it
like
you
could
get
kind
of
a
self
discovery
mechanism
there
by
observing,
what's
in
the
cluster
and
then
using
the
cluster,
to
go
and
extend
the
view
of
octave,
potentially.
A
B
It's
a
port
localhost
right
and
you're
thinking
back
requests,
and
it's
streaming
like
basically
render
commands
octant.
Yes,
correct,
yeah
yeah,
it
seems
like
it'd,
be
an
interesting
model
for
that.
That's
streaming
to
actually
happen
over
any
kind
of
HTTP.
It
doesn't
have
to
be
local.
It
could
actually
be
in
the
cluster
you're
talking
to
yeah.
A
And
I
think
that'll
be
possible.
So
it's
it's
not
a
it's,
not
a
goal
of
the
redesign
of
plugins,
but
one
of
the
things
we
will
be
doing
when
we
redesign
plugins
is
moving
away
from
go
plugin
and
implementing
our
own
G
RPC
runtime
to
communicate
between
octant
and
plugins.
So
since
it
will
just
be
G,
RPC
there's
nothing
to
say
that
it
can't
be
some
other
thing
running
somewhere
else.
A
A
And
so
yeah,
so
that
that
kind
of
covers
what
our
our
our
current
agenda
is.
Our
current
goals,
Sam,
is
also
I
just
want
to
give
an
update.
Sam
is
still
working
on
the
on
teasing
the
hard
requirement
for
octant
to
need
a
cute
config
at
startup.
This
is
something
that
we've
been
knowing.
That
is
that
we
wanted
to
remove
for
a
while
and
Sam
is
currently
in
the
process
of
working
on
on
that
code.
A
A
We're
going
to
fix
everything
without
ever
going
out
into
into
cube
CTL
I'm
gonna
fix
it
all
right
through
octant,
which
is
which
is
pretty
great,
so
I
encourage
folks
to
if
they
are
interested
or
have
time
or
haven't,
seen
a
full
and
end
demo
of
octant
before
to
attend
and
check
it
out.
It's
today
at
4:00
p.m.
Eastern
1:00
p.m.
Pacific
time,
and
with
that
I'll
hand
it
over
to
Milan
who
is
going
to
do
a
quick
demo
of
the
storybook
work
that
we've
had
in
progress.
A
C
So
what
we
did
is
we
added
this
at
sandbox
component
in
inside
the
storybooks,
where
you
can
virtually
put
in
any
Jason
and
play
with
it,
see
how
it
works
and
use
that
as
a
prototyping.
So
in
this
case,
I
literally
went
and
one
of
the
pages
of
the
overview
page
from
one
of
my
clusters.
I
went
and
copied
the
JSON
definition
for
that
and
I
pasted
it
down
here,
and
this
is
what
showed
up
and
it's
it's
it's.
C
It's
really
easy
to
to
play
with
that
and
change
things
and
see
how
how
the
views
respond-
and
this
is
all
thanks
to
the
model
we
have
internally.
Basically,
the
way
we
render
every
page
is
true
that,
based
on
this
JSON
stream,
that
comes
from
the
count
of
runtime
and
that
Jason
seam
defines
every
single
component
you
see
on
this
page.
So
you
know
for
somebody
who
is
trying
to
see
how
this
works
are
trying
to
prototype
new
pages.
C
C
You
know
doing
doing
things
like
that,
there's
a
little
bit
of
why
you
see
this
is
making
sure
it's
not
too
long
so
so
this
is
basically
how
we
plan
to
do
some.
What's
that
be
modeling,
so
that's
only
enable
octant
to
be
much
easier
used
inside
the
other
projects
to
build
your
own
either
pages
or
a
plugin.
So
what
to
start
with?
C
The
only
thing
you
need
to
do
is
get
in
your
browser
got
to
not
for
King
tab
grab
your
JSON
from
here
and
paste
the
vignette
down
here
that
should
should
do
it
right
looks
like
I
actually
had
this
a
mistake.
This
is
I,
don't
know
what
I
did,
but
the
general
idea
is
just
to
you
know,
have
a
playground
where
he
can
test
the
different
things
before
they
are.
There
use
them
actual
code.
A
Now,
when
I
want
to
add
a
new
component
like
it
was
pretty
easy
to
write
a
story
for
a
new
component
before
and
add
it,
but
now
I
can
just
go
and
I
can
get
things
set
up
and
I
can
just
use
the
sandbox
to
prototype
it
quickly
and
make
sure
the
layouts
how
I
want
and
make
sure
that
all
the
things
are
there
and
then
I
can
convert
it
into
its
own
story
and
add
it
as
a
component
in
all
of
that.
So
this
is.