►
Description
Join us for Kubernetes Forums Seoul, Sydney, Bengaluru and Delhi - learn more at kubecon.io
Don't miss KubeCon + CloudNativeCon 2020 events in Amsterdam March 30 - April 2, Shanghai July 28-30 and Boston November 17-20! Learn more at kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects
Keynote: End User Awards - Cheryl Hung, Director of Ecosystem, CNCF
https://sched.co/NGIk
A
Hi
so
I'm
Schell
I'm,
director
of
ecosystem
at
the
CN
CF,
the
CN
CF,
created
this
end-user
award
to
recognize
the
value
that
end-users
bring
to
the
cloud
native
ecosystem
and
users
share
their
real-world
successes
and
failures.
They
collaborate
on
best
practices
and
they
directly
contribute
to
many
of
the
CN
CF
projects.
A
I
managed
the
CN
CF
end
user
community,
which
has
companies
from
finance
healthcare,
retail
and
much
much
more
and
last
year,
the
CN
CF
end
user
community
awarded
the
end
user
award
to
Bloomberg
and
JD
comm
and
based
on
their
usage
impact
and
contributions
to
the
community.
I'm
very
pleased
to
announce
that
the
2019
winner
is.
B
B
The
Argo
project
to
the
cloud
native
ecosystem,
you
know
kubernetes
in
particular,
we
started
our
kubernetes
journey
about
early
early
last
year
when
we
joined
the
CN
CF
end
user
community
and
as
a
member
of
the
community,
you
know,
we've
been
able
to
quickly
learn
as
well
as
share
our
own
experiences
with
other
members.
Other
other
end
users
in
the
community
and
perhaps
more
importantly,
it's
really
significantly
increased
the
visibility
and
kind
of
engagement
of
the
entire
company
with
the
open
source
community,
all
the
way
from
senior
management
down
to
individual
developers.
B
So
today,
developers
at
Intuit
are
in
a
far
more
engaged
with
the
open-source
community
than
they've
ever
been
in
the
past,
and
you
know
we
are
active
participants
in
the
ciencia
technical
oversight
committee,
as
well
as
the
end-user
developer
experience
sig,
so
this
graph
essentially
shows
kind
of
a
history
of
kubernetes
adoption
it
into
it,
and
you
could
see
you
know
about
the
same
time.
Last
year
we
had
zero
applications
running
on
kubernetes.
B
There
were
a
few
individual
developers
experimenting
with
kubernetes
clusters,
but
basically
you
know
we
were
not
using
kubernetes
for
any
production
purpose,
and
today
we
have
well
over
a
hundred
kubernetes
clusters
in
production
over
25
hundred
applications.
You
know
running
on
kubernetes
and
you
can
see
there
around
the
end
of
last
year.
There
was
a
big
increase
in
kubernetes
adoption
that
correspond
to
a
company-wide
hackathon,
where
prizes
were
offered
for
taking
your
project
to
production
within
a
month
of
the
hackathon,
and
they
were
not
required
to
use
cover
Nettie's.
B
In
order
to
achieve
kind
of
this
level
of
adoption,
you
know
we
had
to
kind
of
integrate,
create
a
complete
ecosystem
development
ecosystem
for
our
developers,
which
required
integrating
dozens
and
dozens
of
tools.
At
this
point,
it
may
be,
like
you
know,
80
different
tools
and
services
that
our
development
teams
use
on
a
day
to
day
basis
in
a
seamless
and
kubernetes
native
way
into
our
product,
and
arguably
just
as
important
as
adoption
and
developer.
Experience
is
security,
and
so
one
of
the
things
we
decided
to
do.
B
In
order
to
manage
all
of
these
clusters,
we
had
to
create
an
infrastructure
which
we
called
the
intuit
kubernetes
system
manager,
or
I
KSM
for
short,
which
basically
not
only
manages
the
life
cycle
of
each
kubernetes
cluster,
but
access
to
the
cluster,
as
well
as
access
to
cloud
provider,
accounts
and
also
all
of
the
security
and
compliance
policies.
That's
configure
for
each
cluster
using
AI
KSM
were
actually
able
to
upgrade
all
of
our
clusters
every
two
to
four
weeks
as
new
security
patches
come
out
and
we
continue
to
raw
new
features
for
the
cluster.
B
Of
course,
clusters
provide
a
really
clean
kind
of
isolation,
boundary
between
applications,
but
it'd
be
completely
impractical
to
create
a
new
cluster
for
every
single
application.
So,
as
a
result,
we've
also
had
to
handle
some
of
the
security
and
multi-tenancy
issues
in
each
cluster.
So
from
right
from
the
beginning,
we
decided
not
to
give
developers
access
to
a
complete
cluster.
A
complete
kubernetes
cluster
is
really
too
much
for
most
applications
teams
to
manage
on
a
day
to
day
basis.
So
we
decided
to
give
up
giving
teams
only
access
to
manage
two
namespaces.
B
The
namespaces
are
isolated
by
default.
They
can't
talk
to
each
other
or
anything,
and
they
come
pre-configured
with
a
lot
of
security
and
compliance
policies
baked
in
not
only
security
policies,
but
they
also
come
pre-configured
with
access
privileges
for
all
of
their
the
services
and
resources
that
each
application
needs.
So
this
means
that
applicator,
the
application
developers
don't
have
to
worry
about
managing
or
rotating
access
keys,
or
you
know,
certificates
as
long
as
they're
running
their
application.
B
In
their
designated
names
places
they
automatically
had
access
to
all
the
services
they
need
to
run
their
particular
applications
and
our
development
teams
really
love
this.
You
know
more
for
the
things
they
don't
have
to
do
than
they
do
and,
interestingly,
our
security
teams
really
love
this
as
well.
B
At
this
point,
a
lot
of
developers
view
I
KSM,
which
also
manages
the
namespaces
like
a
big,
automated
vending
for
namespaces.
They
just
go
there
when
they
need
to
develop
a
new
application,
they
get
everything
they
need,
they
deploy
their
applications
very
quickly
and
effortlessly.
So
at
this
point
the
kubernetes
adoption
it
into
it
has
been
a
huge
success.
Its
adoption
has
been
much
faster
than
we
anticipated
and
joining
the
CN
CF
as
a
end-user
member
has
really
accelerated
that
process.
B
So
if
you're,
an
end-user
and
you're
still
kind
of
sitting
on
the
fence,
you're
wondering
whether
you
should
join
or
not
I
mean
I
would
highly
recommend
it.
I
think
a
really
good
way
to
get
your
feet
wet
is
to
start
attending
the
monthly
CNCs
end-user
meetings
you
know,
but
from
where
I'm
standing
the
water
is
fine,
so
jump
right
in
you
know,
don't
hesitate.
Thank
you.