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
Apollo recommends using the [Apollo GraphOS Operator](/apollo-operator/) for production deployments and when managing multiple routers or complex architectures. The Operator provides declarative Kubernetes resources to manage routers, supergraphs, graph schemas, and subgraphs, making it easier to maintain consistency and automate deployments across your infrastructure.
15
+
16
+
<br/><br/>
17
+
18
+
Use the Operator when you need:
19
+
- Production-grade deployments with declarative configuration management
20
+
- Simplified management of multiple routers, supergraphs, and subgraphs
21
+
- Support for complex architectures including single-cluster, multi-cluster, and hybrid configurations
22
+
- Integration with existing CI/CD workflows through deploy-only patterns
23
+
24
+
For more details, see the [Operator workflow patterns](/apollo-operator/workflows/).
25
+
26
+
</Note>
27
+
28
+
<ElasticNotice />
29
+
30
+
This guide uses Helm charts to deploy a self-hosted router in Kubernetes. Using Helm is suitable for quick deployments, testing, or when you prefer direct Helm chart management.
31
+
12
32
This guide shows how to:
13
33
14
34
* Get the router Helm chart from the Apollo container repository.
15
35
* Deploy a router with a basic Helm chart.
16
36
17
-
<ElasticNotice />
18
-
19
37
## Prerequisites
20
38
21
39
<Note>
@@ -124,12 +142,3 @@ For example, this command deploys with a `common_values.yaml` file applied first
The [Apollo GraphOS Operator](/apollo-operator/), which is in Preview, offers an alternative method to deploy the router and manage your schema and subgraphs. The Operator provides declarative Kubernetes resources for managing routers, supergraphs, graph schemas, and subgraphs. It can simplify complex multi-service architectures.
131
-
132
-
The Operator offers different [workflow patterns](/apollo-operator/workflows/) depending on your infrastructure:
133
-
- Single-cluster setups for simpler deployments
134
-
- Multi-cluster and hybrid configurations for distributed services
135
-
- Deploy-only patterns for existing CI/CD workflows
Copy file name to clipboardExpand all lines: docs/source/routing/self-hosted/index.mdx
+12-1Lines changed: 12 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,18 @@ For each version of the Apollo Router, Apollo provides:
24
24
-[A Docker image](#container)
25
25
-[A binary](#local-binary)
26
26
27
-
## Kubernetes using Helm
27
+
## Kubernetes
28
+
29
+
### Apollo GraphOS Operator
30
+
31
+
Apollo recommends the [Apollo GraphOS Operator](/apollo-operator/). The Operator provides declarative Kubernetes resources to manage routers, supergraphs, graph schemas, and subgraphs. It simplifies complex multi-service architectures.
32
+
33
+
The Operator supports [workflow patterns](/apollo-operator/workflows/) based on your infrastructure:
34
+
- Single-cluster setups for simpler deployments
35
+
- Multi-cluster and hybrid configurations for distributed services
36
+
- Deploy-only patterns for existing CI/CD workflows
37
+
38
+
### Helm
28
39
29
40
Helm is a package manager for Kubernetes. Apollo provides a Helm chart with each release of Apollo Router in the GitHub Container Registry. Since router v0.14.0, Apollo has released each router Helm chart as an Open Container Initiative (OCI) image in `oci://ghcr.io/apollographql/helm-charts/router`.
0 commit comments