►
Description
Don’t miss out! Join us at our upcoming event: KubeCon + CloudNativeCon North America 2021 in Los Angeles, CA from October 12-15. Learn more at https://kubecon.io The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.
CNCF End User Partner Summit (RSVP Required)
The CNCF End User Partner Summit, hosted by Cheryl Hung and Katie Gamanji, will bring together cloud native users to share best practices and lessons learned. Our 40 minutes together will include a panel discussion with General Manager of CNCF, Priyanka Sharma, Chris Aniszczyk (CTO, CNCF), Liz Rice (Chair, CNCF TOC), and Ricardo Rocha (Computing Engineer, CERN and CNCF TOC Member). Join us for an engaging conversation centering on strategy, vision, and how to best navigate and contribute to the cloud native community!
In order to participate, your organization must be a member of the CNCF End User Community.
A
So
hello
and
welcome
to
the
end
user
partner
summit-
and
this
is
a
panel
that
will
try
to
center
on
strategy
and
vision
and
how
to
best,
navigate
and
contribute
to
the
cloud
native
ecosystem
as
an
end
user.
Today
we
have
an
incredible
lineup
of
panelists
from
the
cncf
and
toc
leadership,
including
chris
anishik
liz
rice
and
ricardo
roja.
A
Just
as
a
reminder,
we
are
moderating
this
panel
in
zoom
with
questions
mainly
from
the
end
user
attendees.
Additionally,
we
will
aim
to
stream
this
on
youtube
and
linkedin
and
hopefully,
we'll
go
live
throughout
the
event.
So,
if
there's
any
questions,
please
do
put
them
in
the
zoom
chat
or
you
can
raise
your
hand
and
ask
it
live
if
you
choose
so
before
we
dive
into
the
questions.
Could
I
ask
everyone
to
introduce
themselves-
and
maybe
we
could
start
with
chris.
B
C
D
A
E
E
B
Sure
you
know,
as
I
mentioned
in
my
kind
of
introduction,
end
users
have
been
involved
with
cncf
since
the
beginning.
You
know
we
deliberately
as
we
set
up
the
organization.
We
kind
of
jokingly
refer
to
there's
kind
of
three
three
pillars
to
the
you
know.
You
know
circus.
We
have
at
cncf,
there's
the
traditional
you
know
governing
board,
which
is
boring,
handles
the
business
decisions
budget.
We
have
the
toc
which
liz
and
ricardo
are
part
of
that
kind
of
handles.
B
Initially
they
had
a
seat
on
the
toc.
We
now
have
two
end
user
reps
on
on
the
toc
representing
end
user
interests,
and
you
know,
there's
kind
of
multiple
ways.
End
users
get
involved,
you
know.
Sometimes
they
could
simply
just
be.
You
know
passive,
looking
to
kind
of
learn.
You
know
from
each
other
through
presentations
that
we
do
with
the
end
user
group.
You
know
whether
it's
learning
from
another
company,
how
do
they
do
developer
experience?
How
do
they,
you
know,
potentially
roll
out
service
messages,
service
meshes
other
end.
B
Users
tend
to
be
a
little
bit
more.
You
know
active
and
contributing
projects.
For
example,
you
know
capital
one
recently
contributed
cloud
custodian
and
cncf
and
for
capital,
one
they're,
an
organization
that
essentially
is
going
through
their
own
transformation
right.
So
they
started
out
as
a
bank.
You
know
outsourced
a
lot
of
their
engineering
and
services.
Then
they
decided
wait
a
minute.
B
We
need
to
be
a
little
bit
more
progressive
and
actually
own
some
of
our
engineering,
and
so
they
brought
that
in-house
and
they
started
develop
software
on
their
own
open
sourcing
things
sharing
things
to
kind
of
modernize
how
their
you
know,
bank
was
run,
and
so
they
just
started
to
contributing
stuff,
and
you
know
sharing
their
lessons
with
the
end
user
community.
We
have
other
organizations,
you
know
like
spotify,
which
you
know
have
done
similar
things
where
they've
open
source
backstage
to
cncf.
B
That
kind
of
describes
how
internally
they've
done
you
know
developer.
You
know,
experience
and
kind
of
managing
all
the
services
internally
and
they've
decided
to
share
that
with
the
world
to
learn
from
each
other.
So
I
think
there's
there's
kind
of
multiple
avenues
for
end
users
to
get
involved
with,
or
you
could
just
simply
be
a
passive
listener
and
just
learn
from
everyone.
But
ideally
you
would
hopefully
contribute
some
of
your
lessons
learned
within
your
organization,
but
we
essentially
don't
discriminate
in
one
form
another.
C
C
You
know
a
lot
of
the
pieces
are
in
place,
but
there
are
still
things
that
can
be
improved
and
in
many
of
these
examples,
end
user
organizations
are
the
people
who
are
rubbing
up
against
those
problems
and
they're
in
the
best
place
to
innovate
with
those
problems.
So
it's
really
great
to
see
you
know
those
problems
being
identified
and
solutions
being
identified
and
brought
back
to
the
community.
B
Yeah,
I
think,
historically,
you
know
end
users
have
not
really
been
involved
with.
You
know
a
lot
of
open
sourcing
and
so
on.
They
were
consumers,
and
I
think,
especially
in
the
last
decade,
we've
seen
that
switch
from
it's
not
only
the
the
innovation
is
not
only
coming
from
the
vendors.
It's
coming
from
end
users
hitting
problems
at
scale
or
with
vendor
solutions
and
they've
been
a
little
bit
more
progressive
these
days
and
sharing
some
of
those
publicly.
B
You
know
I
remember
when
I
started
my
career
banks
like
it
was
even
impossible
to
do
stuff
like
almost
outside
the
firewall
of
the
bank
and
now
you're
seeing
banks
like
bloomberg
and
others.
You
know
fidelity.
You
know
capital
one
sharing
these
things
working
in
the
open,
so
it's
just
kind
of
nice
to
see
this
shift
happen
in
the
industry.
F
Yeah
there
was
hey
everyone
priyanka
here
I
mentioned
this
in
one
of
my
keynotes
at
last
year's
kubecon
cloud
native
cons
is
we're
seeing
this
virtuous
cycle
of
innovation.
Where
end
users
are
coming
in
and
being
welcomed
into
the
cloud
native
ecosystem,
they're
trying
out
our
technologies
using
them
battle,
testing
them
and
push
putting
as
much
pressure
as
possible
and
then
finding
areas
where
they
could
bring
something
new
and
that's
where
end
user
projects
are
born,
then
they
donate
those.
Then
they
become
even
a
deeper
part
of
the
ecosystem.
F
A
A
Last
year,
the
toc
is
actually
focused
on
streamlining
the
sandbox
entry
process
for
the
projects,
and
now
the
qscs
are
looking
to
revise
the
incubation
criteria
and
guidelines
for
again
the
incubation
projects.
Now
would
you
be
able
to
talk
us
through
some
of
the
motivations
behind
those
changes
and
how
exactly
could
potentially
make
it
easier
for
the
end
users
to
contribute
back
to
the
community.
C
Yeah
I
I
could
start
with
this,
so
the
sandbox
is
relatively
new.
We've
probably
had
it
now
for
two
or
three
years,
maybe
three
years,
but
it
wasn't
part
of
the
original,
the
original
model
that
we
had,
but
we
realized
that
there
were.
There
was
demand
for
a
place
for
experimentation
and
projects
where
people
wanted
to
collaborate.
C
They
didn't
necessarily
have
a
home
that
they
could
do
that
in
and
we
wanted
to
be
able
to
offer
that
so
the
sandbox
was
really
always
intended
to
be
a
space
for
experimentation
and
over
time
we
kind
of
tweaked
a
bit.
What
the
definition
of
sandbox
really
means
like.
How
good
does
a
project
need
to
be
to
get
into
the
sandbox?
C
So
we've
got
a
much
more
efficient
process
so
that,
if
you
do
have
a
project-
and
you
want
it
to
sort
of
start
benefiting
particularly
from
the
collaborative
nature
of
cncf
sandbox
projects,
don't
get
any
marketing
push,
but
they
do
get
a
lot
of
the
ability
to
well
they're
neutrally
owned
for
a
start,
and
it's
a
good
starting
point
to
jump
off
from
into
incubation
incubation
has
always
been
the
really
hard
bar
to
get
past.
You
have
to
be,
you
know,
demonstrably
cloud
native.
C
We
do
a
lot
of
due
diligence
around
the
governance
of
the
project,
the
technology
in
the
project,
whether
people
are
genuinely
using
it
in
production
cases.
Incubation
is
still
not
fully
de-risked,
but
we
do
expect
a
project
to
be
on
a
pretty
solid
path
and
we
we're
working
on
kind
of
streamlining
that
not
to
change
the
the
bar.
E
D
D
One
thing
that
I
also
had
the
motivation
to
join
the
tuc
is
that,
because
we
are
kind
of
in
the
research
side
and
we've
seen
like
we
were
talking
about
how
the
community
has
been
involved
evolving.
One
thing
that
also
happens
is
that
end
users
get
together
themselves
if
the
like
the
mainstream
requirements
are
not
like
enough
for
their
needs,
and
this
happens
in
the
research
community.
D
So
we
formed
this
cncf
research
user
group,
where
we
try
to
accommodate
more
specific
requirements
from
the
research
community,
so
also
one
one
idea
is
to
to
make
those
requirements
more
visible
in
in
the
ecosystem,
because
I
think
eventually
everyone
will
need
them,
but
maybe
maybe
the
research
community
can
can
be
the
one
that
pushes
them
forward.
First.
E
Yeah,
I
definitely
agree
that
it's
really
important
to
bring
out
the
viewpoints
from
the
end
users
and
expose
that
to
the
toc
so
that
you
get
a
different
view
of
the
problems
that
are
coming
direct
from
end
users
and
the
research
user
group.
That
ricardo
you
mentioned
is
a
great
example
of
that,
and
actually
ricardo
also
chairs,
he's
too
modest
to
mention
this,
but
he
also
chairs
that
group.
So
I'm
I'm
really
grateful
for
everything
that
you
do.
Ricardo
for
this
community.
D
Thank
you
yeah,
but
I
I
stress
again
that
this
is
a
the
good
thing
is
that
it's
really
a
vibrant
community,
where
these
things
happen
by
themselves.
So
the
end
user
group
again
the
research
is
a
group-
is
a
very
good
example
that
just
came
up
out
of
cook
con
and
people
getting
together
over
lunch
and
then
forming
this.
A
F
Yes,
absolutely
so
end
user
driven
open
source
that
is,
has
truly
become
our
a
line
that
we
in
this
foundation
identify
ourselves
with
it's.
Because
of
all
that,
you
have
heard
right
now
right
that,
by
having
end
users
participating
in
our
technical
oversight
committee,
which
is
truly
our
you
know,
a
north
star
body
and
having
folks
like
ricardo
participate
in
it,
you
bring
in
this
new
perspective.
F
I
think,
referring
back
to
what
chris
was
saying.
This
is
a
big
change
from
how
things
used
to
be
by
encouraging
end
users
to
be
part
of
our
community
and
ecosystem,
not
just
as
consumers
but
evaluators
feedback
givers
by
creators
of
technology
we've
changed
the
way
open
source
has
been
innovating
and
not
to
say
this
wasn't
happening
before.
But,
of
course,
there's
been
innovation
from
all
kinds
of
companies,
but
by
a
focus
on
end
users.
F
I
think
the
cncf
cloud
native
computing
foundation
has
institutionalized
has
set
in
stone
that
these
engagements
with
end
users
will
always
happen.
Their
point
of
view
will
always
be
front
and
center
and
that,
to
my
mind,
is
end
user
driven
open
source.
It's
actually
very
similar
for
any
folks
here
in
the
audience.
Who've,
you
know
tried
their
hand
at
startups
and
product
development.
The
whole
idea
right
is
customer
driven
development
or
user
driven
development.
That's
kind
of
what
we're
bringing
to
open
source
with
end
user
driven
open
source
here
at
cncf.
E
E
C
Yeah,
so
I
don't
want
to
steal
too
much
thunder
from
my
own
keynote,
but
but
what
I've,
what
I've
done
with
that
one
is
revisit
those
original
predictions
and
it's
always
a
little
bit
hard
to
tell
whether
it
kind
of
becomes
self-fulfilling,
because
we've
said
we
think
this
is.
These
are
interesting
areas,
but
we
have
seen
projects,
particularly
in
the
sandbox,
in
all
the
five
areas
that
we
identified
last
time,
in
particular
around
the
whole
developer.
C
Experience
and
operator
experience
side
of
things,
so
our
toc
colleague
harry
is
also
going
to
be
taking
part
of
that
keynote
and
expanding
a
bit
on
some
of
the
interesting
changes
that
we're
seeing
in
devex
and
opex,
and
then
we
have
got
a
few
more
thoughts
around.
I
mean
I
think,
those
those
five
areas
we
previously
discussed.
It
was
kubernetes
on
the
edge.
It
was
chaos,
engineering,
devex,
opex,
wasn't
an
ebpf
and
one
more
help
me
chris.
C
A
couple
of
other
things
that
we've
highlighted
one
is
that
multi-cloud
is
real.
You
know
I
remember
sort
of
two
or
three
years
ago,
people
saying
oh,
you
know
cluster,
it
was
all
about
multi-cluster
and
it
wasn't
quite
such
a
real
thing
back
then,
but
now
you
know
it
is
it
is.
You
know,
it'd,
be
really
interesting
to
get
a
show
of
hands
from
folks
on
this
call
how
many
of
you
are
actually
engaged
in
multi-cloud.
C
You
know,
I
think,
both
in
terms
of
multiple
public
clouds,
but
also
the
hybrid
cloud
split
between
you
know,
on-prem
and
public
cloud
we're
seeing
some
real
solutions
related
to
to
that,
and
I
I
feel
like
that's
become
you
know,
a
real
area
of
interest
and
another
one
that
I
remember
is
ai.
You
know
it's
we're
seeing.
B
Yeah
staring
at
your
shirt,
yeah
yeah.
I
think
I
think
the
only
thing
I
would
add
to
that
is
seeing
kubernetes
used
as
more
as
kind
of
like.
Let's
call
it
a
cross-cloud
control,
plane
and
running
more
workloads
than
are
just
containers
right.
You
know,
kubernetes
may
have
started
as
purely
focused
on
containers,
but
we're
seeing
it
you
know,
stretch
to
running.
You
know
vms
ai,
based
workloads,
orchestrating
cloud.
You
know
based
services.
I
think
you
know
people
are
just
finding
it
useful
as
a
a
control
plane
that
could
handle.
A
One
thing
I
can
say
I'm
definitely
looking
forward
for
the
keynotes
tomorrow,
so
learning
a
bit
more
of
these
predictions
within
the
cloud
native
ecosystem.
We
actually
have
a
question
from
our
end
users
and
I'm
gonna
read
it
out
now.
So
the
question
is
coming
from
sergio
and
he
is
asking
that
now
we
are
in
an
open
source,
cold
war,
where
open
source
tech
pioneers,
like
elasticsearch,
feel
they
need
to
change
the
open
source
licenses.
How
is
cncf
mediating
this
conflict?
A
B
Question
I'll
start
first,
so
you
know
one
of
the
premises
of
cncf
was
always
to
allow
permissive
innovation
right.
You
know
we
license
all
of
our
stuff
under
apache.
You
know
2.0,
which
basically
allows
end
users,
vendors
everyone
to
build
innovative
solutions.
On
top
of
you
know
these
wonderful
projects
without
worrying
too
much.
You
know
about
any
crazy
licensed
obligations
outside
of
attribution,
so
that's
always
been
kind
of
how
we've
structured
the
organization
and
pushed
ourselves
towards
basically
permissive
and
permissionless.
B
B
I
don't
really
see
cncf
as
an
organization
to
kind
of
like
you
know,
mediate
these
things.
You
know
from
our
perspective.
We
really
want
to
listen
to
our
end
users,
and
you
know
if
our
vendors
or
end
users
have
issue
with
things
we
could
always.
You
know
collaborate
on
potentially
a
solution
to
work
around
these
things,
but
in
general,
like
I,
don't
really
see
cncf
as
a
mediator
here.
These
are
organizations
making
these
decisions
based
on
you
know,
business
needs
or
other
influences.
B
The
only
thing
that,
on
a
personal
level,
bothers
me
is
when
you
have.
You
know
companies
that
essentially
free
ride
on
the
permissive
commons.
You
know
using
a
license
like
atp
or
sorry
apache
and
then
changing
to
a
more
restrictive
license
that
just
personally
pisses
me
off
a
little
bit,
because
it
does
cause
a
little
consternation
in
the
ecosystem
and
it
does
cause
confusion
when
it
comes
to
adoption
on
the
product
side,
but
in
general
cncf's
roles
not
to
be
a
mediator.
B
C
I
could
add
in
a
a
very
much
echoing
that
sentiment.
I
think
we
have
seen
how
successful
this
organization
has
been
based
on
apache
licenses.
You
know,
permissive
licenses
have
allowed
such
great
innovation
and
such
great
collaboration,
and
there
are
plenty
of
vendors
vendors
surrounding
this
ecosystem
who
are
managing
to
build
successful
businesses.
C
A
D
Maybe
maybe
to
add
a
bit
to
that
is
just
reinforced
here
is,
I
think
the
one
worry
here
is
that
the
communities
themselves
change
like
like
it
was
being
said
that
this
has
been
extremely
successful
in
not
only
making
open
source
popular,
but
also
some
companies
that
traditionally
were
not
so
keen
on
open
source,
actually
changed
their
minds
and
have
been
highly
participative
so
yeah.
One
of
the
worries
that
we
kind
of
go
back
in
time
a
bit.
So
let's
see
how
it
continues.
A
F
F
The
community
has
kept
shipping
at
a
great
pace.
Don't
know
what
that
says,
but
we
have
been
productive.
People
have
really
come
together
and
supported
each
other.
I
you
know.
If
I'm
feeling
down,
I
literally
just
needed
to
go
tweet
and
someone
would
reply
and
have
encouraging
words
have
supported
my
words
and
I've.
F
Seen
that
happen
not
just
for
me,
but
for
others
with
each
other-
and
I
think,
we've
been
very
resilient
in
this
time
because
we
are
made
of
a
global
force,
we're
so
many
different
kinds
of
people
coming
together
and
our
mission
is
the
same.
We
want
cloud
native
to
be
ubiquitous,
we're
on
this
path
of
progress
that
is
paved
by
our
diversity
by
our
resilience
by
our
solidarity.
F
So
you
will
see
that
reflected
everywhere
in
kubecon
this
whole
week.
One
of
the
keynotes-
that's
really
exciting,
is
by
peloton
and
it's
on
the
agenda.
You'll
see
they
talk
about
how
they've
navigated,
through
the
pandemic,
gone
fully
cloud
native
and
all
the
cool
things
that
have
happened
for
them
and
they
by
the
way,
are
not
an
anomaly.
F
There
are
so
many
companies
out
there
who've
completely
ramped
up
engineering
workforces
during
the
pandemic,
as
every
company
has
become
a
digital
company
with
like
much
faster
speed,
and
so
many
folks
have
doubled
down
on
cloud
native
you'll
see
a
lot
of
that
in
the
various
talks
that
really
cloud
native
has
become
the
building
block
of
you.
The
human
experience
in
the
pandemic-
and
I
think
that
sets
us
up
for
success
in
the
future.
As
liz
said
there's
so
many
areas
where
we
are.
F
You
know
in
the
predictions
that
we're
going
to
be
critical
in
ai
being
a
big
one
and
aiml
is
taking
a
bigger
and
bigger
role
in
society.
Just
because
of
all
the
information
that
we
have
now
so
you'll
hear
stories
about.
All
of
that,
and
I
think
most
of
all
you
meet
people.
You'll
hang
out
with
folks
not
quite
the
same
as
in
person,
but
it
is
definitely,
I
think,
a
bigger
crowd
like
we
just
have.
E
F
They're,
you
end
users,
you
are
the
heart
and
soul
of
what
we
are
doing.
We
are
building
for
you
for
your
success,
so
any
minute
you're
able
to
spend
with
us
is
a
minute
well
spent
and
one
that
we
value
so
the
simplest
thing
enjoy.
The
cube
cons,
show
up,
learn
and
take
what
you
learn
back
to
your
organizations.
F
I
think
you
know
it's
it's
a
great
way
to
be
in
a
part
of
a
community
where
it's
everyone,
just
it
going
through
very
similar
on
the
same
path
to
progress
as
you
are,
and
you
can
have
clear
candid
conversations
about
what's
working
for
folks.
What's
not
working
for
folks,
and
I
I've
heard
you
know,
I
was
actually
reading
this
book
about
habit
making
and
in
some
ways
we're
all
changing
our
cultures
and
the
way
we
our
old
habits.
F
C
C
You
know
areas
of
of
knowledge
and
experience,
and
we
lean
on
those
groups
for
advice
to
us
and
also
advice
to
that
end
user
community.
So
if
you
have
people
in
your
organizations
who
are
really
involved
in
you
know
security
or
observability
or
any
of
the
there's,
I
think
seven
altogether
getting
involved
with
those
groups.
Sharing
your
experience,
helping
write,
white
papers,
helping
us
understand
where
things
are
confusing
to
people.
C
B
I
guess
to
kind
of
end
the
the
thought
on
this
one
is
you
know
of
all
the
kind
of
the
companies
I've
worked
with
on
the
end
user
side,
everyone
has
different
problems.
Some
are
a
little
bit
more
progressive
than
others,
and
some
are
just
like
super
early
in
the
stage
of
their
cloud
native
journey,
and
sometimes
they
just
have
simple
questions
like
hey.
Can
you
go
talk
to
our
legal
team
to
explain
open
source
or
like
hey,
you
know?
How
do
you,
potentially
you
know,
contribute
upstream?
Without
any,
you
know
ip
concerns.
B
D
Okay,
I
can
just
build
on
that
then,
and
just
add
liz
mentioned
the
six.
There
are
also
the
end
user
groups
that
people
can
can
reach
out
to,
and
it's
a
very
good
way
to
get
introduced
to
other
people
using
the
same
products.
I
think
one
thing
liz
mentioned,
which
is
giving
feedback
to
the
project
themselves.
It's
critical.
This
is
something
that
always
has
a
very
good
reaction
from
from
the
projects
themselves
and
then
maybe
I'll
just
mention
also
this
technology
radars
that
cncf
runs
often
these
are
also
very
valuable.
D
There
are
reports
being
published
in
different
areas
regularly
by
cheryl
and
cncf
end
user
end
users.
So
this
is.
This
is
extremely
good.
If
you
can
provide
feedback
on
those,
it's
always
very
welcome
and
then
in
the
in
coop
con.
I
think
it's
it's
a
very
good,
very
good
opportunity
to
to
reach
out
to
people
there's
very
relaxed
sessions.
I
remember
in
the
last
coup
con,
I
think
also
katie
and
cheryl
were
there.
A
It's
absolutely
fantastic,
so
many
ways
to
contribute
as
an
end
user.
So
I
hope
all
of
the
attendees
will
make
the
best
use
of
these
these
channels
and
these
opportunities,
I
know
we're
kind
of
drawing
close
to
the
end
of
our
panel.
However,
we
still
have
one
question
from
our
end:
users-
and
this
is
directed
to
chris-
and
it
sounds
like
this.
Chris
have
mentioned
that
there
would
be
more
guidance
from
the
cncf
on
projects
moving
to
agpl,
like
menio,
grafina,
labs,
etc.
A
B
Yeah,
no
I
mean
we
have
a
very
you
know,
as
I
mentioned
before.
Cncf
is
all
about
kind
of
permissive
innovation
and
so
on.
So
our
allow
list
of
licenses
that
projects
can
depend
on
are
generally
all
permissive
licenses
like
mit
other
apache
things
bsdns
so
on.
Agpl
is
definitely
a
more
restrictive
license,
so
it
is
not
allowed,
as
I
mentioned
before,
there's
been
a
trend
in
the
industry
to
kind
of
change.
B
You
know,
let's
call
free
writing
on
the
permissive
commons
and
changing
from
something
like
an
apache
agpl,
and
so
some
of
our
projects
are
affected
by
this.
We
recently
posted
some
guidance
on
the
cncf
foundation,
github
repo
for
our
projects
that
we
will
be
publicizing
more
next
week,
but
we're
all
a
little
bit
busy
at
kubecon.
But
if
you're
interested
in
kind
of
reading
the
full
details
that
link,
I
posted
in
the
chat
from
the
foundation,
repo
kind
of
gives
a
set
three
recommendations
of
projects.
What
they
could
do.
B
It
could
be
as
simple
as
using
the
old
release
or
getting
together
with
partners
and
peers
in
industry
and
maybe
forking
that
you
know
that
old
release
and
maintaining
it
in
open.
So
there's
a
different
set
of
recommendations
for
folks
and
we
plan
to
talk
it
out,
talk
about
it
more
after
kubecon
next
week.
A
F
I
just
wanted
to
add
one
piece,
which
is
that,
in
that
spirit
of
being
a
diverse
ecosystem
of
be
having
diversity-powered
resilience,
we
innovated
on
the
kubecon
cloud
native
con
schedule
as
well
and
two
things
that
are
new.
This
time
are
a
business
value
subtract
which
has
a
few
talks
around
literally
cloud
native
101
definitions:
how
to
sell
open
source
internally.
Things
like
that.
So
if
you
have
colleagues
in
your
company
who
you
really
think
would
benefit
from
this
and
would
make
your
job
easier
feel
free
to
send
them
that
way.
F
Now,
if
they
are
coming
into
this
part
of
the
ecosystem
with
us
and
will
support
you
in
your
journey,
the
second
piece
that
we've
added
is
for
learners
and
students
around
the
world.
We've
often
heard
that
even
our
101
content
can
be
advanced
for
someone
who
is
a
learner
or
a
student
and
may
not
have
real
time
experience
with
a
large
production
system.
So
if
you
know
anyone
like
that
or
on
your
teams
or
in
your
life,
please
feel
free
to
send
them.
F
This
way
too,
because
we
want
to
start
supporting
that
path
to
progress
that
people
make
from
as
early
as
possible
and
figured
that
a
student
subtract
would
be
valuable
and
if
people
want
to
find
any
of
these
sessions,
just
go
on
the
schedule
and
click
on
student
track
or
business
value,
and
you
will
have
access
to
talks
that
we
recommend
for
those
experience
levels.
So
just
thought.
I'd
mention
that
since
there's
something
cool
for
you.
C
I
think
I
would
just
say
we
really
really
do
value
input
from
the
end
user
community
things
that
are
impacting
you.
You
know
some
of
the
things
that
have
come
up
in
the
discussions
earlier
about
things
like
licenses.
We,
you
know
we'd
love,
to
hear
what
the
the
real
impact
of
this
is,
for.
You
know
for
end
users
who
are
dealing
with
stuff
like
that
on
the
you
know
on
the
coalface,
as
it
were,
so
your
input
is
hugely
valuable.
Thank
you.
B
B
Users
are
happy
with
it,
so
please
offer
us
feedback
and
hopefully
we'll
be
able
to
all
see
each
other
physically
and
in
los
angeles
in
I
guess,
that's
four
months
or
so
from
actually
a
little
bit
more
than
that
in
october,
so
other
than
that
yeah
give
us
feedback.
We'd
always
want
to
improve
and
iterate
on
making
kubecon
a
better
experience
for
all.
But
hopefully
this
is
my
one
of
my
last
virtual
events.
F
That
is
exactly
what
I
was
going
to
say:
fingers
crossed
last
virtual
only
event
planned
for
la
in
october.
Hopefully
you
know
many
regions
around
the
world
will
be
able
to
travel,
and
I
was
just
thinking
as
we
were
talking
here
right
as
we
would
say
things
it's
like.
I
have
no
idea
if
that
landed
with
this
audience.
F
D
C
A
Definitely
looking
for
in-person
events
and
definitely
looking
forward
for
capcom
europe
next
year.
Already,
this
one
is
not
finished,
but
I'm
already
looking
forward
for
the
next
one.
Thank
you
very
much
for
all
of
our
panelists
and
all
of
our
attendees.
At
the
indies
of
partner
assignment
and
all
of
your
questions,
it
was
great
to
see
what
the
actual
end
users
are
caring
to
talk
more
about
and
explore.