►
From YouTube: Octant Community Meeting - July 22, 2020
Description
July 22, 2020
Agenda
0.14.0 and 0.14.1 released
contains a fix where users may get prompted for a kubeconfig
contains a fix for --kubeconfig
contains a fix for navigation background color
quick demo that hits most new fetures on youtube
Investments in to bringing back our integration testing.
More consistent two week sprint cycles.
JavaScript plugin runtime update. #1141
added an httpClient.get
added apply YAML
added delete resource
updated yo generator to show rxjs workflow
How to visualize knative/tekton workflows. #1145
A
All
right
welcome
everybody
to
the
octant
community
meeting
for
the
22nd
of
July.
2020
I'm
gonna
share
this
agenda
and
we
can
start
to
go
over
it.
So
the
big
item
here
is:
oh
not
14
was
released
and
ODOT
14.1
was
released,
the
ODOT
14
released
went
out,
and
in
it
there
was
a
couple
issues
that
folks
were
running
into.
One
was
just
they
were
getting
prompted
to
enter
a
config,
even
though
they
already
had
a
valid
one
configured.
That
was
kind
of
an
issue
that
we
had
some
difficulty
pinning
down.
A
But
we
put
in
some
changes
that
we
think
alleviated
that
for
most
people,
if
not
all
so,
the
other
thing
was
the
cute.
Config
flag
got
broken,
so
the
environment
variable
was
still
working,
but
the
the
flag
itself
was
not
so
people
who
are
using
that
we're
seeing
the
prompt
to
enter
a
QP
fig.
So
we
got
that
fixed
and
then
we
also
managed
to
to
fix
the
navigation
background
color
on
when
you're
selecting
menu
items
and
navigate
away.
A
The
the
big
highlights
is
mentioned
last
week
that
were
coming
when
we
did
that
short
little
demo
was
the
creation
of
resources,
port
forwarding
of
services
being
able
to
start
without
a
keep
config
and
the
experimental,
javascript
plugins
support
and
then
a
whole
host
of
fixes
and
updates
and
and
things
that
were
we're
done
as
well,
so
feel
free
to
look
at
the
full
notes
find
out
more
and
about
14.1.
Here
it
was
yeah.
There's
the
breadcrumb
link,
color
and
dark
mode
was
off,
so
those
are
the
three
fixes
we
got
in
place.
A
So
thanks
Sam
did
a
great
job
of
getting
this
release
out
in
quick,
quick
fashion.
So
thank
you
Sam
for
taking
care
of
that
and
for
folks
who
haven't
had
a
chance
to
try
the
new
about
14.
There
is
a
there's
a
little
demo
and
YouTube
that
steps
through
all
of
the
I
think
it
hits
most
of
the
of
the
of
the
highlighted
features
in
that
single
demo.
It's
about
two
minutes
long,
if
you're
interested
anything,
anyone
wants
to
add
there
about
the
owed
up,
14
I,
forgotten.
A
Excellent,
so
something
that
came
out
of
about
fourteen
which
I
wanted
to
bring
up
is
we're
gonna.
We
did
a
proposal
a
while
back,
Sam
wrote
it
up
and
we
approved
it
and
got
it
merged
in.
We
haven't
taken
the
action
on
it.
It's
about
getting
our
integration
testing
back
in
place.
We
had
it
previously
when
we
were
over
on
drone.
We
turned
it
off
because
it
was
intermittently
failing
and
it
just
wasn't
configured
well
one
that
configured
well.
It
was
configured
just
fine
it
just
wasn't.
A
The
tests
were
not
predictable
and
we
had
a
bunch
of
flakes,
so
we
turned
them
off
and
we're
noticing
that
we're
hitting
some
issues
that
could
be
solved
by
having
some
integration
tests
back
in
facility
things
like
that
that
cute
config
not
working
right.
That's
like
one
of
those
very
easy
things
to
catch,
and,
and
so
we're
going
to
put
some
investment
back
and
do
getting
our
integration
suite
back
up
and
running
on
github
actions
and
we'll
just
we'll
keep
people
updated
on
how
that
goes.
A
But
the
goal
coming
out
of
that
is
just
to
kind
of
make
sure
that
going
forward.
Our
releases
are,
you
know,
have
an
extra
layer
of
of
check
on
them
and
coming
out
a
little
more
polished
and
and
not
having
to
do
so.
Many
you
know
day
zero
point
dot,
release
fixes
not
that
we've
had
to
do
a
lot,
I
think
the
furthest
we've
ever
made.
It
is
to
it
to
a
dot,
but
maybe
a
dot
three,
but
it's
not
too
bad,
but
yeah
we'll
be
investing
some
stuff
there.
B
Yeah
I,
you
know
one
thing
with
that:
that
kind
of
happened
after
Sam
did
that
initial
work
on
that
is
I
mean
a
proposal.
Is
we
started
using
storybook
and
story
gives
us
a
lot
of
new
options,
including
this
snaps
shirts.
They
have
story
shots
even
a
little
bit
of
integration.
Testing
can
be
done
on
as
long
as
you
have
a
page
inside
the
story
book
you
can
very
easily
plug
in
Cyprus
in
there
I
think
I
open
this
you
for
the
two
just
to
explore.
B
B
A
Yeah,
originally
we
were
doing
some
stuff
with
kind
we
may
revisit
that,
but
yeah
the
I
I
know
I
know
what
we
want
to
avoid
is
essentially
like
mocking
out
the
whole
API.
So
it's
not
really
doing
anything.
We
prefer
to
be
doing
some
integration
against
a
cluster.
We
do
have
a
the
team.
Has
a
cluster
that
lives
in
it's
a
gke
cluster.
A
A
That's
that's
tied
to
the
end
of
Sprint's
so
that
that's
a
little
more
predictable
we're
gonna
be
moving
to
two-week
Sprint's
cycle
that
really
shouldn't
that's
more
of
just
a
implementation
detail
for
for
the
for
the
community
and
people
who
want
to
contribute
but
know
that
that
that's
how
we'll
be
working
moving
forward
and
that
you'll
likely
start
to
see
a
release
that
comes
out
with
the
alignments
of
these
sprint
cycles.
Be
it
every
two
weeks
or
every
four
weeks.
That's
that's!
That's
kind
of
the
cadence!
A
We're
gonna
try
to
shoot
for,
and
that's
that's
really.
It
just
just
wanted
to
get
folks
informed
about
that
in
case
you're,
you're
planning
on
doing
some
upstream
contributions
or
you're
working
on
plugging
things,
or
things
like
that
know
that
we'll
be
doing
that
and
we'll
use
this
meeting
as
a
way
to
kind
of
demo.
The
the
mid
sprint
progress
for
everybody
and
get
feedback
in
and
prioritize
things
as
they're
coming
in
from
the
community.
A
So
that's
all
we
have
for
that
for
the
major
updates.
Then
I
wanted
to
get
into
a
couple
things
that
were
that
we're
considering
and
thinking
about.
One
is
the
thing
that
when
I
say
we
I
mean
mostly
just
me
right
now,
but
we're
starting
to
it's
starting
to
come
together
a
bit
more.
So
in
the
ODOT
14
release.
A
This
was
something
that
actually
came
up
out
of
a
conversation
around
the
current
go
plugins.
The
way
plugins
get
called
is
that
Calma,
the
handlers
in
a
plugin
are
called
on
our
event,
loop
cycle,
so
every
every
second,
your
your
plugin
handlers
are
being
called,
and
this
creates
using
rxjs
for
those
who
are
not
familiar
with
it.
It's
a
it's
a
behavior
framework
that
lets
you
set
up,
observables
and
and
conditions
and
subjects.
A
So
the
reason
I
put
this
in
there
as
a
demo
is:
it
shows
how
to
detach
your
running
plug-in
code
from
the
event
loop
of
octants.
So
if
you
have
a
job
that
you
only
want
to
run
at
certain
time
periods,
or
only
when
in
new
information
has
come
in,
you
can
use
rxjs
to
enable
that
workflow
in
a
very
easy
way,
so
that
you're
not
constantly
calling
some
remote
API
every
one
second,
and
so
that
that's
all
part
of
this
1141
PR
that's
up.
A
A
A
A
We
encourage
people
to
join
in,
but
the
idea
here
would
be
taking
like
what
taking
stuff
from
like
a
native
and
an
Tecton
and
being
able
to
actually
visualize
the
steps
that
are
be
that
are
being
taken
by
these
by
these
functions
and
and
and
show
that
in
a
way
that
eventually
it
would
be
initially
be
read-only
and
then
eventually
would
have
some
actions
and
you'd
be
able
to
retry
things
and
start
new
things.
So
that's
that's
a
feature
work
that
were
that
we're
looking
at
now.
A
That's
still
something
that's
very
important.
We
know
that
it
is
impacting
people
who
are
on
highly
restricted
clusters
and-
and
it
is
something
that
I
am
I'm
very
hopeful-
that
I
can
get
into
ODOT
15
so
will
I'm
targeting
for
that.
So
you
know
likely
for
weeks,
and
the
hope
is
that
that
will
that
will
finally
start
to
alleviate
some
of
those
issues
that
people
have
when
they're
dealing
with
like
restricted
clusters
or
credentials
that
expire
and
things
like
that.
A
The
the
the
catalyst
for
some
of
this
was
was
a
lot
of
the
work
that
Sam
did
with
allowing
octant
to
start
without
a
cube
configured
all
what
that
did.
Is
it
kind
of
detached
some
of
the
the
pieces
that
are
that
are
necessary
for
starting
octant
and
getting
it
running,
which
allows
us
to
now
have
the
like?
Almost
it's,
not
really
a
middleware,
but
essentially
a
middleware
a
space
to
do
work.
A
That's
just
the
air
output
from
a
console
message,
embedded
in
a
text
component
embedded
in
the
table,
which
is
not
a
great
experience
so
that
stuff's
all
there
in-flight
it's.
It's
still
very
important
to
me
and
it's
still
being
worked
on
and
that
that's
all
of
our
current
agenda
were
there
any
additions,
questions
comments.