►
From YouTube: Octant Community Meeting - July 29, 2020
Description
July 29, 2020
Agenda
Context selector to handle long context names in progress #909
--kubeconfig and environment variable currently broken for multiple kube configs
Stepper component in-progress
Open Q&A - add your questions here
Is dark mode for apply yaml editor broken? (Sam)
A
All
right
welcome,
folks
to
the
july
29th
2020
octane
community
meeting.
We
will
be
covering
a
couple
new
things
that
are
just
updates
around
some
open
issues
and
and
give
a
little
status
update
to
the
the
progress
of
some
of
the
the
new
things
that
are
coming
up
that
we
spoke
about
in
the
last
in
the
last
community
meeting.
So
I
believe,
let
me
share.
A
B
Cool,
so
this
one.
The
first
item
is
a
reference
to
issue
909,
it's
a
known
issue:
that's
been
around
for
a
little
while,
and
essentially,
if
you
have
a
context
name,
that's
super
long
and
perhaps,
if
you're
part
of
an
organization
that
tells
you
information
about
the
cluster
before
it
actually
gets
to
the
part
about
what
differentiates
the
context
name
at
the
very
end,
then
you'd
actually
have
this
drop
down
menu.
That
has
all
these
truncated
context
names
and
it
wouldn't
be
a
very
useful
drop
down.
B
So
we're
still
exploring
options
on
what's
the
best
way
to
go
about
this.
A
lot
of
this
just
seems
to
be
coming
from
the
limitations
of
the
clarity
component
and
we're
really
doing
everything
we
can
to
avoid
re-implementing
our
own
component,
because
the
clarity
component
comes
with
some
free
accessibility
options
for
screen
readers
and
such
that
we
don't
really
want
to
implement
by
hand,
but
if
it
really
comes
down
to
it,
I
think
we
will
do
it
anyways.
B
A
B
And
I
guess,
by
extension,
the
environment
variable
as
well,
so
currently
the
if
you
were
to
use
a
file
list
of
cube
configs
separated
by
colon
in
previous
versions
of
octane.
It
would
work,
but
we
recently
did
a
bunch
of
refactoring
on
a
loading
state
for
the
api
when
octan
is
starting.
So
this
ends
up
this.
We
ended
up
breaking
the
supporting
multiple
key
configs.
So
we
will
have
that
patched
up
soon
and
hopefully
push
out
a
release
to
fix
that.
A
A
Who
authored
the
jenkins
x,
plugin
that
came
out
recently
and
they
have
a
desire
to
get
this
in
place,
and
I
know
that
there's
some
the
helm
folks,
the
that
implemented
that
plug-in
they
were
hoping
to
have
some
type
of
of
wizardy.
You
know
stepper
components
so
that
that's
currently
in
progress,
we're
working
on
that
now,
there's
a
there's
a
draft
pr
up,
but
it's
still,
it's
probably
going
to
be
another
day
before
that
thing
is
ready.
I
was
struggling
with
angular
and
various
things,
so
the
that's
coming.
A
If
you're
running
a
local,
if
you're
running
a
un
self-signed
cluster,
so
if
you
have
a
self-signed
certificate
and
and
and
a
local
authority
right
now,
octane
will
throw
an
x-509
error
was
finally
able
to
reproduce
that
and
see
exactly.
It
was
actually
keep
ctl
kind
of
helped
me
to
figure
out
how
they
I
went
and
inspected
how
they
were
dealing
with
that
and
it
was
able
to
kind
of
come
up
with
a
solution.
That'll
be
used
in
octan.
A
So
folks,
who
are
running
clusters
in
that
fashion,
will
be
able
to
actually
use
octant
with
them.
And
there
was
another
thing
and
it's
it's
we
just
merged
it
in.
I
can't
remember
what
it
was.
It
was
a
fix
that
you
might
have.
Oh
the
web
hooks.
So
if
you
were
using
0.15
with
octane
and
you
went
to
go
to
like
resource
viewer
and
it
had
a
connection
to
any
web
hooks,
it
was
failing
to
generate
a
view
at
all.
A
That
was
storing
an
air
and
the
reason
was
because
we
were
there
was
two
pieces
to
it.
You
can
see
it
in
the
in
the
issue,
but
the
we
weren't,
depending
on
the
server
to
do
the
the
upgrade
we
were.
We
were
just
assuming
that
it
was
v1,
and
then
we
were
also
using
the
server's
preferred
version
of
the
resource.
So
even
if
you
had
both
installed,
when
oxen
went
to
create
a
watcher
to
to
get
a
list
of
those
resources,
it
would
pull
this.
A
It
would
ask
the
server:
what's
your
preferred
version
and
then
it
would
attempt
to
use
that
version
for
all
of
the
of
the
resources
instead
of
using
the
one
for
the
actual
resource
itself.
The
upside
there
is
that
if
it
was
going
in
the
correct
direction,
it
could
always
convert
to
the
to
display
that
resource.
But
in
this
case,
was
trying
to
go
the
other
direction.
A
It
was
failing
to
convert
the
resource
because
it
wasn't
supported
so
scott
fixed
that
that'll
be
coming
out
when
we,
when
we
cut
our
next
release
as
well,
so
that
that
should
unbreak
some
some
people
who
were
who
were
running.
I
know
that
by
default,
if
you
spin
up
a
new
gte
cluster
and
do
web
hooks
on
it,
you
get
you
get.
A
B
A
Yeah,
I
think
I
think
it
is
bro.
I
think
I've
seen
enough
people
using
octane
with
dark
mode,
enabled
pull
up
the
editor
and
it
be
in
light
mode
that
I
I'm
willing
to
say
that.
Yes,
it
is
it's
it's
malfunctioning,
I
wouldn't
say
it's
broken,
because
if
you
like
go
and
manually
toggle
the
toggle
it
right
well
broken
whatever
I'm
splitting
hairs,
it's
it
is
broken,
but
it
is
also
it's.
It
works,
but
it's
malfunctioning
so
yeah,
it's
broken
so
yeah.
A
If
we
don't
already
have
an
issue
for
it,
let's
go
ahead
and
create
one
and
and
we'll
get
that
we'll
get
that
try
and
get
that
resolved
as
well,
because
that's
an
annoying,
definitely
an
annoying
thing
when
you're,
especially
if
you're
like
me,
where
you're
like
everything
on
your
desktop,
is
in
dark
mode
if
possible,
and
then
all
of
a
sudden
you
get
blast
in
the
eyeballs
with
white
background,
it
can
be
jarring
in
the
middle
of
the
night.
So
yeah
we'll
we'll
look
at
getting
that
fixed.