►
From YouTube: 2021-09-23 Crossplane Community Meeting
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
All
right,
the
recording
is
now
started
to
the
cloud,
and
this
is
the
september
23rd
2021
cross,
plane
community
meeting.
We
will
start
with
our
milestones
and
upcoming
releases
and
progress
on
the
core
cross,
plane
project
and
then
we'll
shift
over
to
providers
and
the
progress
that's
being
made
there
at
any
point.
In
those
you
know,
everybody
from
the
community
is
quite
invited
to
share
your
opinion.
A
Share
your
perspectives,
or
you
know,
needs
that
you
have
for
upcoming
releases
as
well
too,
so
this
is
always
a
good
place
to
put
in
a
plug
for
what
you
want
to
see
out
of
the
project.
So
I
think
this
was
the
day
after
the
last
community
release.
We
started
the
last
community
meeting.
We
did
a
1.4.1
patch
release
which
smoothed
over
an
issue
with
migrating
or
upgrading
from
previous
releases
to
1.4,
so
that
is
out,
and
that
is
the
latest
cross
plane
release.
A
We
did
talk
about
that
a
little
bit
in
the
last
last
community
meeting
too,
and
I
think
it
came
out
the
day
after
so
the
next
next
minor
release,
we're
tracking
towards
is
the
v
1.5.
A
The
expected
release
date
is
a
little
bit
over
a
month
from
now
on,
our
typical
cadence,
so
october,
26th
is
around
when
we
are
shooting
for
doing
the
release
for
one
1.5,
so
we
can
take
a
quick
dive
into
you
know
the
roadmap
we've
kind
of
talked
about
the
roadmap,
and
this
is
you
know,
kind
of
a
broader
perspective,
longer
term
view
on
upcoming
crossfit
features
that
are
not
tied
to
any
particular
release.
A
I
don't
know
if
there's
big
updates
here
to
mention
from
the
last
community
meeting
versus
what
we're
going
to
be
focusing
on
in
1.5.
So
if
anybody
wants
to
mention
anything
big,
that's
different
on
the
roadmap,
they
can
do
so
now,
but
otherwise
we
can
just
dive
into
1.5.
A
B
No,
my
my
my
general
philosophy
toward
this
is
that
I
don't
think
we
should
be
putting
anything
on
the
1.5
board
until
there's
like
a
concrete
deliverable.
That
is
a
feature
or
thing
that
will
ship
with
1.5.
B
So
I
imagine
that
potentially
I'm
about
to
take
two
weeks
vacation
so
that
might
affect
this,
but
potentially
like
if
scale
testing
was
like.
Oh,
we
did
some
skill
testing
we
found
out.
We
need
to
fix
knob
x
or
whatever.
Then
like
the
issue
for
fixed
knob
x,
I
would
put
in
1.5
because
that
will
shift
with
1.5.
But
the
fact
that
I
did
a
bunch
of
scale
testing
you
know
is
isn't
a
feature
of
1.5
or
any.
A
Oh
yeah,
that
makes
sense
nick
okay
cool
then,
is
there
any
updates
on
some
of
the
ack
pipeline
integrations
or
anything
that's
worth
mentioning
today.
A
All
right,
all
right,
let's,
let's
move
on
into
the
things
we
are
focusing
on,
I
think
a
lot
of
the
terra
jet
related
stuff
is,
you
know
not
tracked
in
this
board
and
I'm
wondering
if
you
know
matthias-
or
anybody
has
an
opinion
on
now
that
from
what
I've
seen
with
the
new
beta
for
github
projects,
that
you
can
track
items
across
for
organizations,
is
that
maybe
a
good
idea
here
matias?
Do
you
think
to
be
able
to?
I
don't
know
if
you
have
to
opt
in.
C
A
That
for
the
cross,
plane
organization
but
then
be
able
to
you
know,
track
terror
jet
related
stuff
on
this
board
as
well,
or
it's
not
really
tied
to
1.5
release.
So
it's
kind
of
another
ancillary
area.
E
So
the
answer
is
yes,
you
need
to
cross
plane.
The
crossplane
org
needs
to
have
access,
so
we
need
to
sign
up
for
the
better
and
get
up
better
from
what
I'm
seeing.
It's
not
enabled
at
this
point.
E
So
let's
sign
up
for
the
beta
first
and
then
we
can
discuss
whether
it's
it's
worthwhile,
we're
doing
this
internally
and
upbound,
and
I
I
I
like
it
a
lot
because
it's
a
for
the
cross
repository
management,
but
also
for
you
know,
fields
and
then
the
capabilities
of
slicing
and
dicing
by
these
fields.
Other
groupings
and
filtering.
E
But
let's
postpone
this
I
would
say
until
we
have
access
and
then
we
can
give
it
a
try.
A
Cool
okay
yeah,
that
sounds
that
sounds
reasonable
there
does
anybody
want
to
have
an
update
for
1.5
for
things
on
this
board,
we'll
get
into
terra
jet
stuff
later
on,
but
anything
specific
for
1.5?
That
needs
to
be
surfaced
here
within
this
meeting.
A
Okay,
oh.
C
Attention-
and
so
I
may
have
missed
this
so
1.4-
you
guys
released
a
composition,
revision
and
we
created.
I
love
it
by
the
way
we've
been
waiting
for
this.
We
created
an
issue
I
believe
nick
you
may
have
commented
on
it
regarding
enhancements
that
we
would
like
to
see
to
the
composition
revision
in
order
for
it
to
actually
work
at
scale
for
multiple
clusters.
B
I
do
yep,
so
there
was
a
there
was
a
if
I
recall
correctly.
The
theme
was
that
revisions
are
being
created
across
multiple
clusters
and
revisions
have
at
the
moment,
non-deterministic
names,
and
you
would
like
to
be
able
to
write
a
configuration
that
will
push
the
same
revision
out
to
all
the
way
where
you
could
sort
of
basically
ask
a
claim
or
xr
to
use
the
same
revision
across
any
cluster,
and
even
if
we
were
to
change
the
names
from
revision,
random
strings
to
revision,
zero
region,
one
et
cetera,
et
cetera.
B
That
would
not
have
coordination
across
clusters.
So
there
was
a
proposal
to
add
versioning,
basically
to
to
revision
semantic
versioning.
If
I
remember
from
I
do
yep
and
is
that
you're
in
just
the
context?
Here's
where
proposing
doing
this
in
1.5
that.
B
I
I'm
a
little
on
the
fence
about
it.
To
be
completely
honest,
not
the
problem.
In
general,
I
see
the
problem
in
general,
and
this
is
this
is
not
a
very
yeah
just
how
we
fix
it
is.
Is
what
I'd
like
to
think
a
little
bit
about
okay,
to
be
completely
honest,
like
an
oops
suggestion
of
semantic
versioning,
for
these
revisions
is
not
probably
would
work
it's
just.
B
I
have
never
seen
an
api
reference,
be
semantically
versioned
in
kubernetes
before
so,
I'm
wondering
if
there's
a
more
idiomatic
way
to
do
it
or
something
like
that
right.
It
probably
wouldn't
be
super
hard
to
implement.
Basically,
I
just
kind
of
want
more
more
feedback
from
the
community.
More
use
cases
on
this,
so
I'm
definitely
not
saying
it
won't
get
done
ever.
I
would
love
to
like
so
far.
We
only
have
guidewire
asking
for
this
feature
right
so
sure.
B
That
means
a
lot
like
it
would
be
awesome
to
get
like
one
or
two
other
customers
on
this.
It
could
just
because
it's
it's
sorry
community
members
on
it
so
could
just
because
it's
super
early
and
you're,
you
know
getting
way
out
there
ahead
of
other
folks,
so
definitely
sort
of
key
to
hear
more
from
community
members
as
to
whether
this
is
a
problem
for
you,
whether
you
would
like
it
solved
how
you
would
like
it
sold
et
cetera,
et
cetera,.
C
It
totally
makes
sense,
I
think,
we're
just
we're
on
the
push
right
to
get
things
fully
adopted
and
moving
ourselves
from
poc
to
really
mvp
and
getting
our
early
adopters,
and
you
guys
know,
revision
is
necessary
for
rds
yeah
makes
sense.
Okay
thanks!
A
Yeah
thanks
for
voicing
that
jillian,
that's
definitely
helpful
to
to
you,
know,
hear
that
feedback
and
know
that
that's
something
that
is
is
a
priority,
so
all
right,
other
other
notes
or
things
to
bring
up
for
1.5,
or
you
know
direction
here
for
core
crossblade
before
we
move
on
to
your
providers
and
then
tearjet
and
things
like
that.
B
I'm
in
the
process-
so
I
didn't
get
to
it
before
this
meeting,
but
I'm
gonna
drop
that
documentation
pr
in
the
1.5
release,
which
again
is
something
that's
kind
of
questionably
related
to
1.5,
given
that
it
was
backported
to
1.4,
but
I
feel
like
it
does
fall
along
the
maybe
lines
of
something
we
put
in
the
1.5
release,
notes
that
there
was
a
documentation
yeah.
Thank
you.
I.
A
All
right,
let's
head
on
over
to
providers
and
the
initiatives
there
around
increasing
provider
coverage,
so
the
first
item
there
is
to
get
an
update
on
the
terror
jet
project,
so
muaf
or
or
mathias.
Do
you
want
to
give
an
update
on
on
that
high
level
here
and.
D
Yeah
yeah
sure
thing,
so
there
are
a
couple
of
updates
one
is.
We
have
cut
the
tech
preview
releases
for
aws
and
azure
tf
providers,
and
everyone
is
welcome
to
play
with
them.
I'm
not
going
to
test
them
out.
Hopefully,
in
the
next
sprint
we
will.
D
We
will
release
alpha
version
of
them
with
more
extreme
features,
implemented
and
and
in
the
last
two
weeks
we
have
done
some
couple
of
like
you
know,
scale
tests
regarding,
like
you
know,
both
crds,
because
I
know
there
are
just
hundreds
of
crds
that
come
with
intelligent
providers.
D
There
are
some
great
findings
that
occur
put
in
the
in
the
issue
about,
like
you
know
how
we
can
make
a
passion
over
work
with
that
many
crds,
and
there
is
also
another
scale
test
related
to
like.
D
You
know
how
many
cr
instances
intelligent
common
controller
could
actually,
like
you
know,
reconcile
you
know,
acceptable
time
frames
so
that
we
know
where
we
are
and
we
have
like
a
baseline
performance,
magic
and
then
the
more
we
do,
like
you
know,
enhancements
on
the
enhancements
on
the
controller
and
all
the
logic
we
can
measure
against
that
baseline
other
than
that.
We
have
implemented
a
few.
D
So
that
is
ongoing
in
a
pr,
and
there
is
this
external
name
annotation.
So
you
know
in
internal
form.
There
is
a
similar
notion
to
our
external
line
called
id,
but
it's
not.
It
is
not
an
input,
it
is
always
output
of
of
the
apply
operation
and
then
you
can
use
it
to
like.
You
know,
import
a
resource,
but
it's
just
like
you
know.
D
D
D
If
user
gives
the
correct
information,
we
remove
the
name
field
from
schema
and
then
once
we
start
to
reconcile,
we
take
the
external
name
and
put
it
to
the
base
hcl
configuration.
So
this
way
we
we
get
the
comparative
with
exam
in
terms
of
like
external
name
behavior,
and
the
third
thing
is
tf
data
annotation.
D
So,
like
you
know,
the
the
tf
state
file
is
something
like
you
know
that
can
have
sensitive
information,
and
it's
also
like
you
know,
big
story
and
annotation
is
just
like
you
know
not
how
we
do
it
in
other
resources
and
we
in
the
original
design.
We
wanted
to
not
have
that
file
to
be
stored
anywhere,
like
annotation
or
secret,
or
file
system.
D
So
with
the
change
the
pri
open.
Today
we
are
able
to
get
rid
of
that
annotation
and
right
now
we
reproduce
a
tf
state
from
spec
status
and
external
name
and
then
run
a
terraform
refresh
to
get
the
current
state
of
the
world
and
then
like
run
the
plan
to
see
diff
and,
like
you
know,
run
all
other
operations.
So
we
are
able
to,
like
you
know,
not
have
any
external
stuff
that
we
we
would
put
it.
Yesterday
too,
we
can
address
some
of
liking,
our
concerns
in
the
community
users.
D
So
these
are
like
you
know
what
I've,
what
we've
been
working
on
in
the
last
two
weeks
in
the
next
two
weeks.
We
will
mostly
be
busy
with,
like
you
know,
making
it
more
like
you
know
like
raising
the
quality
bar
with
additional
tests,
and
there
are,
like
you
know,
a
few
decisions
that
we
made
in
the
beginning
that
we
want
to,
like.
D
Like
you
know,
in
the
alpha
release
of
azure
and
aws,
we
will
be
degree
reducing
number
of
crds
to
to
some
amount
that
we
can,
like
you
know,
add
the
configuration
objects
one
by
one,
for
example,
like
you
know,
50
crds
that
are
highly
requested
in
azure,
but
doesn't
exist
in,
like
you
know,
native
azure
provider.
So
we
would
add
that
we
will
add
those,
but
also,
like
you
know,
add
the
all,
like
external
name,
configuration
references
and
everything
that
we've
implemented.
D
At
that
point,
and
like
you
know,
the
alpha
release
will
will
contain
crds
that
are
like
now
for
the
exam
compliant
hopefully,
and
additionally,
next
in
the
next
screen.
I
hope
we
will
be
able
to
get
the
connection
details
work
as
expected.
Right
now.
We
are
not
able
to
publish
connection
details.
D
It
just
ends
up
in
the
observational
parameters.
So
we
would
like
to
like
you
know,
address
that
as
well
in
the
next
sprint
yeah,
I
think,
that's
that's
pretty
much
it
or
matias
want
to
add
anything
else.
F
Okay,
mine's
short
one
one
point
to
add
to
the
connection
details
thing
I
think
one
of
the
like
obstacle
was
how
we
would
get
the
configuration
from
users,
and
since
we
are
tackling
that
like
in
in
the
scope
of
providing
references,
an
external
name,
I
believe,
figuring
out
or
getting
which
fields
would
go
to
the
connection.
Details
could
be
simpler,
so
I
I
hope
that
that
would
be
solved
sooner
than
the
end
of
next
sprint.
C
E
Yeah,
all
I
wanted
to
add
is
just
a
shout
out
to
the
community
and
we
will
do
this
during
the
sprint
next.
Two
weeks
again,
if
once
we
have,
the
alpha
release
out
is
getting
us
feedback
for
the
existing
providers
for
the
current
state
of
provider,
tf
aws
and
pre
provider,
tf
azure
right.
We
we've
started
this.
It
has
has
some
core
functionality
and,
as
mobile
explained,
the
the
functionality
xrm
features
are
going
to
be
greatly
enhanced,
we're
going
to
create
more
crds.
E
So
it's
a
great
time
to
jump
in
and
and
provide
feedback.
So
shout
out,
please,
you
know,
have
a
look
at
them.
A
Yeah,
thanks
for
the
updates
on
all
that
progress
there,
and
you
know
the
next
focus.
A
Next
couple
weeks,
here
of
getting
those
for
the
azure
ads
aws,
you
know
providers
to
an
alpha
level.
Here.
That's
super
super.
A
D
A
All
that
come
together
since
the
last
community
meeting,
we
did
a
provider
gcp
release
for
v0.18
and
then
also
the
new
provider
gcp
beta,
that
has
you
know
beta
features
from
upstream
or
sorry
from
the
provider
services
from
gcp
itself.
Hassan
did
a
lot
of
work
there
to
author,
a
migration
guide.
So
if
you're
using
an
older
version
of
provider
gcp-
and
you
want
to
start
using
beta
features
of
the
gcp
itself,
then
there's
a
migration
guide
to
follow,
step
by
step
to
make
sure
that
that
migration
is
smooth
there
hassan.
C
A
Awesome,
it
takes
a
lot
of
effort
there,
dan
on
the
upfront
thinking
through
some
of
that
and
communicating
to
the
community
and
then
hassan
working
through
the
issues
there
and
getting
a
good
migration
guide
written
up
as
well
too
as
well
too
so
provider
aws.
I
wanna
dive
into
some
updates
there,
aaron
or
moff.
D
Yeah
yeah
so
right
now
there
isn't
a
huge
list
of
updates
in
there.
Like
you
know
in
this
document
about,
like
you,
know,
new
prs
and
stuff,
but
I'm
happy
to
say
that,
like
in
the
next
two
weeks,
we
will
be
actively
working
on
provider.
Aws,
like
you
know,
providing
feedback
for
prs
and
looking
up
issues
me
and
erin
one
week
me
and
one
week
him
so
yeah.
D
I
think,
and
our
priority
will
be
like
you
know,
merging
your
resource
prs
and
my
period
specifically
will
be
the
aws
sdk
v2
update
pr,
which
will
unblock
some
of
the
working
eks
apis.
A
Yeah
great
I'm
excited
to
do
the
community
focused
community,
push
on
aws
similar
to
what
we've
done
for
gcp
and
azure
recently,
which
I
think
was
pretty
successful.
A
C
C
A
Diving
in
from
your
new
new
fabulous
west
coast,
home
nice,
all
right
and
then
hassan
provider,
gsp
updates.
F
Yeah,
as
you
mentioned,
like
the
biggest
update,
is
we
did
a
release
after
four
months,
so
I
think
it
is
a
long-awaited
way
release.
So
this
is
the
number
one
thing
and
also
like,
while
working
on
this
release,
like
we
spent
some
time
to
fix
some
some
bugs
to
include
them
in
in
the
release.
So
there
are,
I
think,
four
top
top
top
four
bugs
I
listed
here,
which
is
the
one
was
auto
resizing
cloud.
F
Sql
is
handled
and
there
was
an
issue
with
again
cloud
sql
than
a
private
network
provided
actually
like
the
funny
thing
is,
it
is
just
a
you
know,
format
of
of
a
field
how
you
would
need
to
provide
and
unfortunately
like
if
you,
if
you
didn't,
provide
the
format,
the
the
field
in
the
expected
format,
you
got
no
feedback
that
that
is
the
problem,
so
it
was
like
open
as
a
bug
for
it
for
a
long
time.
F
So
after
investigating,
we
provided
a
fix
for
that
as
well
and
also
nick
opened.
The
pr
for
service
account
key
to
like
to
get
it
deleted
once
the
service
account
is
deleted
and
yeah.
There
is
also
another
issue
which
was
causing
gk
note
pose
to
get
updated
periodically,
and
it
is
again
a
similar
issue
with
the
one
that
I
pre
that
I
mentioned.
It
is
just
a
like
wrong
format.
F
The
the
not
pull
image
should
be
in
in
a
capital
case,
but
google
accepts
it
as
lowercase
as
well,
but
converse
is
it
to
capital
case
on
on
the
server
side?
So
crossplane
thinks
that
there
is
any
like
there
is
an
update
required,
etc,
so
that
that
was
also
one
of
the
bugs
included
another
update
and
not
inside
provider
gcp,
but
related
like
in
provider,
helmet
provider
kubernetes.
F
We
could
not
use
gke
after
1.18
and
because
gke
deprecated,
the
basic
authentication
and
provider
helm,
does
not
support
that
and,
like
a
big
shout
out
to
aaron,
to
kicking
this,
this
like
pr
off
and
then
nick
finalized
and
we
merged
it
in
provider
helm.
So
you
can
use
with
any
new
version
of
gke
and
the
tr
for
provider.
Kubernetes
is
also
open,
and
thanks
thanks
nick
for
that
yeah.
That's
that's
all
from
from
provided
gcp
site.
A
Awesome
assange
and
all
these
these
missions,
these
merged
pr's
here
that
are
listed,
all
those
got
included
into
the
18
0.18
release
is
that
correct.
A
Great
okay
and
alpha
updates
for
azure.
C
Reviewing
some
old
pr's,
so
if
we
can
get
those
prs
you
know
merged,
we
can
also
make
a
new
release,
maybe
in
the
near
future.
A
Yeah-
and
I
think
that
definitely
was
you
saw
the
benefits
of
a
community-focused
community-
push
on
getting
a
lot
of
those
pr's.
You
know
attention
and
getting
feedback
on
them,
so
we're
getting
a
lot
of
them
closer
to
being
merged
and
adding
new
support,
adding
fixes
and
stuff.
So
I
think
that
was
definitely
useful
over
the
past
couple
weeks,
all
right
any
other
notes
for
providers
or
milestones
or
anything
before
we
move
to
the
community
section.
A
All
right,
yeah,
let's
move
on
down
there,
then
so
in
terms
of
content,
updates,
a
ton
of
updates,
as
usual
here,
there's
a
whole
bunch
of
new
videos
that
victor
has
been
been
giving
talks
in
videos
here,
so
those
are
all
linked.
I
don't
think
victor's
on
the
call
this
week,
but
these
are
all
links.
The
youtube
videos
are
all
linked
right
here
in
the
agenda
document,
so
you
can
check
those
out
and
see
some
of
the
new
topics
that
victor's
been
working
on.
A
We
did
get
a
write-up
in
forbes
magazine,
that's
really
magazine,
I
guess
it's
all
mine,
but
forbes.
We
got
it
right
up
there,
which
is
quite
interesting,
so
definitely
check
that
out.
If
you
haven't
already
so
that's
some
good
good
content.
Some
a
community
member
also
did
a
intro
talk
to
about
about
cross
plane
recently.
That
is
linked
here
as
well
too.
A
So
that's
that's
available
right
there
and
then
there
is
an
upcoming
webinar
as
well
too,
with
the
strya
folks
led
to
about
a
collaboration
with
crossplane
and
open
policy
agent.
It's
at
the
end
of
the
month
here
in
about
one
week
and
there's
a
link
to
register
there
if
anybody's
interested
in
checking
that
out,
yeah
cool,
so
a
lot
of
interesting
content,
always
opportunities
for
education
and
learning
more
about
crossplane
and
some
of
the
scenarios
and
use
cases
there
with
this
stuff,
and
so
this
cncf
incubation.
A
I
think
this
will
be
the
last
week
that
this
agenda
item
will
be
on
here,
because
we
officially
did
pass
the
the
vote
for
the
technical
oversight
committee
in
the
cncf.
There
has
been,
the
announcements
has
been
made,
etc.
So
we
are
officially
an
incubation
project
and
we
start
getting
some
benefits
now
with
the
cncf.
A
For
you
know,
greater
press
and
marketing,
you
know
getting
more
talks
et
cetera,
acute
upcoming
kubecons,
so
we
have
a
kubecon
china
meet
the
maintainers
maintainer
track,
talk
and
now
as
well
too,
that
we
weren't
able
to
get
at
previous
food
cons.
So
a
lot
of
benefits
coming
out
of
that
a
whole
lot
of
attention
on
the
project
as
well
too.
A
lot
of
the
project
statistics
have
gone
significantly
up
in
the
past
week
or
so
since
we
announced.
A
So
if
you
want
to
read
more
about
the
incubation
milestone-
and
you
know
some
of
the
project
progress
et
cetera,
we
wrote
up
a
blog
post
here,
that's
linked
in
the
agenda
document
on
blog.crossline.io
and
give
some
more
details
on
that,
and
you
know
everything
that's
been
going
on
recently.
So
this
is
a
really
big
milestone
for
the
crossfit
project
to
reach.
A
C
A
Timeline
for
that,
since
it
is
quite
a
rigorous
process
as
well
but
yep,
we
are
an
incubating
project
and
you
know
thanks
to
everybody
in
the
community
to
for
the
work
on
getting
the
project
to
this
point
of
maturity
and
we'll
just
keep
going
from
here
all
right,
okay.
So
then
I
I
really
like
the
concept
still
of
this
agenda
item
here,
but
we
haven't
been
quite
putting
items
in
there,
but
the
intent
here
is
there's
a
lot
of
interesting
conversations
on
slack
a
lot
of
interesting
issues
raised.
A
You
know,
investigations
into
you
know
bugs
and
performance
and
all
sorts
of
cool
stuff
there.
So
does
anybody
have
any
sort
of
interesting
conversations
from
the
community
or
things
of
interest
to
bring
up
here
in
this
forum.
A
All
right,
yeah,
maybe
maybe
a
link
here
to
some
of
the
performance
stuff
that
you
looked
into
out
there
might
be
interesting
for
the
community
as
well
too.
If
you
want
to
drop
a
link
here
to
some
of
your
write-ups
on
on
the
performance
stuff,
I
thought
that
was
quite
interesting
in
a
bit
of
a
illuminating,
deep
dive
into
control,
plane,
api
server,
ncd
performance
and
stuff
like
that.
So
that's
probably
an
interesting
topic
to
maybe
just
link
here
and
the
folks
can
dive
into
that
on
their
time
too.
D
A
Okay,
so
are
there
any
pr's
or
anything
that
folks
want
to
bring
up?
I
don't
see
anything
else
on
the
agenda
document
here.
So
anything
of
interest
or
a
note
that
needs
to
be
brought
up
in
the
community
today.