►
From YouTube: 2019-01-22 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
this
is
the
January
22nd
2019
crossplane
community
meeting
and
I
recognize
I.
Think
almost
every
single
name
today
so
welcome
to
some
of
the
folks
that
might
not
have
been
to
a
community
meeting
yet
but
I
recognize
you
from
github
like
Daniel
and
V
new
and
Zac
I've,
seen
before
as
well
Nomar
as
well.
So
welcome
welcome
back
all
you
guys
good
to
have
you
thanks.
A
Right
so
let's
go
ahead
and
talk
about
some
project
status
here
so
over
since
the
last
community
meeting.
We
you
know
at
that
point
we
had
done
some
initial
2019.
You
know
looking
ahead
planning
to
see
what
were
the
major
priorities
in
milestones.
We
wanted
to
accomplish,
at
least
in
the
next
six
months
or
so,
and
so
we
turned
that
into
roadmap
now,
so
the
roadmap
has
been
officially
updated
at
roadmap
that
MA
MD,
so
the
0.1
milestone,
that's
shipped,
that's
out
the
door.
A
That
was
the
part
of
the
December
fourth
initial
release
and
there's
a
lot
of
good
things
in
there
that
are
all
done
and
completed.
So
then
0.2
is
the
milestone
that
we're
currently
focusing
on.
That's
the
milestone
that
we
are
actively
in
progress
on,
and
so
some
of
the
major
themes
for
that
which
shouldn't
be
too
much
of
a
surprise.
A
Excuse
me,
because
these
are
these
are
items
that
we
had
sort
of
discussed
already
in
the
2019
planning
document,
but
the
big
one
there
is
the
workload
scheduler
Ilya
has
and
Ravi
has
started
on
a
design
for
the
workload
scheduler
in
terms
of
some
of
the
early
features
that
we
want
to
support
in
it
and
sort
of
the
you
know,
phases
that
we
want
to
implement
features
in.
So
there's
I
think
that
there
will
be
a
pull
request
open
for
that
thinking
soon
to
get
more
comments,
all
that
Ilya.
C
A
Awesome
sounds
great:
it's
right
on
the
list
today.
No,
no,
no
I,
don't
think
I
see
Robbie's,
not
here.
Okay,
all
right
and
then
some
other
you
know
importance
features
or
things
we
want
implements
are
some
new
services
Postgres.
This
is
already
in
master.
That's
done,
MongoDB
and
red
s
certs
with
the
other
ones
that
we
think
have
good
bang
for
the
buck
good
value
and
that
we
want
to
go
after
and
implement
those
men
services,
particularly
reticent,
Postgres.
A
Those
are
actually
in
service
as
well
of
wanting
to
be
able
to
support,
get
lab
which
is
in
the
0.3
milestone.
So
we
want
to
make
sure
that
all
these
services
that
get
lab
the
deployment
of
get
lab
depends
on
are
supported
across
all
the
cloud
provider
environments
and
be
able
to
bring
together
the
entire
get
lab
application.
Complicated
application
deployments
in
the
next
milestone,
then
there's
a
number
of
issues
in
other
classes,
so
you
know
improved
experience,
stuff
performance,
reliability
in
the
engineering
debt,
technical
debt
as
well
and
they're.
A
All
you
know,
sorry
that
also
there
is
a
category,
a
classification
of
of
issues
here
about
supporting
services
that
run
locally
or
in
cluster
services
that
have
support
the
operator
pattern.
So
there's
a
fair
amount
of
those
in
rook.
That
would
be
good
to
support.
We've
already
got
some
of
that
support,
going
on
some
of
the
initial
proof-of-concept
work
for
cockroach
DB
using
the
rook
operator,
so
there's
some
more
thinking
to
go
around
there
and
kind
of
formalize.
A
The
proposal
for
how
you
know
in
general
managed
services
that
have
you
know
the
run
in
cluster
and
support
the
operator
pattern
that
can
be
supported,
but
there
already
has
been
some
work
accomplished
on
that
and
then
the
0.3
miles
to
so
the
timeframe
that
we're
talking
about
by
the
way
is
we're
talking
about
doing
quarterly
releases,
so
0.2
would
be
looking
at
the
end
of
March
or
early
April
timeframe
is
what
we're
initially
thinking.
You
know.
A
A
So
looking
at
the
0.2
milestone,
you
know,
we've
all
the
milestones
in
it
issues
and
everything
and
projects.
This
is
all
up
to
date
on
the
github
site.
Now,
so
you
can
see
and
the
0.2
milestone
that
there's
a
number
of
issues
that
don't
yet
have
owners,
but
we've
identified
is
issues
that
we
want
to
target
or
features
that
we
want
to
implement
for
the
0.2
milestone.
So
what
this
is
saying
is
that
there's
a
lot
of
opportunity
from
the
community
to
pick
up
some
of
these
issues.
You
know
as
we
get
through
them.
A
You
know
we'll
claim
more
issues.
You
know,
as
we
free
up
other
other
developers
to
work
on
them,
but
this
there's
a
lot
of
good
opportunity
here
for
folks
in
the
community
to
you
know,
identify
something
that
may
be
interested
in
and
go
ahead
and
start
taking
a
stab
at
it
that
work
as
well
I've
gotten
a
number
of
a
handful
of
messages
on
slack
and
emails
and
such
about
contributors.
New
contributors
are
folks
that
are
interested
in
picking
up
some
work
here.
So
you
know,
I
want
to
continue
to
encourage
everyone.
A
That's
you
know
something
that
we
highly
support,
and
you
know
I'm
happy
to
spend
time
with
folks
getting
you
ramped
up
or
figuring
out
where
our
new
contributor
documentation,
maybe
you
lacking
or
missing
right
now,
so
that
we
can
continue
to
improve
and
iterate
on
that
experience
of
of
onboarding
new
contributors
and
continue
to
grow
the
community.
Now.
Does
anybody
have
any
comments
about
the
roadmap
in
general
or
the
you
know
milestones
like
0.2
that
we're
currently
working
on.
A
So
the
so
in
terms
of
get
lab,
you
know,
that's
the
milestone
that
we're
targeting
having
that
support
completed,
there's
a
number
of
things
along
the
way
there,
like
you
know,
supporting
Redis
and
supporting
Postgres,
and
things
like
that
they
get
lab
will
depend
on,
but
that
will
be
that's
targeting
the
0.3
milestone.
Yes,
and
if
you're
interested
in
that
too,
there's
on
the
cross
plane
slack
there's
now
a
gitlab
channel
that
you
can
join
and
you
know,
follow
along
and
contribute
and
participate
in
the
discussion
there
for
further
get
lab
support
going
forward.
A
All
righty,
so
you
know
moving
on
to
the
community
topics
here,
there's
a
we
had
talked
last
week
or
last
meeting
about
good.
First
issues:
I
had
an
action
item
to
go
through
the
repository
and
identify
issues
that
might
be
good
for
a
first-time
contributor
to
get
into
the
repo
and
understand
some
of
the
source
code
layouts
and
the
developer
process,
and
such
so
I
did
that
I
went
through
the
whole
repo
or
all
the
issues
opened
in
the
repo
and
identified
ones
that
I
thought
might
be
good
for
first-time
contributors.
A
So
this
query
the
label
here
the
good
first
issue
label
should
be
up-to-date
with
a
lot
of
different
items
that
you
know
might
be
good
for
someone
to
come
in
and
check
out,
and
you
know
not
all
of
them
are
in
the
0.2
milestone.
So
they're,
not
you
know
targeted
for
the
next
milestone.
We
want
to
release,
but
I
would
give
the
advice.
A
That's
you
know
if
you
see
something
in
this
good
first
issue
list
that
you
know
you're
interested
in
and
you
think,
would
you
know,
help
you
get
on
board
and
become
a
you
know,
contributor
to
the
project.
Please
do
feel
free
to
work
on
it.
You
know
just
because
it's
not
in
the
0.2
milestone.
I
would
not
say
that
you
know
if
it's
something
you're
interested
in
and
you
think
it
would
be
good
to
bring
you
into
the
project.
A
A
Already
so
we
might
not
need
to
go
into
much
discussion
on
this,
but
I
wanted
to
at
least
get
pulse
from
folks
in
the
community.
Here
there
is
so
there's
a
in
the
rook
project.
You
know
the
CNC
F
project
that
some
of
us
also
contribute
to
that's
their
cloud
native
storage,
Orchestrator
that
focuses
on
orchestrating
and
deploying
and
managing
storage
solutions
in
cluster.
A
A
C
A
A
B
Yeah
I
was
just
wondering
if
we
there
is
a
way
to
rapidly
or
quickly
set
up
an
environment
where
crossplane
is
working
and
to
go
even
or
I
was
thinking
about,
having
a
so,
for
instance,
for
the
people
who
are
working
on
on
gait
lab
if
they
can,
if
they
have
one
in
a
test
environment
where,
where
they
have
ultimate
automated
tests.
For
for
what
they're,
what
you
are
implementing.
A
Yes,
so
there's
you
know,
I
I'm,
not
sure
what
you
have
already
seen
in
the
repo.
So
this
may
be
information
you
already
know,
but
it
could
also
be
useful
for
anybody
else
on
the
call
now.
But
the
first
thing
I
would
address
there
is
that
you
know
running
cross
plain
is
supported
on
mini
cube
environment,
so
you
could
run
the
construe,
the
set
of
controllers
and
custom
resources,
etc
on
mini
cube,
and
so
that's
in
the
cluster
local
directory.
A
C
Can
chime
in
on
that,
so
this
way
using
local
setup
will
actually
require
for
you
to
build
and
build
cosplay
and
build
back
our
image
and
deploy
it
into
mini
kit
a
little
bit,
maybe
heavy-handed
for
quick
iterations.
If
you
look
into
the
cube
builder
project,
which
is
crossplane
is
based
on,
we
using
it
as
a
scaffolding,
there
is
a
option
that
to
run
locally,
so
you
can
actually
run
your
go.
C
A
C
A
You
know
we
should
do
yeah
I,
think
that
we
should
follow
up
and
get
that
documented
as
well,
because
if
that's
you
know
a
fast
way
to
iterates
as
a
developer,
that
you
know
faster
than
mini
cube
and
also
the
point
you
bring
up
about
being
able
to
use
the
bugger
to
the
reset.
This
point.
A
C
A
And
I
read
it's
like
an
action
item
here:
I
wrote,
developer
developer,
documentation
to
get
the
docs
updated
to
kind
of
get
that
more
formally
captured,
so
that
you
know
folks
can
just
come
into
the
repo
can
also
get
those
instructions.
You
know
that
actually
brings
up
an
interesting
question,
though,
and
one
I
haven't
thought
about.
Yet
until
just
now
that's
some
of
the
test
work.
You
know
of
developing
and
running
some
of
the
cross
plane
controllers
to
actually
do
useful
work
like
deploying
a
Postgres
instance
to
Google
Cloud.
A
You
know
the
Google
cloud
or
Amazon
do
that
and
that's
that
starts
up
managed
service
or
services
in
cloud
provider,
environments
that
winded
up
you
know
and
resulting
in
charges.
You
know
actually
cost
money
to
do
that
so
I,
don't
I
haven't
really
thought
about
that
about.
You
know
a
good
way
to
be
running,
crossplane
and
testing.
You
know
for
in
a
way,
that's
you
know,
doesn't
result
in
any
charges
if
you're
you're
doing
using
it
to
start
up
manage
services.
You
know
running
the
control
across
speed.
A
A
Okay
and
then
I
think
Omar.
You
had
mentioned
another
thing
about
get
lab
as
well,
and
so
you
know
that
that
discussion
is
still
very
early
with
get
lab.
Folks,
and
you
know
there
has
not
yet
been
an
environment
to
find
about.
You
know
running
tests
or
you
know
iterating
over
a
deployment
of
get
lab.
So
you
know
on
the
just,
join
the
get
lab
channel
and
crossed
planes
slack,
and
you
should
be
able
to
capture
you
know
any
updates
there
or
it
could
ask
that
question
there,
and
we
can.
A
Okay
yeah,
so
the
next
set
of
items
here
is
about
PRS.
That
would
need
attention.
I
didn't
see
any
that
I
thought
we
needed
to
address
here.
So
that
looks
like
a
shorter
agenda
today.
Is
it
normal,
but
I'll
open
the
floor?
If
anybody
has
any
other
topics
that
they
wanted
to
bring
up
in
this
community
setting
the
floor
is
open.
A
Alright,
ok,
so
you
know
we're
gonna
continue
working
on
the
0.2
milestone.
You
know,
there's
a
reminder,
there's
a
fair
amount
of
issues
that
are
open
and
don't
have
a
sigh
knees
right
now.
So,
if
anybody
is,
you
know
looking
to
figure
out
what
they
want
to
how
they
want
to
help
contribute
to
this
project.
A
You
know
we
could
discuss
about
it
and
you
know
get
some
new
owners
on
those
issues
and
help
you
get
ramped
up,
and
you
know,
as
I
mentioned,
people
have
been
paying
me
and
started
to
talk
about
getting
into
starting
how
to
get
involved
in
the
project.
So
let's
keep
doing
that
and
I'm
looking
forward
to
all
the
folks
that
have
expressed
enthusiasm
about
working
on
the
project
here.
So
with
that
I
think
we
could
a
gern
for
the
day.