►
From YouTube: Octant Community Meeting - May 13, 2020
Description
May 13, 2020
Agenda
Demo
- Demo of plugin docs, work in progress.
- Demo of current master.
B
So
there's
a
fee
and
mostly
I'm,
just
running
dance.
So
last
week
we
talked
about
some
of
the
features
that
we've
been
working
on.
Most
of
those
have
landed
and
merged.
Some
of
them
are
real
close
and
have
been
there.
They're
currently
merge
into
the
branch
that
I'm
showing
here,
but
I
just
wanted
to
walk
through
some
of
those
features,
so
people
could
see
what
we
were
going
to
be
doing
so.
B
The
one
that's
pretty
neat
that
is
this
really
easy
to
show,
is
Brian
recently
added
some
status
around
deletes,
and
so
it's
it
it's
pretty
great,
because
you
get
counting
some
instant
feedback
as
you
as
you're,
working
with
your
resources.
So
now,
when
you,
for
example,
like
delete
this
pod,
you
can
see
that
here's,
the
one
that's
being
deleted,
here's
the
new
one
that
got
created
and
then
this
this
is
all
just
running
refreshing.
So
when
that,
when
that
resource
is
finally
cleaned
up
and
out
of
the
system,
it
will,
you
know,
go
away.
B
The
the
cool
part
about
this
is
that
when
you
start
to
get
into
deleting
lots
of
things
it
it,
you
can
kind
of
get
a
good
insight
into
how
all
these
things
interact
with
each
other
so
see
just
there
goes
it's
gone.
So
what
I
wanted
to
show
was
like,
for
example,
some
folks
have
talked
what
they
were
asking
about
like
how
do
I
delete
multiple
things
right,
I,
I'm,
sick
of
having
to
go
through
and
and-
and
you
know,
I
want
to
I-
don't
have
to
delete
all
these
pods
one
at
a
time.
B
Well,
that's
that's
kind
of
why
we
we
show
the
all
of
these
things
under
your
workload.
So
what
I'm
doing
here
is
I'm
filtering
my
workload
down
to
the
one
I'm
interested
in
this
case.
It's
this
quar
deployment
that
I
have
and
by
filtering
with
this
label,
I'm
able
to
see
the
deployment
the
pods
and
the
replica
set
that
represent
those
pods.
So,
for
example,
say
I
I
came
into
here,
I
added
a
couple
more
replica
sets
to
to
my
deployment
it
scaled
up
to
five
and
then
I
was
like.
B
Oh,
you
know
what,
when
I
scale
up
to
five,
it
grabbed
a
new
image.
My
my
my
image,
fetch
setting,
is
set
to.
Never
so
my
old
ones
didn't
you
know
they
didn't
update
so
I
wanna.
What
I
want
to
do
is
I
want
to
delete
all
of
these
pods
yeah
I
could
go
through
one
of
the
time
or
the
option
is
to
just
delete
the
replica
set.
That
is
controlling
them
right.
All
these
will
get
wiped
out.
B
My
deployment
is
still
there,
so
it
will
do
what
it's
supposed
to
do
and
attempt
to
recreate
the
replica
set
and
recreate
all
of
the
pods.
So
in
a
short
period
of
time
here
we'll
see
them
all
come
back
online.
You
see
the
ages
have
all
updated
to
all
being
restarted
and
now
we're
now.
All
of
these
are
running
on
that
new,
that
new
image
and
I
only
had
to
do
a
single
action
item.
So
that's
just
one
of
the
ways
that
we're
kind
of
giving
you
some
more
visual
feedback
around.
B
What's
going
on
as
you're
working
through
different
things
in
the
clusters,
you're
taking
actions
against
your
resources,
but
also
it's
now
that
we're
adding
some
of
these
features
you're
starting
to
see
why
we've
been
displaying
things
in
the
way
we
have
and
why
we
weren't,
hiding
certain
elements.
So
having
access
to
that
replica
set
is
what
gives
us
the
ability
to
easily
delete
a
large
set
of
pods
all
in
one
swoop,
so
that's
feature
is,
is
going
to
be
in
the
next
release.
It's
currently,
the
PR
is
up.
B
It's
approved,
it'll
be
merged
here
very
shortly,
so
it'll
probably
end
up
as
part
of
the
nightly.
There
is
some
more
work
we
want
to
do
around
it
specifically
around
changing
some
of
the
styling
and
getting
some
of
the
phase
or
the
status
of
those
objects
as
they're
being
deleted,
making
it
a
little
more
apparent
that
this
is.
This
is
kind
of
a
throwback
to
some
of
the
old
issues.
B
We
have
open
around
object,
status
and
pod
conditions
and
other
things
where
right
now
we're
not
doing
as
good
of
a
job
as
we
as
we
want
to
be
doing
around
like
the
actual
status
of
like
a
specific
pod
or
object.
So
there's
some
more
work
work.
We
we
have
in
the
key
around
that
and
as
we
as
we
progress
on
that,
we'll
start
to
see
a
you
know,
a
better
kind
of
better
view
of
what's
actually
happening
with
an
object
in
more
real-time.
B
C
You
missed
the
other
part
of
it
feature,
so
this
is
the
hard
piece.
How
do
we
make
things
obvious?
So
you
notice
on
the
left,
there's
a
green
button,
there's
green
that
it,
that
is
the
object
status.
Click
on
that,
oh
that
actually
won't
show
anything
for
pods
click
on
the
one
for
deployment
yeah,
so
you
notice
it
just
says:
deployment
is
okay.
That
is
actually
the
same.
If
you
click
on
the
deployment
name
now,
and
then
you
go
to
the
resource
viewer
and
you
click
on
that
and
notice.
That
says
deployment
is
OK.
C
It's
actually
the
same
thing.
So
one
of
the
ideas
here
was
to
be
able
to
show
more
information
and
at
would
look
less
clicks
because
not
everybody
goes
to
the
resource
for
you
at
first
I
kind
of
do,
but
that
that
homepage
right
there
now
for
every
single
item
that
we're
showing
something
like
whenever
that
goes
red
and
you
click
on
them
it'll.
C
Actually
they
might
not
show
up.
But
if
you
click
now
you
see
it
for
the
deployment,
the
deployments
gonna
say:
hey
in
real
time.
It's
like
I'm,
not
you're,
not
happy
I'm,
not
happy
I'm
happy.
So
that's
something
I'm
trying
to
figure
out.
You
know
what
does
that?
Look
like
the
colors
are
weird
I'm
a
programmer,
not
a
designer,
and
so
it's
better
than
it
was.
It
was
just
like
this
weird
barber
pole
thing,
but
that
didn't
really
port
over
to
the
light
background.
So
I
just
made
it
I
just
made
it
a
solid
color.
C
So
pretty
cool
thing,
and
just
this
is
like
in
the
theme
of
let's,
let's
tighten
up
the
front
end
as
much
as
we
can
right
now.
You
won't
be
able
to
see
this,
but
all
these
things
on
this
screen
are
made
by
these
things.
We
called
printers-
and
we
started
with
this
couple
years
ago
in
a
little
bit
of
a
9th
place
and
now
I
think
we're
we're
going
to
actually
make
this
all
better
less
code.
So
it's
gonna
make
me
happy.
C
B
Yeah
thanks
Bram
yeah,
so
that
that's
coming,
and
so
the
next
thing
I
wanted
to
show.
This
is
something
that
Sam
had
worked
on
recently,
and
it
is
actually.
This
might
be
a
bad
example
of
it,
because
I
think
there's
only
a
single
container
here,
yeah,
but
some
folks
have
been
asking
about
how
to
get
to
like
they
have
pod.
It
has
multiple
containers
and
they
want
to
be
able
to
get
to
different
containers
within
the
terminal.
So
we
still
default
to
the
first
container.
That
is
in
the
list.
B
B
If
for
folks
who
remember
their
original
terminal
interface,
it
was
you
used
to
be
in
here
on
this
container
page
and
you
would
click
execute
and
it
would
pop
up
this
dialog
and
you
would
have
all
these
options
that
were
confusing
and
hard
to
get
like
you
had
to
make
a
bunch
of
decisions,
so
we've
been
slowly
adding
back
in
those
options
but
with
same
defaults
and
without
having
to
without
people
having
to
jump
through
hoops
to
kind
of
understand
what
they
want.
So
now
you
can.
Click
on
a
terminal
looks
like
I.
B
Have
a
bug,
of
course,
try
different.
You
can
click
on
there
when
you
go
into
the
terminal.
You'll
have
a
drop-down
and
you'll
be
able
to
select
through
the
different
containers.
So
that's
something
that
a
few
folks
have
asked
for,
so
it
sits
in
there
now.
The
other,
pretty
cool
thing
is
this:
is
a
lot
of
people
were
hitting
this
before
I
mean
I,
think
it's
cool,
but
because
it
just
fixed
it
and
things
network.
But
before,
if
you
had
unclaimed
persistent
volumes,
let
me
get
rid
of
my
label
there.
This
would
actually
crash
octave.
B
It
would
throw
500
and
and
panic
and-
and
it
was
not
great
so
now
you
can
see
that
this
is
pending.
No
one
has
claimed
it,
so
you
can
go
in
and
actually
look
through
unclaimed,
persistent
volumes
and,
and
then
you
can
now
just
apply
this
so
now
you
can
see
that
this
nginx
is
started,
saying
that
it's
bound
now
and
it's
all
there.
So
you
can.
You
can
see
this
stuff
happening
now
in
real
time
when
we
first
put
in
the
the
viewer
for
the
persistent
volume
claims.
B
If
stuff
was
impending,
it
didn't
show
up,
and
then
we
add
we
fixed
that,
but
then,
when
it
showed
up
well,
it's
still
in
show
up
when
we
fixed
that
there
was
some
status
issues
that
we
didn't
account
for.
That
would
cause
it
to
to
crash
the
view,
and
now
everything
is
working
great.
So
that's
a
pretty
neat
like
it's.
It's
a
pretty
important
fix.
It's
not
neat!
B
C
Should
have
object
status
for
Purvis
in
a
persistent
volume
claim,
we
should
probably
put
that
in
there
to
make
it
show
a
it's
not
bound.
This
thing
is
not
going
to
work
like
you
think
it
will
yeah
yeah.
That's
a
good
idea.
I
wonder
you
know
the
yeah
selfishly,
let
me
say
the
histor
history
of
this,
the
history
of
this.
B
That's
grab
well,
I.
Think
well
well
want
to
do
that,
we'll
create
an
issue
for
it,
so
that
we
can
remember
to
do
it
and
then
the
final
thing
that
we
did
recently,
where
is
it
you
know,
I
saw
I
closed.
My
notes,
there's
my
problem.
I
had
a
note
of
everything
that
we
did
it's
in
the
it's
in
actually
the
overview
that
that
would
be
the
the
markdown.
B
C
C
Useful
that
feature
is
super
useful
that
came
from
I
was
doing
teach
TGI
K
two
weeks
in
a
row
and
the
first
time
I
might
I
can't
see
this
and
I
need
to
know
what
this
is
so
I
went
looked,
and
this
funny
thing
is
this
is
how
coding
goes.
It
was
mostly
in
there,
like
mostly
who's
some
reason
it
got
disabled
and
so
I
went
there.
I
cleaned
it
back
up,
turn
it
back
on
and
added
secrets.
So
now
it's
pretty
nice
that
that
shows
up
there.
B
So
now
when
you
request
the
next
page
and
you
look
at
the
headers,
you
will
see
that
the
cache
control
now
contains
the
no
cash
and
no
store
for
the
index.
Page
I
mentioned
this
at
the
last
at
the
last
community
meeting,
but
this
will
fix
the
problem
so
once
this
release
goes
out
and
folks
do
another
hard
refresh,
we
will
no
longer
after
that
be
caching.
This
index
page,
which
means
people
will
no
longer
have
to
hard
refresh
to
get
any
of
the
UI
changes
that
we
make.
B
We
know
that
this
has
been
a
constant
like
point
of
frustration.
We
get,
we
get
every
time
we
do
a
new
release.
We
get
at
least
three
or
four
issues
being
open,
saying
that
this
tab
is
broke
or
these
don't
work
and
and
it's
because
the
old
UI
is
still
trying
to
consume
it's
trying
to
consume
the
new
API
stream
and
those
things
don't
align
and
it
causes
things
to
break.
B
So
people
no
longer
have
to
do
a
hard
refresh
after
they
get
this
release
and
they
do
a
hardware
fracture,
which
will
be
very
nice
for
everyone,
including
us
that
is
all
I
had
for
the
main
octant
demo
piece.
I
wanted
Sam
to
show
off
the
the
work
that
he's
been
doing
with
the
plugin
documentation,
because
it's
pretty
neat
and
it's
coming
it's
coming
along.
Well.
So
if
you
don't
mind
doing
that,
Sam
that'd
be
great
cool.
D
E
D
Cool,
so
this
is
going
to
be
a
component
reference
for
octant,
especially
around
plugins,
because
what
often
really
does
is
it
uses
the
clarity
library
for
the
front
end,
and
all
of
that
is
really
just
taken
away
from
the
user.
They're
just
writing
go
and
they
spit
out
these
components.
Using
clarity,
and
so
one
thing
that
we
really
struggled
with
was
how
to
how
to
show
what
a
plug-in
might
look
like
without
actually
having
to
write
the
code,
and
what
this
essentially
does
is
give
the
users
a
chance
to
say
hey.
D
D
In
this
case,
it's
a
button
and
if
they
hit
the
delete,
modal
and
it'll
show
that
go
code
that
will
be
used
in
a
plugin
and
also
a
JSON
reference,
and
this
is
really
for
the
more
advanced
users
who
might
be
attempting
to
do
this
in
a
language
other
than
go,
and
if
they
can
construct
this
JSON
schema.
They
could
also
recreate
this
delete
button
if
they
wanted
to
and
pretty
much
we
went
through
and
went
and
went
and
did
this
for
almost
every
component.
This
isn't
live
anywhere.
D
Yet
this
is
done
an
Elif
I
and
for
our
repo,
what
we'll
actually
end
up
doing
is
taking
out
the
net
effect
configuration
because
this
will
still
be
used
in
a
sort
of
an
Amana
repo.
So
nullify
gets
confused
if
you
have
a
single
configuration
file
in
the
root
directory,
so
we'll
be
a
little
bit
more
reluctant
on
the
UI.
F
This
is
amazing
by
the
way
he's
gonna
help
us
a
lot,
especially
when
we
have
our
rockton
hackathon
in
June,
like
by
the
way
you
guys
don't
remember.
The
date
is
I
mean
it's
coming
up
it's
in
a
month,
so
the
dates
are
June
17th
to
June
23rd.
It
is
gonna,
be
huge.
It's
gonna
help
people
figure
out,
you
know,
and
in
Connecticut
on
how
to
build
a
parking
yeah.
B
We
had
to
continue
on
that.
We
have
issues
right
now
that
are
currently
in
progress
that
are
specific
around
this
documentation
is
saying
now
a
better
getting
started
page
for
plugin
authors
as
well
as
a
better
getting
started
page
for
folks
who
want
to
get
octant
installed,
but
are
more
of
an
advanced
user,
and
once
you
get
it
installed
from
source,
so
they
can
write
plugins
or
hack
on
things.
So
all
of
those
issues
are
currently
in
progress
and
the
goal
is
to
have
a
much
better
documentation,
including
this
plugin
preview.
Already
for
the
hackathon.
D
Yeah
and
quick
shout
out
to
the
team,
I
think
documentation
wise.
This
is
pretty
cool,
because
this
is
the
first
thing
I've
worked
on
where
we
all
said
all
right:
let's
just
sit
together
for
a
couple
hours
and
not
to
sound
problem
and
I'm
behind
it,
and
it's
something
that
I
don't
think
it's
very
common
among
engineering
teams,
so
Thank
You
Wayne
for
jumping
in
on
that
sprint
and
getting
the
ball
rolling
on
this.
That's.
F
Awesome,
thank
you
and
by
the
way
we
have
a
dog
rider.
That
is,
you
know
our
extended
team
now.
So
if
we
need
some
other
resource
like
with
someone
to
another
pair
of
eyeballs
or
someone
to
help
us
write
some
more
things,
please
bubble
it
up.
Some
talk
to
Stephanie
and
she
can
work
with
a
month
and
figure
out
when
and
where
we
can
get
some
of
those
resources.
So
I
know
it's
not
the
core
skill
set.
The
roller
has
engineers
to
actually
write
dogs
and
write
these
things.
Sometimes
it's
fun.
C
B
C
B
C
C
Another
idea
that
I
had
is
that
we're
not
front-end
people,
which
is
probably
pretty
avid
evident
but
in
front
of
people
like
this
thing
called
story
boards
and
what
story
boards
are
are
a
way
for
us
to
experiment
with
a
lot
of
the
front-end
code
without
putting
it
in
the
app.
So
we
can,
we
can
just
set
up
scenarios
for
it,
so
that
actually
should
be
hitting
I
should
be
hitting
master
soon
and
I.
C
We
can
show
we
can
show
a
lot
more
things
being
used
because
sometimes
there's
a
there's,
definitely
a
big
gap,
Queen
what's
possible
and
then
what
you
think
you
can
do,
and
we
can
probably
show
a
lot
of
that
in
a
better
fashion
and
we're
getting
to
the
point
where
some
of
these
so
many
things
they
want
to
do
in
the
front
end
are
bigger
than
one
commit
or
two
commits.
So
we
we
need
some
place
to
stage
these
things.
B
Yeah,
that's
great
I'm
gonna,
look
forward
to
that
I.
We
also
talked
about
potentially
generating
I,
think
touching
on
what
you
were
saying,
generating
some
of
this,
both
directions
so
that
you
could
have
a
tool
where
plugin
authors
were
essentially
able
to
sketch
out
what
their
UI
would
look
like
right.
C
I
wasn't
going
to
surprise
you
with
this,
but
you'll
probably
see
it
pretty
soon,
all
on
the
back
end,
all
of
our
all
of
the
models
for
what
we're
using
so
all
the
translations
of
these
models.
So
for
button
group
and
in
table
and
data
great.
And
what
not
are
we
maintain
them
in
the
go,
and
we
also
maintain
the
typescript
version.
We
have
enough
code
to
generate
them
so
we'll
probably
just
start
maintaining
them
in
the
go
and
we'll
use
a
generator
to
generate
the
typescript
yep
and
and
and
make
that
work.
B
C
C
About
that
client
thing,
I
was
writing.
I
did
just
briefly.
I
mentioned
it
out
of
business.
There's
no
update,
I
literally,
have
not
touched
it
in
a
whole
week,
but
I,
but
I'm.
The
reason
I
haven't
been
is
because
I've
been
working
on
this
other
thing,
because
one
thing
we're
trying
to
do
with
kubernetes
is
kubernetes
is
not
made
for
you
eyes
and
we
made.
C
So
I
want
to
get
us
to
the
point
where
we
don't
have
to
cheat
on
the
edge
and
we
have
a
client
that
is
closer
to
what
we
actually
need
and
does
not
contains
all
the
complexities,
because
we're
using
client
go
there's
a
lot
of
complexity
all
throughout
the
app
just
because
of
the
way
client
guy
works,
medicine,
experiment
and
I.
Think
another
couple
weeks
might
actually
put
it
inside
of
octant
to
start
to
start
testing
it
out
to
see
what
it
can.
F
Sounds
fun
I've
one
request,
maybe
Wayne
you
and
and
Sam
and
Stephanie
and
Milan
can
huddle
together
and
figure
it
out.
Are
there
any
fixes
or
improvements
that
we
need
to
add
you
know
I.
We
talked
a
little
about
the
plugin
experience
and
the
work
that
you
you
all
are
doing.
Some
leading
that's
great
right.
Is
there
anything
else
we
need
to
look
at
before
we
actually
get
the
hackathon
I've
been
running?
Is
there
anything
that
you
know
little
things
like
this
is
like
death
by
thousand
cards.
I.
F
Think
Brian
and
I
talked
about
it
a
few
weeks
ago
as
well
like
there
little
things
that
you
can
improve.
That
will
make
everybody's
lives
easier,
they're,
not
individually,
they're,
not
big
items
and
not
important,
but
when
you
consider
them
all
they
they
do
have
an
impact.
Maybe
that's
something
to
think
about.
C
C
There's
no
guarantee
I
mean
there
is
guarantee
that
we'll
have
a
method.
For
extension,
then
it'll
be
very
close
to
what
we
have
now
it'll
look
close
to
what
we
have
now,
but
there
will
be
no
guarantees
that
there
are
plugins
will
continue
on
as
they
are
now
because
just
might
might
not
be
tenable,
especially
in
cluster
it.
Just
it's
not
gonna
be
tenable
so
way
and
I.
We
talked
a
few
times
every
week
and
ideas
are
flowing.
So
just
keep
that
in
mind.
F
Yeah
I
mean
that
makes
sense,
but
you
know
running
in
cluster
is
months
away
from
now,
and
you
know
an
effort
for
us
to
bring
more
folks
to
the
octan
community.
We
need
to
make
sure
that
you
know
get
more
eyeballs
on
it,
and
this
hike
I
know
is
gonna,
be
a
great
way.
Would
people
need
to
go
and
rework
some
of
their
plugins
in
the
new
architecture
that
could
be
in
cluster
or
would
they
have
to?
We
have
to
give
them
some
automation
that
will
transfer
them
from
go
to
Python
or
something
else.
F
Maybe
people
will
not
put
caveat,
sir,
that
this
is
pretty
wonder,
though
some
things
are
subject
to
change,
but
you
know
octane
is
there
today
is
available,
it
can
deliver
value,
come
and
write
your
octants
and
you
get
to
do
basically
either
automate
or
make
easier
visualizations
from
solid
things
that
people
that
are
important
to
certain
folks
and
we'll
take
it
from
there.
I
mean
there's
caveats
to
it
totally
agree.
All
right
sounds
good.
F
F
B
Well,
that
there's
link
oh
yeah
yeah,
as
Brian
said
we
are
thinking
about
plugins.
We
know
that
people
have
plugins
that
they've
created
now
that
are
popular.
That
folks,
like
we
are
not
going
just
gonna
leave
people
on
alerts
right,
we're
gonna.
There
will
be
some
Pat,
we
don't
know
what
it
looks
like.
We
have
no
clue
what
it
looks
like
yet,
but
there
will
be
some
paths
to
make
sure
that
current
plugins
can
operate
in
this
new
world
either.
B
Automated
manual
documented
whatever
there'll
be
some
path
to
get
you
there
and
so
yeah.
We.
We
still
wanted
to
encourage
folks
to
write
plugins,
but
but,
as
Brian
said,
we
want
to
be
very
clear
that
we
are
especially
with
adding
in
cluster
it's
very
early
and
things
are
things
are
kind
of
up
in
the
air
and
but
we're
not
gonna
we're
not
just
gonna
abandon
people
who've
created
plugins
already,
where
it's
gonna
yeah
we'll
be
there
so
and.
F
C
F
So
so
that's
that's.
Actually
a
huge
net
benefit
like
we
wanna
get
more
eyeballs
on
this
from
the
you
know,
doesn't
hurt
to
you,
know,
get
it
out,
get
our
name
out
there,
pretty
much
you
fellow
as
soon
as
we
actually
create
the
posters.
So
Amanda
is
working
with
some
of
the
branding
folks
to
create
a
poster.
As
soon
as
you
do
that
it's
kind
of
going
everywhere,
TK
g
t,
TK,
t
GI
k
all
of
the
kubernetes
development
for
homes.
We're
gonna
push
it
to
everybody,
hey
you're,
interesting!
This
come
bus
ride.