►
From YouTube: 2021-03-02 - KEDA Standup
Description
B
D
B
Could
hear
it
glad
to
hear
it
all
right?
Well,
we
can
jump
right
into
it.
Then,
as
I
mentioned,
I'm
going
to
have
to
pop
up
here
in
just
a
second,
yes,
great,
good,
first
agenda
item,
which
is
congrats
zibinek
on
the
baby.
I
love
it.
Yeah
everyone
was
thrilled
about
that.
I'm
gonna
go
through.
Let
me
paste
the
meeting
notes
into
the
chat
as
well
for
folks
right
here.
B
Thank
you,
tom
he's
going
ahead
and
going-
and
I
realized
I
probably
need
to
come
in
here
too,
and
remove
a
bunch
of
our
old
notes
into
the
archive
so
that
we
don't
see
this
starting
to
lag
up
again
because
last
time,
when
we
had
like
a
year's
worth
of
agenda
notes,
it
went
really
far
so
I'll
start
really
quickly
with
an
update
and
then
we'll.
If
we
can
just
go
around
the
room
and
do
a
quick
intro
and
then
share
any
items
that
folks
want
to
cover.
B
I've
got
to
go,
help
get
some
kids
off
to
school
and
then
I'll,
hopefully
be
back
here
in
a
few
minutes
if
the
meeting's
still
running
so
I'm
jeff.
Thank
you
for
adding
my
name
already.
I
work
at
microsoft
in
terms
of
updates,
there's
a
few
things
all
updates,
oh
wow,
so
this
is
one
I'll
just
weigh
in
right
now,
yeah,
I
think,
moving
to
the
github
container
registry,
I'm
all
for
it.
I
actually
been
using
the
github
container
registry.
B
More
recently
for
some
of
my
new
stuff,
I
think
that's
a
great
idea,
the
updates.
From
my
side,
I
spent
a
little
bit
of
time,
there's
two
more
customers
who
are
in
azure
who
are
kind
of
enterprises
who
are
looking
about
using
cada
that
I've
been
helping
with
one
of
the
results
of
that
is
that
there's
a
few
folks
who
want
to
use
cata
with
cosmos
db.
B
B
The
other
I
shared.
I
don't
know
if
jonathan's
on
the
call,
I
don't
think
so.
I
shared
the
recording
from
last
week's
recording
with
a
few
folks
as
well
to
look
over.
It
looks
like
there's
a
pretty
common
pattern
between
wanting
like
http
scale
stuff.
I
know
we
have
the
http
k2scaler
that
I
I
think
the
last
email
I
saw
was
that
we
were
just
about
to
publish
that
blog
post,
but
anyway,
that's
it
for
me,
so
so
a
little
bit
of
working
with
cosmos
db,
a
few
working
with
customers.
B
But
with
that,
I'm
gonna
stop
sharing
I'm
going
to
jump
off
and
then
folks
can
keep
going
around
the
room
so
maybe
to
keep
the
ball
rolling
tom
I'll
hand
the
ball
off
to
you,
and
you
can
do
a
quick
intro
and
either
give
your
updates
or
we
can
just
go
around
the
room
and
then
just
go
straight
to
the
agenda
yeah.
So
my
name
is
tom.
E
E
C
A
A
If
you
are
interested
basically
every
year,
we
need
to
mention
what
we
did,
how
it,
how
it
compares
to
the
roadmap
that
we
committed
to
and
where
we
are
going
so
yeah,
that's
all
open
there
and
then,
as
a
follow-up.
We
finally
started
looking
at
our
incubation
proposal,
so
first
we
need
a
sponsor.
So
I
am
checking
now
with
liz
rice,
who
was
one
of
our
original
sponsors
for
going
to
sandbox.
A
For
the
annual
review,
they
just
need
to
go
through
it,
but
I
don't
see
much
issues
there
and
then
for
the
incubation
proposal.
Once
we
have
a
sponsor,
there's
the
whole
due
diligence
process,
but
that's
basically
it
so.
Hopefully
we
can
also
reuse
a
lot
from
the
annual
review
in
terms
of
the
content
to
open
the
incubation
proposal.
Okay,
but
most
probably
we
would
like
we
would
need
to
present
to
the
doc.
A
A
A
A
F
A
Then
the
proposal
to
move
our
docker
images
to
github
container
registry,
so
we
already
have
jeff
and
jebenek.
Agreeing
I
see
ahmed
is
here
as
well.
Do
you
have
any
concerns
on
moving
them?
So
the
I
don't
know
if
you
saw
the
issue,
but
the
point
is
that
github
container
registry
gives
you
a
lot
more
metrics
than
docker
hub
and
given
the
rate
limiting,
they
announced.
J
A
I
think
you
should
see
this
tab
as
well,
but
basically
it's
just
as
simple
as
you
can
do
it
publicly
as
well.
It
gives
you
a
docker
pull
and
then
it
also
shows
you
the
pools
per
tag,
which
means
that
we
would
have
a
better
understanding
of
of
how
many
people
are
still
using
older
versions
and
newer
versions
and
github
will
also
give
you
more
thorough,
metrics,
like
what's
the
the
comparison
between
arm
and
linux
and
windows
and
all
of
those
architectures.
C
A
A
I
retagged
them
and
published
them
to
the
new
registry
so
that
all
the
versions
are
in
the
new
registry
and
then
people
can
already
migrate
or
not,
and
then
just
drop
a
note
that,
as
of
the
next
version,
we
will
only
publish
to
github
container
registry,
but
this
release
is
the
last
one
on
the
upper
hub.
So
you
don't
have
to
change
anything
yet,
there's
also
the
benefit
of
helm
charts.
We
can
change
it.
People
will
implicitly
use
the
new
registry,
so
if
you're
doing
yaml
deployments,
those
will
be
the
only
ones.
A
C
A
F
A
A
C
A
A
F
F
So
we
are
working
now
on
the
blog
post
that
you
see
tom,
put
a
link
in
there
for
that's
gonna,
be
an
announcement
for
the
alpha
one
we
just
mentioned.
Actually
the
images
for
alpha
one
are
up
on
github
container
registry
as
well,
and
I
think
those
are
all
the
the
basic
pertinent
details
of
this
thomas
king,
big
time.
F
I
don't
think
you're
slacking
on
this.
Oh,
yes,
so
yeah,
so
alpha,
one
was
technically
released
on
the
github
page,
the
github
releases
page
a
couple
weeks
ago.
So
since
then
we
are
moving
forward
with
some
of
our
alpha
2
features.
You
can
go
in
and
see
the
milestone
for
that
on
the
hdp
add-on
repo.
F
A
I
think
it's
very
nice
piece
of
work.
Indeed,
the
only
thing
that
sometimes
comes
up
is:
do
we
also
create
the
services
and
the
ingresses,
and
all
of
that
or
do
we
only
support,
bringing
your
own?
I
can
see
value
in
both,
but
today,
noah
had
a
good
point
on
slack.
Is
we're
building
an
auto
scaling
solution?
F
I'll
just
throw
out
there
my
plan
is
to
build
a
layer
on
top
of
this,
it's,
like
you,
said
tom
different,
different
repository,
probably
outside
of
the
keto
org,
so
whatever.
If
we
take
stuff
out
of
this,
if
there
are
things
in
this
that
are
out
of
scope,
it
won't
be
thrown
away
in
case
that
is
off-putting
to
anybody.
So
if
anyone
thinks
that
there
are
things
that
are
out
of
scope
of
this
project
that
are
in
the
project
now,
rest
assured
it
won't
be
just
thrown
in
the
trash
cans.
J
K
F
The
operator
has
to
create
the
the
activator
workload,
the
deployment
for
the
activator
and
the
service
for
the
activator
and
an
external
scaler
and
a
service
for
the
external
scaler,
and
that
is
because
the
external
scalar
may
be
maybe
obvious
why
it
has
to
create
the
service
for
that,
but
for
the
activator.
We
would
call
it
the
interceptor
in
this
case,
but
either
way
that
that
workload.
F
The
external
scaler
needs
to
talk
to
that
as
well.
So
it
actually
creates
two
services,
one
for
the
external
scalers
to
talk
to
it
and
the
other
than
for
for
ingress
from
the
public
internet.
So
to
me
that
seems
like
oh
and
one
of
I
think
one
of
the
things
that
prompted
this
discussion
is
there's
a
pr
in
there
now
to
also
create
an
ingress
to
route
traffic
to
the
public
proxy
server
in
that
that
activator
component.
F
F
A
H
H
Creating
you
know
having
an
option
whether
it's
an
example
or
or
built-in
option
to
have
it
build
everything
for
me
end-to-end,
but
personally,
most
of
our
services
are
going
to
be
exposed
through
a
multi-cluster,
ingress
or
or
something
that's.
Not
the
standard
single
cluster
ingress
so
being
able
to
have
options
to
bring
my
own
would
would
be
something
that
would
be
be
useful
for
for
our
work.
Our
use
case.
F
Another
question
ryan
that
you
just
reminded
me
of
is
right.
Now
we
have
the
operator
that
you
can
just
give
it
an
image
name
and
it
will
automatically
even
create
a
deployment
for
you
and
there's
a
pr
in
now
that
you
can
turn
that
behavior
off
and
just
have
the
operator
route
to
an
existing
deployment.
F
A
Yeah,
I
think
that
the
deployment
side
is
definitely
one
that
I
would
leave
out,
maybe
because
typically
deployments
you'll
need
to
add
environment
variables.
You
need
to
do
mounting
and
all
of
that
stuff.
So
if
we
support
it,
we'll
need
to
support
a
lot
of
different
scenarios
and,
frankly,
for
one
reason,
so
I
agree
there.
J
C
Nothing
makes
sense
to
me,
and
I
guess
that,
like
this
automatic
creation
of,
for
example,
the
deployment
from
the
from
the
image
or
or
the
the
other
things
is
maybe
more
of
in
charge,
some
kind
of
cli,
or
something
like
that.
Basically,
that
maybe
that's
yeah
built
on
top
of
on
on
top
of
the
core
core
solution.
C
J
A
A
F
J
A
F
F
F
A
A
Another
reason
why
that
would
be
useful
is
also
to
explain
to
people
more
in
a
walk-through
fashion
of
a
bit
similar
like
the
samples
we
have
today
hey.
This
is
the
the
non-auto-scaled
application
in
order
to
add
auto
scaling.
You
need
to
do
this
and
this
and
this
and
that's
how
it
works.
Because
then,
maybe
we
have
more
concrete
examples
of
of
the
steps
that
need
to
be
taken.
A
J
A
A
This
nginx
deployment
that
we
have
today,
which
is
exposed
to
a
service
now
we'll
apply
auto
scaling,
and
then
it
basically
shows
what
you
need
to
do
and
what
what
is
being
created
or
what
the
steps
are,
because
the
examples
we
have
now,
I
don't
have
it
open
anymore.
It's
just
hey.
This
is
the
http
scaled
object.
You
need
to
configure
it
like
this
and
this,
but
maybe
if
we
have
the
more
those
high
level
overviews,
that
would
tell
the
story
better,
but
maybe
it's
just
me
yeah.
I
don't
know.
A
J
A
Well,
actually,
I
was
recently
thinking
if
we
should,
I
think
we
once
discussed
it,
but
if
we
should
do
frequent
or
scheduled
releases,
maybe
not
really
have
them
as
hard
deadlines
but
more
to
stimulate
ourselves
to
release.
Because,
honestly,
I
don't
really
think
about
it.
Much
until
I
see
the
whole
changelog
and
thinking
maybe
it's
time
to
ship.
This.
D
C
K
C
C
A
Perfect
anybody
else
who
wants
to
share
some,
maybe
one
more
thing,
chiosi
about
the
scale
jobs.
So
I
was
wondering
if
you
are
up
for
contributing
metrics
for
those
so
that
people
can
use
prometheus
to
monitor
them.
The
discussion
we
had
was
more
about
somebody
who's
looking
at
parsing
the
logs,
because
he
he
doesn't
have
the
metrics,
but
ideally
he
could
use
that.
E
A
E
B
Weeks
it
I
got
back
here
for
the
last
few
minutes,
but
yeah,
that's
what
you're
saying,
but
actually
you've
been
just
here
snooping
around
yeah.
I
was
new,
my
my
daughter.
She
just
started
going
back
to
school
and
she,
when
she
did
this
when
she
was
in
kindergarten,
but
she
gets
really
anxious
when
she
goes
to
school,
and
so
when
she
was
in
kindergarten,
sometimes
she
gets
so
anxious
that
she
would
throw
up
which
usually
the
school
was
like
yeah.