►
From YouTube: 2023-02-09 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
I
will
go
ahead
and
share
the
agenda
doc
link
into
the
zoom
chat
window
right
now,
so
folks
have
direct
access
to
the
agenda.
Doc
and
people
can
either
add
themselves
as
attendees
or
add
discussion
topics
for
things
that
people
might
want
to
be
getting
into
all
right.
So
I
think
biggest
news
is
that
since
the
last
community
meeting
we
got
the
1.11
release
out.
That
was
arguably
the
largest
release
that
crosswind
has
had
in
quite
some
time.
You
know
there
are
definitely
some
big
features
that
were
included
in
it.
A
You
know
such
as
composition,
functions
and
then
being
able
to
patch
from
the
environments
oh
Max
just
joined
in
too
so
max.
We're
just
talking
about
your
your
wonderful
environment,
config
feature,
so
there's
a
whole
bunch
of
awesome
stuff
that
went
into
1.11.
So
thank
you,
everybody
for
that
effort
that
went
into
building
those
features
and
testing
things
the
documents
she
massive
documentation
rewrite
from
Pete.
A
A
We
have
a
regular
release
Cadence
within
the
cross-plane
project
of
once
a
quarter,
so
the
1.12
release
date
is
expected
to
be
on
April
25th,
so
the
the
last
week
of
April
I
think
that
is
right
after
kubecon,
Amsterdam
I
think
it's
the
week
after
that.
So
that's
the
time
frame
that
we're
looking
at
there.
We
are
just
getting
started
on.
You
know,
figuring
out
the
priorities
and
figuring
out
what
folks
want
to
work
on
Etc.
So
we
can
talk
about.
A
You
know
things
that
the
release
board
and
the
roadmap
board
here
is
up
to
date.
So
you
know
I
think
things
are
roughly
ordered.
You
know
top
to
bottom
in
terms
of
priorities.
A
I
think
some
of
the
the
top
things
on
my
mind
that
that
haven't
really
gotten
some
work
on
them.
Yet
because
you
know
observably
resources,
that's
that's
still
getting
lots
of
attention
from
the
Sun.
That's
moving
along
a
lot
that
some
of
the
things
that
we
haven't
really
puts
a
lot
of
time
and
investment
into
yet
are
two
big
topics
that
I
think
are.
A
You
know
definitely
affecting
the
community
and
would
have
a
large
impact
on
the
continued
adoption
and
success
of
the
project
which
are
you
know
the
the
issues
we
have
are
still
around
crd
scaling
and
being
able
to
you
know,
install
multiple
providers
and
you
know,
have
your
cluster.
You
know
usable
Etc,
there's
been
a
ton
of
work
on
that.
Obviously,
and
a
lot
of
it's
been
Upstream
as
well,
but
there's
still
some
things
that
we
can.
A
We
could
do
at
the
crosswind
level
to
improve
that
situation
and
then
order
deletion
is
another
issue
that
I
think
can
can
get
some
attention
soon.
So
those
are
some
of
the
things.
So
this
is
you
can
look
at
this
in
order
here.
I
think
those
are
some
of
the
things
that
I
think
are
somewhat
important
and
I
would
definitely
want
to
consider
for
1.12.
They
are
not
things
that
I'm
saying
could
fit
right
away
in
2012
like
easy,
we'll
get
that
in
no
problem.
A
You
know
just
as
we're
starting
the
Milestone
planning
now
I
think
those
things.
Those
are
things
that
have
impact
and
would
be
worthwhile
for
us
to
consider.
You
know
having
as
a
priority
for
1.12.,
so
I
kind
of
wanted
to
you
know
with
that
statement
there
check
in
with
folks
and
see
you
know
if
there's
things
that
are
not
on
our
radar
here
for
things
that
are
important
to
the
community,
but
you
know
not
necessarily
included
in
the
priority
here,
so
we
can
kind
of
think
about
that.
So,
there's
anything!
A
That's
on
people's
mind!
That's
missing
from
this
release
board
from
the
roadmap.
What's
what's
on
people's
minds.
B
Hey
Jared,
hey
so
I'm
I'm
going
to
be
able
to
pick
up
the
the
Sig
store
integration.
Again,
there
was
a
about
a
a
couple
of
bye
weeks
there,
while
I
had
some
other
things
on
my
plate,
but
I
I,
I,
I
I'm,
not
necessarily
I'm,
not
necessarily
fully
understanding
whether
or
not
we
need
to
increase
the
scope
of
of
the
work
that
I
had
done
there.
Dan
has
given
me
feedback
I'm,
going
to
start
to
pick
away
at
that
feedback.
B
If
the
current
implementation,
with
the
comments
that
he
he
has
given
me
is
sufficient,
I
could
see
that
Landing
in
1.12,
because
I'm
probably
going
to
polish
it
up
over
the
next
week.
So
it's
open
for
discussion,
whether
or
not
it
makes
sense
for
112
or
or
Beyond.
C
I
definitely
love
for
it
to
be
in
for
1.12
and
I'm
happy
to
do
some
like
synchronous
meetings,
that
sort
of
thing,
if
you
want,
along
with
you,
know
anyone
else,
who's
interested
in
that
functionality.
B
There's
some
open
design
questions
but
again
like
without
increasing
the
scope
of
what
we've
already
spoken
about.
I
feel
comfortable
with
the
body
of
work.
B
The
the
the
the
last
pull
request
that
I
had
put
in
that
you
actually
commented
on
Dan
does
include
things
like
keyless
and
the
ability
to
wire
up
multiple
different
static
keys.
So
I
believe
that
most
folks
design
issues
are
Incorporated,
but
we
can
revisit
the
one
pager
and
expand
upon
it
for
further
iteration
I.
B
Just
think
that
what
the
the
what
the
the
initial
stab
was
intended
to
be
was
to
allow,
for
my
use
case
primarily,
which
is
to
you
know,
create
known
good,
builds
of
configuration
and
provider
packages
for
validation
that
they
were
created
by
Autodesk
employees
and
and
that's
kind
of
like
the
scope
that
I'm
targeting
right
now.
C
Yeah
definitely
encourage
keeping
it
as
script
as
possible.
Right
like
the
smaller,
the
implementation,
the
easier
it's
going
to
be
to
to
ensure
it
gets
into
1.12.
C
So
if
there's
parts
we
want
to
shave
away
from
it,
we
also,
you
know,
I
think
as
discussed
on
the
the
pr
a
little
bit
and
in
the
design
like
putting
this
behind
the
alpha
flag,
de-risks
it
a
little
bit.
So
we
have
some
leeway
there.
We
can
work
with
that's.
A
Yeah-
and
you
know
that
that's
it's
pretty
common
as
well
to
Jesse
and
not
unreasonable.
You
know
to
have
a
scoped
release
initially
with
the
functionality
and
then
get
feedback
from
you
know,
other
people's
use
cases-
and
you
know
if
it's
if
it's
meeting
what
their
needs
are
or
you
know
is
it
have
some
oversight
or
you
know
miscaps
and
stuff
like
that,
so
that's
totally
reasonable
to
scope
it
to
what's
appropriate
and
get
it
into
Vietnam,
V
1.12.
That
sounds
good
to
me.
A
D
A
B
A
That
sounds
awesome.
Jesse
then
Valerie
had
a
question
about
observe
only
resources
in
1.12,
and
so
you
know
the
we
have
a
bit
of
a
status
update.
That's
coming
later
on
that
one,
the
design
is,
you
know,
Nick
and
Hassan
are
meeting
synchronously
today
to
try
to
finalize
on
some
lingering
outstanding
discussions
on
the
design
there,
as
the
design
is
currently
proposed.
The
scope
of
the
implementation
is
not
massive,
so
I
think
that
it's
something
that
we're
targeting.
A
That
is
a
priority
and
we're
targeting
to
be
able
to
include
in
1.12,
but
I
think
there
is
still
some
outstanding
conversation
there
about.
What
exactly
would
be
the
scope
of
of
the
final
implementation,
because
we
do
want
to
get
it
right.
A
So
there's
there's
a
bit
more
to
figure
out
there
and
if
Hassan
wants
to
add
more,
then
that's
that's
appropriate
too
and
Jason.
Do
you
have
a
question.
E
Yeah
I
was
wondering
if
that's
based
currently
mostly
on
what
Nick's
approach
have
been
to
that
as
well,
because
we
had
discussed
that
before
around
or
I.
Guess
we
don't
know
I,
guess
we'll
see
when
they
get
done.
That
conversation
I'm
curious
to
hear
the
output
of
that
as
to
what
the
how
that
implementation
goes
forward,
because
it
was
kind
of
predicated
on
composition,
functions
right
or
no
aren't
they
kind
of
tied
together.
A
At
least
with
the
way
that
I
was
reading
the
implementation,
the
design
as
proposed
right
now,
I,
don't
think
it's
predicated
on
composition,
functions
Hassan!
If
you
want
to
add
more
about
that,
that
could
be
useful.
F
For
the
functionality
and
the
design
doc
aims
to
cover
most
of
them
at.
B
Least
like
whenever
it's
it
is,
it
makes
sense,
but.
F
There
are
a
couple
of
use
cases,
especially
to
name
it
like
filtering
and
querying
part,
which
is
another
functionality
available
in
the
telephone
data
sources.
We
are
kind
of
thinking
that
those
functionality
will
be
better
fitted
to
the
composition
functions,
but
overall
The
observed
only
design
function
of
the
observe
only
manage
these
sources.
Functionality
will
be
implemented
as
part
of
the
proposed
design.
F
A
And
Bob
did
you
have
something
to
add
to
that?
You
came
off
mute,
oh
sorry!
Well,
while
I
have
you
Bob
I
think
there
was.
There
was
a
couple
of
issues
that
you
were
thinking
about,
tackling
in
1.12
or
in
the
near-term
time
frame
as
well.
I
cannot,
for
the
life
of
me,
remember
what
it
was
something
about
being
able
to
have
control
over
the
connection,
detail,
information
or
something
was
that
what
it
was.
What
was
it
Bob.
G
So
there's
one
for
the
composite
update,
basically
having
a
default
composite
update.
Sorry,
composition,
update
policy
to
go
along
with
composition
revisions,
so
that
you
can
specify
in
the
xrd
whether
you
want
manual
or
automatic
composition,
update
policy,
because
right
now,
the
way
it
is
right
now.
You
know
it
defaults
to
automatic,
and
you
have
to
put
in
the
claim
whether
you
want
it
to
be
manual
or
you
know
or
automatic.
If
you
want
it
to
be
manual,
but
even
then
it
doesn't
Cascade
down
through
a
nested
composition.
G
So
you
then
have
to
go
into
all
your
compositions
and
set
it
there
as
well
so
having
it
on.
The
xrd
I
think
will
be
a
big
help,
so
that
was
one
and
then
the
other
one
was
the
composite
delete
policy.
Basically
the
same
thing
today
you
have
to
specify
in
the
claim
that
you
want
the
composite
delete
policy
to
be
foreground.
Otherwise,
it's
going
to
default
to
background.
G
A
There
you
go
yeah
and
it's
these
two
issues
right
here,
right
Bob!
That's
it
awesome!
So
did
you?
How
do
you
feel
then
about
us
going
ahead
and
putting
that
in
the
1.12
Milestone
as
well
since
you're
planning
on
working
on
it
soon
and
then
you
know
as
the
Milestone
unfolds
Milestone
unfolds,
then
we
can.
You
know
reevaluate
if
it's
something
to
include
or
not,
but
do
you
you
want
to
add
it
in
right
now,
yeah.
G
I
think
it's
fine
to
put
it
in
I'd
really
like
to
get
to
it.
The
only
thing
is:
there's
some
magic
happening
in
the
whole
xrd
processing
stuff,
that
I
don't
fully
understand
and
so
I
may
need
some
guidance
or
hand
holding
in
terms
of
exactly
how
what
the
implementation
should
look
like.
A
Yep,
that's
still
a
reasonable
Bob
and
I
have
a
fair
amount
of
confidence
that
you'll
be
able
to.
You
know
get
get
to
the
details
that
you
you
want
to
feel
to
feel
comfortable
with
it,
so
I
will
go
ahead
and
update
those
two
issues
to
include
those
in
the
1.12
Milestone
and
Dan.
You
have
your
hand
up.
That's
very,
very
polite
of
you,
sir.
C
A
Yeah
go
for
it
I'm
on
the
other
screen
here.
Updating
Bob's
issues
here.
C
Cool
okay,
so
the
I
just
added
two
issues
into
the
1.12:
one
of
them
is
revision,
resource
ownership
transition.
So
that's
for
folks
who
have
upgraded
providers
before
and
seeing
that,
like
you
can't,
you
can't
upgrade
this
provider
because
you
know
previous
revision
owns
this
resource
and
it
can
establish
control.
This
is
not
a
blocking
thing,
but
essentially
what
happens
there?
Is
the
previous
revision
gets
deleted
before
it's
able
to
transition
from
controller
to
owner
of
a
crd
or
xrd
or
composition?
C
So
we
should
be
able
to
include
that
in
the
deletion
before
we
remove
the
finalizer.
So
that's
a
small
one.
The
larger
one
is
one.
That's
been
around
for
quite
a
long
time
and
I
want
to
bring
this
to
attention
early
on
in
this
cycle
and
it's
the
provider
runtime
interface
issue.
C
So
for
folks
who
saw
on
slacker
in
the
release
notes
at
the
end
of
1.11,
we
made
the
decision
to
deprecate
a
controller
config
which
sounds
really
scary,
because
a
lot
of
people
depend
on
it.
It
is
an
alpha
resource,
but
it
was
introduced
before
our
Fisher
official
feature
life
cycle
policy
if
it
had
been
introduced.
After
that,
it
would
be
off
by
default
right,
so
you
wouldn't
be
able
to
use
controller
config,
but
because
it
wasn't
right
it,
it
has
been
on
and
people
have
been
using
it.
C
So,
despite
it
being
an
alpha
resource
where
the
contract
is,
we
can
drop
it
or
change
it
at
any
time.
We
obviously
don't
want
to
do
that.
If
the
community
is
depending
on
something
which
we
have
pretty
strong
evidence
that
they
are
so
we've
deprecated
it.
That
is
a
notice
only.
There
is
no
change
in
functionality.
What
we'd
like
to
do,
though,
is
move
toward
words,
offering
potentially
multiple
implementations
likely
the
main
one
it'll
be
sort
of
like
the
composition
function,
Runner,
where
we
have
a
default
that
we
deploy.
C
That
will
look
a
lot
like
the
existing
functionality
for
providers
where
we
just
create
a
deployment
free
trivision,
so
that'll
probably
be
the
default,
but
we
would
like
to
give
folks
some
more
functionality
there,
because
we've
had
people
continually
wanting
to
expand,
control
or
config
and
be
able
to
do
interesting.
Things
such
as
like
irsa
or
you
know,
various
different
runtimes
for
providers
recently.
This
has
expanded
scope.
C
A
little
bit
potentially
with
like
external
secret
stores,
and
some
of
that
you
can
see
Hassan-
has
a
good
comment
on
here
kind
of
talking
about
how
something
like
this
may
be
useful
in
that
case
as
well.
C
So
this
may
expand
to
more
of
like
a
general
runtime
interface
that
we
use
for
a
couple
different
features,
but
this
is
something
that
we
would
at
least
like
to
have
a
design
in
for
and
if
possible,
an
alpha
implementation,
which
would
mean
that
you
could
continue
to
use
the
controller
config
exactly
as
it
is,
but
we
might
also
you
know,
have
a
feature
flagged
version
available
where
you
could
provide
alternative
implementations,
so
no
design
is
available.
C
Now
there
is
a
lot
of
issue
or
a
lot
of
context
in
this
issue
for
folks
to
go
to
kind
of
read
up
on
the
motivation.
But
if
you
have
early
comments
even
before
the
design
doc
is
out
there,
please
feel
free
to
go
ahead
and
drop
comments
on
there
and
we
can
start
conversation
and
if
needed,
we
can
develop
kind
of
like
a
Sig
Channel
or
something
like
that.
C
Keep
that
conversation
going
cool.
That's
all
for
me:
Max
did
you
have
a
question
related.
H
To
what
Jesus
said
so
when
you
said
different
provider
runtimes,
you
refer
to
different
kubernetes
configs,
effectively
being
used
to
deploy
them.
C
Or
yeah,
so
it
would
be
basically
moving
the
logic
for
how
a
provider,
or
maybe
a
plugable
Secret
store
or
something
like
that
gets
run.
It
could
be
as
simple
as
there's
multiple
different
implementations
that
all
create
deployments,
but
allow
you
to
configure
different
things
could
be
that
some
create
deployments
some
create
pods
could
be
that
some
use,
AWS
Lambda
functions
to
run
providers
somehow
or
you
know,
some
external
container
service.
C
It's
really
just
saying:
hey
we're
not
going
to
cut
off
people
from
the
functionality
they
want,
and
we're
also
not
going
to
be
as
concerned
about
that
in
core
cross
plane,
where
we
want
to
make
the
happy
path
easy,
but
give
you
those
Escape
hatches
if
you
need
them
awesome.
Thank.
A
You
cool
it's
so
Dan.
Do
you?
Do
you
already
have
some
ideas
about
scope
or
phases,
etc?
For
this,
like?
Is
this
something
that,
oh
you
know
from
the
outside?
It
looks
massive
right.
Is
this
something
that
you
know
in
your
opinion
is
like?
Oh
yeah.
This
is
an
easy,
easy
lift
for
1.12.
We
could
slide
it
on
in
there
or
is
it
like
we'll?
Maybe
we'll
have
the
first
person
of
it
1.12
and
then
more
comes
later
on
or
what
is
your
thinking?
You
know
very.
C
So
there
are
a
few
layers
of
hidden
complexity
in
this
effort,
so
a
good
example.
Well,
actually,
let's
just
say
if
if
we
just
wanted
to
run
containers,
it
might
not
be
that
hard
because
you
can
think
of
if
we
took
the
existing
functionality
right
now,
where
there's
a
cross-plane
controller,
config
API
and
we
instead
said
there's
a
default
cross-plane
implementation
of
the
runtime
interface
and
it
brings
a
controller
config
API.
C
Then
you
could
configure
that
you
could
still
create
your
controller
configs,
essentially
really,
and
all
that
would
be
needed
would
be
for
cross
plane
to
basically
say,
hey,
run
this
container
and
we
might
need
to
say
if
this
is
for
various
interfaces
right.
This
is
a
plugable
Secret
Story.
This
is
a
provider
and
then
the
implementation
would
decide.
Okay,
these
are
all
the
different
ways
I
can
be
configured
to
deploy
the
provider.
C
So
I
think
there
is
a
relatively
straightforward
implementation
that
basically
just
takes
what
we
do
today
and
moves
the
config
kind
of
to
the
implementation
rather
than
core
cross
plane
areas
where
you
start
to
uncover
some
more
hidden.
Complexity.
Are
things
like
our
back
where
you
know
we
create
providers
and
they
install
a
bunch
of
resources?
And
then
we
say:
hey
this
provider
needs
access
to
these
resources,
it
installs
and
our
back
manager
does
that
you
know
right
now.
C
People
sometimes
deploy
without
the
hardback
manager,
but
we
need
to
think
about
what
that
happy
path
looks
like
and
whether
you
know
if
you're
running
a
different
scenarios.
That
means
you
need
more
or
less
information
about
the
provider,
because
the
implementation
of
the
interface
may
not
be
able
to
talk
to
you
know
the
provider
object
or
something
like
that
to
request
more
R
back.
So
there's
a
lot
of
considerations
about
how
you
give
access
to
things
that
will
need
to
be
rolled
into
this.
A
Got
it
Daniel
that
makes
sense
thanks
for
explaining
it
that
way,
all
right,
so
that
also
then
Dan
I
believe
you
added
that
then
to
1.12,
as
at
least
the
preliminary.
You
know,
investigations
and
design,
and
things
like
that.
So
those
issues
are
on
the
board
as
well
and
in
the
backlog,
column,
and
you
know,
feel
free
to
follow
up
on
those
and
and
move
them
through
the
board.
As
you
make
progress
on
them,
then.
A
D
A
There
any
other,
ongoing
efforts
from
folks,
you
know
making
contributions,
maybe
Max,
maybe
you've
got
something
that
you're
picking
up
or
you're
working
on
right
now
that
you
wanted
to
also
include
in
the
board,
because
we
got
one,
we
got
some
from
Jesse.
We
got
some
from
Bob
any
other
contributions
out
there
that
we
want
to
include
on
the
board.
It's
for
official
tracking.
H
I'm
not
from
my
side
today,
I
actually
so
I
just
came
here
to
chime
in
and
see
how
you
plan,
because,
like
I
currently
faced
a
problem
that
we
have
deployment
scenarios
of
cross-plane
where
we,
where
we
have
maybe
multiple
API
servers
and
I,
think
like
what
what
what
we
just
heard
might
solve
a
couple
of
those
challenges.
So
we'll
be
happy
to
contribute
from
sap
side
here
as
well.
H
Also
that
I
can
say
we
have
a
implementation
of
the
usage
tracking
in
a
couple
of
our
providers
running
so
we'd
be
happy
to
contribute
with
the
roadblocks
we
faced
and
yeah.
That's
that's
just
what
I
wanted
to
tell
you
guys.
A
Awesome
that
sounds
good,
then
yeah,
thanks
for
everything
for
sharing
that
all
right,
so
yeah.
So
then,
so
this
is,
you
know
very
beginning
of
of
the
Milestone
here,
and
so
you
know
we'll
continue
taking
feedback
and
you
can
work
on
some
things,
asynchronously
as
well
on
slack
and
GitHub,
because
you
know
everyone
who's
here
at
the
community
meeting.
So
we'll
continue
to
take
opinions
and
feedback
on
the
GitHub
issues
and
on
slack
and
we'll
keep
fleshing
out
this
1.12
Milestone,
but
I'm.
A
Definitely
looking
forward
to
Rolling
off
the
momentum
from
1.12
sorry
1.11
into
another
awesome
release
with
1.12,
so
keep
it
up,
everybody
all
right,
so
that
is
Milestone
planning,
stuff,
I
think
so,
let's
keep
on
rolling,
so
provider
releases
and
other
other
releases.
There's
a
new,
a
fresh
round
of
outbound's
official
providers
for
AWS,
gcp
and
Azure
that
went
out
I
think
just
a
couple
days
ago.
So
those
continue
to
roll
out
on
a
regular
basis.
A
Hart
here
today,
I
don't
think
I
saw
or
heard
him
yet
so
maybe
not,
but
Christopher
made
a
new
release
of
this
competition
generator
tool.
So
that's
that
was
just
last
week
and
some
some
new
fixes
and
some
new
functionality
in
there
that
folks
can
check
out
linked
here
in
the
dock
and
then
a
new
GitHub
provider
as
well
was
was
published.
A
Did
that
is
that
an
update
that
went
to
the
marketplace
or
is
that
the
first
time
it
got
into
the
marketplace?
It
was
the
first
time
oh
sweet
nice,
so
that
is
also
a
oh
man.
That's
fantastic!
So
that's
awesome
to
see
that
in
there
as
well-
and
hopefully
we
get
some
feedback
on
that
one
and
keep
on
making
it
more
useful
for
folks.
A
Everyone
is
welcome
to
if
there's
other
recent
provider
releases
or
advancements.
You
know
you
can
drop
them
here
in
the
agenda
doc
or
talk
about
them.
But
you
know
it's
an
open
space
in
the
agenda.care
for
for
recent
releases
from
everybody
all
right.
So,
let's
move
keep
on
moving
down
through
the
agenda,
then
we're
about
halfway
through
the
hour.
So
now
so
for
some
vendor
updates.
So
you
know:
upbound
Engineers
are
working
on
a
few
different
things.
We
already
talked
about,
observe
only
resources,
so
I
think
this
one.
A
Nothing
else
to
share
there.
Esky
I,
don't
think
he's
here
today,
either
I,
don't
think
so,
but
she
has
got
a
first
PR
now
open
about
having
pluggable
secret
stores.
So
this
is
in
cross-plane
runtime.
A
This
is
the
first
PR
of
I
think
a
sequence
of
a
at
least
a
couple,
but
the
implementation
on
that
has
started
and
will
be
allowed,
be
able
to
open
up
the
doors
for
other
Secret
store,
implementations
or
supports
such
as
like
AWS
secret
manager,
and
you
know
all
the
other,
like
the
other
cloud
provider,
ones
and
and
whatnot.
So
that's
gonna
be
really
helpful.
A
I
think
it's
beyond
the
initial
support
that
we
had
for
Vault,
so
that
looking
forward
to
that
more
of
that
coming
and
then
there
had
been
progress
on
the
further
further
validation
of
compositions
where
via
webhook.
So,
instead
of
you
know
your
your
opposition
being
submitted
and
then
later
on,
down
Downstream
and
not
working
because
there
was
an
issue
with
it.
A
This
would
be
upfront
validated
and
you
know
rejected
if
it's,
if
it's
in
you
know
invalid
shifting
that
left
Philippe
has
been
working
on
that
and
has
some
proposals
that
he's
been
sharing
with
the
team
and
we'll
see
more
of
that
as
the
1.12
release
unfolds
so
I
was
I
was
covering
this
because
I
think
John
was
not
able
to
make
it
today,
but
that's
everything
that
I
believe
currently
right
now
the
outbound
Engineers
are
are
focusing
on
that
as
of
the
last
week
or
so
all
right.
A
So
a
couple
cool
things
here
in
like
amongst
the
ecosystem,
this
particular
one
I
thought
was
quite
interesting
because
it
was
a
fairly
Deep
dive,
I
think
on
how
to
get
some
interesting
Insight
in
metrics
into
health
of
cosplaying
in
the
control
plane
and
all
the
resources.
That's
managing
so
I
think
that's
definitely
worth
the
read
from
everybody.
It
was
very
interesting,
so
the
link
is
here
in
the
agenda
doc,
and
there
are
some
other
issues.
Things
here.
A
I
think
I
think
this
one,
this
blog
post
here
is
it's
a
repost
of
one
that
I
had
done
for
the
new
stack
at
the
end
of
last
year.
So
I
don't
think
that's
super
new,
but
is
interesting,
at
least
for
folks
getting
first
getting
into
cross
plane
and
then
also
this
is
a
webinar
that
I
think
Victor
had
done
with
the
code
fresh
people
just
last
week.
A
I
may
need
some
help
from
someone
to
figure
out
how
to
access
it
because
they
did
it
on
Twitch
and
twitch.
Just
I,
don't
understand
the
point
of
twitch
after
you
live
stream,
something
because
it
seems
like
nothing
is
ever
like
kept
for
posterity,
so
I
don't
know
where
it
lives.
Maybe
it's
somewhere
else.
If
somebody
does
find
a
permanent
link,
please
add
it
to
the
agenda
doc
because
I
don't
know
where
it
is.
C
Yeah,
that's
truly
confounding
to
me
the
twin
Toronto,
but
apparently
it's
quite
popular
I
know
you
can
save
Clips,
but
I.
Don't
know
why
people
don't
just
use
YouTube
but
anyway.
A
A
Okay,
oh
man,
okay,
so
we
talked
about
this
one
last
time
and
I
think
we're
getting
very
close
to
wrapping
this
up.
Phillip
has
proposed
a
security
vulnerability
disclosure
policy
for
the
cross-plane
project.
This
is
important
as
we
mature
the
project
to
continue
to
invest
in
our
security
posture.
A
So
I
think
that
all
the
feedback
has
been
addressed
by
Philippe,
and
then
we
got
some
some
Security
Experts
that
had
weighed
in
on
it
as
well.
So
Philippe
there's
no
more
outstanding
feedback
on
that,
one
like
from
Adam
as
well
too
right
for
beta
Logics,
no.
G
I
think
not
it's!
It's
ready
for
review.
A
Awesome
so
great,
so
hopefully
we
can
get
that
merged
in
this
week
and
and
and
roll
out
that
policy
for
any
upcoming
security
vulnerabilities
that
that
are
disclosed
to
us.
That
will
be
that
will
come
in
very
much
very
much
handy
that'll
come
in
handy
for
us,
because
we
will
be
undertaking
a
full
security
audit
via
the
cncf.
A
You
know
they
they
are
helping
out.
They
will
be
helping
out
with
third
party
security
vendors,
who
will
do
a
full
audit
of
the
project
in
in
your
vulnerabilities.
We
find
there
it'll
be
nice
to
have
that
disclosure
process
in
place
to
roll
out
with
those,
in
addition
to
anything
that
is
or
was
found
with
the
fuzz
testing
effort
as
well.
That's
getting
wrapped
up
so
Philippe,
thanks
for
taking
the
initiative
on
that.
A
One
man
and
I
appreciate
your
efforts
in
contributing
that
so
kubecon
updates
so
kubecon's
a
couple
months
away
from
us
in
Amsterdam
in
the
cfp
acceptances
were
announced
this
week.
So
good
news
is
that
a
maintainer
track
session
was
accepted.
I,
don't
know
why
they
wouldn't
have
us.
We
are
an
awesome
project,
so
Christopher,
Harr
and
I
will
be
teaming
up
to
present
on
Cross
plain
in
Amsterdam.
A
Also,
really
good
news
is
that
we
applied
to
participate
in
the
contrib
Fest
as
well,
and
that
was
also
accepted,
so
we
are
going
to
be
getting
in
a
room
together
and
cross-plane
contributors
and
members
of
the
community
can
we
can
work
through
some
synchronous
things
together?
We
can
talk
about.
You
know
designs
that
are
out
at
that
time
and
I'll
also
be
running
a
new
contributor
enablement
session
as
well.
So
folks
that
are
kind
of
sitting
on
the
sidelines
and
interested
in
getting
into
contributing
to
cross-plane.
A
We
could
do
some
Hands-On
stuff
together,
where
we
get
our
environment
development
environment
set
up.
We
start
learning
about.
You
know
the
different
parts
of
the
code
base
and
you
know
kind
of
get
some
more
folks
feeling
good
to
be
writing
code
and
contributing
PR's
to
cross-plane,
so
I'm
super
excited
about
that.
I
will
need
some
support
from
that.
You
know
if
to
to
help
out,
like
you
know,
Hands-On
with
the
labs
or
maybe
presenting
some
materials
as
well
running
a
small
breakout
session,
something
like
that.
A
We
have
90
minutes
to
do
some
cool
work
together.
So
if
folks
want
to
participate
and
support
that
effort
as
well,
I
would
love
that
Dan
I'm,
probably
looking
at
you
already
of
somebody
that
would
maybe
be
willing
to
help
out
with
that
and
support
that
two
thumbs
up:
okay,
not
even
just
one
so
Dan's
gonna-
be
involved
in
that
as
well,
so
yeah.
A
So
anybody
who
wants
to
participate
in
that
either
on
the
you
know
attending
side,
and
you
know
kind
of
you
know
being
there
and
learning
and
and
that
kind
of
thing
that's
super
super-
welcome
I'm,
really
going
to
appreciate
folks
being
there
for
that,
and
then
also
on
the
teaching
side
as
well,
so
folks
that
can
help
and
support
on
that
side
too.
A
So
anybody
who
wants
to
participate
just
ping
me
as
I'm
planning
this
thing
out
and
we'll
get
it
all
figured
out
and
then
the
other
question
was
trying
to
figure
out
what
other
talks
people
got
accepted.
I
know:
Jesse
got
your
talk,
got
accepted
so
you're
on
the
on
the
schedule
and
on
the
agenda
there.
So
congratulations
on
that.
One
Jesse
good
job
on
that
and
they're
definitely
excited
to
see
that
one
too
anybody
else
Dan.
You
got
to
talk
accepted
right.
Who
else
got
accepted.
C
I
did
it
will
it'll
actually
yeah
I,
don't
have
some
cross
Pine
bits
in
there
so.
C
A
Yeah
you've
been
you've,
been
yeah
I,
don't
know
why
you
kept
getting
that
slot
Dan.
But
when
is
yours,
is
it
what
day.
A
Cool
so
then
other
sessions
that
are
mentioning
cross-plane
there
looks
like
there's
one
from
digitalocean
looks
like
there's
one
from
code
fresh.
We
know
about
Jesse's
session
as
well,
there's
one
from
TV2
Denmark,
which
I'm
super
interested
in
hearing
more
about
that
what
they're
talking
about
and
then
and
then
and
then
Christopher
and
I,
are
presenting
on
the
maintainer
track
as
well.
That
looks
like
that's
the
last
session
of
the
con
God
gosh
darn
it
okay.
C
Last
time
y'all
were
last
session
in
Spain,
though
remember
it
was
packed.
Sorry.
A
That
was
that
was
in
Valencia
yeah
people
were
able
to
show
up,
okay,
we'll
figure
that
out,
and
then
it
looks
like
a
trip
best
here
is
on
Wednesday,
so
early
in
the
week
there,
so
that
that
should
be
cool
there.
So
yeah,
that's
the
schedule
that
we
see
so
far
and
congratulations
to
folks
who
got
their
talks
accepted
and
anybody
else
who
got
a
talk
except
did
feel
free
to
share
that
with
us
right
here
as
well.
A
All
right
keep
on
cruising
keep
on
cruising
so
very
recently
I.
You
know
this
is
insert
what
did
I
just
do.
A
Let
me
move
this
out
of
the
way
Zoom
yeah
so
in
service
of
continuing
to
mature
the
project
and
and
work
towards
a
graduation
with
the
cncf
we
needed
to
have
a
better
sense
of
adopters
of
the
project,
so
it's
fairly
standard
process
to
have
an
adopters.md
file
in
the
in
the
main
repository.
So
we've
created
that
and
we've
given
a
couple
different
options
for
folks
to
be
able
to
add
their
usage
as
well.
To
the
to
this
document.
A
Here
we
have
a
number
of
PR's
open
for
people
adding
into
it
so
we're
kind
of
working
through
those
and
going
through
those
in
order
that
they
were
that
they
were
open,
so
we're
kind
of
respecting
first
in
first
out
sort
of
thing,
but
if,
if
anybody
wants
to
continue
adding
their
your
added
at
their
usage
as
well
like
it
is
very
encouraged
and
very
open,
and
it
does
help
continue
to
mature
the
project
and
and
grow
our
grow.
Our
base
there
so
very
grateful
to
everyone.
A
Who's
already
contributed
to
that
and
looking
forward
for
more,
let's
see
if
I
see
some
mentioned
in
the
chat
there
too
so
sounds
good
to
me.
A
A
So
there's
three
different
options
and
take
it
back
all
right,
Pete,
our
wonderful
documentation,
engineer,
I,
don't
think
is
able
to
make
it
today,
but
he
did
want
me
to
bring
up
this
particular
topic
here
where
Pete
is
going
to
is
considering
adding
in
linting
to
the
docs,
which
will
enforce
some
Style
Guidelines,
and
you
know
various
other
ways
of
keeping
the
docs
consistent.
So
Pete
wanted
to
just
put
this
on
people's
Radars.
A
So
if
you
have
any
questions
or
comments
about
it,
please
do
go
ahead
and
probably
just
comment
on
this
issue.
I
think
so
Pete
can
can
handle
it
directly.
You
know
I,
don't
I'm
not
super
up
to
date
on
unveil
and
how
it
works.
So
I'm
not
a
great
resource
for
that,
but
Pete
definitely
is
and
and
yeah
feel
free
to.
D
A
On
this
issue,
if
you,
if
you
want
to
know
more
about
how
we'll
be
implementing
this
linting
in
the
docs
repo.
A
All
right
and
let's
see
what
else,
what
else
so
a
really
awesome
Tool
was
was
released
and
there
was
a
talk
about
it.
So
there's
a
linting
tool
for
cross
plane
itself.
Now
is
anybody
in
the
call
who
is
contributing
to
this?
That
wants
to
talk
about
it?
So
I
don't
spill
your
thunder.
A
I
guess
maybe
not
got
lots
of
people,
but
not
one
of
the
contributors
to
this
so
yeah.
So
I
think
this
was
driven
by
some
of
the
of
Yan's
team
and
some
of
the
Accenture
folks
so
yeah.
So
this
is
really
useful
to
be
able
to
kind
of
also
in
the
same
vein
of
Shifting
left
in
verifying.
You
know
your
your
platform,
definitions,
your
cross,
your
composition,
definitions
and
all
that
sort
of
stuff,
so
really
really
useful
tool.
A
Here,
that's
I
think
it's
in
its
early
stages
and
there's
more
to
come.
There's
a
bit
of
a
road
map
to
find
and
such
so
it
has
been
donated
to
the
crosswind
contribute
organization.
So
there's
a
neutral
home
to
collaborate
around
it
right
now.
So
definitely
looking
forward
to
more
interesting
stuff
coming
out
of
this
and
hearing
people's
success
with
it.
So
thank
you.
A
And
there
also
is
a
talk
from
the
folks
there
too,
that
was
at
fosdem
last
week
in
Brussels
and
I
wish
I'd
been
able
to
make
it
there,
but
that
would
have
been
really
cool
to
see
in
this
link.
Here
will
take
you
to
the
talk,
I
believe
the
recording
is
posted
there
as
well.
So
you
can
watch
the
full
talk.
Also,
you
get
more
context.
A
Okay,
last
last
two
items
here
is:
there
was
a
call
out
for
just
getting
some
feedback
from
folks
that
may
have
already
been
using
the
composition,
validation
web
hook.
It
has
been
it's
I,
don't
know.
Maybe
it's
in
a
couple
releases
that
it
was
that
it's
been
available,
but
it
is
turned
off
by
default,
as
we
are
doing
more
effort
to
invest
in
the
composition,
validation
as
a
whole.
A
We
will
turn
this
on
by
default,
and
so
we
just
wanted
to
get
some
feedback
from
folks
if
anybody's
already
been
using
it
and
it's
working
for
them,
it's
not
working
for
them.
If
there's
any
feedback
from
folks
that
already
have
experience
with.
It
then
feel
free
to
comment
within
this
issue
here.
A
Okay
and
let's
see,
looks
like
there
is
another
agenda
item
here
about
RDS
day
two
stuff
remember
was
this:
was
this
you
did
you
add
this
one
buddy.
D
That
yeah
sure
so
see
I
am
writing
an
implementation
guidance
around
how
well
like
considerations
that
you
should
have
when
you,
when
you
are
managing
RDS
instances
and
clusters
when
you're
using
crossbank
I
put
most
of
my
thoughts
in
that
document,
but
I'm
just
kind
of
looking
for
feedback
from
the
community.
If
you
have,
you
know,
experience
managing
RDS
instances
in
your
organization
and
if
you
have
you
know
some
time
to
review
it,
I
would
highly
highly
appreciate
any
feedback.
You
have.
A
Yeah
awesome:
we
saw
this
effort
when
we
looked
and
it
looked
really
really
cool
and
so
some
good
it's
generating
some
good
discussion
as
well
on
here
so
yeah.
This
will
be
a
really
good
resource,
I
think
for
the
community.
So
this
is
great
to
be
investing
in
this
man.
A
A
Worries
all
right
so
yeah
that
pretty
much
ends
it
here.
So
if
anybody
else
wanted
to
add
anything,
we
go
ahead.
Otherwise
we
can
wrap
it
up.
A
All
right
well
good
to
see
everybody
thanks
a
lot
for
all
the
effort
on
the
1.11
release,
and
you
know,
let's
cruise
on
into
1.12
and
congratulations
again
to
everybody
that
got
talks
accepted
at
cubecon.