►
From YouTube: Octant Community Meeting - September 16, 2020
Description
September 16, 2020
Agenda
- Octant 0.16 release update
- Feature to manage quotas/limit range for each namespace?
- Idea: Navigation to take up entire height of viewport
A
Okay,
welcome
everybody
to
the
september
16th
2020
octa
community
meeting,
we're
back
from
a
break
from
last
week
about
half
the
team
was
out
last
week,
so
we
just
postponed
and
canceled
not
postponed.
It
happens
every
week,
canceled
it
and
and
decided.
We
would
come
back
this
week.
So
we've
got
a
few
things
that
we
want
to
talk
about
today.
I'm
gonna
go
over
kind
of
what
our
upcoming
plan
is
for
odot
16..
A
I
think
sam
was
wanting
to
have
a
discussion
about
some
features
for
quotas
and
and
limit
range,
and
then
I
either
sam
or
milan.
I
probably
milan.
I
think
this
one
came
up
in
an
issue.
He
was
looking
at
to
talk
about
the
navigation
height
of
the
viewport.
So
with
that
we
will
we'll
get
started.
So,
oh,
not
16.,
it
is
it's
coming.
A
A
I
think
likely
this
1305,
which
is
the
modal
component
from
sam.
There
is
this
one
from
brian,
which
is
1341,
I'm
not
sure
that
this
will
go
into
0.16
this
one
here
is.
Is
we
have
the
slider
view?
That's
currently
in
octane,
which
extends
up
from
the
bottom?
It
didn't
get
a
whole
lot
of
use.
We
we
had
planned
to
use
it
for
some
various
things.
We
briefly
used
it
for
terminal
windows.
A
Brian
has
refactored
it
into
being
a
little
bit
more
of
a
useful
component
and
not
so
dependent
on
needing
content.
So
now
there's
just
this
more
generic
bottom
panel
that
then
you
can
place
custom
content
into
similar
to,
like
think
of
flex
layouts
within
octant,
where
you
can
just
kind
of
pack
in
any
content
that
you
want,
that
pr
is
kind
of
turning
that
bottom
area
into
essentially
a
tabbed
area
for
flex
layouts,
and
it
will
make
it
generally
more
useful.
A
The
idea
is
that
we're
going
to
be
showing
air,
initially
error,
messages
and
events
in
that
area,
which
is
needed
to
get
us
able
to
start
releasing
octant
as
a
application
instead
of
as
a
terminal
app.
So
the
other
thing
that
we
want
to
we'll-
probably
prob-
maybe
milan,
can
maybe
add
some
more
to
this.
But
there
is
the
a
new
view
for
a
resource
viewer
that
we
are
going
to
be
putting
behind
a
feature
flag
and
I
think
that
will
go
into
this.
0.16
isn't
belong.
A
B
All
right
we're
going
to
hold
that
one
back
so
yeah.
It's
basically
going
to
be
feature
flag
for
the
new
resource
viewer,
but
getting
in
a
state
where
it's
useful
and
it's
good
to
compare.
It
still
requires
a
little
bit
of
work,
especially.
We
change
the
interfaces
on
the
back
end
side.
So,
okay,
it's
gonna,
be
a
bit
of
effort
to
collect
them.
A
A
A
A
So
those
those
things
are
yeah,
I
would
say
they're
they're
addressed
they're,
not
in
their
final
form,
but
they
are
addressed
with
respect
to
what
we
were
encountering
during
our
testing
and
during
some
of
the
the
new
updates
we
made.
I
think
those
those
things
are
fixed.
So
is
there
anything
that
I'm
not
that
I'm
missing
for
the
odot
16
that
we're
waiting
on.
A
C
C
I'll
probably
have
to
do
some
research
on
on
whether
or
not
these
are
actually
first
class
objects
in
kubernetes.
I
don't
know
off
the
top
of
my
head,
but
they
were,
but
we
would
have
them
listed
out
somewhere
and
I'm
not
sure
if
it
should
just
be
create
another
action
or
it
should
be
another
form,
because
now
we're.
C
C
Or
we
have
different
ways
of
creating
objects,
and
so
this
is
something
that
we
should
start
to
think
about.
So
I
don't
imagine
this
is
something
that's
very
difficult
to
do.
I
think
it's
something
that
we
could
probably
put
in
for
the
next
release,
not
not
the
one
that's
coming
out
this
week,
but
one
after
that,
but
this
but
moving
forward.
C
C
A
C
Idea,
yeah,
I
don't
have
anything
else
for
that
one,
but
I
also
wrote
the
idea
navigation
to
take
up
the
entire
height
of
viewports
so
for
moving
on.
I
can
also
add
some
words
to
that
one.
Yeah
yeah
that'd
be
great
yes,
so
this
one
was
just
more
of
a
random
thought
that
I
had
the
other
day,
but
currently
on
the
top
left
corner
of
octan.
We
have
the
logo
and
octan,
and
I
tend
to
use
that
a
lot
just
to
navigate
back
to
overview,
not
not
so
much
as
that.
C
It's
like
representative
of
anything,
but
then
I
figured
it
might
just
be
bad
ui
like
that's
what
the
quick
switcher
is
for
I'd
assume
or
maybe
even
just
having
the
side
nav
to
do
it,
because
right
now,
it's
also
really
weird.
If
you
click
that
top
left
button,
it
actually
loads
the
page
twice
it
loads
back
to
the
root
path,
and
then
it
tries
to
go
to
overview
name
space
and
then
your
default
name
space.
C
So
it's
not
something
that's
great
to
begin
with,
but
also,
I
think
like
when
you're
in
an
application
like
they
know
it's
octan
and
the
logo
is
already
there.
So
it's
like
it's
like
free
space
that
we're
not
totally
using,
and
I
could
totally
see
like
a
version
of
octane,
where
we
just
have
that
left
that
expandable
navigation
take
up
the
entire
left
side.
C
A
Yeah,
no,
that
makes
sense.
I
think
that
so
one
of
the
things
that
came
up
the
last
time,
brian
and
I
were
talking-
is
that
if
you
look
at
vcenter
and
vsphere
as
an
example
of
how
they
do
their
layouts,
it's
interesting
because
they
have
they
have
a
similar
thing
where
they
have
these
these
this
menu.
A
You
know
like
like,
like
an
unfolding,
a
telescope
kind
of
like
and
and
the
nice
thing
about
that
pattern
is
that
then
we
we
get
away
from
having
to
worry
about,
like
all
of
this
height,
like
as
modules,
get
added
and
things
get
added
in
here.
There's
there's
not
this
because,
because
all
of
that
height
is
going
to
go
to
the
next
panel
right,
and
so
we
could
play
with
that
idea
as
well
when
we're
when
we're
looking
at
like
what?
B
Right,
I
actually
spent
a
good
part
of
this
morning
chatting
with
brian
about
this,
and
I
mean
I
I'm
kind
of
torn
on
this.
I
really
like
the
simplicity
of
current
approach,
and
so
you
know
the
idea
is
that
the
way
that
navigation
works
currently
basically
for
advanced
users,
which
is
the
compressed
view
like
that,
it
just
tries
to
get
away
from
you.
You
know,
so
it
doesn't
take
too
much
space,
and
I
was
looking
at
this
v
sphere,
currently
navigation.
B
So
you
know,
I
think
I
would
call
openly
for
all
you
know,
ideas
and
suggestions
like
this
one
that
sam
just
mentioned
this
it's,
I
think,
a
really
good
one.
So
maybe
we
should
try
to
figure
out
what
are
the
problems
we're
trying
to?
So
what
other
problems
are?
The
current
navigation,
if
you
start
with
that
and
try
to
you
know,
find
the
best
ways
to
approach
that
and
and
to
solve.
A
Them
yeah
yeah.
I
know
I
agree
that
it's
not
it's,
it's
not
a
it's,
not
a
straightforward
problem.
I
think
it's
going
to
take
some
exploration
and
I
wonder
if
we
can.
You
know
sam
mentioned
the
quick
switcher
and
I
was
I
was
thinking
like
so
we
have
that
I
had
to
look
up
what
it
was.
We
have
the
quick
switcher
and
I'm
wondering
like
is
it?
Is
it
too.
A
Like
because,
because
I'm
thinking
like,
if
I'm,
if
I
am,
you
know,
if
I
just
want
to
go
back
to
the
main
like
we,
we
we
make
whatever
the
default
so
like
right
now,
you
click
on
this
and
and
yeah.
It
goes
to
overview
names.
It
goes
to
whatever
name
space
you
have
selected
and
it
goes
to
the
namespace
overview.
So
if
we
could,
if
we
could
make
it
so
that
the
namespace
overview
is
the
first
option
in
the
quick
switcher,
it
also
would
expose
the
quick
switcher
to
more
people.
A
B
I
I
think
the
biggest
problem
with
current
navigation
is:
if
we
have
too
many
items
they
get
off
the
screen,
especially
that's
going
to
be
important
now,
because
we
have
a
lot
of
plugins
and
I
there
are
a
few
different
ways
to
solve
that.
One
of
them
might
be.
You
know
if
you
look
at
the
slack,
for
example
it
they.
B
They
added
that
left
area
where
you
can
kind
of
check
the
group,
so
imagine
left
from
our
icons
is
another
vertical
tiny,
vertical
menu
that
gives
you
three
or
four
right
once
more,
the
top
one
might
be.
You
know
in
cluster
operation,
the
second
one
cluster
based
and
plugins,
and
so
on,
so
that
will
limit
the
number
of
total
number
of
items
in
the
in
the
whole
navigation
and
that
will
kind
of
give
us
very
much
space
and
reduce
the
clutter
a
little
bit
so
that
that
is
one
thing
I
was
thinking
about.
B
The
other
way
to
solve
the
the
problem
with
too
many
items
is
at
the
very
bottom.
We
can
add
something
like
show
more
or
show
less
and
that
will
open
a
whole
other
set
of
it
almost
like
a
floating
menu.
If
you
click
on
show
more
everything,
that's
missing
show
up
as
a
as
a
floating
man
or
something
like
that.
So
just
some
of
the
ideas
I
was
considering.
A
Yeah
I
mean
I
think
this
area
is
ripe
for
for
exploration
like
we
can
try
some
different
things
and,
and
it
the
the
interesting
thing
about
navigation,
is
that
it
it
it's
a
pretty
it's
one
of
those
things
where
it's
like
it's
a
non-obvious
solution,
but
the
non-solutions
are
very
obvious
like
when
you
try
something
new
and
you're
like
no.
That's
not
it
like.
You
know
pretty
immediately
that
that
way
of
doing
something
like
if
you're,
trying
to
tweak
navigation,
isn't
gonna
work,
and
so
I
think
we
can
yeah.