Repository navigation
Conversation
…cloud integrations - Introduced Terraform modules to support telemetry across AWS, Azure, and GCP. - Provisioned object stores (S3 bucket, GCS bucket, Azure Blob container). - Set up cloud-specific workload identities (EKS Pod Identity, Azure Workload Identity, GKE Workload Identity). - Added Helm charts and templates for deploying Telemetry components (metrics, logs, traces). - Integrated `ServiceMonitor` CRDs for monitoring telemetry metrics. - Enhanced compatibility with Prometheus, Loki, and Tempo. - Updated documentation for deployment steps and configuration options.
…ection - Added `plural-telemetry-agent` catalog to deploy Grafana Alloy on all clusters to ship metrics, logs, and traces to a Plural Telemetry instance. - Configured `alloy-operator` and `alloy` Helm charts for Alloy CRDs and telemetry collection. - Introduced global services for cluster metrics, events, and logs shipping. - Enhanced documentation with deployment details, configuration options, and security notes. - Updated test contracts and contexts to include telemetry agent setup.
- Removed alloy-related `ServiceMonitor` configurations for metrics, logs, and traces. - Deleted Helm charts and configurations for Grafana Alloy in telemetry agent setup. - Dropped `plural-telemetry-agent` catalog for deploying global Alloy services. - Updated `README` to reflect changes in telemetry agent usage and configuration. - Adjusted `telemetry.yaml.liquid` to disable automatic deployment of Alloy agents. - Cleaned up test contexts, output directories, and associated configurations.
- Changed `git.ref` in `plural-telemetry.yaml` to point to a feature branch for testing purposes. - Added comment to revert to `main` after testing completion.
- Eliminated telemetry stacks for Azure, GCP, and management clusters, including related infrastructure and Helm configurations. - Removed Grafana Alloy deployment configurations (Helm charts, templates, and secrets). - Cleaned up Terraform resources for Azure-specific storage, workloads, and IAM roles. - Deleted associated test scaffolds, templates, and generated outputs.
…port - Updated service and release names from `telemetry-stack` to `telemetry` for AWS, GCP, Azure, and management configurations. - Renamed global services from `telemetry-alloy` to `telemetry-agent` and `telemetry-alloy-operator` to `telemetry-agent-operator`. - Added AKS-specific podAnnotations to `controller` and `kube-state-metrics` services for compatibility. - Updated documentation to reflect new naming conventions.
… and metrics - Added changes to `bootstrap/settings.yaml` to configure the Console's `logging` driver (LOKI) and `prometheusConnection` to point to Telemetry. - Enabled overriding of existing Elasticsearch/Victoria Metrics configurations with Telemetry-specific settings. - Updated catalog documentation to reflect automatic PR generation process for settings adjustments. - Ensured existing unused settings remain untouched while integrating Telemetry.
- Dropped versioning and retention lifecycle rules from Terraform configurations for S3 and GCP buckets. - Removed `enable_versioning` and `version_retention_days` variables across AWS and GCP Terraform modules. - Updated catalog documentation and PR-generated content to reflect the removal of versioning and retention features. - Adjusted examples to clarify that versioning must be manually configured in an infra repo, if required.
- Updated `telemetry-operator` and `telemetry-stack` Helm chart versions to use `0.1.x` for flexibility in minor version upgrades.
- Updated Helm `version` fields for `telemetry-operator` and `telemetry-stack` to use "0.1.x" across AWS, GCP, and Azure scaffolds. - Ensured consistency in versioning to allow for patch updates without requiring file changes.
- Introduced Terraform support to create unique Azure storage accounts for telemetry data with hardened configurations. - Updated storage account settings for TLS 1.2, private network access, and no cross-tenant replication. - Removed `storageAccount` variable in favor of auto-generated storage account names based on subscription, resource group, and cluster. - Updated documentation to reflect storage account creation and customization process. - Increased `azurerm` provider version requirement to `>= 4.9`.
michaeljguarino
approved these changes
Oct 26, 2026
floreks
deleted the
sebastian/prod-5328-add-plural-telemetry-service-catalog-entry
branch
October 27, 2026 16:07
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.