Page Menu
Home
Phorge
Search
Configure Global Search
Log In
Files
F117753135
kubernetes-cluster.md
No One
Temporary
Actions
View File
Edit File
Delete File
View Transforms
Subscribe
Flag For Later
Award Token
Authored By
Unknown
Size
1 KB
Referenced Files
None
Subscribers
None
kubernetes-cluster.md
View Options
#
Kubernetes
Cluster
##
Three
or
more
nodes
with
K3S
Run
a
cluster
with
3
or
more
nodes
.
A
cluster
allows
to
manage
the
entire
system
as
a
single
unit
.
Storage
can
be
abstracted
from
the
indiviual
nodes
,
so
workloads
can
move
from
one
node
to
the
other
,
making
the
entire
system
self
-
healing
.
This
simplifies
management
,
and
makes
the
system
particularly
resilient
.
###
Storage
Either
use
local
storage
and
pin
deployments
to
specific
nodes
,
or
set
-
up
a
ceph
cluster
.
###
Failure
modes
With
network
storage
,
such
as
ceph
:
One
out
of
3
nodes
can
fail
with
self
healing
,
assuming
there
is
enough
capacity
on
the
remaining
nodes
.
To
avoid
service
interruption
completely
it
is
necessary
to
configure
replication
within
the
cluster
to
ensure
failover
in
case
of
loss
of
a
node
.
##
Openshift
Kolab
is
deployed
in
a
Kubernetes
cluster
.
This
deployment
assumes
the
availability
of
a
shared
storage
such
as
CEPH
,
and
relies
on
Kubernetes
to
achieve
a
level
of
high
availability
(
services
will
be
rescheduled
on
new
node
if
a
node
fails
).
Metallb
is
used
to
expose
services
where
client
-
ip
visibility
is
relevant
.
###
Storage
Use
ceph
storage
or
an
external
storage
solution
with
a
csi
plugin
.
File Metadata
Details
Attached
Mime Type
text/plain
Expires
Sat, Apr 4, 5:07 AM (1 d, 22 h)
Storage Engine
blob
Storage Format
Raw Data
Storage Handle
18781737
Default Alt Text
kubernetes-cluster.md (1 KB)
Attached To
Mode
R114 kolab-infrastructure
Attached
Detach File
Event Timeline