►
From YouTube: Octant Community Meeting - Jan 14, 2020
Description
We're moving to a weekly cadence, every Wednesday at 1PM ET / 10AM PT.
Please make sure you're subscribed to the Octant Google Group, that way you'll always have an updated meeting invitation:
https://groups.google.com/forum/#!forum/project-octant
B
Great
thanks,
yeah,
hey
everyone
thanks
for
attending
our
first
community
meeting
of
the
year,
so
I'm
just
gonna
go
through
this
agenda.
If
you
have
any
questions
as
as
I'm
going
through
it,
you
can
type
it
into
the
heck
MD
or
just
ask
in
the
chat
and
I
may
answer
them
in
line
or
I
may
wait,
and
so
I'm
done,
but
probably
just
answer
them
in
line
and
then
yeah.
So
first
off
the
ODOT
10
release
is
coming
very
shortly.
B
We
were
finishing
up
some
things
before
a
lot
of
us
went
on
a
holiday
break
and
we
are
kind
of
putting
the
final
touches
on
some
of
those
and
we
will
be
yeah.
We
will
be
releasing
very
soon,
which
is
what
I
said
last
time,
but
this
time
I
really
mean
it
yeah.
The
list
of
features
can
be
found
by
the
easiest
way
to
see
kind
of.
What's
in
there,
and
a
quick
glance
is
to
go
to
our
github
and
you
can
look
at
the
unreleased
changelogs.
B
There's
an
unreleased
folder
under
changelogs
and
that'll.
Give
you
a
quick
brief
of
everything.
That's
going
to
be
in
about
10.
There
are
a
couple
outstanding
things
that
you
probably
won't
see
there,
yet
one
of
them
being
the
terminal
demo
that
I'm
about
to
do
now
and
there's
a
couple
fixes
that
will
be
in
place
before
we
do
that
10
release,
mostly
around
CR
DS
and
some
minor
touch-ups
for
some
of
the
plugins
stuff.
B
So
that
is
that's
where
the
autumn
releases,
the
I'm
yeah,
the
the
exact
date
will
to
be
determined,
but
very
very
soon.
I
mean
within
and
Sam
and
I
are
working
on
PR
reviews
and
final
touches
now.
So
if
it's
something
that
we
can
get
here,
probably
Monday,
I
hope
but
yeah.
So
there's
there's
also
a
blog
post
being
crafted
that'll
kind
of
walk
over
all
of
the
the
features
and
and
and
what's
coming
up
in
this
release,
so
expect
that
very
soon
I'll
actually
also
I'll
save
the
demo
for
the
end.
B
I'll
go
ahead
and
just
go
to
plugins,
so
the
after
o10
is
is
released.
We're
going
to
be
taking
a
good
look
at
at
plugins.
We
have.
Oh
thanks
for
fixing
my
misspelling
of
january.
We
have
gotten
some
good
feedback
from
plugin
authors
and
we
are
going
to
be
addressing
that.
Some
of
the
API
consistency,
consistency
issues
with
plugins
we're
gonna
move
towards
removing
the
hard
dependency
on
our
internal
octant
repo
from
for
plugin
authors.
B
B
So
it'll
also
allow
people
to
do
better
unit,
testing
and
functional
testing
of
their
plugin,
because
there
won't
be
kind
of
these
hidden
corners
where
our
abstractions
leak
and
you
find
yourself
not
able
to
provide
a
fake
or
a
mock
for
some
piece
of
octant
that
you
are
using
in
your
plugin.
So
all
of
that
ties
into
API
consistency,
but
that's
something
you
can
expect
coming
soon
and
then
also
the
details
on
this.
B
Aren't
a
hundred
percent
we're
going
to
be
kind
of
flushing
these
out
over
this
week
and
and
but
we're
going
to
be
adding
some
form
of
a
more
freeform
web
component
for
plugins,
where
you'll
be
able
to
kind
of
provide
custom
javascript
in
HTML,
we'll
inject
those
into
the
the
view.
And
then
your
component
will
render
using
the
data
sent
from
the
plug-in.
B
B
B
So
I
want
to
tighten
that
loop
up
so
that
way
we
can
kind
of
address
those
things
that
as
you're
experiencing
them,
instead
of
having
to
wait
a
whole
month
to
hear
that
we,
you
know,
are
addressing
something
so
and
also
it
allows
us
to
kind
of.
When
we
do
releases.
You
know
the
the
the
feedback
loop
from
hey.
We
cut
a
release,
even
if
we
do
it
on
a
Thursday.
B
C
C
B
Specifically,
when
I
want
to
show
today
is
this
execute
command,
which
was
added
it's
currently
in
a
branch,
but
it
will
be
added
in
a
node
I
10.
What
this
does
is.
It
is
essentially
the
same
as
running
what
you
would
get
with
cube,
cube,
CTL
exec.
It
allows
you
to
just
either
persisted
or
one-off
commands
in
your
against
a
container.
So
here
you
see,
I've
ran
a
adi
message
previously
can
resize
this
I've
ran
a
D
message
previously,
so
it
it
respects
all
terminal
output.
B
B
So
you
know,
if
you
shrink
ur
or
remove
this
window
it'll,
it
will
properly
adjust
all
the
margins
and
borders
and-
and
you
know,
display
things
differently,
so
I'm
I
don't
know
if
that'll
come
across
in
the
in
the
demo,
but
I'm
gonna
try
it
I'm,
just
gonna
like
resize
this
window
to
make
it
smaller
and
then
I'll
do
LS
again
and
maybe
you'll
see
that
it
sent
there
so
it
like.
Instead,
it
wraps
now
instead
of
so
say
so
it's
wrapping
them
instead
of
showing
him
the
Lanka
I,
don't
know
if
that
came
across.
B
But
if
it
it
does
so
looks
good,
the
up,
arrow
and
stuff.
So
if
your
shell
supports
it,
it'll
work
right
now
you
can
see
I'm
sending
the
control
sequence
for
up
some
terminals
when
I,
open
them
up
arrows
and
like
control
R
and
can
in
like
shell,
completion,
all
work,
and
in
some
terminals
they
don't
that's
just
a
known
issue
and
I'm,
not
quite
sure
exactly
how
to
how
to
fix
that.
Yet.
But
when
you
exit
the
terminal,
it
actually
will
save
your
your
buffer
until
you
close
it
from
from
within
octants.
B
You
know
so
so,
as
you
move
around
and
you're
doing
things
with
a
nokton,
if
you,
you
know,
executed
a
command
on
a
container
and
you
want
to
go
back
and
look
at
it
and
reference
it.
You
can
do
that
it
doesn't.
You
know
it
doesn't
go
away
so
until
you
actually
click
the
X
or
restart
octant,
and
then
it
clears
all
of
these
out.
But
that
was
a
feature
that
we
wanted
to
preserve.
B
The
output
I
know
a
lot
of
shells
when
you
exit
them,
they
just
they
close
and
go
away,
but
the
nature
of
octant
is
that
you're
in
here.
Looking
for
information
and
doing
things,
so
this
kind
of
lets
you
keep
that
information
persisted
even
if
it's
a
like
a
short-lived
short-lived
command
like
a
D
message
or
something
you
don't
have
to
specify
whether
or
not
it's
interactive
that
just
happens
on
the
back
end
automatically.
So
if
you
again
I'll
just
run
that
same
one.
B
B
This
is,
is
kind
of
like
more
of
it's
more
for
like
cleanup
or
quickly
navigating
to
a
container
where
you've
ran
up
terminals.
So,
like
you
may
have
run
a
few.
You
can
see
it's
none
show
up
down
here
because
I'm
in
the
cluster
overview,
so
I'm
not
actually
sitting
on
a
name
space.
So
this
is
more
of
just
like
a
quick
way
to
either
clean
up
terminals
or
get
to
the
container
that
has
the
the
terminal
that
you're
looking
for.
B
B
E
But
it
seems
at
this
point
that
octant
is
really
tied
to
being
able
to
requiring
having
an
active
connection
before
they'll.
Do
anything?
Is
there
any
envision
or
possibility
that
we
could
let
octant
run
and
have
a
you
know?
Some
kind
of
obviously
most
of
the
functionality
would
not
work
but
to
be
able
to
have
some
ability
to
use
it
without
an
active
connection.
That
way
we
could
have
at
least
run
through
some
of
our
bootstrap
scenarios
and
launch
kubernetes
and
then
connect
to
it.
So
so
what
do
you
think
about
that?
Yes,.
B
D
And
you're
not
the
first
one
to
ask
this:
there's
multiple
people
that
are
using
cluster
api
to
bootstrap
clusters.
So
when
the
first
cluster
is
not
there
they're
having
difficulty
so
that
kind
of
yes
ability
to
get
octant
to
be.
There
first
allow
your
plugin
to
be
the
first
interface
that
developers
use
and
to
kind
of
execute.
Whatever
actions
you
need
to
start
a
cluster
and
providers,
a
cube,
config,
so
I
think
I
can't
promise,
but
this
probably
high
up
in
our
priority
list.
For
for
for
the
next
set
of
release,
excellent.
E
D
E
A
I
think
so
too,
we'll
close
it
out
and
yeah.
As
Wayne
said,
we're
gonna
move
this
into
a
weekly
cadence,
so
we'll
have
more
more
discussion,
topics
and
kind
of
status
reports
and
things
like
that
every
week,
going
forward,
so
starting
on
Wednesdays
at
1:00
p.m.
Eastern
and
10:00
a.m.
Pacific
I
will
be
updating
the
invite
that
is
being
sent
out
for
through
the
the
Google
Groups.