►
From YouTube: Octant Community Meeting - October 8, 2019
Description
Octant Community Meeting - October 8, 2019
A
Great,
oh
yeah,
sorry
go
ahead.
Wing
yeah,
oh
no
I
was
gonna,
say
yeah
I
was
gonna,
say
what
Jonas
is
about
to
say:
hi.
Everyone
welcome
to
our
second
community
meeting
I
am
when
what
so
an
engineer
on
the
auction
project
and
joined
by
Sam,
foo
and
Jonas
and
Tim.
Think
oh
I
see
Michaels
there
to
you
and
who
else
we
got.
I
can't
hold
on
my
screens
a
little
messed
up,
but
I
feel
like
someone
just
joined,
got
Amanda
on
the
call
Amanda's
here,
yep.
Okay,
great!
A
So
as
for
what's
coming
up
in
ode
on
8
I'm
gonna
go
ahead.
Evans
share
my
screen:
I'll
just
make
it
easy,
so
this
is
our
Zen
hub.
It
is
available
to
people
they'll
take
a
look
at
and
right
now.
This
is
what
we
have
closed
out
for
or
not
eight
technically
Oh
Donna.
It
was
scheduled
to
release
yesterday
we're
probably
going
to
do
it
Thursday
this
week,
just
to
allow
some
time
to
get
some
other
features
in
that
occur.
A
There
were
some
issues
with
adding
external
links
to
the
summary
section
that
some
plugin
author
was
hitting
that's
all
fixed
clicking
through
on
the
heptagons
when
you're,
when
you're
looking
at
the
pod
summary
and
the
resource
viewer
got
fixed,
Sam
added
the
HPA
viewer
to
the
resource
viewer.
We've
got
some
other
this
one
here
in
multiple
cluster
clients.
We
actually
entertained
this
looked
at
it,
but
for
now
we're
going
to
be
shelving
the
idea
of
multiple
clusters
at
once
and
kind
of
keep
octant
two
a
single
cluster
at
a
time.
A
So,
if
you
want
to
be
connecting
to
multiple
clusters,
you'll
just
run
multiple
instances
of
octant
to
do
that.
So
this
was
kind
of
a
PR
that
got
put
up
as
like
a
shim
to
enable
that.
But
then
we
it
turns
out
that
it
it's
just
a
little
more
complex
when
you
actually
start
to
do
it
and
it's
something
that
we
want
to.
A
It's
just
not
something
that
we're
going
to
be
doing
and
in
octant
through
the
for
the
time
being.
So
we
also
thanks
to
Rajah
who
contributed
this
agent
user
agent
PR.
We
got
that
merged
in
that
was
opened
a
while
back,
and
he
recently
made
the
updates
a
couple
of
weeks
back
I
was
at
a
conference
and
Brian
was
traveling,
but
we
were
able
to
get
that
merged
in
today.
A
So
we
really
appreciate
that
contribution
there,
some
other
fixes
for
just
layout
things
and
as
well
as
we
put
in
kind
of
a
temporary
stopgap
for
how
errors
are
handled
specifically
around
access
errors.
We
were
kind
of
spamming,
the
the
console
and
things
were
a
little
hard
to
follow
if
you
were
using
like
a
restricted
context
to
view
a
cluster.
A
So
that
covers
most
of
the
oh
and
a
thing
that
we
landed
just
recently
today.
Actually,
is
we
fixed
the
initial
namespace
flag
there?
There
was
a
couple
errors
around
that
the
initial
namespace
was
still
launching
into
default,
which
was
a
regression
from
a
previous
release
and
then
Sam
also
got
a
fix
in
there,
for
when
you
have
a
bad
name
space
instead
of
just
octant
being
blank,
you
actually
get
a
warning
alert.
A
There
are
some
other
things
that
either
they're
not
showing
up
in
this
list,
just
because
I
haven't
tagged
them
properly,
but
a
learning.
We
have
some
some
proper
alerting
now
because,
as
mentioned
throughout
seven,
we
switched
over
to
WebSockets
and
we
are
able
to
now
do
like
directed
alerts
of
things
that
are
happening.
I
have
I,
can
demo
some
of
that
here
in
a
second
and
I,
think
that
is
kind
of
covers.
A
What's
going
to
be
in
ODOT,
eight,
a
lot
of
a
lot
of
bug
fixes
a
lot
of
eat
like
ease
of
life,
fixes
like
they
make
things
easier
for
people
and
and
that
so
I
could
show
some
of
the
namespace
work.
That
just
happened
to
happen.
To
have
it
up
already
is
just
a
demo
here
that
I
mean,
but
a
good
example
would
be
if
I
specifically
were
to
go
to
some
bad
namespace
this.
It
will
give
me
a
error
that
the
namespace
does
not
exist.
So
then
there's
other.
A
This
is
a
common
case
of
when
you
lot
like
you
launch
octane
just
been
a
restricted
context
in
you.
Don't
actually
have
access
to
then
to
that
namespace.
The
default
namespace,
you
know
this
will
at
least
now
give
you
a
warning
that
the
namespace
does
not
exist
kind
of
and
then
and
then,
if
you
go
into
the
console,
you'll
also
see
the
excess
air,
so
that
will
that'll
kind
of
help.
People.
A
If
you
look
at
our
issue
key,
you
can
see
there's
a
lot
of
issues
of
people
saying:
hey
I
launched
docked
in
it's
just
sitting
on
a
blank
page.
What's
going
on
these,
these
kind
of
the
alerts,
plus
the
the
refinement
with
access
errors,
not
spamming,
so
much
kind
of
help.
People
diagnose
what's
going
on
and
know
see
that
that
they
just
need
to
set
the
namespace
when
they,
when
they
won't
talk
to
in
some
that's
the
that
was
all
good
work,
as
for
so
as
for.
A
What's
coming
up,
next
I
wanted
to
kind
of
pull
up
our
roadmap
and
just
talk
about
what
we're
gonna
be,
focusing
on
and
kind
of
where
things
are
going.
So
this
roadmap
was
originally
drafted
by
Brian
about
three
months
ago
and
it's
still
fairly
up
to
date.
There
are
some
things,
some
things
that
might
need
some
refining
them.
A
That
may
be
missing,
but
for
the
most
part,
this
is
still
our
our
goal
for
octant,
and
so
in
line
with
these
goals,
we
are
drafting
up
some
kind
of
proposals
that
you
are
going
to
see
land
in
the
octant
repo
under
a
proposals.
Folder
we're
not
doing
an
official
like
octant
enhancement
proposal
thing
yet
for
now
we're
just
going
to
be
collecting
them.
They're
they'll
be
going
up
as
PR,
so
that
the
community
can
engage
with
them
and
leave
comments
and
feedback
on
them
as
we're
kind
of
fleshing.
A
These
ideas
out
the
but
the
wall,
funds
that
we're
going
to
be
trying
to
target
for
the
for
the
next
release
are
more
editing
of
objects
within
kubernetes.
We
already
have
some
of
that
now,
with
deployments
being
able
to
scale
them
up
and
down
being
able
to
set
your
images
and
things
like
that,
so
we're
going
to
be
looking
at
trying
to
get
more
of
those
in
place.
A
Add
the
ability
for
potentially
add
the
ability
for
plugins
to
kind
of
extend
in
this
area
and
get
some
better
documentation
around
this
new
action
model
that
we
have.
That
kind
of
enables
you
to
create
custom
actions
which
get
attached
to
the
things
that
happen
within
octant.
That
is,
actions
are
what
we
use
to
kind
of
power,
all
of
our
our
current
editing
capabilities,
and
so
we'll
continue
to
move
forward
with
that
framework
for
our
editing.
A
Shall
contain
image
and
so
being
able
to
kind
of
exact,
one-off
commands,
tale
long-running
commands
and
kind
of
get
that
she'll
access
into
a
container,
but
do
it
right
through
octant
when
you're,
essentially
looking
at
a
deployment,
you
see
your
list
of
containers
you
and
select
one
and
then
you
would
be
exacting
into
it
either
interactively
or
one-off.
So
there
is
a
draft
proposal
up
for
that.
A
That
will
probably
be
getting
moved
to
a
formal
PR
here,
soon
open
for
comments
and
feedback,
and
then
the
final
thing
that
this
is
something
that
brian
has
been
working
on
recently
and
it's
it's
getting
very
close,
but
it
it's
around
kind
of
viewing
your
deployments,
but
more
so
about
at
the
application
level.
So
there's
there's
the
switch
over
here
to
this.
A
The
benefit
of
this
is
that
when
you
have
things
that
are
that
are
kind
of
normally
not
associated
to
each
other,
meaning
that
they
don't
have
owner
references
and
they're
they're
not
attached
in
any
way,
except
for
maybe
through
some
some,
you
know
back-end
mechanism.
This
will
allow
you
to
kind
of
see
those
things
tied
together
and
you
can
see
here
in
the
example.
This
is
like
a
WordPress
example,
but
you
would
you
would
deploy
your
components
and
label
them
as
being
part
of
your
WordPress
deployment,
and
so
then
you
would
see.
A
It
would
would
also
be
start
to
include
tools
like
helm
right
where
they,
they
have
a
set
of
labels,
that
they
use
to
kind
of
track
their
their
things
under
their
management
and
and
we
want
to
support
those
popular
tools
as
well.
So
that's
kind
of
why
this
isn't
just
like
a
one-off,
simple
thing:
we
were
word
there'll
be
a
draft
proposal
around
it.
The
Brian
has
already
made
one
he's
going
to
be
extending
that
to
include
a
little
bit
more
details
around
things
like
like
helm,
so
I
think
that
covers
the
main.
A
The
I
think
the
final
thing
is:
we've
identified
some
performance
and
some
memory
issues
that
we
have
like
a
pattern
of
where
they're
happening
so
Sam
and
I
worked
yesterday
to
kind
of
trying
narrow
down
where
some
of
the
the
larger
memory
usage
issue
is
coming
from
and
I
think
we
have
a
good
idea
for
that.
So
hopefully
that
will
be
something
that
might
even
land
in
the
in
this
ODOT
a
release
spending
on
our
progress
on
it
this
week,
but
definitely
will
be
in
the
in
the
next
release.
A
B
A
We'll
target
Thursday
I
just
want
to
give
some
time
for
potentially
solving
this.
This
memory
issue
that
we
found
and
landing
some
of
the
other
smaller
things
that
are
still
in
the
current
release,
so
yeah
so
Thursday.
We
will
we'll
go
ahead
and
cut
a
release,
even
if
we
haven't
had
gotten
those
things
in
there.
I
just
wanted
to
give
it
a
couple
extra
days
of
more
of
like
that,
just
in
case
okay,.
C
Yeah
well,
I
mean
realistically
there's
nothing,
there's
no,
but
there's
nothing
waiting
or
way.
Dried
and
I.
Think
Tim
asked
a
very
good
question
that
I
had
this
wall
like
you
know
why
not
hold
a
weight
for
some
of
the
memory
issues.
You
know
when
I
discussed
with
Brian
the
past.
Maybe
we
had
a
little
bit
of
leeway
to
release.
Oh
wait.
A
A
Because
there
are
pretty
important
bug
fixes
not
our
plugin,
honors
and
so
I'd
like
to
get
those
out.
But
if
we
are
making
really
good
progress
on
the
memory
issue-
and
we
feel
like
it's
something
where
we
just
need
a
couple
more
days,
then
yeah
we
would.
We
would
hold
the
release
until
Monday
or
Tuesday
next
week
and.
D
D
A
We
we've
known
that
there's
been
a
there's,
been
a
memory
issue
for
a
while,
but
more
recently
it
started
to
it
became
worse
and
so
and
Sam
was
running
up
against
it
quite
a
bit
when,
when
he
was
attempting
to
you
do
some
manual
testing
and
debugging
of
some
of
the
front
end
changes
that
he
was
working
on.
So
as
a
result
of
that,
we
decided
to
get
on
a
zoom
call
and
see
the
kind
of
identify
where
these
things
were
stemming
from.
A
We
were
able
to
to
figure
that
out,
we'll
all
draft
up
a
proper
ticket.
We
just
figured
that
out
yesterday
evening
for
me
and
mid-afternoon
for
Sam,
so
my
plan
was
to
draft
off
a
proper
ticket
today
and
continue
to
kind
of
explore
and
work
on
that
to
get
those
resolved
and
see
where
we
end
up
on
Thursday,
and
if
things
are
looking
very
good,
then
what
yeah,
as
I
mentioned
before
we'll
hold,
and
so
we
haven't
resolved.
A
B
A
No,
so
being
that
we're
still
in
the
in
the
ODOT
phase,
we're
just
releasing
about
on
every
two-week
cadence,
we
it's
a
it's
kind
of
expected
that
people
are.
You
know
these
are
all
our
seats.
If
you
will,
you
know,
that's
still
there
all
betas
so
yeah,
we
will
formalize
our
release
process
a
bit
more,
as
we
start
to
you.
Probably
as
we
start
to
approach
what
we
feel
is
going
to
be
our
one
zero
milestone.
B
E
A
Yeah
I
think
that's
something
that
that
will
want
to
yes,
I.
Think
I.
Think
the
answer
is
yes,
it's
just
a
matter
of
carving
out
some
time
to
get
that
pipeline
set
up
and
doing
it
there
I
I
really
don't
see
a
downside,
especially
right
now
to
having
a
nightly
a
build
that
we
can
point
people
to
you,
and
this
would
definitely
especially
for
plugin
authors.
Let
them
get
access
to
fixes
as
quick
as
possible,
so
yeah
I
think
that's
a
great
idea
we'll
do
it.
B
Alright,
then
we're
gonna
close
it
out
for
today,
thanks
so
much
Wayne
for
going
through
everything,
that's
going
into
0.8
and
what's
coming
up
next
super
awesome
info,
and
thank
you,
everyone
for
your
questions
and
being
a
part
of
the
octan
community.
This
recording
will
be
up
on
YouTube
shortly
and.