►
From YouTube: 2020-08-17 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
is
started,
and
this
is
the
august
17th
2020
cross
playing
community
meeting
kubecon
is
ongoing
right
now,
as
we
speak,
we
had
our
project
office
hours
earlier
this
morning,
yeah
one
and
but
we'll
get
into
that
a
little
bit
more
later
on.
Let's
do
a
check
in
on
0.13
real
quick.
What's
the
latest
on
the
release,
timing
and
time
frame
for
that?
If
somebody.
B
C
That
was
originally
my
understanding,
but
I
believe
that
actually,
in
conversation
with
bassam,
we
were
actually
thinking
about
pushing
we're.
Basically
thinking
about
skipping
this
right,
yeah
there'll
be
not
that
much
in
the
release.
At
the
moment.
A
lot
of
the
last
month,
we've
spent
thinking
about
ways
that
we
can
take
some
of
our
existing
features
and
really
put
them
on
the
on
the
pathway
to
sort
of
be
one
beta.
C
One
stability
which
a
lot
of
the
cross
plane
is
around
apis,
so
that
we've
spent
a
lot
of
time,
just
thinking
about
concept,
names
and
talking
to
the
community
and
things
like
that
and
just
figuring
out
sort
of
some
things
we
can
lock
down,
and
so
we've
focused
on
that
a
lot
rather
than
sort
of
you
know,
building
code
the
last
month
or
so
so
we're
now
getting
to
the
point
that
we're
close
to
locked
down
some
of
those
things
and
we've
torched
the
community
and
we're
feeling
good
about
the
concepts
and
we're
just
gonna
get
into
the
building
code.
B
Yeah
totally
and
there's
kind
of
like
this
example,
cmp
cloud
native
platform,
repo
that
nick
put
together.
That
would
probably
be
worth
going
over
briefly
and
then
a
lot
of
the
effort's
going
to
be
around
getting
kind
of
like
a
thin
slice
of
that
all
built
working
across
like
the
crank,
which
is
a
new
package
manager.
B
And
then,
if
there's
things
in
composition,
there's
some
renaming
and
stuff
like
that
so
yeah.
Definitely
we
can
maybe
spend
five
five
minutes
on
that
or
something.
D
Yeah
yeah,
I
think,
like
in
the
next
series.
If
we
skip
this
one,
we
will
be
able
to
release
cross
plane
agent
as
well
together.
A
B
Yeah
to
be
determined,
I
think
that's
a
great
conversation
to
have.
I
know
that,
like
the
official
release
process
is
monthly
and
there's
been
some
discussions
on,
you
know,
do
we
want
to
kind
of
keep
doing
that
or
what
not
so
maybe
that'd
be
a
good
sidebar
topic.
A
What's
what
are
the
things
that
we
really
want
to
include
like?
Because
it
seems
to
be
like
more
of
a
feature
driven
than
a
time
driven.
B
Yeah,
so
I
think
it's
basically
the
ability
to
to
package
and
run
the
example
cnp
repo.
B
C
B
Yeah,
and
so
it
seems
like
there's
some
things
that
we
definitely
can
cut
out
and
that
the
current
example
cmp
is
like
the
north
star
is,
you
know,
nick
puts
it,
and
so,
if
so
most
of
the
stuff
in
there
looks
like
should
be
able
to
fit
so
it'd,
be
interesting
to
kind
of
maybe
do
an
update
at
the
next
community
meeting
on
like
what
the
reduced
scope
one
is
because
it
sounds
like
we
need
to
kind
of
get
that
figured
out
if
we
have
roughly
you
know
a
month
or
a
month
and
a
week
to
get
that
done,
or
you
know,
however
long
that's
going
to
take
to
get
so,
were
there
things
nick
that
you
saw
that
were
maybe
when
we
go
over
it,
we
could
just
highlight
the
things
that
are
likely
to
be
cut.
C
Areas
of
concern
for
me
anything
that
we're
still
debating,
we
have
seven
or
eight
issues
open
that
are
still
trying
to
arrive
on
on
solutions
too.
Anything
that
is
going
to
take
us
another
10
days
of
of
trying
to
figure
out
what
we
build
is
taking
time
away
from
building
it.
So
so
yeah,
my
my
areas
of
concern.
Are
that,
like
things
like,
you
know,
ui
shiba?
What
are
we
gonna
do
with
that?
How
are
we
gonna
build
that
et
cetera,
et
cetera?
C
We
still
haven't
locked
out,
so
I'm
definitely
not
ready
to
commit
to
anything
that
we
haven't
the
you
know,
okay,.
B
For
that
one
I
mean
stephen.
If
you're
on
the
line
I
mean,
would
it
make
sense
for
you
to
take
point
on
kind
of
getting
a
pr
against
the
branch
for
that,
and
then
then
that
can
kind
of
make
sure
that
you
have
what
you
need,
and
I
don't
think
that
we're
like
super
opinionated
on
that.
But
that
might
be
something
that
we.
B
About
a
little
bit
later,
can
we
have
time
yeah.
We
can
definitely
discuss
it,
some
more,
I'm
not
sure
where
we're
at
right
now
I
haven't
updated
myself
with
the.
C
Current
status
of
those
issues,
but
yeah
something
we
can
discuss
cool
yeah,
so
we'll
definitely
you
know
the
goal
is
to
really
sum
up.
We
will
release
something
at
the
end
of
next
month.
The
question
is
just
how
about
you
know
talking
to
different
people
within
upbounds.
They
interpret
the
the
goal
of
this
repo
and
the
scope
of
this
repo
quite
differently,
so
that
we
we
still
need
to
figure
out
what
we're
building
and
I'm
as
keen
as
anyone
to
move
out
of
that
phase
into
the
building
something
phase.
B
Yeah,
it
sounds
like
most
of
that
can
actually
just
proceed
right
now,
like
the
stuff
that
we're
blocked
on
seems
like
it's.
B
Than
like
blocking
for
implementation,
so.
C
Yeah
well
yeah,
I
would
say:
there's
two
classes
of
things:
there's
stuff
that
we're
blocked
on
and
as
soon
as
we're
unblocked,
it's
trivial
changes
like
naming
fields,
things
like
that.
That's
just
taking
time
to
rely
on
names,
and
then
there
are
things
that
you
know.
In
some
cases,
building
our
back
controllers
were
not
blocked
out.
All
of
that
which
blocked
on
doing
the
design
work
so
that
because
we
can't
be
programming
with
one
hand
and
scheduling
so
yeah.
C
I
think
it's
worth
noting
just
from
the
core
cosplay
team
as
well.
Just
just
other
things
that
will
play
into
this
is
that
dan
mangum
is
on
vacation
for
a
week
at
the
moment
and
getting
married
yeah
and
then
casey
hasn't
been
too
involved
in
this,
because
who
hasn't
been
too
involved
in
this
so
far
to
be
focused
on
providers.
But
he
will
be
on
vacation
driving
his
family
to
texas
in
a
week
or
two
as
well.
B
Would
it
make
sense
to
maybe
just
now
that
we're
past
that
just
to
walk
through
the
the
cmp
repo,
real
quick-
and
I
don't
know
if
you
wanted
to
just
do
a
super
quick
overview
for
people
that
might
be
catching
the
replay
or.
C
Sorry,
I'm
yes,
I
can
but
give
me
one.
Second.
B
And
then,
while
nick
is
doing
that
for
the
provider
acceleration,
I'm
not
sure
if
casey's
on
the
line,
but
casey
has
basically
just
been
doing
a
ton
of
work
on
that.
So
he
has
some
example:
repos
that
are
in
his
github
account
and
there's
a
design
doc
that
I
think.
A
B
But
yeah
it's
definitely
coming
along
for
getting
broader
provider
coverage
through
code
generation,
so
making
good
progress
here.
C
All
right,
do
you
want
me
to,
can
I
shut
my
screen,
so
I
can
drive.
C
C
All
right,
so,
if
you
can
all
see
my
screen,
this
repo
is
intended
to
sketch
out
an
experience
for
what
we
think
of
as
platform
builders,
so
in
the
cosplay
project
at
the
moment,
we're
thinking
about
roughly
three
different
sort
of
personas
who
might
use
crossplay,
who
would
be
platform,
builders,
platform
operators
and
platform
consumers
and,
as
always,
with
sort
of
personas
like
this
there's,
no
guarantee
that
these
are
all
different
people.
It
could
all
be.
C
You
know
it
could
all
just
be
one
person
using
crossplay
or
you
know,
could
be
a
team
of
team
of
hundreds.
The
general
way
that
this
falls
is
crossblade's
a
tool
that
lets
you
publish
your
own
apis
for
for
managing
infrastructure.
Primarily,
so
you
know
create
your
own
opinionated
crs
for
managing
databases
or
kubernetes
clusters
or
whatever
you,
whatever.
You
need
to
do
the
people
who
who
actually
author
the
schema
of
those
crs
and
teach
cosplay
what
to
do
when
they
see
one
of
those
crs.
C
C
Not
the
configuration
that
makes
databases
actually
pop
up
or
clusters
or
whatever
you're
managing,
but
the
the
configuration
that
teaches
crosstalk
how
to
offer
that
service
to
other
people.
C
Then
we
also
have
platform
operators
who
are
sort
of
systems,
engineering
side
of
sre
people
who
might
actually
be
like
spitting
up
cross
planes
running
them,
monitoring
them
keeping
it
going.
You
know,
I
suspect
that
often
that
will
be
the
same
person
as
the
platform
builder,
but
we
do
have
some
cases
where
are
different
people,
then.
C
So
this
repo
is
focused
on
the
platform
builder
experience
the
experience
of
someone
who
wants
to
sort
of
set
up
and
configure
cross-play
to
provide
a
platform
to
people.
We
did
actually
use
one
of
our
community
members
who
had
a
better
use
case
of
cosplay
who's
been
very,
very
helpful
to
us.
C
Who's,
a
fellow
named
jan
from
accenture,
so
this
is
this-
is
sort
of
based
on
the
sketch
of
his
team's
needs,
which
is
to
provide
people
with
he
wants
to
provide
his
consumers
with
kubernetes
clusters,
and
he
wants
those
kubernetes
clusters
to
have
all
the
things
that
they
might
need
on
them.
So,
for
instance,
logging
demons,
monitoring
demons,
sort
of
the
infrastructure
stuff
installed.
In
this
case,
we've
just
got
one
more
example
of
that
which
is
a
logging
domain.
C
So
the
way
that
we
envision
configuring,
crossplane,
especially
from
sort
of
a
get
ops
patent
is,
is
something
that
leverages
our
existing
package
manager
as
sort
of
the
transport
for
getting
stuff
running
on
clusters.
C
We
think
of
this,
as
kind
of
like
a
similar
flow
to
how
docker
works.
You
can
put
a
docker
file
in
your
git
ops,
repo,
and
you
can
have
your
csv
or
jenkins
or
whatever
you
happen,
to
use
build
a
dockerfile
when
you
commit
to
build
a
docker
image
from
that
file.
When
you
commit
to
master-
and
you
know,
push
that
to
the
docker
registry,
then
you
can
have
it
deploy
from
cicd
as
well.
C
If
you
want
to
similar
idea
here
I'll
jump
into
the
there's,
there's
three
packages
in
this
in
this
repository,
the
top
one
clusters.cnp.example.org-
actually
is
a
parent
package.
It
depends
on
the
other
it's
a
little
over
complicated.
It
probably
doesn't
need
to
be
that
way,
but
we
just
wanted
to
demonstrate
what
dependency
would
look
like
between
packages.
C
So
if
you
open
up
this
one,
this
is
the
the
parent
one,
the
one
that
people
would
mostly
interface
with
we're
thinking
that
each
of
these
each
of
these
sort
of
packages
on
disk
will
will
be
represented
by
a
crosstalk
that
lets
our
tooling
know
hey.
This
is
packageable.
C
You
can
package
this
up
and
we
think
that
I
I
keep
saying
package,
but
but
we
actually
think
that,
when
folks
are
sort
of
browsing
these
from
a
from
a
sort
of
operator
standpoint
and
installing
them
they'll
think
of
them
more
as
either
a
configuration
of
crossplane
or
a
provider
for
cosplay
provider
concept
exists
already
across
plane,
we
have
provided
aws,
provided,
gcp,
etc.
They
are
sort
of
controllers
that
teach
crossfit
about
new
functionality.
They
give
you
the
primitive
types
that
you
can
actually
manage.
C
That
cross-plank
can
then
compose
up
into
more
advanced
types,
so
a
provider
just
installs
one
of
those,
so
it
would
be
a
provider
that
you
could
use
as
a
sort
of
a
package
for
aws,
you
say
a
cosplay
and
give
me
provider
aws.
It
could
be
provided
gcp
behind
the
hood
under
the
hood.
Rather
that
would
use
a
package.
C
C
The
entry
point
here
is
is
effectively
just
metadata
about
the
configuration
you
know
who
owns
it,
what
license
it's
under
things
like
that
and
then
any
packages
that
it
depends
on,
or
rather
other
other
configurations
and
providers.
In
this
case
it
depends
on
the
cnp,
eks
and
cmp,
which
are
the
other
two
packages
defined
by
this
repo.
C
As
a
side
note
we're
thinking,
we
might
actually
change
this,
but
depends
on
package.
Two
depends
on
configuration
to
really
put
that
sort
of
concept
front
and
center
that
your
you
know
that
package
is
more
the
delivery
mechanism
for
what
you're,
depending
on,
rather
than
the
actual
thing
that
you're
depending
on
and
then
inside
this
repo
we're
thinking
that
we
mostly
won't
be
too
opinionated
about
sort
of
directory,
layout
or
file
names,
or
anything
like
that,
because
everything
in
you
know
everything
that
we're
delivering
is
yaml.
C
That
is
schemified
that
we
can
discover
the
type
of
it.
So
in
this
case
it
defines
it's
got
a
it's
got.
What
we
call
here
a
composite
resource
definition
that
defines
a
new
type
called
a
cluster,
which
is
a
sort
of
a
generic
kubernetes
cluster
type
composite
resource
definition
is
currently
in
cross
lines.
Code
base,
known
as
infrastructure
definition,
we're
looking
at
ways
to
reduce
concepts,
and
we
was
using
the
term
composite
resources,
the
thing
that
it
was
actually
defined
by
this.
C
So
it
seemed
to
reduce
concepts
to
to
rename
this
to
the
composite
resource
definition,
as
opposed
to
infrastructure
definition,
we'd
love
to
hear
any
community
feedback
on
that,
because
we've
heard
roughly
50
50
at
the
moment,
people
saying
that
they
like
one
or
the
other
much
of
this
is
is
pretty
much
the
same
as
what
you
would
be
used
to
if
you've
already
seen
an
infrastructure
definition,
but
some
of
the
other
changes
that
we're
thinking
about
making
in
here
is
rather
than
having
infrastructure
publication
as
a
separate
cr
we're
likely
to
make
that
eight
well,
we
almost
certainly
will
make
that
a
field
of
the
constant
resource
definition
that
will
be
that
is
currently
in
this
sketch.
C
This
bureau
called
publication
policy.
We've
had
feedback
that
people
tend
to
think
of
publication
as
meaning
something
to
do
with
packages
which
it
does
not
in
this
case
that
we're
currently
workshoping
there's
an
issue
on
this
repo,
if
you're
in
a
way
we're
currently
workshopping
different
names
or
concepts
in
this
field
as
a
way
to
roughly
say
I,
as
the
platform
builder,
want
to
make
a
version
of
this
available
to
platform.
C
Consumers
we're
also
thinking,
instead
of
previously
across
playing
anything
that
was
was
a
published
infrastructure
definition
would
create
a
type
called
a
requirement
which
would
have
in
its
kind
a
suffix
of
requirements.
C
So
if
you,
if
you
defined
a
concept
resource,
called
a
mysql
instance,
then
your
consumers
would
deal
with
a
resource
called
a
bicycle
business
requirement
intended
to
capture
the
fact
that
that
that
is
kind
of
the
front
end
in
front
of
my
sequel
instance:
it's
sort
of
a
proxy
or
a
ship
that
still
results
in
a
bicyclist
we're
thinking
about
just
getting
rid
of
that
suffix.
C
We
can't
give
that
type
literally,
the
same
name,
so
we
do
need
to
have
different
names,
so
we're
basically
just
going
to
let
the
platform
builder
name
those
things
whatever
they
like
which
allows
them
to.
You
know
they
can
stick
with
the
status
quo
and
call
it
a
requirement
if
they
want
to
or
call
it
a
claim
if
they're
feeling
nostalgic
or
call
it
something
else
entirely
other
than
that
there
is
not
a
lot
of
changes
in
here.
C
We
are
thinking
that
we're
going
to
have
a
couple
of
community
members,
customers
that
we've
spoken
to,
who
would
like
crossplane
to
be
a
little
bit
more
opinionated
about
managing
our
back
roles,
so
we're
planning
to
to
build
a
little
bit
of
functionality
into
cosplaying.
That
manages
our
back
for
you.
C
So
when
you
define
new
api
types,
we'll
create
a
set
of
roles,
various
different
scopes
to
that
we
won't
grant
them
to
anyone,
but
we'll
make
them
so
that
you
can
grab
them
to
people
to
to
sort
of
give
people
sort
of
relatively
easy
access
on
two
types.
It
is
a
little
bit
opinionated,
it's
definitely
sort
of
not
one
size
fits
all,
so
we're
just
gonna
put
a
this
policy,
which
is
basically
like
to
turn
that
off.
C
Composition
is
not
terribly
different
than
it
was
before
the
big
changes
that
we're
looking
at
for
this
release.
We
have
a
few
other
things
coming
in
the
pipeline
for
composition,
but
the
big
changes
that
we're
sort
of
having
this
sketch
at
the
moment
are
mostly
around
changing
names
and
types
and
off
the
top
of
my
head.
I
believe
that
mostly
all
we
did
was
change
the
from
and
to
to
composite
resource
and
compose
resources.
C
There
is
a
small
debate
around
these
field
names,
as
well
as
to
what
they
should
be
yeah.
This
is
probably
going
to
be
something
like
composite
type
or
composite
resource
type,
and
this
is
probably
just
going
to
be
resources
or
something
like
that.
There
is
an
issue,
that's
tracking,
that,
on
this
repo
anything
that's
sort
of
up
in
the
air
on
this
repo
has
that's
an
issue
to
track
that.
C
C
The
final
thing:
that's
in
these
packages
is
there's
not
cross-plain
directory,
which,
if
anyone
has
worked
with
about
cloud
or
or
had
any
interest
in
that
before
or
packaged
up
things
for
crossband,
you
might
be
familiar
with
the
dot
registry
directory,
which
is
roughly
where
you
can
put
in
a
bunch
of
metadata
in
your
package
that
our
cloud
product
can
use
to.
C
Technically
any
registry
can
use
it's
a
standard
format.
That's
that's
sort
of
defined
in
cosplay,
so
so
it
doesn't
have
to
be
out
that
cloud
practiced,
since
that's
to
our
knowledge
on
that
cloud,
zero.
The
consumer
of
this
at
the
moment
that
just
teaches
it
a
little
bit
of
sort
of
extra
ui
stuff
about
this
package,
so
it
doesn't
have
an
icon.
You
know
how?
How
would
you
perhaps
build
a
advanced
web
ui
to
configure
it
and
things
like
that?
C
But
this
at
the
moment
is
relatively
unchanged:
it's
just
moved
into
a
different
directory.
C
That
is,
that
is
about
all
the
changes
off
the
top
of
my
head
in
here.
So
going
real
quick.
This
clusters,
as
you
might
have
seen
in
the
composition,
depends
on
two
other
types,
or
rather
closest
to
other
types,
which
is
a
full
and
fit
dks
which
are
defined.
I
won't
really
go
into
the
details,
but
they
are
defined
in
these
packages
here,
so
they
would
all
get
built
next
to
each
other.
So
you
can
see
the
dks
results
in
a
whole
bunch
of
actual
aws
stuff
being
created.
A
Cool
yeah,
I
really
like
that.
It
seems,
like
that's
a
really
great
place,
to
do
a
collaboration
and
get
a
shared
understanding
around
the
experiences
you're.
Having
that
repo
being
able
to
open
issues
if
they're
that
you
want
to
suggest
something,
that's
wrong
or
like
or
could
be
improved
or
open.
A
pull
request
to,
like
you
know,
add
more
to
the
sketch
here.
It's
kind
of
our
you
know
guiding
guiding
like
reference
for
a
design
sketch
of
like
okay.
This
is
the
direction
we're
heading,
and
this
is
what
we'll
be
implementing
towards.
C
Yeah,
I
saw
something
on
twitter
a
couple
of
weeks
back
that
that
that
really
stuck
with
me,
it
was
a
conversation
about
challenges
of
startups
and
joe
vader
waited
on,
and
I
think
he
said
that
one
of
the
hardest
things
he
found
did.
I
assume
heptio
was
when
people
are
talking
about
things
figuring
out
what
time
frame
they're
talking
about
things.
You
know
they're
talking
about
like
the
north
star.
Are
they
talking
about
tomorrow,
yeah,
and
I
think
that
that
has
been.
C
A
All
right
cool,
so
I
think
I'm
sharing
my
screen
again
yeah,
I
think
so
so
yeah,
let's
to
get
through
the
rest
of
the
feature
areas
here
as
we're
working
towards
0.13
phil.
You
already
gave
an
update
about
provider
acceleration
and
code
generation
move
off.
Do
you
want
to
give
a
quick
update
on
the
crossplane
agents
and
it's
moved
to
the
main
crossfit
repo.
D
D
Yeah
yeah,
so
I
have
one
big
massive
pr
that
implements
the
current,
like
end-to-end
workflow,
where
you
can
use
your
service
account
in
this
central
cluster
like
copy
it
to
your
app
cluster
and
then
have
the
agent
connect
to
it.
Sync,
the
you
know,
compositions
definitions,
publications,
everything
to
a
cluster,
and
then
you
can
create
the
requirement
and
sync
it
back
to
the
central
cluster
that
you've
already
moved
classes.
D
However,
you
would
name
it
so
right
now
it
is
current
state.
It
is
able
to
run
wordpress,
so
you
can
have
one
cluster
cross
being
clustered
on,
like
maybe
like
10
different
app
clusters
and
each
with
that,
with
the
name
space,
different
name,
space
that
corresponds
to
a
name
space
in
the
in
the
main
cluster.
D
Then
they
can
all
create
their
own
requirements
completely
independently,
either
using
the
same
service
account
or
different
one.
So
right
now
we
have
in
terms
of
namespace
matching
right.
Now
we
don't.
We
only
have
the
like
one
to
one
where
you
like
in
the
app
cluster.
If
you
use
default,
you
would
use
a
default
in
the
central
cluster
as
well.
D
So
if
you
use
like
the
same
name,
space
default
in
another
cluster,
there
could
be
some
conflicts
if
the
names
match
there
are
a
few
solutions
that
we
came
up
with
for
this
in
the
design,
but
they're
not
implemented
yet.
D
So
I'm
planning
to
get
this
this
first
and
pr
merged
with
with
all
of
its
tests
right
now
implemented
like
after,
I
think
I
have
like.
I
will
like
I'm,
integrating
the
build
sub
module
fixing
some
like
make
reviewable
problems,
and
then
I'm
planning
to
get
it
merged
this
week,
hopefully,
and
then
work
on
these
other
namespace
match
and
other
features
of
the
agent.
But
I
believe
it
will
be
usable
in
terms
of
like
just
getting
an
app
cluster
and
run
your
application
via,
like
with
the
agent.
A
Oscilloscopic,
that's
great.
It
was
good
to
see
that
demo
last
week
too,
dan
is
out
this
week
having
having
been
gotten
married
good
for
him,
congratulations,
dan,
but
then
phil.
Do
you
have
a
quick
update
on
the
package
manager,
refactor.
B
Yeah
so
there's
like
a
pr
that
he
opened
for
some
of
the
api
types
that
for
like
initial
review,
it's
draft
and
then
he's
gonna
basically
do
the
bulk
of
this.
It's
kind
of.
B
Now,
there's
some
additional
changes,
he's
gotta
make
so
he's
gonna.
Do
that
when
he's
back
from
his
his
wedding
nice.
A
All
right
last
last
community
meeting
here
we
discussed
you,
know
the
own
kubernetes,
runtime
repo
and
moving
towards
a
initial
v0.1
release.
We
were
talking
with.
I
think,
ryan
and
harry
were
weighing
in
on
that
ranjan.
That
is,
is.
Has
anyone
heard
an
update
on
that
like
moving?
What's
left
in
terms
of
moving
towards
the
initial
0.1
alpha
release?
There.
B
I
mean
we're
ready
to
go
with
that
and
there's
a
version
of
the
subchart.
That's
been
created
for
roman
kubernetes
runtime,
but
we
still
have
to
remove
the
the
app
config
controller
from
crossplane
core.
So
I
think
dan
was
going
to
tackle
that
whenever
we
were
going
to
do
our
next
release
of
across
plain
court.
So
this.
A
B
B
A
D
Yeah,
actually,
I
was
gonna
ask
a
question
about
this,
so
we're
pushing
the
release
to
mid
september.
That
means
like
0.12
and
like
whatever
oem
code
we
have
in
0.12
will
still
be
there
is.
Are
there
like
any
updates
that
we
need
to
like
maybe
do
a
patch
release
of
crossplay
to
get
them
into
like
get
the
oem
updated?
Basically,.
C
C
I,
if,
if
that,
becomes
a
problem
and
we
do
need
to
release
cosplay,
that
removes
those
controllers,
we
probably
shouldn't
do
it
in
a
patch
release
that
probably
would
justify
doing
a
whole
release
sooner.
I
don't
know
if
we
do
need
to
do
that.
It
could
just
be
the
you
know
the
om
runtime,
I
don't
know
we
need
to
figure
out
a
plan
for
that.
You
know
if
we
need
to
run
a
release,
mostly
just
to
remove
those
controllers.
C
That's
doable
running
a
release
was
something
that
we
put
off
because
it
would
save
us.
You
know
it
usually
takes
us
half
a
day
to
get
a
release
out.
If
not
a
little
bit
more
so
yeah
we
would.
We
would
no
one
would
be
able
to
run
the
new
oem
runtime
with
cosplay
until
we
release
cosplay
0.13.
B
Yeah,
so
we
might
consider
you
know
revisiting
that,
but
right
now
I
think
we're
just
going
to
hold
off
and
then
basically
we're
probably
going
to
be
packaging.
B
The
own
kubernetes
runtime
into
you
know
the
the
cross
plane
app
operator
or
whatever
the
final
name
for
that's
going
to
be
so
that's
another
change,
that's
probably
coming
in
roughly
the
same
time
frame.
B
B
Yeah,
I
know
that
there's
been
a
ton
of
work
going
on
as
far
as
like
scopes-
and
you
know
some
trait
stuff-
I
think
as
well,
but
yeah
it'd
be
good
to
do
an
update
from
them,
maybe
in
the
next
community
session
and
then
get
that
all
rolled
into
0.13.
B
A
A
Cool
okay,
so
we
can
move
down
to
the
community
topics
section
here.
Dan
hashtag
ran
a
latest
tbs
episode.
The
binding
status
episode
21
about
the
stat
comp
operator
just
last
thursday,
like
four
five
days
ago.
I
guess-
and
so
here's
a
link
to
that.
In
case
you
missed
the
live
stream.
A
It's
published
on
the
youtube
playlist
another
good
episode
there,
quick
update
on
the
cncf
onboarding,
so
there's
still
some
issues
remaining
about
transferring
the
google
analytics
of
crosstalk.I
o
and
the
crosstalk
that
iowa
domain
transferred
over
to
the
ownership
by
the
cncf
for
the
linux
foundation
and
I'm
actually
meeting
with
artser.
Who
does
your
infrastructure
at
outbound
to
get
ownership
of
those
and
make
them.
A
Transitions
right
after
this
meeting
here,
so
that
should
be
progress
on
that
right
right
after
this
today,
kubecon
eu
started
this
morning,
as
you
mentioned,
so
the
project
pavilion
you
know,
crossplane
as
a
cncf
project,
has
the
opportunity
in
which
we
took
to
have
a
virtual
booth
in
the
project.
Cncf
project
pavilion,
so
that
is
live
and
here's
a
link
and
an
agenda
document
to
log
into
the
event
as
a
whole.
And
so
when
you
go
to
you
know
the
kubecon
virtual
event.
A
Here
you
can
go
to
the
expo
hall,
the
cncf
project
pavilion
and
that's,
where
you'll
see
all
the
cncf
projects
that
have
little
boost,
and
then
here's
our
cross
playing
on
right
right
in
the
middle,
which
is
pretty
rad,
where
you
can
go
in
there
and
interact
with
folks
stopping
by
the
booth
and
a
lot
of
helpful
links
on
the
right
there
and
whatnot.
So
we've
had
some
traffic
coming
in
and
out
of
there.
A
We
ran
our
office
hours
this
morning
with
a
zoom
meeting
and
we
walked
through,
like
the
project
overview
introduction,
how
things
work.
What
are
the
feature?
Main
features
all
that
sort
of
stuff
did
a
demo
as
well
and
that
I
got
the
recording
for
that
so
I'll
upload
that
to
the
cross
play
in
youtube-
probably
just
a
bit
here
so
that'll
be
available,
and
so
I
think,
like
we've
kind
of
you
know,
we
got
the
booth
set
up.
A
We
worked
through
a
lot
of
hiccups
over
the
past
couple
weeks,
like
getting
getting
the
platform
going
and
getting
everything
running.
We
could
do
a
post-mortem
about
like
the
value
of
this
and
everything,
but
you
know
and
what
what
what
to
change
and
what
to
correct
and
whatnot
in
a
separate
time.
But
does
anybody
have
any
anything
they
want
to?
You
know
discuss
about
like
what.
B
A
Planning,
what
are
some
of
the
goals
for
youtube
con
this
week
or
what
are
some
things
you
don't
want
to
miss,
or
you
know
anything
that
you
want
to
share
amongst
the
group
since
creepcon
just
started
and
there's
lots
of
opportunities
to
take
advantage
of
things
for
the
next
four
days
now.
B
Yeah,
so
basically
getting
people
like
into
slack
so
the
folks
who
were
at
the
office
hours
earlier
today,
you
know
have
been
you
know
in
in
cross
playing
slack
and
gave
me
engagement
there.
So
if
you
see
people
popping
up,
definitely
you
know
be
immediately
responsive
and
super
welcoming,
like
we
usually
are,
but
just
a
heads
up
to
kind
of
monitor.
You
know
slack
even
more
than
you
might.
A
B
B
I'm
just
kind
of
you
know
mentioning
you
know
additional
talks
there,
I'm
pretty
sure
most
of
us
have
already
in
the
the
slides
but
there's
a
way
to
kind
of
drop,
a
mention
for
a
cross-playing,
cross-plane,
booth
or
whatnot.
C
Yeah
coupon's
kind
of
an
interesting
one
to
me
these
days,
because
even
when
they're
in
person,
they
record
all
their
talks
so
well
that
I
don't
really
feel
any
sense
of
urgency
to
go
and
see
them
sort
of
live.
I
usually
just
watch
them
on
youtube
at
my
own
leisure
afterwards,
when
I'm
when
I'm
interested
somewhat,
but
that's
I
I
honestly
have
been
busy
enough
that
I
don't
even
really
know
what
talks
are
happening
that
are
interesting
and
I'm
to
go,
find
that
out
after
I
have
to
go
and
watch
them.
C
So
I
I'm
keen
to
help
out
with
the
booth,
but
I'm
also
conscious.
I,
I
honestly
don't
want
to
be
doing
it
at
4am
in
the
morning.
I
know
you're
doing
it
already
jared
but
came
to
help
out
sort
of
within
reasonable
office
hours.
C
I
won
what
what
time
pacific
does.
Does
the
booth
open?
Was
it
3
30
or
is
it
earlier
than
that
yeah.
A
C
Well,
one
thing
we
could
maybe
think
about
and
depending
on
how
my
my
day's
good
meeting
wise
is
3
30
is
not
that
far
after,
when
I
usually
go
to
bed,
I
usually
go
to
bed
anywhere
between
2
and
3
30,
so
I
could
stay
up
late
one
day
and
open
the
booth
but
you're
sleeping
in
the
morning.
I
just
have
to
make
sure
I
don't
have
to
be
up
to
go
and
go
to
a
meeting
at
9am
or
something.
A
Yeah
I
I
appreciate
that
nick,
but
you
know
something
I've
seen
so
far.
Is
that
the
the
demand
and
the
load
in
the
booth
like
there
are
people
coming
through,
but
it's
it's,
the
design
of
it
isn't
really
like
you're,
not
really
able
to
interact
with
every
single
person
that
comes
in
there
they're
kind
of
like
coming
through
looking
at
the
links
and,
like
you
know,
there's
no
immediate,
like
connection
that's
that's
made
and
that's
just
the
design,
the
booth
itself
and
the
ability,
the
capabilities
of
the
platform.
A
So
I
don't
think
the
value
of
it
is
really
so
high
enough
that
it's
like
worth
somebody
changing
their
schedule
to
like
be
awake,
but
they
shouldn't
be
awake.
I
don't
think
it's
honestly
worth
that
the
platform's,
not
that
good
like
we
want
to
like,
like
we
have
like
things
there
and
I'll
be
you
know
up
during
those
times
anyways,
because
I
have
to.
A
I'm
moderating
sessions
and
I
have
to
be
there
at
live
events
anyway,
so
I
wouldn't
change
anyone's
sleeping
hours,
because
the
booth
doesn't
really
justify
that.
Honestly,
the
value
of
it.
B
Thanks-
and
we
are,
you
know
like
tweeting
out
the.
B
Like
before
they're
happening
and
like
the
office
hours,
you
know
that
that
went
out
on
twitter.
So
if
you
want
to
like
retweet
somebody
to
reach
out
to
me
on
linkedin
this
morning,
basically
saying
like
hey,
I
saw
you
as
a
speaker.
You
know
I
would
love
to
connect,
and
so
we
did
that
and
kind
of
got
them
set
up
with.
You
know
crossplaying
slack,
and
that
kind
of
thing.
So
I
would,
I
would
suggest
you
just
use
your
networks
and,
like
you
know,
either
repost.
B
I
put
a
blog,
a
post
out
on
linkedin
to
post
out
on
twitter
that
links
the
v0.12,
which
is
the
second
link
in
that
thing
here
and
if
you,
you
know,
even
just
want
to
repost
that
or
reshare
it.
That
would
probably
be
an
easy
way
to
get
more
eyeballs
on
it.
And
then
I
can
drive
traffic
to
the
booth
so
yeah
that
second
one
there.
But.
B
Linkedin
or
my
my
twitter,
I
just
put
it
out
this
morning
and
it
has
a
little
bit
of
a
blurb
about
you,
know,
cubecon
and
then
it
links
to
that
doc.
It
says
all
the
sessions
here
at
the
bottom
so
definitely
like
check
out
all
these
sessions,
and
it
also
kind
of
highlight
composition
in
that,
and
this
also
includes
the
kelsey
hightower
demo.
So
this
was
kind
of
designed
as
like.
The
sharing
link
for
kubecon
is
like
equivalent
of
a
you
know,
take
away
pamphlet
or
whatever
nice.
A
A
No,
no,
no
more
cool
cool
cool
yep,
oh
yeah,
and
that's
so.
We
also
have,
as
mentioned
here.
We
have
a
slack
channel
for
talking
about
booth,
staffing
and
stuff,
like
that.
If
you
have
any
questions
about
the
booth
or
you
know
want
somebody
to
hop
in
with
you
for
a
conversation
or
something
like
that
feel
free
to
pay
people
on
that
in
that
channel
to
keep
conversation
going,
you
know
about
the
booth
but
outside
of
the
booth
itself
and
then
yeah
keep
driving
people
to
slack
itself.
A
I
think
that's
where
the
longer
term
relationship
is
gonna.
Live,
it's
not
going
to
live
in
this.
You
know
transient
temporary
virtual
donkey
booth
for
like
any
longer
than
three
or
four
days,
so
you
know
get
people
into
slack,
so
we
can
have
a
longer
term
communication
and
relationship
in
the
community.
There.
A
All
right,
yep
and
then
good
luck
for
everybody's
sessions.
Everyone's
talks.
It
should
be
fun
awesome
all
right.
That's
all
the
items
we
had
on
the
agenda
here.
Did
anybody
else
have
any
agenda
items
that
were
not
included.