►
From YouTube: Octant Community Meeting - May 27, 2020
Description
May 27, 2020
Agenda
Release Status
HPA printer #930
Graphviz memory leak #951
Current
HPA printer #930
Terminal bug fixes (various)
Apply YAML #954
Angular Update #952
Reminder, Octant office hours: schedule a time.
Upcoming
CNCF Webinar, June 3rd
https://www.cncf.io/webinars/how-to-better-understand-k8s-workloads-using-octant/
A
A
All
right
welcome
everybody
to
the
octant
community
meeting
for
May
27th
today,
we're
just
going
to
cover
some
things
about
the
current
upcoming
release.
What
we're
working
on
right
now
and
some
stuff-
that's
upcoming!
So
first
I'll
kick
it
off
with
the
release
status.
So
last
week
May
20th,
we
talked
about.
We
wanted
to
cut
a
0.14
0.14
and
there's
a
couple
outstanding
issues
that
we
want
to
make
sure
we
get
into
that
release.
A
The
first
one
seems
currently
looking
at,
which
is
the
adding
back
to
HB
a
printers
after
we
removed
them
during
the
upgrade
of
some
dependencies
and
the
upgrade
of
client
go.
So
that
would
be
getting
added
back
in.
So
that's
in
progress
and
we're
gonna
hold
the
release
for
that
and
then
the
other
thing
we're
taking
a
look
at
which
we
may
or
may
not
hold
the
release
for
since
it
will
be
part
of
a
nightly.
A
But
is
we
fixed
an
issue
with
the
graph
is
component,
but
it
there's
been
a
report
that
there's
potentially
a
memory
and
leak
win
in
San
Shi,
adding
the
new
component,
and
we
want
to
we're
triaging
that
and
verifying
that
now
to
see
if
we
can
replicate
it
and
then,
if
we
are
able
to
easily
replicate
that
issue,
we're
going
to
go
ahead
and
get
it
fixed
for
this
release
as
well.
So
those
are
the
two
outstanding
issues
that
are
that
are
pending.
That
will
once
they're
completed,
will
allow
us
to
cut
and
ODOT
14.
A
The
current
sprint
work
is
around
those
those
fixes.
We
did.
Some
terminal
bug
fixes
that'll,
be
part
there
in
the
nightly
now,
but
they'll
be
part
of
the
next
upcoming
release
as
well
I'm,
currently
working
on
the
ability
to
apply
yamo
from
within
an
octant
as
part
of
rounding
out.
Some
of
the
full-featured
editor
work
that
we
were
doing
earlier
a
few
weeks
ago,
when
we
swapped
from
the
yamo
viewer
just
a
static
read-only
view
of
resources,
the
the
Amal
that
represents
resources
to
the
Monaco
editor.
This
is
just
carryover
from
that
work.
A
That
will
allow
folks
to
you,
similar
to
what
you
do
with
keep
CTL
now
or
you
take
a
random
yam
will
file
and
apply
it
you'll,
be
able
to
paste
in
Amal
file
and
hit
apply
and
have
it
get
applied
to
the
cluster.
We
also
revved
our
dependencies
for
angular,
updated,
I,
think
nine
one
nine,
as
well
as
some
other
minor
JavaScript
updates.
So
all
of
those
will
be
the
the
apply.
A
A
Okay,
so
moving
on
I
wanted
to
remind
folks
of
the
octant
office
hours
since
the
they
did
move.
They
are
on
the
same
day
as
this
meeting
now
they
start
right
after
this
meeting
is
over.
This
is
the
community
meeting
being
that
and
then
office
hours
were
run
from
1p
well,
essentially
1:30
Eastern
until
6:00
p.m.
Eastern,
with
the
last
time
slot
being
available
at
5:30,
Eastern
Time,
so
there's
there
in
the
CAF
hour
and
45
minute
blocks,
so
I
think
there's
some
later
time
slots
available
today.
A
I
think
all
of
the
earlier
ones
are
already
full.
So
just
remind
folks
that
that
is
there
again,
that
is
for
discussing
anything
and
everything
related
to
octant,
yet
plugins,
where
direction
of
octant
you
just
general
conversation
you
want
to
talk
about
it
you're
want
to
ask
some
questions
about
using
it,
and
things
like
that.
That's
that
it's
open
for
anyone,
so
please
take
advantage
of
that.
It.
B
A
And
then
into
upcoming
I'd
wanted
to
tell
folks
that
we
have
a
CNC
F
webinar
coming
up
next
week.
It's
it's
next
Wednesday
June
3rd,
it
happens,
I
believe,
oh
I,
don't
know
the
exact.
So
it's
in
the
link
here,
let
me
click.
It
happens
at
7
to
8
a.m.
Pacific
time.
Whatever
time
that
is
so
UTC
minus
seven,
there
we
go
yeah.
A
So
this
is,
it's
gonna,
be
a
webinar
covering
kind
of
taking
looking
and
understanding
a
workload
within
octant
I'll,
be
I'll,
be
leading
this
webinar
and
we'll
be
covering
kind
of
taking
an
existing
workload
that
you
might
have
converting
it
into
something
that
runs
in
the
cluster
and
then
really
it's
about
octant
as
a
tool
to
kind
of
get
insights
and
and
work
through
any
issues
or
problems
and
understand
how
that
thing
is,
is
running
within
in
the
cluster.
So
it
might
be
a
I
think.
A
There
will
also
be
some
new
things
that
I'll
be
covering
in
there
more
around
like
usage
patterns
and
how
how
I
use
octant
in,
like
my
own
personal
cluster
and
like
other
things,
when
I'm
migrating
a
workload
into
into
kubernetes,
so
I
encourage
folks
to
attend.
And
if
you
can
attend,
live,
it's
it's
preserved
and
up
on
the
CN
CF
website
for
people
to
watch
at
their
with
their
leisure.
A.
B
Couple
of
three
items,
so
you
know
a
big
big
advantage
of
octant
and
I
know
you've
done
it
before
in
many
demos.
It's
kind
of
you
know,
obviously
our
visibility,
troubleshooting
component
that
you
mentioned
earlier
with
me
worthwhile
and
asking
me
to
change
your
demo
now
a
week
before
that,
but
think
about
it
to
to
basically
deploy
an
app
that
maybe
has
a
broken
config,
whether
that's
you
know
a
PvE
or
or
something
that's,
not
working
and
then
show
octant
to
kind
of
show,
the
correlation
that
this
is
misconfigured.
B
That's
why
your
app
is
not
working
and
then
once
you
fix
it,
maybe
have
something
that
you
can
troubleshoot
by
using
the
logs.
That
way,
you
can
kind
of
walk
them
through
a
scenario:
oh
hey,
I
just
started
my
cloud
native,
developed
or
I
just
build
my
app
I'm.
Not
it
doesn't
look
like
it's
working.
How
do
I
go
about
troubleshooting
that
and
then
start
from
a
broken
config
and
then
maybe
a
bug
in
the
app
itself
that
you
identified
through
logging
and
then
update
the
app.
You
know
an
idea,
yeah.
B
A
To
the
the
the
actual
platform
itself
will
be
talked
about
and
how
its
extensible
and
the
component-based
architecture,
and
then
I'll
will
also
show
off
some
of
the
existing
plugins
that
exist
and
I
am
briefly
point.
People
to
at
the
end,
there'll
be
a
section
where
we're
going
to
recap
and
point
people
to
like
octave
and
and
how
to
explore
creating
their
own
plugins
and
things
like
that.
B
There's
also
practically
that
kind
of
closes
up
the
story
here
or
what
I
mentioned
earlier,
and
now
you
have
your
app
running,
you
debug
the
issue.
You
basically
fix
that
config
and
then
you
can
pull
up
the
3d
scanner
plug-in
and
say:
oh,
this
amusing,
a
library,
that's
super,
vulnerable
I,
guess
I
need
to
fix
an
X
and
you
don't
need
to
actually
fix
it
in
your
demo,
but
show
them
how
you
close
the
flow
of
now.
We
also
have
a
plugin
that
gives
you
additional
details
about
your
app
that
kubernetes
itself
cannot
provide
yeah.
A
No,
that's
that's
a
great
great
idea
to
incorporate
that
plug-in.
So
there'll
be
a
they'll,
be
a
probably
I'll,
probably
post
it
to
this
agenda
as
well
as
send
it
out
to
folks
but
there'll,
be
a
pre-recorded
like
practice.
Run-Through
of
the
demo
I
might
do
it.
I
might
do
it
live
as
well,
but
just
to
you
just
to
let
folks
kind
of
know
what's
coming
and
see
what
we're
going
to
be
talking
about.
B
A
C
No
I
had
think
that's
everything
for
the
HP
printers.
It's
probably
gonna
take
a
little
bit
while
as
well,
because
I
also
I
didn't
mention
this
morning
at
the
stand
up,
but
they
added
a
new
feature
recently
called
it's
a
behavior
feel
for
the
horizontal
pod,
auto
scalars
and
you
can
tune
the
scaling
velocity
and
so
there's
just
some
extra
info
on
top
of
refactoring
the
type
conversions.
So
it's
it's
a
bit
of
work,
but
hopefully
I'll
get
it
done
as
soon
as
possible.
So
we
don't
block
the
release.