►
From YouTube: 2019-04-16 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
April
16
2019
crossplane
community
meeting.
So
the
biggest
news
from
recent
events
in
the
crossplane
community
is
that
the
V
0.2
release
is
officially
out
and
published
and
available
for
consumption
by
the
community.
That
was,
you
know
that
was
good
to
get
that
release
out,
since
that
was
the
first
official
release
since
the
you
know
the
initial
unveiling
of
the
entire
project
and
repository
back
in
December.
A
So
there
was
a
whole
lot
of
great
support
and
new
resources
and
features,
etc
that
had
been
added
since
December,
but
had
not
been
officially
released
yet
so
we
have,
you
can
see
the
full
release,
notes
on
on
the
github
releases
page
and
there's
some
of
the
interesting
features.
I
think
that
it,
you
know
we
included
in
here
are
types
of
support
for
resources
like
Postgres
and
Redis
and
object
storage
and
the
initial
implementation
of
the
workload
scheduler
was
included
in
this
release
as
well,
which
starts
giving
you
the
flexibility
and
ability
to
influence.
A
You
know
where
and
amongst
all
of
your
clouds
and
clusters
workloads
get
scheduled
to.
We
also
wrote
up
a
blog
post
about
the
release
as
well,
so
if
you
want
to
read
instead
of
the
cut
and
dry
release
notes,
if
you
want
to
read
a
little
bit
more
friendly
story
with
more
pictures
as
well,
you
can
check
out
the
this
blog
post
here
on
the
Crossland
IO
blog,
so
great
work
to
everybody
in
the
community.
For
you
know,
implementing
those
features
working
through
a
lot
of
the
designs
and
getting
to
our
second
official
release.
A
Definitely
one
thing
that
we
want
to
improve
for
the
next
release
is
some
of
the
autumn.
You
know
in
our
build
system
and
build
server
etc.
For
for
the
release
process,
we
still
have
some
gaps
in
our
automation
right
now.
So
when
we
went
through
the
release
process,
there
were
some
manual
steps
that
we
needed
to
to
perform,
which
definitely
you
know,
can
lead
to
potential
errors
and
failures,
etc.
A
All
the
major
cloud
providers
will
be
the
biggest
focus
in
0.3,
so
in
the
0
to
3
milestone
here
on
the
github.
We
have
a
number
of
issues
that
you
know
are
focused
on
that
general
theme
of
enabling
real-world
applications,
and
so
we
could
probably
do
a
pass
to
make
sure
that
you
know
all
of
these
items
here.
Are
you
know
in
scope,
or
you
know,
relevance
to
the
theme
that
we
want
to
accomplish
and
potentially
pull
in
other
issues
as
well,
that
we
might
be
missing
that
we
need
to
deliver
on
this.
A
A
So
the
work
items
that
are
you
know
scopes
on
getting
gitlab
itself
up
and
running
will
be
tracked
on
this
project
board,
just
as
it's
a
major
major
feature
to
get
get
lab,
support
and
running.
So
having
a
view
of
you
know,
the
status
of
items
associated
with
that
is
available
on
this
particular
project
board.
A
All
right
so
yeah,
so
you
know
we,
you
know,
can
take
a
pass
through
the
issues
associated
with
0.3,
but
you
know
commenting
on
adding
comments
or
you
know
discussing
on
slack
or
whatever
it
may
be.
What
are
your
preferences,
for?
You
know
issues
in
0.3,
what
maybe
in
scope
or
at
a
scope-
or
you
know,
features
that
the
community
itself
would
like
to
see
as
well
are
very
welcome.
So
we
can
continue
having
discussions
on
on
what's
in
0.3
and
what
the
scope
is
and
all
that
sort
of
stuff.
A
B
Yep,
so
I
just
saw
a
response
to
this
and
I
didn't
know.
If
anyone
had
followed
up
with
them
seemed
like
it'd,
be
a
pretty
cool
time.
They're
sort
of
a
cloud
providers
will
also
get
involved
with
this
sort
of
as
another
partner
I,
don't
know
if
that
might
also
involve
adding
support
for
for
packet.
Just
like
you
know,
AWS
or
GCP,
or
something
like
that,
but
it'd
be
cool
to
take
advantage
of
this
offer
for
sure
yeah.
A
So
you
know
heavily
involved
in
the
rook
project
as
well,
and
so
as
a
CN
CF
project.
You
know
you
have
access
to
packet
infrastructure
to
do
like
continuous
integration,
testing
and
continuous
deployment
type
of
stuff,
so
I
love.
What
packet
has
done
in
terms
of
you
know,
making
available
their
infrastructure
for
projects
to
utilize,
so
I
am
I'm
actually
coming
from
catching
up
a
little
bit
from
being
out
of
town
this
weekend
and
I.
Don't
think
I
had
seen
this
offer
yet.
A
So
thank
you
for
pointing
this
out
Daniel,
but
I
hadn't
seen
this
yet,
but
I
love
what
they're
doing
there
and
then
also
there
there
is
a
guy
I've
been
working
with
recently
down
here
in
San
Diego.
It
runs
a
couple
of
technology,
meetups
and
I'm,
going
to
be
presenting
on
crossplane
in
Los
Angeles
and
then
also
here
in
San
Diego
as
well
in
the
next
couple
of
weeks,
and
he
I
don't
know
if
you
I,
don't
think
he
works
for
packet,
but
he
has
maybe
he's
consults
with
packet,
and
you
know
so.
A
He
we've
been
starting
to
talk
a
little
bit
about
you
know,
so
how
we
could
use
that
infrastructure
or
those
resources
as
well
for
this
project.
So
it
seems,
like
you
know,
there's
multiple
angles
here
of
getting
involved
with
packet
and
their
infrastructure.
One
question
to
you
guys
is
this
packet
have?
Are
they?
Are
they
really
like
an
infrastructure?
Only
provider?
Do
they
have
you
know
a
set
of
managed
services
like
databases
and
caches
and
stuff
is
well
that
they
provide
for
for
people
for
applications
that
they're
hosting
I
think.
B
A
Cool
yeah
that
so,
if
it's
yes
I
guess
that's
a
it
makes
sense
for
highlighting
this
particular
part
of
the
blog
post.
They're
about
you
know,
on-premises
deployments
and
supporting
you
know,
features
that
follow
the
kubernetes
operator.
Pattern
like
like
Rock
does
and
so
like
on
bare
metal
they're
being
able
to
deploy
operators
and
controllers
that
you
know
provide
the
set
of
managed
services
like
the
cloud
providers
to
like
databases,
and
you
know,
object,
storage
and
things
like
that.
So
yeah
we
yeah,
so
that's
cool
that
packet
directly
said.
A
A
B
So
the
the
first
iteration
kind
of
dragged
on
for
a
little
while
and
through
that
process
we
kind
of
reshaped
our
designing
controllers,
and
so
it's
basically
just
rewritten
to
kind
of
adhere
to
that
standard.
So
I
did
put
the
work
in
progress
prefix
on
there,
just
because
I'm
still
implementing
a
couple.
The
tests
but
I
want
to
go
ahead
and
put
up
there
just
because
we
could
go
ahead
and
look
over
it
and
kind
of
see
if
it's
adhering
to
the
new
structure
and
that
sort
of
thing.
A
Awesome,
that's
great
that
way.
I
definitely
appreciate
you
know,
as
the
design
practices
in
patterns
in
the
repository
have
kind
of
been
under
a
little
bit
of
iteration
as
we're.
You
know
finding
our
footing
here
and
finding
what
the
right
patterns
are
for
for
all
the
controllers.
I
definitely
appreciate
you
incorporating
those
those
best
practices
into
your
implementation
is
well
Daniel.
So
that's
a
good
good
example
to
follow.
I
appreciate
that,
definitely
and
so
you're
working
on
the
tests
now
jep's
yep.
B
A
A
I
wonder
if
that's
something
that
we
need
to
add
and
like
what's
the
word
I'm
looking
for
permissions
for
you
to
be
able
to
see,
I
thought
that
we'd
be
able
to
see
test,
results
and
stuff
would
be
have
anonymous
access
that
you
wouldn't
need
credentials
fed
Ilia.
Do
you
do
you
happen
to
know
about
the
Jenkins
access
yeah.
C
B
C
A
Yeah
yeah,
that
sounds
great,
then
guys
I
guess
in
the
crossplane
slack
we
can
in
the
dev
channel.
That
sounds
like
a
good
place
to
talk
about
that
so
yeah
we
should.
We
can
definitely
help
you
get
access
to
the
chickens.
Instance
Daniel.
So
you
can.
You
know,
see
what
the
issue
is
and
you'll
be
able
to
troubleshoot
cool.
B
B
A
All
righty
and
then
I
also
just
opened
a
portal
request
as
well
design
request.
So
the
we
have
an
issue
here,
375
where
you
know
the
general
concept
here
is
that
we
want
to
be
able
to
in
cross
plane
to
be
able
to
support
adding
additional
functionality,
an
extension
extend
cross
plane
with
new
types
and
resources
that
were
not
built
necessarily
inside
the
cross
plane
source
tree.
So
this
is
our
extensibility
story
for
cross
plane.
Essentially-
and
so
this
is
this
pull
request
here
through
97
is
a
work
in
progress
for
sure
attempt
here.
A
It
kind
of
describing
what
these,
what
the
functionality
that
we
need
to
support
is
in
the
extensions
concept,
and
you
know
what
some
of
the
mechanisms
are
and
some
new
types
and
controllers
etc.
So
this
is
kind
of
a
sketch
one
pager
for
what
we
need
to
be
able
to
add
support
for
out
of
tree
extensions
in
crossplane.
So
this
is
open
and
available.
For
you
know
the
review
and
design
discussion
from
the
community.
It
is
the
you
know,
it
is
a
work
in
progress,
pull
request.
So
it's
a
little
bit
rough
right
now.
A
It
has
some,
you
know,
questions
here
that
are
unanswered
right
now,
but
you
know
any
feedback,
or
you
know.
Thoughts
on
this
proposal
here
are
open
to
the
community
and
to
help
us
kind
of
iterate
over
this
and
drive
a
design
that
will
be.
It
will
work
well
for
everyone
to
be
able
to
support
this
new
type
of
extension,
functionality.