►
From YouTube: Octant Community Meeting - Dec 10, 2019
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hi
everyone
and
welcome
to
the
octant
community
meeting.
This
is
a
community
meeting
that
we
run
every
second
Tuesday
of
every
month.
This
is
the
last
octant
meeting
of
the
decade
and
we
will
see
you
all
next
decade,
which
is
2020
so
in
January,
but
to
start
off
we
get
a
bunch
of
stuff
that
we
want
to
cover
here.
So
thank
you
so
much
for
for
joining
us
today.
A
A
B
Sure
I'll
be
happy
to
do
that,
so
thanks
Jonah,
so
yeah,
so
we
are
still
working
on
our
own
attend
release.
We
had.
B
We
had
previously
planned
to
kind
of
release
that
around
mid-november,
and
then
we
decided
that
we
actually
wanted
to
add
a
few
more
features
to
it,
just
to
make
it
something
that
was
a
little
like
a
little
more
meat
on
it.
Then
just
some
bug
fixes
in
like
one
feature,
so
the
the
current
release
is
going
to
contain.
B
There's
pr's
up
for
this
right
now,
so
you
can
go
check
those
out.
If
you
want
to
I'll
see
if
I
can
get
the
numbers
up,
so
I
can
reference
them
as
I
talked
about
it,
but
the
there
is
a
simplified
workload
view
that
is
going
to
be
in
the
next
release.
That's
PR
number
452
that
will
kind
of
allow
people
to
view
and
display
things
that
are
labeled
appropriately
as
as
workloads
and
by
labeled
appropriately.
B
B
That
I
mean
there
were
some
demos
with
that
a
cute
con
and
I
think
we
might
have
did
a
demo
of
it.
Last
I
can't
remember
anyway.
This
basically
allows
you
to
open
up
in
execute
multiple
commands
to
your
pods.
These
can
be
interactive
or
one-off
commands.
The
buffers
of
those
are
stored
until
you
dismiss
them,
they
are
not
stored
between
restarts
of
octant.
They
are
this
so
they're
ephemeral
in
nature,
but
they
all
of
the
output.
B
That
is
that's
pier
number
434
and
there's
a
little
there's
a
little
demo,
video
there
of
that
as
well.
Those
of
you
who
are
familiar
with
no
ID
tools
and
stuff
like
that
will
be
right
at
home
with
some
type
of
quick
switching
thing
for
action,
so
yeah.
Those
are
the
main
three
big
features
that
we're
hoping
to.
You
know.
That's.
B
Yeah,
so
these
are
the
three
features
that
work
that
we
will
be
getting
into
at
10:00.
All
that
Tim
will
come
out
before
the
end
of
the
year
and
there
will
be
a
nice
blog
post.
That
kind
of
outlines
all
of
these
features
and
and
goes
into
some
detail
on
them
and
and
we'll
probably
have
some
suggested
use
for
the
features
and
show
just
just
how
they
work
and
and
how
you
can
take
advantage
of
them.
B
B
B
Yes,
so
a
couple
people
have
asked
about
plugins
and
the
kind
of
state
of
things
and
where
they're
at
so
we
wanted
to
give
a
brief
rundown
of
that.
So
the
current
state
of
the
plug-in
ecosystem
is
there
it's
very
new,
so
there's
not
I,
wouldn't
say
there
really
is
an
ecosystem.
Yet
that
is
what
is
currently
forming
around
plugins.
B
So
we
we
did
create
this
topic
in
github,
which
is
octave
plugin,
which
we're
encouraging
people
who
are
creating
plugins
and
an
authoring
them
to
tag
their
repos
with,
so
that
we
are
able
to
find
them.
There
will
be
a
I
think
there
was
an
issue
created
for
plug-in
wishlist,
which
is
kind
of
we're
encouraging
people
to.
Let
me
see
if
I
can
find
that
so
I
can
put
it
in
the
agenda.
But
what
we're
doing
is
we're
encouraging
people
to
kind
of
go
and
say
hey.
B
You
know,
it'd
be
nice
if
this
plug-in
existed
so
that
people
who
are
interested
in
maybe
creating
plugins
can
come
by
and
see
that
and
then
kind
of
go
and
and
look
at
authoring
a
plug-in.
So
I
am
not
sure
if
that
issue
did
get
created,
but
we
will
create
that
today
and
and
encourage
folks
to
contribute
their
ideas
for
what
might
be
useful
plug-in
there.
B
The
other
part
of
this
is
that
we
are.
We
currently
do
not
maintain
or
really
have
any
plans
to
maintain
like
a
curated
or
official
list
of
octant
plugins
until
we
get
closer
to
one
dadö.
The
and
the
reason
for
that
is
because
there's
it
we
just
don't
have
the
the
capacity
to
do
such
a
thing
right
now,
especially
as
plugins
ecosystem
is,
is
kind
of
evolving
and
changing
rapidly.
So,
as
as
that,
as
things
start
to
solidify
around
plugins,
including
the
API
itself,
we
will
be
taking
a
more
hands-on
approach
to
you.
B
B
Plugins
should
be
able
to
just
say:
hey
I,
want
to
link
to
a
pod
of
this
ID
or
whatever
or
any
resource
of
this
ID
a
resource
and
identifiers,
and
that
should
be
able
to
generate
a
link
within
octants.
So
that's
that's
a
that's
one
that
came
up
recently
and
then
also
the
ability
for
plugins
to
take
advantage
of
all
of
our
components
that
we
offer.
That
includes
things
like
embedding
custom
actions
into
their
components.
Some
components
right
now
are
not
accessible
to
plugins.
B
D
B
A
A
A
C
The
first
one
is
really
get
up:
actions
can
do
everything
that
drone
and
most
of
what
circles
see
I
can
already
do,
and
so
this
would
allow
us
to
consolidate
our
CI
pipelines
a
little
bit
better,
because
currently
we
are
trying
to
do
several
things
with
our
CI
pipelines
in
different
places.
We
want
to
make
sure
it
builds.
We
are
running
our
end-to-end
tests
and
we
also
have
to
also
run
our
unit
testing
and
so
having
those
exist
on
different
places.
C
Sometimes
just
leads
to
just
duplicates
of
build
steps
or
just
more
places
for
things
to
fail
and
I
think
even
circle.
Ci
right
now.
Caching
is
not
on
so
moving
to
get
up
actions,
we'd
get
that
back
for
free
and
so
I'm,
pretty
confident
that
we
can
move
everything
over
with
relatively
smoothly
over
the
next
couple
of
weeks.
The
question
is
just
a
matter
of
when
and
how
we're
prioritizing
the
workloads.
C
The
part
that
I
want
to
focus
on
a
little
bit
better
is
the
state
of
the
end-to-end
tests,
because
it's
something
that's
we've
struggled
with
and
I
think
it
will
probably
continue
to
struggle
with
them,
but
they
are
fairly
brittle
and
hopefully,
by
moving
over
pipelines,
we
get
a
chance
to
inspect
that
a
little
bit
more
closely
and
reduce
test
flakes,
because
right
now,
I
think
it
still
flakes
out
from
time
to
time
and
adding
retries
as
a
band-aid.
Is
it
really
the
best
solution,
but
I
think
we
can?
C
Yeah
I
think
the
two
issues
that
I
want
to
look
into
is
whether
or
not
it
allows
exposing
a
docker
host.
So
how
well
we
can
run
a
kind
of
cluster
or
even
mini
cube
and
be
able
to
connect
to
it
in
a
CI
pipeline
and
the
second
one
is
just
how
reliable
the
build
agents
are
and
I
I
don't
really
have
I,
don't
have
a
good
sense
of
it.
A
All
right
so
we're
gonna
move
into
open
Q&A,
which
means
that
anyone
can
ask
whatever
you
want
from
the
octant
deaths
and
they
often
think
painters
here
well
relating
to
octant
I
mean
so
yeah.
If
you
have
any
questions
any
comments,
anything
you
want
to
discuss
with
them.
Please
just
unmute
and
chat.
A
Yeah,
if
there
aren't
any
more
questions
or
comments
right
now
end
the
meeting
early
and
give
people
back
some
more
time.
You
know
where
we,
where
you
can
find
us
and
I,
slept
on
slack
if
you
have
any
questions
or
comments
yeah,
and
with
that.
Thank
you
all
for
for
joining
have
a
wonderful
rest
of
your
week.
Thanks
everyone
bye.