►
From YouTube: 2021-04-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
Okay,
the
recording
has
started-
and
this
is
the
april
8th,
2021
cross-plain
community
meeting.
We've
got
a
good
amount
of
things
on
the
agenda
here,
so
let's
jump
right
on
into
it.
So
as
as
usual,
we'd
like
to
start
with
our
upcoming
milestones
releases
roadmap
sort
of
stuff
last
time
was
the
the
first
time
we
kind
of
started,
doing
more
planning
and
prioritization
from
a
community
perspective,
and
so
folks,
were
you
know
weighing
in
on.
A
You
know
important
issues
or
status
of
things
that
they're
working
on
as
a
greater
community
community
and
not
just
the
maintainers,
so
we'll
be
continuing
continuing
that
process
for
each
one
of
these
community
meetings
here.
So
the
next
release
that
we
have
coming
up
is
scheduled
for
the
end
of
this
month.
So
that's
about
about
three
weeks
from
now
it's
on
april
27th
that'll
be
the
1.2
release.
You
can
always
stay
up
to
date
with
the
schedule
upcoming
releases
in
the
main
readme.
A
There's
a
release
section
there
that
kind
of
gives
the
timeline
for
for
releases
so
we're
working
towards
the
end
of
the
month.
Here.
A
And
so
we
can
jump
into
kind
of
milestone
planning,
I
think,
there's
you
know,
1.2
is
kind
of
we've
talked
about
it
before
and
it's
kind
of
more
on
a
you
know
trajectory
on
landing
it
now,
as
opposed
to
pulling
in
big
items
to
get
started
on.
So
let's
bring
up
the
community
board
and
let's
just
kind
of
get
overall
status
like
sense
of
status
for
where
things
are,
and
you
know,
update
some
things
that
maybe
need
some
attention
to
them,
but
also
you
know
like
priorities
as
well
too.
A
A
A
But
you
know
that
being
said,
this
is
in
this
community
here
with
people
gathered,
it's
a
good
opportunity
to
talk
about
the
status
of
things
and
weigh
in
on
things,
so
there's
a
whole
bunch
of
nws
features
or
services
that
have
been
added
and
already
merged.
Do
you
want
to
kind
of
give
a
broad
update
around
all
the
other
ones
that
are
in
progress?
Mosf.
B
Yeah,
so
we've
got
a
couple,
big
ones
that
affects
like
almost
all
resources,
for
example,
the
one
update,
sdk
v2
version,
so
we
too
just
got
to
be
like
no
general
available
and
we're
gonna
use
that,
thanks
to
a
few
folks
from
the
community
who
took
on
that
challenge
and
the
rest
of
most
of
the
prs
are,
like
you
know,
introducing
new
services
using
code
generation
pipeline,
for
example,
dynamodb
document,
tb,
sorry
and
a
few
others
like
lambda
and
easy.
B
B
So
this
issue
opened
by
steve,
we're
gonna,
like
you
know,
we
have
talked
about
it
and
we're
gonna
fix
it
in,
like
you,
know,
provide
a
conflict
level.
So
there
are
like
you
know
these
kind
of
kinds
of
pr's
mostly,
and
there
are
a
few
in
the
accepted
column
there
are
like
you
know,
rather
small
bug,
fixes.
B
That
was
that
I've
been
planning
to
take
on,
but
didn't
get
a
chance
to.
Yet
that
is
like
you
know,
overall
provide
aws.
So
in
general,
like
you
know,
most
of
the
pr's
are
new
service
introductions,
and
there
are
a
few,
like
you
know,
changes
in
how
we
do.
A
I
think,
in
addition
to
the
number
of
services
that
are
being
added
there,
the
ones
you
mentioned
about
like
updating
to
the
v2
of
the
sdk
and
then
also
the
you
know,
global
region
partition
thing
that
does
sound
pretty
interesting
as
well
too
did
did
we
did
you
get
a
sense,
I
think,
because
third
steve
there's
a
lot
of
stuff
he's
in
the
crossland
community,
steve
caballo
is:
did
you
get
a
sense
on
if
that
one's
gonna
be
landing
or
like
the
timeline
on
that
one.
B
Yes,
I
believe
it'll
be
before
the
release
deadline.
I
mean
because,
like
the
work
itself,
wasn't
really
you
know
that
big,
but
we
had
to
have
like
you
know
some
back
and
forth
about
like
know
where
to
put
that
field,
and
now
I
think,
we're
all
on
the
same
page
from
what
I
probably
remember.
So
it
should
be
good
to
go.
A
Awesome:
yeah,
okay,
good
yeah,
that's
good!
To
see
convergence
on
that
one
excellent!
There's
a
there
was
a.
There
was
another
pr
that
I
wanted
to
bring
up
here,
I'm
not
seeing
it,
but
it
was
being
able
to
pass
from
multiple
sources.
Hassan
you
had
written
a
new
cross-plane
configuration
for
cross
plane
that
depended
on
that
functionality.
Does
do
you
see
that
on
this
board.
C
Yeah,
I
think
it
is
in
kia,
open
column
and
sixth
from
top
composition,
transform
page.
A
C
I
might
I
haven't
looked
in
a
little
while,
but
my
understanding
is
that
we
really
just
need
to
bet
ben's,
probably
just
blocked
on
direction
and
feedback
from
people.
I've
apologized
to
him
on
on
slack,
and
he
said
he's
he's
surviving,
so
go
review
that
and
make
sure
that
the
sort
of
technical
implementation,
although
the
sort
of
the
implementation
it
does
make
sense,
got.
C
A
Yeah
awesome
yeah.
I
definitely
appreciate
the
the
looks
on
on
this
one
and
you
know
the
managing
of
a
lot
of
different
priorities
as
well
too
yeah.
I
really
like
this
functionality.
I,
when
you
know
we
get
that
in
that
would
be
amazing
to
have.
A
And
hassan,
I
also
found
your
vault
configuration
there
to
be
quite
a
nice
reference
for
doing
more
complicated
stuff
with
provider
helm
too.
That
was
actually
a
really
good
resource
fan.
So,
thanks
for
braver
for
going
down
some
paths
before
I
did
first
off
the
man-
okay,
yes,
so
aws
stuff,
some
of
these
pr's.
What
else
do
people
want
to
check
in
on
for
status
and
including
in
1.2?
What
else
is
on
people's
minds
here?.
D
One
thing
I
know:
movavic
ping
me
on
the
in
the
in
progress
here
we
have
a
pr
open
for
the
required
patch
policy
aborts.
I
just
need
to
test
that
a
little
bit
more
and
we
should
be
good
to
go,
but
thank
you
for
the
reminder
on
that.
One
move
off.
I
think
I
think
it's
looking
pretty
good,
though.
A
All
right-
and
that
was
we
were
thinking
about
just
including
that
in
1.2
right
like
we
do,
we
see
any
reasoning
for
patching
that
or
anything
or
is
1.2.
Okay,.
D
B
D
Behavior,
well
it
it's
it's
kind
of
like
debatable
what
the
intended
functionality
is,
but
I
think
it
is
like
it
is
kind
of
like
working
as
expected
right
now,
but
we
want
that
to
be
different,
and
so
I
I
wouldn't
patch
it
even
if
we
had,
even
if
the
release
was
way
out.
I
don't
think.
A
And
then
also,
this
is
a
good
opportunity
for
anybody
to
you
know
on
the
proposed
column
here
this
is
kind
of
serving
as
a
longer
term
road
map,
because
you
know
these,
the
ones
that
are
proposed
and
not
necessarily
accepted
into
the
milestone
yet
aren't
probably
are
not
going
to
be
included
in
the
1.2
release,
but
these
are
somewhat
of
an
ordered
list
of
things
that
we've
heard
from
the
community
to
be
quite,
you
know,
impactful
or
important
for
for
adopters
of
the
project.
A
So
this
is
definitely
a
chance
for
anybody
to
weigh
in
to
say
hey
this
one
in
the
proposed
column.
Here
is
really
important
to
me
and
kind
of
you
know:
surface
surface
demand
for
some
of
these
issues
as
well
too.
D
I
think
the
reason
why
all
these
are
unproposed
potentially
is
because
I
missed
the
original
meeting
where
we
triaged
this
board,
because
I
was
out,
but
just
something
to
note
on
that.
One
well.
A
D
A
The
meeting
and
we
missed
you
dan
yeah,
so
do
the
in
the
newer
version
of
go
container
registry.
Do
you
think
that
has
anything
related
to
you
know
like
the
networking
certificates
sort
of
behavior
that
rahul
had
been
seeing
in
his
environments
or
it's
just
a
very
regular
update
of
of
this
dependency?
We
have.
D
I
don't
from
what
I've
observed
and
this
is
going
to
be
a
multiple
version
bump.
So
that's
something
to
keep
in
mind
so
anytime.
You
do
that.
Obviously
we're
we're
want
to
make
sure
that
all
the
functionality
we
take
into
account
there.
I
don't
think
that
there's
gonna
be
any
change
there.
D
I
also
haven't
seen
that
behavior
in
any
other
environment,
so
it's
kind
of
difficult
to
troubleshoot
yeah,
but
but
no,
the
main
thing
here
is
actually
a
change
that
that
I
made
upstream
related
to
how
it
defaults
the
the
registry.
So
right
now
like
we
have
some
things
where
it
will
default
dependencies
to
docker
hub
and
we
basically
want
to
say
just
use
whatever
like
use,
whatever's
provided
rather
than
appending
docker
hub
to
the
beginning
of
stuff.
D
So
that's
the
main
thing
that
we
need
to
update
and
that's
related
to
a
new
cli
command.
That's
going
to
be
present
in
1.2,
that's
upgrading
provider
versions.
Currently
it
actually
upgrades
and
appends
something
like
docker
to
it.
You
know
so.
A
Was
there
was
there
a
specific
issue
on
that
upgrade
functionality
being
added,
or
is
that
already
is
that
already
in.
A
Okay:
okay,
excellent
cool,
okay,
anything
else
on
1.2
or
roadmap
beyond
1.2
picking
any.
A
Thoughts,
all
right
cool
you
know,
feel
free
to
always
reach
out
on
slack
as
well
too.
If
you
have
ideas
about
prioritization
or
issues
that
you
you'd
like
to
see,
get
included
in
we're
always
happy
to
for
new
contributors
to
take
on
issues
as
well,
too.
We've
seen
some
really
good
contributions
from
folks
out
in
the
community
over
the
past
few
months.
We're
really
happy
to
continue
that
trend
and
support
folks
as
well
too,
so
all
right
so
yeah.
A
Once
again,
we
will
be
working
towards
april
27th
for
the
the
next
1.2
release.
Thanks
everybody
for
sharing
the
status
and
everything
on
that
release
and
roadmap
going
forward,
then
did
you
want
to
talk
about
the
1.1?
The
only
triple
one
patch
release
from
yesterday.
D
Sure
I
won't
go
into
too
much
depth
here,
because
there's
pretty
good
write-ups
on
all
the
changes,
but
essentially
we
have
a
1.1
patch
1.1.1
patch
release
available.
That
makes
it
possible
to
run
crossplane
on
platforms
that
are
using
run
c,
1.0
rc
93,
which
is
the
most
recent
release.
D
Long
story
short
there's
an
upgrade
and
or
a
change,
I
guess
maybe
not
an
upgrade
and
how
containers
are
initialized
that
sets
the
sets
up
the
user
before
changing
to
the
working
directory
specified
for
that
container
image.
So
the
distro
list,
non-root
based
image
we
were
using,
was
using
the
home
slash,
non-root
directory,
which
only
had
execute
permissions
which
are
required
to
change
to
that
directory
for
the
non-root
user,
so
in
some
environments
folks
had
to
run
with
other
uids.
D
So
this
works
around
that
also
fixes
a
number
of
other
minor
bugs
that
are
outlined
in
the
release
notes.
I
will
also
note
that
run
c
is
fixing
this
behavior
as
well,
but
we've
had
a
number
of
folks
that
are
actually
you
know,
running
crossplane
had
the
container
runtime
updated
underneath
them,
and
then
it
start
failing.
So
obviously
we
want
to
work
with
with
rc93.
So
that's
the
motivation
here
and
it's
available
and
pretty
thoroughly
tested
at
this
point.
C
B
A
Cool
yep,
so
1.1.1
was
released
yesterday.
The
first
patch
release
on
1.1-
and
you
know
it's
great
to
stay
on
top
of
you
know,
quality
and
issues
affecting
our
our
previous
releases.
So
thanks.
A
Okay,
I
think
we
can
maybe
move
on
then
from
the
milestones
and
releases
and
go
into
the
community
topics
section
down
here
there
we
go
so
dan.
You
wanna
give
us
an
update
on
some
of
the
recent
live
streams
or
upcoming
events
and
stuff
that
we're
doing.
D
Yeah,
so
I
think
for
the
past
few
community
meetings,
I've
said:
there's
an
upcoming
live
stream
with
flux,
it's
still
upcoming,
but
we
already
have
the
the
demo
built
out.
So
it's
really
just
coordinating
with
some
folks
on
that
side.
So,
if
you're
using
flux,
this
will
definitely
be
a
cool
one
to
tune
in
for
and
also
just
in
general,
you
know
using
get
ops
with
crossplane.
It
kind
of
illustrates
a
lot
of
the
value
in
that
also
we're
going
to
have
some
upcoming
streams
with
equinix.
D
This
is
mostly
based
around
their
fabric
product,
which
allows
you
to
kind
of
connect,
different
cloud
providers
and
orchestrating
that
with
crossplane,
so
keep
an
eye
on
some
of
those.
Those
will
probably
be
split
between
our
youtube
channels
and
their
various
marketing,
slash,
developer,
advocacy
channels,
so
we'll
make
sure
to
make
some
noise
about
that
and
slack
and
twitter
and
stuff
like
that.
A
Awesome
dana
I'm
particularly
excited
about
the
flux,
v2
stream
as
well
too,
because
as
much
too
I
I
wrote
the
like
a
crossfit
configuration
that
was
using
flux
v1
recently,
so
I'm
gonna.
I
might
need
to
watch
this
to
learn
how
to
upgrade
and
use
v2
as
well.
A
That's
an
improvement.
Thank
you,
dan
cool,
okay,
a
quick
note
on
the
cncf
incubation
process.
We
are
still
moving
ahead
and
made
some
really
good
progress
last
week,
so
the
proposal
has
been
open
upstream
on
the
technical
oversight
committee
repo
for
a
couple
weeks
now,
but
the
latest
updates
are
that
we
have
completed
a
first
draft
of
the
due
diligence
document
which
goes
into
a
number
of
areas
and
details
around
the
project
and
architecture
and
quality
and
all
sorts
of
stuff.
A
So
the
due
diligence
document
is
available
for
review
and
it's
been
passed
along
to
the
special
interest
group,
the
app
delivery
that
is
in
charge
of
of
doing
the
diligence
with
us
and
vetting
the
project,
so
we're
trying
to
make
as
much
progress
on
that
as
fast
as
we
can
and
can
kind
of
keep
pushing
all
the
stakeholders
in
that.
A
So
that
we
can
get
that
to
the
finish
line
also
available
is
a
presentation
on
the
incubation
proposal
that
we
were
scheduled
to
give
yesterday
morning
to
the
big
app
delivery
and
unfortunately,
the
the
meeting
was
cancelled
and
moved
to
next
week
last
minute,
so
we
were
not
able
to
present
yesterday
but
we're
on
the
schedule.
First
thing
for
april
14th,
so
one
week
from
yesterday.
A
So
we
are
hoping
to
get
all
this
done
in
time
for
coupon,
eu
timeline
is
tight,
but
we
are
pushing.
C
A
On
you
know
all
the
stakeholders
as
much
as
we
can
to
keep
it
all
moving
all
right,
lfx
mentorship
with
with
our
minty
rahul,
just
met
with
them
in
in
synced.
Up
for
this
rahul,
do
you
want
to
give
us
a
status
update
on
all
the
work.
C
C
Yeah
sure
I'm
audible,
yep
sounds
good
yeah,
so
I
have
been
working
on
priority
and
that
has
been
completed
and
the
pr
hasn't
merged
and
now
the
next
I
had
also
completed
that
code
cross
upgrade
testing
which
basically
upgrades
from
the
stable
version
to
the
master
version
test.
If
everything
is
working,
fine
and
that
has
also
been
merged-
and
now
the
next
step
assets
were
written,
that
publicating
a
provider
the
functionality.
I
won't
go
into
much
there,
but
I'll
start
with
one
pager,
and
you
would
see
the
pr
soon.
A
Yeah,
it's
awesome
and
yeah,
so
it's
really
good
that
now
we
have
regular
regular
recurring,
like
nightly,
runs
of
the
upgrade
testing
that
rahul
has
built
for
us
to
make
sure
that
we're
able
to
upgrade
the
providers
and
upgrade
core
crossplane
as
well
too.
So
if
we
have
a
commit
to
the
main
branches
that
breaks
or
regresses
the
upgrade
success,
then
we'll
know
about
it.
You
know
within
within
24
hours
of
that
commit.
So
that's
that's
been
really
nice
to
have
that
validation
on
a
recurring
basis.
A
All
right
and
then
last
note
here
on
community
day,
you
know
it's
on
may
4th
as
part
of
the
zero
day
event
for
for
kubecon
schedules
up
there
and
available
and
the
recordings
for
all
the
talks
where
were
due
yesterday,
I
think
was-
was
the
deadline,
so
I
know
everybody
pushed
to
make
that
happen
and
to
get
the
recordings
done
and
talks
finished.
A
A
Okay,
are
there
any
other
topics
that
were
not
put
into
the
agenda
doc
here
anything
else.
That's
on
people's.
A
A
All
right,
okay,
I
don't
see
any
other
particular
pr's
that
we
need
to
go
over
or
any
other
deeper
technical
discussions.
So
with
no
remaining
agenda
items
then
I
think
we
can
go
ahead
and
adjourn
for
this
this
week
here
we'll
keep
on
working
towards
the
1.2
release,
where
we'll
be
online
on
slack
and
to
keep
discussing
things
and
work
on
stuff
before
the
next
community
meeting
two
weeks
from
now
awesome
all
right
thanks,
everybody
take.