►
From YouTube: 2022-04-21 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
recording
has
started,
and
this
is
the
april
21st
2022
cross,
plane.
Community
meeting
folks
are
still
filtering
in,
but
I
think
we've
got
a
decent
quorum
going
here.
So
let
me
fix
this
here
for
for
stephen
all
right.
So,
let's,
let's
jump
on
into
it.
Here
we
are
in
the
middle
or
towards
the
end.
I
guess
the
back
half
of
the
1.8
release
cycle.
A
I
just
checked
before
this
meeting
on
if
there
had
been
any
recent
releases
of
of
cross
planes,
specifically
like
patch
releases
since
the
last
community
meeting
there
have
not
that
I'm
aware
of
so.
If
you
don't
have
any
some
recent
releases
in
a
right
now,
1.8
the
scheduled
release
date
is
may
17th.
A
I
had
been
saying
previously
in
in
previous
community
meetings
that
that
was
maybe
something
we
wanted
to
bump
up,
because
it's
in
the
during
kubecon,
but
actually,
when
I
kind
of
revisited
the
schedule.
The
conference,
like
the
main
conference,
part
after
like
the
co-located
events
and
zero
day,
events
and
stuff
doesn't
start
until
the
day
after
that
till
may
18th.
A
So
I'm
actually
totally
fine
with
just
leaving
the
release
date
as
scheduled
as
advertised
on
the
typical
cadence,
and
then
you
know
I
don't
expect
much
development
work
like
you
know
the
last
minute
there,
because
we
have
you,
know,
code,
freezes
and
feature
freezes
in
place,
so
I'm
totally
fine
with
actually
just
leaving
the
release
date
as
scheduled
for
may
17th.
A
A
So
I
know
that
there
is
a
couple.
A
couple
of
things
that
I
wanted
to
call
out.
One
is
that
I
believe
sergeant
has
a
a
pull
request
in
play
right
now,
that's
being
currently
reviewed
that
unblocks
a
couple
of
scenarios
around
around
references
and
when
they
are
resolved
and
also
like
self-referential
type
of
things
also,
so
I
believe
a
sergeant's
pull
request
addresses
both
of
those
issues
which
will
unblock,
I
think,
a
number
of
folks.
So
that's
going
to
be
really
useful
in
1.8.
A
A
Awesome
and
then
there
is
a
design
proposal,
as
well
as
a
parallel
pull
request
that
would
address
a
long-standing
issue
around
being
able
to
pull
in
data
and
basically
patch
your
compositions
from
common
data
sources,
such
as
config
maps,
etc.
I
think
that
that
is
going
in
a
pretty
good
direction,
but
I
and
I
think
that
some
things
are
being
figured
out
on
that
one
and
some
consensus
is
being
reached,
but
I
don't
have
a
great
read
on
how
much
is
left
in
that.
A
So
if
anybody
who's
been
involved
in
that
pr,
there
can
can
speak
to
that.
That
would
that
would
be
helpful.
But
it
looks
like
there's
good
progress
on
that
one,
and
I
would
love
to
see
that
one
in
1.8.
A
I
don't
know
if
hassan
is
on
tonight.
I
don't
know,
I
think
no,
I
don't
see
assange,
but
he
had
been
doing
some
work
on
the
designs
and
proposal
for
having
you
know:
plugable,
external
secret
stores.
A
We
have
support
right
now,
entry
for
writing,
secrets
and
credentials
and
sensitive
information
to
vault,
as
well
as
kubernetes
secrets
and
there's
a
proposal
here
of
how
we
can
continue
to
extend
that
and
enable
community
contributions
there
more
easily
by
being
able
to
do
those
out
of
the
core
crossplane
tree
and
un
decoupled
from
quarter
cross,
main
releases,
etc.
A
And
then
another
big
thing
here,
that's
being
actively
worked
on
pretty
pretty
hardcore,
which
we'll
get
into
more
details
in
a
specific
update
later
on
is
custom
compositions.
So
those
are
the
major
1.8
things
that
I
know
of
are
in
play.
There's
been
a
couple
of
things
that
have
already
been
merged
and
accepted,
so
they'll
definitely
be
included
in
the
1.8
release,
but
that's
the
most
of
the
stuff
that
I
know
of
that's
going
on
1.8.
B
One
thing
that
came
in,
I
don't
see
it
on
the
board
because
I
don't
think
it's
planned,
but
we
have
an
outside
contributor.
Well,
we
had
a
contributor
put
in
a
base64
encoding
for
compositions,
which
will
help
with
some
provisioning
of
ec2
instances
so
that.
A
A
Thank
you
for
doing
that.
Yep
yeah
was
that
bob.
I
think
I
think
yes,
yes,
awesome
awesome.
That
was
cool
to
see
that
bob
and
I
know
you've
been
doing
a
lot
of
work
in
provider
terraform
as
well.
So
it's
cool
to
see
you
here.
Thank
you
right.
C
A
Right
on
awesome,
okay,
yeah,
so
1.8
is
proceeding
as
planned.
I
think
we
still
need
to
get
into
the
details
around
custom
compositions,
but
proceeding
towards
a
scheduled
release
on
may
17th
all
right,
let's
get
into
some
provider
updates
as
well.
I
know
muaf
is
not
able
to
make
it
tonight,
but
there
are
some
updates
on
the
terror
jet
project
and
the
jet
based
providers
as
well.
This
is
something
I
believe
that
alpair
was
driving
and
I
think
it's
actually
quite
quite
impactful
as
well
alpert.
A
Do
you
want
to
give
us
a
quick
update
and
explanation
of
the
of
the
shared
runtime
for
the
jet
providers?.
D
You
know,
introducing
support
for
running
the
native
provider
as
we
call
it,
the
native
terraform
provider
once
and
you
know,
having
the
requests
done
by
the
terraform
cli
handled
by
that
single
shared
instance.
So,
basically,
how
terraform
normally
does
this
is
when
it
needs
to
make
a
request
to
the
native
provider.
It
forks
it
itself,
and
you
know
after
it
gets
the
response.
D
The
forked
process
for
the
native
provider,
you
know
is
stopped
and
you
know
another
request
results
in
another
fork
of
the
native
providers.
So
this
is,
as
you
would
imagine,
quite
unefficient,
and
you
know
when
we
are
reconciling.
You
know:
multiple
managed
resources.
This
also
means
that
multiple
instances
or
multiple
processes
are
running
in
addition
to
the
terraform
cli
processes
running.
So
we
had
long
ago
experimented
with
this
idea
and
we
had
something
already
working
and
right
now
we
have
introduced
this
support
to
the
big
three
providers
provider.
D
Jtcp
support
has
already
been
merged
and
you
know
provide
the
reject,
azure
and
providers.
Aws
pr's
are
under
review,
so
we
should
be
able
to
get
them
merged
pretty
soon,
and
you
know
we
have
already
done
some
experiments
measuring
any
performance
improvements
regarding
this.
D
The
effect
is,
you
know,
mostly
reduced
cpu
consumption
and
memory
consumption
with
this
shared
grpc
server
approach
in
based
providers,
and
one
more
thing
that
I
could
add
is
we
are
introducing.
We
are
rolling
this
support
initially
to
the
big
three
providers,
namely
azure
gcp
and
aws,
but
you
know,
other
terraform-based
providers
can
also
optionally
use
this
shared
grpc
server
approach.
A
Thank
you,
awesome
malpra,
thanks
for
that
update
on
that
and
thanks
for
driving
the
benefits
of
this
architectural
change
into
the
major
providers
as
well,
so
definitely
happy
to
see
that
in
the
being
included
in
upcoming
releases,
so
great
stuff
and
then
there's
another
update
here
around
missing
status
fields,
and
so
it
looks
like
type
builder,
is
getting
updated
to
make
sure
that
those
get
fixed
or
those
will
be
included
there.
I
don't.
I
don't
super,
remember
this
one
well
myself.
A
E
Yes,
I
am
working
on
this
one.
It
also
contains
the
refactoring
in
the
telegraph,
build
the
site
and
also
addresses
the
nested
stats
field
issue,
and
it's
actually
in
review
for
now
so
yeah.
D
E
D
Sorry,
so
saigon
is
also
tackling
what
this
in
the
refactoring
pr
he's
working
on.
A
Awesome
yep.
I
remember
that
a
couple
of
folks
doing
you
know
jet
based
provider,
development
work
or
you
know
using
them
on
the
field,
had
run
into
issues
that
seem
to
be
stemming
from
this
as
a
root
cause.
Some
of
the
stuff
that's
being
addressed
in
this
pr.
So
that's
super
helpful.
So
that's
good
that
this
progress
being
made
on
this.
A
That's
awesome,
all
right,
great,
okay,
cool
cool
cool,
so
there's
been
a
couple,
or
at
least
one
at
least
it's
called
out
here
of
there's
new
providers
all
the
time
it
did
seem
to
be
cropping
up
in
the
ecosystem
now,
which
is
awesome,
and
then
there
is
a
first
official
release
of
provider,
kafka
which
has
supports
for
both
topics
and
then
knuckles
as
well
in
its
initial
release.
So
a
lot
of
a
lot
of
folks
have
been
contributing
to
this
and
and
driving
the
the
effort
here.
A
So
this
1.0
release
has
been
through
a
lot
of
discussion,
a
lot
of
development
work-
and
you
know
it's
well
tested
et
cetera.
So
I'm
feeling
really
good
about
this
first
provider
release
and
it's
available
and
out
now
and
that's
that's
a
wonderful
thing:
there's
also
a
provider
pager
duty
release
that,
like
christopher
you're
on
the
call
I
think
right
and
so
that
is
now
published.
I
think
you
had
finished
the
work
like
the
functionality
a
while
ago,
but
now
it's
published.
C
Yes,
we
published
this
thanks
for
setting
up
the
variables
et
cetera.
A
Right
on
cool,
so
yeah,
so
it
sounds
like
that's
folks
from
the
community
are
finding
that
valuable
and
you
know
wanting
it
to
be
publicly
like
a
art
of
release,
artifacts
available
to
you,
so
obviously
somebody's
adopting
it
and
that's
a
good
thing
to
see.
Okay,
yeah
christopher!
Maybe
if
you,
if
you
can
think
of
following
up
to
add
a
link
to
that
first
release
of
pagerduty,
then
we
can
have
that
in
this
list
as
well
awesome.
But
then,
before
probably
oh,
yes,
dan,
sorry.
C
I
am
so
sorry
to
jump
in,
but
I
had
to
drop
and
I
just
wanted
to
just
10
seconds
really
quick
reference,
an
issue
that's
down
at
the
bottom
of
the
dock,
because
jesse
wasn't
able
to
make
it.
So
I
told
him
I'd
speak
on
his
behalf.
Yeah.
C
Integrating
signature
validation
into
the
package
manager.
This
is
definitely
something
we're
excited
about,
and
a
big
big
fan
of
the
folks
who
work
on
cosign.
Essentially,
we
would
make
it
a
setting,
I
believe,
for
you
to
be
able
to
verify
that
the
image
you
pulled
is
signed
correctly
and
that
sort
of
thing
I
think
we
might
take
kind
of
like
a
small
like
sig
or
working
group
development
approach
to
this,
for
folks
that
are
have
expressed
interest
so
just
want
to
encourage
anyone.
C
Who's
interested
in
this
functionality
drop
your
use
case
or
your
name
or
say,
I'm
interested
on
the
issue
and
we'll
work
on
organizing
some
some
meetings
and
stuff
around
that
sorry
for
jumping
in
there.
A
Oh
yeah,
no,
absolutely
dan,
that's
great
that
we
got
to
address
this
so
thanks
for
bringing
that
up,
and
I
know
that
you
would
be
probably
a
major
driver
of
the
thinking
around
that
type
of
functionality.
So
thank
you
for
that
work
and
effort.
A
Cool
all
right,
everybody
and
then
christopher,
got
a
chance
to
go
ahead
and
add
the
link
to
the
first
pagerduty
official
artif
artifact
release
and
then
christopher.
We'll
talk
back
to
you
now
for
some
updates
on
provider
aws,
because
I
know
this
is
a
big
thing
as
well.
I
think
that
was
actually
contributed
by
jesse
also
suggests.
His
name
keeps
popping
up.
C
Yeah
jesse
contributed
this
and,
I
think
also
steve
was
on
it
steven
yeah.
It
is
not
possible
with
provider
aws
to
assume
web
identity
roles
with
provider
config,
so
not
only
roles,
but
can
now
use
the
web
identity
roles,
zooming
and
yeah.
We
test
this
also
in
our
environments,
so
with
more
than
50
aws
accounts
in
place,
and
this
works
quite
well.
C
A
Awesome,
yeah,
fantastic.
I
was
definitely
glad
to
see
this
contribution
here,
so
thanks
justin
for
that
and
stephen
for
stewarding
it
and
helping
out
with
that
as
well
and
and
christopher
for
for
verifying
and
testing
and
and
getting
good
feedback
on
it.
Also,
so
that's
great
functionality
to
have
and
then
now
so
there
was
a
release
of
provider
aws.
I
think
what
just
yesterday
right
the
26.1
release
was
this
included
in
that
or
this
that's
going
to
be
in
20.27.
D
A
Got
it
thanks
for
clarifying
that
helper?
I
was,
I
forgot
what
was
included
exactly
in
26.1,
so
yeah.
I
think
that
was
a
fix
from
esky
to
fix
that
crowdfund
distribution.
D
A
There
so
that's
great
okay,
and
it
makes
total
sense.
Then
I'm
very
much
in
support
of
having
the
web
identity
off
stuff.
You
know
get
a
little
bit
of
bake
time
in
in
the
main
branch
and
then
go
out
with
the
major
the
next
next
full
release,
as
opposed
to
being
backboarded
for
a
patch
sweet,
okay,
good
good,
anything
else
to
add
on
provider
nws,
I
don't
see,
updates
for
azure
or
gcp,
so
I'll
open
the
floor
for
anything
from
provider,
aws,
azure
and
gcp.
All
at
once.
A
Cool,
okay,
all
right,
so
that's
all
the
updates,
then,
on
progress
for
crosswind
1.8
for
the
jet-based
providers
for
providers
in
general.
So
I
think
we
can
go
ahead
and
move
on
then
to
the
community
topics
and
questions
in
this
section
here
and
I
see
sergeants
gone
ahead
and
added
some
stuff
for
custom
compositions.
So
when
we
get
there
we'll
have
something
to
talk
about.
Thank
you
sergeant.
A
The
first
thing
I
wanted
to
mention
here
is
in
recent
announcements
and
contents
and
blog
posts,
and
everything
like
that
is
that
I
think
was
this
just
yesterday.
I
think
it
might
have
been
just
yesterday
that
the
both
in
github
stars
for
the
crossfit
project
and
also
slack
members
both
of
those
cost
five
thousand
yesterday
or
we
announced
it
yesterday,
at
least
so
that's
something
definitely
a
big
milestone
that
the
community
continues
to
grow.
A
It's
continuing
to
accelerate
as
well,
and
then
you
know
a
huge
thank
you
to
everybody
in
the
community
that
helps
specifically
with
you
know,
all
the
slack
discussion,
and
you
know
troubleshooting
and
all
that
sort
of
stuff.
So
there's
obviously
a
super
busy
community
people
are
asking
questions.
People
are
getting
help
and
you
know
people
are
answering
questions
and
providing
that
help
as
well.
So
thank
you
to
everybody
who's,
contributing
to
that
and
helping
out
with
that.
That's
been
really
really
helpful
and
continues
to
make
the
community
really
good.
A
Then
victor
has
another
another
video
here
around
using
get
ups,
get
ops
with
crossplane
and
then
flux
specifically,
I
think
that's
a
more
recent
video
and
click
that
here
to
go
and
watch
that
I
think
that's
generated
a
fair
amount
of
buzz.
I
saw
a
lot
of
views
on
that
also,
so
that's
definitely
something
that
people
are
resonating
with.
So
thanks
for
doing
that
victor,
I
think
so.
A
The
aws
folks
and
I
think
actually
some
of
you
all-
might
be
on
the
call
today
too,
if
I'm
not
mistaking
mistaken,
yeah
I'm
here,
yes,
awesome,
it's
good
to
see
you
all,
hey
yeah!
Do
you
want?
Do
you
want
to
talk
a
little
bit
about
the
aws
blueprints
since
you're
here.
B
Yeah
sure
so
so
the
open
source
team
at
aws,
I'm
the
team
members
there.
We
decided
to
create
this
blueprints
for
our
customers
to
use
for
crucibling
templates.
Essentially,
so
these
templates,
you
know
help
our
customers
set.
You
know
playing
like
you
know,
implementing
cross
playing
in
their
own
environments.
Yeah,
hopefully,
you'll
get
more
attraction
as
it
goes
on.
A
Yeah
awesome-
and
I
think
this
is
a
great
example
too
of
you
know
the
of
a
cloud
provider
that
has
you
know
kind
of
given
some
best
practices,
and
you
know
good,
like
solid
ways
of
implementing
compositions
and
provisioning
infrastructure
and
resources
within
the
cloud
fighter.
So
I'm
really
excited
that.
You
guys
did
this
and
it's
it's
pretty
good,
pretty
well
put
together
too,
so
very
excited
to
see
that
I'm
gonna
drop
a
link
to
the
repo
itself,
also
in
addition
to
the
blog
post.
A
So
we
have
that
here
too,
there
we
go
great
work,
awesome
and
then
I
think
then
victor
was
on
another
podcast
as
well
about
about
get
ops
and
infrastructure
and
crossplane.
So
victor
continues
to
stay
busy
and
continue
continues
to
be
talking
about
cool
stuff
for
the
community
all
right.
So
then,
so
I
wanted
to
go
ahead
and
surface
up
for
visibility
here
that
the
steering
committee
has
has
put
together
a
a
well
a
first
attempt
here
at
a
well-defined
project
charter.
A
I
think
some
of
what
the
cross
plane
project
is
about.
What's
in
scope,
what's
not
all
that
stuff
has
been
maybe
maybe
expressed
in
multiple
places
and
then
also
maybe
sometimes
it's
been
a
little
implicit
instead
of
explicit
so
now.
This
is
an
attempt
here
by
the
steering
committee
to
put
that
all
into
one
single
clear
place.
So
the
charter
and
scope
of
the
project
is
is
non-ambiguous.
A
So
I'm
encourage
folks
to
take
a
look
at
this
pull
request.
It
basically
adds
a
charter.md
dot
document
to
the
main
crossband
crossplane
repo,
so
feel
free
to
take
a
look
at
this.
I
know,
there's
been
a
bunch
of
discussion
already
on
it.
There's
already
27
comments
on
it,
so
yeah
feel
free
to
take
a
look
at
it
and
voice
your
concerns
or
or
questions
to
get
more
clarity
here
as
we're
being
very
crisp
about
the
boundaries
and
scope
of
the
the
cross
plane.
A
Project
link
is
available
in
the
agenda
document
here,
all
right,
cool,
then,
sir,
again
I'll
go
ahead
and
turn
the
floor
over
to
you
to
get
us
updated
on
custom,
compositions
work
and
is
nick
here
also
or
just
you
on
on
it,
I
think
maybe
yeah.
So
yes,
sir
sergeant
go
ahead
and
give
us
a
quick
update
on
custom
composition,
work.
E
Yes,
thank
you
jared.
Actually,
he
actually,
we
think
with
nick.
In
this
weekend,
we
announced
also
the
updates
in
the
channel,
and
also
I
want
again
to
say
that
we
picked
up
the
ch
root-based
approach
to
run
the
exam
functions.
E
As
you
know,
we
had
two
approaches
for
this
point,
and
one
of
them
is
the
cronja
based
and
then
other
one
is
the
church
based
and
we
co-pay
of
the
advantages
and
disadvantages
and
pro
and
conspiracy,
and
we
decided
to
implementing
the
church-based
approach-
and
I
added
two
comments
here
about
our
the
idea.
Center
decision
points
and
the
details
are
in
this
two
comments
and
also
nick
has
a
branch
for
the
implementation
it's
on
the
way.
Actually,
it's
not
completed.
E
However,
it
covers
the
general
architecture
and
also
the
actually
the
general
points
of
the
implementation.
However,
as
I
said
that
it's
on
the
way-
and
the
second
point
is
that
I
start
to
work
on
the
hand-based
example-
exam
function,
the
our
goal
about
the
alpha
version
of
the
custom
composition
for
the
cross,
plane
1.8,
the
one
of
them-
is
the
implementing
implementing
one
or
two
examples.
Exam
functions
for
testing
using
and
something
like
that,
so
actually
the
hand-based
one
is
a
good
candidate
for
this.
E
According
to
the
community
requests,
and
also
you
know,
the
helm
is
a
a
very
important
tool
for
us,
so
I
I
start
to
work
on
this
one
and
the
last
one
is
that
the
last
update
from
my
site
about
the
custom
proposition
is
that
nick
pushed
that
design
dock
updates
and
it
has
more
detail
about
the
architecture
now
it
it
also.
It
is
not
also
completed
for
now.
However,
we
hope
that
it
will
be,
it
will
be
completed
in
a
few
days.
A
E
Actually,
we
feel
good
about
this.
We
also
talked
this
point
with
nick
and
we
are
in
the
same
page
actually
for
now,
and
so
yes,
this
is
the
our
first
priority
for
the
releasing
the
alpha
version
in
the
cosplay
1.8
awesome.
A
Okay,
then
kubecon
eu
in
valencia
is
coming
up
soon
been
thinking
with
a
number
of
you
folks
that
have
talks
there
and
it
looks
like
progress
is
being
made
and
there's
a
lot,
a
lot
of
cool
stuff
that
the
entire
community
will
be
talking
about
on
stage
there
in
kubecon
in
valencia.
A
I
I
think
the
only
thing
to
reinforce
here
is
that
we
do
still
have
availability
for
folks
to
join
in
on
the
virtual
office
hours
session,
if
you're
not
able
to
make
it
to
valencia,
that's
a
fantastic
opportunity
to
still
be
included
and
there's
speaking
opportunities
if
you
want
to
present
to
attendees
on
that
session,
and
there
are
also
opportunities
to
help
out
with
the
q
a
because,
typically
over
the
last
couple
years,
when
we've
been
doing
these
virtual
hours
office
hours,
there's,
you
know
more
than
100
folks
that
join,
and
they
have
a
lot
of
questions
too
so
keeping
up
with
q
and
a
is
actually
quite
challenging
for
if
you
were
to
do
it
by
one
person.
A
So
a
small
team
of
folks
to
be
able
to
help
out
and
answer
questions
and
speak
or
present
if
you
want
to
as
well
is
if
those
are
available
so
reach
out
to
me,
and
let
me
know
if
you
want
to
be
involved
in
that.
A
Okay
and
then
yes,
and
then
there
was
another
addition
to
the
agenda
items
here,
about
rds
support
for
postgres
9.6
being
gone
soon,
deprecated
soon,
and
so
I
believe
that
this
has
been
fixed
in
the
upstream
crossbrain.io
documentation
now,
and
so
we
will
need
to
follow
up
and
include
that
in
the
downstream
distributions
as
well.
Essentially,
so
I
believe
that
that
work
is
is
ongoing
to
get
those
docs
updated
as
well,
and
thank
you
for
for
opening
an
issue
and
adding
that
here
to
the
agenda.
A
So
I
believe
that
should
be
addressed
soon,
all
right
and
then
so
jesse.
I
see
you
on
the
call
now
and
when
dan
had
to
take
off
earlier
in
the
call
he's
he
spoke
to
this
real
quick,
were
you
were
you
actually
there
when
dan
mentioned
that,
or
did
you.
B
A
B
Missed
that
part,
my
apologies,
I
had
to
oh
no
problem
at
all.
I
imagine
you
know
he
was
able
to
give
a
good
recap.
One
thing
to
note
is
that
I
did
I
mean
I
don't
know
if
he
mentioned
this
because
he
probably
wouldn't
have
known
so
I
did
join
the
six
store
community
meeting
this
week
and
they
gave
me
some
some
tips
on
on
how
to
explore.
B
You
know
the
implementation
I'm
I'm
interested
in,
and
I
could
speak
to
dan
about
this
async,
but
I'm
interested
in
what
the
cross
playing
communities
take
on
this
particular
feature
is:
how
do
you
go
about
introducing
a
new
feature
like
this,
and
you
know,
is
this
a
isolated
enough
use
case
or
a
specific
sp
specific
enough
scope
that
we
don't
have
to
go
through
major
exploration
here?
A
Yeah
very,
very
good
question
jesse
and
so
dan
spoke
to
some
of
that,
but
not
all
of
it.
So
these
are
still
relevant
things
to
talk
through
right
now,
so
in
general,
I
think
that
we
like
we
tend
to
err
on
the
side
of
you,
know,
proposals
and
design,
or
one
pagers,
at
least
to
kind
of
get
an
opportunity
for
interested
folks
to
weigh
in
and
provide
some
of
their
feedback,
and
you
know
maybe
features
they
would
want
to
see
in
it
or
you
know,
opinions
on
architecture
etc.
A
So,
typically
we
do.
We
do
one
pagers
for
things
that
are,
you
know
still,
you
know
small,
it's
a
medium,
medium
scope
and
above
so
this
one
does
strike
me
as
as
probably
a
good
candidate
for
a
one
pager
to
just
get
the
the
some
of
the
things
out
in
the
open
and
to
be
able
to
converge
on
them.
A
Dan
also
mentioned
that
he
was
actually
interested
in
starting
up
a
little
mini
sig
like
a
little
special
interest
group
for
this
topic
as
a
whole,
also
so
yeah,
so
that
could
be
part
of
that
snake.
Moving
artifacts
from
that
single
collaborative
effort
to
drive
a
little
a
write-up
on
this
and
get
some
consensus
and
then
do
the
implementation
as
well.
B
A
Yeah
awesome
jesse.
I
definitely
appreciate
some
of
the
ideas
you're
bringing
to
the
community
now
and
it's
been
very
helpful,
so
yeah.
This
is
great
and
I'm
excited
to
see
what
the
what
the
sig
can
can
come
up
with
cool
thanks
yep.
So
you
said
yeah
just
stick
up
with
dan
and
you
guys
could
drive
that.
That
should
be
great
all
right.
A
So
that
was
the
end
of
the
written
agenda.
Here.
Do
folks
have
things
that
they
want
to
bring
up
now
that
we're
through
the
the
on
paper
agenda.
A
Okay,
then,
we'll
continue
pushing
forward
to
crossband
1.8
working
on
the
features
in
part
of
the
the
you
know
follow
along
with
progress
on
the
project
board,
release
is
may
17th
this
tuesday
of
when
kubecon
starts,
and
you
know
thanks
again
to
everybody
who's
contributing
to
getting
us
to
this
milestone.
Here
of
you
know
five
thousand
slack
members
and
github
stars
and
a
whole
lot
of
awesome
stuff
going
on
so
yeah.
A
Thanks
for
everybody
for
joining
and
we'll
see
you
all
async
until
the
next
one.