►
From YouTube: 2019-01-08 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
is
started,
and
this
is
the
January
8th,
2019
crossplane
community
meeting.
So
we've
got,
let's
see,
I'm
taking
a
look
at
the
list
here
and
I
think
we
have
a
couple
of
new
folks
here
and
we
don't
have
that
many
people
here.
So
let's
just
go
quit
actually
real,
quick
and
just
introduce
ourselves.
You
know
we
don't
have
to
take
too
long
doing
that,
but
my
my
name
is
Jared
watts
and
I'm
running
this
community
meeting
and
I'm
one
of
the
maintainer
x'
on
the
crossplane
project.
B
A
C
C
C
Yes,
I
well,
my
name
is
Celia
and
I'm.
Another
maintainer
on
the
cross,
plane
project.
D
A
B
E
A
Oh
cool
awesome:
are
you
you're
at
office
time
not
at
a
coffee
shop,
I'm.
A
Man
welcome
back,
thank
good,
see
you
and
then
a
taco
does
not
look
to
have
audio
but
welcome
to
to
you
as
well
alright
cool.
So
we
did
a
little
bit
of
thinking
as
we're
kind
of
turning
2019.
Here
I
mean
we
got
0.1
out
at
the
end
of
December.
You
know
we
had
a
couple
of
talks
and
you
know
presentations
and
such
at
cube
con
in
Seattle,
and
we
are
trying
to
carry
that
momentum
here
that
we've
got
a
nice
community
building.
You're
really
excited
about
that.
A
There's
a
lot
of
interest
in
the
project
and
the
reception
has
been
really
good.
So
far.
We
want
to
carry
that
momentum
into
2019,
so
it
took
a
stab
at
just
some
high-level
planning
for
2019
and
to
go
through
that
real
quick
to
just
kind
of
get
some
get
us
on
the
same
page
about
you
know
what
we're
sort
of
thinking
about
before
the
project
for
the
next
year
and
then
you
know,
starts
maybe
getting
some
feedback
as
well,
because
you
know
it's
really
important
to
remember
here.
A
This
project
is
a
community
driven
effort,
and
you
know
we
want
to
make
sure
that
the
it's
going
in
a
direction
that
you
know
is
going
to
be
beneficial
to
the
entire
community.
So
this
is
just
you
know
some
thoughts
here.
This
is
not
an
official
planning
documents.
It's
just
kind
of
getting
some
of
our
our
initial
ideas
here
down
on
paper,
so
I
think.
A
The
the
really
important
thing
that
we
want
to
focus
on
here
are
some
of
the
major
themes
that
we
want
to
be
looking
at
here
for
2019
those
are
kind
of
centered
or
focused
around
the
upcoming
cube
cons.
So
there's
cube
con
in
Barcelona
and
I
think
in
May,
and
then
the
North
America
one
is
in
San
Diego
this
year,
I
think
in
late
November,
so
those
will
probably
be
good
times
to
have
kind
of
a
major
of
elisa's,
or
you
know
big
x-large
executions
on
this
overall
vision.
A
So
in
barcelona,
really
what
we're
you
can
sum
that
up
as
the
theme
for
that
one
is
trying
to
start
executing
on
the
the
full
vision
here.
So,
there's
a
whole
lot
of
concepts
that
we
introduced
in
0.1,
and
we
want
to
take
that
further
and
keep
working
on
delivering
the
entire
vision
of
you
know:
workload,
portability
and
scheduling
for
heterogeneous
workloads
in
you
know
that
includes
server
lists,
containers,
VMs,
all
sorts
of
you
know
delivery
of
software
for
complicated
applications.
So
that
does
not
say
that
we
will
not
focus
on
reliability
at
all.
A
A
What
we'd
like
to
see
is
the
ability
to
start
being
able
to
have
some
of
the
partners
of
the
project
to
start
being
able
to
dog
food.
The
project
you
could
start
it'll
have
enough
it'll
be
fully
featured
enough
to
start
being
able
to
use
it
in
real
scenarios
and
start
taking
a
dependency
on
it,
not
from
a
production
standpoint
but
from
a
feature
stay
a
full
feature.
Standpoint.
A
One
of
the
we
want
to
show
in
Barcelona
what
we
want
to
show.
What
we
want
to
be
able
to
demonstrate
there
is,
is
gitlab,
being
able
to
deploy
and
manage
the
lifecycle
of
all
of
its
components
across
multiple
clouds
and
on-premises.
So
that's
really
kind
of
the
big.
You
know
visual
demonstration
experience
that
we
want
to
be
focusing
on
they
kind
of
wraps
a
lot
of
the
features
and
this
full
vision
and
be
able
to
show
that
off
and
then
the
rest
of
the
year.
A
Moving
towards
San
Diego,
we'll
be
focusing
on
production
G,
a
type
of
state
stability.
Were
you
know,
once
we
have
the
full
vision
sort
of
brought
together,
then
we'll
be
able
to
introduce
more
reliability.
You
know
production,
ready,
Enterprise
type
of
quality
to
the
project
and
keep
driving
on
that.
So
those
the
overall,
you
know
major
themes
that
we
want
to
be
executing
on
2019.
Does
anybody
have
any
comments
that
they'd
like
to
share
on
that
overall
vision.
A
Everybody's
on
mute
by
the
way,
if
anybody
was
wanting
to
talk
right
now,
I
just
reminder:
you
got
to
unmute
yourself
all
right,
so,
let's
keep
going
then.
So
you
know
let's
talk
about
what
it
takes
to
deliver
on
that.
So
the
a
couple
dates
to
remember
is
that
January
18th
is
the
first
date
here
on
the
list.
That's
only
ten
days
away
and
that's
the
call
for
papers
for
Cuba
on
Barcelona.
A
So
anybody
who
wants
to
submit
things
or
kind
of
define
what
you're
going
to
be
doing
you
know
in
talks
or
on
stage
in
Barcelona,
needs
to
be
figured
out
or
described
at
least
in
the
next
ten
days.
That's
a
big
one
for
the
so
releases.
You
know
we
want
to
have
a
good
release.
Cadence
here,
I'm
thinking,
like
quarterly
releases,
is
probably
going
to
be
a
good
pace.
To
keep
up.
A
You
know
so
Barcelona
is
at
the
end
of
May
ish,
so
I
don't
want
to
wait
for
all
the
way
until
May
for
another
release,
so
I'm
thinking
about
a
0.2
release,
kind
of
more
in
the
near
short-term,
more
like
around
the
end
of
March.
Beginning
of
April,
maybe,
and
then
at
the
end
of
May,
we'll
be
trying
to
push
for
a
0.3
release.
That's
kind
of
more
that
vision.
Complete
we
were
talking
about.
A
Another
important
date
is
July
12th
for
the
North
America
call
for
papers,
but
that
is
very
far
in
the
future
right
now
and
we
can
take
a
little
breather
from
that
and
then,
as
we
mentioned,
the
Cuba
on
North
America
in
San
Diego
is
November
18th
and
that's
where
I
happen
to
live.
So
that's
I'm
very
excited
about
that.
A
So
talking
about
building
the
community
a
little
further,
you
know:
we've
got
a
cup,
some
engineering
resources
that
are
already
you
know
have
put
some
time
into
this
project
and
obviously
we
want
to
keep
expanding
that
we
want
to
build
the
community
and
have
more
contributors
to
it.
So
we
need
to
think
a
little
bit
about
you
know
what
sort
of
you
know
what
the
community
looks
like
to
be
able
to
deliver
on
this
full.
It's
not
just
a
two-person
project.
A
You
know
it's
going
to
be
much
bigger
than
that
and
another
thing
to
think
about
too.
If
a
p.m.
roll
sort
of
fits
into
that
you
know,
if
there's
gonna
be
somebody
that
wants
to
you
know
rise
up
into
kind
of
take
some
of
the
more
you
know,
project
management
tasks
on
it
may
be
sort
of
you
know,
partner,
integrating
with
partners,
and
things
like
that.
A
So
that
may
be
something
that
we're
missing
right
now
in
terms
of
skill
set
that
might
be
interesting
to
have
from
the
community
and
then
we'll
talk
about
it
in
the
roadmap
too.
But
some
of
these
are
some
of
the
really
important
features
that
we've
identified
so
delivering
on
this
vision
of
you
know
portable
workloads
and
scheduling,
workloads
that
are
heterogeneous
across
multiple
cloud
environments
and
local
environments.
One
of
the
big
things
that
we
need
to
execute
on
there's
a
whole
lot
of
meat.
There
is
the
scheduler
Ilya
has
started
on
some
of
that
design.
A
Work
that
he's
he's
gonna,
take
tackling
on
right
now
and
that's
gonna,
be
a
huge
big
meaty
feature.
That's
gonna,
take
a
lot
of
work.
To
really
kind
of
you
know,
be
able
to
optimize
for
scheduling,
resources
and
the
right
region
or
cloud
provider
scheduling
for
optimizing
for
certain
attributes
like
cost
and
things
like
that,
and
so
it's
a
really
I
think
it's
important
too,
that
we
make
that
extensible
so
that
you
know
other
schedulers
can
be
plugged
in,
and
you
know
that
that
everything
doesn't
have
to
be
jammed
into
the
one.
A
You
know
entry
scheduler,
obviously
expanding
all
of
these
supported
resources.
You
know
we
have
buckets.
We
have
my
sequel.
We
have
Postgres
now
just
recently,
we've
got
kubernetes
clusters,
but
we
want
to
keep
expanding
that.
You
know
it's
in
order
to
support
complicated
applications
and
heterogeneous
applications.
We
need
to
expand.
You
know
the
set
of
maintenance
services
for
cloud
providers
that
we
support
and
also
expand.
You
know
local
scenarios
as
well.
A
You
know
distributed
software
solutions
that
maybe
use
the
operator
pattern
and
also
the
cloud
providers
that
we're
not
even
you
know,
haven't
integrated
in
with
yet
there's
a
bunch
of
other
ones
out
there.
We
focus
on
Azure
in
AWS
in
GCP
so
far,
but
there's
other
ones.
That
would
be
great
to
integrate.
With
with
also
we
already
talked
about
heterogeneous
workloads-
and
you
know
there's
a
lot
of
work
to
think
about
here
like
serve
lists.
You
know
we
want
to
do
that.
We
want
to
be
able
to
help
with
you
know.
A
Deploying
functions
may
be
able
to
allow
those
to
be
part
of
your
applications
that
you
can
deploy
across
clouds
and
from
own
premises
with
cross
plane,
but
there
hasn't
been
much
thinking
on
that.
So
we
need
to
start
digging
and
you
know
get
design
on
that
and
then
there's
a
whole
bunch
of
you
know
engineering
improvements.
A
You
know
we
want
to
keep
this
project
at
a
high
quality
level
and
efficiency
and
process
and
all
sorts
of
things,
and
the
experience
of
the
project
is
important
to
there's
some
rough
edges
right
now
that
we
want
to
smooth
out
and
that's
something
that
I
think
is
going
to
be
really
big
for
getting
feedback
from
the
community
on.
Is
you
know
the
people
that
are
actually
using
this
or
starting
to
get
some
experience
with?
What
are
the
rough
edges?
What
are
the
things
that
we
need
to
smooth
out?
A
What
are
the
features
and
scenarios
that
we
need
to
enable
that
we
might
not
have
thought
yet
and
then,
of
course,
reliability
and
purpose
huge
for
for
that,
skort
of
that
you
know
getting
towards
GA
stability,
a
production
ready,
so
I
think
the
rest
of
this
stuff
is,
you
know
like
designs
here
that
we
want
to
that
we
need
to
get
going
on.
He
has
already
started
on
a
scheduler
design,
heterogeneous
workloads.
A
We
need
you
know
it's
more
thinking
about
like
how
we
integrate
and
introduce
server
lists,
and
then
also
you
know
what
we
actually
want
to
show
in
Barcelona
I'm,
taking
a
stab
at
that
right
now
to
sort
of
figure
out.
What
the
experience
that
we
want
to
be
able
to
show
off
in
a
few
months
is
and
then
we're
gonna
work
backwards
from
that
to
start
implementing
it
and
I
think
that's
pretty
much
everything
I
had
in
this
sort
of
this
2019.
You
know
high-level
planning,
thinking
document.
C
A
A
workload
right
now
is
a
kubernetes
deployment
and
maybe
a
service
on
top
of
that
for
for
ingress
to
it
too,
and
you
know
it's
that's
pretty,
constraining,
that's
pretty,
that's
not
very
flexible,
so
being
able
to
maybe
have
the
payload
of
a
workload.
Be
a
home
chart
that
installs.
You
know
your
application,
you
know
in
wherever
the
scheduler
has
decided
that
it
needs
to
run.
That
would,
you
know,
is
one
way
to
expand
the
breadth
of
coverage
of
types
of
applications
that
crossplane
can
support.
A
I
am
I,
don't
know
exactly
where
you
know
private
from
a
priority
standpoint,
all
that
fits
but
the
overall
goal
of
being
able
to
deploy
complicated
applications
that
are
comprised
of
many
disparate
parts.
You
know
or
not
everything
is
going
to
be
a
container.
You
know
it
may
be
function,
server
lists
or
it
could
be.
You
know
higher
level
infrastructure
I'm,
not
we're
not
exactly
sure
when
those
it
needs
to
be
more
thinking
on
that
Zach
I.
F
Have
a
question
as
well,
so
when
you
mentioned
about
workloads
in
and
that's
what
I
seen
in
the
past,
so
we
you,
we
usually
have
shared
services
and
also
we
have
workloads,
so
is
crossplane
also
going
to
allow
the
deployment
of
shared
services
and
for
shared
services.
I
mean
like,
for
example,
an
envier
right.
F
A
That's
a
great
question
jorge
and
thank
you
for
joining
today
as
well.
I
appreciate
you
being
here,
definitely
so
so
my
take
on
that
is
that
you
know
that
I
believe
is
part
of
being
able
to
deploy
complicated
applications.
I
think
that
you
know
like
firewall
networking
connectivity
all
that
sort
of
stuff
is
pretty
important
to
get
things
actually
working,
especially
when
you're
getting
into
scenarios
where
you're
deploying
across
cloud
providers
across
you
know
disparate
sites.
You
have
to
have
them,
be
able
to
connect
and
talk
together.
A
So
with
you
know
a
lot
of
those
cases,
they
may
be
shared
resources
like
you're
talking
about,
and
so
there
is
some
where
did
I
capture
that
there
is
here.
We
go.
There's
this
bullet
point
here.
So
there's
a
concept
of
you
know
a
workload
being
able
to
declare
the
resources
that
it
needs.
You
know,
inside
of
its
workload
and
there's
a
it
seems
to
be.
A
There's
definite
possibility
that
some
of
those
resources
like
network
connectivity
or
some
shared
those
resources
may
be
shared,
and
so
multiple
workloads,
referencing
the
same
underlying
resource
I
think
would
absolutely
be
something
that
would
need
to
be
tackled
and
I,
don't
believe.
It's
necessary
data
scope,
okay,.
A
A
Absolutely
I
think
that's
important
here
that
all
these
designs,
you
know,
are
solicited
for
community
feedback,
so
you
know
everything
in
the
0.1
timeframe.
That
was
all
done
before
the
repo
was
made
public
in
it.
Now
that
the
repo
is
public
in
that
we're
building
a
community
around
it,
we
do
have
a
design
folder
in
the
main
repoed
that
where
these,
like
one
pagers
and
design
documents,
will
go,
and
so
the
normal
workflow
here
is
going
to
be,
you
know,
opening
a
pull
request
that
has
the
design
document.
You
know
in
that
design.
B
A
A
The
kind
with
markdown
gets
a
little
unwieldy,
and
it's
it's
it's
not
quite
as
interactive,
and
so
starting
with
the
shared
document
and
when
there's
going
to
be
a
lot
of
collaboration
makes
a
lot
of
sense
and
then,
as
things
settle
like
Bassam
said,
you
know
moving
it
to
a
per
request
and
markdown
and
more
it's
more
solidified.
So
go
ahead.
Rabi
yeah.
E
We
are
trying
to
add,
like
more
managed.
Services
are
provided,
managed
services
as
part
of
the
milestone
or
like
every
managed
service
for
every
cloud
provider
going
to
be
in
the
same
Drupal
or
because
we
can
have
like
50
minute
service
for
a
cloud
provider,
and
we
may
need
to
have
like
50
controllers
or
20
controllers
or
30
controllers.
So
all
of
them
are
going
to
reside
within
the
same
repo.
A
Yeah
right
now
you
know
everything
is
in
the
same
source
code
repository
and
that's
definitely
has
a
lot
of
benefits
for
convenience
right
now,
especially
when
there's
a
there's
a
lot
of
churn
in
the
foundation
of
the
project
like
the
core
libraries-
and
you
know
all
the
dependencies
of
you
know:
mandus
service
provider,
controller
implementations-
you
know,
take
dependencies
on
that
core
lot.
Library,
that's
still
churning
a
lot
having
an
all-in-one
repo
is
so
much
more
effective
from
a
developer,
iteration
standpoint,
but
it's
at
its
I.
A
D
If
you're
out
of
tree,
you
should
be
able
to
do
everything
that
an
entry
provisioner
can
do,
and
so
we
we
should
try
to
keep
that
property,
and
then
you
know,
if
that's
the
case,
that
we
can
move
code
around
and
think
about
versioning
and
packaging
later
right
now,
there's
a
ton
of
efficiency,
as
Jared
mentioned,
about
keeping
everything
in
tree
for
the
types
of
work.
Now,
as
we
iterate
over
time,
I
think
we'll
probably
break
things
up.
Yeah.
C
I've
got
a
question
as
well,
so
obviously,
as
I
said,
bring
you
to
cross
plane,
so
I
was
thinking.
I
mean
had
the
chance
to
go
through
all
the
dogs.
Yet
is
it
fair
to
think
of
it
as
sort
of
a
tariff
on
top
of
kubernetes,
where
in
the
sense
that
you
could
have
say
the
equivalent
of
a
telephone
provider,
you
know
provisioning?
C
A
Yeah
and
that's
that's,
that's
something
that
I
think
is
a
good
way
to
start
thinking
about
it.
You
know
that
you
can
think
of
crossplane
as
deploying
a
lot
of
services
and
in
a
lot
of
different
environments,
it's
sort
of
similar
to
what
terraform
does
but
I
think.
A
big
difference
here
is
that
crossplane
is
really
focused
on
portability
of
your
workloads.
A
So
you
know
you
define
your
application
a
single
way
and
then,
with
these
abstractions
and
primitives,
that
crossplane
provides
that
same
application
will
be
able
to
be
deployed
without
any
changes
to
all
those
different
environments.
So
it's
you
know
it's
very
portable
across
all
those
environments,
that's
something
that
crossplane
focuses
on
heavily
and
then
also
a
big
difference.
To
is
that
all
of
these,
the
controllers,
the
the
the
software
that
does
the
deployment
and
provisioning
of
your
resources
they're
all
an
active
reconciliation
loops.
A
So
they
they
don't
just
deploy
it
upfront
and
then
go
away
kind
of
like
a
terraform
apply.
They
sit
there
in
active
reconciliation
loops
and
if
things
deviate
from
the
desired
state
that
you
want,
then
it
would
be
able
to
take
steps
to.
You
know
bring
it
back
to
your
desired
state,
which
is
definitely
a
big
difference,
so
it's
you
know
actively
managing
it
ongoing
yeah.
A
A
You
know
we've
added
support
for
a
lot
of
those
already,
but
then
the
overall
big
picture
of
you
know
what
does
get
lab
need
as
a
whole,
cohesive,
complicated
application
or
in
order
in
order
to
deploy
successfully
and
what
features
are
needed
for
that
that
we're
still
in
the
design
phase
for
and
we're
kind
of,
you
know
in
requirements,
gathering
and
understanding
of
that.
So
that's
that's
early
right
now
for
that
get
lab
support.
A
D
D
A
D
D
Yeah
I
I
think
we'll
well
I
believe
there
is
a
well
most
of
this
stuff
will
start
showing
up
as
early
as
like
next
week
in
terms
of
issues
and
so
so
definitely
keep
track
of
the
across
my
treat
mode.
If
we,
if
we
end
up,
if
there's
a
good
luck,
repo
that
gets
created
for
this
work,
we'll
probably
try
to
cross-reference
those,
and
we
can
bring
it
up
at
the
next
community
meeting
as
well.
A
Omar,
it's
definitely
useful
to
you
know
to
have
that
that
knowledge
to
that
you
know
you
have
interest
in
that.
You
know
that's
kind
of
that's.
Why
I
like
these
community
meetings
in
this
inner
disability
that
we
have
to
kind
of
as
a
community
discuss,
you
know
what's
important
to
us
and
you
know
make
sure
that
we're
all
going
in
a
shared
direction.
You
know
so
yeah.
Thank
you
very
much
for
bringing
that
up.
B
F
F
Cross-Play
going
to
manage
compliance
say
like
ISO
27001,
yes
to
name
something
so
is
that
something
that
is
going
to
be
included
is
like
an
extension
that
can
be
used
to
say
this
workload
is
going
to
be
compliance
with
these
specific
controls
and
an
usher
policies
can
be
used
to
feed
that
into
crossplane
or
is
going
to
be
a
different
policy
engine
in
cross
plane.
That
is
going
to
manage
that
so
I
would
like
to
yeah
I'm.
Just
mentioning
something
like
that
to
see
if
you
guys
thought
about
using
policies.
F
D
There
is
a
description
of
policy
that
could
be
authored
by
administrators
or
infrastructure
owners
and
in
consent
constrains
on
what
say:
workloads
are
able
to
do
or
what
resource
resources
are.
You
know
able
to
do
it
and
have
that
apply,
but
it's
super
early
work
and
so
I
think
you
know
if
you
want
to
help
there,
that
I
would
be
great.
We
could
notice
with
a
couple
use
cases
and.
C
D
C
F
A
And
horny
I
think
you
had
already
opened
an
issue
about
compliance
measure.
So
yes,
if
you
you
know,
were
able
to
start
a
document
that
starts
kind
of
collecting.
Some
of
those
ideas
that
linking
it
to
that
issue
would
be
really
helpful.
Well,.
F
A
Wrong
all
right,
so,
let's,
let's
move
on
you
know
in
the
planning
document
that
we
were
just
looking
at
I
started
an
effort
at
sort
of
capturing
that,
in
our
roadmap,
is
well
there's
an
open
pull
request
for
this
number
275
to
discuss
this
further.
So
it's
not!
You
know
committed
to
the
main
road
map
yet,
but
this
is
just
a
quick
like
look
at.
You
know
the
ideas
in
that
planning
document
and
you
know
capturing
them
in
more
formal
in
the
roadmap
here,
that's
published
in
the
repo.
A
So
as
we're
sort
of
talking
about
you
know
a
0.2
milestone
before
Barcelona
to
kind
of
deuce
to
kind
of
expands.
The
scope
of
the
services
that
the
cross
plane
supports,
gets
a
good
start
on
the
workload
scheduler.
You
know
get
some
more
scale
again
scheduling
capabilities,
a
little
bit
more
fleshed
out
in
the
repo,
but
also
a
lot
of
its
gonna
be
designed
work
because
it's
gonna
be
a
long
effort.
It's
not
gonna,
be
all
in
that
one
milestone,
I,
think
so
doing
that
upfront
design
work
is
gonna,
be
really
important
and
it's
them.
A
You
know
engineering
and
improve
UX
sort
of
stuff
too,
for
that
0.2
milestone
is
what
I'm
thinking
and
then
0.3.
This
is
kind
of
gonna
be
around
the
same
time
frame
is
Barcelona
and
we'll
be
able
to
show
off
some
more
complicated
applications
running
like
get
lab,
and
you
know,
executing
or
having
more
fleshed
out
execution
of
the
full
vision
here.
I
mean
with
the
heterogeneous
workloads
and
things
like
that
and
then
beyond
that
it
gets
a
little
more
fuzzy,
but
the
focus
really
is
on
production
ready
and
getting
to
GA
in
stable.
A
So
that's
open
in
a
pull
request
to
75.
That
is
open
for
comments
from
everybody
and
there's
some
more
work
that
I
need
to
do
there
of
I.
Think
it's
I
like
the
policy
in
a
road
map
having
issues
that
are
captured
and
linking
to
it
in
the
road
map.
Then
I
have
not
done
that
for
all
the
issues.
Yet
so
I
still
need
to
update
the
pull
request
to
get
issues
opened
and
tracking
all
this
stuff.
All.
A
Right
yeah,
so
if
anybody
wants
to
to
comment
on
that,
it's
ProQuest
275
and
the
link
to
it
is
in
the
agenda
document.
Okay,
so
for
community
topics
and
questions
here,
one
thing
I
wanted
to
bring
up
is
that
you
know,
as
we
want
to
build
the
community
here
and
attract
new
contributors.
I
think
a
very
good
way
to
do
that
is
to
have
to
make
good
use
of
the
good
first
issue
label
in
the
in
the
repo.
A
We
need
to
take
a
pass
and
identify
more
issues
that
fit
this
there's
only
a
handful
right
now,
but
I
that
have
been
tagged
but
I
know
that
there
are
definitely
more
of
them
that
fit
that
bill.
So
if
you
are
a
new
contributor
interested
in
you
know
providing
commits
or
fixing
issues
in
crossplane,
this
good
first
issue
label
is:
it
will
be
a
good
set
of
ones
to
tackle
first
and
kind
of
get
ramped
up
there
and,
as
you
know,
engineers
that
have
been
in
the
repo
for
a
little
bit
longer.
A
A
All
right,
let's
so
then
another
segment
here
of
the
community
meeting
is
talking
about
poor
requests
that
we
want
to
kind
of
make
progress
on
or
have
a
little
bit
of
discussion
on.
There's
only
one
I
think
that's
still
open
that
I
don't
know
if
there's
some
good
traction
on
it.
That
Luke
had
opened
about
kind
of
streamlining
some
of
the
eks
support,
because
there's
a
few
manual
steps
right
now
and
this
would
add
the
ability
to
streamline
some
of
that
I.
A
Don't
think,
there's
a
chat
going
on
sorry,
let
me
make
sure
that
I'm
not
missing
anything
there.
Sorry,
oh
cool!
This
is
from
all
right,
Thank,
You,
Jorge
and
yes,
so
I
think
that
this
needs
a
review.
Ilya
is
this
thing
that
you
would
be
able
to
take
a
look
at
I?
Think
you
have
more
familiarity
with
this
topic
and
be
able
to
provide
some
feedback
if
needed.
I
can.
A
A
A
So
we
have
a
couple
playlists
here.
One
of
them
is
the
community
meetings
here
that
that's
where
this
meeting
will
get
uploaded
to
and
then
we
also
have
some
talks
that
we've
we've.
You
know
from
last
cubed
on
there.
So
if
you
miss
any
of
those
talks
like
Ilias
clusters
as
cattle
talk,
which
was
amazing,
you
know
you
can
go
to
that
playlist
and
check
it
out
there
and
then
check
out
any
of
the
community
meetings
that
you
happen
to
miss.