►
From YouTube: The Road to Interoperability in Cloud Native Continuous Deli... Kara de la Marck & Fatih Degirmenci
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.
The Road to Interoperability in Cloud Native Continuous Delivery - Kara de la Marck, CloudBees & Fatih Degirmenci, Ericsson
The emergence of cloud native has resulted in tremendous advances in enabling organizations to develop new services and make them available to end users. In addition, new paradigms such as Continuous Delivery (CD) allow organisations to do this much faster than before, empowering them to go to market ahead of the competition. Despite its many advantages, the cloud native CD ecosystem has its challenges. This session will discuss issues arising from the lack of interoperability across proliferating cloud native CD technologies. We will look at end user case studies, including existing integration initiatives such as that between Tekton and Jenkins X. However, these initiatives are localised to the projects involved and do not address the challenges holistically. We will highlight the necessity, and greater sustainability, of a holistic approach to interoperability in the CD ecosystem and invite attendees to join community efforts.
A
Hi
all
thanks
for
joining
our
session,
the
road
to
interoperability
in
cloud
native
contouring
studuri.
My
name
is
fartimranji.
I
work
for
ericsson,
software
technology
as
a
developer
based
in
stockholm,
sweden.
I
am
also
co-chair
of
the
continental
foundation,
especially
in
paris
group
interoperability,.
B
Hi
all
I'm
cara
donovak.
I
work
at
cloudbees
with
the
jenkins
chicken
sex,
open
source
projects
and
I'm
co-chair
of
the
continuous
delivery
foundation's
interoperability
sig.
Thank
you
for
joining
our
talk
on
the
road
to
interoperability
in
cloud
native,
continuous
delivery.
In
the
context
of
continuous
delivery.
What
do
we
mean
by
interoperability,
interoperability,
composability
and
extensibility
of
all
terms,
to
describe
the
openness
of
the
system?
That
is
its
ability
to
offer
components
that
can
be
easily
used
by
or
integrated
into
other
systems.
B
However,
integration
and
interoperability,
while
often
used
synonymously,
are
not
the
same
and
have
significant
differences.
Integration
is
generally
understood
as
combining
applications
to
function
together.
These
applications
don't
necessarily
have
common
interfaces
and
often
use
different
data
formats.
B
The
result
is
often
when
engineering
teams
need
to
have
these
applications
work
together.
They
write
glucose
and
these
custom
solutions
have
maintenance
costs.
In
addition,
services
can
become
tightly
coupled
and
it
can
be
a
significant
engineering
effort
to
later
replace
one
of
the
applications
for
something
else.
B
Interoperability,
on
the
other
hand,
focuses
on
open
interfaces
and
standardized
metadata
that
enable
controlled
and
defined
access
to
services
or
information
from
a
different
application
or
system.
Let's
consider
interfaces
as
an
example
of
an
abstraction
which
enables
interoperability
if
the
interface
is
well
specified
and
openly
available.
Multiple
service
providers
can
implement
the
service
and
enable
customers
to
consume
the
service
in
a
known
way
using
the
defined
interface.
B
This
provides
a
number
of
practical
advantages.
For
example,
if
client
a
consumes
a
service,
by
b
through
a
well-defined
interface,
a
could
switch
to
c's
implementation
of
the
same
service,
which
uses
the
same
interface
and
a
should
not
experience
any
failures.
How
b
or
c
implement
the
service
is
not
relevant
to
a,
which
is
only
concerned
with
the
specifications
of
the
interface.
B
B
B
B
B
B
So
let's
look
more
closely
at
interoperability
within
the
cicd
context.
First
pipeline
standardization
and
or
standardization
in
pipeline
languages.
The
goal
here
is
to
have
the
ability
to
migrate
or
run
pipelines
created
on
one
tool
on
another
one,
as
is
next
the
ability
to
connect
pipelines
running
on
different
tools
in
a
standardized
way
and
pipeline
data
for
traceability
or
visualization.
B
The
goal
is
to
propagate
data
from
cicd
tools,
in
a
way
that
external
tools
can
consume.
Regardless
of
what
cicd
tool
created
that
data,
we
will
look
at
two
open
source
projects
that
help
you
gain
more
visibility
into
your
ci
cd
system
and
consider
the
work
that
they
are
doing
to
map
the
different
data
formats
of
different
tools
and
how
greater
interoperability
could
help
for
ci
cd
events.
We
defined
an
event
following
the
cloud
events.
Definition
has
a
data
record
expressing
an
occurrence
and
its
context.
B
The
common
theme
across
the
different
perspectives
is
data
and
exchanging
data
across
various
tools
that
may
be
employed
by
an
organization
as
part
of
their
cicd
pipelines.
The
data
could
either
be
in
the
form
of
pipeline
definitions,
consumed
by
pipelines
as
input
or
produced
by
pipelines
as
output.
This
means
that
the
definition
of
interoperability
in
the
cicd
domain
is
similar
to
how
it
is
defined
in
other
domains.
It's
all
about
the
data
and
exchanging
data
among
the
activities
of
the
inter
interoperability
sig.
B
We
look
at
existing
case
studies
such
as
how
jenkins
x
incorporates
tecton
as
its
pipeline
engine
to
help
users
build
and
deliver
software
using
the
cloud
well
xingx
helps
you
manage
the
lifecycle
of
your
application,
including
continuous
delivery
on
kubernetes
chingasex
uses
tekton
for
standardized
declarative
pipeline
apis
and
build
execution
when
users
install
jenkins
extecton
is
also
installed
into
the
kubernetes
cluster
when
users
create
new
applications
or
import
existing
ones.
Shinkansen
will
automatically
add
pipeline
as
code
tucked
on
resources
to
the
git
repository
alongside
the
source
code
and
configure
web
book
handling
for
git
events.
B
The
techcloud
pipeline
resources
that
are
added
come
from
a
base
set
of
reusable
pipelines
that
live
in
the
jingenzex
pipeline
catalog.
The
jing
insects
project
essentially
aligns
its
pipeline
definitions
with
tecton
and
make
it
makes
it
super
easy
for
any
test
from
the
textile
catalog
and
to
be
used
inside
a
chaincontext
created
pipeline.
B
B
B
So
reducing
complexly
greatly
improves
the
maintainability
of
software.
Thus,
simplicity
is
a
key
goal
for
any
system
and
making
a
system
simpler
does
not
necessarily
mean
reducing
its
functionality.
It
can
mean
removing
the
complexity
that
is
created
when
you
are
implementing
the
solution
that
you
are
trying
to
solve
by
reducing
the
need
for
application
blue
code.
Interoperability
helps
make
your
system
simpler.
B
It
also
reduces
type
coupling
in
the
system
again
makes
making
your
system
much
more
maintainable.
It
is
likely
that
the
ci
cd
systems
requirements
will
change.
There
could
be
legal
or
regulatory
requirements
that
change
versus
the
growth
of
your
system
or
for
some
changes,
and
new
tools
will
emerge
that
you'd
like
to
incorporate
the
ease
with
that.
You
can
modify
a
system
and
adapt
it
to
changing.
B
This
increase
visibility
into
your
system
can
help
with
investigating
failures
and
finding
and
fixing
bugs
good
operability
means
having
good
visibility
into
your
system's
health
and
having
effective
ways
of
managing
it.
We're
going
to
look
at
two
really
interesting,
open
source
projects
that
can
help
you
gain
more
visibility
into
your
cicv
system.
B
B
One
of
the
challenges
of
gathering
these
dual
metrics
is
that
the
deployment
change
and
incident
data
are
usually
in
disparate
systems,
so
for
the
four
keys
solution
was
to
create
a
generalized
pipeline
that
can
be
extended
to
process
inputs
from
a
wide
variety
of
sources
before
keys
project
in
effect,
creates
a
mapping
between
events
in
different
pipelines
and
tools.
In
order
to
be
able
to
generalize
the
data
it
receives.
B
Standardized
metadata
of
events
in
ci
cd
pipelines
would
enable
much
greater
interoperability
between
tools
and
platforms
and
more
consistent
data
to
be
used
for
analysis.
So
now
we'll
look
at
jing,
it's
like
cd
indicators,
so
this
add-on
to
the
django
text,
ci
cd
platform,
helps
you
gain
visibility
into
your
ci
cd
system.
B
These
insights
are
based
on
the
durametrics
and
the
space
framework.
The
metrics
are
generated
using
git
events,
as
with
the
four
keys
project.
In
addition,
jenkins
x
has
a
kubernetes
custom
resource
definition,
forging
insect
specific
type
called
the
pipeline
activity,
a
kubernetes
controller
watches
the
kubernetes
api
server
for
these
custom
pipeline
activity.
Events,
the
two
main
types
of
event,
data
so
get
events
and
cluster
events
are
kind
of
mapped
together
and
combined
to
create
the
metrics
displayed
in
the
graffama
dashboards,
which
is
an
example
on
the
slide.
B
But
this
mapping
for
now
happens
within
the
context
of
one
cicd
project
jenkins
x
and
not
across
multiple
projects
or
tools.
Here's
a
different
mapping
to
that
done
by
the
four
keys
project
using
different
data
inputs,
but
note
that
this
mapping
work
between
differing
data
formats
needs
to
be
done
by
both
of
these
projects,
so
the
tools
and
technologies
that
are
used
to
construct,
ci
cd
pipelines
and
the
pipelines
themselves
produce
a
lot
of
data
organizations
will
collect,
store
and
use
this
data
in
various
ways
to
get
value
out
of
it.
B
B
B
In
addition,
how
such
metadata
could
be
consumed
and
produced
is
another
topic.
This
is
being
looked
at
within
the
continuous
delivery
foundation's
event.
Sec
fatima's
nut
will
not
speak
more
about
the
work
we
are
doing
within
the
interoperability
sig
and
within
the
wider,
continuous
delivery
foundation.
Community.
A
Thank
you,
tara.
I
would
like
to
start
talking
about
continues
there
foundation,
which
is
a
sister
comment
to
cloud
native
concreting
foundation.
As
we
all
know,
there
are
many
great
technologies
out
there.
One
can
use
to
help
construct
pipelines
and
establish
cloud-native
countries
to
derive
in
their
organizations.
A
However,
there
is
not
without
challenges,
and
one
of
the
challenges
is
the
fragmentation
within
the
cicd
domain.
It
is
challenging
to
adopt
use,
integrate
and
contribute
to
various
crc
technologies.
Here
continuous
data
foundation
comes
to
the
rescue
continues.
Foundation
was
founded
during
march
2019,
hosted
by
new
york's
foundation,
providing
neutral
home
to
cultivate
for
the
next
generation
of
continuous
federation.
A
There
are
various
ways
continues.
Their
foundation
enables
this.
First
and
foremost,
it
provides
home
to
various
open
source
ci
cd
projects
such
as
jenkins,
jenkins,
x,
chemical
pecton
driver,
cd
and
orterius,
in
addition
to
hosting
projects.
It
also
welcomes
the
creation
of
special
interest
groups
and
working
groups
for
community
members
to
come
and
tolerate
on
various
topics
within
cloud
native
contents
delivery.
A
A
Four
topics
I
would
like
to
highlight
during
this
talk
are
shared
vocabulary,
standardized
metadata
events
and
policy.
As
you
notice,
these
topics
are
pretty
disconnected
from
each
other.
It
was
similar
for
us
as
well.
However,
when
we
started
diving
into
the
topic
of
interoperability
and
get
into
the
details,
we
began
realizing
that
the
problem
is
much
bigger
than
just
how
to
get
cic
technologies
interoperate
with
each
other,
with
well-defined
interfaces
or
by
standardized
approach.
A
Let
us
start
with
shared
vocabulary:
special
interest
group
interval
ability
was
approved
during
january
2020
by
continuous
data
foundation,
taking
oversight
community.
So
we
are
a
little
bit
older
than
one
year
we
were
very
eager
to
get
hands-on
with
the
technologies
we
are
using
and
working
with.
However,
we
started
noticing
that,
even
though
everyone
knows
what
continuous
integration,
compensatory
and
continuous
deployment
are,
the
terms
we
use
to
communicate
with
each
other
as
humans
differ
apart
from
that
counts,
used
by
different
cic
technologies.
A
To
describe
the
same
thing
differ
as
well
contributing
to
the
challenges
with
human
communication,
for
example,
we
identified
three
different
terms
are
used
by
various
technologies
when
they
talk
about
pipelines,
workflow
activity
well
hyphen,
as
you
can
guess,
these
impacts
are
able
to
communicate
with
each
other.
Since,
if
I
am
using
a
certain
technology,
I
naturally
use
the
timelapse
of
the
tool
during.
B
A
A
A
This
helped
us
a
lot
since
we
can
now
have
an
easy
way
to
look
at
the
terms
we
don't
know
and
see
what
they
mean
for
us
using
different
terms.
We
call
this
document
project
a
stone
for
cicd
and
currently
has
terms
for
14
cicd
projects.
In
addition
to
cit
technologies.
We
include
current
source
software
configuration
management
tools
such
as
credit,
github
and
gitlab.
A
This
is
a
community
maintained
document
and
we
welcome
contributions.
So
please
check
it
out.
Are
we
done
with
this?
Definitely
not,
since
this
topic
is
relevant
to
modern
interoperability
area.
This
topic
is
continued
to
work
by
special
interest
group
best
practices.
So
they
look
at
what
certain
term
was
first
time
described,
suggest
complete
integration
continuously
continues,
devops
will
define
the
term
first
time
and
what
it
went
through
over
the
years.
A
The
next
topic
I
want
to
discuss
is
standard
lighting
data,
the
cic
tools
and
technologies
that
are
used
to
contract,
cicd
pipelines
and
pipeline
stem
cells,
produce
lots
of
data.
We
as
users
collect
store,
use
and
analyze
this
data
in
various
ways
to
get
value
out
of
it.
There
are
two
questions
we
are
looking
answers
from
the
later.
A
A
We
are
currently
documenting
the
types
of
metadata
we
produce
and
consume,
starting
with
commit
and
artifact
data.
In
addition
to
this,
as
I
noted
earlier,
we
are
not
after
creating
our
own
team,
so
we
are
also
talking
with
various
communities
to
learn
more
about
what
they
are
doing,
see
the
overlaps
gaps
and
explore
collaboration
opportunities.
A
We
recently
start
collaboration
with
spdx
community,
since
we
know
that
they
also
work
on
some
of
these
topics
within
the
data.
I
realized.
I
didn't
talk
about
our
question
for
the
metadata,
how
the
metadata
is
produced
and
how
it
is
concerned-
and
this
is
on
purpose,
since
one
of
the
continental
foundations
special
interest
groups,
especially
in
periscope
events,
is
looking
after
this
explore.
The
use
of
events
in
cicd.
A
A
A
This
special
trace
group
is
looking
at
how
events
can
help
create
ci
cd
systems
with
a
decoupled
architecture
that
is
easy
to
scale
and
makes
it
resilient
to
failures.
Using
events
could
also
increase
automation
when
connecting
workflows
from
different
systems
to
each
other.
As
a
result,
empowering
tracing
visualizing
auditing
of
the
connected
workflow
to
these
events
point
members
from
various
open
source
projects
take
part
in
special
interest
group
events
bringing
their
perspectives
out
and
ideas
to
the
groups.
Some
of
these
communities
are
from
within
continuous
foundation
such
as
spinker
jenkins,
hoteliers.
A
A
A
A
Apart
from
that,
there
are
other
policies
and
security
policies
such
as
business
policies.
These
publicly
also
need
to
be
looked
further,
as
watched
earlier.
This
discussion
started
within
special
interest
of
intervality
recently
and
we
will
reach
out
to
various
projects
that
are
actively
working
policy
working
on
policy
topic
before
this
agent,
not
a
network
automation,
platform,
voice
framework.
A
A
Until
now,
we
talked
about
projects
and
communities,
but
what
about
home
users?
So
I've
touched
the
end
user
aspects
of
content.
Instigation
continuously
as
well,
I
am
from
an
end
user
organization
and
it
is
important
for
my
organization
to
keep
itself
connected
to
the
ecosystem
and
contribute
to
the
projects
we
are
using.
This
can't
happen
without
active
involvement
and
collaboration
within
open
source,
where
we
can
take
part
in
the
discussions
with
communities
which
will
impact
how
our
organizations
utilizing
these
technologies
as
part
of
their
continuous
level
journey.
A
Apart
from
joining
and
collaborating
within
the
communities,
it
is
also
important
to
highlight
our
needs,
use
cases
and
challenges
to
the
projects
from
end
users,
perspectives,
confidence,
data
foundation
and
user
concept
provides
such
an
opportunity
and
allows
end-user
organizations
to
take
part
in
the
discussions
and
user
concert
recently
published.
It
is
2021
planned
based
on
the
input
from
end
users.
The
topic
the
group
planned
to
work
on
during
2021
are
measuring,
develop
success,
developer
productivity
and
experience,
colombian
technology
choices
on
governance
and
compliance.
A
As
you
can
notice,
all
these
topics
have
relations
to
interoperability
in
one
way
or
the
other.
For
example,
measuring
devops
success
require
organizations
to
collect
key
metrics
to
evaluate
delivery
performance.
It
is
very
difficult
to
achieve
that
since
the
tools
that
is
used
by
organizations,
whether
scm
or
ci
cd,
they
all
expose
these
metrics
in
different
ways.
A
Finally,
few
words
about
future,
which
is
what
I
try
to
summarize
during
discussions
about
key
topics.
We
work
with
various
topics
within
various
special
terrorist
groups.
As
you
can
see
here,
the
three
countries,
the
referendum
foundation,
sufficient
groups,
looks
at
various
topics
as
and
will
continue
to
study
them.
We
would
like
to
contribute
cloud
native
contents,
theory
domain
in
various
ways:
white
papers,
case
studies,
best
practices,
specifications
and
recurrence
representations
and
so
on.
A
In
addition
to
working
with
these
topics
within
our
community,
we
will
either
continue
collaborating
with
other
communities
such
as
cncf,
spdx
and
financial
networking,
and
so
on,
or
look
for
new
collaboration
opportunities.
It
is
critical
that
we,
as
sister
communities,
work
on
this,
like
a
single
community,
to
tackle
these
challenges
and
collaboratively.
B
B
We
believe
that
cross
collaboration
and
pollination
across
communities
and
industries
is
key
to
addressing
challenges,
because
these
bring
diverse
perspectives
that
enable
us
to
develop
better
solutions
together.
Please
you
join
us
in
the
continuous
delivery
foundation's
interoperability's
sake.
There
are
links
in
the
slides
on
how
to
find
out
more
about
the
interoperability
sig
and
the
continuous
delivery
foundation.