►
From YouTube: KEDA Standup - 2021-02-16
Description
A
I
got
a
few
messages
last
night
from
folks
who
were
unable
to
join
zibianek,
one
of
our
best
maintainers
just
had
a
child
a
baby
last
week
or
the
week
before,
and
then
tom
is
on
baby
due
to
himself.
So
it
seems
to
be
family
matters
today
and
a
similar
story
for
some
soaks
at
microsoft.
So
we
might
have
a
little
bit
of
a
smaller
meeting,
but
we'll
run
with
it
anyway.
A
A
A
I
may
bring
up
a
topic
yeah,
there's
time
yep,
I'm
sure
we
all
have
the
time
today
perfect
and
then
shuba
same
same
any
topics.
You
want
to
cover
no,
no,
no
right
great
and
then
ritika.
I
see
you
just
joined
as
well.
Thanks
for
joining,
I
mentioned
it
might
be
a
little
bit
of
a
smaller
shorter
stand
up
today.
We've
got
a
bunch
of
folks
who
are
unable
to
join,
but
we'll
run
with
what
we
can
anything
you
want
to
cover
eridica.
A
Any
topics
you
want
to
cover
ritika
that
I
should
add
to
the
agenda,
just
just
listen
and
then.
A
You're
unmuted,
but
I
don't
hear
any
speaking
so
I'm
going
to
assume
you
are
good
and
if
not
that's
fine,
let
us
know
on
chat
or
something.
Okay,
great
so
I'll
run
through
the
agenda
items
that
tom
had
for
us
and
then
jonathan
we
can
go
where
it
is.
There
is
a
reference
case
that
we're
publishing,
which
is
how
alibaba
is
using
keda.
I
just
read
through
it
on
over
the
weekend
and
made
some
edits.
I
think
tom's
just
finalizing
it
and
it
looks
like
we're.
A
Gonna
have
the
cncf
publish
it,
which
is
gold,
probably
has
much
more
visibility
than
just
the
cada
site
itself.
So
this
has
been
a
good
one
from
from
tom
and
so
excited
to
see
this
one
go
out
the
door.
The
the
use
case
is
pretty
cool.
It
just
kind
of
highlights.
Like
hey,
we
had
cluster
scaling,
we
need
application,
scaling
and
alibaba's
baked
in
cada
to
some
of
their
application
platform
stuff,
which
is
pretty
sweet.
A
Oh
interesting,
so
I
didn't
know
about
this.
It
looks
like
we
have
an
annual
review
with
the
cncf.
This
is
something
I
didn't
know
about,
but
makes
sense
that
it
looks
like
tom
has
already
started
running
with
which
I
assume
is
just
like.
What's
the
state
of
the
project,
what's
the
state
of
the
thing,
and
so
it
looks
like
we're
working
on
that
and
then
shortly
after
we'll
be
spending
some
time
on
incubation,
so
those
both
sound
awesome,
especially
the
incubation,
I
think
for
folks.
A
In
an
earlier
meeting,
we
looked
through
like
the
criteria
and
it's
like
hey.
Do
you
have
you
know
activity
on
the
repo?
Do
you
have
some
people
using
it
in
production?
Is
it
documented
and
all
the
things?
So
I
think
we
hit
the
bar
for
incubation,
but
we'll
see
where
it
goes,
but
it
sounds
like
we
have
an
annual
review
first
that
we
can
kind
of
vet
vet.
A
Azure
service
operator
I'm
curious
on
what
this
is,
what
they
can
use
with
cada,
I'm
just
reading
this
now
for
the
first
time,
and
I'm
not
quite
sure
if
this
is
like
hey
if
you're
using
azure,
then
here's
all
the
azure
things
that
you
can
use
crossplane,
I'm
guessing
crossplane
is
some
other
project
that
he's
saying
they're
doing
this,
and
maybe
we
should
too
yeah
without
tom.
A
Here
I
don't
know
how
much
I
don't
know
if
anyone
on
the
call
is
reading
this
issue
and
you're
having
a
better
sense
for
what
we're
getting
for
what
the
tools
are,
that
we
integrate
with
and
how
what
they
can
use
with
cada
yeah.
A
So
I
think
he's
thinking
that
there
would
almost
be
like
a
page
for
azure,
a
page
for
aws,
a
page
for
gcp,
a
page
for
alibaba
on
our
docs
and
it
would
kind
of
say,
like
hey:
are
you
in
azure
land
and
you
want
to
use
cada,
here's
the
integrations
that
might
be
best
for
you?
I
think
that's
what
he's
thinking.
A
Maybe
I'm
not
sure
anyway,
I
don't
know,
I
don't
know
if
there's
much
we'll
be
able
to
say
without
tom
chiming
in
here,
because
I
I
don't
know
how
much
it
has
to
do
with
like
this
actual
cross
plane
feature.
A
Okay,
all
right.
Well,
that's
it!
So
that's
it
for
the
agenda.
It
looks
like
oh
sweet
and
I
think
jonathan.
I
assume
you
just
popped
this
in
this
thread.
Oh
I'm
gonna
have
to
open
this
up
in
my
slack
tab,
yeah.
A
B
Yeah-
and
this
is
sort
of
the
beginnings
of
what
we
hope
to
share
in
our
own
explorations
of
using
cada
it's
from
a
thread
from
a
while
back
when
I
first
started
poking
at
it,
but
until
they
are
what
we
do,
we're
building
an
iot
platform
and
part
of
it
will
have
a
serverless
offering,
and
so
the
goal
is
to
have
serverless
compute
in
a
native
iot
protocol,
actually
multiple
iot
protocols,
and
so
what
we're
trying
to
figure
out
is
how
might
we
use
cada
to
be
the
auto
scaler
for
these?
B
This
basically
custom
serverless
runtime
and
I
posted
some
thoughts
of
potential
architectures.
We
we're
exploring
we're
just
at
the
cusp
of
actually
starting
to
to
to
write
some
code,
but
I
wanted
to
whenever
there's
a
lull
in
the
conversation
or
an
opening
in
the
time
slot
just
kind
of
share
get
some
early
feedback,
so
we
can
go
and
actually
try
it
out
and
return
back
with
what
we
found,
but
the
the
the
thread
which
I
I
I
you
know.
B
If
you
can't
pull
it
up,
I
could
certainly
screen
share
or
something
is
taking
what
we
have
as
well.
Actually,
if
you
can
get,
if
you
get
a
diagram
going,
then
that'd
be
easiest.
A
A
Open
in
this
one-
and
I
can
I
can
so
I
assume
it's
in
the
cada-
the
keta
channel,
yeah
yeah.
B
A
B
It's
all
good,
so
a
little
back
story
on
our
journey.
So
far
we've
been
trying
a
bunch
of
different
approaches
to
serverless
prior
to
you
know,
kato
1.0
and
nothing,
nothing
in
production.
That
should
be
very
clear
here
and
we
built
our
most
recent
prototype
late
last
year
on
k
native
and
ran
into
issues
around
protocols,
and
so
with
the
introduction
of
2.0-
and
you
know
external
scalars.
That
means
we
can
really
easily
prototype
our
idea
of
a
protocol.
B
You
know
an
external
protocol
based
scalar,
just
which
is
pretty
awesome,
and
so
the
the
the
two
diagrams
I
threw
into
the
the
k
to
slack
are
two
potential:
parallel
architectures
one
using
ingress
v2,
which
is
now,
I
think,
the
gateway
api
from
the
network.
B
Sig
as
the
interf
is
the
main
service
that
routes
requests
to
cada
and
then
does
the
auto
scale
with
our
own
proprietary
or
custom
external
scaler
and
the
secondary
is
using
smi
and
custom
traffic
routes
to
do
the
east-west,
auto
scaling
so
for
a
full,
and
then
you
know,
north
south
east
west
type
of
serverless
platform.
Were
you
able
to
get
the
the
diagram?
I.
A
B
Great,
I
see
it
now,
thank
you
yeah,
and
this
is
a
larger
version
of
what's
in
the
slack
channel,
but
a
little
bit
of
that
context
I
just
gave,
and
so
the
idea
would
be.
We
have
these
protocol
gateways
and
we're
building
on
top
of
the
gateway
api,
and
we
have
you
know
the
custom
functions
written
by
our
developers,
our
users
and
we're
trying
to
design
how
we
should
be
leveraging
cada
and
the
external
scaler.
B
B
Going
to
our
our
gateway,
which
doing
stuff
like
authorization,
protocol,
validation
and
and
to
be
to
be
clear
like
today,
this
is
going
straight
to
a
a
container,
so
this
would
be
replacing
that
architecture.
B
But
by
using
you
know
this,
this
sort
of
gateway
we
can,
we
can
create
a
route
and
we
can
rock
to
a
service
which
then,
ultimately
is
the
is
the
user
code,
and
then
kata
can
sit
anywhere
and
so
part
of
my
interest
in
the
http
work
is
where
we
could
probably
leverage
a
lot
of
that
architecture
and
learnings
to
implement
implement
this.
B
So
it
was
not
a
direct
question,
of
course,
there's
a
specific
one.
How?
How
might
we
do
it
and
how
might
we
best
use
the
the
new
scalar
external
scalar
architecture?
We
think
we
know
and
similarly
there's
a
question
out
to
a
discussion
with
the
gateway
folks?
How
might.
A
B
Design,
our
our
gateway
or
our
gateway
v2
integration,
but
this
is
the
general
use
case,
just
curious
about
thoughts
or
ideas
or
questions.
A
This
this
is
really
good
and
I
think
the
the
point
you
brought
up,
which
I
would
just
tackle
is
like.
I
think
that,
there's
enough
prior
art,
or
even
like,
not
necessarily
prior
but
like
in
progress
exploration
on
this
type
of
stuff,
to
your
point
around
like
http.
A
Even
I
know
some
folks
on
on
our
side
at
microsoft,
have
been
prototyping
some
stuff
along
with
the
the
stuff.
That's
in
the
kdhdp
thing,
it's
doing
a
similar
pattern,
which
I
would
you
know
naively
just
assume
like
okay.
Well,
what?
If
you
just
swap
out
the
things
that
are
doing
http
with
your
like
custom
gateway?
I
know
it's
heavily
reliant
on
things
like
envoy
proxies
or
on
envoy
gateways
for
some
of
the
stuff
that
I've
seen
most
recently.
A
I
don't
know
if
envoy
supports
arbitrary
protocols
or,
if
that's
a
technology
that
you've
been
digging
into
too
yeah,
but
at
the
very
least
yeah.
I
think
I
I
I'm
gonna
share
this
portion
of
the
recording
with
the
folks
on
our
team
ahmed.
I
don't
think
ahmed's
on
the
call
today,
because
I'm
curious
if
ahmed
has
any
thoughts
or
even
if
he
can
just
chime
in
on
on
slack
or
somewhere
else,
because
ahmed's
the
one
on
our
side
who's
been
doing
some
of
this
exploration
of
like
okay.
A
A
Actually,
like
pokes
cada
to
scale,
but
then
it
also
dives
into
the
other
aspects
too.
So
I
I
think
the
architecture
makes
sense
to
your
point,
like
the
the
the
kind
of
question
mark
things,
or
maybe
things
that
we
might
be
able
to
help
fill
in
just
based
on
other
work.
That's
happening
in
the
community,
but
the
problem
sounds
like
a
good
one
to
solve
and
it
seems
like
cata
would
be
a
natural
fit
here
to
do
the
scaling
of
the
the
function,
depending
on
how
many
iot
events
are
coming
in.
B
Yeah,
exactly
and
and
for
us
it's
about
the
flexibility
of
this
gateway
right.
We
want
to
have
we're
implementing
idiomatic
implementations
of
these
protocols,
so
we
kind
of
can't
leverage
off
the
shelf
anything
but
the
nice
part
of
the
design
with
keita.
Why
isn't
centered?
That's
annoying
my
little
monkish
adv
there.
B
New
protocols
via
new
gateways
and
just
have
a
common
api
for
via
cada,
which
is
which
is
super
cool
yeah
and
you
know
part
of
part
of
our
exploration
with
canada.
There's
a
lot
of
benefits
to
k-native
and
it
covers
a
lot
of
this
area.
But
it
makes
it
really
hard
to
pull
out
the
the
networking
aspect
of
cable.
B
And
and
similarly,
some
of
this
routing
logic,
this
is
just
as
another
data
point.
If
we
can
leverage
the
gateway
api
is
a
common
way
to
do
ingress.
Well
then,
with
smi
they
have
this
concept
of
routes,
traffic
routes,
yeah
and
innately.
They
have
http
and
tcp
and
udp,
and
so
we
can
then
again
leverage
a
standard
api
via
smi
to
do
east-west
scaling.
So
our
custom,
instead
of
gateway,
is
our
custom
routing
a
traffic
route
implementation
can
also
trigger
east-west
auto
scaling,
which
is
which
is
pretty
nice.
B
So,
for
example,
one
service
can
call
another
service,
for
you
know
batch
batch
work
or
cron-like
chrome-like
things.
So
the
vision
there
is
to
combine
both
the
gateway
api
implementation,
as
well
as
as
an
smi
implementation,
so
that
we
can
truly
get
a
nice
iot
based
service,
offering.
A
Wow,
that's
slick
yeah.
It
makes
a
ton
of
sense
and
I
and
I
see,
similarities
in
terms
of
the
patterns
here.
So
I
think
it's
something
that
I
don't.
I
think
you're
headed
down
a
good
path,
hopefully
we're
just
able
to
accelerate
some
of
those
questions
too.
So
yeah,
I'm
glad
you
actually
had
this.
On
the
cuff.
A
This
was
a
a
good
way
to
kind
of
fill
in
some
time
here
where
we
did
have
some
space
in
the
agenda
and
I'm
glad
we're
recording
this
as
well,
because
I
will
I
will
share
this
with
some
folks
and
say:
like
hey:
is
there
are
there
any
patterns
samples?
Can
we
even
share
some
of
these,
like
prototypes
out
with
your
team,
so
that
you
could
take
a
look
and
back?
Oh
okay?
A
This
is
how
they're
kind
of
talking
to
caden,
where
it
pops
into
where
it
doesn't
to
to
serve
some
of
these
same
things.
I
don't
know
if
we've
actually
done
the
work
with
smi,
but
that
vision
makes
a
ton
of
sense
and
I
would
love
to
figure
out
if
there's
gaps
or
even
things
that
we
can
do
in
the
catacore
project
itself.
That
would
make
that
integration,
pretty
slick,
yeah.
B
Yeah
and
to
be
to
be
fair,
we're
kind
of
going
down
recently
chartered
territory
with
the
gateway
api
and
the
smi
traffic
specs.
However,
we've
been
engaging
with
with
both
groups
and
they've,
been
super
receptive
and
helpful,
and
it's
sort
of
this
potential
triumvirate
of
three.
You
know
two
standards
and
working
complications
and
nikita
project
could
be
useful
for
a
lot
of
other
folks
too.
So
we're
excited
to
see
how
we
can
tie
that
all
together.
A
Great
great
yeah
keep
keep
us
in
the
loop
I'll
I'll,
follow
up
on
some
of
these
things
and
then
I'll
I'll,
probably
just
pop
back
on,
and
you
mentioned
some
of
this
was
in
slack.
Is
it
in
the
cada?
Is
there
a
thread
then
in
the
k21?
Do
you
even
know
what
the
date
would
be
for
that
yeah.
B
Let
me
let
me
stop
sharing,
because
the
I
think.
Well,
if
I
copy
and
paste
it
correctly,
it's
december
third
december.
A
Yeah
I
got
it,
I
got
it
there,
it
is
okay,
sweet!
I
just
want
to
have
it,
so
I
can
oh
add
to
saved
items
even
better
so
that
after
I
share
it,
that
we
can
add
some
more
feedback
here
cool.
That's
perfect,
great
awesome!
Thank
you
for
sharing
that.
Okay,
so
that
wraps
up
our
regularly
scheduled
agenda.
Does
anyone
else
have
any
topics
they
want
to
flag
or
questions
you
have
before
we
have
a
bit
more
of
an
abbreviated
stand
up
today.
A
A
Yeah,
it
looks
like
some
feature:
requests
looking
at
pull
requests.
It's
oh
yeah,
there's
some
just
an
update
on
the
the
side
more
just
as
an
fyi
there's
a
microsoft,
sql
scaler,
that's
being
merged
in
right
now.
That
was
actually
worked
on
by
some
folks
at
microsoft
and
then
just
adding
authentication
to
a
few
other
scalars
and
some
tests,
which
I
love
to
see
wow
end-to-end
tests.
Whoever
did
that
they're
not
on
the
call,
but
pedro
pedro
is
a
hero,
good
job
pedro,
adding
some
indentations.
Okay
great!
A
Well,
thanks
so
much
everyone
for
joining,
as
I
mentioned,
between
the
birth
of
children
for
some
of
our
maintainers
and
then
the
babysitting
of
children
for
the
other
maintainers
a
little
bit
smaller
of
a
chat
today,
but
still
super
useful
thanks
again
jonathan.
We
will
chat
back
again
in
two
weeks
and
and
start
preparing
for,
like
our
annual
checkpoint
with
the
cncf
and
so
forth.
So
have
a
great
rest
of
your
day.
Everyone.