You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/workflows/build-artifact/ARTIFACT_INVENTORY.template
+29-30Lines changed: 29 additions & 30 deletions
Original file line number
Diff line number
Diff line change
@@ -5,64 +5,63 @@ The following tables provide information about the container images and Helm cha
5
5
* pre-pull container images
6
6
* deploy into an air-gapped Kubernetes cluster
7
7
8
-
**Note:** For more information about deploying in an air-gapped environment, refer to
8
+
**Note:** For more information about deploying in an air-gapped environment, refer to
9
9
[Configure SAS Viya Monitoring for Kubernetes for an Air-Gapped Environment](https://documentation.sas.com/?cdcId=obsrvcdc&cdcVersion=v_003&docsetId=obsrvdply&docsetTarget=n0auhd4hutsf7xn169hfvriysz4e.htm#n0grd8g2pkfglin12bzm3g1oik2p).
10
10
11
11
## Table 1. Container Images
12
12
13
13
This table provides the fully qualified container-image names for the components of SAS Viya Monitoring for Kubernetes.
14
-
These names use the following format:
14
+
These names use the following format:
15
15
registry/repository/image_name:version
16
16
17
17
| Subsystem| Component | Fully Qualified Container-Image Name (registry/repository/image_name:version)|
Copy file name to clipboardExpand all lines: ARTIFACT_INVENTORY.md
+29-30Lines changed: 29 additions & 30 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,64 +5,63 @@ The following tables provide information about the container images and Helm cha
5
5
* pre-pull container images
6
6
* deploy into an air-gapped Kubernetes cluster
7
7
8
-
**Note:** For more information about deploying in an air-gapped environment, refer to
8
+
**Note:** For more information about deploying in an air-gapped environment, refer to
9
9
[Configure SAS Viya Monitoring for Kubernetes for an Air-Gapped Environment](https://documentation.sas.com/?cdcId=obsrvcdc&cdcVersion=v_003&docsetId=obsrvdply&docsetTarget=n0auhd4hutsf7xn169hfvriysz4e.htm#n0grd8g2pkfglin12bzm3g1oik2p).
10
10
11
11
## Table 1. Container Images
12
12
13
13
This table provides the fully qualified container-image names for the components of SAS Viya Monitoring for Kubernetes.
14
-
These names use the following format:
14
+
These names use the following format:
15
15
registry/repository/image_name:version
16
16
17
17
| Subsystem| Component | Fully Qualified Container-Image Name (registry/repository/image_name:version)|
18
18
|----|----|----|
19
-
| Logging | Fluent Bit | cr.fluentbit.io/fluent/fluent-bit:4.0.2 |
Copy file name to clipboardExpand all lines: CHANGELOG.md
+2-3Lines changed: 2 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,9 +1,8 @@
1
1
# SAS Viya Monitoring for Kubernetes
2
2
3
-
## Unreleased
3
+
## Version 1.2.39 (20JUN2025)
4
4
***Metrics**
5
-
*[FIX] Resolved issue causing "missing datasource" errors on a number of Grafana dashboards.
6
-
5
+
*[FIX] Resolved an issue where some Grafana dashboards failed to load due to hardcoded Prometheus datasource references. In the previous release, the Prometheus datasource UID was standardized to `prometheus` to support the Grafana alerting system and provisioned alerts. However, some dashboards still contained hardcoded UIDs pointing to the old datasource configuration. This fix updates those references to use the correct UID, ensuring all dashboards now load and function as expected.
0 commit comments