►
From YouTube: CNCF End User Lounge: Societe Generale
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
C
A
Cnc
end
result
where
we
explore
how
cognitive
technologies
are
adopted
by
end
user
organizations
across
different
industries
and
sectors.
The
end
user
community
is
formed
of
more
than
160
vendor
neutral
companies
that
use
the
open
source
software
to
deliver
their
product.
I
am
a
worker,
centric
angle,
a
cncf
ambassador,
and
today
with
me,
I
have
lauren
fabian
and
carfloran
as
guest
speakers
in
this
live
stream.
We
bring
end
user
members
to
showcase
how
the
organization
advocates
the
cloud
native
ecosystem
to
build
and
distribute
their
services
and
products
join
us
every
fourth
thursday
at
9
a.m.
A
Pacific
time
now
this
is
an
official
live
stream
of
the
cmcf
and
as
such
it's
subjected
to
the
cncf
code
of
conduct.
Please
do
not
add
anything
to
the
chat
or
questions
that
will
be
in
violation
of
the
code
of
conduct.
Basically,
we
are
saying,
please
be
respectful
to
all
the
fellow
participants
and
presenters.
If
you
have
any
questions
for
us
will
be
monitoring
them
through
our
live
stream.
Make
sure
to
ask
your
questions
the
live
chat.
A
Before
we
dive
into
the
christians,
I
forgot
what
I
just
learned:
lauren
have
friends,
can
you
briefly
introduce
yourself
please.
C
So
my
name
is
florence:
I
am
a
cloud
engineer
at
society
general,
so
we
are
one
of
the
principal
european
financial
services
group
present
in
more
than
50
countries,
and
so
I'm
specifically
in
the
future
team
in
charge
of
orchestrated
containers
the
offer
that
is
mainly
based
on
the
cognitive
products.
Today
you
know
infrastructure
services.
A
C
Okay,
so
I
can
start
and
certainly
alone,
will
add
some
interesting
points,
so
we
are
quite
an
old
company.
We
are
a
bank
that
is
a
157
years
old.
So
it's
a
quite
huge
group.
As
I
mentioned,
we
are
present
in
61
company
countries,
I
just
checked,
and
so
we
have
a
longer
iit
journey
behind
us
and
also,
of
course,
in
front
of
us.
So
as
most
companies,
we
have
what
we
call
traditional
systems.
C
You
know
with
a
physical
servers
mainframe,
of
course,
physical
network
data
centers,
and
we
are
for
some
years
now.
We
are
in
a
transformation
journey,
so
we
are
going
to
to
the
cloud.
We
have
an
official
target
of
80
percent
of
workload
in
club
and
we
have
a
hip
breath
cloud
strategies.
C
So
by
hybrid
I
mean
that
we
we
use
a
public
cloud
and
also
a
private
cloud
and
so
to
so
laura
and
I
we
are
more
focused
on
the
private
part
of
the
of
the
cloud,
and
today
we
can
share
about
what
we
do
with
containers
privately.
B
Just
maybe
a
small
scale
value
we
are.
We
have
clusters
in
three
regions:
amer
europe
and
asia.
Okay,
so
we
are,
we
are
doing
a
24
7
run
on
the
on
the
clusters
and
we
have
thousands
now
of
containers
running
in
production.
A
B
So
it
was
a
very
small
offer
to
to
to
put
a
foot
in
in
the
cloud
world,
in
fact,
and
and
then
to
propose
to
to
clients
a
new,
a
new
way
to
develop
and
to
be
more
agile
on
the
development
part
and
and
be
more
focused
on
the
time
to
market
help
them
to
to
deliver
more
quickly.
That
was
the
first
step.
Yeah
awesome.
A
Yeah
and
what
other
technologies
do
you
have
in
your
stack
or
component
aside
communities.
C
So
the
core
of
our
current
offer
is
based
on
myranthy's
distribution.
So,
as
man
as
laura
mentioned,
we
started
with
docker
ee
and
my
rentist
about
dr
e
from
docker
inc.
So
now
we
are
very
happy
to
work
with
marantis.
This
is
the
core
of
the
stack
that
we
have.
C
I
would
say
that
the
underlying
solutions
that
we
use
are
pcs
of
and
services
of,
our
private
cloud.
So
we
have
compute
services,
network
services,
security,
services,
storage
services,
so
the
usual
services
that
you
have
in
a
public
cloud,
but
in
a
societal
general
flavor
part
of
it
is
based
on
an
alternative
solution.
I
can
mention
that
we
use
openstack,
for
example,
as
a
foundation
for
our
compute
and.
C
We
also
in
in
all
in
those
these
are
the
foundations
and
in
our
own
products.
You
know
we
use
more
and
more
cloud
native
products.
We
recently
introduced
prometheus
for
some
building
use
cases
internally.
We
needed
some
specific
metrics
for
that.
C
Maybe
we
will
talk
a
bit
more
about
that
if
you
are
interested
later
and
we
have
also
introduced
oppa
opa,
open
policy
agent,
also
for
the
same
use
case
and
of
course,
after
attending
kubecon,
we
have
many
ids,
then
it's
for
us.
We
need
to
prioritize,
that's
maybe
the
domain
domain
challenge
when
we
see
the
cloud-related
landscape
and
all
it
offers.
A
C
So
myself,
I
have
attended
last
year,
the
the
european
online
and
this
year
the
plan
was
to
go
to
los
angeles
and
and
and
be
on
site,
but
unfortunately
it
was
not
possible.
So
we
attended
a
very
late
in
the
evening,
so
virtually
and
also
it
was
very
nice
to
have
the
ability
to
see
the
replay
during
the
day
so
that
you
know
it
was
easier
to
to
avoid
the
jet
flag
or
kind
of
virtual.
That,
like
I
would
say,.
A
A
So
what
talks
did
you
stood
out
to
you
during
kubecon,
and
the
ones
that
are
probably
going
like
you
mentioned
earlier,
are
going
to
influence
certain
decision
making
within
your
organization.
C
I
think
multi-cluster
is
a
very
hot
topic
for
us
at
the
moment-
maybe
not
for
just
now,
but
for
the
coming
years,
as
we
are
in
a
hybrid
cloud
setup,
it's
important
for
us
to
be
able
to
to
move
from
one
cloud
to
another
cloud
with
reversibility
and
also
to
to
offer
more
and
more
bridges
between
private
cloud
and
public
cloud,
so
that
our
end
users
or
maybe
our
end
users-
are
more
application
owner
that
they
are
able
to
take
advantages
of
the
best
of
each
world.
C
We
know
that
we
cannot
compete
in
terms
of
catalog
with
public
cloud,
but
we
can
offer
a
very
good
security
setup
and
for
some
use
cases
there
are
awesome
tools
in
public
cloud
that
we
cannot
have
in
in
the
private
cloud
or
that
are
just
for
a
short
period
of
time
and
for
these
kind
of
use
cases.
It's
very
interesting
for
us
to
to
have
multi-cloud
and
be
able
to
move
workload,
and
that
was
the
demo
of
for
guru.
A
Yeah
awesome
lauren:
did
you
get
a
chance
to
watch
any.
B
In
fact,
I
watched
some
not
as
much
as
I
wanted
to,
but
I
was
mostly
interested
in
all
that
involve
security
topics:
okay,
because
it's
a
major
topic
for
us
and
also
all
the
presentation
around
autoscaling,
because
it
is
a
big
part
of
what
we
will
do
next
year.
I
think
try
to
optimize
our
cluster
be
more
efficient,
reduce
the
the
number
of
vms
on
the
cluster
and
all
that
part.
It's
very
interesting.
A
Yeah
awesome
awesome,
yeah,
so
going
back
to
kubernetes,
I
can
imagine
definitely
the
internet
usage
goods
will
definitely
within
your
organization.
Since
you
are
now
scaling
from
using
your
monolith
and
your
mainframes
to
going
multi-cloud,
it
will
have
brought
some
challenges.
How
did
you
handle
cluster
growth
and
adaption
of
these
technologies
within
your
organization?
Given
that
you
are
now,
you
are
switching
from
a
traditional
way
of
doing
things
to
a
modern
way
of
doing
things.
Let
me
put
it
that
way.
B
It's
a
complex
topic,
in
fact,
because
in
our
team
we
only
manage
the
infrastructure
and
not
the
development
part
of
the
application,
and
so
we
try
a
lot
to
to
to
teach
to
to
share
our
knowledge
of
kubernetes,
because
it's
not
widely
spread
in
the
development
teams
for
the
moment
and
and
they
have
a
basic
knowledge
of
kubernetes
so
that
how
it
works.
What
are
the
basic
principles?
B
But
there
is
a
big
part
of
teaching
to
do
with
them
and
explaining
what
are
the
the
more
complex
parts
of
kubernetes,
for
example,
one
that
come
to
mind
is
the
function,
the
the
usage
of
requests
limits
when
you
deploy
on
kubernetes.
It
is
something
that
is
not
natural
to
people
coming
from
monolith
application,
even
if
it
can
relate
to
gvm
sizing,
for
example.
But
it's
not
really
the
same,
and
they
have
more
it's
complex
for
for
them
to
understand
this
and
to
apply
it
every
day
on
their
development.
A
Oh
awesome
yeah,
so
in
relation
to
that
you
mentioned
earlier
that
you,
you
have
good
private
cloud
and
problem.
C
So
the
destination
there
is,
there
are
some
decision
trees
in
different
business
units.
They
don't
have
all
the
same
type
of
applications
so,
depending
on
the
application,
it
is
eligible
or
not
to
the
public
cloud,
because
of
course
we
have
a
huge
focus
on
data
protection
and
in
in
case
of,
for
example,
customer
data.
C
We
don't
want
to
expose
it
and
we
want
to
make
sure
that
we
have
all
the
security
in
place
to
protect
that
data,
and
so
this
is
regarding
your
first
question
regarding
you
know,
public
or
private,
and
regarding
the
kind
of
cluster
that
we
have,
we
have
a
stretch
cluster
across
multi
reliability
zone
regarding
the
private
cloud,
so
we
are
able,
if
we
lose
one
availability
zone,
to
have
a
zero
downtime
on
our
application.
Based
on
that
setup,.
B
So
that's
part
of
my
team,
mainly
even
if
we
are
helped
by
the
developers
of
florence
team.
In
fact,
we
are
working
in
in
cattle
mode
now
for
the
the
underlying
costs
of
the
cluster
and
we
renew
every
host
every
two
months.
That
is
our
principle.
Every
two
months
we
renew
the
host
with
a
new
version
of
operating
system
with
the
updated
engine
and
once
every
quarter
we
upgrade
the
version
of
mirantis
cluster,
and
this
is
done
in
place.
B
We
never
create
new
clusters
for
the
the
new
version,
so
we
we
do
upgrade
in
place
most
of
the
time
it's
transparent
for
a
user,
but
there
is
a
huge
challenge:
it's
to
work
with
developers
to
anticipate
a
deprecated
feature
from
kubernetes.
That
is
our
biggest
challenge.
Nowadays,
it's
this
one.
A
B
It's
the
multi-tenant
party,
in
fact,
for
me,
that
is
the
the
biggest
problem
because
we
provide
the
namespace
as
a
service.
In
fact,
in
society
it's
not
cluster
as
a
service,
so
many
teams
are
using
the
same
cluster
and
one
team
doing
something
wrong:
can
impact
the
other
team
running
on
the
same
cluster
so
yeah.
This
is
what
we
deal.
B
B
A
Okay,
awesome
yeah:
you
wanted
to
add
something.
C
Yes,
regarding
the
cpu
and
the
quota
and
everything,
I
think
this
is
a
for
us
focus,
because
we
are
on
premises
and
if
our
user
requests
more
than
what
they
need.
Actually
they
artificially
increase
the
size
of
our
infrastructure,
because
behind,
of
course,
there
are
physical
servers
and
so
for
us,
it's
very
important
to
keep
a
good
balance
between
what
is
necessary
for
the
good
work
of
the
application
and
the
cost
and
the
environmental
footprint
of
the
infrastructure
that
we
provide.
A
Talk
about
developer
experience,
you
shared
the
other
time
how
you
are
trying
to
educate
your
developer
team,
who
don't
have
a
lot
of
experience
with
communities
on
how
to
make
use
of
it.
Can
you
tell
us
more
about
what
other
developer
experience
initiatives
you
have
that
have
played
in
the
evolution
of
your
clusters.
C
So
part
of
the
answer
is
about
the
the
way
they
can
consume
our
services.
So
as
part
of
our
private
cloud,
we
have
apis
for
all
services,
and
so
in
my
team,
for
example,
we
are
in
charge
of
developing
the
api
for
the
kubernetes
service.
So
it's
not
the
native
kubernetes
api
or
the
mirantis
api.
C
It's
it's
the
api.
That
is
a
thought
that
is
following
all
the
private
cloud
rules
that
we
have
in
terms
of
security,
integration
with
the
whole
ecosystem,
and
this
api
has
the
advantage
for
developers
who
have
little
knowledge
about
kubernetes
to
get
a
namespace
with
a
single
api
call,
so
just
a
post
on
the
api
and
you
get
your
namespace
and
you
can
also
get
a
full
routing
mesh
with
a
load,
balancer
geographical
load,
balancing
just
with
this
single
call,
depending
on
the
options
that
you
choose
during
this
call.
C
So
this
is
a
huge
accelerator,
because
when
you
have
the
proper
documentation,
getting
up
and
running
only
takes
a
few
minutes.
If
you
have
already
all
the
information
that
you
need
to
to
do
this,
this
bus
on
the
api.
A
Awesome
so
in
line
with
that,
you've
already
told
us
how
your
developers
interact
with
the
clusters
and
the
services.
What
is
the
typical
lifecycle
of
application,
development,
maintenance
and
troubleshooting.
B
C
So
actually,
we
want
to
be
open.
As
we
have
many
business
units.
There
are
different
software
factories
with
different
cultures,
I
would
say,
and
depending
on
the
type
of
workloads,
they
are
free
to
to
use
our
service,
as
they
would
do
on
a
public
cloud
provider
or
service.
For
example.
Okay,.
B
B
C
So
my
experience
is
mostly
related
to
the
qcon,
where
I
was
virtually
and
it
was
a
great
experience
also
for
the
day-to-day
job.
The
quality
of
the
documentation
is
very
important,
and
the
fact
that
we
know
that
everything
is
open
that
we
can,
you
know,
go
to
the
github
interact
with
the
contributors
become
contributors.
Maybe
one
day
this
is.
This
is
very
interesting
and
for
me,
compared
to
you
know
the
van
der
waals
that
we
were
used
to
for
decades.
C
It's
it's
a
really
a
huge
improvement
and
a
source
of
motivation.
A
C
I
think
this
is
for
us
more
and
more
concern,
so
a
company
just
committed
to
be
an
carbon
neutral
in
2050,
and
so
part
of
it
is
in
on
the
banking
side.
So
I
will
not
talk
about
that
because
I'm
not
directly
involved
in
selling
our
products,
but
regarding
the
I.t
we
also
have
our
responsibility.
C
We
know
that
at
the
global
level
year
after
year,
it
footprint
is
increasing,
and
so
it's
important
for
us
to
to
to
optimize
our
footprint
to
reduce
it
when
possible,
and
so
there
are
some
cloud
native
initiatives
that
are
growing.
I
would
say
in
this
area
some
were
addressed
at
the
kubecon.
For
example,
there
were
a
presentation
regarding
kedar
to
to
to
auto
scaling
of
clouds.
Also
the
well.
We
were
talking
about
multi-cluster
when
you
have
multi-cluster.
C
If
you
have
the
ability
to
easily
move
from
one
cluster
to
the
other,
you
can
choose
also
to
move
the
the
workload
based
on
the
footprint,
for
example
the
environmental
footprint.
So
these
are
areas
where
I
think
cloud
native
will
bring
more
and
more
tools
for
us
in
the
future.
A
B
Main
challenges
for
us
is
to
automatize
everything
possible
and
we
want
the
cluster
to
be
self-healing,
to
be
self-regenerating,
to
be
auto-scaling,
to
reduce
to
the
minimum.
What
we
have
to
do
and
be
able
to
provide
more
value
to
the
client
by
adding
new
feature
and
not
having
to
to
deal
with
this
day-to-day
incident
that
are
bringing
nothing
to
the
team,
in
fact,
yeah
sure.
A
So
the
next
cube
con
is
in
valencia,
spain,
I
are
you
all
planning
to
attend
physically,
since
it
probably.
C
B
Thanks
to
cncf
for
the
the
job,
because
it's
a
challenging
world
in
cloud
world
is
a
very
challenging,
very
dynamic
world.
It's
very
difficult
to
follow
all
the
topics
every
day
and
having
a
source.
A
main
source
of
information
is,
is
very
important.
A
A
So
thanks
everyone
for
joining
this
latest
episode
of
the
cloud
native
end
user
lounge.
It
was
great
having
lauren
of
lauren
talking
about
associated
generals
usage
of
cloud
native.
We
also
really
love
the
interaction
and
questions
that
the
audience
are
going
to
be
adding
to
this.
So
please
ask
any
questions.
If
you
have
for
our
audience,
we
will
bring
you
the
latest
cloud
native
end
user
stories
on
fourth
on
the
fourth
thursday
of
every
month
at
9
00
a.m.
A
Pacific
time
so
don't
forget
to
join
us
at
kubecon
cloud
nativecon
eu
in
valencia,
spain.
It
will
definitely
be
hybrid
again
this
time.
So
if
you
are
unable
to
join
physically,
you
can
connect
it's
to
be
happening.
May
17
to
20th
of
202
to
you
can
come
to
hear
about
the
latest
technologies
coming
out
of
the
cloud
native
community.
A
C
A
A
Hey
welcome
back
lauren.
That
was
an
interesting
video
to
watch
again,
so
there
have
been
quite
a
lot
of
interactions
in
the
chats
before
we
get
to
that.
Is
there
anything
else
you
would
like
to
add,
or
maybe
some
more
things
that
have
happened
since
recorded
sessions.
C
So
we
are
running
today
more
than
1000
nodes
of
kubernetes
clusters
with
roughly
30
000
pods,
so
it
represents
hundreds
of
applications
for
for
the
bank
and
what
is
very
interesting
for
us
as
infrastructure
people
is
that
we
have
a
quite
important
diversity
of
applications,
and
so
for
that
we
try
to
customize
the
the
clusters
that
we
provide
with
more
and
more
security
and
more
and
more
features.
C
So,
for
example,
we
are
increasing
the
the
way
we
are
doing
the
building
internally
so
that
people
are
built
just
for
the
cpu
and
memory
they
consume
are
the
requests,
and
this
is
for
for
the
application
owner,
but
for
the
the
group
as
a
whole
a
way
to
optimize
the
way
we
use
infrastructure
because
people
are
able
to
just
to
save
compared
to
what
they
were
doing
on
virtual
machine,
for
example,
and
with
this
new
improvements,
we
think
that
projects
will
be
able
to
save
up
to
30
percent
of
their
computer
compute
billing
on
our
private
cloud.
C
So
it's
it's
really
interesting
and
behind
that
there
is
a
reduction
of
energy
that
is
consumed,
and
so
it's
also
for
us
contributions
to
a
carbon
neutral
objectives
that
we
have
for
2050..
A
C
C
A
Yeah
awesome,
so
I
think
I
also
asked
when
we
were
recording
the
call
one
of
the
user
is
also
asking.
Should
we
should
we
be
looking
forward
to
you
sharing
more
of
your
experience
and
use
cases
at
cubecom,
valencia.
C
C
C
Cncf
is
about
open
services
cloud
native,
but
there
is
also
a
lot
of
open
source
involved,
so
society
general
is
also
trying
to
become
an
open
source,
a
contributor,
but
it's
not
always
as
easy
as
it
could
be,
and
so
we
are
already
opening
source
of
internal
application
that
we
have
and
maybe
in
the
future
we
will
have
more.
A
Yeah
awesome
yeah,
you
were
talking
about
common
neutral.
We
all
have
to
play
our
part.
So
it's
not
just
a
world
problem.
It's
everybody's
problem,
but
okay,
christian,
just
came
in
how
easy
or
difficult
was
the
move
from
swam
to
kubernetes.
C
It's
not
easy,
it's
not
easy
for
all
applications.
It
really
depends,
I
think,
on
the
teams,
some
teams,
some
application
owner
and
their
developers,
they
were
able
to
migrate
quite
fast
because
they
have
the
skills
because
they
they
also
can
have
that
kind
of
priority
in
their
backlog.
C
C
I
think
the
the
difficulty
is
not
technical
when
you
already
have
an
application
that
is
running
within
containers.
Moving
from
swarm
to
kubernetes
is
not
that
complicated
and
also,
as
we
mentioned
a
few
minutes
ago,
we
have
worked
a
lot
on
the
improving
the
developer
experience.
C
So
it's
not
difficult
for
our
end
user
to
get
a
namespace
instead
of
a
docker
ee
workspace
on
swarm.
Also,
we
have
been
using
the
the
same
line
of
products.
We
were
with
the
docker
enterprise
edition
at
the
swarm
period,
and
so
now
marian
is
kubernetes
engine.
C
The
kubernetes
distribution
we
use
is
also
provided,
bundled
with
swarm,
and
so
there
are
tools
for
people
if
they
want
to
migrate
a
docker
compose
to
kubernetes,
for
example,
in
the
distribution,
and
we
have
also
very
good
experts
that
have
been
with
us
for
a
few
years
now,
since
nearly
the
beginning
of
the
journey,
so
they
they
have
been
working
with
the
the
applications
to
migrate
to
swarm
and
they
are
helping
also
the
team
to
migrate
to
kubernetes,
with
a
knowledge
of
their
previous
challenges
and
so
yeah.
C
It's
it's
something
that
is
feasible
and
currently
I
don't
I'm
not
aware
of
people
who
really
want
to
stick
on
swarm.
For
example,
kubernetes
is
evolving
has
become
our
standard.
I
think
it
has
become
also
an
industry
standard
yeah.
So
there
is
quite
a
lot
of
motivation
from
everybody
to
to
migrate
to
kubernetes
and
it's
working
quite
well.
C
So
not
only
of
what
we
are
doing
is
open
source,
but
it's
important
for
us
to
have
a
kubernetes
as
the
core
of
our
orchestrating
offer,
because
we
know
the
the
open
source
community
driven
by
cncf
will
provide
us
a
value
release
after
release,
and
we
will
not
remain
on
a
product
that
is
used
by
a
small
base
of
clients.
C
You
know
now
there
are
thousands
of
kubernetes
cluster
everywhere,
and
so
we
are
not
only
learning
from
our
own
experience
and
a
vendor
experience,
but
but
for
a
much
from
a
much
larger
community,
and
this
kind
of
ecosystem
for
me
brings
much
more
value
and
evolves
faster
than
a
traditional
closed
source
products.
A
Yeah
awesome,
yeah,
there's
one
question
that
I
have
meaning
to
ask
since
we
recorded
the
last
session.
You
know,
as
a
financial
institution
there's
often
talks
around,
that
oh
financial
institutions
are
slow
to
adopt
new
technologies
and
so
on,
and
I
know
it's
because
you
are
in
a
regulated
industry.
How
do
you
manage
regulation
with
innovation.
C
So,
as
part
of
our
internal
standards
for
private
cloud,
we
have
a
system
of
labels
and
this
kind,
these
levels,
the
each
service,
has
the
obligation
to
to
meet
these
standards.
So
we
have
a
first
level,
second
level
and
third
level
and
for
each
level.
C
You
know
that
your
application
can
meet
the
regulator
requirements
when
the
service
has
reached
the
level,
for
example,
if
you
have
an
application
that
is
not
very
sensitive,
not
using
customer
data
and
that
can
use
level
one
services,
then
the
application
owners
know
that
it
can
host
the
application
on
services
with
the
label
level,
one
for
more
advanced
information
in
terms
of
sensitivity,
then
the
application
owner
will
look
at
services
with
level
two
same
for
level
three.
This
is
how
it
is
organized.
C
So,
behind
these
labels
there
is
a
lot
of
work
in
terms
of
security
of
architecture
of
operation
and
development
standards
that
are
written
and
audited.
C
So
actually,
my
team
has
spent
the
last
three
months
just
working
to
reach
a
new
level
of
label
so
that
we
can
host
more
and
more
and
sensitive
application
without
risking
security
and
and
also
security
is
a
very
large
topic.
So
you
know
it
is
about
availability
about
confidentiality
and
many
other
things.
C
A
C
So
we
are
relying
on
kubernetes
mechanisms,
so
basically
we
have
the
possibility
to
segregate
the
network
traffic
with
network
policy.
We
have
a
resource
code
limit
range
to
guarantee
the
cpu
and
memory
for
each
application
inside
a
multi-tenant
environment
and
also
with
the
mariantis
distribution.
C
C
So
these
are
the
the
main,
the
main
characteristics
of
technical
architecture,
to
meet
that
kind
of
challenge.
A
C
So
we
we
are
very
satisfied,
I
mean
we
are.
We
have
people
from
marantis
working
with
us
on
a
day-to-day
basis
for
us,
it's
as
a
financial
institution,
it's
part
of
our
regular
requirements
in
terms
of
regulation
to
have
support
from
external
expertise,
and
and
so
when
we
are
dealing
with
a
complicated
incidence
or
where,
when
we
are
doing
some
major
upgrade
for
us,
it's
a
security
to
work
with
with
marante's
experts
and
to
know
that
also
there
are.
C
A
C
Just
can
mention
that
society
generally
is
hiring
in
different
places
in
the
world,
so
do
not
hesitate
to
go
to
or
carry
your
website
to
find
positions
available,
and
maybe
you
will
join
me
in
your
transformation
journey.
It
will
be
interesting
and
there
is
a
lot
of
interesting
challenges
in
front
of
us.
A
Yeah
awesome:
that's
a
very
awesome,
closing
yeah!
So
thank
you
very
much
everyone
watching,
I'm
just!
I
will
be
watching
the
recording
later
once
again,
if
you're
an
end
user
company-
and
you
would
like
to
share
your
story-
your
cognitive
journey-
you
can
reach
out
to
cncf
at
cncf,
dot,
io,
slash,
end
user
or,
if
you
want
to
be
part
of
the
end
user
community,
also
remember
that
the
kubecon
clan
native
con
eu
2021
happening
in
valencia
next
year
may
17-20.