이 페이지는 기계 번역되었습니다. 영어 원문 읽기.

Component

core/datastore/timescaledb

A time-series database on the PostgreSQL engine: PostgreSQL with the TimescaleDB extension, which adds hypertables — tables partitioned by a time column — and a columnstore for analytical queries over time ranges. Wire here when data arrives ordered by time and is queried over spans of it — metrics, events, telemetry; core/datastore/postgres is the general-purpose relational store, and core/datastore/documentdb the document store on the same engine. It presents the standard PostgreSQL wire contract and exports its host, port, user, database and protocol, so any consumer that speaks PostgreSQL reaches it unchanged. Realized three ways, all self-hosted: a Helm Recipe synthesizing a StatefulSet, a Compose Recipe for local development, and a Helm Recipe emitting a Cluster custom resource for the CloudNativePG control plane. Reach for the synthesized Recipes where nothing is installed in the target cluster; reach for the controller-driven Recipe where that control plane is in place and the cluster can mount an image as a volume. Only that Recipe serves Prometheus metrics; the synthesized Recipes publish those keys empty. On Azure no realization is authored: Azure Database for PostgreSQL flexible server carries the extension's Apache-licensed edition, but nothing its API offers enables it in a database; only CREATE EXTENSION does. The managed path there is core/datastore/postgres on terraform/postgres-flexible-server, with infra.overrides.server_configuration setting azure.extensions to TIMESCALEDB and shared_preload_libraries to timescaledb, and the application running CREATE EXTENSION timescaledb in its database.

출처

공식이 카탈로그가 공식 게시자로 인정하는 서명 ID로 서명되었습니다.
콘텐츠 다이제스트
sha256:25477873aac1609a24de2f7c21f9120a82611f96e5310c74ef3e00fefaf449dd
게시일
2026-11-10T10:11:21Z
서명 ID
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

서명

  • 공식application/vnd.dev.sigstore.bundle.v0.3+json

    https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

    sha256:379cb74b07906f8f04cb9219c65ef8472b8ba66dff92776d78b383fff1a7241b

이 버전의 참조

oci://hub.aggrega.ai/component/core/datastore/timescaledb:1.0.0

개발자 매개변수

개발자가 Aggregate에서 설정하는 값입니다.

이름타입기본값필수설명
databasestringappdb아니요Logical database name created on startup (POSTGRES_DB).
userstringappuser아니요Bootstrap superuser role created on startup (POSTGRES_USER), owner of the initial database.
encodingstring—아니요Database encoding passed to initdb (e.g. UTF8). Omit to use the image default.
localestring—아니요Database locale passed to initdb (e.g. en_US.utf8). Omit to use the image default.
custom_configstring—아니요Raw server configuration block (postgresql.conf format). Applied as the server's configuration file, so settings it omits keep their built-in defaults. One setting is not read from this block: the extension's library must be preloaded at server start or the server refuses to start, so the synthesized Recipes pass the preload list as a server option, which takes precedence over the configuration file. Name any further libraries in extra_preload_libraries rather than here. The controller-driven realization takes server configuration as named settings rather than as a file and halts the build when this is set, naming the key it offers instead.
extra_preload_librariesstring—아니요Additional shared libraries to preload at server start, as a comma-separated list (e.g. pg_stat_statements). The extension's own library is always preloaded and does not need naming here; entries given here are appended to it. Every realization honors this — the synthesized ones as a server option, the controller-driven one as the preload list on the Cluster custom resource.

운영자 사이징

운영자가 환경별로 조정하는 인프라 사이징입니다.

이름타입기본값필수설명
portinteger (min 1024, max 65535)5432아니요Server listen port. Most operators should omit this and let the Recipe assign the default (5432). The controller-driven realization runs the server on 5432 and cannot move it, so it halts the build on any other value rather than handing a consumer a port the server does not answer on.
engine_versionstring2.29.2-pg18-oss아니요Server image tag the synthesized Recipes run. One compound coordinate carries three parts: the extension version, the PostgreSQL major version it is built against, and the edition suffix — so an operator supplies a value shaped like 2.29.2-pg18-oss rather than a bare major version. Dropping the -oss suffix selects the build that also carries the vendor-licensed shared objects. The controller-driven realization does not read this key: it runs a stock PostgreSQL server image and mounts the extension beside it as a second image, so its two coordinates are server_image and extension_image.
server_imagestringghcr.io/cloudnative-pg/postgresql:18.6-minimal-trixie아니요Full reference of the stock PostgreSQL server image the controller-driven realization runs. It carries no time-series extension of its own — the extension arrives as the separate image named in extension_image, which the controller mounts into this one. The two have to be built for the same PostgreSQL major version, operating-system distribution and processor architecture, or the extension's shared objects do not load, so the pair is chosen together. The default here is the build the default extension_image was itself built on: the CloudNativePG project builds its extension images on top of its own minimal PostgreSQL images, and the extension image records that base in its own metadata — PostgreSQL 18 on the Debian trixie base, the minimal build. So the reference has to name the minimal build specifically, not merely the right major version and base: a differently built image at the same major version and base presents a different set of shared libraries for the extension to link against. The default names a specific minor version rather than a tag that rolls, so the reference does not move under a Release. Set this key to move the pin — to another minor version, another base, or a digest reference — and move extension_image with it, since changing one side alone is what breaks the pairing. A build that sets this key empty halts naming it rather than emitting a Cluster with no server image. The synthesized Recipes ignore it and take their image from engine_version.
extension_imagestringghcr.io/cloudnative-pg/timescaledb-oss:2.29.2-18-trixie아니요Full reference of the image carrying the time-series extension, which the controller-driven realization mounts into server_image as a volume. The default names the Apache-licensed build the CloudNativePG project publishes at the extension version this component targets, for PostgreSQL 18 on the Debian trixie base — which is the pairing the default server_image already names, so the two defaults match without an operator choosing either. It is pinned by tag: an image mounted as a volume is resolved by the target cluster rather than by the build, so whether a digest reference resolves on that path is the operator's to check against their own cluster. Set this key to move the pin — to another extension version, another base, or a digest reference that cluster resolves — and move server_image with it. The synthesized Recipes ignore it.
computeobject—아니요—
storageobject—아니요—
overridesobject (open)—아니요Provider-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads.
control_plane_presentbooleanfalse아니요Operator affirmation that the CloudNativePG control plane is installed in the target cluster. The controller-driven realization halts the build unless this is set true, so a Cluster custom resource is never emitted as an orphan into a cluster that cannot reconcile it. The synthesized realizations ignore this flag.
image_volumes_supportedbooleanfalse아니요Operator affirmation that the target cluster can mount an image as a volume, which is how the controller-driven realization delivers the extension. Two things have to hold for it and neither implies the other: the cluster's ImageVolume feature, which is on by default from Kubernetes 1.35 and is enabled by hand on 1.33 and 1.34; and the container runtime the nodes run, which has to be containerd v2.1.0 or later, or CRI-O v1.31 or later. The runtime floor is a node-level one that no newer Kubernetes lifts, so check it against the nodes rather than reading it off the cluster version. The controller-driven realization halts the build unless this is set true, because an extension the cluster cannot mount leaves a server that starts without it. The synthesized realizations ignore this flag.
credentialsstring (generated | supplied)generated아니요Who owns the database's credentials on the controller-driven realization. `generated` — the controller creates the Secret holding the owning role's password and owns it, which is what it does when nothing is supplied; the developer's `database` and `user` values are still honored, and no password reaches the rendered artifact. `supplied` — the controller reads that role's credentials from an existing Secret named in `credentials_secret` and generates none. The synthesized realizations ignore this key: they take the database password from the `password` credential slot.
credentials_secretstring아니요Name of the existing Secret the controller-driven realization reads the database owner's credentials from when `credentials` is `supplied`. The Secret lives in the same namespace as the database, is of type `kubernetes.io/basic-auth`, and carries a `username` entry that must match `values.user` alongside a `password` entry holding that role's password. Leave it empty when `credentials` is `generated`; a controller-driven build halts if `supplied` is selected without it.

출력 계약

이 컴포넌트가 uses 토폴로지를 통해 소비자에게 게시하는 값입니다.

이름타입기본값필수설명
hoststring—예Address a client opens its database connection to. On the in-cluster realizations it is the Service's DNS name.
portinteger—예TCP port the server accepts connections on. It follows the port an operator set in the Release, so a consumer reads it rather than assuming 5432.
userstring—아니요Name of the login role a consumer authenticates as. The matching password arrives through the credential attached to the component, never through this contract.
databasestring—아니요Name of the logical database created at startup. A consumer names it in its connection string to land in the right database rather than the server's default.
protocolstring—아니요Wire protocol the published address speaks — `postgres`, so a consumer reaches the time-series tables with an ordinary PostgreSQL driver.
metrics_pod_selectorstring—아니요Kubernetes label selector matching every instance pod that serves the database's metrics, for a scraper that discovers those pods directly. Set by the controller-driven realization, beside `metrics_pod_port` and `metrics_path`; empty on the synthesized realizations, which serve no metrics.
metrics_pod_portstring—아니요Name of the container port on those pods that carries the metrics, `metrics`. Set and empty together with `metrics_pod_selector`.
metrics_pathstring—아니요Path the metrics are served at on that port, `/metrics`. Set and empty together with `metrics_pod_selector`.

uses 소켓

이 컴포넌트가 연결에 사용하는 의존성 소켓입니다. 소켓을 통해 배선되는 모든 연결의 대상은 해당 소켓의 레이블 셀렉터를 충족해야 하며, 각 연결은 소켓이 선언한 슬롯에 첨부를 전달할 수 있습니다. 필수 슬롯은 Aggregate 또는 Release가 해당 소켓을 통해 배선하는 각 연결이 채워야 합니다.

선언된 uses 소켓이 없습니다.

첨부 슬롯

Feature가 이 컴포넌트에 첨부되는 이름 있는 바인딩 지점입니다. 슬롯의 셀렉터는 어떤 Feature가 슬롯을 채울 수 있는지를 제한하고, 슬롯의 inject 목록은 Feature의 자료를 어떻게 전달할 수 있는지를 지정합니다. 필수 슬롯은 인스턴스의 첨부 또는 그 위 범위의 첨부를 통해 모든 인스턴스에서 바인딩되어야 하며, 민감 슬롯은 비밀 자료를 처리하도록 선언됩니다. Feature는 어떤 슬롯도 선언하지 않은 이름으로 첨부될 수도 있습니다.

슬롯셀렉터필수주입민감설명
passwordfeature.aggrega.ai/kind=secret아니요env예Optional database password credential. When attached, supplies POSTGRES_PASSWORD via the credential subsystem. Unattached, compose/timescaledb and helm/timescaledb set POSTGRES_PASSWORD to the development literal `apppass`, which this catalog publishes, so every Release that leaves the slot unattached shares that password. The controller-driven realization owns the database's credentials through infra.credentials and halts the build when this slot is filled.

자체 주입 허용 목록

env

관계

게시된 다른 엔터티와 주고받는 타입 지정 에지입니다. 게시된 대상이 없는 참조는 링크가 아닌 끊어진 에지로 표시됩니다.

사용함

이 엔터티는 카탈로그의 어떤 것도 사용하지 않습니다.

사용됨

Component 개념 레퍼런스 →

Aggrega 카탈로그 — 컴포넌트, 기능, 레시피, 그리고 이를 렌더링하는 플러그인의 공개 인덱스입니다.

공유 Aggrega 디자인 시스템으로 구축되었습니다.

개인정보 보호