►
From YouTube: Keynote: CNCF Projects Update - Constance Caramanolis, KubeCon + CloudNativeCon Europe 2020 Co-Chair
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 Projects Update - Constance Caramanolis, KubeCon + CloudNativeCon Europe 2020 Co-Chair & Principal Software Engineer, Splunk
https://sched.co/ZfB9
A
A
So
it's
been
a
long
time
since
we've
gone
all
together
and
there
has
been
a
lot
of
progress
and
what
we're
going
to
be
talking
about
today
is
just
a
small
subsection
or
a
small
subset
of
all
the
project
updates
that
we
have
so
get
your
hands
ready,
because
several
projects
do
definitely
deserve
a
round
of
applause.
Let's
start
off
with
argo.
A
Argo
is
a
set
of
kubernetes
native
tools
for
running
and
managing
jobs
and
applications
right
to
subscribe
to
the
git
ops
paradigm,
such
as
continuous
delivery
and
progressive
delivery,
and
enables
ml
ops
on
kubernetes.
Now
this
has
been
a
big
year
for
argo.
In
april
2020,
it
became
an
incubation
project.
A
This
is
where
everyone
should
be
applausing
right
and
so
not
only
achieving
this
milestone,
but
it
did
have
a
lot
of
features.
A
lot
of
large
features
that
came
in
it
was
in
the
continuous
delivery
sub
project.
It
released
the
get
ops
engine,
the
gita,
ops,
engine
packages,
core
functionality
into
lightweight
and
reusable
library
within
rollouts.
It
has
several
new
integrations,
okay,
it
roll
out.
I
mean
it
has
integrations
with
istio
nginx,
aws
alb
and
the
smi
for
canary
updates
and
analysis.
A
Now.
What
I
really
like
about
the
next
two
future
updates
is
that
it
isn't.
It
doesn't
come
across
as
a
shiny
new
feature,
but
it
is
very
important
and
we
need
to
give
a
lot
of
recognition
to
those
who
do
you
know.
Sometimes
what
we've
used
the
grunt
word
right,
refactoring
test
codes
working,
it
so
workflows
right
within
the
workflows.
They
rewrote
the
server
and
ui
components.
It's
not
always
a
new
feature,
but
this
is
always
like.
A
This
type
of
work
is
always
important
to
continue
to
continue
to
deliver
a
healthy
code
and
within
the
events
it
refactored
for
simpler
crds
and
improve
the
user
experience.
So
let's
talk
about
spiffy
inspire
right.
It
is,
you
know,
an
open
source
standards
for
security,
identifying
software
systems
in
both
dynamic
and
heterogeneous
environments.
A
Now,
in
june
of
this
year,
spiffy
advanced
from
sandbox
to
incubation,
which
is
you
know,
an
evidence
of
their
growth,
adoption
and
evolution,
but
not
only
that
too,
there
have
been
improvements.
Right,
there's
been
improvements
to
the
client
libraries
onboard
integration,
there's
also
enhancements
of
the
kubernetes,
automated
workflow
registration,
which
makes
it
possible
to
plug
in
spire
as
a
source
identi
of
identity,
either
natively
or
otherwise,
there's
also
federation
support,
which
now
enables
spire
deployments
to
span
the
boundaries
of
service
meshes
and
different
cloud
providers.
A
A
Now
what
has
been
included
in
some
of
these
releases?
One
has
been
automatic,
tls
certificate,
rotation
for
contour
and
envoy.
So
no
longer
do
you
have
to
have
an
alarm
telling
you
to
rotate
your
certificates.
Ten
days
before
five
days
before
three
minutes
before
everything
expires,
those
fire
drills
aren't
fun
to
move
through.
A
Personally,
the
nerdy
part
of
me
really
likes
this,
because
it
can
be
really
difficult
to
set
this
up
on
your
own.
So
it's
really
awesome.
They
added
this
and
also
just
improvement
in
terms
of
like
better
support
for
manipulation
of
the
headers
from
requests
and
response
all
right.
We
all
know
that.
Sometimes
this
isn't
the
way.
However,
their
sent
is
in
the
way
that
we
want
them
to
be
and
so
being
able
to
support,
manipulating
this
after
the
fact
is
really
really
awesome.
A
Give
contour
a
round
of
applause
now
for
our
next
project.
Tick
v
tikvy
is
a
distributed
relational
key
value
database,
but
before
we
talk
about
the
technology
and
the
improvements
there,
let's
talk
about.
The
community
community
has
had
amazing
growth,
it
has
239
core
contributors,
it
has
7
700
stars
and
it
has
just
under
a
thousand
production
users.
A
There's
also
been
several
sigs
created.
This
is
to
better
address
the
needs
within
the
project.
Some
of
the
sticks
that
are
created
were
co-processor
sig
engine
sig,
raf
sig
and
transactions,
but
now,
let's
actually
do
a
little
bit
of
talk
about
the
performance
and
functionality
there
have
been
major
improvements
to
this.
One
has
been
in
the
performance
aspect
has
been
a
unified
thread,
pool
for
storage,
read,
write,
requests
and
co-processor
requests.
A
Another
within
performance
has
been
the
follower
read,
it
provides
strong
consistency,
reads
for
raf
followers
and
then
also
for
functionality,
fast,
backup
and
restore
it's
really
cool
right.
It
allows
distributed
physical
backup
and
restore
from
tick
v
for
large
clusters,
with
tunable
speeds,
and
also
we
can't
forget
about
security
in
the
last
set
of
you
know
this
year,
they've
also
added
transparent
data,
encryption
for
tick
fee,
so
let's
give
them
a
round
of
applause.
A
And
for
our
last
project
jaeger,
so
jager
this
year
turns
five
years
old.
That
is
amazing.
Right
now,
one
thing
that
we
talked
about
that
has
been
talked
about
within
the
air
community.
Earlier
this
year
has
been
embracing
open
telemetry.
There
is
a
really
lovely
blog
post
talking
about
direction,
and
so
these
first
two,
you
know
big
project
updates,
really
highlight
that
dedication
to
the
embracing
of
the
open,
telemetry
project.
So
first
thing
has
been
that
several
jager
backing
components
have
been
recreated
on
top
of
the
open
telemetry
collector.