►
From YouTube: 2019-03-19 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
Cadence
and
the
last
release
was
was
in
deserve
the
first
release
and
only
released
I,
guess
that
is,
it
was
in
December,
and
so
what
quarter
later
is
here
we
are
in
in
late
March,
and
so
we
want
to
start
focusing
in
on
getting
the
0.2
release
out
the
door
and
in
the
hands
of
the
crossplane
users.
There
is
a
significant
amount
of
work
and
features
that
have
gone
into
the
0.2
release.
You
know,
eat
things
like
object,
storage,
buckets
and
Postgres
support
and
and
retinas
support,
as
well
or
all
in
these
0.2
release
candidate.
A
So
getting
that
out-
and
you
know,
into
the
hands
of
all
the
users-
will
be
very,
very
useful.
So
I
think
that
there
is
some
discussion
that
we
need
to
have
here
today
about
what
the
plans
for
the
release
will
be
and
what
you
know.
What
kind
of
timeframe
were
targeting
here
and
the
list
of
items
that
have
been
tagged
or
included
in
the
0.2
release
needs
to
be?
We
need
to
take
a
pass.
A
Okay,
all
right,
so
let's
go
ahead
and
look
in
at
the
0.2
milestone
and
see
what
the
issues
are
in
there,
and
this
I
believe
has
some
items
here.
That
we've
had
discussion
about
punting
to
a
later
milestone
or
do
not
they're
not
really
in
line
with
current
priorities
that
have
have
been
discussed
since
the
0.1
release.
So
I
think.
A
B
That's
implemented,
my
waiting
for
that
was
revolving
around
that
PR
actually
just
submitted
a
couple
days
ago,
around
restructuring
how
we're
doing
the
directory
structure
for
the
client
fakes
and
so
now
that
we
kind
of
a
direction
with
that
I
can
implement
them
in
that
way,
so
I'm
hoping
in
the
next
day
or
two
to
be
able
to
follow
up
with
some
testing
there,
but
as
far
as
the
actual
functionality
everything's
working.
So
there
can
already
be
review
done
on
that.
If
that's
desired,.
A
B
B
A
A
Yeah
I'm
not
seeing
any
too
many
items
in
here
that
I
am
really
really
concerned
about
getting
included
in
0.2
I.
Think
a
lot
of
these
are
nice
to
haves,
or
you
know,
I
think
the
the
whatever
work
here
for
the
release
pipeline
I
think
that's
that's
a
critical
one
and
we
already
talked
about
that.
They
will
take
a
look
at
that
see
what
what
automation
or
gaps
we
may
have
before.
We
can
push
out
the
next
official
release
so
that
one
I
think
is
very
important.
But
does
anybody
else?
A
A
A
A
We
have
left
to
kind
of
make
sure
that
we
have
that
process
in
place
and
then
that'll
that
would
help
inform
us
about
a
targeted
date
for
it,
but
I
think
it
looks
like
we
could
do
it
pretty
soon,
though,
is
what
I'm
gathering
from
for
the
from
there
nobody
really
screaming
about.
We
have
to
include
XY
and
Z
features.
A
A
Okay,
all
right,
so
we
just
wanted
to
talk
real
quick
about
so
last
week
guy
took
a
trip
to
London
to
speak
at
the
cloud
Expo
Europe
conference,
and
then
I
also
was
fortunate
enough
to
find
a
meetup
group,
a
technology
meetup
group
that
was
in
London
and
the
organizer
there
Justin
Cooke
was
it
was
fantastic
and
pulled
together,
a
meet-up.
You
know
in
less
than
a
week's
time
and
got
a
place
to
host
it
and
sponsors
for
it
and
everything.
So
we
had
a
had
a
little
group
there
and
we
had
some.
A
You
know
great
discussion
about
the
crossplane
project
and
you
know
I
was
able
to
present
on
it
and
speak
on
it.
I
mean
getting
involved
in
little
and
some
discussion
with
with
the
folks
there.
So
that
was
a
great
experience
and
it
looks
like
Justin
the
organizer
of
that
meet-up
published
the
recordings
from
the
from
the
presentations
there,
and
so
I
will
add
those
to
this
playlist.
We
have
here
LinkedIn
the
meeting
notes
for
various
crossplane
presentations,
so
that
should
be
added
onto
there
sometime
today.
A
And
there's
also
speaking
of
meetups,
there
is
one
in
down
here
in
Southern,
California,
there's
one
in
Los
Angeles
and
then
there's
one
in
San
Diego
that
I'll
be
speaking
at
about
crossplane
again
coming
up
like
in
the
next
month
or
so
I
think
that's
sometime
late.
April
is
when,
when
I'll
be
doing
that,
and
so
if
anybody
else
in
the
community
has
you
know
meetups
or
you
know,
opportunities
to
talk
about
crossplane
and
kind
of,
introduce
it
to
more
people
and
get
discussions
going.
A
A
All
right,
so
a
big
focus.
You
know
our
our
first
big
design
partner
was
a
gitlab.
You
know
being
able
to
deploy
gitlab
in
a
portable
way
across
multiple
cloud
providers
and
environments
is,
you
know,
a
big
thing,
that's
kind
of
guiding
our
design
and
our
vision,
and
it's
a
great
scenario
as
well.
So
Nick
has
taken
the
reins
on
that
one
and
kind
of
started
doing
some
organization
in
early
thinking
around
what
it's
going
to
take
to
do
that
support
and
has
gathered
all
that
into
a
new
kit,
lab
label
and
project
Nick.
C
As
far
as
I
can
tell
there's
a
handful
of
things
that
we
need
to
support,
running,
get
lab
on
cross-claim
or
with
crossplane
some
of
those
specific
to
get
lab,
but
although
most
of
them
will
be
helpful
to
other
complex
applications,
so,
as
you
can
see
on
the
list,
they're
good
lab,
heavily
uses
cloud
storage
buckets.
We
currently
I
believe
only
support.
C
C
It
will
deploy
you
a
kubernetes
deployment
and
days
coopered
any
service,
but
if
you,
if
you
look
at
the
helm
templates
that
give
up
uses,
for
example,
they
have
something
like
14
deployments
several
services,
the
state
will
set
jobs
all
these
things,
so
we
met
separately.
Yesterday.
It
had
a
little
bit
of
discussion
about
how
we
might.
C
Model
all
of
that
using
a
workload.
We
have
some
good
ideas
there,
so
I'm
going
to
write
up
a
design
document
for
it.
I
won't
go
into
too
much
of
it
now,
but
I'm
sure
that
design
document
will
be
circulated
publicly.
It
is
a
repo
so
that
others
can
review
it
and
comment
on
it
so
that
effectively
it
will
be
backwards,
incompatible
changes
most
likely
to
how
workloads
work
in
cross
plane,
but
those
changes
will
support
everything
more
clothes
support
today
and
will
add
support
roles.
A
Cool,
thank
you,
Nick
fir
for
that
update
there.
That
has
a
cat
in
the
way
here
out
of
the
way
cat,
the
yes.
So
what
I
really
like
about
you
know
focusing
on
get
lab
and,
having
that
be
a
priority
for
the
crossplane
platform,
is
a
it's
useful.
You
know
people
want
it.
It's
it's
a
great!
You
know
application
that
has
a
lot
of
value
and
then
be
its
complexity.
A
Is
it's
kind
of
a
forcing
function
for
us
to
dig
into
some
of
the
more
difficult
design
aspects
of
the
platform
and
rush
things
out,
so
it's
a
great
driver
for
us
to
get
something
useful
that
people
want
and
also
flesh
out
the
platform
at
the
same
time
so
yeah.
This
is
whatever
this
are
I
believe
highest
priority,
because
it
has
so
much
breadth
across
the
entire
project
of
forming
of
bringing
the
project
forward
so
I.
You
know,
I,
think
that
continuing
to
focus
on
this
is
a
great
thing
for
the
project
and
Nick.
C
Mention
what
our
sort
of
deliverable
the
way
we're
hoping
for
here
is
so
at
the
moment,
if
you
are
using
kubernetes
to
deploy
kid
lab,
which
is
one
of
their
recommended
methods,
they
give
you
a
home
template
it
renders
to
about
almost
5,000
lines
of
llamó.
Our
goal
is
to
still
wrap
everything
up
with
helm
that
have
helm
instead
of
outputting,
just
all
the
basic
kubernetes
reasonless
types
like
deployments
and
whatnot,
we
weren't
held
to
output
across
plane,
workloads
and
cross
plane
resources.
B
C
Idea
being
that
you'll
still
do
a
hell
install,
but
under
the
hood
that
could
be
using
cross
plane
to
set
up
all
of
your
data
bases
and
buckets
and
even
speak
about
the
kubernetes
cluster,
and
things
like
that.
So
you
can
go
from
having
no
cloud
infrastructure
at
all
to
doing
home,
install
block,
so
you
don't
cross,
play
it
and
then
running.
A
Awesome,
ok
and
the
next
item
on
the
agenda
here
is
that
Ilya
had
been
doing
some
recent
work
about
the
patterns
used
in
our
controllers
and
our
reconcile
errs.
Those
are
you
know.
Those
controllers
are
an
enormous
part
of
the
platform
that
are
continuously
you
know,
taking
into
account
what
the
current
state
of
the
environment
is,
what
the
users
desired
state
is
and
taking
corrective
actions
to
drive
that
desired
state
towards
sorry,
the
actual
state
towards
the
desired
state.
So
Ilya
recently
wrote
up
a
really
good
and
very
detailed
document
as
well.
A
That's
where
that
is
going
to
be
shared
soon.
It's
very
you
know
just
just
got
through
writing
right
this
up,
so
it
hasn't
had
a
chance
to
share
it
out
yet,
but
it's
a
great
content
that
I
think
is
going
to
really
help.
They
were
the
reliability,
consistency
and
engineering
standards
of
the
controllers
that
are
hosted
within
the
cross
plains
control
plane.
Illya,
do
you
have
anything
to
add
about
this
reconcile
patterns
or
you
know,
goals
about
it
or
anything?
Yes,.
B
So
good
money,
so
this
is
the
ultimate
work
in
progress.
It's
very
rough
but
I
think
if
anything,
it
can
be
used
as
a
good
introduction
to
overall
controller
runtime
reconciliation.
How
the
controller
runtime
organization
conciliation,
the
some
things
still
in
flux
and
I'm,
still
kind
of
moon
over
the
relation
between
resources,
conditions
and
resources.
Actual
status
values
because
seems
to
be
like
those
two
correspond
to
again
address
the
same
concern.
But
overall
I
would
say
it's
probably
safe
to
say
it's
50
percent
correct.
A
Yeah
I
think
that
this
document
is
I
mean
the
thoroughness
of
it
is,
is
really
really
impressive.
We're
you
know
in
the
initial
couple
of
controllers
that
we
wrote
the
the
frameworks,
like
queue
builder
controller
runtime,
they
the
interface.
There
is
very
simple:
where
you're
you
all
you
have
to
do
really
is
write
a
reconcile
loop,
where
you
know
you
get
the
current
state
of
your
object
and
do
whatever
you
need
to
do.
But
there
are
since
I've
learned
from
reading
this
document.
A
There
are
so
many
complexities
to
handling
errors
and
retries
and
dependencies,
and
all
sorts
of
things
that
having
having
this
well
fleshed
out
and
well
thought
through
I
think
is
a
great
improvement
to
you
know
the
engineering
quality
and
reliability
of
the
cross
plane
project.
So
I
think
this
is
a
great
effort
and
I'm
really
happy
with
it.