►
From YouTube: Octant Community Meeting - April 28th, 2021
Description
Octant community meeting is held weekly. We discuss and talk about the current state and future of Octant, demo upcoming features and releases, and preview new ideas we are considering for Octant.
Meeting agenda: https://hackmd.io/CzaPxtmXT_SW8nEpdwvGzw?view
A
All
right,
everyone,
hello,
welcome
to
the
april
28th
octant
community
meeting.
We've
got
a
few
things
on
the
agenda
today
and
I
think
we
were
supposed
to
have
some
folks
in
kubeflow
show
up,
but
they
had
to
bump
to
next
week.
So
that's
fine!
If
there
are
any
things
to
add
to
the
agenda,
feel
free
to
add
them
to
the
hackmdoc.
A
All
right-
and
let
me
actually
do
some
shenanigans
here,
so
we're
not
sharing
the
scripture
cool
all
right,
so
the
first
thing
on
the
agenda,
so,
oh,
not
20.
I
think
I'm
gonna
make
the
call
to
push
this
out,
maybe
a
week
currently
right
now,
as
of
today,
we
are
a
little
behind
on
well,
not
necessarily
behind.
A
I
think
we're
exactly
right
where
we
need
to
be
with
vacations
and
engineers
on
vacation,
but
just
simply,
I
think,
just
looking
at
our
change
logs
at
the
moment,
we
don't
really
have
enough
changes.
I
think
that
merits
a
release
and
we're
trying
to
target
some
key
features.
If
we
look
into
our
0.20
project
log,
I
think
the
key
features
that
we
really
want
to
get
in
here
are
one
making
sure
we
have
these
new
form
changes
in
master,
and
I'm
also
personally
doing.
A
I
guess
this
is
in
progress
and
I'm
trying
to
get
this
stepper
component
inventing
off
the
ground
simply
because
dynamic
steppers
has
been
something
that's
been
requested
for
a
while
the
remaining
items
I
think
they
can
be
bumped
out,
but
really
I'd
like
to
see
these
form
changes
go
into
0.20.
A
So
I'm
going
to
just
be
a
little
bit
generous
with
the
time
I
think
originally,
I
said
push
to
may
2nd,
which
is
next
monday,
but
I
think
it
will
probably
realistically
be
next
wednesday
so
slightly
longer
than
that,
and,
of
course,
if
there's
someone
who
is
currently
awaiting
any
of
the
issues
which
are
in
master,
it's
a
reminder
that
we
do
have
nightly
builds
and
I
think
pretty
much
what
the
some
of
the
changes
like
give
you
like
tool
tips
or
something
styling
for
buttons
so
like.
A
If
you
need
any
of
these
things,
you
can
always
grab
it
from
the
nightly,
but
otherwise
the
release
will
have
to
wait
a
little
bit
cool.
A
Cool
all
right,
then,
moving
on
to
the
next
item
on
the
agenda,
so
this
is
a
officially
the
new
release
for
the
octan
helm
plug-in.
I
talked
about
it,
I
think
at
the
last
community
meeting,
but
this
time
there
is
a
release.
That's
been
formally
cut
this
time,
and
this
is,
I
think
I
even
could
demo
it
if
we
want
yeah.
Let's
do
a
demo,
I
feel
like
we
don't
get
enough
demos.
A
A
Alright,
so
helm
plug-in,
I
believe
I
have
it
installed
since
yeah
since
the
time
that
I've
basically
cut
the
release.
So
the
first
thing
that
you're
going
to
see
with
this
helm
plug-in
is
right
now
you're
going
to
have
this
table
of
releases,
and
I
think
we
talked
about
last
time.
There
are
like
uninstalled
menus,
but
the
cool
thing
is
we
added
the
sub
routes.
So
we
get
these
chart
repositories.
A
Now
you
can
see,
you
know,
I
think,
there's
like
the
bitnami
one
jet
stack
and
then
engine
x
ingress
has
its
own
and,
I
believe,
like
the
helm,
stable.
I
believe
this
is
being
deprecated,
I'm
not
sure
what
the
situation
is,
but
we
can
see
like
you
know
like
totally
like.
We
could
add
a
button
here
and
they
could
like
have
an
input
and
we
could
like
recommend
urls
right
or
like
people
can
like
point
to
their
own
repositories
or
remove
them.
A
So
there's
work
to
be
done
here,
but
this
is
kind
of
cool
it.
Just
kind
of
bubbles
up
this
notion
of
chart
repositories
right
so
like,
ultimately,
this
the
goal
of
a
plug-in
like
this
is
to
let
people
who
aren't
familiar
with
helm
just
do
stuff
all
right
and
without
having
to
figure
out
what
all
the
command
line
commands
are.
A
So
the
one
that
I
think
is
of
interest
is
probably
something
like
nginx
ingress
here,
because
we
always
use
nginx
for
all
examples
right
and
we
can.
I
can
demo
something
like
an
upgrade
right.
So,
like
let's
say
we
look
at
our
nginx
controller
here
and
let's
say
we
want.
You
know
this
is
kind
of
like
the
vanilla
chart
deployed
one
from
helm
and
let's
say
we
want
to
update
like
an
environment
variable
right
like
there's
like
ld
preload,
there's,
pod
name
and
pod
namespace.
A
We
can,
we
can
see
if
we
can
add
you
know,
add
another
one
in
here
and
see
how
that
goes,
and
so
the
next
feature
that's
added
up
here-
is
going
to
be
this
values
tab.
It
currently
shows
all
of
the
default
values,
there's
a
lot
of
stuff
and
right
and
how
helm
basically
works.
A
It
kind
of
takes
this
piece
of
yaml
and
it
shoves
it
into
the
templating
where
it's
you
know,
wherever
it's
applicable,
but
in
this
particular
case
right,
we're
interested
in
our
controller,
and
I
think
we
said
we
want
to
do
like
an
environment
variable.
So
we
could
do
something
like
I
don't
know
name.
What
do
we
want
to
call
our
environment
variable?
A
Let's
call
it
hello
value
world,
you
know
not
very
creative
right.
We've
got
an
upgrade
button,
let's
see
if
this
goes
through
update
boom,
so
we've
upgraded
our
release,
and
so
now
we
see
this
provision.
History
kicks
off
right,
the
old
release
is
superseded,
and
this
has
updated
12
seconds
ago.
So,
let's
check
out
what's
going
on
in
podland,
so
we
can
see
one
out
of
two,
so
it's
currently
doing
the
upgrade
it's
killing
off
the
old
controller
and
it's
spinning
up
the
new
one
and
the
new
one
is
spun
up.
A
So
let's
take
a
look
at
it
and
we've
got
you
know
our
new
environment
variable
hello
world
right.
It's
kind
of
that
easy!
Well,
it's
not
really
that
easy.
There
are
probably
a
ton
of
cases
where,
like
a
ton
of
veg
cases,
right
like,
for
example
like
if
you
have
a
if
you
want
to
have
an
upgrade,
that
requires
a
secret,
that's
kind
of
not
possible
right
now
and
of
course
like,
depending
on
the
templating.
Sometimes
just
naively
upgrading
doesn't
work.
A
So
this
is
kind
of
a
happy
case,
but
you
know
I
think
this
kind
of
just
shows
like
the
potential
for
what
plugins
can
do
and
which
is
ultimately
the
goal
of
the
recent
updates
and
then
finally,
when
we're
done
with
this,
you
know
we,
let's
say
we
don't
care
about
engine
x
anymore,
let's
uninstall
it
and
hopefully
our
engine
x
is
gone.
So
there
you
go
a
couple
of
features
off
the
bat
with
the
new
plugin,
so
0.2
check
it
out
more
of
that
coming
soon,.
A
A
All
right
cool
moving
on,
we
got
our
website
migration
to
hugo.
This
is
a
special
thanks
to
jonas.
I
think
he
coordinated
some
of
this
work.
I
am
aware
that
the
site
is
down
and
it
actually
it
caused
some
side
effects
to
reference
reference.dev.
A
I
know
the
reason
why,
but
I
got
locked
out
of
the
netlify
account,
so
I
don't
have
permissions
to
do
things
at
the
moment,
but
the
site
right
now.
I
think
it's
just
well.
Actually
we
need
to
update
readme
and
stuff
as
well,
but
we
can
see
like
now
it's
using
hugo
and
it's
doing
all
the
hugo
things
and
I
think,
for
the
most
part,
build
speed,
doesn't
really
matter
for
us.
A
That's
one
of
the
big
pull
to
hugo,
but
the
cool
part
about
hugo,
I
think,
is
that
it's
gonna
line
up
a
lot
nicely
with
all
the
other
vmware
open
source
website
build
so
like
contour
and
valero.
That
looks
all
the
same
way,
and
it
also
opens
up
the
idea
so
like
if
you
look
at
something
like
valero
dot
io,
you
know,
like
the
site.
A
Pretty
much
looks
mostly
similar
right
so
like
we
can
see
a
world
where
all
of
the
vmware
open
source
websites
just
build
off
of
the
same
theme
and
so
like.
If
valero
implements
like
a
versioning
scheme,
we
can
do
the
same
thing
with
having
duplication
across
multiple
open
source
projects.
So
this
is
more
of
like
a
long-term
vmware
thing,
but
I
think
it's
it's
kind
of
cool
that
we
made.
A
We
made
this
move
over
and
we're
gonna
get
this
website
fixed,
of
course,
as
soon
as
possible,
but
just
heads
up,
if
you're
looking
for
reference.dev
at
the
moment,
I
think
it
repoints
to
just
a
doc
site
yeah
and
that's
just
because
it's
being
overwritten
by
our
netlife
configuration.
A
So
we
will
get
that
over
and
if
like,
and
if
I
can't
get
permission
to
in
a
reasonable
amount
of
time,
I'm
just
going
to
reverse
the
commit
temporarily,
and
then
we
can
just
redo
this,
like
whenever
I
get
the
proper
permissions.
A
Yeah
for
development
work,
you
could
probably
get
it
working
with
a
fork
if
you're
willing
to
toggle
the,
if
you're
willing
to
toggle
some
netlife
settings
on
your
end.
But
obviously
it's
nicer.
It's
nicer
if
it
just
works
out
of
the
box
right,
but
yeah.
Currently
out
of
my
control,
I
can
paint
some
people
to
figure
out
who
can
give
me
access
to
it
or
who
has
access
to
it.
But
that's
just
kind
of
you
know
large
company
issues,
nothing,
no,
nothing
can
be
done
about
it.
A
No
I'll
wait!
That's.
A
No
okay
cool,
so
I
was
originally
reserving
a
slot
for
the
open
q
a
for
some
kubeflow
plug-in
discussion.
I
don't
know
if
there's
anyone
who's
on
the
call
who
can
speak
to
that?
A
I
don't
think
so.
I
think
george
reached
out
and
said
he
couldn't
make
it
and
I
believe
I
think
it's
gonna
be
next
week,
so
we
can
keep
those
discussions
going,
as
always
like.
I
think,
the
getting
plug-in
work
and
just
building
up
that
ecosystem
is
really
what
octan
is
all
about
right.
So
if
someone
comes
up
to
us
and
say
we
like
about
a
plug-in
and
we
need
help
doing
it,
that
does
get
her
attention
very
quickly.
A
So
for
anyone
else,
who's
on
this
community
call-
and
you
know-
has
thoughts
of
round
plugins
once
a
dota
plugin
feels
intimidated
by
the
process
like
definitely
reach
out
we're
willing
to
invest
in
that.
A
All
right
cool
well,
does
anyone
else?
Have
any
questions
for
open
q,
a
no
all
right?
Well,
if
everybody's
happy,
then
we
can
call
it
a
little
early
today,
pretty
much
you
know.
As
always,
if
there
are
any
questions
to
follow
up,
always
feel
free
to
ping
on
slack
or
hoping
to
get
at
the
issue
and
we'll
get
back
to
it.