►
From YouTube: 2022-04-07 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
has
started-
and
this
is
the
april
7th
2022
cross,
plane
community
meeting.
There
are
a
number
of
folks
who
are
not
able
to
make
the
call
tonight,
but
I
think
that
they
have
added
their
agenda
items
to
the
agenda
document
here.
This
is
a
live
agenda
doc,
so
folks
are
more
than
welcome
to
continue
adding
suggestions
and
we
will
go
through
all
the
items
one
by
one,
okay.
So
let's
get
into
the
usual
starting
section
of
releases
and
upcoming
milestones.
A
A
Now
my
understanding
of
these
patch
releases
was
mostly
around
setting
up
the
previous
1.5
and
1.6
branches
or
those
those
patch
those
patch
releases
and
to
be
able
to
install
successfully
to
upcoming
1.7
1.8
milestones
that
have
support
for
web
books
and
migrations,
etc.
So
a
couple
of
things
have
been
added
in
there
to
make
that
a
more
smooth
process,
so
getting
updated
to
the
latest
releases
in
the
1.5
1.6
branches
before
migrating
to
upcoming
releases
is
is
recommended.
A
Folks
can
can
add
any
more
commentary
on
that,
but
I
think
that
was
the
main
focus
of
those
patch
releases.
The
release
notes
are
available
in
the
agenda
document
and
you
can
peruse
through
those
and
ask
any
questions.
If
there
are
any
there.
A
I
don't
know
of
any
other
upcoming
plans,
patch
releases
that
are
on
the
horizon,
but
you
know,
as
usual,
we
will
be
releasing
you
know
any
priority
fixes
or
things
that
are
affecting
previous
releases,
as
as
they
come
up
I'll,
keep
accepting
additions
here
for
folks
adding
themselves
to
the
attendees
list
now.
So
the
the
next
milestone
that
we're
working
on
is
the
1.8
release.
The
current
schedule
for
this
is
is
may
17th,
which
is
right
around
kubecon
time
frame.
A
I
think
it's
still
a
good
idea
to
probably
bump
that
release
up
just
slightly
a
few
days
so
that
it
would
be
right
before
kubecon,
as
opposed
to
during
kubecon.
This
makes
sense
from
a
number
of
perspectives,
because
a
lot
of
times
during
keep
going
week,
it's
pretty
hectic.
Pretty
crazy
people
are
busy
with
other
things,
so
trying
to
run
a
release
during
the
middle
of
that
doesn't
sound
like
a
good
idea
and
then
having
the
release
available.
A
So
we
can
talk
about
it
and
get
feedback
on
it
and
gate
and
engage
with
the
community
around
it
during
kubecon
is
probably
a
nice
thing
as
well.
So
I
think,
having
I
think,
that's
still
the
right
thing
to
do
there
and
we
should
probably
make
that
change.
It's
not
it's,
not
a
big
change.
It's
only
a
few
days.
A
It
just
makes
sense
from
a
time
and
perspective
you
can
follow,
along
with
the
plan
releases
and
as
well
as
the
community
calendar,
which
I
think
we
talked
about
in
last
community
meeting,
which
I
was
not
able
to
make,
but
those
are
all
linked
in
the
agenda
documents
as
well
for
1.8
features.
I
think
the
1.8
board
is
fairly
up-to-date,
which
kind
of
reflects
the
highest
level
the
highest
priority
of
road
map
items.
A
So
I
did
a
little
bit
of
cleanup
recently
to
get
this
all
set
up,
so
the
roadmap
is
right
here
and
I
just
changed
windows
with
that
and
then
a
slice
of
things
that
will
be
that
high
level
important
things
that
we
focused
on
in
1.8
time
frame
are
captured
in
the
1.8
specific
word.
So
I
wanted
to.
I
don't
think
muafik
is
able
to
make
it
today,
but
you
know
a
big
focus
for
him
recently
has
been
around
pluggable
web
hooks
and
be
able
to
do
you
know,
validation
and
migration.
A
You
know
mutating
admission
sort
of
stuff
the
that
is
available
in
1.7,
but
there's
still
some
lingering
issues
here.
So
this
is
still
open,
even
though
bulk
functionality
is
there.
So
I
think
there
will
be
a
little
bit
more
commitment
or
investment
in
time
to
figure
to
finalize
some
of
these
lingering
issues.
A
Custom
compositions
is
still
a
huge
investment
that
we're
making
for
the
1.8
time
frame,
we'll
go
into
a
little
bit
more
details
on
custom
compositions
later
on
in
the
agenda
here,
and
I
know
sergey
is
on
the
call
yeah
who
can
provide
us
a
little
bit
more
details
about
what's
been
what's
been
focused
on
recently,
there's
been
a
really
good
community
effort
from,
I
believe
max
has
been
driving
it
for
something
that's
been
largely
requested
from
the
community
that
would
help
out,
with,
in
general,
building
compositions
it's
around
being
able
to
reference
data
sources
from
the
environments
such
as
config
maps,
etc.
A
There's
been
a
couple
of
proposals
on
that
and
a
couple
of
efforts
actually
that
we
weren't
really
able
to
converge
on
from,
I
think
main,
the
main
the
main
feedback
there
was
around
security
potential
vulnerability
issues
with
it.
So
the
current
proposal
looks
like
this
being
driven
by
max,
I
believe,
is
looking
pretty
good.
Where
is
the
pull
request
on
this
one?
I
think
it's
this
one
3008.
A
So
I
encourage
folks
to
take
a
look
at
this,
because
I
think
this
addresses
a
lot
of
people's
requests
for
for
the
functionality
of
being
able
to
support
patching
in
from
common
data
sources.
It
looks
like
muafik
took
a
good
review
on
it
recently
a
couple
of
passes
and
provided
some
feedback,
and
it's
discussing
with
max,
looks
like
this
proposal
is
going
in
a
very
good
direction.
A
So
it's
definitely
something
that's
on
the
on
the
roadmap
here
for
a
little
bit
and
then
being
discussed
and
and
and
having
time
put
into
it
during
the
1.8
time
frame.
I
don't
know,
I
don't
think
we're
committing
right
now
to
the
implementation
getting
into
1.8,
but
the
design
is
is
being
looks
like
it's
being
finalized
right
now
is
making
some
good
good
progress,
so
it
would
be
nice,
since
I
think
max
has
been
working
on
the
implementation
in
parallel
with
the
design
proposal.
A
A
There's
still
some
more
work
on
continuing
to
go
further
with
the
external
secret
store
work
that
hassan
had
been
working
on
recently.
Those
are
that
work
was
in
in
1.7
and
then
some
more
work
here
to
have
a
pluggable
model
where
more
support
besides
vault
and
kereti
secrets
can
just
continue
to
be
added
in
an
out-of-tree
way,
so
that
it
could
be
opens
up
the
doors
for
a
lot
more
support
for
various
secrets
managers-
and
you
know,
credential
management,
sort
of
services
to
be
integrated.
A
It's
cross-planed
very
easily
and
without
a
large
dependency
on
updating
the
core
of
crossplane.
So
that's
something
that's
getting
some
more
attention
here
and
then
some
other
things
that
are
going
to
be
getting
some
attention
are
more
identity
management,
things
like
being
able
to
run
crossplane
in
the
context
of
your
cloud
providers,
identity,
management
and
identity,
aware
services
and
then
observe
only
crossband
resources
are
going
to
be
getting
some
attention
too.
So
I
think
these
are
all
these
put
together
are
from
what
I
believe
to
be
fairly
highly
requested
items
from
the
entire
community.
A
So
I
think
we're
taking
a
fairly
good
focus
here
with
1.7
what
we've
done
and
then
what
I
did.
What
we're
doing
to
continue
that
to
to
address
a
lot
of
things
that
have
been
have
been.
That
will
be
very
helpful
for
a
lot
of
people
in
the
community,
any
questions
or
feedback
on
1.8
or
other
priorities
that
people
want
to
see
or
any
of
that,
and
then
you
know
in
related
to
upcoming
milestones.
A
Or
anything,
I
missed
that
we
know
we're
working
on
that.
We
want
to
get
added
to
the
roadmap.
A
All
right,
if
there
are
any
because
those
are
like
the
main
high
level,
big
ticket
items
that
folks
are
working
on.
So
if
there's
some
smaller
bug,
fixes
and
features
that
folks
are
also
making
contributions
on
or
planning
to
spend
some
time
on.
Please
do
let
us
know
and
they
can
go
ahead
and
make
sure
that
they're
included
in
the
project
board
as
well.
So
they
have
a
little
bit
more
visibility,
but.
A
Ticket
items
that
I
know
are
getting
attention
right
now,
all
right,
so
that
is
core
crossplane,
at
least
so
we
can
go
ahead
and
move
on
down
to
the
provider
section
as
well.
So
let
me
see
who
all
is
on
the
call.
I
think
both
of
them,
so
matthias,
hassan
and
mafik
are
missing
here.
So,
let's
take
a
quick
look
here,
moafix
has
been
driving
the
proposal
around
merging
our
classic
providers
for
aws
for
gcp,
etc,
along
with
their
their
target
generated
providers.
A
There's
been
a
fair
amount
of
discussion
and
feedback
amongst
the
entire
community
on
this
pull
request.
That's
linked
in
the
agenda
dock
here,
29
30.,
and
I
believe
this
is
converging.
A
So
the
proposal
here
that
muafik
is
outlined
of
merging
the
providers
so
there's
just
a
single
aws,
a
single
gcp
and
a
single
azure
provider
will
reduce
a
lot
of
confusion
amongst
the
ecosystem
and
as
well
as
have
a
lot
of
benefits
around
increasing
the
velocity
at
which
in
which
providers
and
features
and
coverage
are
being
delivered.
A
So
you
know,
there's
been
a
ton
of
discussion
on
that
and
it
looks
like
it's
getting
ready
for
going
ahead
and
ratifying
and
merging
in
so
it's
kind
of
a
bit
of
a
last
call,
for
you
know,
feedback
and
opinions
there,
but
you
know
the
the
trend
has
been
reaching
convergence
on
that.
So
that's
that's.
A
big
announcement
to
make
there
looks
like
aaron
is
adding
some
recent
releases
here,
which
is
super
helpful
erin.
C
Hey
the
provider
terraform
is
not
mine,
however.
The
I
wanted
I
we
had.
We
had
this
started
last
community
meeting,
but
we
hadn't
done
an
official
release
of
it.
So
I
just
wanted
to
put
out
the
community
that
we
do
have
an
initial
provider,
a
jet
based
vault
provider
that
implements
one
resource,
which
is
the
generic
secret
resource
for
vault
for
the
terraform
vault
provider.
So
I
want
to
make
sure
that
was
out
there
and
it's
available
for
contribution.
A
Awesome
thanks
aaron,
and
thanks
also
for
grabbing
the
v0.2
release
of
provider,
terraform,
which
I
know
yuri,
has
been
working
a
bunch
on,
along
with
some
community
members
yuri.
B
A
An
update
of
some
of
the
broad
functionality
here,
because
I
know
that
there's
a
pretty
big
push
here-
that
we
should
be
pretty
pretty
happy
about.
E
E
Mechanism
we
have
a
exposure
of
a
tariffer
model,
outputs
right
in
the
status
and
a
bunch
of
bug
fixes
on
the
stabilization
of
the
provider.
E
So
basically
we
got
some
interesting
from
the
community
and
this
provider
and
all
that
folks
from
ge
digital
I
for
posting,
a
blog
post,
mentioning
pro
editor
form
and
action,
and
I
work
with
them
on
reproduction
of
some
scenario
where
they
using
a
composition
which
is
mixing
native
resources
and
some
provider
terraform
based
resources,
so
basically
encapsulating
some
legacy
model,
plus
mixing
them
with
a
visit
classic
native
cross
plain
ones,
and
we
got
a
new
contributor
bob
from
nokia,
which
is
pretty
amazing,
so
yeah.
E
I
think
this
provider
is
getting
more
mature,
there's
like
obviously
a
lot
of
things
to
do
there,
but
currently
it's
pretty
stable
way
to
execute
your
existing
terraform
model
in
cosplaying,
extra
and
yeah.
It's
working.
A
Yuri
I
I
definitely
appreciate
as
well
the
effort
that
went
into
this
release
to
you
know
to
stabilize
it,
but
also
to
put
in
some,
you
know,
feature
functionality
gaps,
and
so
this
is
now
becoming
a
useful
way
or
useful
bridge
for
starting
to
get
your
feet
wet
with
cross
plane,
starting
to
move
some
of
your.
You
know,
terraform
workloads
into
it,
and
you
know
continuing
as
a
part
of
a
grander
vision
for
adopting
crossplane.
So
it's
super
useful,
and
I
also
think
it's
it's
it's
humorous
too.
A
How
quickly
you've
dove
you
have
dived
dove
into
it
with
you
know,
being
included
as
a
new
contributor
in
the
release,
notes
then
becoming
a
maintainer
and
then
driving
the
release
to
get
all
this
out.
So
that's
that's
one
heck
of
a
release
for
written
for
yuri,
but
well
done
man.
A
All
right,
okay,
so
then
we
can
move
on
to
provider
aws
so
v0.26
is.
I
saw
that
there
was
a
delay
on
it
for
getting
like
a
build
a
linter
check
in
I
I
don't
have
an
update
myself
on
if
0.26
is
still
going
out
today.
I
don't
know
if
some
of
the
other
maintainers
of
writer
aws
are
on
right
now
office,
not
christopher's,
not
aaron.
Do
you
have
an
update
on
that
or
know
what
might
be
the
latest
of
fighter
aws
release.
C
No,
I
I
only
know,
what's
mentioned
in
the
notes
that
that
zero
260
is
due
out
today,
okay,
to
include
the
support
for
the
external
secret
store.
Okay,.
A
Yeah,
so
I
know
I
did
see
some
of
that
getting
pushed
in
recently
as
well,
so
yeah,
let's
follow
up
and
see
if
that's
still
coming
today,
but
it
should
be.
You
know,
things
should
be
pretty
much
near
the
finish
line
there
and
they
should
be
going
out
fairly
soon.
That's
that's
something
that
we're
gonna
have
a
lot
of
confidence
in
jessie.
I
saw
you
added
a
note
here
on
the
start
of
the
work
on
assuming
web
of
identity
rules.
B
Yeah,
so
this
is,
this
is
going
to
be
my
first
contribution.
How
are
you
guys
doing?
This
is
something
that
I've
been
speaking
with
a
number
of
upbond
folks
via
a
proof
of
concept
that
we're
working
on
with
upbound
here
at
autodesk
and
due
to
some
some
restraints
on
the
way
that
autodesk
does
you
know
cross-account
authentication
within
within
amazon's
walls.
We
cannot
use
sts,
chaining
and
all
of
the
existing
solutions
for
reaching
cross
accounts
with
a
single
provider
to
multiple
subordinate
accounts
require
sts
chaining.
B
Currently
so
so
the
idea
is
that
we
would
produce
a
solution
that
would
be
similar
to
what
is
being
done.
If
you
were
to
review
the
rest
of
that
issue,
there
there's
there's
other
work,
that's
being
done.
I
think
dan
spoke
to
some
of
that,
but,
unfortunately,
that
those
capabilities
are
not
going
to
cover
assuming
roles
with
web
identities,
which
is
what
irsa
facilitates.
B
So
this
is
going
to
allow.
I
imagine
you
know
if
we
were
to
to
look
at
the
solution,
it's
going
to
allow
for
the
provider
to
move
between
underlying
web
identity
arn's
using
the
same
web
identity.
Token
file
used
saw
alternate,
arns,
possibly
provided
via
the
provider
config,
I'm
not
quite
sure
yet.
I'm
interested
in
anyone's
input
you're
welcome
to
comment
on
that
thread
there,
but
this
is
something
that
we're
going
to
kick
off
today.
Actually.
A
That's
a
great
update.
Jesse.
Definitely
appreciate
that.
I
know
you've
been,
you
know,
providing
a
lot
of
feedback
and
contributing
in
a
lot
of
ways
so
far.
So
then
having
this,
as
you
know,
contributions
the
functionality
is
going
to
be
really
cool
to
see.
Also
so
thanks
for
thanks
for
getting
started
on
that
jesse.
A
Okay,
awesome
all
right
and
then
so
we
can
move
our
head
on
to
provider
azure
and
alpha.
I
know
you've
been
doing
a
bunch
around
there
with
some
identity
related
things
as
well,
which
is
obviously
a
big
focus
in
1.8
across
all
the
providers.
Do
you
want
to
give
us
an
update
on
that
too
out?
There.
D
Yeah
sure,
regarding
provider,
azure
there's
an
open
pr
that
introduces
support
for
user
assigned
and
system
assigned
manager
identities.
As
part
of
this
pr
we
had
also
we
also
had
to
visit.
D
There
was
an
opening
issue
requesting
support,
for
you
know
many
identities
in
aks
clusters.
Currently
we
are
provisioning,
the
service
principle-
that's
the
aks
cluster
will
assume
the
aks
cluster
you
know
has
to
provision
volumes,
load,
balances,
etc,
and
it
does
this
under.
D
Currently
it
does
this
on
resource
account
that
we
provision
in
parallel
to
the
case
cluster
itself
or
before
provisioning,
the
aks
cluster
itself
in
the
controller.
So
this
also
has
a
related.
You
know
bug
that
I
had
opened
it's
product
one,
you
know
that's
related
to
the
propagation
of
the
service
account
that
we
provision
in
the
controller.
D
So,
while
working
on
introducing
support
for
manager
identities,
we
also
had
to
sort
of
you
know
change
the
way
we
do
change
the
way
we
provision
service
principles
for
aks
clusters.
So,
instead
of
you
know
manually
or
you
know,
instead
of
provisioning
game
service
principle,
we
would
like
to
have
azure
user
manager
identity
for
the
aks
cluster.
A
Awesome
and
now
does
that,
does
that
tie
back
into
any
updates
you
want
to
provide,
for
you
know
like
identity
support
in
general
across
providers
in
the
onenote
type
time
frame.
You
know
maybe
above
and
beyond
azure.
D
D
I
have
also
read
about
you,
know
jess's
scenario
and
I'm
very
happy
to
hear
that
we
will
have
assumed
web
identity
support
coming
to
aws,
or
at
least
the
effort
is
beginning,
so
we
have
also
covered
some
other.
You
know
cross
playing
community
use
cases
regarding
these
authentication
and
authorization
issues
in
general.
D
So
the
the
root
issue
that
I'm
also
interested
in
is
provider
partitioning,
there's
an
issue
opened
by
then
you
know
regarding
provider,
partitioning
and
generally.
What
I
do
is
when
I
see
a
use
case,
I
try
to
figure
out
whether
we
really
need
provider
partitioning
to
implement
it
or
not.
You
know
this
is
also.
This
also
have
some
relation
to
the
control
plane
of
control
planes
concept.
D
So
if
you
adopt
such
an
approach
of
you
know,
control
planes
of
control
planes,
then
you
do
the
isolation
at
a
deeper
level
so
that
you
know
you,
don't
you
don't
need
a
separate
provider
deployments
running
in
the
same
kubernetes
cluster,
etc.
D
So
what
I
will
do
next
is,
you
know,
try
to
put
together
some
user
scenarios
that
we
have
heard
about
and
discuss.
You
know
some
alternative
implementations
for
them.
So
currently
you
know
any
user
scenario
that
requires
using
multiple
kubernetes
source
accounts
for
a
cross
plane
provider
does
not
work.
As
you
know,
however,
it
also
looks
possible
that
you
know
using
mutating
wave
at
mission
hooks
and
some
you
know:
kubernetes
arbi
groups
etc.
D
With
the
current
architecture
of
crossplane
we
can
achieve
more.
So
I
will
try
to
prepare
one
pager
where
we
discuss.
You
know
some
alternatives
to
you
know
implementing
these
scenarios
and
then
maybe
we
will
decide
to
implement
an
actual.
You
know
partitioning
or
maybe
we
will
adopt
another
approach.
You
know
where
we
use
some,
for
example,
mutating
weapons,
etc
to
implement
certain
scenarios
yeah.
So,
as
you
mentioned,
these
are
all
under
the
umbrella.
For
me,
at
least
all
under
the
umbrella
of
this
identity-based
authentication
and
the
related
concept
of
provider.
Partitioning.
A
Pretty
awesome-
and
I
think
that
yeah-
that's
something
I'm
really
excited
about
here
upper-
is
that
we're
taking
a
comprehensive
look
at
you
know:
identity
and
usage
and
support
you
know
across
all
the
providers
and
and
seeing
the
patterns
and
and
the
consistency
we
can
get
there.
So
that's
definitely
useful.
I'm
glad
you're
looking
at
it
from
a
complete
angle
in
the
1.8
time
frame,
yeah.
A
D
Thank
you.
One
thing
related
to
this
topic
is:
we
recently
introduced
support
for
manager,
identities
in
jet,
asia.
D
D
E
A
Thanks
for
adding
that
link
gary
all
right,
okay,
cool,
so
I
think
that's
all
the
updates
we
had
for
sharing
on
various
providers,
so
we've
covered
core
cross
plane,
we've
covered
providers,
so
I
think
we
can
move
on
ahead
to
the
community
topics.
A
I
think
I've
accepted
all
comments
and
additions
to
the
agenda
document,
as
we've
been
going
on
so
keep
on
going
in.
I
think
we've
got
everything
integrated,
a
quick
note
here
on
various
content.
I
didn't
see
too
much
since
the
last
community
meeting
at
least
I
know
dan,
which
the
reason
you
can't
make
it
today
is
that
he's
currently
in
london
presenting
at
qcon.
So
he
gave
a
presentation
earlier
this
week
about
cross
playing
and
control
planes
in
general.
A
It
is
not
published
yet
for
the
recordings
not
published
yet
or
the
slides
aren't
published
yet,
but
you
can
see
a
little
bit
of
twitter
talk
on
it
there
at
least
the
the
one
link
provided
there
victor
if
there
is
any
other
videos
or
talks
or
anything
that
you
had
added
recently
feel
free
to
add
these
to
the
gender
documents,
so
they
make
it
as
well.
A
Sweet
sounds
good
and
any
upcoming
talks
that
you
want
to
share
with
us
to
victor,
like
the
like.
You
know,
conferences
that
you'll
be
speaking
at
or
anything
like
that.
C
A
Fair
enough,
all
right
so
cool,
so
custom
compositions,
you
know
very
important
feature.
That's
been
worked
on
in
1.7
time
frame,
but
then
shooting
for
an
alpha
release.
1.8.
I
believe
I
think
that
sergey
is
on
the
call
here
so
yeah
sergeant.
Do
you
want
to
go
ahead
and
give
us
an
update
on
the
latest
efforts
in
general
for
custom
compositions.
F
F
As
you
know,
before
this
one,
we
worked
on
a
poc,
it's
about
using
the
need
containers
to
run
the
krm
functions,
so
this
was
an
option
and
another
option
was
using
the
a
ch
root-based
range,
so
there
is
an
actual.
There
is
a
ready
prototype
in
our
poc
repo.
I
also
added
the
link
here
and
also
as
as
as
I
as
far
as
I
know,
nick
is
also
working
on
preparing
a
prototype
and
another
prototype,
and
our
last
two
think
meetings
about
the
custom
composition.
F
We
could
not
make
them
so
I
hope
that
in
the
next
meeting
we
will
discuss
the
details
about
this
one
and,
as
I
said,
that
about
the
two
options
to
running
the
krm
functions
via
init
containers
or
change
ch
route
based
runners,
we
will
discuss
the
advantages
disadvantages
and
we
will
try
to
decide.
How
can
we
have
can
be
the
next
steps
about
this
one
and
the
general
topic
of
the
custom
compositions.
A
Nice
is
there:
when
is
the
next
scheduled
custom
composition,
sig
meeting
sergeant.
F
Yes,
yes,
when
is
it
scheduled
for
wednesday
morning
wednesday
morning
actually-
and
I
also-
I
can
also
publish
the
time
information
to
the
agenda
doc.
I
think.
A
Yeah
appropriate
to
add
that
in
there
cool
and
is
there
anything
that
you
need
to
sync
with
nikon
before
that
to
get
unblocked
on?
Are
you
making
good
progress
there
independently
still.
F
A
Sounds
good,
yeah
yeah
all
right
glad
to
see
all
that
progress
there,
that's
great
okay!
So
then
you
know
cubecon
eu
is
coming
up
a
little
bit
more
than
a
month
away.
You
know,
as
previously
stated
we
got
a.
We
have
a
booth
in
the
cncfs
project
pavilion.
We
have
a
intro
and
deep
dive
session
in
person
in
valencia
on
the
maintainer
track
and
we
also
have
a
virtual.
You
know
online
project
office
hours
session
as
well,
so
the
project
booth
in
the
cncf
pavilion
project
billion
area.
A
We
do
have
good
staffing
for
that.
I
think
that's
fairly
well
covered.
Obviously
more
folks
are
invited
to
come
and
you
know
hang
out
at
the
booth
or
take
some
sessions
there.
If
you're,
you
know
a
contributor
maintainer
in
the
project,
and
you
want
to
talk
to
the
community
and
answer
questions
and
such
more
people
are
certainly
welcome
to
join
in
on
that,
so
feel
free
to
reach
out
to
me
and
I'll
get
you
in
there
for
sure,
and
then
the
speaker
lineup
is
settled
for
the
intro
deep
dive
session.
A
So
the
final
speaker
line
up
for
that
one
is:
is
christopher.
Harr
yuri
and
stephen
barely
and
then
envy
as
well.
So
those
are
the
four
speakers
on
that
one
and
then
the
virtual
office
hours
the
online
session.
That
is
the
one
we
do
still
need
some,
some
volunteers
or
folks
that
want
to
answer
questions
and
present.
Or
you
know,
however,
you
want
to
get
engaged.
There
are
still
openings
for
that,
one
if
you
want
to
speak
or
if
you
want
to
do
the
q
a
there's
opportunities
there.
A
A
All
right,
I
don't
think
there
were
any
other
things
that
were
added
to
the
agenda,
doc
of
prs
or
deeper
technical
discussions,
etc.
So
that's
all
the
contents
that
I
had
on
the
agenda.
A
Is
there
anything
that
folks
want
to
bring
up
now
or
address
here
at
the
open
time.
A
Okay
cool!
Well
then,
if
there's
not
anything
else
than
on
the
agenda,
then
we
can
go
ahead
and
adjourn
and
we'll
continue
working
on
the
1.8
milestone
and
making
progress
on
that
towards
the
release
right
around
the
kubecon
time
frame.
And
you
know,
if
you
don't
see
folks
at
community
meetings
in
the
meantime
that
hopefully
we'll
see
you
in
valencia,
then.