You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/docs/guides/applications.md
+74-24Lines changed: 74 additions & 24 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,24 @@ aliases:
7
7
- /docs/components
8
8
---
9
9
10
-
## Managed Kubernetes
10
+
11
+
## Application Management Strategies
12
+
13
+
Cozystack deploys applications in two complementary ways:
14
+
15
+
-**Operator‑managed applications** – Cozystack bundles a specific version of a Kubernetes Operator that installs and continuously reconciles the application.
16
+
As a rule, the operator chooses one of the most recent stable versions of the application by default.
17
+
18
+
-**Chart‑managed applications** – When no mature operator exists, Cozystack packages an upstream (or in‑house) Helm chart.
19
+
The chart’s `appVersion` pin tracks the latest stable upstream release, keeping deployments secure and up‑to‑date.
20
+
21
+
## Tenants
22
+
23
+
Tenants in Cozystack are implemented as managed applications.
24
+
Learn more about tenants in [Tenant System]({{% ref "/docs/guides/tenants" %}}).
25
+
26
+
27
+
## Managed (Tenant) Kubernetes Cluster
11
28
12
29
Cozystack deploys and manages Kubernetes clusters as standalone applications within each tenant’s isolated environment.
13
30
These clusters are fully separate from the root management cluster and are intended for deploying tenant-specific or customer-developed applications.
@@ -27,7 +44,9 @@ Deployment involves the following components:
27
44
28
45
This architecture ensures isolated, scalable, and efficient Kubernetes environments tailored for each tenant.
@@ -99,8 +131,10 @@ It aims to provide a unified, high-throughput, low-latency platform for handling
99
131
In Cozystack, we use [Strimzi](https://github.com/cozystack/cozystack/blob/main/packages/system/kafka-operator/charts/strimzi-kafka-operator/README.md)
100
132
to run an Apache Kafka cluster on Kubernetes in various deployment configurations.
The Managed TCP Load Balancer Service simplifies the deployment and management of load balancers.
180
+
It efficiently distributes incoming TCP traffic across multiple backend servers, ensuring high availability and optimal resource utilization.
181
+
182
+
Managed TCP Load Balancer Service efficiently utilizes HAProxy for load balancing purposes.
183
+
HAProxy is a well-established and reliable solution for distributing incoming TCP traffic across multiple backend servers, ensuring high availability and efficient resource utilization. This deployment choice guarantees the seamless and dependable operation of your load balancing infrastructure.
0 commit comments