►
From YouTube: 2019-02-05 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
So
I
think,
since
the
last
meeting
the
the
roadmap
hasn't
undergone
any
major
changes.
It
is
in
master.
Now,
though,
so
you
know
as
a
community,
we
agreed
upon
the
set
of
features
that
we
want
to
see
in
the
upcoming
0.2
and
0.3
milestones,
so
no
surprises
there.
So
let's
go
ahead
and
look
at
the
project
boards
in
milestone
itself.
Let
me
make
that
a
little
smaller.
A
Kinda
will
have
a
specific
label
for
those,
but
there's
a
lot
of
interesting
things
that
are
bite
sized
chunks
that
can
be
picked
up
here.
So
quick,
look
at
the
project
board.
We
have
a
fair
amount
of
issues
that
are,
you
know
already
in
the
done
column,
and
we
have
a
the
the
issues
that
I
mentioned
that
are
currently
in
progress
now
about
the
resource,
scheduler
workload
scheduler
the
Redis,
supports
and
then
also
I'm
doing
a
cleanup
refactoring
to
reuse
the
general
resource
controller
for
other
types
as
well.
A
I've
initially
used
it
for
Postgres
in
my
sequel,
but
it
also
will
work
perfectly
for
buckets
and
for
clusters
as
well
so
I'm
in
the
midst
of
implementing
that
and
finding
the
time
to
do
that
and
then
the
to-do
column.
We
have
a
fair
chunk
of
the
issues
that
are
remaining
and
have
are
not
quite
not
picked
up
by
anyone,
yet
that
or
missing
assignees.
A
That's
the
same
issues
that
are
on
the
0.2,
your
milestone
that
we
were
just
looking
at.
So
this
board
is
I,
believe
an
up-to-date,
accurate
reflection
of
the
issues
in
the
0.2
milestone
and
anybody
that
wants
from
the
community
that
wants
to
pick
up
any
of
these
issues.
You
know
they're
all
fair
game
if
they
don't
have
an
assignee
on
them
and
we're
more
than
happy
to
help
get
anyone
that
wants
to
contribute
on
these
issues,
ramped
up
and
productive
on
all
of
them.
A
A
portable
workload
across
multiple
cloud
providers
is
gitlab
that
we've
been
talking
about
and
excited
about.
So
I
just
wanted
to
give
a
small
update
on
that.
Did
the
gitlab
some
of
the
folks
engineers
from
the
get
lab
side
like
DJ
and
Jason,
have
been
working
on
testing
out,
crossplane
and
kind
of
get
you
know
getting
ramped
up
on
it
and
figuring
out.
You
know
the
current
status
of
you
know
the
feature
set
and
what
might
be
missing?
A
What
are
some
of
the
gaps
in
terms
of
what
get
lab
will
need
for
support
to
be
able
to
successfully
deploy
to
get
lab
application
and
all
of
its
components
and
in
many
different
environments,
and
so
we've
been
engaging
with
them.
Jason's
been
working
on
that
in
terms
of
getting
buckets
and
databases
and
things
installed,
so
we
will
continue
working
with
the
get
lab
team.
You
know
it's
everything,
that's
being
done.
There
is
being
tracked
either
in
get
lab
here
on
issue
9
91
in
the
charts,
repo
for
get
lab
and.
A
All
along
with
the
discussion
there
for
sort
of
you
know
big
updates
that
are
going
along
that
process
and
then
there's
also
still
to
get
lab
channel
in
our
crossplane
slack
workspace.
So
there's
those
are
the
two
main
places
to
follow
along
with,
if
you're
interested
in
the
get
lab
progress
for
supporting,
get
lab-
and
you
know,
there's
still
plenty
of
space
for
anybody
who
wants
to
contribute
on
that,
since
it
is
a
fairly
complicated.
A
You
know
application
of
support
that
has
a
fair
amount
of
touch
points.
For
instance,
you
know
nick
picking
up
the
support
through
Redis
managed
services
that
is
in
you
know
that
that
will
be
useful
for
the
community
as
a
whole,
but
it's
also
in
direct
service
to
supporting
get
labs
since
it
uses
Redis
for
its
caching.
A
I
wanted
to
also
just
briefly
talk
about
a
documentation
for
adding
support
for
new
resources.
We
have
a
couple
of
more
recent
contributors
that
have
been
adding
support
for
things
like
Redis,
that
Nick
was
doing
and
then
Daniel
had
been
working
on,
adding
modeling
and
adding
a
controller
for
resource
groups
and
Azure,
and
so
you
know,
as
people
are
getting
ramped
up
on
the
general
process,
for
adding
support
for
new
resource
types
in
cross
plane.
A
You
all
right
another
issue
that
I
was
interested
in
that
I
I,
don't
have
insight
into
I.
Think
Illya
does
is
about
being
able
to
iterate
more
quickly
as
a
developer
on
the
project.
What
I
have
still
been
doing
to
this
day
is
running
cross
lean
in
mini
cube
with
the
helmet
art
firm,
that
I
build
locally,
and
you
know
that
works
fairly.
Well,
it's
it's
not
a!
A
You
know
a
very
costly
iteration
cycle,
but
you
know
you
don't
have
the
ability
to
easily
at
least
attach
a
debugger
and
run
into
in
a
debugger,
and
you
know
you
have
to
build
like
the
container
image
and
the
helm
chart
every
time
that
you
make
an
update
and
so
the
the
way
of
being
able
to
run
as
just
a
local
process
on
your
dev
machine
that
you
can
easily
attach
the
bugger
to,
and
you
know
quickly,
teardown
and
bring
back
up
again
is
still
pretty
desirable.
So
Ilya
had
originally
expressed
that
yeah.
A
That's
how
he's
working
things
now
and
so
getting
some
information
from
him.
You
know
even
just
raw
notes:
I'd
be
happy
to
kind
of
pull
those
together
and
put
a
little
bit
more
structured
documentation
around
that.
So
our
dev
Doc's
and
then
daniel
has
expressed
some
interest
in
helping
is
well
Daniel.
I
know
you're
on
the
call
right
now
are
you?
Are
you
using
mini
cube
right
now
to
test
or
what
is
your
general
flow
right
now?
Yes,.
B
I've
been
using
mini,
cube
and
I
mean
it
works
fine,
but
I,
don't
know,
I
feel
like
that.
It
took
me
a
little
while
to
get
up
and
running
and
making
sure
everything
was
you
know,
configured
is
specified
in
the
installation
documents,
so
I
definitely
think
a
more
standardized
way
to
do.
That
would
be
good.
Obviously,
it's
not
as
big
of
an
issue
right
now,
because
we're
at
like
11
contributors
or
something
like
that,
but
hopefully,
as
it
ramps
up
some
more
people,
especially
when
people
start
to
have
questions
doing
it.
B
A
Definitely
that's.
Those
are
good
points,
Daniel
cool
yeah,
so
we
had
this
issue
and
it's
in
the
to
do
sorry,
it's
in
the
0.2
milestone
and
to
do
column.
So
I
expect
that
we'll
be
able
to
collect
some
information
around
this
from
the
from
the
general
community
and
from
Illya,
especially
as
well
since
he's
actively
doing
this
and
we'll
get
that
that
experience,
improved.
A
A
So
this
one
for
the
workload
scheduler
has
just
been
opened
yesterday.
So
it's
you
know:
it's
not
been
sitting
around
and
waiting
for
someone's
attention.
It
just
was
opened
yesterday,
but
this
is
you
know,
kind
of
one
of
the
first
big
steps
in
the
implementation
of
the
you
know,
workload
scheduler
for
deploying,
and
you
know
making
sure
that
workloads
and
all
their
resources
are
running
and
optimized
across
the
various
environments
that
we
want
to
support.
A
So
taking
a
look
at
this
poor
request
is
definitely
in
the
best
interest
of
anyone
from
the
community
that
is
interested
in
the
direction
and
the
implementation
specifics
for
the
workload
scheduler,
so
pull
request.
310
is
one
that
is
just
open
now
and
is
open
for
feedback
for
a
discussion
from
from
folks
in
the
community.
If
you're
interested
in
that.
A
So
it's
it
can
also
be
potentially
educational
if
you
want
to
take
a
look
at
it.
So
this
is
pull
request,
307
for
supporting
Redis
and
all
these
links
are
in
the
agenda
document
as
well.
So
you
can
find
you
can
find
all
of
them
there
all
right.
So
that's
all
that
I
had
in
terms
of
community
topics
and
pull
requests
that
I
wanted
to
discuss.
Was
there
any
other
topic
that
anybody
wanted
to
bring
up
on
the
call
today,
I
think
everyone's
muted?
A
A
All
righty
Jorge
I
notice
that
you're
on
the
call
and
I
wanted
to
thank
you
for
the
the
discussion
that
you
had
you
had
started
with
me
about.
You
know
some
of
the
various
has
your
resources
and
getting
ramped
up,
so
that
was
a
fruitful
discussion.
I'm
excited
about
your
you
know
your
interest
in
your
collaboration
here,
yep.
C
A
All
righty
everybody
up
in
Seattle
stay
safe,
then,
with
with
the
weather
up
there
I
know.