►
Description
Don’t miss out! Join us at our upcoming events: EnvoyCon Virtual on October 15 and KubeCon + CloudNativeCon North America 2020 Virtual from November 17-20. Learn more at https://kubecon.io The conferences feature presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.
Keynote: CNCF Project Overview - Constance Caramanolis, Principal Software Engineer, Splunk & Stephen Augustus, Sr. Member of Technical Staff, Tanzu Kubernetes Grid - Release Engineering, VMware
https://sched.co/cpGJ
A
A
A
I
have
the
pleasure
of
working
on
the
governing
board
for
open
telemetry.
It
is
a
sandbox
project,
I'll
be
hearing
more
about
it
with
due
time
and
I'm
a
contributor
to
the
collector,
which
is
a
part
of
that
project.
Before
that
I
was
an
envoy
maintainer
at
lyft,
and
now
I
want
to
introduce
my
co-chair
stephen
augustus.
B
Hey
everyone.
I
am
steven
augustus.
I
am
a
senior
member
of
technical
staff
at
vmware.
I
focus
on
open
source
technologies,
primarily
kubernetes,
as
well
as
working
on
tanzu
kubernetes
grid,
I'm
one
of
the
kubernetes
sig
release
chairs
and
release
managers,
so
we're
the
team,
that's
responsible
for
actually
releasing
kubernetes,
also
working
in
the
larger
cncf
as
one
of
the
sig
contributor
strategy
chairs.
B
So
that's
defining
defining
methodology
and
process
for
to
allow
all
of
the
cncf
projects
to
work
better,
both
internally
and
together
and
finally,
I'm
newly
a
maintainer
of
dex,
which
is
now
a
cntf
sandbox
project.
If
you
want
to
follow
me
on
twitter
and
have
a
conversation
there's
my
handle
below,
so
we
are
going
to
give
you
a
few
project
updates
and
I'm
going
to
kick
it
back
over
to
constance.
A
Awesome
so
actually,
before
I
start
up
a
test
project
update,
one
thing
I
want
to
do
is
thank
everyone
who
is
watching
from
home.
Hopefully
you
have
your
popcorn
is
I
want
to
thank
all
of
you
for
your
amazing
submissions,
one
thing
that
really
stood
out
to
both
stephen
and
I
was
the
one
of
the
quality,
but
also
just
the
scale
in
which
all
of
you
operate
your
cncf
projects.
A
A
So
one
thing
I
want
to
talk
about
is
graduation
as
you'll.
Most
of
you
know
it
graduated
november
2019.,
and
so
the
thing
what
I
want
to
highlight
today
is
that
in
january
of
this
year
they
shared
a
blog
post
about
one,
the
process
of
graduating
and
also
just
what
they've
learned
from
it,
and
so
it
really
focused
on
the
process
right
in
terms
of
from
starting
incubation
to
graduation,
and,
as
some
of
you
may
or
may
not
know,
is
that
graduation
does
measure
onto
several
things.
A
One
is
quality
contributions,
adoption
and
so
one
of
the
way
those
things
are
measured
is
through
the
statistics,
and
so
one
example.
That
is
the
number
of
stars
right.
So
one
of
those
easy
things
you
see
in
github
and
what
is
really
amazing,
is
that
over
the
short
period
of
time
from
november
till
now
is
that
the
amount
of
attention
this
project
has
gone,
has
skyrocketed
back
in
november
of
this
past
year,
they're
roughly
nine
thousand
stars
and
now
they're
over
almost
ten
and
a
half
thousand
right.
A
That
is
an
amazing
amount
of
attention
over
the
past
few
years
or
sorry
past
several
months
same
thing
goes
with
commits.
At
the
time
of
the
blog
post,
there
are
roughly
seventeen
thousand
commits
and
now
they're,
almost
twenty
and
a
half
thousand
right.
The
amount
of
work
that
went
into
this
project
is
incredible,
and
so
thank
you
all
the
contributors
to
this
project.
I
highly
suggest
that
all
of
you
read
this
retrospective.
A
A
A
If
it's
hard
to
install
or
adopt-
or
you
know,
include
your
project
or
technology,
adoption
is
going
to
be
really
low,
and
so
seeing
these
contributions
to
increase
adoption
and
ease
that
process
is
so
valuable.
Not
only
that
too,
but
health
of
the
code
base
right.
This
include
refactoring
and
deprecating
features.
These
are
all
important
process
of
the
coding
life
cycle.
A
Let's
talk
about
version
six
one
of
the
latest
ones
especially
had
some
cooler
features.
One
is
expanding
the
support
for
sql.
This
came
in
two
ways:
one
is
expanding
the
support
that
it
had
for
mysql
statements,
understanding,
wider
variety
and
also
actually
improving
the
end
to
end
test
and
to
better
reflect
what
applications
and
frameworks
would
do
as
a
queries.
A
Another
one
is
the
general
ability
of
your
replication
based
workflows,
just
as
a
little
tidbit
v
replication
is
meant
to
provide.
You
know,
use
cases
such
as
real
time,
roll-ups
re-sharding
all
really
important
things
in
terms
of
database,
and
this
is
really
cool,
and
the
last
thing
I
want
to
highlight
is
the
end
to
end
test,
suite,
go
link
and
why
this
is
actually
really
important.
A
Is
that
one
thing
that
happens
in
graduation
is
looking
at
quality
quality
is
hard
to
measure
in
terms
of
contributions
up
there,
but
reducing
the
barrier
to
provide
better
testing
for
a
project
is
something
we
should
all
celebrate,
and
so
one
thing
I
want
to
do
is
thank
everyone.
Who's
contributed
to
this
project
and
all
the
students
you
have
projects
and,
if
you're
moving
to
kubernetes,
don't
leave
your
data
behind,
which
is,
by
the
way
great
tagline.
Now
I'm
going
to
hand
it
off
to
stephen.
B
It's
always
fun
to
talk
about
the
new
features
that
are
coming
out,
but
I
think
that
it's
even
more
important
to
talk
about
some
of
the
things
that
you
might
see
in
in
you
know
in
a
graduation
retrospective
right,
the
the
things
that
we
care
about
code-
health-
they
you
know
lots
of
the
things
that
constance
is
talking
about.
So
you
know,
by
way
of
that,
for
for
process
and
and
project
level,
things
we've
been
working
on
annual.
B
The
kubernetes
steering
committee
is
kicking
off
annual
reviews
for
sigs
and
working
groups,
so
the
special
interest
groups
and
the
and
working
groups
which
are
two
of
the
governance
structures
and
kubernetes
we're
doing
some
project
cleanup.
So
the
github
administration
team
is
working
on
making
sure
that
projects
that
no
longer
need
to
exist
in
our
ecosystem
are
no
longer
have
maintainers
or
certain
levels
of
interest
around
are
archived
and
any
of
those
assets
are
transferred
into
projects.
That
may
be
more
more
active.
B
B
Overall,
while
we
have
the
kubernetes
119.0
release
coming
out
soon
towards
the
end
of
august,
we
did
decide
to
extend
the
release
cycle
by
about
a
month
and
some
change,
and
that
was
to
give
an
opportunity
for
the
contributors,
the
consumers,
really
everyone.
That's
involved
in
the
kubernetes
ecosystem
time
to
digest
the
global
situation
time
to
tend
to
their
families.
B
So
that
is
something
new.
That's
something
that
has
actually
impacted
will
impact
the
release
cycle
for
for
120,
we'll
see
we'll
see
a
shorter
release
for
120.,
but
with
the
release
of
119.
We're
also
extending
support
for
newer
kubernetes
releases,
so
we've
been
talking,
you
know
for
several
cycles.
The
the
lts
working
group
has
been
talking
about
extending
disc
one
discussing
what
lts
might
even
look
like
in
kubernetes,
but
also
what
would
be
some
near-term
steps
that
we
could
take.
B
So
this
is,
you
know
this
has
been
in
discussion
for
a
little
bit
and
then
there
have
been
multiple
issues
and
we're
finally
moving
forward
with
establishing
guidelines
across
the
project
for
how
to
do
that
and
hoping
to
hoping
to
do
that
on
a
wider
cncf
level,
as
well
with
other
projects.
So
now
next
step
we're
going
to
talk
a
little
bit
about
security
and
release
supply
chain.
B
Again,
I
you
know
it's
great
to
talk
about
shiny
features,
but
I
think
it's
it's
even
more
fun
to
talk
about
how
we
how
we
remain
consistent
and
sustainable
as
a
project
over
time.
So
a
few
things
coming
out
of
security
and
release.
We've
got
the
bug
bounty
program
recently
spun
up
and
by
recently
I
think
it's
it's
it's.
It's
been
a
little
bit.
It's
been
around
for
a
little
bit.
B
Around
cvs,
there
has
been
quite
a
bit
of
cv
work
across
the
past
year
or
so
multiple
cvs
that
we
have.
We
have
become
faster
and
faster
at
iterating,
over
and
and
mitigating
so
kudos
to
everyone
on
the
product
security
committee
kudos
to
everyone
who
is
kudos
to
everyone
on
the
release,
management
teams
responsible
for
getting
those
releases
out
in
kudos
to
everyone
who
is
reporting
and
reporting
responsibly
to
our
various
reporting
channels.
B
B
This
is
a
smaller
footprint
if
you
think
of
something
like
building
a
container
from
scratch,
it's
similar
to
that
with
a
little
bit
more
a
few
more
bells
and
whistles.
So
we've
worked
on
moving
our
base
images
over
to
distributors
containers
or
a
slight
modification
on
top
of
distributors
containers
and
we'll
see
that
work
come
forth
in
the
119
release
cycle.
B
We've
sped
up,
and
this
is
kind
of
correlated
with
the
cve
work.
We've
sped
up
our
ability
to
update
dependencies
across
the
project,
primarily
in
the
core,
kubernetes
kubernetes
repository,
but
but
overall,
across
the
project
as
well
and
related
to
those
dependencies,
or
also
making
sure
that
we're
updating
the
base
images
that
we
build
the
api
server,
the
controller
manager
scheduler
the
cube
proxy.
All
of
those
things
making
sure
that
we're
updating
those
base
images
more
frequently
for
for
the
ones
that
are
not
on
distro
list.
B
Yet
we
want
to
make
sure
that
we
provide
a
secure
and
safe
experience
for
everyone
consuming
kubernetes
so
related
to
this
has
been
the
the
kubernetes
infrastructure
working
group.
This
was
an
effort
that
was
spun
up
after
the
google
donated
about
nine
million
in
credits
for
gcp
to
the
kubernetes
project
as
a
means
of
providing
a
base
for
us
to
move
from
google
based
infrastructure
and
over
to
community
owned
infrastructure.
B
So,
across
the
the
last
year
and
change,
there
has
been
quite
a
bit
of
improvement
with
community
ownership
of
infrastructure,
we're
seeing
more
of
our
testing
move
over
to
community
infrastructure,
we're
seeing
more
of
our
our
imaging
process.
So
we
have
an
image
promotion
process
that
is
all
community
based
right
now
and
we
have
recently
moved
the
backing
endpoints
for
kates.gcr.io,
which
is
where
a
lot
all
of
the
images
are
hosted
over
to
community
infrastructure
and
finally,
for
security.
We
see
well
not.
B
B
B
B
We
have
seen
discussions
from
the
alum
os
crew,
the
arm64
folks,
and
we're
trying
to
make
sure
that
we
have
a
consistent
experience
for
people
who
are
interesting
and
interested
in
adding
architecture.
Our
os
support
to
kubernetes
enhancements
a
topic
that
is
near
and
dear
to
my
heart,
how
we
introduce
change
to
the
kubernetes
ecosystem,
we've
been
making
improvements
around
the
labeling
automation,
the
review
and
approval
of
kubernetes
enhancement,
proposals
or
keps,
and
finally,
the
production,
readiness
reviews,
production
readiness
reviews
have
become
part
of
the
of
the
kept
process.
B
What
production
readiness
reviews
are?
Basically,
we
have
a
bunch
of.
We
have
a
bunch
of
ops
types
folks
within
this
project
that
have
seen
have
seen
the
way
things
operate
at
scale
and
the
way
things
fail
at
scale,
and
we
want
to
make
sure
that
we
consider
all
of
the
various
aspects
of
this
when
developing
an
enhancement
right.
What
does
what
does
this
enhancement
look
like
when
we
scale
this
to
5000
notes?
Right?
B
If
that's
a
question
that
we
can't
answer,
then
we
need
to
step
back
and
talk
about
it,
because
a
lot
of
you
are
operating
at
that
scale
and
for
cluster
life
cycle.
We
have
been
discussing
for
a
few
cycles,
now
cube
adm
moving
out
of
the
core
kubernetes
kubernetes
repo.
Overall,
there
are
several
pieces
of
functionality.
The
cloud
providers
cube
ctl
or
cube
cuddle,
cube
c.
You
know
key
of
control
depending
on
what
you
prefer
that
have
existed
in
the
core,
kubernetes
kubernetes
repo
and
for
maintenance.
B
Overall,
it
makes
more
sense
for
them
to
maybe
live
separately,
speed
of
of
iteration
and
and
development,
and
encouraging
more
more
contributions
from
newer
contributors
by
separating
this
out
into
into
distinct
code
bases,
so
expect
some
forward
progress
on
that
in
the
next
few
cycles.
Then.
Finally,
I
think
that
cluster
api
has
been
a
really
interesting
thing.
That's
popped
up
for
the
across
multiple
kubecons
cluster
api
is
declarative
cluster
management
using
kubernetes.
So
it's
a
very
it's
a
very
meta
way
of
deploying
your
kubernetes
clusters.
B
If
you
could
write,
if
you
could
write,
manifests
kubernetes
manifest
to
describe
the
resources
that
belong
to
kubernetes
cluster,
like
how
would
you
do
that
and
cluster
api
is
the
answer.
So
thank
you
all
for
taking
the
time
to
sit
down
with
us
and
and
chat
a
little
bit
about
projects.
We
hope
that
you
have
an
awesome,
awesome
conference
and
we
hope
that
you're
staying
safe
with
your
with
your
respective
loved
ones
and
taking
the
breaks
that
you
need
to
in
this
interesting
time.