►
From YouTube: 2020-01-30 KEDA Standup
Description
A
A
C
A
E
D
A
A
G
A
B
A
A
We
just
go
around
we'll
use
the
order
of
the
list
here
and
if
anyone
has
any
short
updates
in
terms
of
what
they've
done
in
the
last
week,
what
they
plan
to
do
this
week
and
then
we
can
kind
of
have
some
discussion
for
agenda
items
and,
if
folks
want
to
add
those
to
it,
looks
like
Raja
Sachi
just
joined
as
well,
so
Raja
Sol.
Let
you
quickly
introduce
yourself.
A
H
A
A
One
that's
top
of
mind
right
now,
only
because
I
had
a
few
conversations
about
it.
Yesterday's
the
CNCs
proposed
old,
it's
still
in
flight
it
about
a
little
bit,
backed
up
just
because
it
has
to
get
approved
by
a
cig
who
has
not
met
since
last
year,
but
things
are
looking
fine.
There
I
created
a
few
issues
this
morning,
based
on
last
week's
stand-up,
specifically
of
some
items
who
want
to
do,
including
include
implementing
duck
typing
Mel.
A
C
C
It
was
difficult
for
for
me
to
get
started
to
debug,
Lisa
and
I
am
interested
in
knowing
I
see
that
there
is
some
thing
from
Semak,
I,
think
and
other
cells
also
working
on
email
also
I
want
to
see
if,
if
we
have
a
good
story
of
somebody
new
coming
and
starting
to
develop,
especially
on
windows,
so
yeah
windows-
maybe
it's
easier.
Basically,
she
is
setting
up
your
environment
just
starting
to
use
it.
Yeah.
A
C
C
A
Steven
and
Daniel
I'll,
let
you
both
split.
If
you
have
the
same
topics
or
different
topics
on
I
know,
one
of
the
things
Daniel
had
been
working
on
in
the
past
was
the
Postgres
scaler
I.
Think
last
week
there
was
some
interest
in
looking
at
my
sequel,
I've
seen
a
little
bit
of
cheddar
on
slack
I'll.
Let
you
both
update
for
any
work,
planner
or
work
done.
Yeah.
I
Absolutely
so
yeah
a
a
lot
of
some
good
projects
going
on
there,
so
an
associate
of
ours
from
a
company
called
politi
anine
at
omec.
He
actually
he
was
the
one
who
created
my
sequel
scalar,
because
Apache
airflow
Postgres
and
my
sequel
are
the
two
most
popular.
So
my
guess
is
at
some
point.
We'll
also
have
to
do
some
integrations
for
MS
sequel
and
anything
any
other
databases
that
airflow
users
are
using,
but
we
figured
that
would
be
a
good
enough
for
a
start.
Yeah.
C
I
C
I
Please,
and
if
probably
at
some
point
this
week,
I
know
there
was
some
questions
about
like
changing
it
from
Postgres
to
Postgres
sequel,
so
I'll
just
make
those
modifications
and
then
yeah,
I'd
love
to
Steven,
isn't
is
a
colleague
of
mine
from
astronomer
he's,
actually
kind
of
taking
taking
on
the
helm
of
helping
us
integrate
Keita
into
our
into
our
actual
systems.
So
we
can
start
offering
the
Postgres
scalar
for
airflow
for
board,
basically
yeah,
auto
scaling
for
some
of
our
customers
Steven.
I
If
you
want
to
speak
it
all
to
like
our
integrations
or
also
just
I,
wanted
to
bring
him
along,
because
he
also
has
some
good
experience
with
things
like
CI,
CV
and
I
was
mentioning.
There
was
some
interest
in
creating
some
like
kind
infrastructure
for
our
CI,
CT
pipelines
and
so
yeah
and
ten
testing
yeah.
D
Yeah,
do
a
lot
of
testing
stuff
infrastructure
stuff,
just
like
astronomers,
really
interested
in
Keita
that
get
cost
savings
in
our
cluster,
because
we
have
a
lot
of
just
like
pods
that
are
sitting
around
not
doing
anything
in
the
case
of
air
flow
celery,
so
I'll
be
working
with
Dan
I'm
gonna
just
like
to
listen
the
first
couple
of
times
and
see
like
what
needs
to
be
done
and
then
what
to
contribute.
Yeah.
E
I
E
Yeah
I
have
a
service
principle
that
has
access
to
one
kubernetes
cluster
and
the
test,
just
grabs
the
those
credentials
logs
into
Azure
and
then
grabs
the
queue
config
and
just
uses
it.
It
doesn't
actually
create
the
cluster.
The
cluster
is
created.
It
just
deploys
the
latest
Kida
to
it
and
a
bunch
of
pause
that
need
to
be
scaled
and
just
make
sure
that
these
kill
correctly.
It
only
tests,
Azure
queues
and
Ezra
blobs
right
now,
because
this
was
just
the
one
that
we
have
do.
I
E
I
A
Awesome
yeah
I'm,
showing
here
like
this,
is
yeah,
so
we
use
these
secrets
and
I
github
action
to
spin
up
a
cluster
run
some
tests,
but
if
there
were
other
n10
tests
where
we
needed
other
secrets
too,
we
can
chat
about
the
best
reason
to
get
those
in
a
nice
thing
here
is
like
once
they're
here,
I
can't
like
I,
can't
even
hold
a
value
there,
they're
very
invisible,
which
is
nice
yeah.
Only
your
github
actions
and
probably
some
other
weird
tool.
A
A
I
I
did
the
docs
I,
don't
know
if
I
Pete
I,
don't
know
if
that
PR
got
merged
and
I
know
that
there
was
like
there
was
a
comments.
I
think
it's
from
Tom
about
changing
it
from
Postgres
to
Postgres,
sequel
and
changing
the
variable
name
for
connection
I
could
probably
do
that
today,
I
just
kind
of
clear,
clear
it
up,
so
that
it's
ready
for
one
point
sure
great.
F
So
I
submitted
a
PR
for
as
a
monitor
yesterday
evening.
There
are
a
few
things
that
I
haven't
done
yet
so
for
tres
I
haven't
done
the
pot
identity
which
I
want
to
add
and
then
specifically
I
need
to
implement
authentication
with
off
grams
or
resolved
and
I
wanted
to
ask
some
questions
about
like
what
exactly
each
of
those
is
because
I'm
not
as
familiar
potato
face
the
k10,
codebase
I
seemed
off
ramps.
Is
the
information
taken
from
the
trigger
authentication
ya
know
file?
If
there
is
one
but
I,
don't
know
what
result
and.
A
E
Comes
from
the
tradition,
spec
sort
of
the
skilled
object,
references,
a
trigger
application
spec,
then
all
the
values
from
the
spec
will
be
resolved
in
the
off
pram.
If
it
doesn't,
then
the
other
option-
or
at
least
the
old
way
of
doing
it-
is
that
kata
would
resolve
the
environment
or
the
part
that
you're
pointing
to
because
the
idea
is
that
you're
trying
to
scale
the
pod,
so
you
get
all
the
secrets
from
it
and
then
you
see
what
kind
of
connection
strength
is
trying
to
connect
to.
So
those
will
be
the
result
environment.
F
E
E
The
name
of
the
enviable
yes,
so
the
idea
is
that
you
don't
want
to
store
in
the
skilled
object
or
you
only
want
to
store
it
in
a
secret
object
in
Canaries.
So
you
reference
it
indirectly,
either
through
the
metadata
or
through
the
trigger
off.
Essentially,
you
just
reference
the
name
of
the
environment
variable
in
the
metadata
universe,
the
name
of
the
environment
variable
it
that
the
pod
is
listening
to
and
then
that
will
be
resolved
or
you
just
mention
a
secret
directly
and
be
trigger
off,
and
that
will
also
be
resolved.
E
If
you
don't
have
any
secrets
in
your
metadata
that
you
might
not
need
to
use
them,
you
can
just
use
the
values
from
the
committed
ena
directly.
But
if
you
have
a
secret
then
it
should
live
in
a
canary
secret
and
then
it
should
be
indirectly
referenced
by
name
through
the
metadata
or
the
trigger
auth.
F
E
H
F
And
then
I
was
gonna.
Ask
a
question:
I
sorry
I,
don't
remember
who
said
it,
but
the
person
he
was
talking
about
contributor
guy.
It
pains
is
that
specifically
related
to
scalars
or
is
that
just
setting
up
from
the
beginning,
as
in
like
going
through
the
readme
that
has
the
multiple
options
or
how
you
consider
so.
C
I
think
so
this
is,
this
was
I,
think
I
was
able
to
get
it
to
build,
and
so
that
was
fine.
But
that
also
had
couple
of
couple
of
issues
there.
But
after
that
now
sort
of
just
changing
code
and
wing
and
just
deploying
it
using
helm
and
deploying
it
I
had
to
go
to
Emma,
TLP
out
and
I'm
unblocked,
but
some
things
could
be
just
clearer
there.
So.
F
So
I
guess
the
question
that
I
have
is
like
from
what
I've
been
seeing
as
I've
been
working
on.
This
like
kata,
is
a
pretty
active
project
and
there
are
a
lot
of
people
who
are
working
on
scalars
and
like
getting
up
to
speed
and
I
was
planning
on
doing
the
documentation
update.
It's
probably
not
gonna.
Take
me
very
long.
Would
people
prefer
that
I
do
that
really
quickly
and
finish
that
up
before
I
finish
my
scalar
so
that
way?
Hopefully,
people
are
running
into
this
problem.
Less
often.
A
It's
a
fair
question,
I
think
my
the
two
things
that
come
to
mind
there
are.
If
somebody
else
wanted
to
pick
this
up
and
then
the
only
other
one
is
will
get
to
talk
about
like
the
1.2
release,
but
I
know
that
there's
a
few
things
both
around
the
operator
hub
and
then
some
of
the
stuff
that
daniel
has
been
working
on.
F
C
A
F
That's
a
specific
to
like
helm
and
kubernetes.
So
if
you
don't
understand
that
as
well
like
when
I
was
walking
RJ
through
some
of
the
things
she
pointed
out
but
like
she
just
didn't
know
those
things
shouldn't
have
as
much
experience
with
keeper
Nettie.
So
that's
part
of
the
reason
that
I
wanted
to
do
it
because
there
was
a
lot
of
stuff
that
was
just
intuitive
for
me,
but
would
not
be
intuitive
for
someone
who
hasn't
been
working
with
kubernetes
and
home
for
like
two
and
a
half
years
so
yeah.
H
Yeah
that
really
helped
also
like,
as
I,
think
another
pointed
out
earlier.
The
experience
on
for
Windows
users,
because
I
believe
the
current
documentation
is
all
assuming
that
you
are
building
on
Linux,
so
I
think
that
also
makes
a
difference
on
like
this
mentioning
the
right
commands
that
would
work
on
a
Windows
environment
as
well.
So
yeah
Mel
helped
me
out
with
that.
So
that
really
works
well.
C
A
Crews
are
in
there
I
know
the
only
other
one
I'm
I'm
aware
of
because
this
event
have
one
was
in
the
last
release.
I
think
the
last
release
was
right
around
right
after
this
event
hub
once
then,
there's
something
around
the
operator
hub
that
Sibiu
neck
was
holding
out
for
so
I.
Think
honestly,
I'd
be
curious.
Daniel
are
you
okay
in
the
mode
where
it's
at
right?
Now,
where
you
have
it
working,
but
it's
not
checked
into
an
official
release,
or
would
it
be
beneficial
to
you
if
we
got
that
release
out
ASAP
I.
I
Think
it
would
be
beneficial
to
get
it
out
in
the
release.
Well
like
it
would
definitely
be
able
to
get
it
out
in
a
release
and
I
can
address.
The
I
can
address
the
Tom's
comments
about
changing
the
name's,
pretty
ASAP
I
I,
don't
know
if
there's
like,
if
you
get,
if
I
would
need
to
do
like
further
testing,
but
it'sit's,
pretty
stable
in
terms
of
like
I,
haven't
run
into
any
problems
with
it
sure.
A
And
I
I
also
don't
want,
like
the
other
thing,
I
it's
okay.
If
we
do
a
number
of
releases
and
Mel
I,
don't
I
also
don't
want
you
to
fill
my
god,
hey
we're
all
waiting
for
this
PR
aspect
to
it
too.
So
I'm
almost
wondering
if
we
should
just
cut
a
release
today,
do
make
sure
the
test
I'll
pass
yesterday,
which
they
just
did
cutter
release
today
at
1/2,
and
then
we
can
do
1/3
like
we
can
talk
about
it
next
ni.
A
F
Yeah
I
mean
either
way
is
fine.
For
me,
like
I,
said,
I
would
appreciate
more
eyes
on
the
PR,
because
I
know,
for
example,
like
Tom,
doesn't
have
tons
of
go
experience
and
I
I,
don't
know
who
to
reach.
Who
would
be
good
people
to
review
these
scalars?
So
that
would
be
nice
but,
like
I
said,
there's
not
a
ton
of
stuff
left
to
do
and
I'm
confident
that
I
will
be
done
by
the
end
of
this
week.
F
A
Let's
put
on
that
then,
and
that
is
good
I'll
flag,
so
Ahmed
would
also
obviously
be
good,
but
I
can
even
like
focus
on
the
call.
We've
had
experience
with
this
with
scalars,
whether
it's
you
know
Roger
saw
Daniel
myself
you
just
like.
If
you
get
the
chance
it'd
be
awesome,
you
know
if
you
want
to
poke
around
the
PR
and
see
if
anything
stands
out
to
you.
That'd
be
great.
I
H
A
And
then
Lucas
has
a
great
question,
which
is
something
because
this
was
one
of
the
things
that
like
right
now
we're
kind
of
like
releasing
one
we're
like
yeah.
It
feels
like
we
have
some
good
stuff
to
do.
We
could
switch
to
a
mode
where
it's
like
every
two
weeks,
we've
had
a
release
with
whatever's
that
merged
in
we
have
a
healthcare
request.
I
still
even
just
stop
there.
If
anyone
has
any
thoughts
either
way
on
that
one.
F
A
A
You
know
code
code
lock
as
of
1:30
and
then
in
release
of
whatever,
like
I,
can
work
with
you
on
that
and
we
can
sort
it
out,
but
I
think
it
makes
sense
so
that
it's
at
least
more
clear
to
folks
contributing
when,
when
releases
will
go
and
it's
possible
if
things
slow
down,
we
don't
need
to
force
ourselves
to
do
a
release.
If,
like
there's,
not
a
lot
there,
but
I
think
for
for
the
next
month
or
two.
These
days
have
anxieties.
A
C
I
I
Just
kind
of
wondering
about
it's
like
especially
like,
since
it
seems
like
people
make
these
scalars
pretty
quickly,
is
if
we
can,
along
with
like
the
documentation
on
how
to
make
a
scaler.
Maybe
you
kind
of
thought
of,
like
so
I
know
what,
if
we
could
like
kind
of
codify,
what
variable
names
need
to
be
like
if
we
have
more
of
a
code
around
that,
because
one
thing
that
I
would
want
to
avoid
is
any
situation
where
someone
has
to
like
change
the
API
after
it's
been
released.
A
I
C
I
think
you
are
using
is
that
in
the
contribution
guide
that
we
have
for
scalars,
we
also
basically
codify
how
those
properties
of
if
there
is
some
standard
that
we
want
to
follow.
There
are
scalars
what
those
attributes
or
properties
should
be
right,
because
it
keeps
coming
back.
Somebody
will
call
it
cons
of
you
know,
connection
string,
and
if
you
want
to
sanitize
that
you
should
also
qualify
that
yeah.
A
I
A
G
A
Have
this
today
in
that
we
have
a
way
that
kada
can
call
it's
called
an
external
scalar
which
uses
g
RPC
to
kind
of
talk
to
anything.
So
in
fact,
there's
a
scaler
that
works
with
a
tool
called
durable
functions
that
you
just
deploy
immersion
separate
from
kata.
We
talked
about
at
one
point
like:
should
we
make
all
scalars
external
things,
but
I
think
the
thing
that
held
us
back
is
like.
We
didn't
want
too
many
containers
that
all
got
floated
around
that
people
had
to
version
independently.
A
A
I
G
G
G
E
A
Alright
awesome
some
good
conversation
that
I
created
an
issue
while
we're
there.
You
probably
saw,
if
you're,
watching
the
recording
male.
Thank
you
very
much
as
well.
You've
been
helping
out
in
a
number
of
different
areas.
Sandra
I
think
you,
you
mentioned
the
beginning,
you
to
have
any
updates
this
week
and
feel
free
to
correct
me
on
chat
or
in
person.
Scott
anything
specific.
You
want
to
update
her
or
chat
about.
While
we
keep
going
down
the
line.
No
I
was
just
saying
hello.
A
I
know
the
ones
iffy
annex
not
here
I
think
was
the
one
who's
gonna
do
it,
but
we
had
a
big
conversation
last
time.
There's
a
few
changes
were
already
aware
of
we're
gonna
be
doing
in
some
v2
release,
which
could
be
whenever
that
is.
But
one
of
the
issues
that
I
tracked
today
like
actually
created
was
around
typing
and
I
know
that
the
kind
of
the
discussion
last
time
was.
A
You
know
there
was
a
few
C
or
Q
con
talks
that
we'd
seen
and
a
few
others,
but
whoever
ends
up
taking
this
I
think
it's
gonna
be
Sevilla
neck
from
from
Red
Hat
could
just
use
a
good
point
of
contact
to
help.
Make
sure
invalidate
like
hey.
Is
this
using
it?
Are
we
taking
full
advantage
of
this
pattern
here?
I,
don't
know
if
you
would
be
that
contact
and
I
might
just
thing
you
on
slack
and.
G
Know
it
sounds
great
I
also
been
working
up
a
proof
of
concept
to
do
duck
type
resource
discovery,
so
in
so
in
Canada.
If
we
have
a
bunch
of
object,
refs
that
point
to
things
in
the
eventual
ideas
that
that
reference
has
like
duck
type
ylabel
and
then
it'd
be
interesting
to
be
able
to
help
have
the
cluster
kind
of
like
autofill
what
what
options
are
available
for
that
slot.
So
maybe
that's
interesting
to
you
if
you're
gonna
also
dabble
in
the
duck
type
world,
sure
yeah,
absolutely
so.
A
G
Yeah,
you
can
also
do
things
like
it
doesn't
have
to
be
K
native
right.
It's
anything
that
uses
an
image
that
uses
going
and
kubernetes
or
docker
or
even
cloud
run
like
I
ship
images
and
run
them
in
cloud
run
from
that
very
cool,
so
is
it?
Is
it
only
go
based,
though?
It's
only
go
based
and
there's
a
few
other
things
that
are
in
progress.
Various
languages,
but
Co
is
its
kubernetes
go
gotcha.
C
A
And
ensure
I
assume
I
just
want
clarify
this
too,
because
some
of
these
repos
I
noticed
this
week,
I'm
not
watching
as
closely,
and
so
there
were
a
few
issues
on
some
of
my
samples
that
I
just
cleaned
up
this
week
when
you
open
the
PR
for
samples
I
assume
it
would
be
on
this
samples.
Repo
is
the
one
you
were
talking
about.
A
So
be
whenever
that's
finished
like
this
is
just
kind
of
a
collection
of
samples
that
folks
have
done
it'd
be
awesome
if
you
added
a
PR
here
too,
that
said
like
azure
blob,
and
then
it
can
link
like
this
one
links
to
in
this
case
it's
lives
in
kata.
So
that's
probably
a
bad
example,
but
this
one
links
to
like
Tom's
won't
hug
repo
where,
where
he's
managing
it,
but
at
least
it's
more
discoverable
yeah.
C
A
The
main
one
was
in
even
this
one:
I'm
curious,
I,
don't
get
alerts
or
if
I
do
I
have
too
many
github
alerts.
Now,
if
you,
if
I,
just
open
this,
where
it's
more
or
less
meaningless,
much
like
my
inbox,
so
just
ping
me
if
you're
seeing
a
PR
is
not
making
progress
on
one
of
those
answer.
Every
post
and
I'll
look
at
it
sure
thanks!
H
So,
in
my
end,
I
was
what
can
be
event
upscaler,
but
basically,
I
had
to
move
from
the
event
upscaler
to
using
the
task
card
to
the
scalar
with
event
hubs,
because
the
event
upscaler
there
is
a
dependency
that
the
roster
would
have
to
take
on
a
job
lot:
storage,
which
state
is
not
one
so
I
moved
to
the
factor.
Stealer
and
basically
I
saw
that
the
that
event
has
made
Stargell
official
plain
authentication
to
work
to
have
the
fafsa
endpoint
work
with
it.
H
So
that
is
an
authentication
that
I
added
into
the
sock
to
the
scalar.
So
those
are
not
sending
ER
for
eternity.
The
length
of
its
obfuscated
and
yeah
actually
Mel
have
to
help
a
lot
debugging
this,
because
I
had
all
helping
need
debug
in
general.
The
goal,
because
I
had
a
couple
of
I,
have
a
couple
of
things
that
I
wanted
to
accidently
call
out.
H
A
Okay,
so
let
me
I
want
to
dig
into
the
secrets
thing
I'm,
also
just
making
sure
so
you're
using
event
hubs,
but
you're
gonna
use
the
Kafka
scale
or
with
event
hubs.
Is
that
part
right?
Okay?
Is
that
so
what
I'm?
This
is
more
just
clarity,
I
one
of
the
reasons
or
one
of
the
things
I
run
into
issues
with
a
few.
This
might
have
been
almost
a
year
ago
at
this
point.
Was
that,
like
the
reason,
the
event
hubs,
one
requires
a
storage
account
is
because
event
hubs
doesn't
manage.
A
Checkpoints
for
you,
but
Kafka
does
Mike
Kafka
will
create
a
little
state
for
you
to
manage
the
checkpoints
when
you
use
the
Kafka
scalar
with
event
hubs.
Is
there
any
weirdness
there
with
where
the
checkpoints
are
stored
or
how
they're
stored,
or
does
it
just
seem
to
work
and
you're
doing
the
check
pointing
in
your
your
code
anyway?
I
assume
you
have
it
work.
Just
I
was
curious.
Yeah.
H
No
that's
a
great
question,
so
the
differences
with
the
event
upscaler
that
we
have
currency,
the
checkpointing
is
done
and
blobstore,
because
we
are
assuming
that
the
consumer
is
going
to
be
the
event
processor
host,
just
like
what
you
use
with
agile
functions
on
the
software
process.
Scaler,
yes,
you're
right,
Sarkar
does
checkpointing
in
another
topic
itself,
and
there
are
API
is
available
to
actually
get
that
check.
Pointing
information
and
those
api's
are
the
ones
that
are
called
in
the
state
in
the
fastest
killers.
H
C
C
H
Basically,
event
has
also
does
check
pointing
in
the
backend,
but
that
is
oblivious
or
that
is
not.
You
know
available
to
the
customers,
but
because
caster
does
check
pointing
and
that
API
is
available
when
event
hubs
implemented.
Thus,
after
endpoints,
they
also
made
sure
that
that
API
works
with
went
up
very
interesting.
A
Wow
and
then
for
this
is
super
interesting.
This
actually
might
simplify
step
2,
ok,
so
that
one
was
great
and
then
in
the
process
of
this,
the
Kafka
scalar
needed
to
support
a
new
authentication
type
so
that
it
worked
with
the
Venice,
and
in
doing
that
there
was
an
issue
where,
when
you
try
to
resolve
a
value
that
was
coming
from
a
secret
and
I
assumed,
this
is
not
the
trigger
authentication.
A
A
H
They
did
check
my
deployment
secret
family
file
for
carriage
returns,
as
I
am
base
encoding
it
to
base
in
base64
encoding
it.
So
I
did
cross
check
that
I
verified
that
there
are
no
new
Lancaster's
being
found
anywhere
else.
My
golang
file
is
all
in
LF
instead
of
CRLs,
so
I
mean
anything
that
I
could
think
of.
I've
tried
out,
but
just
a
simple
since
space
work
and
that
solves
the
issue.
But
I
was
just
wondering
why
in
the
first
place,
those
new
lancaster
do.
E
E
H
E
A
H
Thank
you.
The
other
thing
that
I
had
was
so
the
law
gift
library
that
is
being
used
in
the
Kafka
scaler
I
saw
that
it
is
not
printing
out
any
lower
level
logs.
So
this
is
what
actually
Mel
had
helped
out
with
I
had
to
actually
pass
the
parameters
that
I
wanted
to
be
printed
out
as
errors,
and
then
they
bubbled
up
and
were
printed
out
from
the
scale
object
controller
go
file,
but
so
probably
this
could
be
a
limitation
from
my
understanding
of
go
language
and
the
package.
A
Know
things
though
yeah
I
think
I.
Remember.
Let
me
open
up
the
chart
here,
because
this
was
recently
added
to
the
home
charts.
So
in
the
helm
there
is
a
oh
it's
not
even
on
that
one,
so
yeah.
This
is
really
poorly
documented,
which
I
can
grab.
Oh,
no
right
here.
Okay,
so
there
is
a
log
level
per
atom.
A
Passing
that
says
info
and
if
you
I,
don't
know
how
familiar
or
thumb
charts,
if
not
it's
fine
when
it
creates
the
operator
and
it's
passing
in
an
argument:
zap
level
equals
whatever
and
so
on
the
helm.
Char.
If
you
set
this
to
info,
you
can
even
like
manually,
go
and
edit
the
deployment
and
you'll
see.
Zap
level
is
input
by
default
and
I
think
to
to
a
Allman's
point.
A
F
C
A
I,
just
because
the
reason
it's
in
the
helm,
char
was
first
I
was
like
hey.
Is
there
a
way
to
pass
it
in
and
at
one
point
you
sent
me
a
note
which
is
like
here's,
what
the
values
mean
so
I'll
take
the
extra
time
that
I'll
reach
out
to
him
and
make
sure
that
this
is
documented,
both
like
maybe
later
on
and
the
contributor
guy,
but
at
the
very
least,
on
our
home
chart
so
that
the
home
charts
like
by
the
way.
This
is
log
level,
different
values,
name
yeah,.
H
C
C
C
A
Great,
that's
awesome.
Thank
you
great
updates.
Ok,
so
that's
that's
more
or
less
the
roundtable
for
the
sake
of
time,
because
it's
already
48
I
think
I'm
gonna
skip
some
of
the
agenda
items
which
is
fine
because
I
think
most
of
these
were
created
by
Tom
and
Tippi
Annette,
who
both
aren't
here
on
so
there's
not
much
discussion,
but
I
will
pause
here
and
I.