►
From YouTube: 2021-02-01 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
february
1st
2021
cross,
plane
community
meeting.
I
think
this
maybe
is
the
no
no,
it's
not
the
first
one
we've
done
of
the
year.
I
know
we
did
not
have
one
last
time,
but
we
did
do
one
january
4th
all
right
sweet,
so
not
the
first
one
of
the
year
but
yeah.
A
So,
let's
get
started
how
we
normally
do
with
move
off,
making
suggestions,
I'm
going
to
do
the
like
the
roadmap
here,
so
we
put
out
a
1.0
or
the
1.0
right
before
the
holidays,
and
that
was
really
good
to
get
that
out
there
and
have
stable
apis
and
be
production,
ready,
etc.
A
The
1.1
milestone
here
we've
been
working
towards
it
and
we
made
some
progress
in
a
couple
different
areas.
I
want
to
talk
a
little
bit
about
some
of
the
status
of
some
of
the
areas
we're
making
investments
in
and
also
talk
about,
the
release
schedule
as
well
too.
For
that,
I
think,
maybe
I
think
the
project
board
might
be
fairly
up-to-date.
I
believe,
but
we
might,
it
might
be
good
to
just
talk
through
some
of
the
high-level
feature
areas
further
further
down
in
the
agenda
as
well
too.
A
Let
me
just
take
a
quick
look
at
this
here:
yeah,
it's
provider,
acceleration
stuff
or
compositions
multi-language
support
yeah.
Okay.
I
think
this
matches
the
feature
areas
down
below.
So,
let's
just
let's
just
dive
into
that,
I
guess
and
talk
about
status
and
things.
A
C
Sure
so
most
of
the
stuff
is
around.
I
guess
provider
authentication
right
now.
So,
if
you're
familiar
with
the
current
model,
we
mostly
suggest
using
kubernetes
secrets
to
provide
credentials
and
reference
them
from
a
prior
provider
config
for
each
provider,
which
means
you
know
for
each
resource.
You
provision,
you
can
specify
the
credentials.
You
want
the
provider
to
use
to
execute
that
with
that
model
right.
It
requires
that
you
store
your
your
secrets
in
that
cd
or,
if
you
have
a
different,
you
know
backing
store.
C
You
could
use
that
as
well,
which
is
fine
in
some
cases,
but
especially
if
you're
running
in
kind
of
an
untrusted
environment,
you
definitely
do
not
want
to
be.
You
know,
writing
secrets
to
disk
or
scoring
them
a
net
cd
or
something
like
that.
So
we've
done
some
work
in
the
past,
enable
things
like
irsa
if
you're
running
on
eks,
which
seems
a
lot
of
folks,
were
interested
in,
and
we
want
to
extend
this
model
a
little
bit
further.
C
So
different
cloud
providers,
if
you're
using
their
hosted
solution,
will
often
have
something
like
irsa
or
workload,
identity
that
allows
you
to
have
your
credentials
injected
into
the
file
system
of
the
container
for
the
provider
and
we
kind
of
were
manually
supporting
that
by
just
adding
support
in
each
provider
and
we
have
an
injected
identity
source.
But
that's
that's
not
super
flexible.
We
are
only
kind
of
adhering
to
these
certain
environment
variables,
for
instance
with
irsa
that
required.
C
You
to
you
know,
use
the
specific
paths
that
the
eks
mutating
web
hook
does
to
put
the
credentials
in
the
file
system
and
we
wanted.
Basically,
the
ability
to
have
for
any
provider,
to
you
know,
have
an
external
system
right
thanks
to
the
file
system
or
provide
via
environment
variables,
or
something
like
that
and
be
able
to
generically
do
that.
C
C
So
you
need
to
be
able
to
put
annotations
on
the
pod
to
be
able
to
do
that.
So,
if
you're
familiar
with
the
controller
config,
it's
basically
a
way
to
modify
the
deployment
that
gets
created
for
a
provider
that
you
install
so
first
step.
These
are
kind
of
listed
in
order
of
how
things
are
implemented.
C
First
step
is
passing
annotations
to
the
provider
pod.
So
right
now
you
can
pass
them
to
the
service
count
or
the
deployment,
but
not
to
the
pod,
and
we
want
to
be
able
to
do
that.
So
that's
a
pretty
small
change
and
then
with
crossplane
runtime.
We
want
to
make
it
really
easy
to
use
these
different
sources
so
for
secret
file,
system
and
environment.
C
We
want
to
have
some
kind
of
like
default
extractors
to
get
those
out,
and
so
now
you'll
be
able
to
have
like
a
provider,
config,
ref
and
say
source
fs
and
specify
the
path
or
something
like
that,
and
then
I've
also
got
a
work
in
progress,
implementation
in
provider
aws,
so
yeah
we're.
Basically,
just
trying
to
support
more
ways
to
provide
provider
credentials
and
if
there
are
some
that
you
don't
think
are
accounted
for
by
this
definitely
open
issues
reach
out
this.
A
Yeah
thanks
for
that
dan,
I
don't
think
that's
an
important
aspect
of
this,
too,
is
that
you
know
the
additional
affordances
that
are
being
added
to
support.
You
know
more
secure
scenarios
and
and
keeping
credentials
out
of
the
cluster
etc
is
is
all
really
good,
but
you
know
having
folks
like
real
use
cases.
You
know
kind
of
the
feedback
from
that
from
the
community
is
super
important
to
be
able
to
understand.
A
A
Dan
cool,
so
that's
exactly
a
solid
thing,
that's
being
added
in
1.1
that
area
of
investment
there
you
know
we're
we're
still
investing
in
the
you
know:
coverage
code
generation
provider,
acceleration
stuff
move
off
in
kc.
Do
you
all
want
to
get
us
updated
on
the
those
areas
that
we're
putting
some
work
into
as
well.
B
Yeah,
I
can
get
a
quick
update,
so
I'm
mostly
working
on
a
list
code
generation
with
the
folks
from
ack.
So
right
now
we
have
the
full
instructions,
step
by
step
that
you
can
start.
You
know
following
and
like
implementing
additional
resources
that
you
need
and
a
lot
of
folks
income
in
the
community
actually
followed
it
and
like
opened
prs.
B
B
If
you
need
like
an
additional
resource,
we
can
do
it
via
code
generation.
Now.
A
And
you
often
all
these
are
community
contributions.
B
Yeah
yeah,
it's.
B
I
encourage
people
like
to
try
and
see
like
you
know
how
they
can
add
a
new
resource.
It's
it's,
it's
a
pretty
good
contribution
and
like
not
a
really
hard
one.
So,
like
you
know,
there's
only
some
custom
parts
that
you
you
need
to
re.
You
need
to
write
and
there's
also
one
work
in
progress.
Pr
that
I
opened
waiting
for
review
that
updates
this
code
generation
document
with
more
details
about
testing
it
testing
what
you
wrote.
B
So
it
should
be,
like
you
know,
even
more
straightforward
to
do
that
when
this
pr
on
this
blog
is
merged.
A
Is
there
anything
blocking
that
that
pr
mo
off
or
you
just
haven't
gotten
the
feedback
yet
yeah?
I.
A
Cool
well
yeah.
I
definitely
think
that
was
a
a
good
resource
as
well
too
of
having
this.
Basically,
the
guide
about
how
to
use
code
generation
to
you
know,
get
a
new
feature
or
a
new
service
resource
bootstrapped,
and
then
you
know
the
parts
you
need
to
do
to
accomplish
like
by
hands
to
get
it
to
the
finish
line.
I
think,
having
this
is,
is
really
really
important
to
be
able
to
enable
or
empower
folks
from
the
community
to
be
able
to
add
their
own
resources
as
well
too.
A
A
Muaf
is
that
all
for
for
you
on
your
side,
yeah,
I
think
that's
it
cool
casey.
Are
you?
Do
you
want
to
give
us
an
update
on
all
the
things
that
you've
been
putting
work
into
as
well.
D
Yeah
so
since
ack
is
going
great,
we
are
the
community.
Demo
was
for
an
aws
provider,
but
we
don't
want
to
move
forward
with
using
terraform
code
generation.
D
For
that
at
the
moment,
since
ack
is
looking
good,
so
we
decided
to
focus
on
long
tail
providers,
starting
with
vsphere
phil,
pulled
some
data
from
terraform,
and
that
was
the
that
was
the
provider
that
was
the
most
popular
outside
of
aws,
azure
and
google,
and
so
I've
been
reworking
the
the
code
generation
to
work
with
like
arbitrary
terraform
providers,
and
so
I
have
you
know:
resources
generated
for
vsphere
and
provider
config
and
now
I'm
testing
to
see
if
it
actually
works
using
vc
sim,
which
is
a
a
go
program
that
simulates
the
vsphere
server.
D
And
there
are
a
few
resources
that
still
need
additional
work.
They
have
the
same
issues
that
that
prevented
us
from
generating
some
of
the
aws
resources,
so
we'll
also
get
those
bugs
fixed
as
a
you
know,
in
the
process
of
getting
the
vcr
director
done.
A
Nice
casey,
that's
awesome
man.
I
definitely
like
that.
I,
like
the
scenarios
that
this
opens
up
as
well
too,
of
like
more
on-premises
scenarios
too,
to
be
able
to
like
provision
and
manage
you
know:
vm
or
virtual
machine
resources
on
an
on-premises
environment.
So
that's
that's
really
cool.
Were
there
any
big
speed
bumps?
Do
you
hit
with,
like
you
know,
using
your
code
gen
pipeline
to
to
do
things
for
a
new
terraform
provider,
or
is
it
kind
of
like
the
generalities
they're
starting
to
get
good
coverage
and
not
to
me
unexpected
things.
D
No,
I
think,
yeah,
it's
mostly
been
pretty
changes,
just
generalizing
things
in
the
the
templating
layer
that
that
were
that
I
kind
of
put
in
place
by
hand
for
aws.
D
The
only
thing
that
I
haven't
built
yet
that
we
will
need
to
build
to
you
know,
have
the
click
a
button
and
get
a
provider
tool
is
the
ability
to
each
terraform
provider?
Has
the
the
provider
itself
has
a
a
type
that
is
similar
to
the
resource
type
specified
in
the
same
kind
of
schema,
but
the
shape
is
different
because
it's
not
you
know,
we
don't
have
for
provider
and
app
provider
spec
in
status
fields,
and
we
have
secret
management
kind
of
baked
into
that
as
well.
D
So,
in
the
case
of
vsphere,
I
wrote
that
for
him
by
hand
and
then
the
next
provider
that
we
build
we'll
actually
automate
that
piece
as
well.
A
Got
it
yeah,
really
cool
man?
I
definitely
like
the
the
focus
here
on
you
know.
Another
provider
here
that
doesn't
have
there's
no
coverage,
like
doesn't
even
exist
in
cosplaying,
yet
it's
that's,
really
exciting,
awesome,
cool
and
then
another
focus
area
for
the
1.1
milestone
here
is
around
improvements
to
composition.
A
Definitely
one
that
sticks
out
of
my
head.
So
far,
that's
I
think
has
been
merged.
Is
kellen's
investment
there
in
the
bi-directional
patching
that
yeah
it
is
merged
right.
So
that
is
that's
really
amazing
to
see
a
very
non-trivial.
You
know
improvement
to
like
a
real
feature
in
the
composition
layer,
so
that
was
really
cool
to
see
that
kellen
was
there.
Was
there
anything
big
that
you
learned
from
that
experience
there
kellen
or
like
getting
getting
that
that
feature
into
into
maine?
A
It
was
just
kind
of
learning
how
to
claim
you
know
controller
and
com
composite
controller
kind
of
that
functionality,
so
it
was
nice
to
kind
of
get
into
the
internals
there
so
and
to
see
how
some
of
those
are
generated.
So
that
way
we
can
have
like
actual
like
statuses
on
xrds
now,
and
you
know
patch
information
back,
so
it's
pretty
cool,
definitely
yeah,
and
I
appreciate
that
too.
A
As
a
more
of
a
user
of
the
composition
in
crossplane
and
some
of
the
reference
platforms,
I've
been
building
there
to
get
status.
You
know
kind
of
bubbling
back
this
way
to
you
know
like
up
the
chain.
There
is
it's
gonna,
be
really
useful
like
help
with
troubleshooting
and
understanding.
What's
going
on
deeper
in
the
layers
there
without
having
to
dive,
hop,
hop,
hop,
hop
yeah
for
sure
nice
kellen
great
work
on
that
man
nick
anything
else,
you
wanted
to
add
about
composition
or
improvements
that
we
may
be
making
it
1.1.
E
Nothing
too
much
there
is.
There
is
at
least
two
pr's
in
the
pipeline.
At
the
moment
one
was
my.
I
started
working
on
one
that
would
allow
you
to
reorder
templates
within
a
composition
which
is
not
in
and
of
itself
that
exciting,
but
it
opens
up
the
pathway
to
composition,
revisions
so
letting
you
sort
of
carefully
roll
individual
custom
resources
over
to
a
new
composition
without
necessarily
having
to
sorry
carefully
roll
individual
xrs
over
to
a
new
composition
without
having
to
change
every
xr.
E
That's
using
a
particular
composition,
if
that
makes
sense,
so
new
versions
of
existing
compositions.
That's
I.
I
wasn't
super
happy
with
the
implementation
to
begin
with,
and
it's
going
to
need
a
pretty
big
refactor.
I
think
now
that
kellen's
pr
has
merged,
so
no
no
guarantees
that
that'll
make
it
for
1.1.
It's
not
a
priority
for
that
release,
but
it
might
it's
likely
to.
There
is
also
let
me
put
a
real,
quick
ben
agricola
open
to
pr.
E
It
was
also
a
competition
improvement,
and
I
I'm
gonna
review
this
week,
but
I
can't
right
now
remember
what
it
is.
Oh,
it
was
allowing
the
sort
of
allowing
it
to
patch
from
multiple
fields
into
one
or
two
basically
aggregate
together
the
output
of
multiple
fields,
a
specific
place.
This
is
being
asked
for
in
a
couple
of
time,
places
is
when
building
iam
policies.
E
Sometimes
you
might
want
to
put
like
the
ar
end
of
something
in
an
am
policy,
and
then
there's
one
or
two
other
things
that
you
want
to
sort
of
inject
into
an
iam
policy.
We
already
support
sort
of
a
very
basic
form
of
templating
there,
where
we'll.
Just
let
you
do
a
go
string
format,
but
we
only
let
you
have
one
string
input
at
the
moment,
so
we've
been
playing
around
with
it.
E
We
don't
we
no.
There
is
a
pr
open
for
individual
sort
of
little
feature
improvements
like
this
to
to
composition.
We
don't
require
that
folks
open
like
a
design
dock
or
anything.
We
typically
play
around
with
some
different
approaches
on
the
on
the
issue
which.
C
E
Did
in
this
case,
so
you
can
check
that
check
the
pr
out
that
should
look
back
to
the
issue
and
now
ben
has
a
pr.
Over
now
I
haven't
looked
at
it
at
all.
I
think
he
said
it
might
have
been
a.
It
might
be.
A
draft
still.
A
Awesome
yeah,
that's
great
to
see
another
investment
there
from
the
from
the
broader
community
to
into
more
features
for
composition.
So
that's
fantastic.
I
expect
to
use
all
of
those
myself
so
awesome
and
then
harsh
mentioned
in
the
chat
too,
that
you
started
working
on
the
gcp
secrets
manager
is
there?
Is
there?
Do
you
want
to
expand
a
little
bit
more
on
that
one
harsh.
E
Yeah
jared,
so
I
started
to
work
on
it
and,
like
I
got.
D
Bit
stuck
with
the
proto
definitions
like
with
the
secret
manager
like
there
is
they've
used
particular
types
of
one-off
from
google,
and
so
I'm
trying
to
figure
that
out.
If
I
get
stuck
I'll
hit,
you
guys
up
on
slack.
A
Awesome
sounds
good
yeah
and
thanks
for
taking
that
on
that'll
be
that'll,
be
a
good
addition
as
well
too
cool
and
then
phil
normally
updates
us
on
multi-language
support,
and
you
know
the
ongoing
collaboration
with
amazon
and
the
cdc
dk.
I
think
it
does.
Anyone
have
an
update
on
that
that
and
phil's
stead.
I
don't
I
don't
know
the
current
status
myself.
E
I'm
afraid
I
don't
either.
I
know
there
have
been
ongoing
meetings.
I
just
saw
one
getter
moved
around
on
the
on
the
calendar,
but
I'm
not
sure
of
the
status.
I
don't
know
if
there's
been
too
many
developments
this
year,
I
think
that
they
haven't
really
had
time
to
wrap
back
up
as
my
guess,
but
don't
quote
me
on
that.
B
Yeah
yeah,
I
think
the
latest
update
was
like
fill
enabling
level
2
objects
like
it.
It's
basically
easier
an
energy
abstraction
for
cdks
to
use
crossplane
objects,
but
I
think
that's
pretty
much
it.
A
So
that's
good
and
then
the
in
terms
of
a
1.1
release
schedule
there.
I
recall
a
date
being
mentioned
on
that,
but
I
don't
remember
off
top
of
my
head
or
where
that
was
published
nick,
do
you
have
an
idea
of
what
we're
targeting
there
for
a
1.1
release.
E
That's
a
good
question.
I
was
thinking
about
it
the
other
day,
given
that
we
released
1.0
on
the
15th,
it
would
actually
be
due
pretty
soon.
I
know
that
dan
has
just
sort
of
revamped
our
release
schedule
and
I
believe
we
were
going
for
eight
weeks
between
releases
now,
so
we're
kind
of
we're
going
to
release
a
little
bit
slower
than
we
were
previously
with
more
feature
and
and
sort
of
code
freeze
at
the
end
than
we
have
historically
had
long.
B
E
Guess
it
depends
if
you
say
we're
taking
it
from
eight
weeks
from
the
start
of
the
year,
then
february,
more
realistically,
probably
about
two
weeks
from
now
I'd
say.
A
Got
it
and
did
you
was
that
the
clarification
around
like
lts
and
and
on
scheduling
for,
like
support
and
stuff,
like
that
too
yeah.
C
Like
that
one
here,
there's
actually
I
realize
there's
a
few
things
we
should
probably
cherry
pick
we're
gonna.
Do
cherry
pick
back
to
the
the
like
1.0
docs,
more
frequently
now
as
we
as
we
move
forward
since
we'll
have
more
longer
support
for
stuff.
So
this
is
just
on
the
master
branch
right
now,
but
I'll
go
ahead
and
link
it
regardless.
A
Okay,
cool
sounds
good
yeah,
so
we
are
working
towards
that.
1.1
we've
already
got
some
features
in
there
and
then
we
got
status
updates
for
pretty
much
everything.
That's
kind
of
within
the
charter
of
that
milestone.
There
so
sounds
like
in
yeah.
I
think,
like
kneeling
down
a
more
concrete
release.
Date
would
be
beneficial
but
kind
of
as
we're
making
a
transition
here
from
monthly
to
a
bit
of
a
slower
cadence
to
get
bigger
features
in
there.
A
We,
you
know
we'll
we'll
firm,
that
up
cool
anything
else
on
1.1
from
from
people
yeah.
I
don't
remember
asking
my
dog
down
there.
Okay,
I
don't
know
why
she's
barking.
A
Okay,
coach:
let's
move
on
ahead
to
the
community
topics
section,
the
the
team
did
a
write
up
and
have
already
implemented
a
on
duty
rotation
and
it's,
I
think
it's
working
really
well
as
well
too.
I
think
that
was
a
fantastic
idea.
Here
is
a
link
to
oh.
I
don't
know
why
I
put
a
specific
hash
in
there,
but
here's
a
link
to
kind
of
the
expectations,
the
schedule
everything
there
does.
A
B
And
I
think
I
I
think
I
like
it
like
my
week-
wasn't
like
very
busy,
so
I
had
time
to
look
at
like
other
things,
as
well
with
the
peace
of
mind
like
in
normal
days.
You
kind
of
have,
like
you
know,
the
like
the
future
requests
and
all
that
stuff
like
you
know,
you
have
to
work
on
it,
but
on
duty,
it's
kind
of
like
more
cold,
so
it
kind
of
helps
other
things
as
well.
E
I
think
my
only
observation
so
far
is
that
all
of
us,
who've
done
on
duty,
including
myself,
have
fallen
into
the
trap
of
in
our
spare
time
around
on
duty
working
on
not
stuff.
That's
really
improving
the
future
of
our
duty
for
other
engineers,
it's
very
easy
to
follow
the
track
for
being
like.
Oh,
I
have
this
half
completed
pr.
That's
unrelated
I'll
go!
A
Yeah,
I
definitely
I
I
think
this
is
a
great
idea
that
we
did
this,
where
you
know
we're
kind
of
putting
ourselves
putting
the
right
resources
in
the
place
to
make
sure
that
the
community
is
getting
support,
they
need
and
they
pull
requests
or
getting
reviews,
and
you
know
that
that
effort
is
being
load
balanced,
a
bit
as
well
too.
So
I
love
the
intention
here
and
I'm
really
happy
that
we,
you
know,
drove
to
make
that
happen
and
have
codified
it
and
are
following
up
on
it.
A
So
that's
great,
I'm
really
happy
that
that
you
know
this
is
going
to
have
a
positive
effect
for
for
us.
So
that's
that's.
Amazing.
A
Cool
all
right,
I
have
a
quick
update
on
the
you
know.
Docker
hub
is
what
I
meant
to
say
here:
docker
hub
open
source
project
application,
so
I
applied
some
time
before
the
holidays.
I
don't
know
exactly
when
to.
Basically
you
know
grant
status
for
the
crossplane
project
within
docker
hub
as
an
open
source
project
which
makes
it
free.
D
A
The
throttling
and
quotas
etc
that
they
put
on
have
recently
added
to
projects
or
containers
being
images
being
hosted
in
docker
hub.
I
did
hear
back
from
them
and
recently
just
followed
up
with
them
a
couple
days
ago
last
week
I
think,
and
then
so
they'll
be
they
had
a
long
tale
of
or
a
big
set
of
projects.
That's
all
you
know
submitted
applications
for
this
status
and
so
they're
getting
to
ours.
What
they
said
is
within
the
next
week.
A
So
hopefully
we'll
get
an
update
about
that,
and
and
be
you
know,
granted
that
status.
One
thing
to
that's
a
bit
a
bit
open-ended
right
now
is
that
they
have
a
requirement
that
the
project
isn't
funded
by
a
commercial
organization,
and
so
I
kind
of
pushed
back
on
that
and
asked
for
some
clarification
as
well
too,
and
it's
still
not
very
clear,
they're
being
fairly
vague
about
that.
So
I
don't
really
know
what
the
requirements
are
for
that
and
the
impact
etc
and
any
sort
of
relationships.
A
That's
like
organizations
that
you
know
have
employees
contributing
to
it
and
that
you
know
how
that
gets
into
funding.
So
we
need
to
learn
a
bit
more
about
that.
It
seems
like
the
way
they
originally
described.
A
It
would
would
basically
cut
out
all
a
lot
of
open
source
projects
unless
it's
just
you
know
like
a
single
project
made
by
a
single
person
out
of
love,
so
I'm
not
sure
exactly
what
the
requirement
is
and
we'll
have
to
learn
a
little
bit
more,
but
definitely,
I
think,
there's
it's
over
time,
be
nice
to
potentially
find
you
know,
alternate
solutions
to
hosting
a
doctor
hub,
and
the
up
on
cloud
registry,
I
think
is,
is
very,
very
compelling
for
that
cool,
okay,
so
any
other
community
topics
then.
A
All
right!
Well,
yes,
so
if
we
didn't
have
do
we
have
any
other
pr's
or
anything
that
folks
wanted
to
bring
up
here,
any
prs
that
needed
some
attention
or
it's
a
couple
comments.
A
On
all
right,
well,
that's
everything!
That's
on
the
agenda
document.
Then
we've
gone
through
all
of
our
items
there,
so
we'll
keep
making
progress
on
the
1.1
milestone
there
and
all
of
the
interesting
features
here
that
we've
been
discussing
so
great
work
from
everybody
who's.
You
know
contributing
in
all
sorts
of
shapes
and
ways
to
the
crossplane
project,
and
we
will
see
everybody
on
stock.
Then
awesome
thanks.