►
From YouTube: 2019-06-11 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.
This
is
the
June
11
2009
teen
cross
playing
community
meeting,
and
so
we
will
start
with
current
milestone.
So
we've
done
a
little
bit
of
work
after
getting
back
from
Cuba
and
Barcelona
and
to
figure
out,
you
know,
identify
some
issues
of
technical
debts
and
some
quality
issues
that
we
want
to
address.
So
the
remainder
of
the
0.3
milestone,
which
does
include
all
the
work
we
did
for
supporting
gitlab
the
remainder
of
the
milestone,
we'll
be
focusing
on
addressing
some
of
that
technical
debt
and
also
a
stab
of.
A
So
I'm
gonna
go
ahead
and
bring
up
the
0.3
milestone
and
project
boards.
So
I
we
took
a
pass
through
the
0.3
milestone
and
we
updated
the
issues
that
are
in
the
milestone
with
what
we
believe
to
be
the
higher
priority
issues
around
establishing
patterns
and
practices
and
technical
debt
and
quality
engineering
quality
type
of
related
issues.
So
these
are.
A
Roughly
prioritized
as
well,
so
we
have,
you
know
going
from
top
to
bottom.
You
know
these
are
all
issues
and
I
think
we
should
address
in
0.3,
and
you
know
they're
pretty
much
I
think
in
order
to
which
we
can
attack
them
as
well.
One
of
the
big
outstanding
things
is
this:
release
pipeline
is
kind
of
a
bit
of
an
unknown.
Now,
where
we
shipped
the
0.2
milestone
with
a
bit
of
a
manual
process.
A
We
have
builds
scripts
and
make
files
and
all
this
automated
logic
that
runs
and
publishes
the
build,
artifacts
and
tags
and
all
that
sort
of
stuff.
But
we
don't
have
integration
with
our.
You
know:
continuous
and
continuous
integration,
continuous
deployment,
type
of
environment
or
Jenkins
environment
to
run
all
that
automated
forests.
So
the
last
release
we
did
that
from
a
developer
laptop,
and
we
are
hoping
to
address
this
with
a
fish
tool
build
automation
to
such
that
we
run
the
0.3
release.
It
will
be
done
from
the
official
Jenkins
build
server.
A
And
then
we
have
a
number
of
items
that
are
related
to
you
know,
issues
to
that,
make
it
difficult
to
to
contribute
to
cross
flane
issues
that
make
it
difficult
to
be
a
maintainer
on
cross
plane,
issues
that
make
it
difficult
for
newcomers
to
use
crossplane
we.
So
this
is,
as
I
was
saying
these
year
down
three
milestone
here.
Is
the
output
of
you
know
that
exercise
around
trying
to
get
some
some
ideas
around?
Where
are
the
areas
that
mean
to
attack
in
terms
of
our
technical
debt
and
establishing
patterns,
etc?
A
There
was
another
board
I'd
like
to
show
everyone
to
that.
We
put
together.
That
was
the
big
you
know
all
these
issues
and
kind
of
categorized
as
well.
They
kind
of
fed
into
our
you
know,
milestone
prioritization.
So
this
this
technical
debt
prioritization
board
here,
is
just
a
first
stab
at
finding
out
all
the
issues
that
are
affecting
our
engineering
quality,
our
engineering
processes,
you
know
preventing
other
people
from
coming
and
writing
new
new
controllers
and
services,
etc.
So
this
is
just
a
big.
A
A
And
if
there's
any
other
feedback
or
ideas
around,
so
you
know
what
are
some
of
the
biggest
pain
points
in
crossplane,
then
getting
issues
opened
on
that
issues
are
very
welcome
and
desired
and
we'll
be
happy
to
as
a
community
incorporate
those
into
the
mid.
The
planning
for
this
milestone
and
future
milestones
as
well.
B
Yeah,
so
this
actually
would
be
perfect
for
shooting
over
to
get
lab,
did
put
a
post
on
the
cross
plains
like
over
there.
So
I
think
this
information
about
like
what
we're
doing
and
then
that
board
that
shows
the
groupings
would
actually
just
be
perfect
for
for
actually
kind
of
replying
back
on
that
issue
that
they
had
posted
as
well.
So
this
is
great
I.
Think.
A
A
That's
in
another
repo
that
is
not
in
the
main
cross,
plane
repo,
that's
in
a
get
lab,
troller
repository
underneath
the
cross,
plane,
io
organization,
and
so
you
know
it's
been
a
bit
of
discussion
on
it,
but
it
seems
like
the
logical
place
for
bugs
or
issues
or
improvements,
etc
that
we
want
to
capture
specific
to
the
get
lab.
Implementation
would
be
done
in
that
repository
over
there.
A
So
in
terms
of
the
main
milestone
you
know,
what
we
want
in
the
cross
plane
core
to
improve
is
would
not
capture
and
everything
that
would
be
very
specific
controller,
so
I
think
it'd
be
kind
of
a
combination
of
and
I,
don't
think
we're.
We
have
everything
captured
necessarily
in
that
get
lab
controller
repo
either
there's
so
that
we
need
to
do
an
exercise
of
keeping
all
that
information
written
down
issues
opens.
You
know
better
help
us
track
the
efforts
we
would
that
any
woman
would
need
to
do
who,
in
the
lab
controller,
specifically
yeah.
B
Totally
totally
agree:
yeah,
it's
just
I,
think
I'm.
There
get
lab
stuff.
These
posted
issue
like
one
155
and
it's
just
title
evaluation
of
cross
playing
as
a
means
for
provider
agnostic
month,
like
pot
deployment,
and
they
just
we're
looking
for
some
additional
info
and
I
think
that
kind
of
just
cross-linking
that
for
just
the
feedback
on
cross
point
specific,
completely,
probably
helped
a
lot
but
yeah
I
totally
agree
to.
Thank
you.
Live
controllers
was
a
separate
thing
and
so
should
keep
the
feedback
for
that
supper.
Yes,.
A
A
A
All
right,
the
next
item
I
had
here
was
around
you
know
general
roadmap
planning.
So
we
had
discussed
this
in
the
last
meeting
last
community
meeting
here
about
taking
a
two
layered
approach
to
our
roadmap,
and
you
know
our
upcoming
milestones
and
themes
that
we
want
to
accomplish
with
the
cross
plane
project.
So
the
first
one
would
be
you
know
about
making
you
know
extending
kubernetes
to
be
able
to
have
standardize
on
the
kubernetes
api
and
be
able
to
manage
and
deploy,
configure,
manage,
etc.
A
So
that
is,
you
know
still
the
you
know
what
the
community
thinking
is
here,
but
we
have
some
more
work
to
do
to
actually
update
the
roadmap
and
capture.
All
of
that,
and
so
I
just
wanted
to
make
a
note
here
in
this
meeting
that
you
know
any
sort
of
feedback
or
input
into
the
roadmap
in
future
milestones
that
the
community
would
like
to
see.
A
All
right
and
then
the
I
did
want
to
just
bring
up
one
pole
request
here
that
we
have
open
so
there's
a
couple
of
folks.
A
couple
of
users
in
the
community
noticed
that
our
cloud,
sequel
creation
and
deployment
has
a
regression
or
a
bug
and
such
that
it's
preventing
it
from
being
able
to
instantiate
and
be
available
for
the
workloads
to
consume
the
database.
A
So
one
of
our
community
members
opened
an
issue
on
this
and
suggested
a
potential
workarounds
is
well
Marcus
took
on
this
took
on
that
fix
with
this
particular
pull
request
and
I
was
kind
of
curious
as
to
the
fix
here
or
how
this
works
actually
of
how
this
addresses
the
issue
where
we
pass
in
the
host
field
of
the
user
is
that
is
that
something
that's
already
set?
Is
there
like
the
guarantees
around,
that
you
know
being
a
non
empty
string,
or
how
does
that
work
exactly?
What
does
that
value
come
from?
So.
C
We
go
filled
to
start
update
user
operation
for
user
root
invalid
request
invalid
host
in
request
body,
so
it
wasn't
sending
a
host
at
all
and
I
checked
what
the
my
sequel
user
accounts
were,
because
the
way
that
we
get
the
account
that
we're
going
to
update
as
we
we
run
through
the
available
accounts
and
I
checked,
and
there
was
a
root
at
that
percent
account
on
there.
So
the
wild
card
host,
and
so
what
happens
in
this
updated
update
statement
is
that
we're
a.
C
I
didn't
want
default,
so
what's
happening
in
this
update
statement
now.
Is
that
we're
we're
we're
getting
our
update
request
back?
It
doesn't
have
the
host
set
and
then
we're
just
using
this
dot
host
method.
That's
available
there.
It's
a
setter
that
updates
the
update
request
with
the
host
and
then
we're
calling
do.
Oh
and.
A
C
C
A
Awesome,
that's
that's
great
that
we
found
that
and
I
definitely
think
it's
good
that
we're
being
able
to
address
these.
You
know
issues
that
are
found
by
the
community.
You
know
quickly
as
well.
I
love
it
like
that
and
I,
also
like
everything
about
Thomas's
user
name
and
his
icon
as
well.
I
like
everything
about
this
that
is
so
cool
alright.
So
let's
go
back
to
the
agenda
document
and
I
believe
that's
all
that
I
had
on
the
agenda
document
today.