►
From YouTube: Knative community meetup #2
Description
In this event, we announce the Knative TOC election results, there are intros by the new TOC members, and updates from Autoscaling and Eventing working groups. Evan Anderson, software engineer at VMWare, runs a demo titled "Automating service delivery with bindings"
A
Welcome
everybody
to
the
community
needs
up.
My
name
is
Maria
Cruz
I'm,
a
program
manager
in
the
Google
open-source
program
office,
and
today
we
are
going
over
a
few
topics.
I
linked
the
agenda
on
the
chat,
if
you're
just
coming
in,
and
you
cannot
see
it,
other
people
can
link
to
it
again
and
I
think
we're
gonna
go
ahead
and
get
started.
I
Thomas
is
the
first
presenter
with
an
update
from
the
student
committee.
So
Thomas
floor
is
yours.
A
B
Thank
you.
Thank
you.
Okay,
welcome
everyone
and
thank
you
for
joining
our
community
meeting
and
Thank
You
Maria
for
organizing
this.
Of
course,
I'm
excited
to
see
all
of
the
content.
We're
gonna
talk
about
today
and,
of
course,
extra
excited
to
talk
about
the
toc
election
and
in
this
election
we're
gonna
in
this
election.
We
have
the
about
it
for
three
of
the
five
toc
seats
and
the
two
remaining
seats
are
part
of
the
bootstrapped
committee
and
they
will
be
voted
for
next
year.
B
Our
most
active
community
and
community
members
are
eligible
to
vote,
so
we
had
117
people,
our
job
eligible
to
vote
and
83
of
them
voted
was
great.
Thank
you
all
the
builders
for
voting
and
to
make
sure
that
we
get
a
great
TOC
and
the
new
TOC
is
drumroll
Nia
Marcus
and
grant
our
new
TOC
members
I'm
super
thrilled
to
see
these
three
getting
elected.
C
Everyone
I'm
here
I'm,
very
honored,
to
receive
the
support
in
the
election.
I
have
been
involved
with
Canada
in
the
very
early
days
and
in
the
last
two
years
I
have
been
leading
the
networking
work
group
my
hope
were
in
joining
a
Tac
toc
is
that
I
can
help
increase
collaboration
in
the
project
as
well
as
help
improve
cognitive
user
experience.
Hopefully
that
would
lead
to
even
wider
reduction
and
early
success
that
we
have
now.
B
C
D
Alright
thanks
everybody
for
the
support.
I
am
truly
humbled
to
be
to
be
like
cual
accord,
winning
one
of
the
election
seeds
in
a
community
vote.
My
name
is
Marcus
I'm
based
out
of
Germany
I
might
be
the
only
member
of
the
new
TC
who
is
not
living
in
Seattle.
So
that's
that's
interesting.
I
know
my
grant
lives,
but
the
others
do
I.
Think
I've
been
working
a
full-time
or
creative.
Since
back
then
it
was
non
public
and
still
called
Ella
for
us
enough.
D
You
guys
remember
that
before
that
I
already
worked
on
function
as
a
service
in
the
Apache,
open,
wisk
project
and
outside
of
coding,
I'm,
a
guitarist,
a
medical
band,
a
singer
and
a
choir
and
the
voluntary
firefighter
when
I
wrote
that
down.
I
found
it
interesting
because
it's
kind
of
broad
I
always
was
very
dear
to
my
heart.
So,
first
and
foremost,
I
want
to
ensure,
as
me,
a
that
the
Canadian
community
stays
the
well-oiled
machine.
E
Let's
see
I've
I
work
at
Google
right
now
in
Seattle,
but
before
that
I
worked
at
github,
mostly
I've
searched.
So
you
can
blame
me
for
all
the
times
that
code
search
fails
you,
but
anyway,
the
reason
I
mentioned
github
is
because
one
of
my
projects
there
was
Bill
processing
platform
to
run
on
kubernetes
and
at
the
time
we
had
to
build
a
lot
of
stuff
ourselves:
publisher,
library's,
an
event
envelope
format
that
was
surprisingly
hard
schema
registry
auto-scaling.
E
E
Think
that
experience
of
needing
this
set
of
tools
that
we're
building
gives
me
some
insight
into
how
those
tools
could
best
serve
the
needs
of
our
users
and
I
hope
to
use
that
to
build
the
right
tools
for
them
like
Nia
and
Marcus
I'm,
also
pretty
passionate
about
keeping
the
community
healthy,
I
think
without
the
healthy
community,
all
the
code
that
we
wrote.
Doesn't
you
know
that
much
so
thanks
everyone
for
trusting
me
with
the
oversight
of
this
project?
It's
it's
really
an
honor
and
I'm
humbled
and
excited
to
get
started.
B
A
D
Forgot
to
mention
earlier
in
it
I'm
also
leaving
your
skating
working
group,
so
there
we
go
now
we
have
that
covered
as
well
yeah
regarding
auto-scaling
I
just
wanted
to
give
a
quick
heads-up
that
we
improved
already
a
lot
of
our
dogs
and
are
still
in
the
process
of
more
information
and
like
more
dogs,
mud
works
always
helps,
and
I
would
really
love
to
get
feedback
from
actual
users
on
if
they.
If
these
dogs
cover
what
you
need
or
if
you
need
more
and
if
you
need
more,
please
tell
us
what
what
that
is.
D
We
also
did
best
improvements
in
the
way
our
load
balancing
works.
That's
currently
on
unreleased.
It
will
all
be
in
our
15,
so
looking
forward
to
releasing
that
and
seeing
how
it
helps
you
especially
help
on
running
low
container
concurrency
values.
And,
last
but
not
least,
we
are
currently
preparing
a
questionnaire
for
you
for
you
users.
Basically,
we
cannot
get
finished
with
that,
but
see
this
as
a
general
culture
action.
D
We
have
a
lot
of
discussions
in
the
auto-scaling
working
group
and
we
desperately
need
more
user
data
and
need
to
know
how
users
are
using
things.
What
you
need.
What
do
you
find
heart?
Which
knobs
do
you
find
yourself
tuning
and
where
do
you
find
yourself
relying
on
defaults,
and
you
are
actually
pretty
happy
with
that?
D
So,
while
we
don't
have
the
questionnaire
out,
please
feel
free
to
reach
out
to
me
directly
if
you
need
to,
if
you
can't
put
stuff
publicly
open,
give
give
up
issues
if
you
do
have
issues
or
open
thread
on
kanae
diffusers,
and
please
tell
us
how
many
using
stuff?
What
are
your
pain
points,
so
we
can
make
like
inform
our
decisions
better
in
terms
of
twitching,
with
all
the
default
values
that
we
have
and
exposing
more
values
stuff
like
that,
Thanks.
F
F
This
alone,
we,
as
eventing
group
yesterday
I,
decided
to
give
this
visibility
in
a
community
meeting
for,
like
all
the
users
and
not
just
those
that
regularly
attend
working
group
meeting.
So
there
is
a
good
omission
and
are
linked
in
the
document,
which
has
some
action
items
and
the
first
poor
request.
I
guess
where
you
can
all
I
guess
party
on
and
you
feedback
in
comments
and
whatnot,
and
the
summary
is
this
makes
easier.
A
G
G
So
it's
just
a
little
go
application
and
you
can
load
it
and
define
a
word
so
banana
and
it
will
go
to
there's
a
couple
different
sources
it'll
pull
from,
but
it
prefers
the
oxford
english
dictionary.
So
here's
some
definitions
for
banana,
which
is
all
well
and
good,
and
you
know
if
I
decide.
You
know.
Oh
maybe
I
should
say
style.
G
Yeah,
okay,
so
I,
don't
remember
how
to
do
inline
styles.
This
is
not
about
how
I
know
or
don't
know
how
to
do
HTML,
because
clearly
I
don't.
But
so
you
know
my
local
development
loop
is
pretty
quick.
You
know
just
kill
it
and
restart
it,
but
then,
if
I
want
to
go
and
actually
run
this
on
K
native,
you
know
I
don't
know.
Can
people
read
that
does
it
need
to
be
a
little
bigger.
A
G
G
And
you
know
you've
all
seen
this
and
it
takes
some
time.
You
know
I
happen
to
be
using
go,
but
you
know:
there's
lots
of
different
languages
and
almost
all
of
our
stuff,
unless
you're
using
Co
kind
of
looks
like
this,
and
what's
even
better,
is
now.
If
I
want
to
push
this
I
realize.
Oh
wait.
I
forgot
to
tag
it
so.
G
G
G
But
but
you
know,
that's
that's
sort
of
your
typical
workflow,
but
wouldn't
it
be
great
if
your
workflow
could
look
a
little
bit
more
server-side,
driven
and
so
I'm
going
to
show
you
a
couple
of
tools
that
were
written
by
a
variety
of
folks
from
VMware
when
they
were
under
the
pivotal
umbrella.
So
some
of
these
come
from
project
RIF
and
some
of
these
come
from
Capek.
G
G
When
I
create
this
image
Hamel
it
will,
let's
see,
is
it
done?
It's
done.
I'm
also
gonna
show
off
octant
for
those
of
you
who
haven't
seen
it
it's
kind
of
a
nice
UI
on
these
things,
so
I
just
created
an
image
and
right
now
it's
not
ready
yet,
but
it
will
create
a
build
each
time
that
things
change
and
you
can
see
that
the
build
is
currently
progressing.
G
We'll
leave
that
back
there
doing
its
thing
and
we'll
look
at
what's
actually
in
an
image,
so
an
image
defines
a
source
I've
just
pointed
it
at
github
and
master
branch
and
a
builder
which
gives
you
a
set
of
build
packs.
This
will
actually
build
a
lot
of
different
languages.
This
is
this
default.
Kpac,
1
and.
G
G
Yes,
do
all
the
saves
push
this
up
and
in
a
minute
or
so
we'll
see
another
build
kick
off.
Another
way
you
can
watch
that
is
with
Cube
control
at
build.
W
is
just
a
watch
on
builds,
so
you
can
see
right
now.
We
have
the
one
build
that
was
created
at
the
beginning
of
time,
but
we'll
pretty
soon
and
see
another
build
kick
off
as
the
image
notices
that
there's
been
a
commit,
and
these
are
various
stages
of
the
build
making
progress,
and
so
it
keeps
updating
the
status.
G
This
is
the
one
we
want.
So
if
we
look
at
build
define
here,
the
llamó
status
has
this
field
latest
image
and
if
you
all
are
familiar
with
duck
typing,
you
may
know
where
this
is
headed.
Anything
that
has
a
latest
image
you
can
see,
our
build
is
finished
and
the
latest
image
has
been
updated
to
build
to
our
friends
in
project.
Rif
have
created
a
created,
duck
type
controller.
G
G
H
G
So
yeah
this
is
some
of
this
is
early
prototype
code.
Some
of
this
is
semi
production
code.
None
of
it
has
hooked
up
with
eventing,
so
there's
no
there's
no
registration
of
a
web
hook
or
anything
like
that
to
kick
the
build
process.
It's
just
doing
a
poll
on
github,
but
github
can
deal
with
some
polling
so
and
here
we
go,
it's
kicked
off
and,
let's
see,
while
we're
waiting.
Let's
take
a
look
at
that
service.
I
G
G
Since
we
have
two
image
bindings,
we
can
apply
the
same
thing
that
we
built
to
both
of
them,
which
is
less
interesting.
If
it's
in
a
web
application
like
this,
but
if
it's
a
sidecar
you
could
potentially
push
a
whole
bunch
of
different
side
cars.
At
the
same
time,
let's
see
we
just
built
something
that
is
in
E.
Oh
look,
it's
already
updated
on
the
deployment.
Let's
go
look
at
this
surface
and,
of
course,
I'm
doing
a
live
demo,
so
the
service
didn't
get
updated
here.
G
G
G
E
G
G
G
Image
bindings
come
from
this
project
RIF
bindings,
and
they
have
some
nice
documentation
down
here.
That
shows
you
what
to
do
with
them
and
all
the
different
values
you
need
to
put
in,
but
yeah
the
exciting
thing
about
image
binding
is
that
it
should
work
not
just
with
kpac
but
with
anything
else
that
exposes
a
spec
test
image.
G
So,
theoretically,
you
could
query
a
docker
registry
and
find
you
know
the
last
version
of
a
given
tag
if
you
wanted
and
have
that
auto
bump,
using
image
binding
to
resolve
it
down
to
a
specific
reference
or
you
could
say
hey,
this
is
my
external
store
of
passed.
End-To-End
tests
or
you
know,
passed
QA
runs
once
something
passes:
QA
then
it
can
actually
get
rolled
out
to
the
next
stage
of
production.
A
Awesome,
thank
you
so
much
Evan
for
the
demo.
Now
we
have
allotted
some
time
to
discuss
this.
Ideally
we
would
be
doing
this
on
individual
rooms,
but
we
were
not
able
to
enable
that
for
this
meeting.
So
we
can
open
the
floor
to
discuss
now
or
you
know,
share
any
comments
or
ideas.
This
may
have
inspiring
you
or
questions.
A
I
I
G
Connected
the
github
event
source
and
use
that
to
poke
the
image
that
would
cause
the
reconciler
to
kick
off
and
decide
to,
you
know,
go
and
check
and
see
if
there's
anything
there
and
oh
look,
there
is
which
would
let
you
reduce
the
polling
interval.
It
would
look
like
webhook
to
something
running
on
the
cluster.
You
know
to
the
source,
which
would
poke
the
build
controller
and
then
would
kick
off.
I
G
They
have
these
source
types
and
so
a
source
can
be
a
get
or
a
blob
or
you
can
actually
pull
from
a
registry
and
they
all
you
can
take
a
sub
path.
So
you
can
say
not
this
whole
git
repo,
but
like
some
sub
path
of
the
repo
or
you
know
not
this
whole
tar
ball,
but
like
this
sub
path
build
from
there,
so
you
can
see,
gif
has
URL
and
revision
blog
is
just
a
URL
and
the
registry.
G
You
know,
obviously,
you
need
to
get
into
the
K
pack
source
to
extend
this
further,
but
it
would
be
doable
if
you
move
to
something
like
Tecton.
The
fetch
the
source
is
actually
a
separate
piece,
and
so
you
that's
probably
more
easily
pluggable.
The
listen
for
changes
is
a
little
bit
harder
with
Tecton,
which
is
why
I
chose
K
pack
right
now.
G
K
pack
is
is
very
focused
on
basically
building
a
single
docker
image
from
a
single
repo.
Tecton
is
basically
a
full-featured
workflow
system.
So,
if
you
want
to,
you
know,
use
multiple
repos
or
you
want
to
deliver
multiple
artifacts
to
different
places,
or
you
want
to
do
something
more
than
just
build
your
software.
You
know
if
you
have
a
more
involved
testing
process.
G
For
example,
you'll
find
that
k
pack
will
run
out
of
steam
fairly
quickly,
but
works
really
well
for
the
simple
case
of
I
have
some
code
and
I
just
want
to
turn
it
into
a
docker
image,
whereas
Tecton,
because
it's
got
so
many
more
capabilities.
You're
greeted
with
you
know,
okay
figure
out
what
you
want
to
do
and
how
to
describe
that
and
a
bunch
of
yeah
Mille
documents,
whereas
you
know
there
were
like
three
or
four
things:
I
had
to
like
intentionally
write
for
the
K
pack
configuration,
but
it's
pretty
minimal.
G
G
K
G
G
So
one
neat
thing
about
octant
is
that
you
can
actually
go
in
and
look
at
a
pod
and
if
it
knows
what's
going
on,
you
can
start
a
port
forward
from
the
UI
which
is
kind
of
slick,
and
you
can
see
all
the
events
and
stuff
that
we're
related
to
it.
So
I've
been
trying
to
train
myself
to
actually
use
the
pretty
UI
is,
rather
than
just
do
everything
from
the
command
line
and
then
curse
when
it
doesn't
work
well,
so
you
can
see
now.
G
J
J
M
G
K
G
A
G
G
And
I
happen
to
show
off
a
bunch
of
stuff
from
VMware
I
think
it's
cool
and
it
happens
to
be
stuff
done
by
my
employer.
It's
totally
fine
just
show
off
stuff
that
you've
worked
on
for
work.
It's
also
fine
to
show
off
cool
stuff
that
you
did
cuz.
It
was
fun.
I
showed
off
cool
stuff
that
someone
else
did
because
it
was
fun.
A
A
Ok,
class
1
2
once
a
month
great
we're
thinking
of
doing
it
on
the
second
Thursday.
Well
now,
maybe
Friday,
so
that
it
doesn't
coincide
with
other
CN
CF
events
that
maybe
we
share
a
similar
audience
group
with
so
it
might
be.
We
might
be
moving
this
to
Friday
morning
for
the
second
Friday
of
every
month.
If
that
works,
cool,
so
I.
Think
with
that,
please
give
us
feedback
on
the
survey.