►
From YouTube: Octant Community Meeting - Feb 19, 2020
Description
February 19, 2020
Agenda
-------
Security Fix
Angular9 has landed in master
Logging Updates (Milan)
UI updates
Plugin examples repo octant-example-plugins
Shoutout
Persistant Volume Printer / Jordan Jensen & Andy Schiefe
Multi-Context Logging / Jack Wink
Octant RCE Bug / Jack Wink
A
A
Not
really
just
casually
suggest
it
so
first
things.
First
I
would
like
to
start
off
with
the
security
fix
that
went
into
octant
last
week.
So
there
is
a
security
vulnerability
posted
up
on
github.
You
can
see
thanks
to
Jack
wink,
who
reported
the
issue
was
found
through
evaluation
of
the
tool.
It
was
a
very
it.
A
A
A
Thanks
yeah
and
thank
you
Michael
for
helping
to
coordinate
all
that
through
the
the
VMware
security
team.
That's
great
so
so
moving
on
yeah
all
that
information
is
there
in
the
in
the
security
advisory.
That's
supposed
to
make
it
up!
It's
it's
public!
You
can
see
it
so
definitely
update
to
the
latest
octant.
A
The
next
thing
is
angular
9
is
in
master
now,
which
was
she
actually
went
fairly
smoothly.
There's
some
minor
things
that
need
to
get
fixed
up
that
are
related
to
that,
but
for
the
most
part
II
it
went
in
pretty
well,
and
so
that
means
that
the
work
that
I
was
working
on
with
getting
the
Monaco
editor
integrated
in
Stockton
has
been
picked
back
up.
So
I've
started
working
on
that
again
this
week
and
have
made
some
progress
there.
A
No
set
time,
but
we
have
enough
in
there
there's
a
lot
of
good
features
in
there
and
a
lot
of
good
stuff
in
the
current
and
the
concurrent
master
that
amount
or
to
a
pretty
nice
release
for
everybody.
So
and
speaking
of
that,
I
wanted
to
have
Milan
kind
of
go
over.
Some
of
the
recent
updates
to
the
logging.
C
C
Yes,
so
I've
been
working
on
logging,
mostly
for
now
focused
on
search
and
filtering
and
that's
been
partially
the
unimplemented,
mostly
most
functionality
that
I'm
still
waiting
for
the
final
design.
I
touch
base
with
Ross
about
that
yesterday.
So
that's
coming
up
soon,
I
think
I
hope.
That's
still
the
client
and
also
did
some
small
fixes
like
times
that
was
breaking
up
or
to
the
second
line.
That's
not
happening
anymore
and
yes,
so
we
now
do
support
regex
as
well.
There
were
some
issues
with
that
things.
We
had
two
pointing
that
out.
C
B
C
D
C
A
Awesome
thanks
for
that-
and
this
was
yeah,
so
I
called
up
the
got
it
they're
a
little
late
after
everyw
was
done.
Talking
cuz,
it's
walking
into
so
many
things,
but
here's
the
logging
said
six
ago,
so
you
can
see
the
the
closeout
issues
here
at
the
bottom.
Quite
a
few
have
been
have
been
closed
out
this
one
in
progress
here,
section
one
that
I'm
working
on,
which
is
not
actually
related
to
the
logger
itself.
It's
related
to
the
API
and
virtual
nodes
on
a
juror
kubernetes
service.
A
So
that's
something
that
I'm
still
looking
into
it
would
have
been,
was
fighting
a
little
battle
with
aks
yesterday
and
finally
got
it
all,
set
up
and
working
with
virtual
notes
and
was
able
to
actually
get
some
of
my
deployments
to
deploy
their
workloads
into
a
virtual
mode,
which
was
like
the
first
step
to
actually
replicating
and
then
fixing.
So
that's
that's
coming
along
so
moving
on
to
as
met
UI
updates.
A
So
we
we
made
a
quite
a
few
just
kind
of
minor
just
in
improvements
to
the
UI
around
just
components
that
are
being
used
and
in
classes
and
using
the
correct
clarity
components.
A
lot
of
this
work
is
based
on
worked
out.
Ross
Fenric
did
with
creating
some
new
mock-ups
and
just
kind
of
making
sure
that
we
were
using
what
was
available
in
the
clarity
library
as
best
that
we
could
so
I
wanted
to
just
kind
of
show
some
of
that
quickly.
This
is
this
is
based
off.
A
Current
master
and
I
was
just
going
to
walk
through
it
and
then
Ross,
if
there's
anything
that
you
wanted
to
to
mention
afterwards
or
during
just
feel
free.
So
this
is
the
the
kind
of
what
you
see
now
when
you
land
on
achtung,
you
can
see
the
the
namespace
drop-down
has
been
moved
over
to
fall
in
line
with
the
NAB.
A
Here,
we've
changed
this
background
when
you're
in
book,
when
you're
in
dark
versus
light
mode
so
light
mode
before
the
background,
the
top
bar
was
still
a
dark
color
and
it
created
this
hard
contrast,
which
actually
kind
of
made
it
difficult
for
your
eyes
to
kind
of
see
stuff.
So
we've
lightened
that
up
a
little
bit
and.
A
It's
crooked
there's
an
issue
for
it.
Yes,
so
again,
that
was
one
of
the
things
I
think
that
actually
happened
when
we
moved
to
angular
9
I,
don't
think
it's
always
been
crooked,
like
that,
so
this
I
think
Sam
saw
this
like
renegade,
that's
crooked
and
so
yeah.
Those
are
the
minor
angular,
nine
things
that
I
was
mentioning
that
we're
gonna
want
to
touch
up
before
we
before
we
cut
a
release
from
master
so
yeah.
A
Yes,
we
know
about
that
yeah
and
we
so
we
changed
up
the
the
labels
as
well,
so
now
they're,
actually
using
the
clarity
label,
selector
or
label
component,
and
so
they're,
not
just
buttons.
It
makes
them
a
little
more
changes.
The
font
changes
how
they're
outlined
changes,
how
they
highlight.
So
it's
it's.
A
A
There's
like
I
can
filter
and
there's
objects,
and
it
will
bounce
me
to
the
to
the
objects.
We
can
also
show
only
the
lines
that
match,
which
is
which
is
nice
for
when
you're.
Looking
for
a
very
specific
thing
like
if
I
was
if
I
was
like.
Oh,
are
these
with
something
with
the
cash?
Oh
there.
It
is
right
there
and
you
can
just
see
the
one
line.
So
that's
all
work
that
quick.
A
A
C
A
A
C
A
A
D
Theming,
like
syntax
theming,
for
both
the
logger
and
for
the
yeah
Moe.
Once
we
have
Monaco
and
I
think
you
can
do
custom
themes
with
that
and
I'm
just
kind
of
used
like
a
clarity
palette,
for
you
know,
dark
and
both
dark
and
light
theme.
So
that's
something
I
hus
some
work
on
and
I
look
around.
Maybe
someone
has
already
done
that
with
clarity
too
so
I'm
gonna
look
around
that.
Okay.
E
B
E
I'm
working
on
changing
out
the
navbar
on
the
left
and
one
of
the
big
notable
changes
is
that
we're
going
to
be
renaming
this
workloads
on
the
very
top
under
that
namespace
box
to
the
applications
per
Ross's
new
design,
and
that
makes
sense
because
we
have
workloads
in
the
sense
of
like
a
kubernetes
workload.
But
then
we
also
have
this
other
representation
of
workloads
in
our
code
base,
which
really
is
just
a
give
me
a
summary
of
all
the
applications.
E
That's
running
on
the
cluster,
so
I
think
for
the
first
pass,
we're
just
gonna
rename
just
rename
the
menu
entry,
but
I
think
eventually
it'll
bubble
out
to
the
rest
of
the
code
internally
and
and
we're
also
going
to
be
changing
out
a
ton
of
the
icons.
A
lot
of
them
are
going
to
be
collapsed
up
and
we're
essentially
going
to
be
using
these
clarity.
Icons
instead
of
the
old
kubernetes
I.
E
So
hopefully,
these
new
icons
catch
on
I
probably
push
up
the
PR
with
Nico's
code,
probably
sometime
today,
as
soon
as
the
backend
is
done,
there
shouldn't
be
too
much
work
left
and
then
there's
some
minor
CSS
tweaks
that
were
probably
just
going
to
fix
over
the
course
of
the
week,
but
that's
something
I'd
like
to
get
into
this
next
release,
or
and
at
least
have
sometimes
sitting
on
masters.
So
then
we
kind
of
see
if
we
want
to
tweak
something
in
the
meantime.
We'd
have
adequate
time
to
think
about
it.
A
Yeah
great
yeah-
this
is
this
is
great.
This
is
another
UI
change
that
came
out
of
the
work
that
Ross
mocked
up
and
then
Nico
did
the
front-end
changes
for
that
and
yeah
I
say
I
mentioned
he's
working
on
the
backend
changes
so
I
have
it
pulls
up
here
you
can
see
what
the
new
kind
of
nav
is
gonna
look
like,
and
if
you
compare
that
to
the
to
the
old
nav
over
here,
in
our
opinion,
it's
that's
play.
Sweet,
quite
yeah,
better.
A
Okay,
so
any
questions
on
any
of
those
things
from
folks,
let's
see
I,
mean
make
sure
I'm.
Looking
at
the
chat
like
there's
anything
so
and
I
mean
look
at
the
dock,
nothing
there.
Okay,
so
moving
on,
we
were
are
going
to
what
we
do.
We
have
this
new
repo
actually
already
have
it
open.
So
there
was
some
questions
about
getting
a
example
repo
for
octant
plugins
that
wasn't
part
of
the
main
octant
repository.
There
was
a
couple
reasons
behind
this
one.
It
ensures
that
we're
not.
A
We
don't
have
any
tight
dependencies
to
internal
octant
things
in
in
plugins,
which
are
you
know
external
and
then
the
other
part
was
that
it
created
kind
of
a
landing
area
for
people
to
easily
make
suggestions,
improvements
or
submit
ideas
around
plugins
that
aren't
maybe
like
full
features,
but
just
more
of
like
conventions
or
ideas
on
how
to
do
things
which
we
can
later
link
to
in
science
to
our
plugin
documentation.
So
we
have
created
this
octant
example
plugins
repository.
A
There
is
an
initial
pull
request
up
right
now.
This
initial
pull
request
creates
three
plugins.
One
is
for
demonstrating
the
actions
plug-in.
The
other
one
is
a
copy
of
the
sample
plug-in
from
the
octan
repo
and
the
final
one
is
an
example
of
writing
a
plug-in
using
Python,
so
those
will
be
hopefully
merged
into
this
main
repo
soon,
and
we
will
start
to
build
out
kind
of
our
examples
in
this
repository
and
likely
well
we'll
take
the
will.
Take
the
example
plug-in
that's
currently
in
the
main
oxidant
repo,
maybe
we'll
make
it
a
sub
module.
A
So
we
can
leave
the
the
the
build
the
easy
build
option
there
so
that
people
can
install
the
test
plug-in
quickly
but
it'll.
Let
the
actual
sample
plug-in
itself
will
come
out
of
the
out
of
the
octan
repo,
which
is
an
action
item
that
came
up
during
during
the
last
agenda
or
community
meeting.
Some.
A
Questions
comments
there,
okay
and
then
finally,
I
wanted
to
just
do
some
shout
outs.
So
there's
a
there
was
a
couple
things
that
came
in
from
the
community
that
were
you
know,
big
deals
and
the
persisted
volume
printer
thanks
to
Jordan
and
Andy,
for
working
on
that
and
we've
got
that
merged
in
and
it's
it's
looking
looking
really
good,
so
really
appreciate
all
of
their
hard
work
on
that.
A
F
Hey
Wayne,
this
is
Andy
Superboy,
Jordan
and
I
were
talking
about
some
of
the
oddness
that
were
doing
and
and
wondering
if
some
of
that
could
be
resolved
by
doing
a
pull
request
for
the
defect
or
I,
don't
know
if
it
was
a
defect.
It
was
more
of
a
enhancement
request
that
I
opened
a
while
ago
we're
we're
kind
of
stitching
together
command-line
options
for
a
couple
of
different
programs,
and
it
would
be
nice
to
be
able
to
know
which
ones
are
specific
to
each
one
of
them,
and
we
were
talking
about.
F
Maybe
there
would
be
a
way
to
expose
either
the
flags
or
the
names
of
the
the
command
line,
options
that
would
be
going
to
each
one
of
the
programs
in
in
in
the
programs.
It
would
be
like
a
constant
structure
that
would
would
be
available
for
for
those
of
us.
That
would
have
to
do
such
a
thing,
but
before
we
went
down
that
road,
we
were
kind
of
curious
if
that
was
even
an
appropriate
approach,
or
if
that
would
be
something
that
would
be
acceptable.
G
A
Was
gonna
say
if
you
all
wanted
to
write
up
a
so,
we
have
a
proposals
folder
in
octant
that
you
can
submit
PRS
against,
which
is
just
a
place
to
put
markdown
files
around
enhancement,
ideas
or
larger
features
that
you
want
to
put
into
octant.
If
this
is
something
that
you
think
is
is
useful,
then
I
think
getting
like
a
more
like
asynchronous.
Like
you
write
it
up,
people
have
time
to
digest.
It,
read
it
and
give
feedback,
and
we
kind
of
iterate
through
that
process
would
be
the
way
to
go.
G
The
short
of
it
to
put
a
little
bit
as
fleurs,
we
have
a
command
line,
wrapper
kind
of
that
we're
writing
for
octant.
So
we
can
utilize
a
couple
of
extra
flags
for
things
like
using
an
airship
comp,
instead
of
a
cube
comp.
That
kind
of
thing
and
using
airship
libraries
to
to
manage
that
stuff,
and
one
of
the
things
that
we
ran
up
against
was
having
to
basically
hard
code,
all
the
flags
from
octant
into
that
CLI
tool,
because
currently
the
CLI
flags
for
octant
are
internal
and
not
not
visible
to
to
other
things.
G
H
A
Cuz
cuz
I
was
just
thinking
like
if,
if
you
had
you
could
have,
you
could
still
have
that
file
that
had
the
values
like
you
know,
this
equals
this
and
then
and
then
at
startup.
You
could
load
that
into
the
environment
and
then
acht
and
before
you
launch
the
octant
command
and
then
the
octave
command
would
read
them
and
respect
them.
That
might
bear
that.
If
that
and
that's
something
to
try,
if
that
doesn't
work,
then
yeah
I
think
we
can.
We
can
look
into
what
other
options
there
might
be
sure.