►
From YouTube: KEDA Standup - 2021-01-19
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
I'm
recording-
I
am
recording
good
morning
everyone
good
afternoon
good
evening,
wherever
you
are
we'll
jump
right
into
it,.
A
Have,
as
I
sign
in
here
and
grab
this.
A
Apologies
for
the
late
start,
my
my
nine
month
old,
just
woke
up,
so
I
was
helping
get
him
ready
for
the
day
before
I
jumped
on
all
right,
maybe
we'll
just
start
by
going
around
and
making
sure
everyone
on
the
call
has
a
chance
to
introduce
themselves,
and
if
you
have
a
topic
that
you
want
to
cover
on
the
agenda
that
maybe
isn't
already
listed,
this
would
be
a
great
time
to
flag
and
we
can
just
depend
the
agenda
as
we
go
so
I'll
start,
I'm
jeff,
holland,
I'm
from
microsoft,
and
the
only
updates
I
have
is.
A
I
have
a
to-do
list
to
finish
a
pr
around
scalar
governance
that
I
did
not
get
to
this
week
that
I
was
hoping
to.
It
was
on
my
to-do
list
every
day
and
I
kept
punting
it.
So
I
think
I
should
still
have
the
time.
I
don't
have
my
calendar
open
right
now,
but
especially
on
friday,
so
I'm
going
to
keep
that
one
and
I
should
be
able
to
get
to
it
this
week.
A
If
I
don't
get
it
to
this
week,
then
I
might
have
to
just
punt
it
off
to
someone
else,
but
we'll
see
and
the
only
other
one
I
have
before
I
keep
going
actually
I'll
pause
that
one
I
just
have
some
folks
from
microsoft
who
might
be
start
attending
these
that
I
was
able
to
talk
to
about
this
week.
So
with
that,
I'm
just
gonna
go
down
the
list.
As
I
see
it,
daniel
you
are
the
next
one
that
I
see.
B
Hi
guys
I'm
daniel,
I'm
from
astronomer,
and
I
do
have
something
to
add
to
the
agenda,
so
I
figured
out
the
problem
I
discussed
with
you
guys.
Last
meeting,
however,
is
kind
of
opened
up
some
new
problems
that
are
pretty
interesting.
B
Essentially,
what
happened
was
that
the
customer
who
was
using
caden
having
problems
they
were
on
eks
and
they
had
switched
their
entire
cni
to
calico,
which
I
guess
is
a
thing
people
do
in
eks
when
they're
doing
it
at
scale,
because,
like
calico,
has
like
a
limited
number
without
the
you
need
calico,
otherwise,
you're
limited
in
the
number
of
ips
you
can
use
for
your
cube
cluster
and
what
happens
is
calico
doesn't
allow
anything
in
the
coop
any
like
custom
controllers
to
speak
to
the
cube
api
safe
to
put
on
the
host
network.
B
A
We'll
dig
into
that
some
that's
perfect,
just
going
off
my
list
and
I
think
some
of
these
folks
are
just
joining
so
sorry
for
bringing
on
the
spot
we're
just
kind
of
going
through
giving
a
quick,
intro
and
then
letting
me
know
if
there's
something
we
should
add
to
the
agenda
or,
if
you're
just
here
to
hang
out
and
listen
in
so
next
on
my
list,
I
have
terry
humphries.
C
Hi,
I'm
with
gtp
services,
we're
kind
of
a
high-level
user
of
cada,
and
I
just
some
of
the
high-level
things
we
use,
such
as
cada
and
aks,
and
those
things
like
to
sit
in
on
the
public
meetings
just
to
go,
get
a
center
direction
and
how
things
are
going
and
that
type
of
thing.
So
I
appreciate.
A
D
A
Yeah
and
and
the
first
three
agenda
items
I
think,
and
this
one's
a
great
one.
I
I'm
using
this
one
later
today,
actually
in
a
demo-
and
I
used
it
during
that
webinar
last
week,
okay,
so
next
I
see
on
my
list
is
aaron
aaron.
You
want
to
give
a
quick
intro
and
let
us
know
if
you
want
us
to
add
anything
to
the
agenda.
E
Howdy
yeah
aaron
schlesinger,
I
work
at
microsoft.
I
am
working
on
the
kada
http
add-on
and
I
can
give
like
a
30
second
update
on
where
that
is
maybe
at
the
end
or.
A
A
Yep
perfect
thanks
for
joining
shubham.
G
Hi,
my
name
is
shubham,
I'm
from
nbc
as
a
I'm
working
for
nbc
as
a
open
source
developer.
I'm
here
for
just
attending
the
meeting
and
for
updating.
A
Perfect
thanks
for
joining
okay,
I
think
that's
everyone
great
all
right,
so
we'll
jump
into
the
agenda
then,
and
I'll
just
add,
yeah.
Actually,
cncf
incubation
is
the
one
I'll
add,
because
that
has
to
do
with
the
new
pm
that
I'm
gonna
see
if
we
can
get
some
help
with
so
we'll
get
to
that
there.
So
we
will
go
back
to
our
regular
scheduled
programming.
A
This
first
issue.
Let
me
open
it
up,
I'm
assuming
tom
that
you
created
this
zibianik's
not
on
today.
I
don't
know
if
he's
off
just
because
he's
off
for
the
day
or
I
also
he,
I
think,
he's
also
expecting
a
child.
I
don't
know
if
that's
what's
happened
either.
A
I
don't
know
tom
if
you
know
mostly
just
curious.
D
Maybe
I
should
unmute,
but
he
couldn't
make
it
today,
but
he
added
this
issue
because
somebody
wants
to
have
armed
support
and
fortunately,
github
does
not
provide
an
arm.
Github
actions,
runner
so
we'd
love
to
do
this,
but
we
would
have
to
somehow
run
arm.
I
don't
think
azure
has
arm
support
yet
so
we
would
need
to
get
it
somewhere
else.
D
A
A
I
jus,
I
don't
know,
I
don't
know
if
anyone
on
the
call
knows
how
we
could
do
this,
given
that
we
use
github
actions
for
ci
cd,
and
I
don't
even
think
github
actions
has
the
way
to
like
install
an
agent
on
some
arm
vm
in
aws.
If
we
want
to
use
like
aws
arm
vms.
A
An
arm
machine
somewhere
and
I
think,
with
cncf
we
get
a
bunch
of
google
cloud
credits.
I
don't
know
if
google
cloud
has
arm
vms
and
maybe
we
would
do
that
would
be
the
preferred
approach
for
us
I'll
check
that.
Actually,
if
we
can
get
that
yeah
yeah
yeah,
I
don't
know
if
they
have
it
either,
but
interesting.
Okay,
I'm
curious.
Do
they
mention
why
they
want
arm
support?
Oh
yeah,
we
asked.
A
That's
true
yeah.
I
know
a
few
folks
who've
done
the
raspberry
pi
thing
and
they've
just
used
the
the
worker
nodes
as
the
raspberry
pi's
and
then
like
the
the
operator.
One
they've
had
to
use
a
different
instance,
so,
okay
cool
for
arm
support.
We
need
an
arm
machine
to
build
wondering
if
google
cloud
could
provide.
A
A
I'm
not
gonna
go
ahead
and
update
that
issue
right
now,
but
okay
k
to
2.1,
oh
we're
ready
for
another
release,
I'm
so
excited
wow.
It's
already
been
drafted.
Did
you
put
oh
zibianik
put
this
together
five
hours
ago,
very
cool.
There's
a
ton
here,
yeah
we're
we're
definitely
due
for
a
release,
but
we
can
do
it
if.
D
A
Could
be
the
the
release?
Captain
too,
I
wish
we
had
a
quick
chat
for
me
to
just
like
chat
with
you
zibianek.
Even
when
I
was
I
guess
we
have
email,
maybe
I'll,
send
an
email,
we'll
just
figure
out
who
can
be
the
release
kind
of
captain
for
this
release,
but
yeah.
This
is
great.
There's
a
lot
of
good
stuff
here.
A
Okay,
I'm
just
reading
through
it
quickly
awesome,
okay,
yeah!
Let
me
make
a
note
here
to
send
a
and
sorry
I
don't
know
what
you
can
and
can't
see.
When
I
open
up
my
to-do
list,
hopefully
there's
nothing
sensitive
there.
I
moved
it
out
anyway,
email
say
yoshi
on
release.
Captain
question
mark
sweet,
yeah,
I'll
see.
If
so,
yoshi
can
grab
it.
That'd
be
super
helpful.
Oh
and
I
see
a
chat
message
here.
Yeah
it
looks.
A
He
doesn't
think
gcp
has
rpms.
Maybe
cncf
gives
us
aws
credits
too
they're.
The
only
cloud
that
I
I
know
has
arm
vms.
I
don't
even
know
what
azure
story
is
with
that.
I
should
know
when
or
if
it's
coming,
that
I
don't
okay
and
so
the
next
one
here
functions
tooling
the
azure
functions
tooling.
A
Now,
when
you
use
these
commands,
that,
I
think,
is
what
you
link
to.
I
think,
there's
actually
even
a
dock
here.
If
I
come
in
here
to
functions
in
kubernetes.
A
If
you
run
this
command,
it
will
actually
generate
for
you
aka,
2.0,
metadata
and
and
deployment
which
is
awesome
and
and,
like
I
said,
it's
live
and
pro
now
I
installed
the
latest
functions
core
tooling,
and
it
had
that
in
there,
and
that
is
special
thanks
to
tom.
Who
did
you
end
up
just
fully
doing
that
entire
pr?
Like
did
anyone
even
assist
you
on
that
other
than
reviewing
it.
A
A
A
Out
it
is
out
if
you
have
and
that's
what
like,
if
you
just
download
through
the
main
versions,
core
tools,
3.0
dot,.
A
Which
I
now
have
running
on
both
my
mac
and
my
windows
machines.
They
have
the
bits,
so
your
bits
are
live
in
prod,
okay,.
A
Yep
three
two
three
three
three
point:
oh
three,
two
three
three
and
obviously
greater
okay.
So
that
brings
us
here
daniel
to
this
calico
and
cni
stuff.
A
I
don't
know
if
we're
going
to
have
many
networking
experts
on
the
call
you
kind
of
mentioned
the
beginning
when
they're
using
calico
they're
configuring,
their
networking
to
pretty
much
like
calico,
is
handling
all
traffic
and
that
gesture
is
somehow
making
it
so
that
ada
is
unable
to
communicate,
and
I
actually
don't
even
fully
know
like
which,
because
in
for
cadet
to
work,
I
believe
the
main
call
is
like
cada
calling
the
event
source
and
then
kata
calling
the
metrics
api,
and
it
sounds
like
one
of
those
things
or
both
of
those
things
are
being
blocked
anywhere.
B
Yeah
yeah,
so
I
actually
chris
dockery,
I
just
had
him
join,
he's
he's
our
head
of
support
and
he.
B
H
Hey
guys,
thanks
for
having
me
I'll,
try
to
lay
this
out
the
the
best
I
can.
So.
This
is
it's
kind
of
a
specific
scenario
where
we
have
a
customer
running
on
eks.
H
The
unique
bit
is
that,
rather
than
just
slapping
calico
on
top
of
an
eks
cluster,
which
basically
like
delegates
calico
to
a
network
policy
manager,
they've
actually
ripped
out
the
default
eks
cni,
which
is
like
aws,
vpc,
cni
or
or
whatever
it's
called,
and
so
this
leaves
an
eks
cluster
in
a
unique
situation
where
you're
running
calico
on
all
of
your
worker
nodes
handling
all
of
that
traffic.
But
because
it's
a
managed,
control
plane.
H
H
H
So,
in
this
particular
scenario,
they're
using
they're,
they're,
running
airflow
and
the
scaling
events
that
cata
uses
to
determine
when
to
scale
is
a
postgres
sql
query
looking
for
airflow
tasks,
and
in
order
to
do
that,
it
has
to
talk
to
the
postgres
database
through
a
pg
bouncer
pod
in
in
in
different
name
spaces,
and
in
order
to
allow
that
traffic.
We
have
network
policies
in
place
that
allow
you
know
cada
operator
and
kit
operator,
metrics
api
server
to
speak
to
the
pg
bouncer
in
in
each
name
space.
H
What
we
found
is
that
pods
running
on
the
host
network
do
not
respect
these
these
network
policies
right.
So,
no
matter
how
wide
open
you
create
that
network
policy,
the
only
way
to
actually
enable
that
traffic
is
to
delete
the
network
policy
altogether.
A
I
think
it
made
some
sense.
I
think
in
short
and
like
maybe
my
even
statement
at
the
beginning
is
accurate
and
a
good
recap
where
it's
like
kata
needs
to
do
two
or
I
guess
three.
Networking
calls
like
three
primary
networking
calls
that
all
must
work
for
cater
to
work.
The
first
one
would
be
calling
your
event
source,
and
in
this
case
it's
postgres,
sql
and
postgres
is
inside
the
cluster
as
well.
Is
that
how
this
is
configured.
H
It
can
be
inside
or
it
can
be
an
external
database
either
with
it.
The
important
part
is,
is
that
it's
it's
it's
communicating
via
pg
bouncer
pods
that
are
in
the
cluster.
A
So
the
first
one
is
cada
needs
to
be
able
to
talk
to
postgres,
to
say,
like
hey
are
there,
you
know
rows
returned
in
our
query.
To
let
me
know,
there's
data
to
be
returned,
and
then
the
next
thing
keda
needs
to
be
able
to
talk
to
is
the
metrics
api,
which
is
part
of
the
kubernetes
master
and
say
like
hey,
metrics
api.
A
This
is
the
answer
I
got
from
postgres
and
then
the
third
one
that
I
was
thinking
of
while
you're
going
through
is
cada
actually
makes
a
call
directly
to
the
kubernetes
apis
to
scale
from
zero
to
one
and
from
one
to
zero.
To
say,
like
hey,
I
need
you
to
modify
this
deployment,
create
an
hpa
and
like
make
some
operations
controls
and
from
what
you've
described.
A
If
I
understand
right,
the
way
that
they've
configured
their
network
and
the
fact
that
they
have
control
planes
that
need
to
go
through
the
regular
eks
traffic,
because
it's
aws
is
managing
those
control
planes
and
then
you
have
a
bunch
of
traffic,
that's
also
being
managed
by
conoco
or
calico.
Sorry,
calico
kate
is
kind
of
trapped
between
both
worlds
and
you're.
Not
able
to
make
a
network
policy
that
makes
it
happy
enough
to
make
all
three
of
those
calls.
Is
that
a
fair
recap.
H
Right
exactly
so,
the
so
with
network
policies,
once
you
have
one
in
place,
it's
a
deny
all
unless
it's
explicitly
allowed,
and
so
when
you,
when
you
put
a
network
policy
in
place,
no
matter
because
those
pods
are
running
on
host
network,
they
never
get
picked
up
by
that
network
policy
budget
so
that
so
that
traffic
is
never
allowed.
A
Yeah,
and
so
the
problem
is
the
way
they've
set
up
their
cluster,
it
doesn't
seem
like
there's
an
easy
way
for
something
to
talk
to
both
something
outside
of
the
host
network
and
the
host
network
itself.
A
I
don't
quite
know-
and
I
don't
know
if
other
folks
on
the
call
have
any
thoughts
like
it-
would
be
good
to
capture
some
of
this
in
a
github
issue.
That
would
be
the
first
one,
because
I
don't
know
if,
like
zibianek
or
or
even
some
folks,
that
we
could
ping
might
have
other
thoughts,
I'm
not
sure
even
what
keda
could
do
here
outside
of
kind
of
this
interesting
configuration?
I
don't
know
if
it's
weird,
I
don't
know
if
it's
a
best
practice,
I
don't
actually
know,
but
it's
it's.
A
It's
interesting
like
like
the
almost
thinking
is
it's
it's
common
enough
that
it
is
mentioned
in
the
calico.
A
A
That
would
both
need
to
talk
to
the
master
node
and
make
some
kubernetes
calls,
but
also
might
want
some
ability
to
traffic
things
in
other
places,
a
lot
of
sidecar
operate
like
istio.
Even
I
would
imagine,
is
doing
some
some
stuff
there,
and
so
part
of
me
is
interested
in
like.
Is
this
a
cada
problem,
or
is
this
a
calico
ekscni
problem?
A
D
A
Yeah,
because
the
the
only
other
thought
like
I
was
thinking
like,
is
there
a
world
that
we
split
up
cada
like
not
that
we
would
do
this?
I
don't
think
we
would
make
this
change
just
for,
but
like
in
the
theoretical
world
like
how
could
we
build
cada
in
a
way
that
would
get
around
this
pattern?
A
And
I
I
don't
need
like
there'd
have
to
be
some
like,
maybe
instead
of
cada
talking
to
the
the
postgres
database,
cada
talks
to
something
that
has
that
answer
and
then
you
would
have
to
deploy
something
in
the
cluster,
that's
pulling
postgres
and
then
just
storing
the
answer
and
some
storage
and
then
cada's
just
pulling
up
from
the
storage.
A
I
don't
know
if
that,
like
pretty
much
you
relay
the
data
you
say
like
kate
is
no
longer
going
to
be
using
http
or
whatever
it's
using
to
talk
to
postgres,
I'm
going
to
use
a
relay
here
or
message
broker
to
get
the
messages
that
cata
needs
to
cata.
A
I
don't
know
if,
theoretically,
that
would
work
it's
interesting
like
I
don't.
I
don't
know
if
that
feature
would
have
much
use
outside
of
the
scenario,
but,
but
I
don't
know
also
like
I'm
not
an
expert
in
calico
or
cni,
I'm
mostly
just
trying
to
piece
together
like
what
could
be
done
here.
So
I
I
think,
first
and
foremost,
it
would
be
like
describing
some
of
this
in
an
issue.
Maybe
linking
to
to
your
point
daniel,
I
think
you
mentioned,
like
calico,
has
some
docs
on
this
scenario.
A
I
would
be
interested
if
we,
if
we
did
some
google
searching-
and
we
saw
like
you
know
for
other
popular
kubernetes
operators,
whether
it's
linker
d
or
istio,
or
whatever
else
does
this
seem
to
be
a
problem
that
other
people
have
hit
and
how
did
they
get
around
it
or
have
they
been
able
to,
and
that
might
help
us
better
understand
what
could
be
done
here.
A
I
want
I
thought
about
that
for
a
second,
but
then
I
was
like
I
don't
even
know
if
kate
would
be
able
to
talk
to
that
external
scaler,
but
yeah
that
crossed
my
mind
too.
A
D
A
Maybe
it's
not
actually
an
external
scale
of
postgres,
maybe
it's
an
external
scaler
to
a
container
that
drops
something
in
storage
that
then
another
container
running
within
the
right
network.
You
know
wakes
up
on
and
says,
like.
Oh
I'm
gonna
go
make
this
call
and
then
relay
the
info
back,
like
kind
of
acting
as
a
bridge
like
you
almost
build
a
bridge
external
scaler.
That
in
theory,
could
work
too
that
one
actually
would
be
easier
than
changing
how
keta
works.
A
It's
just
a
lot
of
it's
a
lot
of
extra
moving
pieces
to
get
around.
What
feels
like,
I
mean
candidly.
What
feels
like
a
perfect
world
is
that
calico
has
a
network
policy
that
is
flexible
enough
to
say,
like
hey
this
thing,
this
thing
needs
to
be
able
to
talk
to
both
both
sides
of
this
coin,
but
I
yeah,
I
I
you
know,
I'm
speaking
well
above
my
expertise
here
when
it
comes
to
networking
policies.
A
Great,
it
would
be,
and
that
also
too
it's
like
xibianex,
not
here,
he
is
likely
a
a
better
kubernetes
networking
expert
than
myself
and
and
tom
and
I'd
be
interested
to
get
his
thoughts
on
it
too.
A
Okay,
aaron.
That
brings
us
to
you
anything
else
on
this
one:
eks,
calico,
cni,
okay,
aaron,
http,
add-on.
E
Cool
yeah
just
share
a
short
status
siren
been
to
the
meeting
in
the
past
couple
of
meetings
so
yeah
we
had,
if
you
remember,
a
prototype
repository
with
a
working
implementation.
Just
the
architecture
wasn't
really
exactly
what
we
wanted.
So
we've
moved
over
all
the
relevant
code
from
there
to
a
pull
request
in
the
http
add-on
repository.
E
E
I
have
to
put
together
a
few
more
issues
just
to
overview.
What
we
need
to
do
to
get
to
a
beta,
at
which
point
we'll
be
able
to
cut
a
beta.
So
I'm
thinking
early
to
mid
february
is
when
we
can
do
something
we
can
get
something
called
a
beta
out,
at
which
point
I'll
record
a
few
ascii
casts
or
screencasts,
or
something
like
that
and
write
a
couple
blog
posts
over
different
places
on
the
internet
and
so
forth.
E
So
that
brings
me
to
last
thing.
I
did
a
talk
at
a
small
conference
called
contributing.today,
along
with.
G
E
So
tom,
you
did
cata
overview
right.
A
E
Didn't
really
have
to
do
the
talk,
but
thank
you
for
that.
So
I
followed
right
up
after
tom's
cata
overview
with
http
add-on
overview.
I
showed
a
demo
of
the
prototype
but
talked
a
lot
more
about.
You
know
what
cada
http
looks
like
and
why
it's
around
and
so
forth.
So
that
was,
I
thought
both
of
our
talks.
I
thought
went
really
well
tom's
better
than
mine,
but
that
was
great.
E
A
That's
awesome
yeah.
This
is
great
progress.
I
I
know
this.
I
noticed
this
repo
was
here
and
I
even
plugged
it
during
one
of
the
answers
in
the
webinar
that
I
helped
with
where
someone
was
asking
about
http,
I
didn't
realize
we
had
the
pull
request
already
open,
though
with
a
bunch
of
the
code,
and
as
you
mentioned,
it
looks
like
it's.
It's
almost
ready
to
merge
in
so
this
is
really
exciting.
A
A
Never,
you
know
given
a
cater
presentation
without
this
being
a
question-
and
I
know
tom
even
added
this
to
the
faq
in
in
in
our
home
page,
so
keen
to
see
how
how
the
response
is
for
this,
how
many
folks
it
it
unblocks
and
how
we
continue
to
evolve
this
story
too.
So
thanks
aaron,
that's
a
great
update.
A
Would
you
be
up
for
writing
a
blog
post
as
well.
E
D
D
E
Yeah
so
that
starts
yeah
I
can,
I
can
for
sure,
write
a
post
that
last
thing
you
said
tom.
The
bits
and
pieces
thing
reminded
me
as
well.
E
What
we're
thinking
about
doing
is
writing
an
smi
external
scaler
and
kind
of
using
that
as
a
prototype.
If
that
makes
sense,
and
if
it
if
it
seems
to
fit
well
and
work
well
and
do
scaling
well
and
so
forth,
then
we
we
can
merge
back
into
core.
If
that
makes
sense,
I
know
there's
an
issue
open
for
it.
A
Great
yeah
yeah
there
is,
there
is
the
smi
when
I
was
just
asking
tom
about
that
one,
the
other
day,
because
I
know
he's
been
chatting
with
some
folks
from
the
smi
world,
great
okay,
so
good
updates
on
http
add-on.
Thank
you
aaron
for
joining.
It
was
that
the
last
one
I'll
mention
tom,
I
think,
brought
this
up
last
meeting,
which
is
that
we
want
to
pursue
the
next
step
in
our
cncf
process.
We
are
right
now
a
sandbox
project
and
we're
interested
in
becoming
an
incubation
project.
A
I
spent
some
time
last
week
just
looking
at
the
criteria
and
from
what
I
can
read.
I
think
we
meet
all
the
criteria
all
of
the
stuff
around
having
a
community
which
is
currently
on
this
wonderful
phone
call
and
elsewhere
around
having
some
folks
using
kata
in
production,
so
we're
gonna
work
towards
that.
I
have
asked
a
new
pm:
well,
not
a
new
pm
pm
who's
been
on
my
team
for
a
while,
but
she's
just
recently
returned
from
from
some
leave.
A
I
think
she
was
going
to
try
to
join
this
meeting
this
morning,
but
I
don't
see
her
so
that's
fine,
but
mostly
heads
up
tom,
her
name's
sonia
ives,
sonia
to
to
see
if
she
can
drive
some
of
the
work
here
to
get
the
incubation
status
set
up.
So
I'm
sure
she
will
be
pinging
you
if
she
has
not
already
and
myself
to
to
get
everything
that
we
need
to
get
that
set
up
in
in
review.
I
think
we
review
on
one
of
the
sigs.
A
I
don't
know
they're
always
changing
the
process,
but
but
yeah
that's
a
good
update
and
I'm
I'm
feeling
optimistic
that
we
could
actually
pull
this
off
and
that's
a
that's
a
major
achievement.
There's
not
a
whole
lot
of
cncf
incubation
projects
and
those
that
are
there
are
really
world-class
projects.
So
I'm
hoping
we
can
get
to
that
step
find
out
and
if
not
we'll
get
some
good
feedback
from
the
cncf
on
what
else
they
need
to
see
from
us.
A
A
A
Yes,
tom,
okay
tom
is
fantastic
at
reaching
out
to
folks
and
making
sure
that
our
logo
wall
becomes
even
more
beautiful.
So
if
you
are
on
the
call
and
you're
like
hey,
I'm
cool
to
have
my
logo
be
here.
That
would
be
awesome.
You
can
open
up
a
pr
on
the
k
to
docs
repo.
If
you
don't
want
to
open
the
pr,
you
can
ping
tommer
myself
on
slack
and
say
here's
the
logo
and
we
will
open
the
pr
for
you,
but
we
love
our
logo.
A
Wall
interior
go
go
for
it
tom.
I
have
one
coming.
D
Soon
but
it's
waiting
the
typical
legal
reason,
you're
sure
yeah.
A
A
Also
share
it
as
well,
and
then
terry
asked
estimate,
release
date
for
2-1
terry.
I
think
optimistically,
we're
hoping
it
will
land
later
this
week,
maybe
on
thursday
or
something
it
might
be.
Next
week,
though,
next
week's
probably
a
safer
bet
for
2-1,
just
because
I
don't
know
how
how
good
the
response
is,
but
if
we're
lucky,
it
will
land
later
this
week,.
A
Yep
no
worries;
okay,
awesome!
Well,
thanks
everyone
for
joining
I'll
upload,
this
recording
to
our
youtube
channel
and
we
will
meet
again
two
weeks
from
today.
So
thanks
everyone,
if
you
need
us
in
the
meantime,
slack
is
probably
the
easiest
way,
there's
details
for
the
slack
channel
in
our
cadet.sage
so
that
you
can
join.
Where
is
the
slack
channel
info?
Oh
right
here,
yep,
okay,
great
thanks!
Everyone
we'll
talk
to
you
later
thanks!
Thank
you.
Bye.