Skip to content

[enterprise-4.12] OBSDOCS-1147: Bugfix - update storage secret table #91665

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 4, 2025
Merged

[enterprise-4.12] OBSDOCS-1147: Bugfix - update storage secret table #91665

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
88 changes: 88 additions & 0 deletions modules/distr-tracing-tempo-config-default.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -59,3 +59,91 @@ managementState: managed # <21>
<19> Configures operands to handle telemetry data.
<20> Configures search capabilities.
<21> Defines whether or not this CR is managed by the Operator. The default value is `managed`.

.`TempoStack` CR parameters
[options="header"]
[cols="a, a, a, a"]
|===
|Parameter |Description |Values |Default value

|`apiVersion:`
|API version to use when creating the object.
|`tempo.grafana.com/v1alpha1`
|`tempo.grafana.com/v1alpha1`

|`kind:`
|Defines the kind of the Kubernetes object to create.
|`tempo`
|

|`metadata:`
|Data that uniquely identifies the object, including a `name` string, `UID`, and optional `namespace`.
|
|{product-title} automatically generates the `UID` and completes the `namespace` with the name of the project where the object is created.

|`name:`
|Name for the object.
|Name of your TempoStack instance.
|`tempo-all-in-one-inmemory`

|`spec:`
|Specification for the object to be created.
|Contains all of the configuration parameters for your TempoStack instance. When a common definition for all Tempo components is required, it is defined under the `spec` node. When the definition relates to an individual component, it is placed under the `spec.template.<component>` node.
|N/A

|`resources:`
|Resources assigned to the TempoStack instance.
|
|

|`storageSize:`
|Storage size for ingester PVCs.
|
|

|`replicationFactor:`
|Configuration for the replication factor.
|
|

|`retention:`
|Configuration options for retention of traces.
|
|

|`storage:`
|Configuration options that define the storage.
|
|

|`template.distributor:`
|Configuration options for the Tempo distributor.
|
|

|`template.ingester:`
|Configuration options for the Tempo ingester.
|
|

|`template.compactor:`
|Configuration options for the Tempo compactor.
|
|

|`template.querier:`
|Configuration options for the Tempo querier.
|
|

|`template.queryFrontend:`
|Configuration options for the Tempo query frontend.
|
|

|`template.gateway:`
|Configuration options for the Tempo gateway.
|
|

|===