►
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
Hello,
everybody
welcome
to
another
episode
of
cloud
native
live.
My
name
is
mario
lauria.
I
am
here
with
victor
farcik
and
this
is
a
really
really
special
episode
for
me.
It's
going
to
be
my
last
episode,
possibly,
and
definitely
I
don't-
I
don't
know
we'll
see
what
next
year
brings.
I'm
gonna
take
the
fall
and
soak
up
the
amazing
kubecon
that
we
have
coming
before
us,
cubecon,
north
america
and
cloudnativecon.
A
But
thank
you
so
much
for
taking
the
time
today
and
and
joining
us
victor
and
upbound,
especially
the
cross
plane
project,
are,
is
probably
one
of
my
favorite
projects
in
the
cloud
native
ecosystem
because
of
the
the
focus
on
shifting
left
the
developer,
experience
and
giving
more
autonomy
to
developers
to
provision
and
handle
infrastructure
components
that
they
need
and
depend
on
and
taking
more
off
of
sres.
So
I
can
talk
about
crossplaying
all
day,
but
that's
not.
A
What
we're
here
for
victor
is
here
as
a
freshly
minted
advocate
for
upbound
the
company
behind
crossplane,
and
if
you
don't
know
what
crossplane
is
the
the
the
one
sentence,
is
you
can
provision
infrastructure
with
kubernetes
gamma
and
that's
the
very
thin?
You
should
definitely
go
to
the
documentation.
Crosslink.Io
victor.
I
know
him
as
a
very,
very
huge
member
and
advocate
for
the
entire
cloud
native
community.
A
I
was
listening
to
him
the
other
day
while
exercising
for
his
devops
paradox,
podcast,
which
he
has
some
great
guests
on,
and
talks
about,
some
some
really
awesome
technical
and
more
high
level,
maybe
even
leadership,
components
as
well
in
the
industry.
I
victor
is
one
of
my
favorite
people,
I'm
so
glad
to
have
him
today
without
further
ado.
Here's
victor
farcik
to
to
introduce
and
bring
us
compositions
on
crossplane.
A
Okay,
that's
okay,
I'll
I'll
I'll
plan
to
interrupt
you
plenty
and
make
your
face
even
redder.
A
little
later
on
with
my
dumb
questions,
yeah
one
last
thing
too
audience:
please
leave
in
your
platform
of
choice,
leave
any
any
questions
and
comments
and
thoughts
on
what
victor's
talking
about
today
or
cross
playing
and
I'll
I'll.
Stop
him
and
try
to
have
him
answer
those
for
you.
So.
B
B
The
more
you
can
enter
the
more
you
interrupt
me,
the
better,
so
you
already
heard
the
introduction.
My
name
is
victor.
I
work
for
abound.
We
had
a
company
behind
plane
and
a
few
other
things,
but
today's
subject
is:
is
cross
plane.
So
if
you're
not
familiar
with
cross
plane,
the
explanation
that
mario
just
gave
is
essentially
correct.
It
is
a
way
to
manage
infrastructure
from
inside
kubernetes
and
you
might
be
asking
okay.
So
what
is
the
benefit
of
that?
B
Almost
everything
that
is
happening
right
now
today
in
an
industry
is
somehow
levitating
around
kubernetes
right,
and
that
means
that,
if
you're
managing
something
whatever
that
something
is
doesn't
matter,
whether
it's
applications
or
infrastructure
of
this,
and
that,
if
you
do
that
through
kubernetes,
then
you
get
basically
out
of
the
box.
Certain
features
or
certain
benefits
that
either
do
not
exist
or
are
hard
to
accomplish
outside,
like
you
have
automatic
reconciliation
and
drift
detection,
high
availability
you
have-
and
this
is
my
favorite
and
a
a
single
api-
to
manage
everything.
B
Basically
right,
usually
when
people
talk
about
kubernetes,
the
first
association
is
hey,
I
can
run
containers
and
my
pro
association
is.
I
have
an
api
that
I
can
use
to
do
whatever
I
need
to
do
right
and
on
top
of
all
the
features
that
everybody
knows
and
loves
in
kubernetes,
there
is
the
ecosystem
right
if
you
want-
and
I'm
really
not
talking
in
general,
even
though
that
flows
into
crossplane
hey.
If
you
would
like
to
manage
your
stuff
using
github's
principles.
B
Yes,
there
are
tools
and
they
happen
most
of
them
to
be
kubernetes
based.
If
you
want
monitoring
again
kubernetes,
if
you
want
service
mesh
again
kubernetes,
so
for
us,
it
was
very
important
that
the
tool
that
we
are
building,
which
is
essentially
and
mostly
focus
on
infrastructure
and
his
services.
It's
it's
hard
even
to
distinguish
what
is
a
service?
B
For
us,
it
is
very
important
the
the
idea
that
we
can
shift
to
left
the
workloads
or,
to
put
it,
in
other
words,
that
we
can
enable
almost
everybody
to
do
almost
everything
right,
and
there
are
many
depending
on
the
aspect
of
what
we
are
enabling.
There
are
many
different
projects
and
cross-plane
falls
into
that
category
when,
when
we
are
talking
about
infrastructure
so
and
in
general,
when
we
speak
about
those
things
usually
either
we
get
something
flexible.
B
B
We
want
to
enable
those
experts,
let's
say
to
create
opinions
for
the
rest
of
the
people
in
their
company
company,
and
we
do
that
with
what
we
call
composites.
So
in
a
way
you
can
use
crosstalk
directly
and
define
yaml
manifests,
and
I
will
show
you
that
in
a
few
seconds
that,
through
which
you
define
your
infrastructure,
a
cluster
networking
database,
whatever
you're
having
or
you,
can
create
a
composite
that
says
hey.
I
need
all
these.
All.
All
those
things
are
unavoidable.
B
A
Really,
yeah
really
really
quick.
So
what
what
you're
saying
is,
as
we
go
on
this
journey,
to
self-service,
more
intuitive
ux,
driven
sort
of
products
that
anybody
can
use
like
you
said,
and
I
think
about
it
as
like,
instead
of
everything
being
encapsulated
in
the
sre
team,
and
they
have
to
do
this
and
they're
your
dependency
they're,
your
blocker
right,
you
they
have
to
allow
you
to
do
things
or
do
things
for
you.
You
now
have
control
of
do
that.
What
you're
seeing
is
compositions,
extends
that
even
further,
and
actually
it
helps.
A
You
extract
away
that
complexity
and
more
of
a
maybe
a
templatized
version,
maybe
think
of
like
a
a
base,
common
helm
chart
or
something
like
that
right
for
these
compositions
and
things
that
you
want
to
provision
or
that,
maybe
all
your
django
services
need
a
database
of
a
certain
type
or
something
like
that
right.
B
Yeah
so
think
of
it,
like
think
of
it
as
sres,
creating
a
health
chart
and
everybody
in
the
company
having
freedom
to
fine-tune
that
help
chart
through
him,
values
right
and
but
that
team
does
not
necessarily
want
to
deal
with.
All
the
complexities
of
everything
defined
in
chart.
Chart
is
kind
of
somebody's
in
charge
of
creating
that
chart,
and
you
are
tweaking
you
have
the
level
of
freedom
that
you
need
through
the
through
the
hem
values
right,
except
that
we
are
not
talking
about
helm
charts.
But
the
idea
is
somehow
similar
that
somebody.
B
B
But
also
they
do
not
want
to
open
a
jira
ticket
every
time.
Every
single
detail
is
needed
so
that
you
do
it
for
them,
and
you
don't
you
probably
don't
want
to
do
it
yourself
either,
because
my
in
my
head
at
least
the
job
of
an
sre
or
whatever
the
title
is,
is
not
really
to
fulfill
the
requests
of
others,
but
to
create
tooling
that
enables
the
others
to
manage
everything
in
a
way
that
is
agreed
in
a
way
or
simplified
to
the
level
that
does
not
provides
freedom
without
complexity.
A
That
is
that's
the
clincher
right
there.
That
is
the
statement
of
the
year.
That
is
what
sre
team
should
be
about.
They
should
not
turn
into,
I
like
to
say,
glorified
support
teams,
maybe
more
so,
teams
that
are
blockers
and
dependencies
in
getting
things
done
in
shipping.
We
should
instead
build
the
tooling
to
automate
and
provide
more
power,
more
flexibility,
more
metrics
to
the
people
that
actually
own
the
services,
I.e
the
coders,
the
service
owners,
the
developers,
so
so
really
quick.
A
We
have,
I
think,
ahmet
who
said
hi
victor
following
your
youtube
closely.
Great
content
got
your
post
on
udemy
as
well,
but
it's
a
bit
outdated.
Now
I
think
that's
a
call
out
on
you
victor
you
gotta,
keep
those
updated
come
on.
Give
us
the
latest.
B
A
A
A
To
approach
generally
having
a
dev
staging
production
workflows
in
the
same
cluster,
I'm
gonna,
let's
put
that
on
the
table
for
now
victor,
I
want
you
to
get
into
compositions
and
we
can
maybe
circle
back
to
what
these
kind
of
disparate
environments
and
how
you
know
these
changes
that
you're
trying
to
test
can
then
bounce
through
and
graduate
to
production,
so
I'll,
shut
up.
B
Sounds
great,
shall
we
switch
it
to
a
demo
and
see
it
in
action
instead
of
me
talking
talking
talking,
yeah,
oh
okay,
I
see
there's
the
screen
right.
So
let
me
first
show
you
how
I
would
use
crosstall
to
manage
infrastructure
without
compositions
right
directly
me
with
crossplane,
without
having
any
sre
or
any
cs
admin
or
any
infrastructure
present
in
between,
and
it
could
look
something
like
this.
For
example,
if
I
would
like
to
create
a
gk
cluster
with
crossplane,
I
would
create
it
as
a.
B
B
So
this
is
equivalent
to
how
you
would
do
things
with
other
tools,
except
that
this
is
jumble,
and
these
are
kubernetes
resources,
instead
of
being
whatever
else
you
might
be
used
to.
So
we
are
basically
assuming
that
kubern
that
you
or
the
potential
user
has
adopted.
Kubernetes
api
is
the
de
facto
standard
to
do
whatever
needs
to
be
done
or
to
be
more
precise,
to
define
the
state
of
whatever
is
needed
through
it.
So
I
have
that
definition,
and
this
is
intentionally
simple.
B
I
will
show
you
more
complex
definitions
in
a
second
in
a
real
world
situation,
you
would
not
have
only
those
two.
You
would
have
a
bunch
of
other
things,
because
it
looks
easy
when
you
create,
let's
say
a
kubernetes
cluster
in
using
causal
click,
click
click.
But
realistically
there
are
many
other
things
that
we
need
there,
but
there's
nothing
simple
right.
B
So
if
I
would
want
to
create
that,
I
would
do
something
like
this.
This
is
just
like
with
any
kubernetes
type
of
resource,
I'm
going
to
apply
it
file
name
is
going
to
be
gk,
yaml
and
and
off
you
go
now.
B
Nothing
here
just
happened
for
a
simple
reason,
because
before
I
started
before
I
came
to
this
session,
I
already
applied
this
resource
to
speed
things
up
so
instead
of
you
waiting
for,
I
think
it
takes
like
six
seven
minutes
until
cluster
is
created
in
gk
gke,
but
what
I
can
do
is
basically
now,
since
those
are
kubernetes
resources
and
not
some
random
stuff,
I
can
do
other
kubernetes
stuff
that
I
normally
do
like
hey
get
managed,
which
is
a
shortcut
to
get
all
the
many
resources
managed
by
crossplane,
and
here
you
can
see
yes,
just
like
querying
pods
or
deployment
or
anything
else.
B
Yes,
I
have
gt
cluster
definition
being
applied
in
my
kubernetes
cluster.
Let's
say
that
we're
talking
about
two
classes
now
control
plane
cluster,
where
I'm
running
crossplane
in
a
cluster
that
I
just
created
and
I
have
a
node
pool,
I
can
see
the
statuses
they're,
all
ready,
they're,
all
synced,
they're,
all
running
and
so
on
and
so
forth.
B
Right
now,
the
the
thing
with
that
one
is
that
those
definitions
can
tend
to
be
complex
right,
not
because
cross
plane
is
complex
or
it's
not
complex,
but
simply
because
there's
a
lot
of
things
that
we
need
to
think
about
when
creating
infrastructure,
and
if
we
want
to
shift
left
to
enable
everybody
else
in
an
organization
to
self-manage.
B
We
need
to
reduce
that
complexity,
but
we
need
to
do
it
in
a
way
that
we
cannot
just
buy
something
off
the
shelf,
reduce
complexity,
because
that
would
not
take
into
account
all
the
special
things
that
everybody
has
in
a
company.
But
the
whole
idea
is
that
we
can
use
definitions
similar
like
what
I
showed
you,
this
jk
yaml
and
create
compositions
and
then
simplify
everything
else
for
everybody
and
that
simplification
could
look
like
this.
B
So
this
is
something
that
sorry
wrong
one.
This
is
something
that
developer
or
anybody
else.
Every
vast
majority
99
of
the
people
in
the
company
would
consume,
and
this
would
be
something
called
in
this
case
composite
kubernetes
cluster.
So
this
is
a
custom
resource
that
I
is
sre
defined
for
everybody
who
wants
to
use
who
wants
to
manage
kubernetes
clusters
in
my
company
in
my
organization,
and
there
are
a
couple
of
interesting
things
here.
To
begin
with,
I
can
specify
the
name
of
the
composition.
B
So
in
this
case
the
name
is
cluster
google,
but
I
also
created
the
implementation
of
the
composition
for
clustering,
aws,
clustering,
azure
alibaba,
wherever
right,
so
a
potential
consumer.
The
end
user
of
this
can
just
go
and
pick
wherever
they
want
cluster
to
be
created
without
really
knowing
the
details
about
that
specific
platform.
B
And
then
there
are
a
couple
of
parameters
that
my
end
users
can
use.
There
is
a
size
of
the
nodes
version
and
the
minimum
number
of
nodes
now
for
the
size
of
the
nodes.
The
values
you
can
see
in
a
comment
can
be
small,
medium
large.
So
this
is
all
custom
right.
This
none
of
those
things
come
out
of
the
box.
B
This
is
what
I
created
for
everybody
else
in
my
organization,
and
the
sizes
are
small,
medium
large,
meaning
that
if
you
use
aws
or
any
other
provider,
you
know
that
those
sizes
do
not
exist,
but
composition.
Cross
plane
itself
will
make
sure
that
small
is
converted
to
something
t2.
Something
and
medium
will
be
converted
to
something
else,
but
we
I'm
imagining
a
situation
where
vast
majority
of
people
do
not
want
to
care
about
hey.
Is
it
t2
t3,
which
type
of
of
zillion
of
nodes
in
aws
or
azure
or
google
we're
talking
about?
B
No,
it's
simple.
Do
you
want
small?
They
want
medium.
Do
we
want
large,
which
version
of
kubernetes
do
we
want?
And
what
is
the
minimum
number
of
nodes
I
set
intentionally
minimum
because
I
assume
that
the
cluster
is
expandable
and
that
it
will
start
with
certain
number
and
potentially
grow
over
time
with
cluster
autoscaler,
so
not
the
specific
number
of
nodes,
but
minimum
now
those
two
are
commented,
meaning
that
they
have
default
values
if
you
as
a
as
a
developer
or
qa
or
tester
or
whatever
you
are.
B
B
And
finally,
once
the
cluster
is
created,
I
want
the
I
want
the
kubernetes
secret,
that
is
to
contain
the
credentials
on
how
I
can
connect
to
that
cluster
and
I'm
specifying
that
it
should
be
that
it
should
be
created
in
an
a
space
called
tma
and
that
the
name
of
the
secret
will
be
cluster
right.
B
So
this
is
basically
that
end
result,
interface
that
I
created
and
everybody
else
in
my
company
can
consume
to
self-manage
their
own
clusters
and
limited
them
limiting
themselves
to
the
things
that
matter
while
leaving
the
complexity
somewhere
else
somewhere
outside
of
of
all
that.
B
B
And
here
we
go,
and
you
can
see
the
cluster
from
before
that
I
created
earlier,
and
now
you
have
a
cluster,
the
new
one.
That
is
right
now,
it's
synchronized,
meaning
that
crossplane
got
the
information
and
it
is
currently
working
on
make
provisioning
it
and
it
is
not
yet
ready
and
once
the
cluster
is
ready,
then
the
node
pool
will
be
created
and
all
all
the
stuff
that
we
need
around
the
infrastructure.
For
this
specific
case
right.
B
So
I
will
leave
that
running
in
the
background,
because
that
will
take
a
few
minutes
and
now
switch
to
switch
to
the
point
of
view
or
the.
How
that
same
set
of
features
would
be
seen
from
an
sre
perspective,
and
the
sre
would
need
two
things
first
is
is
the
definition
which
is
this
one
right.
B
This
is
this
is
a
xrd
or
composite
resource
definition
that
defines
the
new
custom
resourcing
kubernetes,
the
one
that
I
showed
initially
right,
the
one
that
allows
everybody
to
create
and
manage
their
clusters,
and
basically,
what
I'm
doing
here
is
that
I'm
saying
hey,
there
will
be
a
custom
resource
definition
that
will
be
called
composite.
B
Kubernetes
clusters,
cluster
or
claim
kubernetes
clusters
so,
depending
on
permissions,
I
want
to
give
to
people
that
can
manage
the
infrastructure
on
a
with
cluster
byte
permissions,
which
is
most
of
the
time,
not
a
good
idea
or
create
claims
just
like
when
you're
claiming
volumes
and
then
you're
limited
within
your
nay
space,
and
then,
whichever
other
restriction,
somebody
post
now.
B
The
important
part
here
is
the
open
api
schema
right.
So
I'm
defining
a
complete
schema
for
a
completely
new
kubernetes
resource
that
will
have
some
parameters
and
those
parameters
will
be
properties
with
version
node
size
and
min
node
count.
So
those
are
the
same
properties
that
you
saw
earlier
when
I
was
consuming
the
end
result
of
all
that,
so
I
defined
the
zestaria
defined
xrd
or
composite
resource
definition
that
defines
the
interface
that
everybody
else
would
consume
and
then
what
they
did
is
I
created
implementations
of
that
xld
or
composites.
B
I
created
one
for
azure,
so
if
somebody
would
want
to
create
a
cluster
in
azure
using
that
simple
definition,
this
is
what
would
happen
right.
I
would
create
an
aks
cluster.
It
would
have
certain
parameters
that
defined
and
hard
coded,
because
those-
let's
imagine
that
nobody
in
my
company
is
changing
the
region.
We
are
all
running
in
one
region.
So
why
would
you
bother
right?
This
is
the
dns
name
prefix.
This
is
the
default
version,
the
default
number
of
nodes,
the
default
size
of
nodes,
and
then
we
have
patches
now.
B
This
is
what
what
gets
converted
from
that
interface
that
I
was
consuming
at
the
very
beginning.
This
is
how
we
are
overwriting
those
values
and-
and
that's
about
it
now
azure
is
the
simplest
one,
I'm
going
intentionally
from
the
simplest
to
the
more
complex
and
then
we
have
recipe
which
is
slightly
more
complicated,
which
defines
two
resources
in
that
composition
says:
hey
okay.
B
I
like,
whenever
we
create
a
clustering
in
aws,
we
need
the
route
table,
we
need
the
gateway,
we
need
a
subnet
and
another
subnet
and
more
subnets
and
security
groups
and
vpcs,
and
that
some
role
attachments
and
more
attachments
and
more
attachments
and
then
what
else
do
we
have
and
the
node
group
and
finally
an
eks
cluster
right.
So
this
is
underneath.
A
This
is
this
is
what
he's
talking
about
like
he's,
abstracting
we're
extracting
the
wake
of
the
complexity
by
making
some
safe
general
assumptions
about
the
environment,
we
find
ourselves
in
how
we
use
the
infrastructure
as
a
service
platforms,
aws
gke
right
and
we're
doing
that
for
you,
so
that
as
a
developer,
you
can
just
say
I
just
need
a
cluster,
and
I
needed
to
you
know-
be
able
to
support
my
workload
with
this,
maybe
cpu
and
memory
or
whatever,
whatever
it
might
be
right
some
basic
pieces.
There
are
articles.
A
I
have
read
on
this
many
many
times
on
the
leveraging
of
crds
and
creating
a
sort
of
like
homegrown
crossplane.
If
you
will
there's
a
great
one
from
pinterest
engineering
on
building
a
kubernetes
platform,
you
can
look
at
even
borg.
A
It's
the
actual
configuration
is
incredibly
simple
for
the
end
user
in
just
getting
a
workload
onto
this
platform
and
that's
what
we're
that's
what
victor's,
showing
here
so
very
nice.
Thank
you,
sir.
I
know
there
is
a
few
mentions
here
in
chat
about
fargate.
It
looks
like
dan
magnum
also
from
outbound
a
a
co-worker
of
victors.
A
great
great
person,
I
think,
we've
had
him
on
before
is
handling
answering
some
of
those
questions
and
it
looks
like
fargate
is
supported
and
cross-planed.
So
that's
awesome
to
see
yeah.
B
B
B
I
believe,
because
either
zeo
marios
and
sre
would
need
to
do
all
that
work
to
create
that
cluster
for
dot
dot
for
others,
because
others
are
unlikely
to
learn
all
this,
and
even
if
they
learn
that
they
will
want
to
spend
the
time
to
that
or
others
would
need
to
create
clusters
through
you,
some
web
ui,
where
I
don't
want
to
enter
by
that
is
bad
right
anyways.
So
where
was
I?
Let
me
see?
B
Yes,
yes,
yes,
so,
and
finally,
once
we
create
that
completely
new
resource
definition,
we
can
use
something
like
cube
cattle,
explain
composite
what
is
it
kubernetes
cobain
methods,
cluster
that
is
recursive
and
if
anybody
doesn't
know
which
are
the
parameters
allowed,
you
can
output.
This
is
just
another
custom
resource
definition
and
see
hey.
Yes,.
A
B
The
where
is
it
the
specification
is
that
we
need
parameters
with
those
three
parameters.
This
is
what
I
can
use
and
off
I
go
right.
It
does
require
some
minimal,
kubernetes
understanding,
but
really
really
minimum
right
now.
Another
thing
that
we
get
through
that
custom
resource
definition
is
something
like
get
composite.
Kubernetes
clusters,
eye
clusters,
and
we
can
see
so
this
is
now
the
output.
This
is
a
completely
new
resource
that
never
existed
before
that
was
created
by
that
sre
and
I,
as
a
developer
or
whatever
my
role
is
I
can.
B
I
can
actually
skip
even
looking
at
vpcs
and
this,
and
that
I
can
just
go
straight
into
that
resource
definition,
and
I
get
a
custom
output
that
I
defined,
which
in
this
case,
and
it
can
be
anything
hey
control
plane.
Is
it
running?
Yes,
not
pull
running?
Yes?
Is
it
all
ready?
Yes,
what
is
the
name
of
the
composition,
cluster?
Google
off
you
go
right,
it
can
get
as
simple
or
as
complicated,
depending
on
the
design
and
agreement
between
sres
and
everybody
else
now.
B
Another
thing
that
is
happening
over
here
is
that
we
can
update
our
cluster.
So,
for
example,
I
can
do
gk.yaml,
I
can
say:
let
me
see
what
should
I
do
here.
B
Minimum
number
of
nodes
should
be,
let's
say
two
right:
the
in
the
same
way
as
you
would
deal
with
any
other
kubernetes
type
of
resource.
You
update
the
manifest
and
you
do
cube
cattle
apply,
dark
starch
file,
name
directly
or
even
better,
and
for
simplicity,
I'm
for
simplicity,
I'm
executing
cube
cattle
apply.
I
don't
think
that
anybody
should
do
even
that
in
ideal
combination.
B
You
should
have
that
gk
yaml
or
your
definition,
and
you
should
be
modifying
it
and
you
should
be
pushing
it
to
get
and
from
there
on
tools
like
argo,
cd
or
flux
or
whichever
you're
using
for
synchronization
between
git
and
cluster,
would
kick
in,
and
that
would
mean
that
you
as
the
end
user,
you
would
not
even
need
to
have
cube
cattle
even
know
about
kubernetes.
All
you
have
to
know
is:
this
is
the
interface.
This
is
the
ammo.
B
I
push
it
to
get
argo
cd
flux,
whatever
synchronizes
with
my
control,
plane,
cluster,
and
then
things
just
appear.
But
in
this
case
I
didn't
do
that.
I
was
too
lazy,
I
think,
for
to
set
it
up
for
this
demo,
so
I
just
did
cube
cattle
apply
and
if
I
go,
let's
see,
let
me
go
up,
for
example,
to
my
gk
console
just
to
prove
you
that
that's
really
happening.
B
If
I
go
to
kubernetes
engine,
you
should
see
two
clusters,
the
first
one
that
I
created
without
sorry
this
this
one
that
I
created
without
composites
and
this
one
that
I
created
the
through
composite
simplified
version
and
you
can
see
the
it's
up
and
running.
It's
all.
B
A
Victor,
like
I
just
want
to
stop
for
a
second.
What
he
just
showed
is
that
as
an
sre
team,
if
you
have
a
new
policy
or
a
new
minimum
or
maximum
like
he
showed
or
some
other
change
to
how
your
you
want
your
clusters
to
run
how
you
want
them
to
be
executed.
A
What
this,
what
this
means
is.
You
can
make
that
in
that
of
that
abstraction
that
you're
defining
and
the
compositions
will
inherit
that
automatically
right
and
everything
will
be
up
exactly
everything
will
be
up
to
up
to
your
desired
state.
Pretty
much
automatically!
A
There's
a
question
here,
really
quick
victor
as
you,
you
showed
your
qctl
commands
and
you
you
got
the
that
cluster
composition
object,
there's
a
question
which
one
which
of
the
crds
are
namespace
specific
and
I
actually
had
a
wireless
question
on
if
we
said
like
a
developer,
had
access
to
a
specific
namespace.
Let's
say
it's
just
their
name,
so
I
have
mario,
the
mario
namespace.
Could
I
use
that
namespace
and
deploy
these?
A
These
composition
objects
to
my
just
my
namespace
and
kind
of
be
locked
so
that
they're
not
cubesystem
or
they're,
not
just
generally
in
the
default,
or
something
like
that.
How
does
that
work.
B
So
when
we
create
a
composite
resource
definition
or
xrb,
basically,
there
are
two
two
things
we
define.
I
mean
more
than
two
but
two
important
for
this
question.
We
have
the
kind
which
is
composite
kubernetes
cluster,
which
is
the
one
I'm
just
using
right
now,
and
then
there
is
claim
names
so
typically
that
type
of
user
would
not
have
permissions
in
my
cluster,
the
one,
the
control
cluster,
to
execute
anything
on
cluster
level,
so
in
majority
of
cases
people
would
not
have
the
ability
to
create
composite
kubernetes
cluster.
B
Instead,
I
would
give
them
permissions
to
create
claims
in
specific
namespaces-
and
this
is
this
is,
I
think,
where
crossplaying
comes,
shows
its
strength
for
a
simple
reason
for
being
a
kubernetes
native
type
of
infrastructure
management
tool
right.
So
you
would,
you
would
create
a
namespace.
You
would
choose
your
weapon
of
choice
like
either
opa
gatekeeper
or
kyver,
not
to
set
up
policies
in
that
in
that
control
cluster
right,
not
the
clusters
that
we
are
creating
control
cluster.
B
Those
are
the
policies,
those
are
the
namespaces
all
the
stuff
that
you
normally
do
and
give
give
a
you
give
a
person
or
a
group
of
people.
Access
to
that
namespace,
you
say
hey.
This
is
what
you
can
do
in
in
that
next
space
and
nobody
else
and
among
other
things
you
would
say,
hey
you
can
create
claims
for
kubernetes
in
this
example
for
kubernetes
cluster
right,
yeah,
okay
and
you
could
even
you
could
one
more
thing
very
quickly.
B
If
you
combine
it
with
policy
management,
you
could
say:
hey
in
the
namespace
a
you
can
create
clusters
with
five
nodes
and
in
a
space
b
you
can
create
clusters
with
500
nodes,
because
those
are
the
policies
and
policies
that
are
acting
against
the
kubernetes
resources,
and
this
happens
to
be
a
kubernetes
resource.
Gotcha.
A
Okay,
that's
incredibly
powerful.
I
actually
did
not
know
any
of
that
at
all.
So,
if
your
victor
just
said,
you
have
that
control,
you
can
dial
in
what
a
namespace
can
and
can't
do.
Maybe
one
namespace
can
create
clusters
and
another
namespace
can
create
rds
instances
right
whatever
it
might
be
in
terms
of
provisioning
and
cloud
resources.
A
Other
kubernetes
clusters,
when,
when
victor
2
says
a
control
cluster
he's
just
talking
about
the
cluster
like
he's
interacting
with
right
now,
where
he's
creating
these
custom
objects
and
that
cluster
is
then
cross
lanes
running
and
creating.
You
know
the
cluster
for
you
that
that
the
created
object
right,
which
is
a
different
cluster.
Obviously
right,
yeah.
A
A
Right
right,
gotcha,
one
less
one,
last
question
on
that,
so
in
terms
of
access,
so
I've
created
my
cluster
with
my
cluster
composition.
How
do
I
get
like?
How
would
I
go
and
set
up
cube,
ctl
and
and
all
the
rest,
so
I
could
start
interacting
with
that
cluster
with
that
resource,
and
this
is
kind
of
the
same
for
like
if
I
was
creating
an
rds
instance
or
anything
like
that.
Like
how
do
I
get
the
the
details,
I
need
to
be
able
to
interact
with
that.
A
Maybe
for
my
laptop
is
that
kind
of
a
more
like
a
more
manual
set
of
steps,
or
you
know
how
does
cross-plane
enable
maybe
that
to
be
a
little
easier.
B
To
enable
you
to
access
the
cluster
that
you
created
yourself,
yep
yeah,
so
it's
cube
cattle.
Does
this
cross
plane
system?
No,
it's
not!
That
brush
stash,
name,
space
cross,
plane
system,
get
secrets
right.
So
and
again
it
depends
on
how
you
define
your
composition
right.
B
Let
me
see,
I
made
a
mistake
somewhere,
I
know
upbound,
I'm
using
a
bound
version
of
it
system,
get
secrets
right.
So
if
you
look
at,
let
me
find
it:
where
is
it.
B
Yeah,
so
you
see
here
in
the
team
main
namespace
I
have,
I
have
a
secret
called
cluster
and
that
secret
contains
all
the
all
the
authentication.
I
would
need
to
use
to
connect
to
the
cluster,
either
myself
or
cross
plane
to
do
additional
actions
in
that
class
cluster,
because
I
could
connect
cross
plane
with
helm,
for
example,
to
install
some
stuff
in
that
cluster
through
crossplane
or
me
as
a
user.
B
So
and
now
again,
this
secret
happens
to
be
called
cluster,
because
that's
how
I
defined
that
it
should
be
called
in
composite
definition
right
and
that
secret
can
be
anything
because-
and
this
is
important-
I
think
you
as
sre
you're
in
total
control
of
what
is
really
happening.
Should
there
be
a
secret
with
authentication
or
not,
should
it
be
name-spaced
or
not?
Should
it
contain
this
or
that
yeah.
B
A
Yeah,
I
was
just
I
was
thinking
like
you
could
maybe
even
do
something
in
a
pipeline
where,
like
the
pipe
like,
let's
say
that
you've
got
a
feature,
branch
and
you're
actually
spawning
cross,
plane
and
you're
spawning
a
femoral
environment,
and
that
is
a
new
cluster
right
and
it's
got
some
resources
in
it
and
then
obviously
you
might
want
to
access
that
cluster
to
interact
with
it
during
the
the
time
frame.
Where
you're
you
know,
testing
some.
A
You
know
the
feature,
and
maybe
someone
else
wants
to
look
at
it
or
you
want
to
play
around
with
some
of
the
processes
whatever
it
might
be.
Maybe
the
pipeline
can
then
surface
those
those
credentials
to
you
somehow
or
send
them
slack
or
whatever
it
might
be.
Where
you
can
then
just
easily
just
send
you
I
mean,
send
you
a
cue
config
right
and
then
you
can
start
interacting
from
your
laptop,
depending
on
your
networking
and
all
those
other.
A
All
those
other
pieces
medic
asked
about
having
two
control
plane
clusters
using
git,
ops,
syncing
on
the
same
repo.
Would
it
create
multiple
cloud
resources
and
dan
magnum
came
to
the
rescue
and
said
you
know,
crossplane
will
kind
of
assume
control
of
an
existing
resource,
but
he
would
not
recommend
that
either.
I
wouldn't
recommend
that
that
gets
into
h.a
and
all
that
other
stuff,
so
medic.
Thank
you
for
bringing
the
hard
hard
hitting
questions
and
dan
thanks
thanks
for
answering
those
victory
I'll.
Let
you
continue
with
this.
A
B
A
B
B
And
nobody
gets
and
everybody
still
can
do
whatever
they
need
to
do.
A
B
Yeah,
so
one
more
thing:
actually,
I
will
try
to
keep
it
short,
so
in
case
there
are
more
questions.
I
hope
that
there
are,
but
what
did
I
want
to
do?
That's
not
what
I
wanted
to
do.
I
didn't
want
to
go
to
here,
I'm
getting
lost.
Where
did
they
want
to
go?
Go.
A
B
So,
in
the
meantime,
let
me
see
what's
the
status
of
my
cluster
yeah,
so
another
thing
that
I
think
that
this
is
the
last
thing
that
I
will
show
we
have
also
out
since
we
are
talking
about
kubernetes
and
we're
talking
about
fully
automated
and
constant
feedback
loop,
meaning
that
there
is
a
constant
drift
detection
reconciliation.
B
So
if
I
happen
to
have
a
access
to
in
this
case
to
google
cloud
console-
and
I
go
here
this
will-
I
will
this-
will
actually
the
first
question.
I
will
ask
the
audience-
and
I
go
here
edit
and
change,
for
example
this
to
number
three
and
if
I
enable
all
to
upgrade
and
save,
can
anybody
guess
what
will
happen.
A
No,
no
yeah,
I
I'm
speaking
for
the
audience
in
this
case.
No
one
said
anything
yet,
but
I'm
gonna,
I'm
gonna,
be
that
that
person.
Nothing
should
happen
right.
This
is
the
team,
a
cluster.
This
is
managed
by
crossplane
right.
It's
it's
more
so
managed
by
that
that
core
base
template
configuration
that
we're
talking
about
right,
that
core
composition
and
that
composition
doesn't
say
that
we're
okay
to
upgrade
things
right,
so
imperative
changes
should
not
get
applied.
A
B
Something
will
happen
right
because
I
did
actually
go
directly
to
google
behind
crossplanes
back
it's
it's
equivalent
to.
Let's
say
that
I
created
the
deployment
with
three
pods.
It
would
be
the
same
as
if
I
deleted
one
of
the
pods.
B
And
I
think
that
this
is
something
special
that
hardly
any
tools
in
that
area.
Have
it
it's
not
only
that
we
can
create
and
manage
infrastructure
with
cross
plane,
but
crossplane
guarantees
that
the
state
that
we
defined
is
maintained,
always
yeah.
B
A
A
Yeah,
I
think
medic
was
just
asking
about
single
points
of
failure
for
infrastructure,
provisioning,
okay,
well,
yeah
now's,
the
time
like.
If
anybody
here
is
like
what
does
this
even
mean?
Why
does
this
make
sense?
What
what
am
I
trying
to
do
with
this?
We
have
some
time
here
for
questions,
so
please
please
share
them.
No
question
is
stupid.
I
had
a
bunch
of
dumb
questions
for
victor
before
we
started
this
and
so
yeah.
A
Just
just
ask
just
ask
away,
and
I
know
dan's
doing
a
great
job
while
we're
waiting,
crossplane
dot
io,
you
can
check
them
out
on
twitter
as
well
at
crossplane,
underscore
io.
Victor
is
also
on
twitter
twitter's,
where
it's
hopping
for
the
cloud
native
community.
Like
you
gotta,
be
on
twitter.
You
gotta
dial
in
that
feed.
You'll
get
some
you'll,
get
some
great
news
and
thoughts
and
comments,
and
you
know,
philosophies
as
well
victor's
at
v
farsec.
A
You
should
absolutely
check
out
the
devops
paradox
podcast
as
well
that
he
does
yup
yup
his
name
yup.
Our
names
are:
wait,
wait,
wait,
yep
got
it
got
it
got
it
at
devops
paradox!
That's
that's!
A
great
great
podcast,
in
addition
to
I'm
sure
the
kubernetes
podcast
and
many
others
out
there
cube
lists
that
are
that
are
fantastic,
is,
is
crossplaying
gonna
do
its
own
podcast
or
is
it?
Is
it
working
on
one?
I
know,
there's
a
youtube.
B
Yeah
there
is
not
yet
podcasters
if
only
audio,
but
I
took
over
part
of
youtube.
So
if
you
go
to,
I
don't
know
the
others,
but
if
you
go
to
outbound
the
youtube
channel,
you
will
see
me
there
at
least
once
a
week
something
new.
A
Excellent
wow,
that's
awesome,
okay,
yeah!
I
see
it
here
and
it
looks
like
there's
a
google
group
as
well
and,
of
course,
the
slack
channel
for
for
crossplane.
Oh
wow,
yeah,
there's
lots
on
the
youtube.
Actually.
This
is
this
is
very
cool.
There's
some
great
talks
and
great
live
streams.
There's
some
great
q
con
talks
as
well
on
crossplane,
which
I
think
is
how
I
got
a
little
bit
more
acquainted
with
it
back
in
gosh,
2019,
north
america,
in
san
diego.
I
think
gosh
such
a
great
such
a
great
time.
A
B
Yeah,
I'm
not
sure
that
might
correct
me.
I
don't
think
that
there
is
a
way
to
kind
of
like
a
tool
that
says
validate
this.
You
I
mean
if
there
is
an
obvious
that
it
doesn't
fulfill
specification
it
you
will
not
be
able
to
create
it
in
the
first
place,
kubernetes
api,
but
on
the
other
hand,
whether
you
brought
version
or
version
or
whatever
that's
that's
going
that
that's.
We
don't
have
a
tool
for
that
and
then
after
the
specification,
would
you
create
a
composite
it?
B
Would
it
would
fail
or
not,
depending
really
on
what
the
what
the
error
is.
A
Question
as
I'm
looking
at
the
upbound
website
again
for
those
that
don't
know,
crossplane
is
a
project
by
the
company
upbound,
which
victor
is
an
advocate
for,
and
so
I'm
I
I
know
upbond
recently
announced
the
universal
control
plane
kind
of
the
up
on
cloud
victor.
Can
you
give
us
kind
of
the
the
tl
dr
on
what
that
what
that
is
and
what
problems
upbond's
trying
to
solve,
and
maybe
more
so,
how
it's,
making
crossplane
more
flexible
and
easier
to
use.
B
So,
yes,
we
have
built
to
begin
with
the
web
ui
and
a
sas
service.
So
you,
if
you
go
to
cloud.upbound.io,
basically
you
get.
The
crossplan
is
a
service
and
we
are
about
to
release
that
same
and
we're
about
I'm
not
sure
about
the
naming
yet
but
enterprise
crossplane
self-managed,
so
you
can
self-manage
it
or
you
can
consume
crosstalk
as
a
service.
B
A
Sure
definitely
very,
very,
very
exciting,
yeah,
that's
awesome,
that's
really
cool!
I'm,
I
think
we're
gonna.
My
team,
at
least,
is
gonna,
be
trying
to
look
at
that
q1
q2
of
next
year,
when
we
have
a
little
bit
more
of
our
tech
debt
crunch
and
we're
not
we're
not
so
busy.
We,
you
know,
I
think
we
and
many
others,
many
other
people
I
talked
to
are
thinking
about
this.
A
How
do
I
get
esri
out
of
this
churn
of
these
ad
hoc
requests,
just
kind
of
the
maintenance
of
things
at
a
certain
level,
and
how
do
we
get
to
like,
like
you
mentioned
before
so
so
eloquently
victor
building
automated
systems,
self-service,
tooling
and
more
insights
and
observability
around
our
systems
and
providing
that
as
a
service
as
a
product
to
the
very
engineers
that
depend
on
our
infrastructure
right
and
that
and
then
thus
the
sre,
you
know
moniker
becomes
something
different
and
and
what
it
is
in
so
many
organizations
which
is
kind
of
a
glorified
devops
cd
sort
of
team
that
operates
very
similar
to
the
way
it
did
10
15
years
ago,
right
so
yeah.
B
You
know
the
way
I
see
it
is
what
aws,
or
whatever
your
provider
is
is
to
sres
is
what
the
sres
should
be
to
everybody
else
kind
of,
like
you,
don't
send
an
email
to
to
aw
saying
I
need
three
notes
right.
A
Exactly
yeah,
it's
all
about
that
new
abstracted
interface.
I
mean
I
am
not
someone
who's
not
like
encountered
this,
like
I
mean
months
ago,
solving
for
ticket
like
seeing
jura
tickets.
That
said,
create
rds
instances
for
service
x,
y
and
z.
Right,
I
mean
like
this
is
this
is
a
common
thing
and
it's
more
prevalent
than
you
think,
I'm
not
seeing
any
more
questions
victor.
So
I'm
gonna
give
you
the
floor.
Is
there
anything
that
you've
been
thinking
about
around
crossplane
leveraging
this
or
what?
What
is
your
next?
A
A
B
From
big
announcements,
what
we
are
working
on
right
now,
there
is
a
strong,
huge
focus
on
provider
coverage
so
that
what
the
the
amount
of
providers
and
the
coverage
that
you
have
with
crossplane
is
close
to
100
percent
of
what
major
providers
give
you
know:
aws
azure
google
alibaba
whatever
there
is,
and
that's
on
top
of
there
is
a
lot
of
providers
that
are
contributed
by
a
community
and,
what's
or
not
like
sibo,.
B
Day
we
worked
on
it,
but
the
major
focus
now
is
to
be
is
to
get
as
close
to
100
as
we
can.
Okay.
A
Gotcha,
no,
that's
a
big
one
for
those
that
don't
know
providers
or
just
what
the
the
providers
ie
aws
or
maybe
in
aws,
like
supporting
elastic
cache
right
providers
are
just
the
interface
to
crossplane,
to
interact
with
those
sorts
of
resources
and
be
able
to
then
provision
them
manage
them
for
you
through
crossplane
and
again
through
the
compositions
you
saw
today.
So
that's
awesome.
I
know
providers,
I
mean.
A
That's,
that's
huge,
like
me,
maintain
maintaining
those
providers
has
got
to
be
painful,
and
it's
not
you
know
so,
for
those
who
don't
like
crossplane
is
a
open
source
project
donated
to
the
cncf,
I'm
not
sure
what
stage
it's
actually
at
right.
Now
it's
got
to
be
not
sandbox
anymore.
Maybe
I
don't
know,
but.
A
You
can
file
issues
you
can
you
know
if
you
find
in
gcp,
there
is
a
resource
that
is
not
working
well
or
it's
not
managed
by
crossfire
like
it
should
be.
You
can
help
make
that
happen.
Make
that
a
reality.
A
B
A
B
I
think
important
important
thing:
crossplan
is
open
source.
So
whenever
somebody
wonders
hey
who
is
maintaining
this,
it
is
an
officer's
project,
so
the
community
around
it
is
maintaining
whatever
is
being
maintained.
Upbound
is
a
company.
B
Let's
say
you
have
dedicated
number
of
engineers
working
on
open
source,
but
it's
not
true.
It
is
open
source.
So
whoever
asked
who
is
maintaining,
I
would
say
you
yeah,
come
to
the
come
to
the
repo.
A
Yeah
and
dan
kind
of
answering
medic
on
you
know
what
kind
of
how's
the
provider
working
more
details
there
definitely
check
out.
What
is
that?
I
think
it's
just
crossplaying
io
is
the
the
github
and
you
can
find
all
of
this
on
crossplane.io
website
as
well.
I
think
upbond.io
is
the
company
website.
I
think
it's
time
to
to
sign
off.
We've
covered
a
lot
of
ground
here,
again
check
out
prospect.
Crosspoint.Io,
my
name
is
mario
lauria.
You
can
check
me
out
mariolauria.dev
for
now.
A
This
is
my
last
cloud
native
live
we'll
see.
I
might
I
might
make
a
return
in
the
future.
Thank
you
so
much
to
victor
and
the
upbound
team
dan
magnum
as
well
who's
been
answering
those
those
questions
and
victor
who's
kind
of
newly
minted
there
and
already
doing
a
great
idea.
I
was
hoping
to
get
him
caught
on
like
some
things.
He
wasn't
quite
sure
on
because
he's
so
new,
but
victor
is
an
evangelist
and
loves
his
stuff.
A
Just
as
much
as
I
do
so,
it's
great
to
talk
to
you
again
victor
today.
This
was
fantastic.
Thank
you
to
the
cncf
bill,
libby
and
others
who
have
made
this
happen,
and
thank
you
so
much
for
taking
your
time
and
your
busy
day
to
tune
in
to
another
episode
of
cloud
native,
live
we'll
be
back
next
week
thanks,
everybody
have
a
great
rest
of
your
day
and
week.
Talk
to
you
later.