►
From YouTube: 2020-02-04 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
A
But
things
look
stable
from
our
initial
testing
that
we
could
just
go
ahead
and
run
the
release
on
Monday
February
17th.
So
we've
got
this
week
and
next
week
to
finish
up
our
planned
work
items
for
0.8
and
let's
go
ahead
and
take
a
look
at
the
roadmap
which
I
believe
fill
updated
quite
recently,
Thank
You
Phil.
B
A
So,
let's
see
so
template
stacks,
we'll
talk
more
in
details,
do
some
of
those
in
some
of
the
PRS
that
are
mentioned
later
on
in
the
documents
and
and
then
we
also
have
some
of
the
easy
stacks.
The
minimal
stacks,
if
you
will,
those
are
coming
together
nicely
with
the
GCP
stack
and
azure
an
idea
of
us
all
functional.
They
are.
A
Yet
that
will
have
to
that
will
happen
after
the
template
stack
based
functionality,
it
wafak
and
Susskind
and
Marcus
are
all
working
on
now,
so
that
will
could
probably
come
in
next
week
or
next
sprint
post
aware,
stack
manager
was
merged
into
master.
Yesterday,
bless
Hassan's
heart
for
being
as
patient
as
he
was
to
get
that
in
semester.
That
was
a
great
example
of
a
review
system
where
you
know
it
drags
on
for
too
long
through
the
holidays
and
then
kind
of
lost
them
and
some
from
getting
the
eyes
on
it.
A
They
didn't
need
it
so
I,
you
know,
take
responsibility
for
that
wimped
for
not
getting
to
look
at
it
until
recently,
but
then
we
got
some
momentum
up
on
it,
and
I
saw
and
persevered
through
multiple
merge
conflicts
and
did
an
excellent
job
at
getting
that
host,
aware,
stack
manager
up
to
quality
and
merged
into
master
and
ready
to
be
included
in
the
0
to
8
release
so
great
job
asan.
On
that,
then
we're
working
on
multiple
designs
is
well.
A
A
You
know
without
having
to
write
me,
define
any
types
or
anything
and
go
nick
has
been
working
hard
on
that
and
being
able
to
for
claims
a
particular
claim
to
be
satisfied
by
multiple
resources,
such
as
like
a
database
and
a
firewall
rule
or
whatever
the
composition
of
claims
may
be.
Nick's
been
working
on
that
and
then
finally,
we're
also
going
to
bump
up
a
few
more
types
to
beta
in
this
release,
so
storage
in
buckets
and
networking
resources.
Adana.
Are
you
working
on
that
or
is
morphic
working
on
that.
B
A
C
A
Cool
all
right,
Nick,
we'll
continue
to
persevere
on
that
as
well
then,
and
the
last
one
who
lists
here
is
something
I
am
very
thrilled
with.
Personally
is
that
Nick
spent
some
time
doing
doing
our
logging
and,
if
anything,
the
right
way,
I
think
we've
had
a
long-standing
problem
where
something
goes
wrong
with
the
system.
A
So
it
should
be
in
the
0.8
release,
a
much
better
troubleshooting,
an
observer
abilities
story
and
without
compromising
architecture
purity
as
well.
So
thank
you
Nick
for
doing
that.
The
kubernetes
way
all
right.
So
that's
that's
the
roadmap
reserved
a
date,
and
we
talked
about
the
timing.
The
plan
timing
for
when
we
want
to
do
a
mid
month
released
again
sticking
to
their
our
schedule
here,
release
every
every
month
in
the
middle
of
the
month,
so
we
can
move
ahead
on
to
the
community
topics
section.
A
So
the
cube
con
Amsterdam
schedule
and
CFP
proposals,
notices
went
out
last
week
or
so,
and
so
there
are
a
number
of
talks
from
the
crossplane
community
that
got
accepted
Phil.
You
got
one
accepted
for
speaking
with
Microsoft
right
about
I.
Am
the
open
application
model
in
crossplane
doke
super
excited
about
that
right
on
and
I
also
got
a
talk
accepted
for
speaking
about
the
open
application
model
with
Alibaba,
and
so
there's
a
little
bit
different
focuses
between
those
two.
A
A
And
yeah
there's
a
if
there's
easily
applicable
knowledge
from
that
release
process
to
bring
back
into
the
crossplane
community
in
our
release
process
there.
That
would
that
would
be
awesome,
but
I
know
that,
for
my
understanding
of
prowl
and
all
the
systems
there
that
it's
not
really
a
streamlined
minimal,
lift
so
to
speak.
Yeah.
B
A
Are
you
factoring
bash
sounds
fun,
hope
you
make
it
to
Amsterdam
alive.
After
all
that
awesome,
cool,
yeah,
so
yeah
a
lot
of
talks
got
accepted
there
I
don't
know
if
anyone
else
on
the
call
got
or
unaccepted.
But
that's
super
exciting
that
you
know
there
will
be
number
of
chances
to
to
get
on
stage
and
talk
about
what
we're
doing
and
meet
more
community
members.
And
so
that's
that's
awesome.
Great
work
and
Hasan
got.
A
Right,
yes,
I
did
get
that
talk
accepted.
That's
awesome,
great
job
Hasan,
all
right,
so
the
binding
status
episodes
Dan's,
amazing,
live
streaming
show
had
some
really
cool
episodes
recently
and
there's
some
cool
episodes
coming
up
as
well.
Dan.
Do
you
want
to
talk
about
some
of
the
recent
TPS
stuff
yeah.
B
A
B
You
pronounce
that
that's
yeah,
that's
what
the
readme
says,
but
I
usually
just
call
it
keys
up
or
k3s
up,
but
I'm.
Just
trying
to
you
know,
adhere
to
the
community
standards
there,
but
yeah,
so
you
can
now
install
crossplane
with
that
tool
as
well.
So
if
you
bootstrap
a
k3s
cluster,
you
can
just
install
crosswind
right
in
there
with
one
command
with
that
seoi.
So
we
showed
that
we
also
showed
doing
some
kind
of
like
lightweight
Federation,
by
scheduling
from
a
k3s
cluster
running
on
a
Google
VM
to
Raspberry
Pi
in
my
apartment.
B
That
was
also
running
KPS
cluster,
so
that
was
pretty
cool.
You
can
check
that
out
and
there's
also
a
guide
for
reproducing
that
on
your
own,
and
then
this
is
actually
the
first
time
we
brought
it
up
and
we'll
have
some
announcements
this
week
about
it,
but
next
week,
on
Thursday
back
to
our
regular
time
at
9
a.m.
Pacific,
we'll
be
doing
a
show
with
crossplane
and
octet
au,
which
is
basically
an
open-source
project
that
allows
you
to
do
local
development
and
kind
of
have
like
a
high
reload
experience
with
your
apps
and
kubernetes.
B
A
On
man,
that's
super
exciting,
I
love
these,
like
collaboration,
episodes
that
you're
getting
lined
up
to,
like
you,
know,
use
crossplane
and
integrate
with
other
open-source
projects,
and
you
know
get
some
of
that.
I
hate
that
we
hate
using
the
word,
but
I'm
gonna
use
its
energy.
So
that's
great
work.
Man,
that's
super
exciting!
Is
that
octet?
Oh,
that
sounds
like
sort
of
like
a
project
that
I
believe
came
out
at
Google.
It
was
for
doing
like
local
development
in
kubernetes
clusters
or
like
abstracting
away
the
where
your
kinase
cluster
is
so
you
can.
A
B
I
think
it's
scaffold,
I
haven't
actually
used
it
and
I
haven't
used
our
teto
either.
So
it
would
be
a
lot
of
learning,
but
it
seems
pretty
cool
and
they
also
have
a
platform
where
you
can
basically
get
a
namespace
to
do
local
development
and
connect
to
it
from
your
local
machine
and
that
sort
of
thing.
So
you
can
imagine
some
pretty
cool
use
cases
where,
let's
say
you're
developing
like
a
web
app
and
you
need
my
sequel
database
just
for
testing
or
something
like
that.
A
Right
on
grid,
oh
that's,
exciting
that
you'll
get
to
dive
into
that
and
I'm
highly
confident
that
the
quality
of
your
investigation
and
what
you
come
up
with
will
be
exciting.
So
I
will
be
tuned
in
next
Thursday
at
9
a.m.
Pacific
to
watch,
watch
them
cross
plane
in
octet,
oh
action,
so
you
all
right
so
I
had
just
dropped
a
link
in
here
they
there's
a
proposal
out
for
to
the
Oh
a
to
OEM.
A
The
open
application
model
that
is
a
standardized
way
to
define
applications
within
the
code
is
that
ecosystem
that
is
being
worked
on
by
a
number
of
companies
Nick
cope
is,
is
driving
a
proposal
to
alter
the
spec
for
our
open
application
model
to
make
it
a
little
bit
more
kubernetes
friendly,
you
know,
have
some
more
assumptions
you
can
make
about.
You
know
presence
of
incorporating
this
API
server
in
the
kubernetes
api
and
then
how
cross
play
engine
it
in
as
a
runtime
and
integrating
with
the
open
application
model.
A
So
Nick's
been
doing
a
great
job,
driving
that
and
talking
to
a
lot
of
the
folks
at
Microsoft
about
them
and
there's
a
link
to
that
discussion
in
the
agenda
here.
So
you
can
take
a
look
at
that
as
you
wish,
and
also
weigh
in
some
comments
there
as
well
Tim.
This
is
your
item
about
AWS
service
accounts,
yep.
B
So
we
had
a
recent
community
issue
open
requesting
the
ability
to,
instead
of
basically
providing
your
credentials
in
a
secret
which
we
currently
do
for
all
our
providers
for
our
different
infrastructure,
specs,
basically
being
able
to
fall
back
on
a
service
account
that
connection
I
am
role
in
AWS.
So,
if
you're
running
on
eks,
basically
it
will
configure
your
nodes
in
your
cluster
to
have
connection
information
via
I
am
role.
B
So
you
can
authenticate
to
the
API
that
way,
which
you
know
would
allow
you
to
have
kind
of
like
more
fine-grained
control
and
also
rotate
credentials,
and
that
sort
of
thing
so
there's
a
lot
of
people
to
use.
Eks
use
this
kind
of
authentication
basically
exclusively.
So
we
definitely
want
to
enable
that
from
the
organizational
perspective
so
I'm
working
on
that
and
it
should
be
in
40.8
hoping
it
does-
require
a
little
bit
of
testing
in
terms
of
setting
up
clusters
and
making
sure
it
works
for
different
use
cases.
B
But
it
should
be
pretty
cool
functionality,
but
will
need
some
documentation
around
it,
because
it
obviously
affects
the
way
that
you
actually
deploy
crossplane
itself,
because
you're
the
pods
have
to
be
able
to
access
environment
variables
on
the
nodes.
Basically,
so
you
have
to
give
them
read
access,
but
we'll
probably
just
results
using
documentation
to
explain
how
to
do
that
for
now,
rather
than
you
know,
adding
some
sort
of
flag
in
the
deployment
just
for
the
time
being.
Yeah.
A
That's
fair
and
I
also
really
like
how
this
is
a
request
from
you
know,
from
the
community
for
a
user
request
for
this
functionality.
So
I
definitely
like
that.
You
know
we're
incorporating.
You
know
that
feedback
in
listening
to
new
scenarios,
that
would
you
know,
expand
the
usefulness
and
value
of
crossplane
and
responding
to
it
by
doing
the
integration
of
the
work.
So
that's
awesome.
A
A
Look
at
that,
but
I
knew
that
there
so
there
the
work,
that's
ongoing
and
template
stacks
right
now
is
across
three
different
developers:
Markus
Susskind
and
wafak,
and
so
I
there's
a
lot
of
a
lot
of
velocity
going
on
there
right
now,
so
I
wanted
to
just
bring
up
some
of
the
pro
requests
that
may
be
ready
to
start
getting
some
eyes
on
them.
So
Marcus
you
added
both
of
these
here
yeah
yeah,
that's
about
17!.
B
D
Pr
that
introduces
the
stack
definition
type
in
a
stack
definition
controller.
So,
with
this
template
stacks
work
in
a
previous
sort
of
preview
functionality
that
was
added
to
crossplane.
There
was
the
introduction
of
a
stack
configuration
type
which
introduced
the
behaviors
that
allow
you
to
say
for
a
given
CRD,
execute
this,
this
helm
chart
or
this
customized
URL,
and
so
in
this
current
PR
and
the
this
current
round
of
PRS
were
extending
that
to
two
helm
and
customize
and
the
way
that
the
stack
controllers
work
we're
finding
that
we're
going
to
have
a
better
time.
D
Moving
away
from
this
stack
configuration.
This
then
stack
configuration
type
to
something,
that's
more
like
the
full
stack
type
and
so
we're
we've
got
this
intermediary
stack
definition,
type
that
we're
using
there's
a
lot
more
things
that
we
expect
will
need
to
change
in
the
stack
type
later
on
and
there's
even
maybe
the
possibility
that
stack
and
stack
installs
could
merge,
and
so
we
don't
want
to
introduce
too
many
changes
to
staff
right
now.
So
that's
where
this
new
stack
definition
type
comes
from
the
stack
definition
controller
will
produce
the
stack
resource
and
yeah.
D
A
You
see
Bri
bases
in
your
future,
I
see
a
lot
yeah
nice
that
sounds
fun
cool.
Yes,
I
took
a
pass
through
this.
This
first
pull
request
to
define
the
type
and
controller
over
the
weekend,
and
so
I
think
Susskind
replied
to
my
comments
yesterday.
So
I
could
take
another
pass
to
hopefully
converge
on
merging
this
today
to
unblock
some
of
the
other
work,
no
problem
with
that
and
in
and
then
yeah
ping
me,
and
let
me
know
like
when
this
is
ready.
D
A
C
Yeah
there
was
there
was
one
concern
brought
up
about
our
standard
for
removing
old
designs
versus
marking
them
as
defunct.
I.
Think
Marcus
brought
up
and
I
just
wanted
to
address
that,
but
also
just
raise
a
hand
for
this
PR.
So
I
didn't
I
didn't
know
if
what
what
the
proper
process
was
for
removing
old
designs,
if
they
haven't
really
been
implemented
anywhere
fully.
A
Yeah
and
I'm
not
sure
exactly
the
details,
but
in
general
for
me
the
most
important
part
is
like
what
is
the
contracts
like
an
you
know.
Types
are
the
API
that
we
surface
like.
If
there
is
some
API,
the
resurfaced
it's
you
know
already
beta
or
something
like
that,
then
removing
a
design
or
removing
functionality
from
it
is
much
more
of
a
conversation
than
if
it's
not
something.
A
C
A
C
A
A
B
Mention
on
some
of
these
PRS
about
changing
the
UI
metadata
and
I've
mentioned
this
to
Steven
before,
but
I'd
like
to
get
to
a
place
where
we
can
do
at
least
some
generation,
especially
in
regards
to,
or
even
if,
not
generation.
Some
of
this
is
like
updating
the
version
number
of
the
stack
in
the
UI
metadata,
which
isn't
part
of
our
release
process
like
when
we
do
our
prep
on
the
release
branch.
B
We
haven't
been
touching
the
UI
metadata
so
long
term,
I'd
like
to
do
some
sort
of
generation
around
this
UI
metadata
and
short
term.
We
should
probably
add
a
step
in
the
prep
process
of
the
manifest
and
that
sort
of
thing
on
the
release
branch
for
each
of
them.
That
updates
the
UI
metadata
as
well
like.
B
A
B
A
A
Yeah,
so
yeah
I
think
it's
not
explicitly
part
of
the
release
process,
but
only
as
Steve
is
mentioning
when
the
schema
itself
changes.
How
ya
believe
it's
an
independent
version
they
can,
and
this
better
there's
probably
better
ways
to
have
a
process
around
that
dan
I
totally
understand
that
that
part
of
it
but
I
get
it
I
think
it
is
important
to
note
that
it's
not
right
now,
part
of
the
released
version
and
process
up
the
stack
itself.
Gotcha.
B
That's
really
helpful
Steven
one
thing
I
want
to
ask.
So
if,
like
one
of
the
you
know,
API
changes,
let's
say
the
DB
subnet
group
goes
to
view
on
beta
one
or
something
like
that
and
some
of
the
fields
change.
If
we
needed
to
change
the
UI
scheme
as
well,
would
we
just
bump
to
0.6
on
that?
Am
I
understanding
that
correctly
yeah.
B
A
C
I
was
this
morning:
this
is
just
this
is
just
kind
of
related
to
a
change
that
move.
Offic
recently
did
to
update
from
crossplane
IO
to
cross
plane.
I
was
causing
a
break,
and
so
I
just
am
updating
some
other
names
to
align
with
how
stack
GCP
does
naming
I
think
the
issue
right
now
is
the
crossplane
CLI
tool.
When
you
run
crossplane
in
it,
it
automatically
adds
across
playing
io
prefixed
to
a
lot
of
these
places,
and
it
looks
like
after
the
fact
manually,
those
have
to
be
updated.
A
Yeah
yeah,
thank
you
doing
that
Steven
and
I
would
say
that
these
ones
here,
probably
do
these
ones
are
functional
changes
here,
because
it's
talking
about
like
the
the
image
repo
and
in
image
name.
So
these
ones
are
probably
I
mean
they
look,
I
think
they're
only
local
stuff
over
the
sample
yeah,
but
yeah
those
ones
have
functionality,
changes
these
ones.
Look
to
be
more.
You
know
vanity
or
consistency
wise.
So,
but
thank
you
for
finding
that
Steven
and
if
there
is
a
bug
in
well.
A
First
of
all,
the
stack
minimal
GCP
definitely
is
a
good
reminder
about,
like
automation
and
testing
in
verification
of
these
stacks
we're
building
because,
like
I
made,
it
changed
like
update
one
name
of
the
the
stack
in
one
place
and
that
wasn't
all
timed
in
wafak
found
another
one,
and
then
you
felt
like
a
third
one.
So
it's
a
clearly
there's,
not
the
right
verification
in
the
ends
and
make
sure
that
everything
is
fully
updated
or
verified.
A
C
A
Awesome
yeah
that
sound
that
sounds
good
then
yet
see
make
four.
Have
those
consistent
across
all
the
almost
access
that
sounds
great
cool
man,
you're
gonna
have
more
commits
in
the
cross
plane
repos
than
I
do
soon
and
Steven
keep
up
the
good
work
good
job,
oh
yeah,
and
then
I
am
going
on
a
note.
So
I'm
somewhat
slightly
related
note.
A
There's
a
quick
start
there
for
how
to
you
know
simply
here
we
go
QuickStart
stacks
to
use
the
tools
across
many
line
tools
to
initialize
a
project
and
get
a
building
and
publishing
and
validated
not
stuff.
So
I
was
gonna
point
somebody
at
this,
but
I
didn't
know
if
this
is
up-to-date,
so
I
was
gonna,
take
a
run
through
it
myself
to
see
if
it's
still
functional-
and
you
know
up-to-date,
if
it's
not
then
updated
before
I,
send
that
link
off
has.
D
B
I
talked
to
move
off
ik
this
morning
about
this,
and
he
said:
I
was
asking
if
he
had
used
it
to
bootstrap
his
different
minimal
stacks.
That
sort
of
thing
he
said
yes,
but
he
said,
there's
some
issues
with
after
you
actually
do
the
initial
setup,
I,
don't
think
all
parts
of
the
craftsman
CLI
are
working
correctly
and
there's
a
number
of
open
issues
on
there,
and
some
of
them
are
pretty
friendly
to
new
contributors
as
well.
A
Cool
if
there's
I,
if
I
find
issues
when
I
run
through
it,
I
will
I'll.
You
know,
update
these
issues
or
maybe
even
provide
fixes
as
well,
but
the
one
thing
that
I
think
has
been
tricky
about
migrating.
The
implementation
of
Crossman
see
life
from
scripts
batch
scripts.
To
go
binary
is
the
distribution
of
it.
It's
you
know
to
be
able
to
ship
and
publish
the
binary
as
opposed
to
right
now.
It's
you
know.
A
Just
a
couple
of
you
know
like
a
couple:
kilobytes
sighs,
you
know
bash
scripts
that
are
really
easy
to
download
and
it's
all
locally
by
just
copying
the
script
server.
So
when
you
have
a
binary
in
place
like
the
distribution
story,
becomes
more
challenging,
they'll
have
to
be
thought
through
yeah,
so
I
mean
some.
A
And
I
noticed
that
too.
Actually,
when
from
this
note,
when
I
was
walking
walking
through
installing
it
the
latest
last
night,
because
the
tray
screen
will
not
be
installed,
oh
shoot,
so
we
already
have
an
issue
in
text
right.
A
D
A
A
Cool
all
right,
all
right,
all
right,
so
that
was
the
last
we've
been
on
a
little
bit
of
a
tangent
there,
sorry
everybody
that
was
the
last
item
on
the
agenda
here.
So
I
will
open
the
floor
for
anybody
who
might
have
additional
agenda
items
that
did
not
make
it
to
the
agenda
doc,
and
if
there
are
none,
then
we
can
go
ahead
and.