►
From YouTube: Octant Community Meeting - July 8, 2020
Description
July 08, 2020
Agenda
Upcoming release
Create resource (apply yaml)
Start without Kubeconfig
Port Forward Service
Better ALB Ingress Support
Easier delete namespace (grid action)
Continued efforts
Viewing RBAC permissions (can-i)
HasAccess / subjectaccess refactoring
Resource Viewer
Plugin System #1080
Upcoming
More electron app focus
Structured log viewer
More clarity components (Wizard, Timeline)
Look into: Stepper component as well
Visualizing knative
Visualizing tekton
https://github.com/tektoncd/experimental/tree/master/octant-plugin
Open Q&A - add your questions here
Community Meeting Agenda and Video
when video is uploaded, copy that weeks agenda with video link in to our GH repo?
still use hackmd for live agenda
relpace agenda with link to GH
Action: create wiki entry for community notes, add notes and video link together.
A
B
All
right
wait:
yeah
thanks,
so
yeah
today
we're
going
to
cover
the
upcoming
release,
talk
about
some
of
the
continued
efforts
you've
been
working
on
and
then
just
go
into
a
little
bit
about
what
might
be
coming
up
and
then
there's
some
some
Q&A
around
this
meeting
and
the
agenda,
and
things
like
that
so
get
started
with
the
upcoming
release.
So
we've
got
some
really
neat
features
coming
up.
B
We
were
thinking
about
doing
a
release
this
week
or
actually
we're
think
about
doing
it
last
week,
but
I
we
kind
of
wanted
to
wait
and
hold
up
force
for
these
features
that
are
listed
here.
All
of
them
are
in
flight
right
now
and
or
emerged
or
about
to
be
merged,
so
the
they
shouldn't
hold
up
things
for
too
long,
but
the
create
resource
or
apply
yeah
mole.
That's
a
feature
that
people
have
been
asking
for
for
a
while.
So
we're
getting
just
kind
of
the
first
iteration
of
that
in
place.
B
It'll
be
a
very
simple
modal.
You
paste
camel
you
hit,
apply
whatever
it
is,
and
things
happen
and
off
it
goes
into
your
cluster,
so
Scott
is
currently
doing
that
work
now
and
so
that'll
be
part
of
the
the
next
release.
The
start,
without
a
keep
config
work
that
Sam
has
been
working
on,
is
just
about
ready,
there's
a
final
pass
for
a
review.
That's
going
to
be
happening
today
and
I
believe
that
that
all
that
all
that
work
is
now
ready
to
be
merged.
B
So
it's
a
some
nice
kind
of
workflow
change
that
hasn't
existed
in
octant
before,
but
the
other
nice
thing
about
this
is
now.
It
enables
us
to
really
start
focused
on
getting
the
electron
application
as
the
primary
viewer
for
the
octant
UI
the
benefit
there
is
that
we
are
no
longer
bound
to
the
things
that
individual
browsers
can
and
cannot.
Do
we
also
get
access
off
access
to
a
full
for
those
who
aren't
familiar
with
electron?
B
It's
it's
basically
nodejs
and
chromium
mashed
together
to
give
you
a
native
runtime
for
a
JavaScript
type
application,
so
we'll
be
using
that
we
have
a
branch
or
we
have
it.
We
have
a
feature
now
that's
merged
into
master,
where
you
can
build
and
run
that
when
this
lands,
this
start
without
a
cube.
Config
lands
that'll
actually
be
a
lot
more
usable
because
you're
actually
able
to
start
the
application
and
and
see
a
UI
without
it.
Just
failing
with
no
right
now.just
fails
and
it
doesn't
tell
you
why
or
make
it
easy
to
figure
out.
B
Why
just
fails,
because
you
don't
have
a
cube
config,
so
not
very
friendly.
This
fixes,
all
of
that
which
is
really
nice,
the
port
forward
of
service.
This
is
something
that
came
up
very
early
on
was
just
one
of
those
things
that
just
kind
of
need
it
to
be
done.
We
have
a
group
of
folks
who
are
currently
working
on
that
issue.
Right
now,
there's
a
branch
it
works,
they're,
just
writing
some
tests
and
flushing
out
some
of
the
finer
details
on
it,
but
that
will
be
in
this
next
release
as
well.
B
Another
thing
that
Sam
worked
on
was
the
the
ale
being
ingress
support.
This
is
specific
around
the
bug
that
was
opened
when
you
use
annotation
as
your
as
your
I
believe,
as
your
I
was
at
the
port
or
the
name
or
something,
and
then
the
target
is,
is
the
actual
port
is
like
SSL
redirect
and
and
anyway,
the
Amazon
has
a
dialogue
that
will
go
and
it'll
read
this
HTTP
HTTPS
configuration
from
the
annotation
on
the
ingress
and
then
it
will
use
that
to
forward
your
requests
and
and
and
do
do
the
SSL
redirect.
B
So
this
was
failing
an
octant
causing
just
the
whole
thing.
That's
a
V
render
at
all.
So
we
fixed
that,
but
we
also
took
that
information
and
moved
it
up
into
the
config
section.
So
when
you're
looking
at
the
ingress
you'll
see
that
it
is
using
annotation,
but
then
you
also
see
the
configuration
that's
in
that
annotation.
So
that's
that's
a
nice
little
extra
that
way
that
we
put
in
there
and
then
finally,
just
the
ability
to
kind
of
delete
namespaces
without
having
to
go
into
the
namespace
listing.
B
Then
click
on
the
individual
namespace
and
then
go
and
hit
delete.
Now
you
can
just
write
from
the
grid
from
the
list
of
namespaces.
There's
a
grid
action
similar
to
how
we
have
for
other
resources.
You
can
just
select
delete,
so
those
are
all
things
that
will
be
coming
up
in
the
next
release.
Is
there
anything
that
I
forgot
or
anything
that
someone
wants
to
add
before
I
move
on
to
the
continued
efforts.
B
Great,
so
the
continued
effort,
so
this
is
all
stuff
that's
been
being
worked
on
and
has
been
in
flight
for
a
while
I
just
wanted
to
touch
on
it
again
to
kind
of
give
an
update
of
where
they're
at
so
the
viewing
are
back.
Permissions
are
essentially
the
can
I
view
that
might
have
that
within
octant.
B
That
is
something
that
I've
been
working
on
and
going
back
and
forth
on
for
the
last
couple
releases,
and
what
we've
decided
is
that
we're
going
to
build
out
the
can
I
view
under
the
under
the
cluster
module
and
then
once
we
have
that
built
out.
We'll
then
take
that
and
leverage
the
the
permissions
that
we've
collected
with
them
with
our
has
access.
Subject:
access
refactoring,
so
originally
I
was
trying
to
kind
of
do.
Those
has
access,
subject:
access,
refactorings,
first
and
then
I
was
going
to
map
them
into
the
can
idea.
B
I
got
a
little
stuck
in
some
places
and
and
wasn't
able
to
really
flush
that
idea
out
fully
because
it
was,
it
was
trying
to
do
too
much
at
once.
So
I
want
I,
took
a
step
back
from
it
and
decided
that
we'll
implement
the
can
idea,
which
will
give
us
all
of
the
kind
of
core
pieces.
We
need
to
then
start
to
incrementally
move
forward
with
refactoring
or
has
access
the
goal.
There
is
to
remove
that
spamming
of
the
API.
B
When
we
don't
have
access
to
resources,
we
just
were
able
to
just
kind
of
accept
the
fact
that
we
don't
have
access
to
it
and,
and
we
refresh
on
a
on
a
timer,
the
the
access
that
we
have
and
then
also
provide
some
user
actions
to
manually
refresh
and
attempt
to
reconnect
and
get
a
new
set
of
permissions.
So
the
resource
viewer
work
that
Milan
has
been
doing.
That's
been
progressing
forward
in
Milan.
Do
you
want
to
talk
about
that?
A
little
bit.
C
B
B
So
we're
really
working
hard
on
that
to
make
sure
that
we're
that
we're
adding
some
like
enriching
the
existing
resource
viewer
and
making
it
something
that
that
provides
higher
value
than
the
current
one
does
and
I
think
we're
doing
that
so
keep
an
eye
out
for
that
I'm
sure
we'll
have
some
more
demos
as
that
progresses
and
then
one
of
the
things
that
has
also
been
being
worked
on
recently.
That
I've
shown
a
couple
of
times
now
is
the
plug-in
system
I
I.
B
Finally,
appropriately
made
an
issue
for
it,
because
I
had
been
slacking
and
doing
that.
So
1080
is
the
issue
for
kind
of
prototyping,
the
JavaScript
typescript
plug-in
system.
The
goal
here
is
we're:
gonna
create
a
no,
it
won't
be
full-featured,
but
it
will
do
the
baseline
of
what
our
plugins
do
now
and
will
provide
some
scaffolding
and
some
documentation
around
how
to
get
started
using
it
and
then
we're
gonna
release
it
under
experimental
feature
flag
or
it
might
not
even
need
to
be
under
a
feature
flag.
B
It'll,
basically
just
be
released,
experimental
use
at
your
own
risk,
but
please
use
it
to
so.
We
can
get
feedback
on
it.
It
will
exist
alongside
the
existing
go
plug-in
system
that
won't
be
changing
at
all
for
the
for
the
time
being,
and
these
two
things
will
will
live
side
by
side
and
use
its
kind
of
drive,
the
shape
and
design
of
the
plug-in
system,
as
we
try
to
make
it
so
that
it's
it
can.
B
Plugins
can
easily
be
shipped
out
to
various
platforms,
but
they're
also
easy
to
create
and
easy
to
get
started
with
just
reducing
any
friction
around
plug-in
installation
and
running
and
and
things
like
that
and
in
creation
itself,
so
that
work
will
will
will
land
at
some
point
in
master
but
will
be
again
we'll
be
doing.
Demos
and
talking
about
it
as
it
as
it
progresses
just
like
we
have
been,
did
I
miss
anything
on.
B
B
Not
only
can
we
have
it
alongside
all
of
the
component
documentation,
but
it
can
be
a
more
feature-rich
experience
by
being
able
to
have
a
tutorial
for
building
a
plugin
that
includes
the
actual
visualizations
that
you're
going
to
be
creating
using
the
code
that
you're
actually
going
to
be
copying
and
pasting
to
do
that.
So,
as
you
walk
through
the
docs
you'll
be
getting
this
guided
UI
experience
of
building
a
plugin
that
will
map
directly
to
what
you're
going
to
see
in
octave.
B
It's
it's
a
pretty
neat
way
to
use
storybook
and
so
I,
and
fortunately
I've
done
the
groundwork
for
us.
So
I
create
an
issue
that
linked
to
their
two
repos
are
the
two
entries
in
their
repo.
That
kind
of
make
this
happen
within
story
book
and
we're
gonna
be.
This
is
part
of
the
continued
effort
around
building
out
better
docs
for
people.
B
We
know
right
now
that
we
have
some
some
pretty
large
gaps
and,
as
things
have
moved
and
updated,
we
haven't
done
so
well
of
of
keeping
those
things
updated
and
the
whole
storybook
initiative
was
was
a
big
part
of
making
sure
that
keeping
our
Doc's,
up-to-date
and
and
presenting
them
in
an
in
a
useful
way
was
was
a
priority
for
us,
and
so
that's
that's.
Why
that's
where
the
motivation
for
all
this
came
from
and
that's
what
you
can
expect
to
see
from
our
storybook
is
a
very
similar
experience
to
what
we
have
is.
Does.
B
B
B
B
These
big
long,
like
input,
form
type
style,
Wizards
yourself,
and
this
will.
This
will
alleviate
a
lot
of
a
lot
of
that
setup
and
then
we're
also
thinking
about
how
can
we
visualize
popular
tools,
especially
tools
that
have
like
lots
of
events
and
workflows
in
octant
thinking
about
like
K
native
and
Tecton?
We
we
want
to
be
able
to
take
the
output
of
some
of
these
common
things
that
people
use
and
show
them
in
a
way.
That's
helpful
surface.
D
Was
just
gonna
add
for
the
wizard
in
the
timeline:
Colonia
also
look
into
the
stepper
component
as
well,
if
it's
not
already
in
there
from
like
a
design
side
of
things
like
the
design
team
at
VMware
that
don't
use
this
clarity,
it's
kind
of
like
the
preferred
out
of
those
three
but
kind
of
a
preferred.
One
I
mean
they'll
have
like
their
use
cases
but
help
kind
of
similar,
but
that
one's
pretty
good
cool
awesome.
Thank
you.
B
All
right
so
open,
Q&A
section
this
first
one
is
when
I
put
in
so
we
were
talking
about
Jonas
brought
up
a
point
that
PAC
ndio
documents
have
a
character
limit
and
that
eventually
we
will
run
up
into
that
character.
Limit
at
some
point,
one
of
the
other
another
open
source
project
that
Jonas
is
involved
with
Valero
has
done
that
exact
thing.
So
we
are
I,
think
what
we
are
likely
going
to
start
doing
is
win
when
the
video
lands
in
YouTube,
which
is
currently
a
manual
process.
B
A
Can
I
can
provide
some
some
feedback
there,
so
what
we
did
for
the
other
open
source
project
was
that
we
we
continued
to
use
the
the
current
hack
MD.
We
just
copied
everything
over
to
another
one
that
we
called
archive
the
it's
a
clumsy
way
it
worked.
We
didn't
have
to
update
any
links,
people
who
had
bookmarked
the
the
previous
community,
meaning
notes,
still
get
to
them.
A
A
B
I
really
like
the
idea
of
it
going
into
the
wiki
I
and
also
part
of
my
reason
for
not
for
wanting
to
keep
use.
This
was
we
didn't
have
to
changing
links.
So
if
we
just
if
we
just
take
the
info,
that's
here
and
migrate
it
to
the
wiki
yeah
I
guess
it
means
that
anyone
who's
linked
directly
to
one
of
the
headings
in
this
agenda.
Would
those
links
would
break
I.
Think
that
would
be
rare,
yeah
I
do
too
so.
Okay,
yeah
I
think
I.
Think
I
like
that,
with
adding
them
to
the
wiki.