# How to Deploy OpenObserve on Spectro Cloud Palette

> A step-by-step guide to running OpenObserve on a Spectro Cloud Palette AWS cluster: build the cluster profile, add the OpenObserve pack as an add-on, configure PostgreSQL, and open the UI.

Source: https://openobserve.ai/blog/deploy-openobserve-spectro-cloud-palette/
Published: 2026-11-18
Authors: Chaitanya Sistla, Medha Kulamarva
Category: How To
Tags: OpenObserve, Kubernetes, AWS, Integrations, Infrastructure, Observability

---

**Deploying OpenObserve on Spectro Cloud Palette** takes two cluster profiles: a full cluster profile that builds the Kubernetes cluster on AWS, and an add-on profile that installs the OpenObserve pack from the Palette Registry. This guide walks platform engineers through both, end to end, including the PostgreSQL database OpenObserve needs and how to open the UI once it is running.

## TL;DR

- **Cluster profile**: Ubuntu 24.04, Palette eXtended Kubernetes (PXK), Cilium, and Amazon EBS CSI on AWS IaaS.
- **Add-on profile**: the OpenObserve pack with your root user, S3 storage, service, and PostgreSQL values.
- **PostgreSQL is required**: add the PostgreSQL pack (embedded database) or use a managed one.
- **Access**: select the **:5080** link under **Services** on the cluster Overview tab.

## Why run OpenObserve on Spectro Cloud Palette?

Spectro Cloud Palette manages Kubernetes clusters through **cluster profiles**: layered stacks of packs (OS, Kubernetes, network, storage, and add-ons) that Palette deploys and keeps in sync across clusters. Adding OpenObserve as a pack means your observability backend is versioned, repeatable, and deployed the same way as the rest of the platform.

OpenObserve is an open source (AGPL-3.0) observability platform that stores telemetry as Parquet on object storage. Once it is running in your Palette cluster, you get:

- **Telemetry**: logs, metrics (PromQL and SQL), traces with a service graph and service catalog, and continuous profiling.
- **Frontend and synthetics**: real user monitoring (RUM), session replay, error tracking, and synthetic browser and protocol checks.
- **AI**: AI Assistant, SRE Agent for AI root cause analysis, an MCP server, LLM observability and evaluations, anomaly detection, log patterns, and insights.
- **Alerting and reliability**: scheduled, real-time, composite, and anomaly alerts, incident management, and SLOs with error budgets and burn rate.
- **Dashboards and reports**, plus **pipelines**, VRL functions, enrichment tables, and downsampling for data processing.
- **Storage and cost**: object storage, bring your own bucket, extended retention, and ingest-based pricing with no per-host or per-user fees.
- **Security and compliance**: SSO, RBAC, multi-tenancy, sensitive data redaction, audit trail, cipher keys, and federated search. OpenObserve is SOC 2 Type II and ISO 27001 certified, with GDPR support through its EU region.
- **Open standards**: OpenTelemetry-native ingestion for logs, metrics, traces, and profiles.

Some of these, such as SSO, RBAC, and the AI features, are part of OpenObserve Enterprise and Cloud.

## How does an OpenObserve deployment on Palette work?

A Palette cluster is built from a full (or infrastructure) cluster profile plus zero or more add-on profiles. OpenObserve lives in an add-on profile, so you can attach it to any healthy cluster without rebuilding the cluster itself.

| Profile | Layer | Pack used in this guide |
|---|---|---|
| Full (`Openobserve_k8s`) | OS | Ubuntu (AWS) 24.04 |
| Full | Kubernetes | Palette eXtended Kubernetes (PXK) 1.37.0 |
| Full | Network | Cilium 1.20.4 |
| Full | Storage | Amazon EBS CSI 1.67.2 |
| Add-on (`o2_layer`) | Monitoring | OpenObserve 1.0.3 |
| Add-on (`o2_layer`, embedded database only) | Database | PostgreSQL |

## Prerequisites

- A [Palette](https://console.spectrocloud.com) account and a project you can create profiles and clusters in.
- An AWS account added to Palette, and an EC2 key pair in the region you deploy to. (Source: Spectro Cloud docs, Create and Manage AWS IaaS Cluster, November 2026)
- A PostgreSQL 14 or later database for OpenObserve metadata, or the PostgreSQL pack for the embedded database (Step 4). (Source: Spectro Cloud docs, Deploy OpenTelemetry Monitoring Stack, November 2026)
- Optional: an S3 bucket and access keys if you want OpenObserve to store data in object storage instead of on the pod.

## Step 1: Log in to Palette

Log in to [Palette](https://console.spectrocloud.com) and select your project. The **Project Overview** page shows your clusters and their health.

![Spectro Cloud Palette Project Overview page with the left menu showing Profiles, Clusters, and Cluster Configurations](/assets/blog/deploy-openobserve-spectro-cloud-palette/image1.png)

## Step 2: Create the cluster profile

The cluster profile defines the OS, Kubernetes distribution, network, and storage for the cluster that will run OpenObserve.

1. From the left menu, select **Profiles**, then **Add Cluster Profile**. Enter a name (this guide uses `Openobserve_k8s`), keep version `1.0.0`, select **Full** as the **Type**, and select **Next**.

   ![Palette Add a new cluster profile wizard, Basic Information step, with name Openobserve_k8s and type Full selected](/assets/blog/deploy-openobserve-spectro-cloud-palette/image2.png)

2. On **Cloud Type**, select **AWS IaaS** under **Infrastructure provider**, then select **Next**.

   ![Palette Cloud Type step with AWS IaaS selected as the infrastructure provider](/assets/blog/deploy-openobserve-spectro-cloud-palette/image3.png)

3. On **Profile Layers**, select **Ubuntu (AWS)** as the base OS pack.

   ![Palette Profile Layers step 1 of 4, Select your base OS pack, with Ubuntu (AWS) highlighted](/assets/blog/deploy-openobserve-spectro-cloud-palette/image4.png)

4. Leave the Ubuntu 24.04 values as they are and select **Next layer**.

   ![Ubuntu (AWS) 24.04 pack configuration in Palette with the pack readme open](/assets/blog/deploy-openobserve-spectro-cloud-palette/image5.png)

5. For the Kubernetes layer, select **Palette eXtended Kubernetes (PXK)**.

   ![Palette Select your base Kubernetes pack with MicroK8s, Palette eXtended Kubernetes, and RKE2 options](/assets/blog/deploy-openobserve-spectro-cloud-palette/image6.png)

6. Keep the default PXK values (version 1.37.0) and select **Next layer**.

   ![Palette eXtended Kubernetes (PXK) 1.37.0 pack configuration with its readme](/assets/blog/deploy-openobserve-spectro-cloud-palette/image7.png)

7. For the network layer, select **Cilium**. (The screenshot shows Calico highlighted; select Cilium.)

   ![Palette Select your base Network pack listing Calico, Cilium, Cilium CNI (Canonical Kubernetes), Custom CNI, and Flannel](/assets/blog/deploy-openobserve-spectro-cloud-palette/image8.png)

8. Keep the default Cilium values (version 1.20.4) and select **Next layer**.

   ![Cilium 1.20.4 network pack configuration in Palette with prerequisites in the readme](/assets/blog/deploy-openobserve-spectro-cloud-palette/image9.png)

9. For the storage layer, select **Amazon EBS CSI**. OpenObserve uses persistent volumes, so this layer provides the storage class for them.

   ![Palette Select your base Storage pack with Amazon EBS CSI highlighted among AWS storage options](/assets/blog/deploy-openobserve-spectro-cloud-palette/image10.png)

10. Keep the default EBS CSI values (version 1.67.2), adjusting the storage class only if your environment needs it, and select **Confirm**.

    ![Amazon EBS CSI 1.67.2 storage pack configuration in Palette with the AWS EBS CSI Driver readme](/assets/blog/deploy-openobserve-spectro-cloud-palette/image11.png)

11. Select **Next** to review the profile, then select **Finish Configuration**.

    ![Palette cluster profile Review step showing csi-aws-ebs, cni-cilium-oss, kubernetes, and ubuntu-aws layers and the Finish Configuration button](/assets/blog/deploy-openobserve-spectro-cloud-palette/image12.png)

## Step 3: Deploy the AWS cluster

After you save the profile, Palette opens it. Select **Deploy** to create a cluster from it.

![Openobserve_k8s cluster profile page in Palette showing the four infrastructure layers and the Deploy button](/assets/blog/deploy-openobserve-spectro-cloud-palette/image13.png)

The cluster wizard asks for the following. (Source: Spectro Cloud docs, Create and Manage AWS IaaS Cluster, November 2026)

1. **Basic information**: a cluster name.
2. **Cluster config**: the **Cloud Account**, **Region**, and **SSH Key Pair Name**.
3. **Node pools**: control plane and worker pools, each with an **Instance Type** and **Availability Zones**. Spectro Cloud recommends at least 4 CPUs and 4 GB of memory per node; size the workers for the telemetry volume you expect OpenObserve to handle.
4. **Validate**, then **Finish Configuration**.

Provisioning takes several minutes. When the cluster's **Cluster Status** shows **Running**, move on. The full field reference is in Spectro Cloud's [Create and Manage AWS IaaS Cluster](https://docs.spectrocloud.com/clusters/public-cloud/aws/create-cluster/) guide. If you run OpenObserve on AWS without Palette, compare this with [deploying OpenObserve on Amazon EKS with ALB ingress](/blog/how-to-deploy-openobserve-on-eks-with-alb-ingress/).

## Step 4: Choose a PostgreSQL option for OpenObserve

OpenObserve stores its metadata in PostgreSQL 14 or later. By default, the OpenObserve pack deploys its own embedded PostgreSQL database, and that database runs on the [CloudNative-PG](https://cloudnative-pg.io/) operator, which must be installed in the cluster before the pack deploys. Pick one of two setups before you build the add-on profile, because **if OpenObserve has no working database, the add-on deployment fails**.

| Option | When to use it | What to configure |
|---|---|---|
| Embedded PostgreSQL (pack default) | Evaluation, or clusters without a managed database | Add the **PostgreSQL** pack from the Palette Registry to the OpenObserve add-on profile, as Spectro Cloud's own OpenObserve setup does. Give it a lower install order than OpenObserve (Step 5). With the embedded database on, the chart generates its own connection string and ignores `ZO_META_POSTGRES_DSN`. |
| External managed PostgreSQL (for example, Amazon RDS for PostgreSQL) | Production; you want backups, upgrades, and failover handled for you | Set `ZO_META_POSTGRES_DSN` to the database's connection string and turn off the embedded database. Allow traffic from the cluster's worker nodes to the database on port 5432. No PostgreSQL pack is needed. |

For an external database, the values look like this. In the upstream OpenObserve Helm chart, the embedded database is on by default and its generated connection string takes priority, so set `postgres.enabled` to `false` when you bring your own:

```yaml
charts:
  openobserve:
    auth:
      ZO_META_POSTGRES_DSN: "postgres://<DB_USER>:<DB_PASSWORD>@<DB_HOST>:5432/<DB_NAME>"
    postgres:
      enabled: false
```

## Step 5: Create the OpenObserve add-on profile

1. Go to **Profiles** and select **Add Cluster Profile** again. Name it (this guide uses `o2_layer`), select **Add-on** as the **Type**, and select **Next**.

   ![Palette Add a new cluster profile wizard with name o2_layer and Add-on type selected](/assets/blog/deploy-openobserve-spectro-cloud-palette/image14.png)

2. Add a pack, search for `openobserve` in the **Palette Registry**, and select the **OpenObserve** pack.

   ![Palette pack search for openobserve in the Palette Registry showing the OpenObserve monitoring pack, latest v1.0.3](/assets/blog/deploy-openobserve-spectro-cloud-palette/image15.png)

3. Select **Values** and set your configuration: the root user, S3 storage, and how the service is exposed. Add the PostgreSQL settings from Step 4 if you use an external database:

   ```yaml
   charts:
     openobserve:
       auth:
         ZO_ROOT_USER_EMAIL: "admin@example.com"
         ZO_ROOT_USER_PASSWORD: "<STRONG_PASSWORD>"
         ZO_S3_ACCESS_KEY: "<AWS_ACCESS_KEY_ID>"
         ZO_S3_SECRET_KEY: "<AWS_SECRET_ACCESS_KEY>"
       config:
         ZO_LOCAL_MODE: "false"
         ZO_S3_REGION_NAME: "<AWS_REGION>"
         ZO_S3_BUCKET_NAME: "<BUCKET_NAME>"
       service:
         type: LoadBalancer
         annotations:
           service.beta.kubernetes.io/aws-load-balancer-internal: "true"
   ```

   The upstream OpenObserve Helm chart defaults `service.type` to `ClusterIP`, which is reachable only inside the cluster. A `LoadBalancer` service gets an AWS load balancer address, which Palette shows as a link in Step 7. The `aws-load-balancer-internal` annotation keeps that load balancer inside your VPC; remove it only if you need public access, and put TLS in front of OpenObserve if you do. Check the pack values to see what your pack version sets.

   `ZO_LOCAL_MODE: "false"` runs OpenObserve in cluster mode, storing telemetry in S3 and metadata in PostgreSQL. Spectro Cloud's own OpenObserve guide sets local mode to keep data on the pod, but the OpenObserve docs describe local mode as a single-node deployment, so treat that as evaluation only. Every setting is described in the [OpenObserve environment variables reference](https://openobserve.ai/docs/environment-variables/).

   ![OpenObserve 1.0.3 pack values editor in Palette showing the pack image list and charts.openobserve settings, with the Confirm & Create button](/assets/blog/deploy-openobserve-spectro-cloud-palette/image16.png)

4. If you use the embedded database, add the **PostgreSQL** pack to this profile too. Palette installs packs with the lowest **Install order** value first and waits until they are ready before installing the next ones, so give PostgreSQL a lower value than OpenObserve (for example, `0` for PostgreSQL and `10` for OpenObserve). The field sets the `spectrocloud.com/install-priority` annotation on the pack layer. (Source: Spectro Cloud docs, Add-on Profiles, Install Order, November 2026)

5. Select **Confirm & Create**, then **Next**, review the profile, and select **Finish Configuration**.

## Step 6: Add the OpenObserve profile to your cluster

The screenshots in this step and the next come from a different, existing cluster (`o2-internal-arm`) that already has an OpenObserve add-on attached, so some details differ from the ones built above: the profile names, Calico instead of Cilium, EBS CSI 1.67.1, OpenObserve 1.0.2, and PostgreSQL 1.29.0. The add-on steps are the same.

1. From the left menu, select **Clusters** and open the cluster you deployed in Step 3.
2. Select the **Profile** tab, then the **+** next to **Addon Layers** (**Add add-on profile**).

   ![Palette cluster Profile tab with the Add add-on profile button next to Addon Layers, above the infrastructure layers](/assets/blog/deploy-openobserve-spectro-cloud-palette/image17.png)

3. In **Choose a Profile**, select your OpenObserve add-on profile and select **Confirm**. Review the layers, then select **Save**.

   ![Palette Choose a Profile panel with the openobserve add-on profile selected and the Confirm button](/assets/blog/deploy-openobserve-spectro-cloud-palette/image18.png)

## Step 7: Open OpenObserve from the cluster Overview

Select the **Overview** tab to watch the add-on deploy. **Cluster Detail Status** shows the add-on deployment in progress, and the **Cluster Profiles** panel shows each pack with a green indicator once it is healthy.

![Palette cluster Overview tab showing a healthy running cluster with the OpenObserve add-on still deploying and the postgresql pack ready](/assets/blog/deploy-openobserve-spectro-cloud-palette/image19.png)

When OpenObserve is up, Palette lists its service under **Services** on the same Overview tab. Select the **:5080** link to open the OpenObserve login page, then sign in with the `ZO_ROOT_USER_EMAIL` and `ZO_ROOT_USER_PASSWORD` you set in the pack values.

## Troubleshooting

| Symptom | Likely cause | Fix |
|---|---|---|
| Add-on deployment fails with an external database | OpenObserve can't reach PostgreSQL | Check `ZO_META_POSTGRES_DSN`, `postgres.enabled: false`, and the security group (port 5432 from the worker nodes) |
| Add-on deployment fails with the embedded database | The PostgreSQL pack is missing or installs after OpenObserve | Add the PostgreSQL pack and give it a lower **Install order** than OpenObserve |
| Pods stay `Pending` | No storage class or not enough node capacity | Confirm the Amazon EBS CSI layer is healthy and the worker pool has enough CPU and memory |
| No **:5080** link under **Services** | The OpenObserve service is `ClusterIP` | Set `charts.openobserve.service.type` to `LoadBalancer` in the pack values |
| Login fails | Wrong credentials | Use the exact root email and password from the pack values |

## How do you send telemetry to OpenObserve after deploying it?

OpenObserve accepts OpenTelemetry (OTLP) for logs, metrics, traces, and profiles, so any OpenTelemetry Collector can export to it. Spectro Cloud documents a full pattern for this in [Deploy OpenTelemetry Monitoring Stack](https://docs.spectrocloud.com/clusters/cluster-management/monitoring/open-telemetry/): workload clusters send to a central collector, which exports to OpenObserve.

From there:

- Collect cluster metrics with the approach in [Kubernetes monitoring with OpenTelemetry and Prometheus](/blog/kubernetes-monitoring-with-opentelemetry-prometheus/).
- Load ready-made views with [prebuilt Kubernetes dashboards for OpenObserve](/blog/import-prebuilt-k8s-dashboards/).
- Manage alerts, dashboards, and pipelines declaratively with the [OpenObserve Kubernetes Operator](/blog/openobserve-kubernetes-operator-observability-as-code/).
- Learn the collector basics in the [OpenTelemetry guide](/opentelemetry/).

## What should you change for production?

- **Use a managed PostgreSQL database** instead of an in-cluster one, so metadata survives cluster changes.
- **Keep cluster mode with S3** (`ZO_LOCAL_MODE: "false"` plus bucket settings) rather than local mode on the pod.
- **Run OpenObserve in high-availability mode** for large telemetry volumes. The [OpenObserve HA deployment guide](https://openobserve.ai/docs/ha_deployment/) covers the components.
- **Keep secrets out of plain values** where possible, and rotate the root password after first login.
- **Version the add-on profile** in Palette, so upgrades to the OpenObserve pack roll out the same way to every cluster.


## Get started with OpenObserve

- Read the [OpenObserve documentation](https://openobserve.ai/docs/).
- Try OpenObserve Cloud at [cloud.openobserve.ai](https://cloud.openobserve.ai).
- Self-host it with the [OpenObserve quickstart](https://openobserve.ai/docs/quickstart/).
