1.2.22 - February 13th 2024

Version 1.2.22 (13FEB2024)

• Overall

  • [TASK] Refactored how container image and Helm chart version information is handled to permit automatically generating this information from files. Note
    that this change does NOT alter how users provide this information should they wish to change it. User should continue to include this information in the
    appropriate user values yaml file within their USER_DIR directory. However, specifying a Helm chart or container image version different than the default
    should rarely be necessary or appropriate.

• Metrics

  • [ANNOUNCEMENT] In an upcoming release, we will be making a BREAKING CHANGE related to how the connection between Prometheus and
    Alertmanager is configured. Currently, we define the prometheusSpec.alertingEndpoints.* keys programmatically; but, after this change,
    we will expect users to provide this information when they define the ingress resources associated with the metric monitoring applications
    (e.g. Grafana, Prometheus and Alertmanger). This will consolidate the connection and ingress configuration in the same place, the
    $USER_DIR/monitoring/user-values-prom-operator.yaml file. This change will only be a BREAKING CHANGE when updating an existing deployment
    that uses ingress to reach the metric monitoring applications or when using an ingress configurations based on the previous ingress sample.
    The ingress sample has been updated to work with the new approach (see note below). If you do not update your configuration before the
    change is released, Prometheus will not be able to send alerts to Alertmanger after the change. The release of this change is tenatively
    scheduled for our 1.2.23 release (expected mid-March).
  • [CHANGE] The ingress samples have been updated to accomodate an upcoming, potentially breaking, change (see note above). These updated
    ingress samples can be used now, prior to the change being released, since they are compatible with both the existing and new behavior.
  • [FIX] Replaced obsolete container image name for OpenShift oauth proxy container

• Logging

  • [REMOVAL] The deploy_eventrouter.sh script has been removed. The Event Router component it deployed
    is no longer actively developed and was replaced with a Fluent Bit deployment focused on collecting Kubernetes events in our 1.2.19 release.

• Tracing

  • [FEATURE] By default, the Tempo datasource will now add the logs datasource connection so traces and logs can be connected.