Skip to content

OBSDOCS-3386: Logging 6.6.0 release notes - draft#114835

Open
johnwilkins wants to merge 4 commits into
openshift:standalone-logging-docs-6.6from
johnwilkins:OBSDOCS-3386
Open

OBSDOCS-3386: Logging 6.6.0 release notes - draft#114835
johnwilkins wants to merge 4 commits into
openshift:standalone-logging-docs-6.6from
johnwilkins:OBSDOCS-3386

Conversation

@johnwilkins

@johnwilkins johnwilkins commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

Summary

Draft release notes for OpenShift Logging 6.6.0 release. This PR contains the new features/enhancements and deprecations sections. Bug fixes section will be added after JIRA query for fixed issues.

Status: Draft for review

Changes

New modules (3):

  • modules/logging-release-notes-6-6-0.adoc - Main release module with abstract and errata placeholder
  • modules/logging-release-notes-6-6-0-enhancement.adoc - New features and enhancements section
  • modules/logging-release-notes-6-6-0-deprecations.adoc - Deprecations and removals section

Updated files:

  • release_notes/logging-release-notes.adoc - Updated from 6.3 to 6.6, added includes
  • _topic_maps/_topic_map.yml - Updated release notes title to 6.6
  • _attributes/common-attributes.adoc - Added :entra-id: attribute

Features documented (3)

1. Azure Monitor Logs Ingestion API support (OBSDA-804)

  • New azureLogsIngestion output type with Data Collection Rules
  • Replaces deprecated Data Collector API (Microsoft disabling Sept 14, 2026)
  • Enhanced security with Microsoft Entra ID Workload Identity
  • Schema flexibility for custom log schemas (TimeGenerated, ASIM)
  • Migration path with coexistence support

2. GCP Workload Identity Federation authentication (OBSDA-746)

  • Short-lived credentials instead of service account keys
  • Uses ccoctl for GCP service account and IAM setup
  • Pod-injected tokens for WIF token exchange
  • Only supported on OCP on GCP with WIF enabled

3. Metrics collection profiles to reduce collector cardinality (OBSDA-1341)

  • minimal profile for cluster monitoring operator
  • Reduces Prometheus CPU by ~21%, memory by ~33%
  • Excludes high-cardinality histogram metrics
  • Maintains all platform functionality (alerts, dashboards, telemetry, HPA/VPA)
  • Configured via cluster-monitoring-config ConfigMap

Deprecations (1)

Azure Monitor Data Collector API deprecated

  • azureMonitor output type deprecated
  • Microsoft disabling API on September 14, 2026
  • Must migrate to azureLogsIngestion before deadline
  • Coexistence during migration period supported

Still to be added

  • Bug fixes section - Need to query JIRA for fixed issues in Logging 6.6
  • Known issues section (if any)
  • Errata number - Placeholder currently (added during release process)

Approval needed from

Per OBSDOCS-3386 requirements:

  • Engineering lead: Robert
  • Engineering lead: Jeff
  • PM
  • QE
  • Peer review

Related PRs

The features documented here have corresponding docs PRs already merged or in review:

JIRA


Signed-off-by: John Wilkins jowilkin@redhat.com

…ations

Initial draft of release notes for OpenShift Logging 6.6.0 release.

New modules created:
- logging-release-notes-6-6-0.adoc: Main release module with abstract and
  errata placeholder
- logging-release-notes-6-6-0-enhancement.adoc: New features section with
  three major enhancements
- logging-release-notes-6-6-0-deprecations.adoc: Deprecation notice for
  Azure Monitor Data Collector API

Features documented:
1. Azure Monitor Logs Ingestion API support (OBSDA-804)
   - New azureLogsIngestion output type with DCR support
   - Enhanced security with Entra ID Workload Identity
   - Schema flexibility and improved reliability
   - Migration path from deprecated azureMonitor output

2. GCP Workload Identity Federation authentication (OBSDA-746)
   - Short-lived credentials instead of service account keys
   - Uses ccoctl for GCP service account and IAM setup
   - Pod-injected tokens for WIF token exchange
   - Only supported on OCP on GCP with WIF enabled

3. Metrics collection profiles to reduce collector cardinality (OBSDA-1341)
   - Minimal profile reduces Prometheus resource consumption
   - 21% CPU reduction, 33% memory reduction
   - Excludes high-cardinality histogram metrics
   - Maintains all platform functionality

Deprecation:
- Azure Monitor Data Collector API (azureMonitor output type)
- Microsoft disabling API on September 14, 2026
- Migration required to azureLogsIngestion before deadline

Updated assembly:
- Changed title from 6.3 to 6.6
- Added abstract
- Included new enhancement and deprecation modules

Status: Draft for review - bug fixes section still to be added

Signed-off-by: John Wilkins <jowilkin@redhat.com>
Changes:
- Updated _topic_map.yml: Changed "Logging 6.3" to "Logging 6.6"
- Added :entra-id: Microsoft Entra ID attribute to common-attributes.adoc
  (needed for Azure Logs Ingestion feature description)
- Reformatted JIRA ticket links to be inline at end of paragraph with
  parentheses instead of on separate lines (matches existing RN style)

Signed-off-by: John Wilkins <jowilkin@redhat.com>
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 7, 2026
@openshift-ci-robot

openshift-ci-robot commented Jul 7, 2026

Copy link
Copy Markdown

@johnwilkins: This pull request references OBSDOCS-3386 which is a valid jira issue.

Details

In response to this:

Summary

Draft release notes for OpenShift Logging 6.6.0 release. This PR contains the new features/enhancements and deprecations sections. Bug fixes section will be added after JIRA query for fixed issues.

Status: Draft for review

Changes

New modules (3):

  • modules/logging-release-notes-6-6-0.adoc - Main release module with abstract and errata placeholder
  • modules/logging-release-notes-6-6-0-enhancement.adoc - New features and enhancements section
  • modules/logging-release-notes-6-6-0-deprecations.adoc - Deprecations and removals section

Updated files:

  • release_notes/logging-release-notes.adoc - Updated from 6.3 to 6.6, added includes
  • _topic_maps/_topic_map.yml - Updated release notes title to 6.6
  • _attributes/common-attributes.adoc - Added :entra-id: attribute

Features documented (3)

1. Azure Monitor Logs Ingestion API support (OBSDA-804)

  • New azureLogsIngestion output type with Data Collection Rules
  • Replaces deprecated Data Collector API (Microsoft disabling Sept 14, 2026)
  • Enhanced security with Microsoft Entra ID Workload Identity
  • Schema flexibility for custom log schemas (TimeGenerated, ASIM)
  • Migration path with coexistence support

2. GCP Workload Identity Federation authentication (OBSDA-746)

  • Short-lived credentials instead of service account keys
  • Uses ccoctl for GCP service account and IAM setup
  • Pod-injected tokens for WIF token exchange
  • Only supported on OCP on GCP with WIF enabled

3. Metrics collection profiles to reduce collector cardinality (OBSDA-1341)

  • minimal profile for cluster monitoring operator
  • Reduces Prometheus CPU by ~21%, memory by ~33%
  • Excludes high-cardinality histogram metrics
  • Maintains all platform functionality (alerts, dashboards, telemetry, HPA/VPA)
  • Configured via cluster-monitoring-config ConfigMap

Deprecations (1)

Azure Monitor Data Collector API deprecated

  • azureMonitor output type deprecated
  • Microsoft disabling API on September 14, 2026
  • Must migrate to azureLogsIngestion before deadline
  • Coexistence during migration period supported

Still to be added

  • Bug fixes section - Need to query JIRA for fixed issues in Logging 6.6
  • Known issues section (if any)
  • Errata number - Placeholder currently (added during release process)

Approval needed from

Per OBSDOCS-3386 requirements:

  • Engineering lead: Robert
  • Engineering lead: Jeff
  • PM
  • QE
  • Peer review

Related PRs

The features documented here have corresponding docs PRs already merged or in review:

JIRA


Signed-off-by: John Wilkins jowilkin@redhat.com

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci Bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Jul 7, 2026
@ocpdocs-previewbot

ocpdocs-previewbot commented Jul 7, 2026

Copy link
Copy Markdown

🤖 Wed Jul 08 03:48:36 - Prow CI generated the docs preview:
https://114835--ocpdocs-pr.netlify.app
Complete list of updated preview URLs: artifacts/updated_preview_urls.txt

Added fixed issues module documenting 19 bug fixes resolved in this release.

JIRA query used:
project = "OpenShift Logging" AND type in (Bug) AND fixVersion in ("Logging 6.6.0") AND resolution in (Done) ORDER BY key ASC

Bug fixes organized by severity/impact:
- Blocker issues (5): LOG-9422, LOG-9444, LOG-9470, LOG-9539, LOG-9566
- Critical issues (2): LOG-9389, LOG-9542
- Major issues (3): LOG-9384, LOG-9448, LOG-9513, LOG-9540
- Normal issues (7): LOG-4914, LOG-9359, LOG-9383, LOG-9391, LOG-9423
- Minor issues (3): LOG-8509, LOG-9367, LOG-9400

Key areas addressed:
- Azure Logs Ingestion API issues (payload size, reserved keywords, hostname)
- GCP Workload Identity Federation token refresh
- LokiStack tuning and crash loop issues
- CloudWatch payload limits
- Operator reconciliation after upgrade
- Metrics accuracy (loki_build_info, lokistack_info)
- Compactor STS permissions
- Proxy configuration handling
- API documentation improvements

Each bug fix follows the pattern:
"Previously, [problem]. With this release, [solution]. (JIRA-LINK)"

Signed-off-by: John Wilkins <jowilkin@redhat.com>
@openshift-ci openshift-ci Bot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Jul 8, 2026
Added feature description for improved high availability for LokiStack
ingestion (LOG-9352).

Feature:
- 1x.extra-small and 1x.small sizes now deploy 3 ingester replicas
  instead of 2
- Ensures RF+1 replicas (replication factor + 1) for HA
- Prevents log ingestion interruption during pod restarts or node failures
- Resources redistributed within existing envelope (no additional resources)
- Aligns with HA configuration already used by 1x.pico and 1x.medium
- Resolves operator warning condition about non-HA configuration

Related:
- Engineering JIRA: LOG-9352
- Docs PR: openshift#114090 (OBSDOCS-3530)

Signed-off-by: John Wilkins <jowilkin@redhat.com>
@openshift-ci

openshift-ci Bot commented Jul 8, 2026

Copy link
Copy Markdown

@johnwilkins: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants