►
From YouTube: 2019-06-25 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
June
25th
2009
crossplane
community
meeting,
so
we
will
go
ahead
and
start
with
a
bit
of
a
check
up
on
the
current
milestone
and
the
items
in
progress
and
some
of
the
stickier
issues
and
such
so
just
a
bit
of
a
reminder
here.
We
are
currently
in
the
0.3
milestone,
and
there
are
two
big
focuses
that
we
have
left
concerning
this
current
milestone.
One
of
them
is,
you
know
we
took
a
step
back
and
we
thought
about.
A
You
know
what
are
the
big
items
or
the
looming
questions
or
some
of
the
unanswered
unanswered
questions
that
we
have
now
that
may
pose
the
biggest
risk
or
things
that
we
want
to
front-load
and
D
risk
early
on
here.
So
there
we're
doing
some
design
investigations
on
some
of
the
hairier
issues
here
to
kind
of
get
on
top
of
those
and
kind
of
hopefully
flesh
out.
A
A
lot
of
the
remaining
paths
for
the
for
subsequent
milestones,
so
that'll
be
a
big
focus
in
the
in
the
new
0.3
milestone
that
we'll
look
at
in
just
a
second
and
then,
as
we
talked
in
a
previous
community
meeting,
we
are
also
taking
a
focus
on
you
know:
engineering,
quality
and
process
stuff.
Some,
you
know
reef
actors
of
the
codebase
as
we've
kind
of
iterated
over
it.
A
You
know,
since
the
beginning
of
the
project's
latter
late
last
year-
and
you
know-
we've
also
identified
some
items
that
are
obstacles
or
difficulties
for
new
contributors
to
get
involved
in
the
project
or
for
new
users
of
the
project
as
well.
So
kind
of
a
quality
focus
and
an
engineering
focus
is
the
other
side
of
the
coin
here
for
the
0.3
milestone.
So
let's
go
ahead
and
I
think
the
project
board
is
gives
us
the
best
view.
Honestly
I
went
and
organized
this
product
project
board
just
earlier
today
before
the
meeting
here.
A
That
does
it
look
like
Nick's
here
so
I'll
speak
through
some
of
his
stuff,
because
I
am
aware
of
what's
going
on
there.
So
one
of
the
that's
in
the
currently
in
review.
We
have
simple
requests
open,
so
one
of
them
that
Nick
is
working
on
is
we
have
a
single
single
controller
that
has
a
general
implementation
for
resource
claims
and
resource
classes
and
binding
concrete
resources
to
your
abstract
resources,
such
as
a
claim
for
a
Redis
service
and
then
creating
instantiating
deploying
and
binding
a
concrete.
A
A
So
that's
I
like
that
change,
because
that
affects
a
lot
of
different
types.
Since
that's
a
core
controller,
that's
used,
you
know,
reused
for
many
of
the
different
types,
so
I
think
that's
fantastic,
and
so
Nick
is
also
tackling
with
that
refactor.
That
touches
a
lot
of
other
parts
of
the
codebase
he's
also
tackling
a
couple
of
other
issues,
so
those
are
all
in
review
together.
A
Marcus
Marcus
took
a
pass
at
as
one
of
the
newer
contributors.
The
crossplane
community
Marcus
took
a
pass
at
some
of
our
documentation
that
had
some
issues
with
it.
He
already
completed
updating
our
examples
for
google
for
using
google
cloud
and
then
now
Marcus
is
as
they
pull
requests
open
for
AWS
as
well
Marcus.
Do
you
want
to
share
anything
about
that,
specifically.
B
It's
mostly
straight
forward,
moving
the
old
yield
compute
workloads
to
the
newer,
kubernetes,
app
workloads
and
updating
the
documentation
for
that
along
the
way
it
found
like
a
few
things
that
I
thought
made,
made
it
easier
to
work
with
so
the
instructions
for
getting
started
with
AWS
we're
kind
of
elaborate,
a
lot
of
things
that
had
to
be
done
in
the
AWS
cloud,
UI
and
so
that's
been.
Those
instructions
are
still
there.
B
But
if
you
want
to
run
a
script,
there's
a
AWS
credentials,
SH
script
that
matches
what
I
did
with
the
GCP
provisioning
script,
and
so
it
just
makes
it
easier
to
get
started
with
the
examples.
If
you
run
that
script
sets
up
the
sets
up,
the
VPC
sets
up
the
cloud
formation
stacks.
That's
up
several
of
the
things
in
addition
to
that,
I
also
found
a
few
places
where
the
where
say
a
cloud
formation
stack
could
possibly
fail
and
it
wouldn't
get
caught,
and
another
minor
tweak
was
the
output
columns
on
on
the
provider.
B
Resources
I
found
myself
needing
to
get
access
to
the
secret
that
was
associated
with
a
provider
and
also
to
figure
out
what
the
project
ID
or
the
region
associated
with
a
provider
was,
and
so
I
added
those
columns
either
as
the
native
or
as
the
standard
columns
or
as
the
wide
columns
available
I.
Don't
think,
there's
anything
too
much
beyond
that.
A
I
love,
in
addition
to
you,
know
improving
the
quality,
accuracy
and
ease
of
use
for
the
you
know,
documentation
and
user
examples
here
to
get
your
new
users
that
are
new
to
the
crossplane
project
and
platform.
You
know,
give
them
a
better
experience.
You
know,
I
also
really
like
your
attention
that
you're
taking
there
Marcus
to
automation
is
well
where
you're
you're
writing
scripts,
or
you
know,
writing
automation
to
improve.
A
You
know
to
decrease
the
burden
or
a
number
of
manual
steps
that
are
required
and
kind
of
setting
up
some
environments
there
and
I'm,
hoping
that
we
can
continue.
You
know
in
a
general,
you
know
a
general
direction
of
the
project
to
be
able
to
continue
to
automate
everything
really
of
you
know
decreasing
any
manual
step
or
even
some
of
the
scripts.
You
know
codify
those
into
our
controllers,
maybe
as
well
as
in
the
future.
So
that's
attention
to
automation
and
ease
of
use.
I
really
appreciate.
I
think
the
community
has
whole
benefits
from
it.
A
The
pattern
is
well
documented
that
new
contributors
that
want
to
add
support
for
new
resources
and
new
cloud
providers
new
serve,
is
that
they'll
be
able
to
easily
write
a
more
robust
controller
as
well
if
needed,
and
so
that
can
only
help
to
improve
the
overall
quality
and
standards
of
the
entire
project.
So
we
are
working
on
that
on
a
number
of
different
fronts
and
you
know
that
ticket
is
in
progress.
A
C
So
I
haven't
been
able
to
do
too
much
work
on
it
recently,
but
I've
kind
of
had
some
conversations
in
slack
that
people
may
have
seen
Nate
kind
of
suggested.
The
implementation
as
sort
of
its
own
separate
controller
I'm,
just
for
sort
of
a
separation
of
responsibilities
there
for
the
different
controllers,
so
I'm
looking
into
what
that
might
look
like
and
also
sort
of
how
the
the
changing
of
the
structure
that
Nick
is
proposing
would
affect
that.
C
So,
from
what
I
understand
my
original
thought
process,
when
we
kind
of
went
with
the
core
controller
method,
it
was
responsible
for
the
binding,
and
that
sort
of
thing
was
that
the
implementation
details
for
the
default
resource
class
should
kind
of
live
in
there.
But
now
I
think
it's
gonna
have
to
be
broken
out
separately,
so
I'm
gonna
be
moving
forward
kind
of
in
that
path.
Yeah.
A
A
So
we
had
talked
about
when
I
had
merged
the
design
for
we're
calling
extensions
into
master
a
few
weeks
ago
that
you
know,
allow
new
applications,
new
collab
fighters,
etc
to
be
their
support
for
them
in
functionality,
for
them
to
be
added
to
the
cross
plane
to
its
control
plane
and
not
having
to
be
built
inside
the
main
cross
plane
repo
in
ship
way,
along
with
the
cross,
plane,
core
functionality
and
it
be
installed.
You
know
at
initial
crosswind
deployment,
time,
etc,
etc.
A
That
is
doing
the
main
reconciliation
and
you
know
main
controller
responsibilities,
and
just
calling
in
to
you
know
simple
code,
simple
functions
that
you've
written
to
be
able
to
manage
your
resource.
You
know
a
very
scoped
way:
Marcus
is
looking
into
the
prototyping
those
types
of
implementations
and
see
what
the
obstacles
are.
What
the
challenges
are?
You
know
how
that
design
is
shaking
out
for
and
we're
scoping
that
to
the
wordpress
example,
since
it's
pretty
it's
a
pretty
constrained
example
and
it
makes
a
mixed
usage
of
resource
claims
and
classes
etc.
A
And
then
just
the
last
thing
here
about
the
project
in
the
milestone
for
0.3
is
that
you
can
see
here
near
the
top
of
the
to-do
column
that
we
have
a
number
of
other
design
tickets
related
here.
So
for
the
whole
extensions
work,
you
know
how
we
do
dependency
resolution,
how
we
upgrade
what's
our
isolation
story,
etc.
That
is
all
work
that
needs
to
be
figured
out
and
then
also
this.
This
one
here
are
351
the
workload
security,
that's
a
huge
topic
that
is
going
to
be
really
important.
A
That
Nick
is
going
to
be
looking
into
soon
and
that
that
is
all
about.
You
know
when
you
bring
up
a
resource,
let's
say
like
a
my
sequel
database
and
how
do
you
first
give
make
sure
that
the
workload
that
wants
to
use
it,
let's
say
WordPress?
How
do
you
give
access
to
the
database
from
WordPress?
You
know
how
can
it
make
sure
how
you
make
sure
that
it
can
connect
to
it
if
the
set
up
the
V,
pcs
or
subnets
or
security
groups,
or
whatever
it
may
be?
How
do
you
do
that,
then?
A
How
you?
How
do
you
do
that
in
a
very
secure
way
as
well,
so
it's
very
scoped
that
only
that
resource
will
be
able
to
access
it
and
it's
not
open
to
you
know
other
other
services
or
other.
You
know,
connections
that
may
want
to
sneak
in
there.
So
that's
really
important
part
of
our
design
and
security
and
ease
of
use
of
the
platform
as
well,
and
so
we
wanted
to
front-load
that
one
and
D
risk
that
in
this
milestone
as
well,
so
we're
looking
forward
to
seeing
what
Nick
comes
up
with
that
one.
A
Okay,
so
I
think
that's
everything
for
0.3.
We
got
a
whole
lot
in
progress
here,
but
we
have
you
know
a
fair
amount
of
contributors
that
are
pitching
in
and
tackling
all
these
things
too.
So
there's
a
whole
lot
of
activity
going
on
in
the
cross
plane
project
right
now-
and
you
know,
I'm-
really
excited
about
all
the
progress
that
we're
making
here.
A
Okay,
so
the
next
topic
I
had
on
the
agenda
today
is
that
coop,
con
Shanghai
is
ongoing.
Right
now,
I
think
it's
in
the
second
or
third
day
right
now,
and
there
were
two
talks
that
members
of
the
cross
Bank
community,
we're
giving
in
Shanghai
the
first
and
that's
why
they're
not
here
at
the
meeting
today,
because
I
think
it's
like
early
in
the
morning,
1
or
2
or
3
a.m.
there
right
now
in
Shanghai,
so
Ilya
I
was
giving
a
talk
about
how
to
extend
the
kubernetes
scheduler
for
multi
Western
multi-cloud
workloads.
A
So
we
had
started
a
lot
of
this
work
and
done
some
design
and
expiration
etcetera
for
cross
plains,
specifically
where
you
have
a
multi
cloud
control
plane
and
you
want
to
make
you
know,
scheduling,
decisions
and
optimize
for
various
attributes,
about
where
you
place
different
resources
in
different
clusters
and
different
clouds.
And
how
do
you
make
sure
that
everything
is
well
connected
and
optimized
etc?
A
So
Ilya
is
giving
a
talk
about
that,
and
the
agenda
document
has
a
link
to
of
it
there
that
you'll
be
able
to
get
the
slide
deck
and
also
the
YouTube
recording
is
well
and
for
cube
con
Barcelona.
Last
month
they
put
up
the
YouTube
recordings
of
the
talks
with
it
before
the
conference
was
even
over.
So
look
by
the
end
of
the
week,
maybe
if
they
keep
up
that
same
pace
that
they
did
for
Barcelona.
Look
at
these
links
here.
A
If
you
want
to
watch
those
talks,
hopefully
by
the
end
of
the
week
and
then
Steve
who's,
giving
a
talk
this
week
about
composability
and
cloud
native
applications
and
how
you
can
take
basic
primitives
and
building
blocks
such
as
a
cross
plane
offers
you
and
composed
them.
As
you
know,
a
unified
set
of
resources
into
higher-level
applications
and
services
so
very
excited
about
both
those
talks
and
I
will
be
watching.
A
Those
youtube
links
this
weekend,
probably
because
I
am
super
cool
and
do
cool
things
on
the
weekend
like
that,
I
have
a
life
and
then
the
other
thing
about
coop
con
I
want
to
talk
about.
Is
that
I?
Just
heard
yesterday
that
the
call
for
papers
or
proposals
for
San
Diego
is
open.
The
San
Diego
cube
con
conference
is
in
November
and
the
let's
see
what
is
the
window
here
for
proposals?
A
A
Okay,
so
we
had
Nick's
not
here,
and
we
had
talked
about
the
core
resource
controller
resource
claim
controller
refactoring
that
he
was
doing.
We
got
into
that
a
little
bit
provided
some
details
there.
So
there's
a
link
to
that
pull
request
in
the
agenda
document.
If
you
want
to
weigh
in
there
or
provide
any
comments
or
feedback
on
it,
and
that
I
think
is
all
that
I
had
on
the
agenda
document
today
with
there
any
other
topics
that
anybody
on
this
call
wanted
to
add
or
to
bring
up
right
now
in
this
venue.
A
All
right
sounds
great
yeah.
Thank
you.
Everybody
for
joining
in
today,
I'm
really
excited
about
all
the
work
that
we're
tackling
40.3
and
will
set
us
up
for
future
milestones
as
well.
You
know
a
lot
of
activity
going
on
and
excited
to
see
all
the
progress
that
we're
making.
So
thanks,
everybody
for
joy
to
say,
I
appreciate
it.