►
From YouTube: 2020-10-29 - KEDA Standup
Description
Meeting notes: https://hackmd.io/cEi_FerdQvyTvB1i-5U0kg
A
How's
it
going
hey
jeff,
just
making
sure
all
my
stuff
is
set
up.
I've
I've
had
to
start
this
new
set
of
meetings
that
honored
and
I
are
helping
with
that's
at
8.
30
am
our
time,
and
so
I'm
always
barely
finishing
that
meeting
and
jumping
to
this
one,
but
but
we
are
good
all
right.
Let
me
just
pull
up
the
agenda.
I
see.
We've
got
a
good
few
folks
here.
I
think
we're
gonna
have
some
good
discussion
today.
This
should
be
a
great
one.
A
A
10Th
we'll
be
meeting
on
tuesday,
we'll
also
be
moving
this
in
hour
forward,
but
zoomy
neck.
I
think
you
already
had
daylight
savings,
I'm
about
to
have
daylight
savings
on
sunday,
so
maybe
it's
not
an
hour
forward
for
you,
but
in
general,
utc
is
moving
forward
an
hour.
So
first
things
first,
is
if
you're
new
to
this
meeting
or
watching
this
recording.
That's
the
most
important
thing
to
know,
because
we.
A
Okay,
we'll
jump
right
into
it.
We've
got
a
bunch
of
topics
here
to
start
with,
I'm
looking,
I
think
there
are
a
few
well
there's.
Definitely
some
folks
that
say
you
haven't
met
because
I
see
like
aaron's
on
the
call
he's
got
a
good
topic,
that's
on
the
agenda
as
well,
so
maybe
we'll
just
start
and
we'll
kind
of
do
a
quick
round
table.
If
folks
want
to
just
introduce
themselves.
A
I
think
the
big
one
is
first,
you
can
just
share
your
name
and
then,
if
there's
any
topics
that
you
want
to
discuss,
especially
if
they're
not
already
on
the
agenda
just
feel
free
to
flag
it
in
any
it
kind
of
updates
too.
So
maybe
I'll
start
just
kind
of
follow
this
one.
So
I'm
jeff
I
work
at
microsoft
on
azure
functions
and
on
cada.
The
only
update
I
have
before
we
go
into
some
of
the
agenda
things.
I
spent
a
little
bit
of
time
this
week
and
updated
the
samples.
A
D
A
F
A
A
Awesome
yeah
thanks
for
joining,
feel
free
to
listen
in
and
chime
in
if
anything,
pops
up.
So
thanks
for
joining-
and
I
spell
carvana
right-
it's
not
super
important,
but
just
curious
yeah
yeah,
you
spelled
it
correctly
sweet.
I
didn't
know
if
it's
gonna
be
okay
or
something
all
right
back
on
my
list.
James.
G
A
H
H
I
A
A
J
A
K
A
C
A
All
right,
so,
let's
talk
about
keda
2.0
we
had
recently.
If
I
come
over
here
to
our
releases
tab.
We
had
2.0
rc2
six
days
ago,
which
had
the
new
ibm,
mq
scaler
and
a
few
of
these
pr
merges
us
stuck
in.
We
just
want
to
checkpoint
and
see
oh
and
I
actually
am
curious
on
this
helm
stuff
because
I
haven't
dug
into
it
yet,
but
something
happened
with
home
too
anyway.
I'll
just
pause
any
any
thoughts
on
2.0.
A
K
That
we
are
on
a
good
way,
so
we
have
received
a
couple
of
small
fixes
from
the
rc2
so
and
suashi
did
a
great
job
on
fixing
the
memory
leak
problem.
It
was
like
the
like
the
biggest
issue
we
had.
So
I
guess
that
if
nothing
appears
like
anything
serious,
we
can
we
can
release
the
the
release
next
week.
Probably
I
don't
know
maybe
on
one
wednesday
or
something
like
that
in
the
middle
of
a
week,
so
yeah,
that's
it.
Maybe
I
will
keep
it
on
tom
for
the
helm,
issues.
D
C
Nrci
didn't
test
the
deployment,
so
apparently
I
broke
the
home
chart.
So
I
reversed
that
okay,
so
we
need
to
yeah
basically
migrate
to
full
helm,
api
version
2
again,
but
make
sure
the
crds
are
still
installed
correctly.
So
it's
the
first
issue
which
is
shipped
as
of
today
with
the
rc3
which
just
reverts
the
the
hunting.
K
A
A
A
B
A
C
A
C
A
A
A
Any
reason
we
don't
want
to.
Maybe
that's
a
better
question
sounds
like
we
want
to
all
right
and
then
we'll
have
to
do
a
few
things
at
the
time
I
can.
I
can
work
on
azure
applications,
specifically
like
an
azure
update
or
maybe
an
open
source
at
microsoft,
blog
post
tom.
You
mentioned
a
blog
post.
I
don't
know
if
this
is
one
of
the
different
like
use
case
blog
posts.
A
A
And
it's
possible
that
this,
the
azure
amplification
one
might
go
out
on
like
november
7th
after
this
has
already
passed,
but
I'll
see.
Sometimes
they
have
like
these
weird
things
around
links,
not
working,
and
they
don't
approve
it
until
the
links
actually
work.
End-To-End,
but
we'll
see
what
we
do
anything
else.
We
have
to
do
from
the
release
process.
Who
would
be
the
I
guess
who
wants
to
take
on
the
ownership
of
this?
I
guess
that's
maintainers.
We
could
probably
close
on
this
offline.
We
don't
have
to
close
it
here.
K
Yeah
one
more
one
more
little
thing
regarding
this,
so
probably
we
can.
We
can
move
like
the
development
back
to
the
master
branch
or
we
should
probably
agree.
Maybe
two
main
right.
I
am
good
at
this,
so
we
can
probably
do
this
to
do
this
change
like
right
before
the
release.
So,
okay,
I
can
do
that.
K
G
A
A
Yes,
all
right,
this
is
exciting
november
4th
unless
something
terrible
arises.
That's
super
exciting
all
right
before
we
get
to
the
demo
last
one
here
tom,
you
want
to
chat
a
bit
about
the
stand-up
moves,
which
I
guess
I
teased
I'll.
Let
you
just
comment
on
because
I
know
you
weren't
here
last
time
when
we
talked
about
the
sum
too.
C
E
K
B
L
A
A
lot
of
weight,
but
I
love
all
of
the
people
on
the
call.
Is
anybody
here
have
a
negative
reaction
to
1600
or
maybe
in
chat?
You
can
say
plus
one,
I'm
actually
calling
from
a
terrible
time
zone
right
now
and
it's
like
10
o'clock
at
night
and
that's
great
for
me,
but
I,
but
I
think
this
is
fair
tom
and
I
think
we
can.
We
can
do
this
so
I'll
keep
an
eye.
E
E
A
A
A
D
So
before
I
go
to
a
little
demo,
there
are
three
components
of
this
thing
and
what
we
were
looking
at
is
to
see
what,
if
any
of
these
components
make
sense
inside
of
cada
versus
what
makes
sense
is
like
a
complement
to,
and
then,
if
there's
a,
if
someone
is
a
complicate
comp
limit
to
cada
then
like,
where
should
it
go?
Should
it
be
outside
the
cater
outside
the
keto
org
inside
the
kid
or
whatever
that's
kind
of
a
secondary
discussion?
D
There's
an
external
scaler
implementation,
which
is
external
only
it'll,
probably
turn
into
an
external
push
at
some
point,
and
then
there's
a
reverse
proxy
as
well,
and
the
reverse
proxy
is
basically
a
hop
between
ingress
and
the
back
end,
the
actual
app
that's
scaling
that
doesn't
really
need
to
be
there.
That
could
just
be
your
standard
ingress
controller,
but
it
was
a
little
bit
easier
for
us
to
build
for
for
reasons
at
sort
of
at
the
outset.
D
D
So
I
have
this
khp
command
line
tool
right
now,
we've
called
this
thing:
cata
http
for
lack
of
a
better
term,
better
name
right
now
it
just
has
a
run
and
remove
so
run
takes
in
like
the
name
of
the
quote
app
and
then
a
container
and
some
other
metadata
and
then
behind
the
scenes.
I
have
k9s
the
little
dashboard
running
that
it's
just
gonna
show,
like
the
scale
up
scale
down
stuff.
All
of
this
is
in
a
namespace.
D
D
D
We
can
do,
of
course,
and
we
were
looking
at
exposing
like
a
yama
based
but
simpler
type
of
interface,
like
maybe
the
sort
of
your
docker
compose
like
interface
or
something
else,
on
the
same
level
of
simplicity,
to
be
sort
of
one
step
beyond
and
one
step
more
level
of
control
than
the
cli,
but
not
having
to
go
all
the
way
whole
hog
into.
I
need
to
learn
all
the
kubernetes
yaml
to
get
this
thing
to
work
so
anyway,
it
is
just
the
cli
for
now.
So
I'm
running
that
deployed
app.
D
D
Services
are
there
and
there's
more
there's
a
deployment
there
there's
an
ingress
there,
there's
a
bunch
of
other
stuff
there
as
well,
but
sort
of
the
cli
took
care
of
all
of
it
and
the
developer.
The
person
using
the
cluster
didn't
have
to
care
the
cada
operator,
the
not
not
this
cada
operator,
the
actual
person
who
installed
cada
and
who
is
operating.
The
cluster
has
a
record
of
all
of
this
happening
inside
of
that
control
plane.
D
So
you
also
get
a
sub-domain,
and
this
is
kind
of
fudged
at
this
point
for
the
prototype.
But
we
have.
We
have
a
pr
in
that
uses
the
http
application
router
to
get
a
real
automatic
subdomain
containing
creating
thing,
but
for
now
it's
fudged
I'll
just
show
the
web
app
just
renders
xkc
comics
via
the
via
the
comic
id.
So
just
for
fun.
Let
me
put
it
in
chat.
D
D
Xkcd.Containerapps.Dev,
let
that
run-
and
I
think
I
said
cata
to
a
polling
interval.
I
think
it's
10
seconds
maybe
might
be
30.
So
this
might
oh,
no
okay,
yeah,
so
keda
scales
up
the
ingress
and
the
actual
app.
We
may
change
how
this
works,
or
we
may
think
of
more
about
how
this
works,
at
least
but
yeah,
that's
cada.
Obviously
working
and
that's
sort
of
you
know.
I
show
this
because
this
you
know
sort
of
the
proof
that
all
the
machinery
scaled
object.
D
Everything
else
was
set
up
and
cada
is
working
properly
to
scale
this
thing
up
and
then
scale
down.
This
will
take
a
little
bit
longer.
So
I
won't.
I
won't
hold
up
the
rest
of
the
the
rest
of
the
meeting
with
this,
but
basically
this
goes
into
cooldown,
just
just
like
any
other
k2
app
and
then
starts
scaling
everything
down
back
to
scalar
proxy,
we'll
scout
onto
one,
and
then
this
of
this
xkcd
thing
will
eventually
scale
down
to
zero,
but
that'll
take
obviously
that'll
take
longer.
D
C
C
D
Yeah
right
now
it
doesn't
really
hold
the
request
very
well
for
yeah
for
lack
of
a
better
term.
I
think
it
has
a
timeout
of
20
seconds
and
we
should
probably
be
a
little
bit
smarter
about
how
long
it
waits.
I
could
probably
have
a
little
bit
more
now
it
could.
It
could
be
smarter
about
it.
It
could
look
at
the
back
end,
look
to
see
if
there's
a
pod
currently
pending
and
then
hold
it
for
longer
than
that,
but
yeah
right
now,
it's
dumb.
C
A
Yeah,
this
is
really
cool,
as
I
mentioned.
I
haven't
seen
this
before.
I
just
read
about
it
super
exciting.
The
the
question
I
have
in
this
is
part
my
ignorance
on
how
all
of
the
proxy
stuff
could
work.
Do.
What
would
I
like
if
I
wanted
to
use
nginx,
for
example,
for
like
my
ingress
and
I
do
like,
let's
encrypt
certificates?
D
You
could
use
it
with
this,
but
really
this
proxy
shouldn't
be
a
proxy.
It
should
probably
just
create
a
new
ingress
object
and
let
nginx
do
all
the
magic
and
then
this
thing
this
would
be
one
less
piece
of
machinery,
then,
could
offload
the
proxy
off
to
engine
x,
but
right
now,
nginx
could
point
to
this
proxy
and
things
would
still
work.
It
would
just
be
another
kind
of
unnecessary
hop
to
be
honest
with
you.
A
Sure
yeah
and
it
would
only
be
like
it-
you
know
I
I
can't
do
things
like
the
you
know,
auto
cert
bot
thing
on
ingenix,
and
that
was
the
only
one.
It's
like.
Okay,
if
I
go
with
this
approach,
what
happens
to
those
capabilities?
So
it
was
just
trying
to
map
it
together,
but
yeah
any
other
questions
from
folks
conversation
topics.
K
D
D
The
external
scaler
excuse
me,
so
they
keep
state
on
how
many
requests
are
coming
through,
so
that
they
can
feed
it
into
cada,
but
they
should
be
broken
out.
So
the
proxy
can
be
just
completely
stateless
right
now,
it's
multi-tenant
anyway.
So
it
would
make
a
lot
of
sense
to
be
able
to
have
it,
stateless
and
then
be
able
to
scale
it
up
and
down
and
then
yeah
and
then
it
can
just
you
can
spread
them
out
all
across
the
cluster.
K
And
if
I,
if
I
understand
correctly,
like
all
the
objects
and
everything
is
created
through
the
cli,
so
have
you
been
thinking
about
like
creating
some
controller
or
some
operator
right?
That
will
manage
the
resources,
because,
basically,
if
I
manually
delete
the,
for
example,
the
ingress
or
anything
any
other
object,
it
won't
be
reconciled
right.
D
Right
yeah
right
now
the
cli
talks
to
a
tiny
little
rest
api.
Actually
that's
in
the
proxy
and
yeah.
We
have
to
make
that
better.
I
think
you're
right.
Maybe
the
best
approach
is
to
have
an
app
object.
I
don't
know,
but
maybe
the
best
part
is
put
an
app
object,
app
object
into
kubernetes
and
then,
like
you
said,
have
a
controller
running
that
that
does
that
reconciles
it.
D
That's
smart
enough
to
know
whether
there
is
a
pod
running
for
an
app
and
when
there
is
a
pod
running,
it
updates
the
ingress
object
to
point
directly
to
that
service.
When
there's
not
a
pod
running,
the
ingress
object
points
to
it
and
it
that's
when
it
holds
the
request
until
there's
a
pod
running
it
forwards
the
request
and
then
updates
to
point
the
ingress
to
that
pod,
so
that
that's
as
far
as
I've
thought
through
that's
the
one
reason
why
this
you
know
quote-unquote
proxy
component
should
be
around
should
be
a
thing.
D
A
A
How
do
I
do
it
with
http
that
I
would
love
to
figure
out
how
we
could
first
class
this
in
many
ways
too,
like
I
think
we
at
one
point
tried
to
integrate
with
osiris
osiris
did
things
slightly
differently,
but
in
general
I
think
the
big
problem
was
like
osiris,
just
kind
of
is
on
the
shelf
from
everything
that
it
looks
like
from
that
repo.
I
think
it
would
make
sense
to
figure
out
what
parts
of
this
like.
A
I
don't
know
exactly
how
to
pull
things
apart,
but
I
would
love
to
see
how
we
could
start
to
move
this
and
whether
pieces
of
improvements
or
functionality
go
into
the
main
keto
core
at
the
very
least.
Making
it
really
easy
for
people
to
opt
into
this
additional
functionality
is
something
I
would
love
to
see.
Progress
being
made
on.
D
N
K
But
maybe
maybe
the
the
issue
is
like
more
more
transparent
for,
like
other
folks
that
are
not
like
directly
involved.
So
if
they
like
search
for
the
http
and
cada,
they
will
find
the
issue
immediately.
So
you
can
open
an
issue,
put
a
proposal
in
there
and
maybe
link
limited
documents
in
there.
If
you
want
to
put
it
in
the
document,
that's.
A
What
I
was
thinking
and
that
way
like
as
we
have
comments
or
evolve,
you
don't
have
to
kind
of
like
event,
source
the
github
issue
to
figure
out.
What's
the
current
state
but
yeah
github
issue
that
points
to
a
google
doc
where
we
can
go,
add
comments
and
update
and
kind
of
have
be
the
source
of
truth,
I
think,
would
be
fantastic,
yeah,
aaron
anything
you
can
do
to
help
here
and
ping
me.
If
there's
anything
I
can
do
as
well.
This
is
this
is
cool.
A
Cool
sweet
all
right
so
back
to
the
agenda.
We've
got
two
more
topics:
what
at
least
on
the
agenda-
and
I
let's
see
if
I
can
share
nope.
I
can't
because
I'm
not
the
host
anymore.
It's
fine!
The
way,
I'm
not
really
sharing
anything
with
the
agenda,
but
if
you
right
click
me
and
make
me
the
host
again,
then
I'll
I'll
share
my
screen
whenever
the
next
one,
though,
is
from
you
tom,
I'll,
open
the
issue,
while
I'm
getting
share
permissions.
C
A
metrics
from
somebody
I
don't
remember
his
name,
but
it
was
an
interesting
idea
since
we
already
scraped,
let's
say
all
the
metric
sources:
well,
the
scalar
sources
to
make
decisions
on
that
means.
We
have
the
metrics
and
his
idea
was
to
provide
metrics
for
all
of
these
so
that
they
can
also
be
used
in
other
systems
like
prometheus.
We
do
provide
some
metrics
already,
but
not
on
the
exact
metrics
that
we
we
got
from
the
dependent
system.
A
K
Yeah,
I
I
think
it
does
make
sense,
because
currently
as
systems
that
we
are
like
exposing
some
metrics
in
the
in
the
metrics
adapter
or
like
the
other
stuff,
that
is
pushing
the
metrics
to
the
hpa
to
the
actual
scaling
in
kubernetes.
So
we
are
exposing
these
metrics,
but,
for
example,
if
you
are
using
scale
jobs,
so
you
are
scaling
your
jobs.
You
don't
have
such
a
matrix,
because
skill
jobs
doesn't
use
the
metrics
server
or
mat
matrix
adapter.
So
I
see
I
guess
it
would
be.
K
There
are
some
like
hooks
already
like
prepared
by
the
operator
sdk
framework
or
the
build
up
framework,
so
it
should
be
pretty
easy
easy
to
expose
them
directly
on
operator,
and
it's
just
about
like
collecting
the
metrics
and
exposing
them
on
the
on
the
right
interface.
So
I
think
it
does
make
sense
to
to
have
it
because
then
we
when
we
can
create
some
kind
of
nice
dashboards
or
something
like
that
to
see
what
was
the
scale
and
etcetera
sure.
A
So
if
I
understand
this
right,
I'm
just
going
to
try
to
echo
back
what
I
think
I
understand
today.
When
you
use
scaled
objects,
we
pull
some
metrics
and
then
we
publish
them
to
our
external
metrics
adapter,
which
then
the
hpa
can
pull
from
which
in
theory
works
fine.
If
I'm
reading
this
issue
right,
if
I'm
using
skilled
objects,
the
problem
is
some
code
pass,
notably
scale
jobs.
We
don't
publish
the
metrics
to
our
external
metrics
adapter.
A
We
just
use
it
to
drive
scaling
decisions
in
the
operator
itself,
which
means
that
those
metrics
are
invisible
to
something
like
prometheus,
so
they're
saying.
Could
the
cada
operator
itself
expose
a
metrics
endpoint
so
that
prometheus
could
go
get
metrics
for
both
skilled
jobs
and
skilled
objects?
Is
that
more
or
less
accurate.
A
Yeah
it
sounds,
it
sounds
like
this
makes
sense.
It
sounds
like
it's
actually
not
super
complex
and
I
even
see
some
conversation
here.
It
looks
like
operator
framework
where
I
have
some
stuff,
so
yeah
yeah,
I
mean
tom.
I
don't
know
what
the
next
steps
you
have
in
mind,
but
I
think
the
consensus,
at
least
for
folks
on
this
call,
and
that
makes
sure
I
have
chat
open
as
well
in
case
anyone's
chiming
in
there-
is
that
this
this
feature
would
make
sense
to
add
in
yep.
A
Great
yeah,
that's
pretty
cool
all
right,
so
mirror
had
to
drop
off
but
chelsea.
I
believe
you
are
still
here,
and
so
the
last
item
on
our
set
agenda
was
discussing
this
pr
that
you
were
looking
to
open
so
I'll
just
turn
the
time
over
to
you
to
chat
and
if
you
need
to
share
your
screen,
let
me
know
and
I'll
I'll
give
you
those
permissions
as
well.
I
I
K
K
Maybe
maybe
the
other
question
is
like
like
do
we
want
to
make
this
exclusive
just
for
kafka,
or
do
we
want
to
make
it
part
of
the
specs
so
expose
it
for,
like
the
other
scalers
as
well?
That's
the
that's
the
general
question,
because
at
the
moment
we
can
we
can
put
the
property
in
the
directly
in
this
specs.
So
as
we
have
like
the
max
maximum
replicas
and
minimum,
we
can
have
like
this
this
field
or
we
can
put
it
into
the
into
the
scalar
specs
so
like
into
the
kafka.
A
Like
up
where
we
have
main
replica
yeah
yeah,
my
my
two
cents
were
like
the
scenario
makes
a
ton
of
sense
even
coming
from,
like
the
other
half
of
my
life,
which
is
azure
functions.
This
is
something
I
hear
from
that
site
as
well.
So
I
think
the
pattern
is
sound.
I
don't
think
it's
an
anti-pattern
in
any
way
yeah.
I
found
this
issue
and
I
guess
that
is
the
the
biggest
question
is
like.
A
Do
we
build
this
in
a
way
that
it's
unique
to
kafka,
or
in
this
case,
the
issue
that
they
said
they're
like
hey?
I
might
actually
want
to
do
this
with
the
event
hub,
scaler,
the
rabbit
on
cusco
or
the
kafka
scaler,
and
so
is
it
something
that
we
could
first
class
as
a
pattern
that
either
scalars
opt
into,
or
at
least
is
consistent
across
them
and
maybe
even
automatic
across
them.
I
don't
know
enough
about
the
code
base,
but
to
me
that's
kind
of
the
biggest
question.
I
A
A
Trying
to
think
I
know
we,
you
might
not
know
I'm
curious
if
there
is
a
like
if
there
is
a
spot,
where
we're
doing
anything
like
this
today,
where
like
before
a
metric,
or
I
guess
it's
just
before
activation
like
if
we
could
have
whenever
the
activation
path
gets
triggered.
It
checks
to
see
if
this
property
is
defined
and
make
sure
that
whatever
metric
is
less
than
activation.
I
don't
know
if
that's.
K
K
Yeah
like
for
from
the
just
top
of
my
mind,
I
guess
it
should
be
part
of
the
like-
is
active,
active
function,
so
the
one
that
is
being
been
checking
the
scalars.
So
basically
we
will
have
to.
We
will
have
to
modify
like
the
this.
This
function
for
all
the
scales,
so
that
would
basically
just
do
the
check.
As
you
said,.
K
A
A
Since
I
know
you
want
to
do
this,
if
like
we
could
almost
start
with
what
this
would
look
like
in
kafka,
just
keeping
in
mind
that
before
we
merge
it
in,
we
might
we'll
just
have
to
have
a
discussion
which
is
like.
Can
we
do
this
everywhere
else?
And
maybe
it's
a
copy-paste
exercise,
and
we
pretty
much
just
say
I
mean
there's
a
lot
of
this
actually
today
that
is
more
or
less
copy-paste
exercise
where
it's
like
load
in
the
metadata.
A
So
I
could
just
see
there
just
being
some
consistent,
very
standard
pattern
here
and
is
active,
which
is
before
you
go
to
whatever
line
here
is
telling
you
to
scale
the
thing
we
just
do.
A
check
which
is
like
hey
actually
is
the
metric
we
just
found
in
this
case
lag
like
is
lag
less
than
the
the
threshold
that
they
defined
and
I
think
the
way
we're
talking.
If
I'm
understanding
this
right
too,
it
would
even
be
that
in
the
spec
that
we
have,
we
might
add
another
property
like
a
first-class
property.
D
K
Okay,
so
maybe
if
you
can,
if
you
can,
please
open
the
pr
or
maybe
like
comment
on
that
issue,
and
maybe
like
show
us
what
you
have
done
for
the
photo
kafka
kafka
bit
and
then
we
can
think
about
like
okay.
This
is
like
good
enough
to
be
like
replicated
across
all
the
scalers
or
something
like
that.
It'll
be
great.
K
I
A
A
Great
yeah
and
if
you
need
anything
in
the
meantime
as
well,
whether
if
you're
not
on
it
already
obviously
github
issues-
are,
are
great.
I'm
I'm
really
bad
at
looking
at
github
notifications,
but
I'm
pretty
good
at
looking
at
slack
stuff.
So
you
can.
You
can
reach
us
all
on
the
kubernetes
slack
channel
as
well.
If
you
have
questions
throughout
this
week
or
next,
if
you
start
to
spend
some
cycles
on
it,.
A
K
A
I'll
paste
it
in
chat
here
for
convenience
in
case
you
want
the
notes
open,
but
I'll
pop
it
in
the
meeting
notes
too
great.
That's
all
the
scheduled
agenda
items
anything
else.
Anyone
wants
to
bring
up
while
we're
all
on
the
call
before
we
meet
again
on
november
10th
after
2.0
has
gone
out,
and
we
are
all
going
to
be
bright,
bright-eyed
and
bushy-tailed
earlier
in
the
morning
or
earlier
in
the
evening.
For
many
of
you.
C
I
have
one
more
thing
that
I
forgot
to
mention,
so
we
finally
sent
the
designs
for
the
merch
to
print,
and
yesterday
I
got
a
fedex
notification
that
something
is
coming
my
way,
which
was
not
the
idea.
So
normally
there
would
be
a
website
where
you
can
order
the
merch
yourself,
but
it
sounds
like
I'll
be
doing
a
lot
of
shipping
soon.
C
C
A
Great
awesome,
perks
of
the
perks
of
the
gig,
all
right,
that's
fantastic!
Finally,
and
if
you
want
that
evangelized
at
all,
I'm
more
than
happy
to
amplify
it,
but
I
also
don't
want
you
to
be
overwhelmed
with
all
the
people
who
want
swag.
If
we've
learned
anything
from
hacktoberfest,
it's
that
people
will
do.
A
For
a
free
swag,
oh
boy,
all
right
thanks
so
much
everyone
from
for
joining
and
yes
fulfilled
by
tom
you're,
you're,
very
reliable,
even
in
pandemic
times
thanks
everyone
it's
great
to
have,
especially
some
of
you
folks
who
haven't
joined
before.
Hopefully,
this
was
useful,
as
mentioned,
feel
free
to
reach
out
on
slack
or
on
github,
and
we
hope
to
see
a
few
of
you
in
a
few
weeks
and
have
a
bit
of
a
celebration
on
keda,
2.0,
so
great
job.
Everyone
we'll
chat
again
soon.