►
From YouTube: 2022-09-22 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
A
The
oh
agenda
is
open
for
everybody
to
be
adding
things
or
suggesting
things
so
we'll
be
happy
to
get
into
any
topic.
You
all
want
to
look
at.
So,
let's
start
first
with
our
recent,
our
Milestone
checkup.
So
first
of
all,
we
did
a
series
of
patch
releases.
It
looks
like
Dan
is
on
the
call
who
ran
those.
So,
let's,
let's
have
Dan,
give
us
an
update
so
on
the
specific
functionality
there.
B
Cool
thanks
Jared,
so
there
was
two
or
three
kind
of
like
big
bug:
fixes
I,
guess
it
depending
on
how
you
look
at
it,
but
the
the
three
that
kind
of
stuck
out
for
all
these
is
one.
We
needed
secret
deletion.
Permissions
on
the
crosswind
service
account
that
was
part
of
the
Secret
store
implementation.
So
that's
enabled
for
all
these
branches.
Another
one
was
something
contributed
by.
B
Let
me
see
if
I
can
actually
find
the
that
person's
name,
because
I
want
to
give
them
a
shout
out.
Royal
looks
like
that.
Does
retries
with
gits.
B
If
a
head
request
fails
when
checking
the
digest
of
packages
which
is
required
for
installation,
some
Registries
don't
support
getting
the
digest
via
head
request,
which
is
kind
of
like
a
legacy,
Docker
distribution
thing,
so
that's
updated
and
that
I
think
quay.io
or
however,
you
say
that
I,
don't
think
anyone
really
knows
is
the
the
key
registry
where
that
was
breaking
so
that
was
nice
to
get
in
and
then
the
last
one
here
fixes
a
race
condition
and
we're
moving
to
having
revisions
just
remove
themselves,
specifically
from
the
lock
in
a
dependency
situation,
and
that
avoids
the
case
where
they
were
previously
using
their
source.
B
So
it
would
look
and
say:
hey,
I'm,
cross-plane
provider,
AWS
and
I'll.
Just
remove
that
and
it
led
to
revisions
kind
of
fighting
over
the
lock
when
you're
installing
new
ones.
So
that
was
most
of
everything.
There
was
also
some
docs
fixes
that
you
can
see
here
in
the
release
notes
they
were
great
to
get
in
as
well.
A
Awesome
Dan
thanks
for
giving
us
the
update
some
of
the
details
about
those
fixes
and
thanks
of
course,
as
well
to
all
the
contributors
that
we're
putting
in
fixes
and
getting
improvements
in
as
well.
Everything
that
goes
into
this
series
of
patch
releases,
so
1.9.1,
1.8.2
and
1.7.3
obviously
will
also
be
included
in
the
upcoming
1.10
release.
A
So
speaking
of
1.10,
the
release
date
is
coming
up
just
under
a
month
from
now
and
just
before,
kubecon
in
Detroit,
so
October
18th
is
the
planned
release
date
there
along
our
normal
or
typical
Cadence,
and
nothing
has
changed
from
that.
A
So
there's
a
number
of
things
that
are
in
progress
and
going
on
in
the
in
the
1.10
release,
there's
a
whole
there's
a
fair
amount
of
activity
going
on
so
I
think
maybe
some
of
the
biggest
ones
to
highlight
I
think
that
have
you
know
that
have
a
lot
of
activity
going
on
right
now,
oh
I
can't
move
this
thing
yeah.
A
Okay,
one
is
that
Max
has
been
continuing
to
push
on
the
does
the
implementation
for
being
able
to
take
configuration,
information
from
the
environment
and
then
patch
it
into
your
compositions.
The
design
was
approved
and
finalized,
and
the
implementation
PR
is,
is
still
outstanding,
so
I
think
that
it
largely
is
in
good
shape,
but
I
think
a
reviewer
doing
a
full
pass
before
Nick
then
gives
a
final
approval,
as
it
I
think
is
where
we
stand
now.
So
I
am
definitely
wanting
to
get
that
into
1.10.
A
I
know.
A
number
of
people
are
looking
forward
to
that
functionality.
So
I
definitely
want
us
to
drive
to
get
that
in
for
1.10,
the
other
another
PR
or
area
of
focus.
That
has
a
lot
going
on.
A
lot
of
activity
right
now
is,
is
being
driven
by
Bob
and
then
Max
is
contributing
as
well.
I
believe
for
supporting
foreground,
cascading
deletion,
Bob
I
think
you're
on
the
call.
A
C
So
Nick
has
been
spending
some
time
on
this
on
the
subject.
I've
chatted
with
him
on
slack,
haven't,
haven't,
had
an
opportunity
to
talk
to
in
person
or
he
hasn't
needed
to
which
is
fine
too
I.
Guess
there's
some
there's
some
question
right
now
in
terms
of
what
the
solution
should
be.
C
I
think
this
topic
has
ended
up
being
much
larger
and
much
much
more
complex
in
terms
of
the
scope.
Then
initially,
you
know
initially
thought
from
some
perspective.
It's
it's
actually
fairly
simple,
but
from
another
from
another.
You
know
when
you,
when
you
kind
of
take
a
step
back
and
look
at
the
larger
picture,
you
start
asking
more
questions
so
I
mean
I.
C
C
Is
this
the
direction
we
want
to
go
and
I
think
you
know,
I
I
tend
to
try
to
look
at
things
from
as
simple
a
perspective
as
possible,
just
because
I
have
enough
complexity
in
my
life
and
so
I.
Try
to
drive
complexity
out
wherever
I
can
and
so
I'm.
C
Expectation
would
be
that
none
of
the
resources
associated
with
that
composite
would
go
anywhere
until
I
removed
that
finalizer
and
maybe
that's
overly
simplistic,
but
that's
kind
of
just
the
Viewpoint
that
I've
been
taking
and
so
Nick's
kind
of
you
know.
C
Looking
at
the
situation
and
and
trying
to
understand
all
the
different
perspectives
he's
been
looking
at
a
feature,
a
proposed
feature
called
weens,
which
is
kind
of
similar
but
kind
of
different,
and
so
there's
some
discussion
around
that
I'm,
not
sure
this
is
going
to
make
1.10
it's
going
to
kill
me
if
it
doesn't
make
1.10,
because
we
really
really
really
need
this
capability
in
terms
of
resource
dependency
management
and
not
not
orphaning
resources.
C
But
you
know
I,
don't
I
want
I,
want
the
right
solution.
I
don't
want
to
push
for
something.
That's
not
you
know,
that's
not
the
right
solution,
so
I'm
happy
to
work
with
Nick
and
whoever
else
you
know
to
drive
this
to
whatever
the
correct
solution
is.
A
Yeah.
Thank
you
for
that
ongoing
effort
Bob
to
drive
to
a
a
you
know,
high
quality.
You
know
thorough
and
reliable
solution
for
what
is
not
a
trivial
scenario
at
all,
especially
as
you
get
into
the
depths
of
it.
So
thank
you
for
that.
Continued
effort.
A
Awesome
so
then,
oh
and
then
Bob
is
there
one
thing
that
I
was
getting
a
little
confused.
In
my
mind
about
was
because
there
are
a
number
of
discussions
in
a
few
different
places.
There's
some
related
issues,
there's
maybe
a
couple
different
PRS.
Does
it
make
sense
from
within
this
PR
here
to
have
like
a
you
know,
a
related
issues
section
or,
like
you
know,
direct
links
to
all
the
related
PRS
for
it.
A
C
That
yeah,
that's
where
they
kind
of
like
yeah
there's,
no
things.
No,
that's
a
good
idea
and
I
mean
I.
They
all
do
reference
this
PR,
you
know
indirectly,
meaning
there
are
mentions
in
there,
but
I
think
tying
them
together
into
one
specific
section
that
says
you
know
here's
what
the
related
PRS
are.
C
You
know
and
I've
kind
of
I've
kind
of
tried
to
make
it
I
tried
to
make
it
small
pieces
right
so
that
because
I
I,
my
my
impression
was
that
if
I
try
to
tackle
the
entire
thing
at
once,
it's
just
so
complicated
that
it's
really
hard
to
explain
to
somebody
never
mind
you
know
actually
understanding
it.
C
So
you
know
there's
the
cross-plane
run
time
piece
like
you
mentioned,
that
has
two
major
functionalities
in
it.
One
is
just
setting
the
block
owner
deletion
field
on
the
controller
owner
references
and
then
the
other
one
is
having
the
reconciler.
C
Basically,
not
you
know
recue
when
it
when
it
sees
outside
finalizers
and
then
there's
a
cross
plane
equivalent
to
that
which
is
essentially
the
same
thing
on
the
composite
and
the
claim
reconcilers,
where
a
lot
of
the
complexity
comes
in
is
is
due
to
the
fact
that
the
composite
is
named
is
cluster
scoped
and
the
claim
is
not
so
there's
no
owner
reference
between
the
composite
and
the
claim
and
so
cross
plain
actually
manages
the
deletion
of
the
composite
when
the
claim
gets
deleted.
It's
like
I
said
this.
A
I
think
that
is
a
good
approach
there
to
do
things
in.
You
know
manageable
pieces,
so
it's
easier
to
understand
and
parse
and
really
like
anticipate
the
impact,
but
in
also
limiting
last
radius
from
potential
regressions
exactly.
C
A
B
A
Didn't
get
that
we
get
to
get
lab
wow
GitHub
does
a
good
job
of
you
know
like
linking
mentions,
but
there
are,
like
you
know
in
the
comment
stream,
so
you
kind
of
have
to
search
for
them
and
kind
of
consolidating
with
the
at
the
top
would
be
very
useful.
So
thanks
for
doing
that,
yep,
okay,
so
I
think
that's
most
everything
the
big
stuff
going
on
for
1.10.
Is
there
anything
else
that
folks
want
to
bring
up
to
discuss
in
the
context
of
the
upcoming
1.10
release,.
A
B
A
A
Okay,
so
then,
let's
move
on
to
the
provider
section
as
well
looks
like
there
is
an
upcoming
release.
I
think
32
is
not
out
yet
right.
This
is
the
tracking
issue
for
it
NASA
Christopher.
You
want
to
catch
us
up
on
the
upcoming
AWS.
D
Can
you
open
the
the
next
link,
I
added
because
yeah
the
release
at
the
moment
a
little
bit
back
because
of
this
issue?
There's
a
fix
for
S3
notifications.
The
problem
here
is
that
we
deprecate
notification,
API
Group
in
the
past
and
has
three
notification,
looks
only
to
the
notification
group
and
not
to
the
SNS.
So
the
new
introduce
group
and,
from
my
point
of
view,
it's
it
is
safe
to
introduce
such
changes,
but
I
want
to
have
one
more
maintainers
in
the
approval
phase.
D
It
will
not
break
anything
for
current
users
using
the
S3
notifications,
because
the
selectors
and
references
our
yeah
searching
for
notification.
Everything
is
in
place
for
there
for
the
notification
API.
If
you
change
this,
but
for
all
the
future
yeah
users
that
you
want
to
use
SNS
for
S3
buckets,
we
can
fix
this,
but
would
be
better
if
someone
else
can
have
a
look
on
it.
So
like
more
or
call
that
we
can,
you
know,
bring
it
in
because
of
the
deprecation
things
for
notification.
A
D
I
I,
so
we
we
found
the
same
on
our
side,
I
guess
two
weeks
ago,
and
there
was
also
one
thing
in
the
community
and
we
had
the
discussion.
I
guess
malabu
was
also
in
the
call
he
was
honored
in
the
in
the
discussion,
so
it
would
be
great
to
have
it
also
in
the
next
release,
so
it
would
be
cool
if
I
attacked,
Carl
and
more
I
guess
more
on
vacation.
A
He
just
got
back
like
a
a
day
or
two
ago,
so
he
is
okay,
unburying
himself
right
now,
but
starting
to
get
back
on
top
of
stuff.
Do
you
want
to
add
a
note
here
then
too
Christopher
that,
like
explicitly
that
this
is
blocking
the
release,
yeah.
D
A
D
I
will
I
will
let
this,
and
if
you
have
problems
with
this,
we
can
cut
the
release.
Otherwise
it
would
be
great
to
bring
it.
D
A
E
Yeah
so
I
saw
the
last
release
on
Broadway
gcp.
It
was
in
March
and
there
was
some
commits
going
on
there
and
I
was
trying
to
to
have
in
the
release
and
there's
five
PR's
open
in
the
in
the
repository
and
I
am
reviewing
two
of
them
because
other
three
I
opened
so
I
can't
like
review
myself.
So
I
am
asking
for
for
a
review
for
anyone
that
can
help
me
and
then
we
when
I,
merge
these
five
PRS.
We
can
release
the
32
release.
A
Awesome
Gabriel
thanks
for
bringing
that
up
and
and
taking
an
inventory
on
the
PRS
that
are
that
are
outstanding
there.
Let
me,
let
me
try
to
Ping
a
couple
folks
of
their
maintainers
I.
Think
there's
a
couple
that
are
on
the
call
here,
but
let
me
try
to
pick
a
couple
other
folks
that
are
maintainers
for
that
as
well.
Obviously
we
can
get
some
tractions,
so
we
can
get
to
cut
the
release
out.
A
All
right,
okay
and
then
there
was
also
the
the
gcp,
the
jet
provider,
which
used
to
speed
just
got
a
recent
release
as
well.
Gabriel
did
you
add
that
as
well
or
I,
think
Moapa
ran
the
release,
so
maybe
he
added
it.
A
Yeah
that
might
have
been
morphic
but
yeah,
so
a
new
release
has
been
cut
for
for
the
for
the
gcp
provider,
and
then
you
know
we
can
see
the
release,
notes,
Here,
a
number
of
new
resources
that
were
added
and
new
functionality.
A
A
D
Yeah
so
in
our
company
we're
using,
for
example,
so
we
bumped
the
provided
jet
AWS
to
a
new
terraform
version,
because
we
are
using
very
heavily
grafana
and
manage
prometos
from
AWS,
and
we
implemented
this
with
one
PR
and
also
we
start
using
network
firewalling
and
AWS.
And
we
also
implemented
this
in
the
jet
providers.
So
it
would
be
cool
if
we
can
see
a
review
of
the
merge
requests
and
a
new
release
of
it.
D
Because
at
the
moment,
we're
running
an
I
would
say:
release
candidate
cut
it
for
our
own,
but
would
be
better
to
to
to
to
to
to
in
zinc
with
with
the
official
ones
that
we
have
in
the
community.
A
A
Okay,
then
we
can
move
on
to
the
community
topic
section
here
as
well.
So
I
wanted
to
call
out
a
couple
interesting
pieces
of
content
that
has
been
authored
around
the
community
and
ecosystem
Pete
you're
on
the
call-
and
you
did
a
just
a
series
of
two
different
blog
posts
here
going
back
to
back.
Do
you
just
want
to
give
us
a
quick
overview
of
what
was
in
those
blog
posts
get,
and
so
people
could
read
the
details
later
on.
F
Yeah
I'm
coming
into
this
as
kind
of
a
kubernetes
cross-playing
noob,
and
this
is
a
little
bit
of
my
view
on
the
value
for
somebody
who
kind
of
lacks
that
expertise.
To
say
like
oh,
hey,
kubernetes
does
all
this
cool
stuff,
but
it
still
leaves
this
huge
gap
with
cloud
services
and
so
understanding
that
you
can
easily
see
where
a
cross
plane
fits
in
and
the
Value
Cross
plane
provides
so
really
trying
to
give
an
overview
of
the
the
problem
space
and
how
we're
a
solution.
A
Awesome,
Pete
I
think
that's
really
good
too,
that
it's
taking
that
angle
of
you
know
being
an
accessible
entry
into
the
space.
I
think
that's
something
that
can
can
be
forgotten,
sometimes
so
having
your
spin
on.
That
is
really
really
helpful.
A
Okay,
cool
and
then
Sean
Kane
wrote
a
someone
detailed
case
study
about
about
using
crossblane
and
his
thoughts
on
it.
So
definitely
worth
the
read
as
well:
some
good
good
opinions
in
there
and
some
well
thought
out
stuff
and
so
good
feedback
too.
A
So
this
is
this
is
a
useful
article
from
Sean
all
right,
yep,
so
cubiccon
North
America
is
coming
up
in
about
a
month
from
now
there's
this
link
has
been
here
in
the
agenda
DOC
for
a
bit,
so
you
can
click
on
that
and
you
can
see
all
the
talks
that
are
referencing
cross
painter
about
cross
planes
so
feel
free
to
jump
into
those
and
and
join
join
us
there,
and
hopefully
we'll
be
seeing
a
lot
of
your
your
friendly
faces
there
in
person.
A
A
So
I
guess
I'll
follow
up
with
him
about
if
there's
any
fruits
that
have
come
out
of
his
investigations
into
those
bugs
yet
I
haven't
heard
anything
explicitly
so
there
might
not
be,
but
I
wanted
to
check
with
him
and
I'll
follow
up
with
him.
Then
all
right
then
Pete.
This
is
your
big
topic
here
about
migrating
the
crosswind.io
website
and
docs,
and
everything
like
that.
So
let
us
know
some
details
about
this
topic,
sir.
F
Yeah
so,
first
off
the
the
commit
here
doesn't
change
anything
on
the
UI.
The
goal
was,
is
you
know
nobody
notices
so
coming
back
to
justification
today,
we're
building
with
Jekyll,
which
is
fine.
It
has
a
pretty
large
dependency
collection
and
leads
to
pretty
slow
local
development
experience
and
local
authoring
experience.
So
you
know
non-scientific
non-through
benchmarking.
You
know
three
to
five
minutes
to
build
the
site
on
on
my
MacBook
here.
F
The
big
reason
to
move
to
Hugo
was
speed,
Hugo's
build
times
so
first
off
Hugo
is
a
single
Standalone
binary
and
its
build
times
are
subsecond
for
most
Pages
until
you
get
pretty
large,
but
it's
also
all
go
based,
so
it
makes
kind
of
the
tooling
and
the
thinking
about
things
a
little
bit
more
in
line
with
you
know,
kubernetes
and
cross-plane.
In
that
sense
it
also
aligns
us
with
the
Upstream
kubernetes
documentation,
which
is
also
based
on
Hugo.
F
So
that's
that's
kind
of
the
big
reason
why
I
was
interested
in
this,
and
it's
also
you'll
be
seeing
myself
thinking
pretty
big
push
into
the
crosswind
documentation
between
now
and
kubecon
and
and
Beyond.
But
I'm
really
looking
at
trying
to
get
a
lot
done
to
enhance,
improve,
simplify
and
expand.
The
existing
crosswind
documentation,
I
think
moving
to
Hugo
will
just
make
that
process
a
lot
easier
and
a
lot
faster.
F
A
I,
definitely
like
the
the
angle
here
of
you
know,
being
able
to
more
quickly.
Add
you
know,
content
or
features,
or
you
know,
being
able
to
have
some
agility
with
our
with
our
development
time
here
and
investment
on
it,
especially.
A
You
know
a
solid
technical
documentation,
technical
writer
as
such
as
yourself,
where
that
might
that
speed
might
actually
be
utilized
so
good
stuff
man
yeah
thanks
for
taking
taking
this
for
yeah
taking
this
functionality
on
is
there.
What
is
the
next
steps
for
this
piece
because
I
know
I
took
about
I,
didn't
look
at
the
code
because
I
don't
know
I,
don't
have
a
good
understanding
of
of
the
technical
stuff
to
you
know
actually
understand
and
improve
it.
A
But
I
did
you
know
from
a
user
perspective,
went
through
the
sites
and
checked
for
things
and
clicked
on
things
and
was
you
know
analyzing
it
and
it
does
look
to
meet
that
goal
of
parity.
So
what
are
the
next
steps
for
this.
F
A
A
There
Pete
it's
like
like:
can
we
merge
this,
and
then
we
have
to
synchronize,
like
the
the
update
to
cross
plane,
to
do
publishing
the
docs,
or
are
there
not
like
a
tight
coupling
like
that
or.
F
So
they
are
tightly
coupled
today.
My
guess
is
I
I
didn't
look
at
the
script
close
enough
to
know.
My
guess
is
that
the
attempted
merge
from
the
cross
plane,
Source
repo
would
either
fail
or
it
would
just
commit
docs
that
don't
do
anything
like
you're,
just
adding
a
file
that
isn't
referenced
anywhere
else,
so
it
doesn't
matter
so.
I
I,
don't
expect
a
breakage
there,
but
it's
kind
of
like
merge
this
in
fix
the
make
file
kind
of
at
the
same
time,.
A
Got
it
okay
sweet,
so
we
probably
want
to
have
like
a
pinned.
Apr
opened
that
you
know
what
is
what
we
think
the
fix
is
and
so
that
we
can,
you
know,
merge
and
then
merge
the
docs,
the
Upstream
cross-plane
effects,
and
then,
if
that
doesn't
work,
we
can
iterate
over
it,
but
yeah
at
least
have
have
both
PR's
open
at
the
same
time.
So
we
can
kind
of
review
them
to
Tandem
yeah.
F
And
the
the
Upstream
make
file,
there's
no
there's
no,
like
downside
like
we
don't
have
to
do
this
within
seconds
that
make
file
gets
triggered
on
I.
Believe
it's
a
release
of
cross
plain.
There
might
be
a
time-based
element
in
there,
but
you
know
I
would
imagine
we
had
some
control
over
of
that
file
running.
F
A
It's
not
totally
out
of
our
hands.
Yeah
awesome,
okay,
cool
man.
Thanks
for
thinking
through
this
this
stuff
here,
yeah
then
I'm
super
excited
also
to
be
able
to
add
new
functionalities
such
as
like
linking
to
things
that
are
within
tabs
within
our
docs.
That.
F
Would
be
yeah
definitely
have
a
bunch
of
work
that
that
I
can
bring
in
now,
I
was
trying
not
to
my
goal
was
really
you
know.
Net,
Zero
and,
and
with
this
approved,
definitely
got
some
stuff.
We
can
bring
in
on
code,
highlighting
linking
the
line,
numbers
and
code
blocks.
F
A
Nice,
a
real
docs
engineer
here.
This
is
nice.
The
community
benefits
from
your
from
your
skill
set.
My
friend
love
it
all
right,
great
great,
great,
great
great
great.
So
then
Dan
do
you
want
to
catch
us
up
on
this.
This
PR
that
went
into
Maine
recently
and
will
be
included
in
1.10
sure.
B
So
I
think
this
is
something
we
wanted
to
do
for
quite
a
while,
but
just
honestly,
as
the
provider
ecosystem
and
actually
configuration
package
ecosystem
has
continued
to
evolve,
it's
become
more
critical.
So,
as
a
lot
of
folks
know,
if
you
have
a
dependent,
you
can
declare
dependencies.
I
guess
I
should
say
first
in
your
packages,
they
basically
say
hey.
When
you
install
me,
I
also
rely
on
these
other
packages.
B
You
know
similar
to
most
package
managers.
You
can
set
version
constraints
and
cross
plane
will
basically
construct
a
dag
and
resolve
that
for
YouTube
make
sure
you
have
everything
present
and
if
it's
not
present
depending
on
how
you've
configured
it,
you
can
have
it
install
them
for
you
automatically.
Now,
when
Crossway
goes
about
doing
that,
it
only
has
limited
information
about.
You
know
what
secrets
you
want
to
be
able
to
use
and
that
sort
of
thing.
B
So
what
this
change
does
is
it
allows
you
to
attach
package
full
secrets
to
the
Cross
plan
service
account
and
that
will
automatically
be
considered
whenever
you're
doing
any
package
operations,
so,
whether
you're
installing
a
single
private
package-
and
you
just
don't
want
to
have
the
specified
package
full
secrets
on
install
which
is
a
little
more
cumbersome
and
can
get
in
the
way
of
documentation
that
sort
of
thing
or
you
have
you're
installing
a
package
as
private
dependencies,
which
previously
was
just
impossible.
B
B
Those
full
Secrets
will
get
applied
all
the
way
down
the
chain,
and
so
I
think
this
will
help
enable
a
lot
more
use
cases
and
we'll
especially
be
you
know,
useful
for
folks
who
are
using
this
internally
in
their
organizations
to
install
private
packages,
so
it'll
be
really
useful.
Last
thing
I'll
mention
is
the
pull
secret
is
also
applied
to
the
deployment
that
gets
created
for
the
provider,
or
rather
the
service
account
the
deployment
uses
it
gets
created
for
the
provider,
and
that
means
that
now
that
we
use
the
bundled
provider
images.
A
Yeah,
oh
you're,
back
now,
yeah
I
think
I
heard
of
something
like
now.
We
use
bundled
images:
okay,
yeah.
B
I
was
just
mentioning
that
now
that
now
that
we're
using
bundled
package
images
or
bundled
provider
images,
obviously
that's
that
same
private
image
right.
So
you
need
to
be
able
to
give
permissions
to
the
deployment
to
be
able
to
pull
as
well
last
thing
that
folks
had
some
questions
around
was
if
I
actually
do
manually,
Supply
pool
secrets
for
installing
a
package,
and
it
has
dependencies,
will
those
also
get
propagated
down
the
chain.
We
decided
to
decouple
that
from
this
implementation,
because
attaching
them
to
the
service
account
does
unlock
this.
B
The
the
use
case
where
you'd
want
to
use
it
on
a
single
package
in
its
dependencies
would
be
if
you
didn't
want
to
share
secrets
between
most
of
the
time.
People
are
okay,
with
using
same
set
of
Secrets
for
pulling
packages,
because
that's
already
kind
of
an
administ
straighter
level
task,
but
we
may,
in
the
future,
depending
on
demand-
and
please
feel
free
to
you
know,
show
support
for
this.
B
If,
if
you
need
it
say
that
all
of
the
dependents
of
a
given
package,
when
it's
getting
resolved
to
by
cross
plane
will
actually
fetch
all
of
those
pull
secrets
and
apply
them
to
that
package
as
well,
but
something
that's
a
little
more
cumbersome
and
and
wasn't
required
to
initially
enable
this.
So
we
decided
to
leave
that
off,
but
this
will
be
in
1.10
should
be
useful
for
folks.
A
A
Great
Dan
I
I
expected
no
less
from
you.
My
friend
all
right
sounds
good,
okay
and
then
next
thing
on
the
agenda
is
yes,
so
Christopher
you
had
brought
this
up
last
community
meeting
and
about
adding
maxed
as
a
maintainer
to
provider
AWS,
and
then
we
made
a
little
call
out
to
to
other
maintainers
for
it
in
AWS
and
there
were
some
more
more
support
there.
A
So
it's
up
to
five
maintainers
now,
which
I
think
is
very,
very
valid:
support
for
the
maintainer
teams
that
says
that
they
would
love
Max
Deb
to
be
there
as
well.
So
is
there
anything?
Oh,
so
you
already
added
him
to
the
owner's
file
up
to
a
dirt,
wait
that
was
during
this
meeting
Christopher.
D
D
A
Week
talk
about
a
live
agenda;
I
love
it
okay.
So
then
that
was
everything
that
was
part
of
the
written
agenda
here.
Is
there
anything
that
folks
want
to
bring
up?
That
was
not
that
did
not
make
it
to
the
doc
yets.
A
Okay,
all
right,
then,
if
there's
nothing
else,
then
we'll
go
ahead
and
adjourn
and
get
20
minutes
back,
but
yeah
good
to
see
everybody
and
looking
forward
to
all
the
great
stuff.
That's
in
1.10
release
and
all
the
other
provider
releases
that
are
coming
out
soon.