►
A
A
This
is
just
the
cost
model,
part
of
it
which
actually
provides
prometheus
metrics,
for
course,
based
analysis,
and
what
I
did
I
just
installed.
This
cube
coast
course
model
to
be
used
with
gitlab's,
prometus
integration
and
the
end
result
is
this:
chart
I've
added
two
charts
to
this
dashboard,
one,
which
is
the
monthly
note
cost,
as
I
have
a
fixed
number
of
nodes.
A
As
this
is
an
example
cluster,
there
isn't
much
to
be
seen
actually
in
in
this
variance
in
the
coast,
but
you
can
get
the
basic
idea.
I
think,
following
this
topic,
there
are
many
other
metrics
that
we
can
calculate
using
the
cube
cost
model.
Everything
is
written
down
in
the
prometeur
smartdown.
If
I
remember
well
so
here,
but
actually
I
would
better
speak
about
what
I
actually
did.
A
A
After
that,
I've
been
playing
a
bit
to
have
all
of
this
one.
In
a
more
institute's
code
style,
so
with
gitlab
ci
to
deploy
the
xml
files,
this
was
much
more
involved,
as
I
have
a
gitlab
managed
cluster
and
in
the
gitlab
manage
cluster.
The
namespace
and
service
accounts
are
pre-populated
for
us,
so
basically
the
gitlab
managemaster
needed
to
to
have
these
kubernetes
kinds
to
be
applied
in
advance,
as
the
gitlab
provided
service
account
is
too
restrictive.
A
I
need
a
service
account
that
comes
by
default
with
qcos,
and
I
had
to
say
that
with
the
gitlab
ci
file,
but
actually
it
was
very
simple.
I
basically
just
have
a
simple,
deep
learning
gmo
file
with
really
minor
customizations,
this
part
and
the
cloud
provider
api
key
for
ourselves
and
the
community
server
endpoint.
That
was
all
the
customization
needed
to
have
it
set
up
and
following
that,
I
added
the
custom
dashboard.