►
From YouTube: Octant Community Meeting - July 7th, 2021
Description
Octant community meeting is held weekly. We discuss and talk about the current state and future of Octant, demo upcoming features and releases, and preview new ideas we are considering for Octant.
Meeting agenda: https://hackmd.io/CzaPxtmXT_SW8nEpdwvGzw?view
A
Hello,
everybody
and
welcome
to
the
july
7th
octant
community
meeting
today
we
have
a
fairly
short
just
set
of
status
updates
and
then,
if
folks
have
anything
for
open
q,
a
we'll
cover
that
but
feel
free
to
pull
up
the
agenda
as
always
and
add
things
as
we
are
going
over
them.
I
will
go
ahead
and
share
my
screen
and
we
can
start
going
through
some
of
these.
A
Okay,
so
I
just
wanted
to
call
out
that
the
the
team
itself
has
been
on
kind
of
a
bit
of
a
reduced
capacity.
I
was,
I
was
out
sick
recently
and
we've
had
some
folks
on
vacation.
So
I
just
wanted
to
just
kind
of
highlight
that
and
say
like
expect
things,
if
you
notice
things
were
a
little
slow
last
week,
expect
them
to
maybe
be
a
little
slow
this
week
as
well.
A
Just
kind
of
folks
are
trying
to
recover
and
and
get
back
to
get
back
from
vacations
and
get
settled
in
so
yeah.
Don't
really
have
much
more
to
add
there
just
wanted
to
call
that
out.
The
next
thing
in
our
status,
update
is
o.22
is
releasing
july
13th.
We
talked
about
this
at
the
last
community
meeting
where
we
were
going
to
potentially
create
a
odot,
well
we're
looking
at
creating
an
0
21.1.
A
Ultimately,
we
kind
of
looked
at
what
we
were
going
to
be
doing
for
that
odot
21.1
and
looking
at
what
we
wanted
to
do,
for
planning
for
the
actual
next
set
of
features
and
and
the
next
release
after
that
and
ultimately
decided
that
we're
going
to
make
0.22
the
next
release.
We
do,
which
it
will
have
some
api
enhancements
for
using
actions
as
a
library,
some
improvements
and
fixes
for
the
typescript,
plugin
and
ap
and
library
generation,
and
then
just
a
host
of
various
bug,
fixes
and
quality
of
life.
A
Improvements
will
be
part
of
0.22
and
just
to
kind
of
add
why
we
made
that
decision.
Was
the
we've
been
going
through
this
process
of
doing
some
road
map,
planning
and
updating,
and
we
wanted
to
perform
that
exercise
as
a
team
and
then
also
take
some
time
to
create
some
issues
and
or
update
some
of
our
documents
to
reflect
the
outcomes
of
that.
So
we
haven't,
we
haven't
quite
reached
a
a
set
of
outcomes.
A
Yet
so
I
believe,
where
there's
a
discussion
group
that
will
be
opened
or
is
opened
to
talk
about
roadmap
items,
so
expect
us
to
be
kind
of
calling
that
out
and
and
having
discussions
there,
but
the
goal
is
to
create
some
more
focused
releases
around
a
specific
set
of
core
features
that
will
drive
us
to
know
this
1.0
for
octant
yeah.
Any
anything
anyone
wanted
to
add
to
that.
B
Only
that
they're
you're
right
there
is
a
discussion
open
on
the
on
the
themes.
Just
the
top
level
themes,
rewording
them
for
the
roadmap.
A
Excellent
here
it
is
right
here
yep,
so
I
will
pop
that
into
here.
So
folks
can
find
it
easy.
Whoops.
C
A
And
that
was
that
was
kind
of
it
that
I
had
for
top
agenda
items.
So
I
think
there's
two
things
we
can
do
first,
we'll
see
if
there's
any
other
discussion
points
or
open
q
a
and
then
we
can
use
some
of
this
time
to
actually
maybe
with
the
group.
That's
here
go
through
some
of
the
road
map
items
and
add
a
little
bit
of
detail
as
we
talk
about
each
one
for
folks
who
might
be
interested
in
engaging
in.
A
A
A
Okay,
I'll
take
that
as
a
now
do
you
want
to
take
some
time
to
discuss
this
road
map
we'll
be
visiting
a
little
bit
while
we're
here.
A
Okay,
so
roadmap
for
octet
is
interesting,
so
we
have
a
set
of
existing
themes
which
we've
we've
captured
in
a
roadmap
markdown,
that's
in
our
main
repository
and
once
that
actually
loads
here
very.
A
A
Am
I
still
here:
did
my
internet
go
out
what's
happening
to
get
up,
go
what's
going
on,
okay?
Well,
it's
there.
I
promise
and
the
goal
is
to
kind
of
revisit
some
of
those
themes,
mainly
because
we've
done
some
of
them,
and
I
guess
I
should
say
if
you,
if
you
were
looking
at
the
document,
you
would
see
that
there
there
are
headings
and
then
underneath
those
headings,
there's
essentially
intermixing
of
ideas
and
essentially
tasks
to
be
yeah.
A
Here
it
is
right
here,
so
you
can
see
like
here's,
here's
kind
of
like
these,
these
bigger
things,
and
then
we
have
headings
that
that
add
a
little
bit
more
detail
and
then
some
of
these
get
even
more
fine
grain
and
make
them
almost
explicit
tasks,
whereas
some
of
them
still
kind
of
capture
a
more
high
level
objective
of
like
the
vision
for
octan,
and
so
it's
kind
of
intermixed
throughout
this
document
where
you
may
be
reading
something,
and
you
end
up
with
a
list
of
tasks
or
you
may
be
reading
something
and
end
up
with
a
list
of
of
high-level.
A
You
know,
oh,
what
are
the
what's:
the
vision
for
for
octan
long
term,
and
so
the
goal
of
of
revisiting
this
road
map
was
to
make
sure
that
everything
in
the
roadmap
that
we're
capturing
is
more
along
the
lines
of
that
vision
or
high
level
and
then
letting
that
kind
of
filter
into
the
releases
and
projects
we
create
to
enable
the
you
know
executing
that
high
level
vision.
A
So
across
those
current
themes,
we
have
I'm
just
going
to
kind
of
read
it
out
here,
working
with
kubernetes
workloads.
Answering
the
question:
why
isn't
my
workload
working
extending
octant
to
work
with
any
kubernetes
type?
You
can
read
that
as
both
plug-ins
as
well
as
good
default,
behavior,
it's
a
little
overloaded
and
then
providing
better
defaults
and
then
being
a
better
ecosystem
participant
which
not
it's
it's
an
interesting
and
that
last
one
is
always.
I
have
to
go
look
at
what
we
put
on.
A
I
don't
know
anyway,
some
of
them
are
not
quite
clear,
so,
the
as
a
group
we
were
discussing
hey,
let's,
let's
revisit
these
and
decide.
What
is
that?
What
do
those
things
actually
mean,
and
so
one
of
the
examples
here
that
was
put
in
was
answering
the
question:
why
isn't
my
workload
working
could
be?
You
know
kind
of
translated
into
provide
excellent
kubernetes,
debugging
and
troubleshooting,
which
is?
Is
it
evokes
more
a
more
clear
vision
of
what
that
might
mean
right
like?
A
Why
isn't
my
workload
working
is
kind
of
open
a
little
too
open
and
it's
hard
to
really
create
structure
and
and
like
drive
towards
achieving
that
objective,
whereas
with
the
the
rewording
of
provide
excellent,
kubernetes,
debugging
and
troubleshooting?
Where
now
we
know,
does
this
feature
directly
enable
us
to
debug
or
troubleshoot?
A
It
kind
of
it
just
adds
crazy,
better
definition
of
isn't
working.
So
that
was
that's
the
exercise
we're
looking
at
completing
here
in
the
discussion
and
yeah.
So
I
guess
do
we
want
to.
A
We
can
there's
a
couple
ways
we
could
do
this.
We
could
just
go
through
the
current
themes
and
try
to
create
these.
These
reworded
clear
definitions
for
high
level
road
map
objectives
or
we
could,
I
guess,
that's
the
only
that's
the
only
thing
I
can
think
of
to
do
right
now.
A
I'll
also
go
into
details
of
each
of
the
current
high-level
objectives
and
explain
kind
of
what
they
mean
versus
what
the
what
the,
how
they
currently
are
awarded
or
what
the
tasks
call
out
might
be
within
them.
Whatever
folks
think
would
be
useful.
C
A
Okay,
so
which
for
you
vikram,
which
one
is
the
least
clear
or
or
seems,
the
most
generic
that
would
help.
C
C
A
Yeah,
okay,
yeah
so
providing
better
defaults.
Can
I
can
I
nominate
somebody
to
to
end
the
discussion.
Take
notes
for
these
someone
willing
to
do
that.
I
can
do
that
excellent.
Thank
you.
A
Yeah,
so
on
the
one
of
providing
better
defaults,
the
the
goal
here
is
is
a
couple
things.
One
that
is
called
out
here
is
that,
to
help
users
understand
the
scope
of
their
workloads.
This
is
this.
A
Is
the
the
common
level
point
so
right
now,
if
you
use
these
set
of
recommended,
labels
within
your
application
will
create,
creates
a
view
underneath
what
what
we
call
our
applications
view
on
the
left-hand
menu
and
inside
that
view
is
a
grouping
of
of
your
workload
and
all
of
the
potential
all
of
the
things
that
are
related
to
it,
as
well
as
some
information
around
cpu
and
memory,
and
so
the
better
def,
when
that,
when
this
says
providing
better
defaults,
the
default
is
referring
to
is
the
default
views
within
octant
that
help?
A
You
understand
immediately
how
your
application
is
configured
deployed
and
the
various
components
that
are
connected
to
it,
and
this
goes
so
far
as
to
with
a
go
by
things
like
you
know,
this
was
installed
with
helm,
or
this
was
installed
with
this
tool,
and
this
has
various
metadata
on
it
that
lets
us
infer
that
it
it
can
be
used
this
way
or
that
it
was.
It
is
controlled
by
some
external
controller.
A
So
so
that's
that's
really.
The
the
main
goal
of
providing
better
defaults
is
is
creating
clear
ways
to
visualize
an
application
or
workload
within
your
within
your
cluster
and
then
understand
how
that
workload
is
connected
to
the
to
the
various
components
and
resources
within
the
the
cluster,
because
by
default
it's
really
difficult
to
see
that
you
know
these
things
are
really
kind
of
an
over
overlap
with
with
the
resource
viewer,
but
like.