►
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
They
will
build
things,
they
will
break
things
and
they
will
answer
all
of
your
questions,
so
you
can
join
us
every
Wednesday
to
watch
live,
and
this
week
we
have
Thomas
here
to
talk
with
us
about
solving
conflict
drifts
across
environments
with
score
very
exciting,
and
today
we're
going
to
take
questions
and
intervals
along
with
the
presentation
so
and
and
the
demo.
A
So
whenever
you
feel
like
asking
a
question
just
pop
it
into
the
chat
and
we're
going
to
get
to
it,
when
we
have
a
nice
spot
within
the
presentation
or
demo
where
we
can
have
like
a
discussion
about
it,
a
bit
perfect
and
as
always,
this
is
an
official
live
stream
of
the
cncf
Alexa.
As
such,
it
is
subject
to
the
cncf
code
of
conduct,
so
please
do
not
add
anything
to
the
chat
or
questions
that
would
be
violation
of
that
code
of
conduct.
A
Basically,
please
be
respectful
of
all
of
your
fellow
participants
as
well
as
centers
and
I'll
hand
it
over
to
Thomas
right
now
to
kick
off
today's
presentation.
B
Thank
you
very
much.
Thank
you
very
much.
I'm
excited
to
be
speaking
here
today,
so
I'm
going
to
show
a
couple
of
slides
and
then
I'm
going
to
go
on
to
the
the
more
interesting
stuff
which
is
the
demonstration
okay.
So
let's
get
going.
B
One
spec
to
rule
them
all:
okay,
so
yeah
I'm,
I'm,
Thomas,
Harris
I
work
as
a
customer
success
engineer.
B
But
today,
I'm
going
to
be
speaking
about
open
source
project
that
I'm
involved
with
called
score.
Okay,
so
score
is
built
by
Developers
for
developers
and
aiming
to
improve
the
developer
experience.
B
Ultimately,
it
is
looking
at
providing
a
single
source
of
Truth
on
how
a
workload
should
be
run
on
any
container
orchestration
platform,
whether
that
be
Docker
compose,
whether
that
be
kubernetes,
whether
that
be
using
tooling,
like
Helm
to
deploy
to
kubernetes,
or
maybe,
if
you're,
using
a
bespoke
platform
API,
which
is
now
becoming
more
common
okay.
B
So,
let's
take
a
step
back
and
look
at
the
problems
that
or
some
of
the
problems
that
score
is
trying
to
solve.
Okay,
the
first
one
is
cognitive
load.
Now
cognitive
load
is
a
a
wide
subject
and
within
this
we're
specifically
looking
at
context,
switching
okay,
so
developers,
switching
between
different
tools,
different
workflows,
creates
high
cognitive
load
and
impacts
their
daily
work
say
noticeable
problem
within
the
you
know,
within
the
environment.
B
The
second
is
inconsistency
between
environments,
okay,
so
if
I'm
developing
locally
I'm
using
something
like
Docker
compose
to
verify
my
workload
once
I'm
happy
with
that,
I
need
to
then
go
and
deploy
it
to
a
production
system.
I
may
be
using
Helm
to
deploy
to
kubernetes
I
may
be
deploy
into
ECS,
Google
Cloud
run.
B
This,
then
creates
inconsistencies
between
environments.
You
get
this
sort
of
convict
drift
and
problems
with
replicating
the
workload
from
local
development
to
production,
development
and
then
another
problem
is
infrastructure.
Management
yeah
I
have
not
spoke
to
any
developers
who
actually
want
to
manage
infrastructure.
Okay,
they
need
infrastructure,
it's
sort
of
a
necessity
to
run
their
workloads,
but
actually
managing
that
infrastructure
really
requires.
You
know
specific
knowledge
around
Cloud
providers
around.
B
You
know
Cloud
architecture
design
and
it
again
it
also
creates
cognitive
load
when
we
have
to
think
about
management
infrastructure,
so
score
promotes
what
we
are
calling
a
workload:
Centric
development
type
of
development,
okay
versus
infrastructure-centric
development,
which
is
pretty
common
today,.
B
So
what
what
score
is
looking
to
do
and
what
we're
moving
towards
is
providing
a
single
source
of
Truth
for
your
workload,
so
it
being
the
definitive
reference
on
how
a
workload
should
be
run
regardless
of
environment
regardless
of
platform.
B
A
B
B
B
We
only
released
publicly
in
November
just
at
the
start
of
November,
so
we
have
a
couple
of
implementations.
One
of
those
is
Docker
compose.
One
of
those
is
helm,
okay
and
it's
very
extensible,
so
the
community
are
able
to
write
specific
implementations
for
their
platform,
whether
that
be
you
know,
implementations
that
are
available
on
the
public,
Cloud
providers
or
specific
platform.
Specific
implementations
for
your
own
custom
platform,
API.
B
A
So
far,
but
looking
forward
to
those,
so
if
anyone
has
any
questions,
you
can
send
them
in.
B
Oh
Google,
so
before
I
dive
straight
in,
let
me
give
a
sort
of
a
brief
scenario.
So
I've
been
developing
locally
I've
built
a
Docker
image,
a
container
image
I've
tested
that
locally
I'm
happy
with
it
now.
I
need
to
run
that
on
a
more
production
grade
infrastructure,
so
I
could
be
using
off
of
Docker
locally
here,
as
you
can
see,
I've
got
nothing
running
yet
we'll
get
to
that,
and
then
my
production
infrastructure
could
be
something
like
gke
Okay.
So.
B
Developer
I
need
to
understand
the
implementation
of
Docker
compose
right,
Docker
compose
files
when
I
want
to
transfer
that
workflow
to
a
production
grade.
Infrastructure
I
also
have
to
understand
how
to
write
Helm
files
as
an
example
and,
as
you
know,
an
organization
that
I
work
for
uses
more
Technologies,
maybe
a
platform
specific
API
I
I
have
to
understand
how
to
run
that
workload
on
those
different
platforms.
B
So
what
score
is
doing
is
having
a
single
specification
that
can
translate
to
any
of
those
platforms
Okay.
So,
let's
take
a
quick
look
at
a
an
example
score
file,
and
this
is
a
very
an
example
that
just
uses
a
simple
image:
Okay.
So,
okay,
it's
just
for
demonstration
purposes.
But
let's,
let's
take
a
closer
look
at
this
file.
B
And
pretty
standard
nowadays
as
well
and
then
I
am
giving
it
a
name
given
the
workload,
a
name
specifying
a
container
or
a
group
of
containers
and
a
specific
image:
okay,
so
author
yeah
so
far
so
good
supplier,
some
commands
line
arguments
to
the
workload.
This
is
just
something
that
keeps
our
workflow
running
in
this
instance.
Okay,
then,
this
is
where
the
point
where
it
gets
more
interesting
right.
This
is
just
a
definition
of
I
need
to
run
this
container
image.
B
If
you
flip
down
to
this
sort
of
resources,
piece
from
line
13
and
look
at
sort
of
line,
20
that
says
DB,
okay,
so
database,
but
rather
than
me
worrying
about
the
specific
implementation
of
that
database
or
where
that
database
runs,
whether
that
be
running
as
a
local
container
if
I'm
developing
locally
or
whether
that
runs
as
a
full-blown
service
on
Google
clouds
under
Cloud,
SQL
I'm,
not
worried
about
that
implementation.
I
just
need
an
endpoint
that
is
a
postgres
database,
so
I
just
declare
database
and
type
postgres.
B
B
A
Need
to
we
get
zoom
in
a
bit.
There's
someone
who's
wanting
to
see
a
bit
closer.
B
Okay
I
can
it
makes
it
interesting
to
look
at
is
that
okay.
B
So
what
we're
actually
doing,
rather
than
explicitly
declaring
the
connection
string,
we're
just
putting
a
placeholder,
so
we're
saying
we're
referring
to
the
actual
database,
and
these
will
be
resolved
when
the
workload
actually
gets
deployed
on
the
relevant
platform.
Okay.
So
this
is
something
that
is
part
of
the
platform
engineering
ideology
which
we
are
calling
Dynamic
configuration
management.
B
B
B
B
So
the
first
thing
I
need
to
do
is
translate
the
files
to
something
that
is
platform
specific,
so
I'm
going
to
translate
this
back-end
file
I'm
just
going
to
copy
and
paste
this
now.
Oh
I
literally
need
to
be
in
the
correct
directory
to
do
this.
B
Okay,
so
I've
translated
that
trial,
I've
outputted
it
to
a
specific,
a
platform
specific
file.
That's
the
that's!
The
back
end
I've
also
got
a
front
end
that
is
similar
to
simulate.
You
know
a
production
type
workload
I've
got
these
two
files.
We
take
a
look
at
those
a
bit
closer.
You
can
now
see
that
I've
got
these
two
files,
I've
got
a
back-end
compose
and
front-end
compose
okay,
so
the
back
end
compos
is
translating
the
score
spec
to
the
the
the
docker
specification.
B
B
Now,
I
actually
need
to
bring
the
workload
up
if
you're
wondering
how
the
database
is
going
to
be
brought
up.
Typically,
you
know
in
production
environments
that
is
down
to
a
platform
team
to
implement.
In
this
instance,
I've
just
run
in
a
database
locally,
which
is
fine
for
a
developer.
You
know
just
bring
up
a
local
database
when
we
move
into
production,
it
becomes
more
difficult
for
them
to
Define
that
it's
something
that
a
platform
team
would
implement.
B
Okay,
so
I'm
going
to
run
the
DB
just
as
a
compose
file,
the
the
back
end,
which
I
showed
you
and
and
the
front
end
as
well.
Okay,.
B
B
If
we
look
at
the
bottom,
I
know
there's
a
lot
going
on
here,
but
these
are
just
the
sort
of
the
logs
from
bring
these
workers
up.
We
can
see.
We've
got
this
hey
Jimmy
connecting
to
the
database
and
we've
actually
resolved
the
connection
string
Okay.
So
we've
got
a
front
end
a
back
end
and
we
resolving
the
connection
string.
So
we
can
speak
to
the
database.
B
B
B
B
B
B
I
can
see
that
I
have
these
pods
running
okay
and
if
I
just
tell
the
logs
as
well,
we
can
see
the
connection
string
so
there
we
are
so
in
the
same
way
that
I
deployed
my
workload
before
I
used
the
initial
score
spec,
which
is
here-
oh
sorry,
she's,
not
there,
which
is
here
just
the
back.
End
example:
I
deployed
this
workload
to
Docker
compose
and
then
I
deployed
to
kubernetes
using
the
same
file
and
I've
got
the
same
outcome
right.
B
I've
got
this
workload
running,
it's
speaking
to
the
front
end,
it's
speaking
to
the
back
end.
They
can.
They
can
communicate
to
each
other
and
we
can
speak
to
the
database.
And
if
we
look
at
the
connection
string
that
we've
echoed
out,
we
can
see
that
it
has
been
resolved.
The
inputs
have
been
passed
in
and
everything
is
successful.
B
B
So
this
is
just
a
simple
example
right
there
there
may
be
other
tooling
out
there
that
can
translate
from
to
duckling
pose
and
drums
link
to
helm
in
a
single
file,
and
but
what
we
are
looking
at
really
here
and
the
vision
is
to
support
the
platform,
engineering
ideology,
the
ability
for
platform
Engineers
to
Define
resources
to
best
practice
or,
as
some
may
call
Golden
paths
and
for
developers
to
take
a
a
workload-centric
view
of
their
development,
which
means
that
they
can
concentrate
on
writing
code,
pushing
that
code
to
an
environment
and
then
that
same
specification
being
consistent
across
all
environments.
B
B
So
in
future
we're
looking
at
many
different
implementations,
we
have
a
very
sort
of
strong
implementation
system
where
the
community
are
able
to
write
their
own
plugins,
so
we're
really
excited
about
the
future
of
score
and
how
that's
going
to
help
developers
improve
their
experience
in
their
day-to-day
work.
A
There
was
a
question
which
was
the
score:
have
a
GitHub
repo.
B
It
does
indeed,
yes,
yes,
I
shall
post
it
in
the
in
the
chat
on
second.
A
B
I
think
this
is
just
private
to
yourself,
but
so
there's
the
score.dev
website
and
then
I
will
bring
up
the
repo
as
well.
B
We
go
so
there's
there's
the
actual
specific
repository
that
relates
to
the
spec
and
if
you
look
a
step
back
in
that
repository,
you'll
find
the
specific
implementations
that
we've
developed
so
far.
A
Yeah
so
there
we
have
put
it
in
the
chat
and
then
there's
a
question.
How
do
you
compare
config
drift
between
two
environments.
B
If
I
understand
the
question
correctly,
convict
drift
happens
when
a
developer
uses
one
type
of
platform
or
technology
to
deploy
their
workload
and
then
when
they
need
to
deploy
to
another
type
of
platform,
they
need
to
redefine
that
workload.
Okay,
so
they
need
to
resolve
and
understand
the
differences
between
the
two
specifications
or
the
platform
specific
implementation,
and
they
probably
have
the
best
interests
at
heart,
but
naturally
understanding
many
different
platforms.
B
Many
different
specifications
means
that
the
the
config
becomes
different
between
those
environments
and
there's
also
the
point
of
updating
the
config
as
well.
If
I
make
a
change
to
one
environment,
I
need
to
represent
that
in
the
other
environment.
So
what
score
is
aiming
to
do
and
yeah,
and
it's
actually
achieving
in
this
demo,
as
we've
seen,
is
creating
a
single
specification
that
is
consistent
across
those
environments.
A
Yeah
great
perfect,
to
ask
your
readout:
if
you
have
any
any
extra
questions,
just
send
them
in
and
we
can
get
answers
about
them
as
well.
Yeah
did
you
have
anything
else
you
wanted
to
show
as
far
as
the
demo
goes
or
anything
there.
B
I,
don't
have
anything
specific
today,
but
what
I
will
say
is
that
we
we
are
going
to
share
the
link
to
the
sandbox
environment.
B
That
I
just
showed
there
to
give
viewers
access
will
only
be
available
for
about
a
week
at
the
moment,
so
we're
going
to
keep
that
up.
Let
people
play
with
it
if
they're
interested
and
we're
happy
to
take
feedback.
So
please
either
you
know
reach
out.
B
A
Perfect
should
I
share
the
link.
Now,
absolutely
there
we
go
I'm
sharing
to
people
here
as
well,
so
they
can
see
a
good
industry
as
well,
so
people
can
go
there
and
play
around
themselves
and
was
available
for
about
a
week.
A
Yeah,
perfect,
and
so,
if
they
want
to
reach
out
with
questions,
do
you
have
like
a
slack
channel
that
people
can
join
or
should
they
reach
out
in
the
cncf
slack
or
with.
B
Or
we
do
so
there's
a
specific
slack
Community
dedicated
to
the
score,
so
I
will
just
find
that
I'm
not
prepared
to
share
that,
but
I
will
find
it
right
now.
B
B
A
The
first,
the
simple
one,
is:
if
someone's
now
super
excited
to
learn
more
about
the
topic
and
they're
gonna
do
hopefully
some
playing
around
with
the
environment
and
everything.
What
should
do
they
after
that,
like?
What's
the
next
step?
What
should
they
be
learning
if
they
want
to
do
even
more
of
a
deep
dive
into
the
topic?
What
do
you
do?
You
have
any
recommendations.
A
B
The
first
I
say
the
first
thing
is:
tell
us
your
experience
on
the
score.
Slack
Community
tell
us
what
you
need
to
learn.
You
know
what
what
you'd
like
to
know
more
we'd
be
happy
to
provide
like
many
more
materials
on
platform
Engineering
in
general
and
some
guidance
on
on
where
to
go
next.
Okay,.
A
Perfect
so
very
customized
approach,
I
love
it
so
yeah
sounds
good
and
then
the
one
thing
that
I'm
always
interested
in
so
what's
going
to
be,
do
you
think,
do
you
have
any
sneak
peeks
or
any
kind
of
anything
you
can
share
about
the
future
of
score?
Is
there
anything
coming
up
in
the
future?
What's
in
the
roadmap.
B
So
we
have
a
very
clearly
defined
Vision,
okay,
so
that
vision
is
to
provide
this
sort
of
single
workload
specification,
that's
consistent
across
platforms
and
solving
problems
that
you
know
we
set
out
at
the
start
of
the
presentation.
Okay,
so
that's
that's
the
vision!
There
are
a
few
implementations
on
the
sort
of
internal
roadmap
that
we're
speaking
of,
and
that
really
would
be
interesting
to
hear
from
The
Wider
Community.
What
implementations
are
important
to
them,
which
platforms
are
they
using
most
where
their
pain
points
are
and
yeah?
A
Perfect
so
clearly,
I
guess
the
the
slack
Community
is
the
place
to
be
to
discuss
and
then
take
things
further
and
really
kind
of
see
where
the
future
takes
score
as
well.
It's
perfect
and
since
I
don't
think,
there's
any
new
questions
coming
in,
so
we
can
start
wrapping
up
soon.
So
Thomas
do
you
have
any
final
words
or
anything
that
you
want
to
kind
of
finish
off
as
well.
No.
B
I
don't
know
just
thank
you
for
the
people
that
have
joined
really
appreciate
you
taking
your
time
out
of
your
busy
days
and
yeah
if
you've
got
the
chance
test,
the
the
Hands-On
sandbox
environment
and
and
reach
out.
A
Perfect-
and
here
is
the
sandbox
environment
link
again,
if
you
didn't
catch
it
the
first
time
any
days
are
also
in
the
chat
as
well.
Well.
Perfect,
thank
you
so
much
for
coming
in
and
doing
such
a
great
demo
and
and
really
being
very
Community
minded
and
getting
started
with
discussions
with
everyone.
That's
always
lovely
to
see,
but
thank
you.
Everyone
for
joining
the
latest
episode
of
cloud
native
live.
A
It
was
great
to
have
a
session
about
solving
conflict
drift
across
environments
with
score,
really
love
the
new
questions
that
we
got
from
the
audience
as
well
and
I
hope
everyone
jumps
in
and
tries
out
the
environment
and
next
week
as
well
in
the
coming
weeks,
we
would
have
great
sessions
coming
up,
but
we
have
a
bit
of
a
holiday
break
now
coming
up
with
Cloud
native
life,
but
we
will
be
back
in
January
with
more
great
sessions
coming
up
so
stay
tuned.
For
those.
A
Thank
you
for
joining
us
today
and
see
you
in
the
next
Cloud
native
life.