Version 1.2.49 - May 8 2026

Version 1.2.49 (08MAY2026)

• Overall
  • [CHANGE] Support for Helm 4.x has been added. As part of this change, the --force-conflicts option
    will be used when deploying using Helm 4.x. During an update-in-place, this can overwrite some
    post-deployment changes to Kubernetes resources implemented with kubectl patch commands. If you have
    made such changes, you should implement these changes via the appropriate Helm user-values yaml file
    prior to the update (if possible) or re-apply the patches manually after the upgrade.
  • [TASK] The various user-values yaml and user.env files included in the project repository, including
    those in the samples sub-directories, were reviewed and validated with obsolete values removed.
  • [TASK] Documentation links in the various markdown files within the project reposistory were reviewed
    and revised to eliminate the use of version-specific pointers when not appropriate.
• Metrics
  • [FIX] The CAS Memory Usage High sample alert now uses container_memory_working_set_bytes
    summed across all CAS server pods (controller, backup controller, and workers) instead of
    cas_node_mem_size_bytes - cas_node_mem_free_bytes, which reported node/VM physical memory
    rather than actual CAS memory consumption
• Tracing
  • [CHANGE] Fluent Bit tracing configuration updated to improve reliability and performance:
    increased input buffer sizes, enabled gzip compression on output, set retry limit to 5,
    added worker threads, and configured connection/IO timeouts
  • [CHANGE] Tempo ingester configured with flush_all_on_shutdown to prevent trace data loss
    on restart, reduced max_block_duration to 5m to lower memory pressure, and set
    replication_factor to 1 for single-instance deployments; compactor block_retention
    aligned to 24h to match retention setting
  • [CHANGE] Tempo datasource for Grafana is now provisioned via the datasource sidecar mechanism
    (ConfigMap with grafana_datasource=1 label) consistent with how other datasources are handled,
    rather than being passed as a Helm values overlay
  • [CHANGE] Removed Grafana feature toggles tempoSearch and tempoBackendSearch as they are no
    longer needed in the current Grafana version
  • [CHANGE] OpenShift deployments now use the standard values-tempo.yaml instead of a separate
    OpenShift-specific file
  • [CHANGE] Tempo metricsGenerator remoteWriteUrl now resolved dynamically from MON_NS at
    deploy time rather than being hardcoded to the monitoring namespace

Version 1.2.48 - April 3 2026

Version 1.2.48 (03APR2026)

Overall

• [CHANGE] The Contributor Agreement has been revised to clarify the need to sign-off on contributions and to disclose the use of generative AI in their creation.
• [CHANGE] Support for Kubernetes 1.26 has been dropped

Logging

• [UPGRADE] OpenSearch and OpenSearch Dashboards upgraded from 2.19.4 to 3.4.0
• [UPGRADE] OpenSearch Helm chart upgraded from 2.36.0 to 3.4.0
• [UPGRADE] OpenSearch Dashboards Helm chart upgraded from 2.32.0 to 3.4.0
• [UPGRADE] Fluent Bit upgraded from 4.2.0 to 4.2.3
• [UPGRADE] Fluent Bit Helm chart upgraded from 0.54.0 to 0.56.0
• [UPGRADE] Elasticsearch Exporer upgraded from 1.9.0 to 1.10.0
• [UPGRADE] Elasticsearch Exporer Helm chart upgraded from 7.0.0 to 7.2.1
• [UPGRADE] OpenSearch Data Source Plugin to Grafana upgraded from 2.32.4 to 2.32.6

Version 1.2.47 - March 6th 2026

Version 1.2.47 (06MAR2026)

• Overall
  • [ANNOUNCEMENT] All development work on the Ingress NGINX project, including bug fixes and
    security updates, is expected to end by the end of March 2026. For information,
    see Ingress NGINX Retirement: What You Need to Know.
    While existing deployments will continue to function and new deployments are possible,
    continued use of the ingress-nginx ingress controller poses security risks. SAS Viya Monitoring for
    Kubernetes recommends moving to Contour as the replacement ingress controller.
  • [DEPRECATION] The existing ingress sample focused on using
    ingress-nginx is now deprecated. Users can refer to the Contour sample
    for information on manually configuring Contour as the ingress controller.
  • [FEATURE] The auto-generation of ingress configurations now supports Contour (in addition to
    the existing support for ingress-nginx). To enable ingress via Contour, set the environment
    variable INGRESS_TYPE to contour. To use ingress-nginx, set INGRESS_TYPE to ingress-nginx.
    Setting the environment variable AUTOGENERATE_INGRESS to 'true' and providing a value for
    the environment variable BASE_DOMAIN are also required. As with ingress-nginx, support for
    both host-based and path-based routing are supported with Contour as well. A new option for
    how the Kubernetes Secret resources, used to hold the ingress TLS certs, are handled is available.
    See the
    Configure Ingress Access to Web Applications
    topic within the Help Center documentation for further information.
• Metrics
  • [FEATURE] New PodMonitor resources are deployed to enable the collection
    of metrics from Contour if it is detected on the Kubernetes cluster during the
    deployment process.
  • [FEATURE] Two Grafana dashboards focused on Contour and Envoy metrics are now deployed
    if Contour is detected on the Kubernetes cluster during the deployment process.
  • [CHANGE] Following the migration of the Grafana and Tempo Helm charts to the
    Grafana Community Kubernetes Helm Charts project,
    our project now deploys these charts from that project's repository.
  • [CHANGE] Following the retirement of the ingress-nginx maintained variant of the
    kube-webhook-certgen, the Prometheus Community Helm charts
    moved to a new actively maintained replacement.
    Therefore, our project, in turn, now deploys the component from this new source as well.
  • [UPGRADE] Kube-Prometheus Stack Helm chart has been upgraded from 78.4.0 to 81.5.2
  • [UPGRADE] Grafana Helm Chart (for OpenShift deployments) has been upgraded fom 9.4.5 to 11.0.1
  • [UPGRADE] Prometheus Pushgateway Helm chart has been upgraded from 3.4.1 to 3.6.0
  • [UPGRADE] Alertmanager has been upgraded from 0.28.1 to 0.31.0
  • [UPGRADE] The config-reloader has been upgraded from 0.86.1 to 0.88.1
  • [UPGRADE] Grafana has been upgraded from 12.2.0 to 12.3.2
  • [UPGRADE] The k8s-sidecar has been upgraded from 1.30.9 to 2.5.0
  • [UPGRADE] Kube-State-Metrics has been upgraded from 2.17.0 to 2.18.0
  • [UPGRADE] Node-Exporter has been upgraded from 1.9.1 to 1.10.2
  • [UPGRADE] Prometheus has been upgraded from 3.7.1 to 3.9.1
  • [UPGRADE] Prometheus Pushgateway has been upgraded from 1.11.1 to 1.11.2
  • [UPGRADE] Prometheus Operator has been upgraded from 0.86.1 to 0.88.1
  • [UPGRADE] OpenSearch Data Source Plugin to Grafana upgraded from 2.31.1 to 2.32.4
• Logging
  • [CHANGE] Improve handling of Envoy (Contour) log messages

Version 1.2.46 - February 6th 2026

Version 1.2.46 (06FEB2026)

• Overall
  • [FEATURE] A new sample demonstrates how to use Contour HTTPProxy resources to
    provide access to the web applications, such as OpenSearch Dashboards and Grafana,
    deployed as part of this project. Refer to the Contour Sample README
    for more information.
• Logging
  • [FEATURE] A new script, setup-airgap automates many of the setup preparations needed prior
    to deploying into an airgap environment. This setup includes populating the container registry
    (with both images and helm charts) and downloading the necessary files (e.g. CRDs and Grafana
    plugin files) into the appropriate sub-directories in the $USER_DIR directory. The location
    of the private container registry and the associated credentials need to be identified by
    setting the environment variables AIRGAP_REGISTRY, AIRGAP_REGISTRY_USERNAME, and
    AIRGAP_REGISTRY_PASSWORD prior to running the script, preferably in the $USER_DIR/user.env
    file. Refer to the Prepare to Deploy SAS Viya Monitoring for Kubernetes in an Air Gap Environment documentation for more info.
  • [FIX] The logging/bin/onboard.sh script no longer fails when the -p parameter is set
• Metrics
  • [FEATURE] Support for automatically defining SMTP server configuration (permitting Grafana
    to send e-mails) has been extended to OpenShift clusters
  • [FEATURE] Support for deploying Grafana alerts defined in files from the $USER_DIR/monitoring/alerting
    sub-directory has been extended to OpenShift clusters
  • [FIX] Corrected behavior on non-OpenShift clusters which had inappropriately required a Kubernetes
    Secret resource be created when automatically defining the SMTP server configuration

Version 1.2.45 - December 16th 2025

Version 1.2.45 (16DEC2025)

• Overall
  • [CHANGE] Use with Kubernetes versions prior to 1.26 produces a WARNING message
  • [CHANGE] Drop support for OpenShift 4.12; the minimum supported version of OpenShift is now 4.14
• Logging
  • [UPGRADE] OpenSearch and OpenSearch Dashboards upgraded from 2.19.3 to 2.19.4
  • [UPGRADE] OpenSearch Helm chart upgraded from 2.35.0 to 2.36.0
  • [UPGRADE] OpenSearch Dashboards Helm chart upgraded from 2.31.0 to 2.32.0
  • [UPGRADE] Fluent Bit upgraded from 4.0.8 to 4.2.0
  • [UPGRADE] Fluent Bit Helm chart upgraded from 0.52.0 to 0.54.0
  • [UPGRADE] Elasticsearch Exporer Helm chart upgraded from 6.7.2 to 7.0.0
  • [UPGRADE] OpenSearch Data Source Plugin to Grafana upgraded from 2.31.1 to 2.32.1
• Tracing
  • [UPGRADE] Upgraded Tempo from 2.7.0 to 2.9.0
  • [UPGRADE] Upgraded Tempo Helm chart from 1.18.1 to 1.24.1

Version 1.2.44 - November 18th 2025

Version 1.2.44 (18NOV2025)

• Metrics
  • [UPGRADE] Kube-Prometheus Stack Helm chart has been upgraded from 75.15.0 to 78.4.0
  • [UPGRADE] Grafana Helm Chart (for OpenShift deployments) has been upgraded fom 9.3.0 to 9.4.5.
  • [UPGRADE] Prometheus Pushgateway Helm chart has been upgraded from 3.4.0 to 3.4.1.
  • [UPGRADE] The config-reloader has been upgraded from 0.83.0 to 0.86.1.
  • [UPGRADE] Grafana has been upgraded from 12.1.0 to 12.2.0.
  • [UPGRADE] The k8s-sidecar has been upgraded from 1.30.3 to 1.30.9.
  • [UPGRADE] Kube-State-Metrics has been upgraded from 2.16.0 to 2.17.0.
  • [UPGRADE] Prometheus has been upgraded from 3.5.0 to 3.7.1.
  • [UPGRADE] Prometheus Operator has been upgraded from 0.83.0 to 0.86.1.
  • [UPGRADE] OpenSearch Data Source Plugin to Grafana upgraded from 2.29.1 to 2.31.1
• Logging
  • [FIX] Log messages from Alertmanger pod redirected to OpenSearch viya_ops-* (rather than viya_logs-*) index
  • [CHANGE] All OpenShift-specific scripts now fail when run on non-OpenShift clusters

Version 1.2.43 - October 10th 2025

Version 1.2.43 (10OCT2025)

• Metrics
  • [FEATURE] A new sample demonstrates how to extend SAS Viya Monitoring
    for Kubernetes to monitor the SingleStore instance that is embedded within
    SAS SpeedyStore. This allows administrators to monitor their SingleStore
    cluster using the same Grafana instance that they use to monitor the rest
    of their SAS Viya deployment. Refer to the SAS SpeedyStore Sample README
    for more information.
• Logging
  • [CHANGE] We have changed how we handle defining extra volumes for the Fluent Bit log collecting pods.
    This change should be transparent to virtually all users. However, if you define additional volumes for
    these pods, you will need to update your configuration to eliminate references to certain default volumes.
    Refer to the updated samples/generic-base/logging/user-values-fluent-bit-opensearch.yaml
    file for details and adjust the contents of your $USER_DIR/logging/user-values-fluent-bit-opensearch.yaml
    file accordingly.

Version 1.2.42 - September 16th 2025

Version 1.2.42 (16SEP2025)

• Logging

  • [FIX] Corrected handling of unavailable API endpoint in deploy_opensearch_content.sh
  • [FIX] Log messages from Prometheus Operator pod redirected to OpenSearch viya_ops-* (rather than viya_logs-*) index
  • [UPGRADE] OpenSearch and OpenSearch Dashboards upgraded from 2.19.2 to 2.19.3
  • [UPGRADE] OpenSearch Helm chart upgraded from 2.34.0 to 2.35.0.
  • [UPGRADE] OpenSearch Dashboards Helm chart upgraded from 2.30.0 to 2.31.0
  • [UPGRADE] Fluent Bit upgraded from 4.0.2 to 4.0.8
  • [UPGRADE] Fluent Bit Helm chart upgraded from 0.49.0 to 0.52.0
  • [UPGRADE] Elasticsearch Exporter Helm chart upgraded from 6.7.2 to 7.0.0
  • [UPGRADE] OpenSearch Data Source Plugin to Grafana upgraded from 2.28.0 to 2.29.1

• Metrics

  • [FEATURE] Automatically define the SMTP server configuration to permit Grafana to send e-mails.
    If enabled (by setting AUTOGENERATE_SMTP to 'true'), this optional feature allows admins to define
    email-based contact points for alerts. Users need to provide connection information via the environment
    variables: SMTP_SERVER, SMTP_PORT, SMTP_FROM_ADDRESS and SMTP_FROM_NAME. See Configure Email Settings for Grafana Alerts
    for more information.
  • [CHANGE] The Grafana alerts targeting SAS Viya that previously were provided by default have been moved
    to the samples directory. Given the variability of SAS Viya environments, these alerts are now optional.
    They can be copied to USER_DIR/monitoring/alerting and customized to fit the SAS Viya environment prior
    to deployment. They have also been split into separate files for easier customization. See the Alerting Samples README for more details.

Version 1.2.41 - August 19th 2025

Version 1.2.41 (19AUG2025)

• Metrics
  • [UPGRADE] Kube-Prometheus Stack Helm chart has been upgraded from 70.8.0 to 75.15.0.
  • [UPGRADE] Grafana Helm Chart (for OpenShift deployments) has been upgraded fom 8.13.1 to 9.3.0.
  • [UPGRADE] Prometheus Pushgateway Helm chart has been upgraded from 3.1.0 to 3.4.0.
  • [UPGRADE] The config-reloader has been upgraded from 0.81.0 to 0.83.0.
  • [UPGRADE] Grafana has been upgraded from 11.6.1 to 12.1.0.
  • [UPGRADE] The k8s-sidecar has been upgraded from 1.30.0 to 1.30.3.
  • [UPGRADE] Kube-State-Metrics has been upgraded from 2.15.0 to 2.16.0.
  • [UPGRADE] Prometheus has been upgraded from 3.2.1 to 3.5.0.
  • [UPGRADE] Prometheus Operator has been upgraded from 0.81.0 to 0.83.0.
  • [UPGRADE] OpenSearch Data Source Plugin to Grafana upgraded from 2.26.1 to 2.28.0

Version 1.2.40 (15JULY2025)

Version 1.2.40 (15JULY2025)

• Overall
  • [REMOVAL] Removed the previously deprecated TLS sample. Deploying with TLS enabled has been the default since version
    1.2.15 (18JUL23).