Skip to content

Commit

Permalink
chore: Remove OTel LogPipeline-related data from docs and Telemetry C…
Browse files Browse the repository at this point in the history
…RD (#1654)
  • Loading branch information
TeodorSAP authored Dec 12, 2024
1 parent f32da99 commit 9b6b497
Show file tree
Hide file tree
Showing 4 changed files with 1 addition and 45 deletions.
1 change: 1 addition & 0 deletions Makefile
Original file line number Diff line number Diff line change
Expand Up @@ -105,6 +105,7 @@ manifests: $(CONTROLLER_GEN) $(YQ) $(YAMLFMT) ## Generate WebhookConfiguration,
$(YQ) eval 'del(.. | select(has("x-kubernetes-validations"))."x-kubernetes-validations"[] | select(.rule|contains("otlp")) )' -i ./config/crd/bases/telemetry.kyma-project.io_logpipelines.yaml
## Remove empty x-kubernetes-validations arrays from logpipeline crd that can be caused by previous yq manipulations
$(YQ) eval 'del(.. | select(select(has("x-kubernetes-validations"))."x-kubernetes-validations" | length == 0)."x-kubernetes-validations")' -i ./config/crd/bases/telemetry.kyma-project.io_logpipelines.yaml
$(YQ) eval 'del(.. | select(has("log")).log)' -i ./config/crd/bases/operator.kyma-project.io_telemetries.yaml
$(YAMLFMT)

.PHONY: manifests-dev
Expand Down
27 changes: 0 additions & 27 deletions config/crd/bases/operator.kyma-project.io_telemetries.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -49,33 +49,6 @@ spec:
spec:
description: TelemetrySpec defines the desired state of Telemetry
properties:
log:
description: LogSpec defines the behavior of the log gateway
properties:
gateway:
properties:
scaling:
description: Scaling defines which strategy is used for scaling the gateway, with detailed configuration options for each strategy type.
properties:
static:
description: |-
Static is a scaling strategy enabling you to define a custom amount of replicas to be used for the gateway. Present only if Type =
StaticScalingStrategyType.
properties:
replicas:
description: Replicas defines a static number of Pods to run the gateway. Minimum is 1.
format: int32
minimum: 1
type: integer
type: object
type:
description: Type of scaling strategy. Default is none, using a fixed amount of replicas.
enum:
- Static
type: string
type: object
type: object
type: object
metric:
description: MetricSpec defines the behavior of the metric gateway
properties:
Expand Down
6 changes: 0 additions & 6 deletions docs/user/resources/01-telemetry.md
Original file line number Diff line number Diff line change
Expand Up @@ -77,12 +77,6 @@ For details, see the [Telemetry specification file](https://github.com/kyma-proj
| Parameter | Type | Description |
| ---- | ----------- | ---- |
| **log** | object | LogSpec defines the behavior of the log gateway |
| **log.​gateway** | object | |
| **log.​gateway.​scaling** | object | Scaling defines which strategy is used for scaling the gateway, with detailed configuration options for each strategy type. |
| **log.​gateway.​scaling.​static** | object | Static is a scaling strategy enabling you to define a custom amount of replicas to be used for the gateway. Present only if Type = StaticScalingStrategyType. |
| **log.​gateway.​scaling.​static.​replicas** | integer | Replicas defines a static number of Pods to run the gateway. Minimum is 1. |
| **log.​gateway.​scaling.​type** | string | Type of scaling strategy. Default is none, using a fixed amount of replicas. |
| **metric** | object | MetricSpec defines the behavior of the metric gateway |
| **metric.​gateway** | object | |
| **metric.​gateway.​scaling** | object | Scaling defines which strategy is used for scaling the gateway, with detailed configuration options for each strategy type. |
Expand Down
12 changes: 0 additions & 12 deletions docs/user/resources/02-logpipeline.md
Original file line number Diff line number Diff line change
Expand Up @@ -186,19 +186,7 @@ The status of the LogPipeline is determined by the condition types `AgentHealthy
| AgentHealthy | False | AgentNotReady | Failed to get DaemonSet |
| AgentHealthy | False | AgentNotReady | Pod is in the pending state because container: `container name` is not running due to: `reason`. Please check the container: `container name` logs. |
| AgentHealthy | False | AgentNotReady | Pod is in the failed state due to: `reason` |
| GatewayHealthy | True | GatewayReady | Log gateway Deployment is ready |
| GatewayHealthy | True | RolloutInProgress | Pods are being started/updated |
| GatewayHealthy | False | GatewayNotReady | No Pods deployed |
| GatewayHealthy | False | GatewayNotReady | Failed to list ReplicaSets: `reason` |
| GatewayHealthy | False | GatewayNotReady | Failed to fetch ReplicaSets: `reason` |
| GatewayHealthy | False | GatewayNotReady | Pod is not scheduled: `reason` |
| GatewayHealthy | False | GatewayNotReady | Pod is in the pending state because container: `container name` is not running due to: `reason`. Please check the container: `container name` logs. |
| GatewayHealthy | False | GatewayNotReady | Pod is in the failed state due to: `reason` |
| GatewayHealthy | False | GatewayNotReady | Deployment is not yet created |
| GatewayHealthy | False | GatewayNotReady | Failed to get Deployment |
| GatewayHealthy | False | GatewayNotReady | Failed to get latest ReplicaSets |
| ConfigurationGenerated | True | AgentConfigured | LogPipeline specification is successfully applied to the configuration of Fluent Bit agent |
| ConfigurationGenerated | True | GatewayConfigured | LogPipeline specification is successfully applied to the configuration of Log gateway |
| ConfigurationGenerated | True | TLSCertificateAboutToExpire | TLS (CA) certificate is about to expire, configured certificate is valid until YYYY-MM-DD |
| ConfigurationGenerated | False | EndpointInvalid | HTTP output host invalid: `reason` |
| ConfigurationGenerated | False | ReferencedSecretMissing | One or more referenced Secrets are missing: Secret 'my-secret' of Namespace 'my-namespace' |
Expand Down

0 comments on commit 9b6b497

Please sign in to comment.