►
From YouTube: 2022-09-08 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
has
started-
and
this
is
the
September
8th,
2022
cross
plain
community
meeting.
The
agenda
document
is
open
for
folks
to
go
ahead
and
add
any
topics
they
want
to
discuss.
Add
yourself
to
the
attendees
list.
I
will
drop
a
note
in
the
zoom
chat
right
now.
That
is
a
direct
link
to
the
agenda
document.
So
if
you're
not
in
there,
you
have
access
to
it
now
and
anything.
A
You
want
to
talk
about,
feel
free
to
add,
as
a
suggestion
to
the
suggestion
to
the
doc
and
we'll
go
ahead
and
accept
it.
So,
let's
get
started
as
usual
on
our
Milestone
checkup
Dan
I
think
this
topic
came
up
last
week,
but
and
I
don't
think
I
had
a
good
answer
for
it
and
I,
don't
think
you
were
there
and
I
didn't
get
to
follow
up
with
you.
A
So
if
you
can
give
us
an
update,
Dan
I
know
that
there's
been
some
pull
requests
that
are
code
related
changes,
not
just
docs
changes
that
have
gone
into
the
like
being
backboarded
into
our
release.
Branches,
I,
don't
think.
We've
had
a
patch
release,
that's
gone
out,
though,
and
since
these
changes
is
there
a
plan
for
a
patch
release
coming
out
soon,
then,
with
these
code
changes
there.
B
Hasn't
been
an
explicit
date,
but
I'll
go
ahead
and
get
some
issues
open
tracking
that
and
we
can
likely
Target
like
early
next
week
at
the
latest.
A
Got
it
is
there?
Is
there
a
desire
to
like
batch
up
a
couple
of
changes,
or
you
know,
are
these
this
particular
changes
for
you
know
our
package
package
polls,
but
the
only
thing
that
you're
aware
of.
B
That's
really
the
only
major
code
change,
there's
a
lot
of
like
docs
fixes,
and
things
like
that.
I
do
have
one
other
thing
that
I
opened
yesterday.
That
I
think
would
be
good
to
batch
into
this
as
well,
which
is
part
of
the
reason
why
they
haven't
gone
out
yet
and
I'll
make
sure
to
link
that
on
the
the
the
patch
release
issues.
A
Okay,
so
then
that
brings
us
to
our
next
next
Milestone,
our
major
Milestone,
which
is
the
V
1.10
release.
So
there
was
a
little
bit
of
confusion
and
I
take
account
of
accountability.
For
that.
So
sorry
about
that,
where,
in
this
community
meeting
venue,
we
had
discussed
that
we
had
made
the
change
to
do
quarterly
releases
as
opposed
to
every
two
two
months-ish
time
frame,
and
so
we
talked
about
that.
A
We've
talked
about
the
October
18th
dates,
that's
been
there
for
a
while,
but
I
did
not
follow
up
into
any
other
of
our
venues
where
we
track
releases.
So
I
caused
some
confusion
for
other
projects,
maintainers
where
we
almost
started
to
do
a
release
last
week
accidentally,
so
that's
been
cleaned
up,
and
so,
for
instance,
on
the
release
table
now,
we've
got
the
expected
1.10
release
dates.
A
The
tracking
issue
for
1.10
is
appropriately
set
for
October
18th
now
as
well,
and
the
community
calendar
has
been
updated
so
that
the
code
freeze
the
feature
freeze.
All
those
Milestones
associated
with
the
releases
is
on
a
quarterly
Cadence
when
the
correct
dates
as
well.
So
all
of
that
confusion
has
been
cleared
up
now
and
we
are
still
targeting
towards
October
18th
as
our
1.10
release,
release
dates
and
once
again,
sorry
about
the
confusion,
everybody,
so
you
know
the
we
have
everything
tracked
on
our
releases
board.
A
There
is
still
some
I
think
some
organizational
effort
that
needs
to
be
put
into
this
board
where
we,
you
know
we're
using
this
as
kind
of
a
a
a
entire
overview
for
everything.
That's
going
against
Crossbay
releases
in
the
roadmap
as
well.
So
you
know
I
want
to
be
able
to
segment
this
by
a
specific
release
so
that
you
can,
you
know,
use
this
board
and
a
view
onto
this
board
to
see
what's
in
1.10,
you
know
what
would
be
in
the
next.
A
One
is
1.11
all
that
sort
of
stuff,
and
so
we
can
get
a
better
a
little
bit
better
segmentation
of
of
the
data
here.
That's
on
this
board.
It
is
in
pretty
much
priority
order.
A
You
know
where
the
backlog
is
is
ordered
and
the
things
that
I
think
are
pretty
important
near
the
top
of
it
here.
So
that
will
continue
to
be
to
remain.
A
You
know
true,
so
I
think
the
the
some
of
the
roadmap
ideas
we
have
and
then
everything
else
is
kept
up
to
date
in
terms
of
what's
in
progress,
you
know,
what's
in
design,
what's
already
been
done,
Etc
so
are
there
any
updates
that
folks
want
to
make
to
this
board
or
things
to
call
out
things
that
we're
working
on
Etc.
A
Dan,
maybe
any
of
those
issues
that
you
had
or
you
wanted
to
open
up.
You
can
add
to
this
board
as
as
appropriate,
too.
A
All
right
so
yeah,
so
this
board
is
fairly
fairly
live
and
you
know
if
anybody
wants
to
members
of
the
organization,
you
know,
have
the
ability
to
update
issues
and
assign
themselves
to
them,
and
things
like
that,
so
that
would
be
reflected
on
this
board.
When
that
happens,
so
I
don't
think,
there's
a
lot
of
intervention
that
needs
to
to
happen
from
like
the
project
maintainers.
Let's
say
when
there
is
something
that
you
want
to
work
on
and
something
that
you're.
A
You
know
you're
you're
trying
to
drive
to
be
included
in
a
release,
but
do
feel
free
to
reach
out
to
me
and
sync
with
me
anytime,
though,
to
be
able
to
talk
about
including
things
and
releases
or
getting
the
support
that
you
need
to
be
able
to
drive
things
or
just
projects
management.
You
know
labels
organization,
assignees,
all
that
sort
of
stuff
feel
free
to
reach
out
to
me
anytime.
For
that
stuff.
A
Okay,
sweet,
so
that's
the
crossplay
core
releases
and
plans
for
that.
Let's
move
on
to
Providers,
then
I
just
took
a
quick
pass
at
some
recent
provider
releases
so,
for
instance,
I
think
maybe
Christopher.
It
was
like
a
couple
an
hour
or
so
after
the
last
community
meeting
that
we
got
out
the
V
0.31
for
provider
AWS.
Do
you
want
to
go
ahead
and
give
us
a
little
bit
of
overview
of
the
important
changes
in
that.
C
Yeah
so
I
guess
in
in
the
glue
space,
we
had
a
lot
of
rework
done
by
folks
from
Deutsche
Bahn,
so
they
changed
a
lot
of
fields
to
make
it
more
than
the
rest.
C
We
have
over
the
resources
and
it's
now
possible
to
use
fully
also
the
update
and
this
up-to-date
functions
for
glue
for
all
of
the
resources
we
have
in
this
space
and
I
guess
the
rest
of
the
release
was
one
thing
for
databases,
so
there's
also
no
possible
to
restore
for
more
sources,
the
databases
and
yes,
and
also
a
few
things
we
handled
in
my
company
for
the
e-cluster
update
it's
now
possible
to
update
database
clusters
with
all
the
fields.
A
All
right,
yeah,
so
a
couple
other
releases
like
the
the
jet
palette,
the
provider
Jeff
palette,
one
had
released
recently.
The
providers
VA
had
a
release
as
well,
so
you
can
see
dive
into
those
release,
notes
as
needed,
and
anyone
is
welcome
to
add,
since
the
ecosystem
of
writers
is
continuing
to
to
grow.
A
If
anyone
is
welcome
to
add
links
to
releases
of
their
providers
here
as
well,
and
we
can
always
talk
about
them,
foreign,
we
keep
on
moving,
then
I
think
to
now
we'll
go
past
the
milestones
and
release
this
section
and
we'll
go
into
the
community
topics.
So
we'll
start
with
contents.
Recent
content
here
a
couple
of
good
pieces
of
like
content
with
blog
posts
and
live
streams,
etc,
etc.
Dan
do
you
want
to
kind
of
give
us
a
quick
overview
of
some
of
these?
These
popular
live
stream.
B
Popular
seems
perhaps
inaccurate,
but
these
are
some
examples
of
updating
the
providers
which
I'll
talk
about
in
a
bit
to
using
the
bundled
package
format
we
have.
The
same
image
is
used
for
the
controller
and
the
package
I'll
go
into
a
little
more
detail
on
that,
but
these
are
just
me
doing
that
so
they're
not
very
exciting.
B
But
if
you're
interested
in
following
along
and
learning
a
little
bit
more
about
how
the
build
sub
module
Works,
we
go
through
like
a
little
bit
of
the
Precedence
order
and
make
targets,
and
things
like
that,
so
feel
free
to
check
those
out
I
think
they
do
expire
at
some
point,
which
is
gonna,
be
my
question
yeah,
which
is
probably
fine,
honestly
I
mean
like
I'm
fine
with
us
saving
them,
but
we
need
to
sync
them
to
YouTube
or
something
like
that.
B
But
they
are
it's
a
lot
of
hours
of
me
just
doing
that
so
I'm
not
sure
how
much
folks
want
to
engage
but
could
be
useful.
So.
A
Awesome
yeah
thanks
for
sharing
that
Dan
I,
think
that
we've
gotten
or
you
not
me,
you've
gotten
some
good
feedback
on
people
enjoying
you
know
being
able
to
watch.
The
experience
of
you
know:
live
programming
and
Building
Things
for
crossplay
to
kind
of
having
that
available
as
an
educational
aspect
and
perhaps
an
inspirational
aspect
of
it
as
well,
so
I
think
the
folks
in
the
community
enjoy
you
doing
that
thanks
for
doing
that,
awesome
so
that
I
definitely
wanted
to
call
out
this.
A
This
piece
of
content
here
so
Mauricio
saladino
he's
he's
been
a
long
time
fan
and
contributor
to
the
Cross
Lane
project,
and
so
he
wrote
up
a
pretty
well
thought
out
article
about
where
cross
plain
is
in
2022
and
some
you
know
potential,
you
know
feedback
and,
and
some
some
you
know
a
critical
eye
to
the
project
which
is
which
is
insightful
and
really
helpful.
I
think
so.
A
This
is
super
useful
and
I
think
great
for
anybody
to
to
read
through
and
and
catch
up
on,
some
well-formed
opinions
about
where
Crossland
is
and
there's
definitely
opportunities
to
collaborate
and
push
some
of
these
initiatives
as
well.
So
Deputy
thanks
a
lot
to
Mauricio
for
for
writing
that
up.
A
That
was
that
was
time
well
spent
and
I
definitely
appreciated
that,
and
then
the
last
one
is
that
Aaron
sorgerson
presented
with
some
of
the
team
at
the
VMware
World
VMware
Expo
I,
can't
remember
what
it's
called
and
I
apologize,
but
presented
on
an
integration
between
cross,
plain
and
tanzu,
and
so
now
the
recording
is
available
for
this.
So
on
this
link
here,
I
think
you
can
click
it
and
you
can
watch
that
recording
if
you're
interested
in
that
all
right.
A
So
this
will
be
our
final
final
updates,
I
think
on
the
LFX
mentorship
summer
term.
So
we
have
completed
the
term
with
rohika
and
with
parole,
and
the
projects
are
finished.
The
final
evaluations
are
in
so
we
have
a
yet
another
successful.
A
You
know
mentorship
experience
with
with
with
folks
from
you
know
that
are
still
in
University
and
contributing
to
their
first
open
source
project
and
getting
involved.
So
you
know
once
again
thank
you
very
much
to
Rika
into
parole
for
contributing
and
being
part
of
this
mentorship
program
for
the
for
the
summer
here,
and
you
know
we're
looking
forward
to
hopefully
having
more
contributions
from
both
of
them
and
hopefully
they'll
stay
involved
and
keep
helping
out
with
the
project.
A
So
Dave.
Do
you
want
to
give
a
quick
update
then
on
parole,
since
you're
you're
I'm
a
mentor
for
her
of
you
know
what
we
have
there
and
potentially
next
steps
for
for
where
we
might
want
to
take
it
in
the
future?.
B
Sure
So
Pro
worked
on
pulling
private
packages
with
cross
plain.
Some
folks
may
be
familiar
with
the
Machinery
that
we
use
to
do
this.
It's
based
on
go
container
registry,
which
is
a
pretty
popular
library,
but
essentially
Registries.
B
Don't
have
a
standardized
authentication
authorization
mechanism,
so
most
of
them
are
Loosely
based
on
how
Docker
Hub
works,
but
they
integrate
whatever
their
native
auth
is
so,
for
instance,
Google,
artifact
or
industry,
which
is
what
Google
spent
the
majority
of
her
time
on
uses
typically
uses
Google
service
accounts
to
go
to
authenticate,
so
there's
a
variety
of
different
ways.
B
You
provide
this
credential
data,
and
so
what
we
want
to
do
is
have
automated
tests
to
make
sure
that
any
updates
such
as
bumping
or
go
container
registry
version
or
any
change
to
the
package
manager,
aren't
going
to
break
the
different
scenarios.
Now.
This
is
a
fairly
specific
one
that
is
addressed
right
now.
Google
artifact
registry,
but
the
Machinery
that
Peru
will
put
in
place
can
be
applied
to
a
lot
of
different
Registries.
I
know
the
the
issue
we
were
just
talking
about
that
we
want
to
include
in
the
back.
B
Port
was
with
clay.io
or,
however
Red
Hat
folks
say
that,
but
there
was
some
issues
with
authentication
over
there.
So
that's
an
example
of
something
we
could
catch
with
these
ongoing
integration
tests
that
we
run
on
a
schedule,
so
that
Machinery
is
in
place.
So
we
can
continue
to
expand
that
to
test
against
multiple
Registries
and
make
sure
we
we
don't
have
any
regressions.
A
Awesome
Dan
thanks
for
that
summary
and
yeah,
so
then
I
think
we're
at
a
good
place
there.
Where
we've
got.
You
know
recurring
testing
logic,
to
make
sure
that
we
don't
regress
with
your
private
package
polls
with
the
Google
artifact
industry,
and
then
you
know
we
have
everything.
We
need
to
continue,
adding
more
support
for
other
registries
over
time,
so
I
think
that's
a
great
place
to
get
that
project
and
then
quick
update
on
on
the
Rubik's
project.
A
You
know
her
intent
was
to
be
able
to
detect
breaking
changes
in
crds
and
report
back
on
them
nprs.
So
we
got
to
the
logic
of
of
you
know,
detecting
a
couple
different
cases
for
when
a
a
crd
may
have
breaking
changes.
A
The
The
Next
Step
there
you
know
after
you
know
if
she
wants
to
continue
contributing
to
it
after
the
term
is
over,
would
be
to
integrate
that
in
to
pull
request
workflows
so
that
you
know
when
you're,
creating
new
pull
requests
will
automatically
scan
the
the
crds
that
are
potentially
affected
by
the
pull
request
and
report
on
any
breaking
changes
there.
Within
that
context,
right
now
we
have
some
of
the
lot
that
we
have
the
logic
and
then
we
have
it.
A
You
know
unit
tests
to
exercise
it
and
verify
the
logic,
but
it's
not
integrated
into
the
pr
workflows
which,
which
is
which
is
a
big
step
there.
So
that's
something
that's
not
yet
done,
but
you
know
more
contributions
to
continue.
That
effort
are
certainly
welcome.
A
Okay,
sweet,
so
yeah.
We
talked
about
this
before
cubecon
North,
America,
I
think
we're
one
month
out
or
so.
You
know,
there's
last
time,
I
checked
that
this
direct
link
to
see
cross-plane
related
talks,
there's
eight
of
them.
So
yeah
you
can
check
out
those
and
and-
and
you
know,
add
them
all
to
your
schedule-
come
and
join.
I've
got
them
all
on
my
schedule,
so
hopefully
I'll
get
to
join
as
many
of
them
as
I.
A
Can
there
and
see
see
some
of
you
all
there
too,
we
also
did
mention
some
of
the
repository
maintenance
cleanup
stuff.
We
had
done
recently.
A
I
just
wanted
to
leave
this
here
for
another
week
since
I
think
there
are
more
opportunities
for
folks
to
join
in
the
reviewer
role
of
you
know,
being
able
to
start
contributing
more
and
you
know
reviewing
and
taking
a
look
at
pull
requests
providing
feedback
there
and
you
know
getting
more
exposed
to
the
project
in
its
internals
and
become
more
of
a
domain
expert
on
the
project
as
a
path
towards
maintainership
by
becoming
an
official
reviewer
of
PRS.
So
I
think
there's
a
couple
more
thoughts
for
that.
A
There's
more
availability
for
that,
so
reach
out
to
me
anytime.
If
you
want
to
and
Nick
there's
another
person
reach
out
to,
if
you're
interested
in
that
role,
we
could
talk
about
that
foreign.
A
Agenda
item
about
bundle
packages.
B
Yep,
so
those
issues
linked
there
describe
kind
of
the
changes
made
in
gcp,
Azure
and
AWS
and
I'm
happy
for
folks
who
are
maintainers
of
other
providers
to
help
bring
this
same
functionality
to
to
them
as
well
or
to
any
other
community
ones.
B
But
essentially
we
had
to
change
a
while
back
in
Cross
plain
that
allowed
to
use
a
single
image
for
the
the
packages
and
the
controllers,
so
we're
switching
to
using
that
here
we're
also
switching
to
using
some
updated
Machinery.
That
makes
it
a
little
bit
nicer
to
work
with
these
images
and
build
multi-architecture
images,
and
things
like
that.
B
So
broadly,
the
flow
looks
like
we
still
depend
on
Docker
build
X
to
produce
the
multi-architecture
controller
image,
and
then
we
reference
that
as
a
base
when
we
build
the
package
image
and
it
puts
that
package
content
on
top
of
the
the
controller
base
and
annotates
that
so
crosswind
knows
hey.
You
only
need
to
consider
this
one
layer
and
then
that
image
with
the
extra
layer
in
there
gets
pushed
up
to
whatever
registry
a
couple.
B
Other
updates
that
came
along
with
this
by
default,
the
tooling
that
we're
using,
which
is
the
up
CLI,
which
is
open
source
as
well,
will
include
the
examples
directory
as
a
separate
layer
and
the
examples
directory
is
really
nice,
because
I'm
not
sure
if
we
have
a
I,
think
I
have
it
on
the
provider
AWS
one
they
might
have
a
screenshot.
Do
you
want
me
to.
B
B
Yeah
and
I
think
if
we
scroll
down
I
attached
there,
we
go
this
guy's
an
image
yep,
so
you
can't
necessarily
see
it
in
that
one.
So
it's
not
the
best
image,
but
once
we
have
new
releases
of
these
providers,
we're
now
publishing
to
both
Docker
Hub
and
the
outbound
Marketplace
and
the
nice
thing
about
the
about
Marketplace.
B
Is
it's
gonna
both
post
the
image
right,
but
it's
also
going
to
create
automatic
documentation
for
all
of
the
crds
that
are
provided,
and
it's
going
to
include
examples
for
them
as
well,
and
those
are
all
going
to
be
combined
together.
B
So
when
you
go
to,
for
instance,
a
specific
like
the
certificate
page,
it
will
give
you
documentation
on
those
crds
kind
of
like
doc.crds.dev
has
done
in
the
past,
but
perhaps
in
a
bit
of
a
nicer
format,
because
I'm
not
a
front-end
engineer
and
and
then
also
have
examples,
so
it
was
really
cool.
I
actually
didn't
modify
the
examples
in
any
of
these
providers.
B
It
well
at
all,
and
and
up
so
I
just
said,
oh
found
the
examples
I'll
go
ahead
and
include
them
up
there,
and
so
all
the
your
whole
examples
directly
will
automatically
get
associated
with
the
right
types
so
we'll
both
publish
to
Docker,
Hub
and
up
on
Marketplace.
We
want
folks
to
be
able
to
have
optionality
and
pull
from
where
they
see
fit,
but
yeah.
B
You
should
get
this
documentation
pretty
much
for
free
here,
just
by
pushing
there
so
yeah
excited
to
propagate
that
to
other
providers
as
well
as
folks
are
interested.
A
And
Dan
is
that
that's
something
that
will
will
owners
and
maintainers
of
other
providers
be
able
to
follow
the
same
pattern.
You've
done
in
those
pull
requests,
or
will
they
need
some,
maybe
I
guess
one
thing
they
might
need
is
credentials
to
be
added
to
their
their
their
repo
too.
B
Yep
that's
correct
and
at
the
current
moment,
I've
created
scoped
credentials
for
each
of
the
repositories,
and
so,
like
you
know,
provider
AWS
can
push
to
provider.
Aws
we've
also
in
the
past,
at
least
with
Docker
Hub
had
org
level
credentials,
which
were
you
know
for
all
of
the
different
repositories
that
we
had
both
the
GitHub
repositories
and
the
docker
of
ones,
which
does
put
us
in
a
somewhat
precarious
position
in
that
like.
B
If
a
maintainer
accidentally
pushed
to
the
wrong
repository
via
CI
right,
they
update
their
CI
to
push
the
wrong
thing.
Then
they
could
overwrite
existing
images.
B
We
haven't
run
into
that
and
it
does
make
it
more
convenient
when
spinning
out
new
repositories
for
the
time
being
post-conditional
free
to
reach
out
to
me
and
I'm
happy
to
make
sure
we
have
credentials
in
place
on
the
repository
or,
if
there's
another
maintainer,
who
has
access
to
configure
the
secrets
there
you're
welcome
to
do
that
as
well.
A
Awesome
thanks
for
filling
Us
in
on
that
Dan
cool,
so
quick
update
on
the
fuzz
testing
effort
that
cncf
has
been
helping
out
with
so
we
have
been
getting
some
test
case
results
from
the
fuzz
testing
effort,
and
so
alpair
is
I.
Think
Opera's
here
right,
no
he's
not
on
the
attendee
list
today,
so
yeah
so
Albert
is
starting
to
excuse
me
starting
to
dig
into
those
and
start
analyzing
or
assessing.
If
you
know
they
are
repeatable.
A
If
they
are,
you
know
something
that
we
can
reproduce
and
so
he's
digging
into
that
in
kind
of
there's
a
few
things
to
learn
there
about,
like
the
the
fuzz
testing
tool,
the
first
testing
environments,
all
that
sort
of
stuff,
so
Alberta's
effort
here
he
needs
more
access
to
get
into
the
test
case,
dashboard
that
the
cncf
pointed
us
at,
but
the
access
that
he's
gotten
so
far
in
the
effort
that
he's
putting
into
being
able
to
you
know,
rebuild
and
run
the
fuzzers
locally
and
reproduce
locally,
and
investigate
and
dive
deeper
will
be
repeatable
across
any
other
test
case
failures
that
show
up
in
the
future.
A
So
the
expected
more
to
come
out
of
this,
because
Albert
is
focusing
on
it
now:
okay,
Jesse
and
Dan
I
think
you
all
wanted
to
talk
about
some.
You
know
supply
chain,
securing
and
signature
verification
of
packages.
D
Use
cases
oh
yeah
I
can
talk
about
the
use
cases,
so
so
Autodesk
is
in
the
process
of
evaluating
cross-plane
as
a
kind
of
Next
Generation
IAC
tool
for
our
Cloud
deployment
platform
and
as
a
part
of
that.
Well,
actually,
around
the
same
time,
we
are
also
actively
pursuing
a
fedramp
ATO
so
that
we
can
sell
our
services
to
the
federal
government.
D
One
of
the
issues,
one
of
the
controls
that
the
federal
government
requires
is
for
artifact
signing
for
numerous
different
artifact
types
and
as
we
were,
you
know
doing
Discovery.
We
came
across
six
door
and
and
have
already
implemented
cosine
image
signing
for
our
containers
and
cross
plain
uses,
oci
images
and
there's
no
reason
why
we
couldn't
easily
extend
our
signing
to
those
images.
The
validation
is
is
something
that
that
we
need
to
kind
of
do
some
work
on.
D
So
this
proposal
is
for
modifying
the
cross,
plane
package,
controller,
I,
believe
the
package
controller
to
to
check
and
validate
cosine
signatures
in
a
minimal
viable
fashion,
and
if
the
images
are
validated,
then
the
the
fetch
will
continue
in
the
the
package.
D
Revision
will
be
kind
of
completed
so
I'm,
not
as
well
versed
in
how
the
package
manager
works,
but
I
did
do
a
lot
of
discovery
which
you'll
find
in
this
proposal
and
Dan
has
been
helping
me
like
kind
of
locate
where,
but
the
best
locate
the
best
spots
in
the
code
base
would
be
to
do
some
of
this
implementation.
I
also
have
a
few
folks
from
the
six
door
project
who
are
helping
with
the
kind
of
the
basics
of
the
validation
implementation
as
well,
which
you'll
we
will
find
below.
D
If
anyone
has
any
questions
about
our
use
case,
I'm
happy
to
fill
that
in.
If
you
have
more
detailed
questions
about
the
implementation,
I
might
I
might
need
to
lean
on
on
the
the
aforementioned
subject
matter.
Experts.
A
That's
awesome,
Jesse
Yeah.
So
thanks
for
going
through
the
effort
of
writing
up
disposal-
and
you
know
getting
some
of
these
ideas
clear
and
you
know
the
approach
that
we
want
to
take
there
Dan
do
you
have
anything
to
augment
with
what
Jesse
has
said
so
far.
B
Yeah
I
think
that's
a
great
description.
I
will
say
that
we
have
some
some
Milestones
we'd
like
to
hit
around
this
I.
Think
we'd
like
to
have
it
as
an
alpha
feature,
which
means
off
by
default
but
can
be
enabled
by
the
V
1.10
release
and
I
know
Jesse
and
some
of
the
same
store
folks
have
a
cute
contact.
I
think
is
going
to
touch
on
this.
B
So,
as
Jesse
mentioned,
he's
already
done
a
lot
of
work
in
looking
into
where
we
can
do
this
I
think
for
folks
to
kind
of
like
conceptualize
this
step
a
little
bit
Jesse
pointed
to
another
PR.
We
had
a
while
back
around
someone
adding
support
for
self-signed
search
for
internal
Registries,
and
things
like
that.
It's
kind
of
similar
to
that,
although
you
know
we're
not
augmenting
the
transport,
we're
instead
saying
we're
gonna,
actually
fetch
the
signature
and
verify
it,
but
somewhere
to
go
container
registry.
B
We
get
to
differ
a
lot
of
that
existing
libraries
for
cosign,
and
things
like
that.
So
should
be
a
really
nice
thing
to
would
be
able
to
enable
in
this
minimum
viable
way
that
Jesse's
talking
about
but
I,
think
we'll
probably
expand
that
future
work
section
to
go
into
even
more
opportunities
for
like
how
you
can
do
more
granular
verification
and
how
we
can
talk
about
claims
and
that
sort
of
thing.
So
lots
of
excitement
here,
another
benefit
of
being
built
on
top
of
oci.
A
Yeah
awesome
yes
and
Jesse
thanks
always
too,
for
you
know,
sharing
the
details
about
your
use
case
as
well,
because
you
know
it's
one
thing
to
propose
a
you
know:
change
Behavior
or
new
functionality,
Etc,
but
I
think
you've
always
done
a
good
job
of
you
know
giving
folks
in
the
community.
The
background
of
you
know
what
your
team
is
doing
and
why
they
need
it,
and
you
know
kind
of
that
context
around
the
use
case
is
always
really
helpful.
D
Yeah
and
if
anyone
wants
to
to
actually
attend
that
kubecon
talk,
that's
actually
going
to
be,
you
know
pretty
much.
The
first
half
of
the
talk
will
will
be
about
well,
maybe
the
first
third
of
the
talk
will
be
about
why
Autodesk
needs
this,
and
why?
It's?
Why
it's
beneficial
to
to
companies
like
Autodesk,
especially
in
compliance
regulatory
environments,
to
to
have
that
extra
check
before
deploy.
A
A
Sounds
great
all
right,
let's
see
where
are
we
now
so?
Yes,
that
is
package,
signature,
verification
stuff,
then
it
looks
like
we've
got
a
issue
to
discuss
about
the
grafana
provider.
C
Yes,
I
can
say
something
about
this
all
right,
so
this
is
a
jet
provider,
so
they
generated
the
provider
out
of
terraform
the
grafana
guys
and
yeah.
In
my
company
we
decided
to
move
all
our
grafana
dashboards
and
want
to
deploy
this
with
the
grafana
provider
for
cross-plan
system
and
if
it's
grown
a
little
bit
down.
C
There's
one
issue
in
my
comment
in
the
dash:
if
you
this,
if
you
have
in
the
dashboard
in
variable
like
DS
prometoys,
the
jet
providers
with
trying
VAR
substitution
when
you
deploy
the
dashboards-
and
this
leads
to
the
to
the
issue
that
DS
Primitives
is
well
substituted
with
an
null
value
and
you
need
to
modify
every
dashboard
with.
C
If
you
use
a
variable,
you
need
to
add
a
dollar
in
front
of
the
variable
that
Diva
substitution
knows
that
this
is
a
variable
of
the
dashboard
and
my
question
is,
if
it's
possible
to
disable
for
Fields
the
vars
substitution
and
the
Jet
providers,
because
I
can't
find
anything
in
the
documentation
about
this,
because
it's
very
annoying
to
change,
tons
of
kafana
dashboards
and
add
a
double
dollar
for
all
of
the
variables
and
I
guess.
C
Bob
also
entered
a
comment
afterwards,
so
what
you
mean
exactly
so,
if
you,
if
you
deploying
the
dashboards
directly
with
terraform,
there's
no
issue
with
the
raw
substitution
for
the
config.json
field,
it's
only
a
problem.
If
you're
using
the
jet
provider.
A
Got
it
got
it
yeah
into
Christopher,
so
you
said
you
started
looking
into
you
know
where
this
type
of
fix
can
be
more
generally
applied,
and
so
did
you
and
it
sounds
like
you
with
that
investigation.
You
weren't
quite
clear
about
where
that
would
need
to
be
a
fixed
or
like
what
the
proposal,
or
you
know
what
the
impact
would
be
exactly
foreign.
C
Things
we
need
to
fix
this
or
make
an
option
that
you
can
disable
our
substitution
for
Fields
I,
don't
know,
but
I
didn't
find
anything
and
also
did
not
get
got
no
replies
in
the
community
for
this.
So
that's
why
I'm
edit
this
to
the
agenda.
A
Got
it?
Is
there
a
discussion
like
a
link
to
a
discussion
that
that
you
were
starting
on
this?
Is
it
in
slack
or
or
it's
like,
okay
yeah
feel
free
to
to
add
a
link
to
that
here.
So
we
have
that
that
you
know,
in
addition,.
A
Have
the
where
that,
where
that
that's
discussion
is
happening
also
so
yeah
and
I
definitely
know
that
I
do
not
have
the
expertise
and
the
understanding
of
the
the
charge-based
providers,
their
pipelines
of
of
how
this
might
be
inserted
in
there.
So
I
will
certainly
defer
to
anybody
else
on
the
call
that
may
have
that
information,
but
then
I'm
also
looking
for
a
couple
names
that
would
have
a
good
sense
of
that,
and
and
not
seeing
not
seeing
a
few
of
those
folks
today.
B
A
One
of
those
folks
might
have
some
good
insights
into
the
first
thing.
I
want
to
identify
is
what
is
a
potential
fix
here?
What
does
it
look
like?
How
scoped
is
it?
Does
you
know?
What
does
it
require
to
roll
it
out
all
that
sort
of
stuff
to
get
a
good,
get
a
good
sense
of
the
scope
and
then
and
then
we
can
go
from
there.
Yeah
cool
awesome,
yeah,
thanks
for
picking
that
up.
Let
me
accept
that
link,
yeah
I
think
Christopher
I
want
to
just
give
you
edit
access.
A
This
document
too,
do
I
get
a
lot
of.
We
got
a
lot
of
like
things
in
there
to
success
like
may
as
well.
Just
give
you
edit
access
honestly
yeah
Chris.
If
you
want
to
send
me
a
just
a
message
on
slack
of
like
what
you
know,
email
to
use,
to
add
you
to
an
editor
here,
then
I'll
follow
up
on
that
man.
Okay,
thanks,
sweets!
A
Okay!
So
then,
let's
move
on
to
a
quick
topic
here
so
Christopher
as
a
maintainer
of
Provider
AWS
has
proposed
to
go
ahead
and
add
Mr
MX
Max
to
as
a
maintainer
or
provider.
Awas
as
well
looks
like
it's
getting
plenty
of
support
from
from
the
rest,
the
maintainer
team,
so
Carl
has
plus
one
did
and
Dan
is
plus
one
did
as
well
and
a
couple
of
non-binding
votes
as
well.
A
So
you
know
the
adding
maintainers
to
repository
as
per
the
governance
is
not
something
that
requires
steering
committee
approval,
so
the
maintainers
themselves
can
make
this
decision.
So
the
only
thing
you
know
and
I'm,
not
a
maintainer
I'm
Predator.
Yes,
so
I
don't
have
a
necessarily
a
strict
vote
here,
but
so
the
only
thing
that
I
wanted
to
suggest,
at
least
for
us,
is
to
get
a
a
bit
more
validation
from
the
other
maintainers,
because
I
think
there's.
A
The
preventative
base
has
the
most
maintainers
so
like
Nick
and
mafiken
Hassan
and
Albert
and
Aaron
they're,
all
maintainers
on
it
too.
So
just
a
couple
more
like
you
know
so,
just
general
support
from
them
and
I
think
that
you
all
as
a
maintainer
team,
can
decide
when
you've
got
the.
You
know,
support
and
validation
to
go
ahead
and
pull
Triggers
on
this
so
yeah.
So
there's
no
steering
committee.
You
know
intervention
that
needs
to
happen
or
approval.
A
That
needs
to
happen
here,
but
if
you
do
need
access
for
like,
if
anybody
here
needs
access
to,
you
know
adding
adding
Macs
to
the
permissions
of
the
repository
feel
free
to
reach
out
to
me.
Otherwise
you
know
I'm
just
advertising
this
for
the
rest
of
maintainer
team
to
add
their
approvals,
and
then
you
walk
as
maintainer
team
can
make
the
final
decisions.
Okay,
but
Max
is
awesome.
So
I
have
my
my
non-binding
plus
one
in
there.
A
Sweet
and
then
I
reached
also
Christopher
I,
reached
out
as
well
directly
to
some
of
these
folks,
like
Nick
and
and
Hassan,
and
them.
C
A
Think
mafiken
has
has
honored
both
on
vacation
this
week,
so
we
might
not
hear
much
from
them,
but
Aaron
and
Alberta
and
Nick
are
all
around
so
might
be
a
couple
more
plus
ones.
Coming
in
soon
too,.
A
Sweets
all
right
and
thanks,
you
know
to
Max
as
well
for
all
of
his
contributions
and
things
that
he's
driving.
So
this
is
great
okay,
so
that
was
everything
that
was
on
the
agenda
for
today.
Does
anybody
want
to
add
a
last
minute
agenda
item.
C
C
And
yeah
some
new
page,
it
would
be
great
to
that
if
we
can
go
for
this
for
the
110
release,
because
it's
very
annoying
that
this
is
not
working
in
patch
sets
the
two
composite
field
path,
and
that
and
and
you
need
to
yeah-
you
get
not
a
real
error
message
that
this
is
not
working
you.
The
only
thing
you
find
it
out
is
to
find
this
issue,
and
then
you
write
your
two
composite
field
paths
without
the
patch
sets,
and
yes,
yeah.
A
Yeah
that
was
time
wasted:
okay,
dude
yeah,
so
yeah
I
totally
support
that
as
well.
This
is
a
bug
that
that
kind
of
concerned
me
and
it's
kind
of
a
a
landmine
out
there
for
folks
to
to
unfortunately,
step
on.
So
we
don't
want
that.
Then
I
did
or
go
ahead
and
add
it
into
the
cross.
Plane
releases
backlog
and
prioritize
it
there.
A
So
it
does
not
have
an
assignee
a
direct
assignee
right
now,
but
this
is
something
that
totally
has
my
support
of
you
know
it'd
be
great
to
include
that
on
1.10
we've
got
the
help
wanted
label
on
it.
A
So
if
somebody
wants
to
pick
this
up,
they're
more
than
welcome
to
Reach
Out,
get
it
assigned
and
and
run
with
it
as
well,
because
I
think
this
is
a
bug
that
you
know
is
is
behavior
that
is
going
to
cause
more
problems
for
people
and
I
think
it
would
be
good
to
have
it
included.
1.10
thanks.
A
Yeah,
that
may
be
something
kind
of
interesting
for
myself,
even
if
I
get
time
to
to
do
a
little
bit
of
Crossbay
code,
this
could
be
a
a
nice
little
juicy
one
to
take
I'll.
Keep
that
in
mind
as
well.
Christopher.
A
That's
certainly
no
guarantees
on
that.
One
I,
don't
know
what
I'm
doing
for
most
of
the
time.
Okay,
sweet,
so
I'll,
actually
I'll
go
ahead
and
move
that
one
up
Christopher
for
for
issues
here,
patch
just.
A
All
right:
well,
that's
everything,
then
good
to
see
all
you
all
today
and
some
of
you
yesterday
as
well,
and
we
will
see
you
online
and
in
two
weeks
of
the
next
community
meeting.