►
Description
wasmCloud is a platform for writing portable business logic that can run anywhere from the edge to the cloud, that boasts a secure-by-default, boilerplate-free developer experience with rapid feedback loop.
https://wasmcloud.com
A
To
awesome
cloud
wednesday
for
july
6th,
we
usually
get
started
with
a
demo,
but
today
we
have
something
just
as
exciting
and
I'll
hand
it
off
to
taylor
to
talk
about
it.
C
Thanks
brooks
so,
let's
go
ahead
and
talk
about
some
exciting
things
of
governance.
Okay,
no
honestly,
this
is
it's
more
than
just
that.
I
want
to
show
kind
of
what
we're
planning
on
doing
and
then
it'll
give
people
the
chance
to
kind
of
answer
or
like
look
at
things
and
answer
me
and
ask
any
questions
they
might
have.
C
So
we
for
a
while
have
been
kind
of
just
going
forward
with
the
project
we've
had
lots
of
people
from
the
community
contribute.
We
haven't
had
a
clear
way
for
people
to
become
contributors
contributors.
So
to
that
end
we
wanted
to
make
sure
we
kind
of
laid
out
at
least
a
basic
framework.
These
documents
are
not
meant
to
add
a
ton
of
process
or
anything.
C
I
helped
write
the
first
draft
of
helm,
so
there's
a
large
chunk
of
those
that
are
still
things
that
I
wrote
and
I
figured
I
didn't
want
to
rewrite
it,
because
all
humans
are
lazy
and
then
also,
I
really
loved
what
porter
did
for
the
contributor
ladder.
So
what
we've
done
is
is
put
those
all
together,
we've
completely
revamped
our
contributing
documents,
we've
also
added
a
contributor,
a
contribution
ladder
or
a
contributor
ladder.
C
It's
called
this
because
it's
kind
of
like
the
rungs
you
you
follow
to
be
able
to
become
a
maintainer
of
a
wasm
club
project.
So
there's
there's
three
different
kinds:
there's
a
community
member
which
pretty
much
everyone's
a
community
member.
So
those
are
different
things
that
you
can
do
and
kind
of
give
some
suggestions
of
how
to
start
getting
involved
in
the
community.
C
After
that,
we
get
to
an
actual
contributor
level,
which
is
someone
who
does
the
the
basic
like
triaging
of
issues
and
pr's,
that
they're
able
to
contribute
code
and
have
issues
and
things
that,
like
directly
assigned
to
them,
they
can
apply
different
labels
and
things
they
can
and
they
just
help
kind
of
that
basic
triaging
stuff.
It's
kind
of
the
precursor
to
becoming
a
project
maintainer
and
a
project.
C
Maintainer
is
someone
who
is
over
one
or
more
different
projects
inside
the
wazon
cloud
space
that
could
be
if
you're
interested
in
capability
providers
and
help
write
a
lot
of
capability
providers
and
update
the
ones
we
have
then
perhaps
becoming
a
maintainer
of
the
capability
provider
project
would
be
good
for
you.
Some
people
might
want
to
work
on
the
host.
Some
people
might
want
to
work
on
the
interfaces.
It
just
depends,
and
so
that's
how
that's
what
we
have
is.
C
We
also
point
out
here
that
some
maintainers
might
not
be
code
based
maintainers,
some
people
might
more
might
be
more
along
the
lines
of
like
community
management.
If
that's
your
type
of
thing
and
you
like
doing
it,
please
let
us
know
we
love
to
try
to
enable
those
people
to
contribute
in
the
way
they'd
like
to
contribute
as
well.
C
So
this
is
going
to
be
a
nice
thing
for
people
to
be
able
to
follow
and
know
exactly
how
you
can
become
a
maintainer
rather
than
just
going
well,
do
I
just
kind
of
contribute
stuff
or
whatever
it
gives
us
some
specific
steps
that
you
can
follow
to
be
able
to
become
a
maintainer,
so
we've
added
that
in
there
and
like
so,
we've
also
had
the
contributing
thing.
This
has
the
full
detailed
thing
of
how
we
contribute
stuff,
how
we
add
how
we
handle
issues.
What
tags
are
sorry
labels
that
we
have?
C
There's
also
the
governance
side
of
all
this,
and
one
of
them
is
the
whole
idea
of
a
security
document.
This
is
the
thing
we've
been
following
before
we've
already
done
this
once
with
a
with
a
security
issue,
we
found
on
the
wasm
cloud
host,
but
we
have
created
a
a
whole
list
of
of
how
we
do
security
reports.
We
have
an
initial
list
that
I
just
put
together.
If
you
are
another
maintainer
who
is
on
this
call
or
and
and
is
involved
in
the
organization
would
like
to
be
on
there.
C
Let
us
know
these
are
always
made
up
of
project
maintainers
or
org
maintainers,
and
so
this
just
shows
exactly
how
we
acknowledge
vulnerabilities,
how
we
report
them,
how
they're
they're
sent
out,
and
obviously
this
can
continue
to
be
improved
as
the
project
grows
and
more
people
use
it.
So
if
we
get
to
a
future
in
two
or
three
years,
when
there's
multiple
big
companies
who
are
trying
to
use
things
for
mods
and
cloud,
then,
for
example,
we'll
probably
have
an
early
like
disclosure
list,
those
kind
of
things
you'd
normally
have.
C
We
don't
have
that.
Yet
we
just
are
trying
to
keep
a
bare
minimum,
and
the
governance
explains
just
the
very
basic
levels
of
like
how
how
do
we
run
the
project,
so
it
talks
about
the
contributor
ladder
it
talks
very
specifically
about
org
maintainers
and
how
we
vote
on
specific
things
and
also
how
project
level
maintainers
can
vote
as
well
as
licenses
that
we
use.
C
So
it's
just
a
very
basic
structure
meant
to
kind
of
codify
exactly
what
we've
already
been
doing
and
add
a
few
other
things
that
just
kind
of
help
keep
everything
organized
based
on
on
things
I've
experienced
in
the
past,
but
I
am
by
far
the
only
person
who
has
worked
extensively
in
open
source.
So
the
reason
this
is
open
as
a
pr
is
so
that
the
community
has
sufficient
time
to
go
in
and
make
sure
that
everything
looks
okay.
C
If
there's
something
that
concerns
you
or
something
that
needs
to
be
addressed,
we
want
to
make
sure
these
things
are
covered
inside
of
this
pr
and
then
once
this
is
adopted,
we'll
start
following
its
processes,
so
we'll
come
with
with
basically
the
initial
list
of
org
maintainers
and
then
make
sure
there's
project
maintainers
that
are
that
are
specified
out
there
and
then
having
a
nice
like
structure
in
place
to
follow
as
we
go
forward.
So
that
is
what
what
this
does
it's
I
mean
it
can
be
considered
boring.
C
I
get
it,
but
also
it's
a
critical
part
and
shows
the
maturity
of
the
project,
especially
as
we
continue
to
move
forward
into
probably
incubating
in
the
cncf
and
and
other
things
along
those
those
lines,
because
we
want
to
make
sure
that
the
people
know
how
they
can
contribute
and
follow
those
those
kind
of
procedures.
So
that's
all
I
have.
I
will
turn
over
any
questions
to
floor.
There's
surprisingly,
no
questions
in
chat,
which
means
most
people
probably
considered
it
boring,
which
is
totally
fine.
A
I
I
have
a
good
question
for
myself.
Actually,
so
you
know
I
I've
seen
over
the,
like
course
of
the
wasp
project,
that
there
are
people
that
are
you
know.
Contributors
now,
who
I
feel
like
would
be
good
at
like
good
candidates
for
like
project
maintainers,
like
people
to
like
outside
of
the
core
team
as
we're
doing
this
and
expanding
who
would
work
well
on
the
like
higher
up
the
ladder?
What's
the
the
process
that
you've
seen
before
taylor
is
it
like?
A
C
This
is
this
is
the
let
me
google
that
for
you
treatment,
so
this
is
explicitly
stated
in
the
contribution
ladder.
The
idea
is
that
we
do
watch
out
for
people
who
do
it.
I'm
going
to
be
fully
and
completely
transparent
here.
If
we
merge
this,
for
example,
as
is
people
who
are
already
contributing
and
doing
things
to
watsonville,
there's
no
like
process
to
follow
we're
just
going
to
reach
out
to
you
and
say:
hey.
You
are
already
kind
of
a
contributor.
C
Do
you
want
to
officially
become
a
contributor
under
this
new
system
and
boom?
Add
you
as
a
contributor
there's
not
gonna,
be
anything
official,
no
one's
gonna,
no
one's
starting
from
scratch
or
anything
we're
just
going
like
the
first
step
is
done
by
basically
by
fiat.
We
just
say
here:
are
the
org
maintainers
we're
not
holding
a
vote,
we're
not
doing
anything.
This
is
like
this
is
who
it
appears
to
be,
and
then
we
start
from
there
we're
a
new
project.
We
don't
have
to
make
this
super
fancy.
C
We
don't
have
to
have
a
bootstrapping
vote
or
you
know
we
don't
have
to
have
the
13
states
ratify
the
constitution,
sorry
for
the
u.s
specific
joke,
but
like
we
don't
have
to
do
anything.
Super
fancy
we're
just
going
to
go
like
start
doing.
This
take
the
best
guess
of
the
people
who
are
out
in
the
community,
especially
and
if
you're
like,
oh,
I
was
already
planning
on
helping
maintain
like
the
the
capability
providers
or
something
then
like.
C
Please
let
us
know
just
in
case
we
miss
you,
we're
not
trying
to
miss
we're
not
trying
to
miss
anybody,
we're
just
trying
to
start
something
and
go
from
there.
We
do
keep
an
eye
out,
though,
that's
generally
how
this
works,
though,
like
we
say
like
if
you,
if
you
are
on
this
call
and
you're
like
oh
I've,
wanted
to
contribute,
and
I've
only
been
doing
some
small
things
reach
out
to
us,
we're
going
to
say.
Oh,
that's
great
and
kind
of
coach
you
through
the
whole
thing.
C
Stunned
silence.
Okay,
so
if
anyone
has
any
questions
or
comments,
please
drop
it
on
there.
I
prefer
to
keep
these
open
for
a
week
or
two,
because
it's
a
big
change,
I'm
gonna,
want
to
make
sure
people
have
time
to
see
that
this
is
happening.
So
probably
my
personal
feel
on
this
is
we
should
wait
until
one
more
wasn't
cloud
meeting
next
week
give
people
the
reminder
that
this
is
there
and
then,
by
the
end
of
the
week,
merge
it
so
that
gives
people
basically
a
week
and
a
half
to
look
at
this.
C
If
we
feel
like
we
haven't
gotten
enough
feedback
or
things
from
people,
we
can
also
extend
it
a
little
bit
further
because
you
can
generally
go.
If
you
look
at
the
actual
governance
document,
we
say
that
a
lot
of
things
are
done
like
within
three
weeks
for
like
a
big
decision
like
adopting
a
new
org
maintainer,
or
something
like
that
so
but
generally
a
week
and
a
half
given
the
size
of
our
project
is
probably
good
enough.
So
that's
kind
of
the
next
steps
here.
D
Solid
work,
taylor.
I
know
that
was
a
lot
of
a
lot
of
work
and
I
really
appreciate
the
all
the
attention
you
put
into
this.
You
know
this
is
there's
the
the
level
to
go
from.
Sandbox
to
incubation
is
the
biggest
leap
in
the
cncf,
and
you
know
this
is
certainly
one
of
the
rungs
in
the
ladder
that
we
need
to
cross.
So
I
really
appreciate
all
the
all
the
effort
on
this.
A
Thank
you,
taylor.
I
actually
didn't
have.
I
don't
have
a
demo
for
today.
Does
anybody
have
something
fun,
something
cool
that
they
did
with
wasn't
cloud
that
they
wanted
to
show
off?
We
kind
of
have
some
some
extra
time
in
the
demo
section.
A
All
right,
I
thought
I
would
give
some
some
time
there
for
an
open
floor.
There
are
a
couple
of
things
from
the
wasn't
cloud
perspective.
I'd
love
to
talk
about
now:
oh
hey,
taylor,
demo.
C
No,
not
a
demo.
I
just
remembered
something
I
wanted
to
point
out.
I'm
pretty
sure
liam
can
correct
me
if
I'm
wrong
here,
but
the
cf.
The
cfp
is
open
for
the
next
cloud
native
wasmday
in
detroit,
so
that
is
very
applicable
to
this
audience.
Even
if
it's
not
wasn't
cloud
related,
just
please
submit
to
that.
C
We
love
having
this
last
one
was
really
cool
to
see
the
whole
different
uses,
use
cases
that
were
out
there
for
everybody,
and
so
we're
obviously
going
to
be
there
actually
currently
most
of
the
the
people
who
work
at
cosmonaca
are
all
planning
on
being
there.
So
that's
a
good
chunk
of
the
the
core
team
is
going
to
be
there.
So
if
you
want
to
just
like
chat
about
anything
laws
and
cloud
related
that'd
be
great.
C
C
We
love
any
of
those
types
of
things,
so
I
just
remembered
that
we
wanted
to
point
that
out
that
this
is
open
and
please
let
us
know
if
you
are
are
interested
in
maybe
getting
together
for
an
event
if
people
are
going
to
be
there
if
we
get
even
if
we
have
like
three
to
five
people
there
who
all
want
to
talk
was
in
cloud
plus
the
wasm
cloud
maintainers
who
are
there,
I
mean
that's,
that's
enough
to
have
a
really
fun
like
place.
C
We
can
reserve
a
room
somewhere
and
be
able
to
to
hack
and
and
do
whatever
we'd
like
and
just
talk
about
cool
things
we're
doing
with
webassembly.
So
please,
please!
Let
us
know
if
you're
interested
in
that
and
please
do
go,
submit
talks,
even
if
we're
not
saying
just
that
there
wasn't
clutter
related
anything
wasm,
please
go
submit
to
this.
C
This
cloud
native,
wasn't
wasabi
this
day
has
been
really
really
fun
and
after
having
attended
some
other
days
at
other
conferences
recently,
like
I
can
tell
you
this
one
is
still
one
of
the
most
interesting
and
enjoyable
out
there.
It's
it's
kind
of
like
having
our
own
conference
and
it's
just
been.
The
content
is
very
high
quality.
So
I
have
I
highly
recommend
submitting
to
this
and
definitely
recommend
going
to
it.
It's
very
worth
any
any
money
you'll
spend
on
it,
so
just
pointing
that
out.
A
Yeah
and
please
feel
free
if
you're
thinking
about
writing
a
proposal
for
the
first
time
and
not
really
sure
where
to
start
or
anything.
Some
of
the
people
on
the
core
team
here
are
very
experienced
of
giving
talks
at
conferences,
so
I'm
gonna
go
ahead
and
whoops
sign
you
up
taylor,
but
taylor
really
helped
when,
for
all
of
the
cfps
that
I've
written
for
conferences,
it's
been
super
helpful,
so
you
know,
even
if
you're
wondering
if
your
use
case
is
exciting
enough
for
this,
it
is,
and
you
should
submit.
D
I'll
just
add
in
you
know,
in
past
conferences,
you
know
we
you
know,
are
willing
to
invest
a
lot
of
time
with
you
one-on-one.
If
there's
topics
that
you
want
to
develop
for
the
for
the
conference,
we
really
try
to
balance
diversity
and
content
and
diversity
and
speakers
prioritize
new
speakers
and
prioritize
new
topics.
So
the
webassembly
community
is,
you
know,
a
total
reboot
on
cloud
native.
So
there's
I
think,
openings
across
the
board
here
for
every
topic.
I
mean
best
practices,
real
world
use
cases.
D
You
know
developer
tooling
languages
and
you
name
it.
The
topics
are
completely
wide
open.
So
if
you
have
something
you're
interested
in,
we
have
a
lot
of
spots
to
fill
and
the
topics
range
from
you
know
from
lightning
talk:
regular
talk
to
maybe
even
training
or
demonstration
sessions.
So
please
feel
free.
If
you
have
thoughts
or
ideas.
Just
drop
me
a
note
or
one
of
the
other
team
members
of
note
and
we'll
happily
collaborate
with
you
to
make
something
happen.
D
Can
hear
all
the
kids
in
the
background
screaming?
I'm
sorry!
I
have
no
idea
what
just
happened.
Somebody
apparently
just
I
think
my
cousins
just
arrived
at
at
the
house
and
all
their
all
the
kids
there's
like
now,
nine
kids
here
or
all
just
saw
each
other
and
they
go
full
muppet.
When
that
happens.
A
A
D
A
A
Yeah,
thank
you.
Taylor
definitely
go
up
submit
proposals.
I
had
a
couple
of
things
from
the
walls
of
cloud
side.
We
did
publish
another
blog
post
last
week.
You
can
find
this
at
wasmcloud.com
blog,
the
one
on
distributed
webassembly
applications.
This
is
a
essentially
a
setup
guide
for
nats
and
ngs,
and
it
takes
you
from
installing
wasmcloud
on
your
local
machine
to
running
an
application.
Here's
a
little
diagram
that
I
like
to
show
but
running
an
application
across
your
local
on
another
cloud
or
on
an
edge.
A
What
have
you
it's
just
easily
connected,
then
gs
so
would
highly
recommend
if
you
are
interested
in
how
to
get
that
set
up.
You
check
out
the
blog.
This
was
one
of
I
wrote
this
one,
this
one
my
favorite
ones
to
write.
This
is
what
powers
a
lot
of
the
magic
of
our
recent
demos,
and
it's
just
really.
It's
really
exciting
to
get
this
out
there,
because
it's
not
magic
and
it
doesn't
require
hours
and
hours
of
infrastructure
set
up
or
anything
like
that
which
is
really
cool.
A
A
All
right,
so
I
wanted
to
mention
the
most
recent
blog.
It's
always
fun
to
talk
about
the
blogs
that
we're
putting
out.
I
also
and
great
timing.
Kevin
just
came
in
here.
I
wanted
to
bring
up
this
pr
into
wadom.
A
We've
talked
about
wadom
intermittently
over
community
calls,
and
in
the
last
one
we
actually
demoed
or
kevin
demo
the
initial
functionality
for
deploying
and
undeploying
an
application.
This
is
really
the
way
that
we're
going
to
do
declarative
application
management
with
wasmcloud
kevin.
Did
you
want
to
talk
about
this
first
pr
that
you
put
out
a
little
earlier
either
today
or
this
week.
B
You
know
you
know
like
it
says
it's
basically,
the
initial
implementation
of
doing
declarative
deployment,
so
you,
if
you're,
if
you're,
using
the
absolute
latest
version
of
wash,
which
hasn't
yet
been
merged,
I've
got
some
changes
in
the
pr
still
waiting
for
that
one
then
you'll
be
able
to
do
things
like
submit
a
yaml
file
for
a
declarative
application
and
you'll
be
able
to
do
things
like
issue
deploy,
commands
and
undeploy,
and
when
you
deploy
you
know,
the
autonomous
agent
will
monitor
the
state
of
a
given
lattice
and
if
it
detects
divergence
between
what
your
spec
says
and
what
the
lattice
has,
it
will
make.
B
B
The
only
real
sort
of
warning
that
I
would
have
is
that
this
is
the
the
first
implementation,
so
it's
definitely
still
experimental.
There's
no,
I
wouldn't
recommend
using
it
for
anything
that
needs.
You
know
guarantees
of
no
bugs
things
like
that.
This
is
all
still
basically
just
getting
something
checked
in,
so
that
we
can
start
iterating
on
it,
because
up
until
this
point
too
much
of
this
stuff
has
just
been
in
my
head.
So
you
know
now
that
it's
it's
out
there.
E
Kevin
questions
and
comments.
I
suppose
I
see
that
the
two
lattice
control
command
stuff
is
in
there,
which
is
great,
because
that
was
a
part
that
I
wasn't
entirely
sure
how
we're
going
to
implement
with
the
original.
I
guess
idea
of
actually
happening
or
using
the
kubernetes
operator
to
do
this.
E
How
do
we
want
to
provide
feedback
to
it?
And
I
would
assume
at
this
point
in
time,
because
the
reconciliation-
actually
you
see,
occurs
in
one
of
them
that
the
operator
will
just
be
something
that
reflects
status
as
opposed
to
try
to
reconcile
anything
or
send
any
commands
down,
except
for
the
initial
file,
but
I'm
not
clear
on
like
what
we
want
to
do
for
a
status,
and
I
guess
I
mean
I
know
taylor
has
lots
of
experience
here
as
well,
so
yeah.
B
If
there's
a
couple
of
things
that
I
think
are
are
kind
of
hard
and
fast
rules,
if,
if
a
kubernetes
operator
was
to
take
advantage
of
what
I'm
under
the
hood,
the
operator
itself
would
not
be
responsible
for
reconciliation.
B
Wadam
should
be
the
only
thing
that
does
reconciliation
right
now.
You
would
probably
be
able
to
maintain
some
really
really
high
level
state
as
we
keep
iterating
on
whatem
there
inside
the
pr
you'll
actually
see.
There's
there's
a
comment
that
the
state
machine
that
we're
using
is
not
fine-grained
enough.
B
We're
not
modeling
enough
states,
so
that
will
eventually
get
better
and
scheduled
for
this
week
or
sometime
early
next,
I'm
also
going
to
put
in
some
stuff
in
wadam
where
we're
emitting
events
every
time
wadam
takes
an
action,
and
then
you
know
a
kubernetes
operator.
B
Could
then
listen
for
those
events
as
well,
but
the
the
design
goal
for
adam
isn't
to
support
kubernetes
it's
to
be
usable
by
some
other
tool,
so
you
can
certainly
use
it
from
a
kubernetes
operator,
but
why
item
is
predominantly
designed
to
be
stood
up
in
a
wisdom,
cloud
infrastructure
and
operated
via
wash.
A
Taylor,
you
got
a
couple
more
comments
on
the
same
kind
of
kubernetes
question.
C
Yeah,
I
was
just
saying
we
can,
I
think,
kevin
answered
most
like
the
super
technical
details
for
jamitha,
but
the
I
would
just
also
point
out
that,
like,
if
you're
using
the
the
kubernetes
applier
stuff
that
we
created
to
connect
into
like
wasn't
cloud.
So
if
you
had,
that
could
be
a
use
case
for
something
where
you
want
to
do
a
a
controller
of
some
kind.
C
So
you
want
to
like
define
something
you
could
either
have
like
a
mixed
definition
that
could
spin
up
some
things
that
are
pods,
that
are
old
things
that
still
run
in
containers
and
new
things
that
run
in
with
damn
you
could
you
could
do
some
sort
of
connection
layer
there
as
well,
but
with
the
service
supplier
you
would
you
would
make
it
so
that
anything
that
came
up
that
was
spinning
up
an
http
server
would
automatically
have
something
spun
up.
On
the
other
end,
to
connect
like
back
to
the
new
wasn't
cloud
stuff.
C
So
there
are,
there
are
tools
there
that
can
be
used
for
it,
but
definitely
angry
with
kevin.
The
orchestration
part
of
it
would
probably
want
to
be
handled
by
all
by
all
by
damn
itself,
rather
than
the,
rather
than
like
the
controller
trying
to
to
spread
things
out,
though,
there's
nothing,
stopping
a
controller
from
doing
that,
it'd
just
be
reinventing.
What
dam
is
already
doing.
B
Yeah,
that
said,
I
think,
there's
I
haven't.
I
obviously
haven't
played
with
this
yet,
but
one
thing
that
might
be
possible
is
a
kubernetes
operator
could
start
with
them
in
a
docker
image
inside
a
kubernetes
cluster,
and
then
why
item
itself
would
then
be
able
to
manage
the
wasm
cloud
resources.
E
I
guess
in
my
head,
I
have,
I
know,
kev
sorry,
taylor,
you
did
the
kubernetes
supplier
stuff
some
time
ago
and
I
think
initially
like
long
time
ago,
with
some
of
the
guys
from
red
badger,
we
came
up
with
an
operator
as
well
just
to
ship
the
oem
spec
down
through
nuts
in
and
I
haven't
actually
dipped
the
two.
E
So
I
guess
the
question
is:
what
do
we
want
to
do
or
what
we
should?
We
do
and
then
yeah
the
the
what
I'm
inside
of
kubernetes.
Yes,
I
think
that,
would
I
don't
well
actually
wouldn't
that
be
a
vanilla
deployment,
I'm
not
sure.
E
Well,
I'm
actually
trying
to
stitch
everything
together
as
well.
I
think
out
loud,
so
I
know
you
worked
on
taylor.
You
worked
on
my
kubernetes
supplier
stuff
and
then
there
was
an
another
operator
that
was
created
from
the
red
badger
people
and
myself.
E
That
was
also
gonna
ship,
the
om
spec
across
gnats
to
whatever
and
that's
how
one
of
them
actually
came
about
that
that
was
going
to
be
the
original
receiver
was
autumn
and
then
kevin
also
mentioned
actually
running
water
inside
of
kubernetes
as
well.
B
Those
are,
are,
those
are
not
mutually
exclusive
possibilities.
So
your
original
comment
about
shipping
yaml
over
nets,
that
that
is
actually
how
that's
how
adam
gets
its
control
stuff
now.
So,
if
you
look
at
again,
this
hasn't
been
merged.
Yet,
but
if
you
look
at
the
code
in
wash
for
the
app
sub
command,
you'll
see
how
it
talks
to
what
and
why
them
has
a
a
control
api
that
you
can
interact
with
directly.
A
Okay,
I
was
gonna,
let
you
go,
but
I
I
just
wanted
to
nail
one
thing
home
that
I
that
I
was
thinking
about.
I
know
that
there's
going
to
be
a
lot
of
overlap
when
we
start
thinking
about
the
way
that
kubernetes
does
declarative
deployments
and
how
autumn
is
going
to
handle
declarative
deployments
for
a
wasm
cloud
application
and
they're
handled
and
they're
going
to
be
handled
in
similar,
but
different
ways.
A
Sorry
about
that,
I
got
something,
but
one
main
reason
why
I
can't
or
hi
why
we
didn't
implement
this
as
like.
A
kubernetes
operator
is
mostly
because
we
don't
want
to
be
dependent
on
kubernetes
like
to
have
the
jump
from
hey.
I
want
to
deploy
a
declarative
application
with
wasmcloud.
To
have
to
tell
people
now
you
need
to
introduce
kubernetes
is
something
that
we
didn't
want
to
go
to.
C
C
Everything
for
wasn't
cloud
or
any
of
the
other
awesome
things
that
are
going
on
like
that
would
be
stupid
if
we
expected
that,
and
so
the
idea
behind
what
we
try,
what
we're
trying
to
do
with
the
things
like
kubernetes
supplier
and
anything
that
would
be
any
any
controller
that
someone
would
create
for
kubernetes
would
be
purposely
for
creating
what
I
like
to
what
I
personally
term
the
bridge
to
the
future.
C
Kubernetes
is
not
going
to
be
the
primary
way.
People
should
run,
wasn't
cloud
to
get
the
full
benefits.
Now
that
doesn't
like
that,
that's
not
saying
no
one
should
run
it
like.
That's
exactly
why
we
offer
a
chart,
because
people
want
to
try
it
out
now
and
they
want
to
be
able
to
connect
to
what
the
future
is.
Hence
the
bridge
to
the
future
through
the
stuff
they
already
have,
which
is
kubernetes.
C
So
we've
come
to
meet
people
where
they're
at
with
those
technologies,
but
wasm
cloud
is
never
going
to
be
a
deeply
integrated
into
kubernetes
kind
of
thing.
That's
not
where,
where
any
of
us
as
core
maintainers
now
I
could
be
wrong
if
any
core
maintainer
on
here
is
differently
minded
than
me.
Please
tell
tell
people,
but
as
far
as
I
understand,
all
the
core
maintainers
of
this
project
are
very
much
in
the
we're
not
going
to
go.
Try
to
integrate
super
deeply
with
kubernetes
and
make
this
a
kubernetes
crd,
dependent
thing.
C
C
We
don't
what
we
don't
want
to
do
and
what
would
be
very
bad
for
us
as
a
project
and
for
web
assembly
in
general
is
to
tie
our
chain
to
the
kubernetes
boat
and
no
matter
what
happens
to
the
kubernetes
boat.
It
could
keep
floating
for
40
years
or
it
could
sink
in
five
years.
We
don't
know,
but
instead
of
tying
it
to
that
we're
setting
out
to
build
a
new
future,
but
at
the
same
time,
to
over
stress
the
analogy
here,
we're
putting
out
a
plank
in
between
the
two
boats.
C
So
people
can
still
do
stuff
across
the
boats,
but
they
don't.
We
don't
want
to
completely
tie
it
in
there
and,
like
brook
said,
brooks
brought
up
a
very
good
point.
We're
trying
not
to
re-implement
kubernetes
like
kubernetes.
Does
things
very
well?
C
It
offers
a
very
good
set
of
building
blocks
that
are
very
good
for
building
platforms
with,
but
they
they
come,
there's
been
so
much
baggage
and
shark
jumping
that
is
been
added
on
to
it
that
that
sometimes
drags
things
down
with
it,
and
so
I
don't
think
we're
ever
going
to
get
to
the
place
that
that
maybe
you're
envisioning,
based
on
what
I
understand
jennifer.
But
we
want
to
make
it
as
easy
as
possible
to
connect
with
the
things
you
have.
C
People
have
invested
millions
and
billions
of
dollars
across
the
world,
getting
things
on
the
kubernetes
and
that
that
was
a
huge,
a
huge
step
for
people.
It
got
a
lot
of
people
out
of
like
running
vms
in
their
own
data
centers
to
running
things
in
the
cloud,
and
so
that's
a
very
important
evolutionary
step.
But
we
also
think
that
the
future
of
this
is
going
to
be
a
future
of
a
lot
of
these
things
is
going
to
be
web
assembly
based
and
so
sorry
for
the
long
rant.
C
That's
that's
just
a
step
too
far
and
too
limiting
for
what
we're
trying
to
do
so.
Hopefully
that
explains
a
little
bit
more
and
if
anyone
else
on
here
is
like
no.
I
do
not
agree
with
what
taylor
said.
That's
perfectly
fine,
please
say
it,
but
I
just
wanted
to
very
clearly
but
but
nicely
specify
why?
Why
we're
doing
the
things
we're
doing
and
what
we
are
trying
to
avoid.
A
So
jennifer,
I
know
you
had
some
specific
questions
about
kubernetes
and
and
what
did
that
kind
of
delineate
where
we
are
at
and
answer
your
questions?
There.
E
Yeah,
I
need
to
look
through
the
code
and
I
just
found
the
found
the
stuff
that
the
kubernetes
applied
just
now,
but
I
think
that
I'd
completely
understand
and
agree
with
what
has
been
said
so
far.
My
understanding
was
that
the
reason
that
we
came
up
with
what
is
currently
in
wasn't
cloud
for
the
title
cadets
operator
was
a
way
to
just
ship.
The
oem
spec
from
left
to
right.
E
Nothing
implemented
inside
so
whatever's
running
runs
in
wasm
cloud
and
an
otp,
but
it
was
just
a
way
to
get
the
cube,
cto
command
to
be
compliant
to
provide
a
playing
field.
If
you
like
that's
familiar
to
what
taylor
is
pointing
out
to
the
people
actually
using
kubernetes,
not
really
try
to
run
anything
anywhere
else,.
B
A
Jennifer,
do
you
have
a
link
to
that
the
wasn't
cloud
kubernetes
operator?
I
I
know
that
that
kind
of
inspired
some
of
the
stuff
here,
but
I
can't
seem
to
locate
where
it
is.
Maybe
it's
a
red
badger
work.
A
A
Yeah
looking
at
this,
it
definitely
looks
like
this
was
kind
of
an
initial
implementation
for
what
you
know
for
a
declarative
deployment
and
the
you
know
what
we're
settling
on
with
guadam
is
essentially
something
like
this,
but
not
kubernetes,
specific,
which
I
think
we've
talked
about
a
good
good
bit,
but
this
is
good
to
find
again.
A
Alrighty,
well,
I
had
one
more
thing
that
I
knew
of
that
I
wanted
to
bring
up.
A
We
talked
about
it
in
a
previous
community
call,
but
I
know
that
matt
wilkinson
here
sorry,
I
feel
like
I
need
to
sneeze
matt
started
working
on
the
the
watson
cloud.tamil
rfc
and
proposed
a
bunch
of
different
fields
that
can
be
in
there
with
the
eventual
goal
of
being
able
to
use
wash,
maybe
in
addition
to
a
make
file
like
the
way
that
we
do
things
today
with
with
make
build
or
make
push
make
start,
and
do
that,
partly
with
wash
as
well
just
to
kind
of
keep
everything
contained
in
the
same
the
same
tool
kit
and
enable
some
other
scripts.
A
F
Yeah
sure
I'm
just
kind
of
scoping
out
how
exactly
I
kind
of
thought
it
would
work.
It's
kind
of
it's
a
little
bit
messy
right
now
to
be
honest,
but
the
the
main
thing
is,
if
you
go
to
the
the
test
folder
at
the
top
of
the
repo
and
then
there's
a
wasm
file
that
thermal
file
that
I
was
basically
just
messing
around
with.
So
this
is
kind
of
what
I
was
thinking.
It
would
look
like
if
people
have
any
initial
comments
on
on
this.
F
I
also
saw
that
I
know
for
the
bottom,
the
pr
they
were
looking
at
earlier,
that
there
was
a
yaml
file
in
there.
So
I
wasn't
totally
sure.
If,
like
do,
we
have
a
preference
of
tomol
versus
yaml,
should
we
use
one
in
one
scenario
and
one
in
the
other
should
they
be
lined
up?
I
wasn't
totally
sure
on
that.
Right
now,
yeah.
F
B
C
Yeah,
I
would,
I
would
also
throw
throw
my
towel
in
there
at
fear
of
starting
a
flame
war
of
that,
like
yaml
is
being
used
just
because
that's
what
the
oam
stuff
is
written
in
and
it's
just
what
people
are
familiar
with
in
that
space
and
it's
more
of
an
application
definition
than
a
config
file.
This
is
very
much
a
config
file
and
so
tomml
is
perfect
for
config.
C
In
my
opinion,
it
is
my
personal
favorite
for
config
things,
but
I
think
what
you're
doing
with
the
tamil
is
exactly
what
we're
thinking
of
doing
anyway,
as
we
brainstorm
this
idea,
and
so
this
works
just
fine.
In
my
opinion,.
F
A
I
like
that,
you
started
this
out,
though,
with
like
a
test
module
with
the
test,
config
always
nice,
to
see
from
the
beginning.
I
did
have
one
thing
that
I
thought
I
would
mention
for
the
tommel.
I
know
that
we
talk
a
lot
as
rust
developers
and
wasn't
quite
as
rust
actors
providers.
A
You
know
kind
of
a
rust
core,
but
a
lot
of
the
languages
that
we're
going
to
add,
aren't
going
to
have
rust,
config
or
rust.
Tom
will
config
files
by
default,
like
I
don't
think
that
tommel
has
any
place
in
like
a
node
project
or
like
in
a
in
a
go
project
or
anything,
but
I
would
also
agree
you
know
no
matter
what
we're
doing
that,
especially
with
this
flat
kind
of
tommel
structure.
A
A
All
right
yeah,
thank
you,
matt
for
doing
a
little
a
little
update
and,
of
course,
thank
you
for
getting
started
on
this
and
and
poking
around
at
what
this
may
look
like.
A
F
I'll
keep
you
guys
updated
hopefully,
next
week,
I'll
have
some
more
stuff
to
show.
A
A
All
right!
Well,
if
that
is
it,
I
won't
make
everybody
sit
here
in
silence.
Thank
you,
everyone
for
for
coming
to
the
community
meeting
today,
some
some
great
discussion
and
announcements
and
looking
forward
to
seeing
you
next
week,
I'll
stop
recording
I'm
gonna
hang
out
for
a
little
bit,
though
we
can
always
chat
bye.
Everyone.