Releases: sassoftware/viya4-monitoring-kubernetes
Releases · sassoftware/viya4-monitoring-kubernetes
1.0.5 - March 15, 2021
-
Overall
- There is a new document discussing support of various
Cloud providers
- There is a new document discussing support of various
-
Monitoring
- [FEATURE] The
monitoring/bin/deploy_dashboards.sh
script now accepts a
file or directory argument to deploy user-provided dashboards - [FEATURE] A new
$USER_DIR/monitoring/dashboards
directory is now
supported to supply user-provided dashboards at deployment time - [FEATURE] The new CloudWatch sample provides
instructions on configuring the CloudWatch agent to scrape metrics
from SAS Viya components - [FEATURE] The browser-accessible URL for Grafana is now included in
the output ofmonitoring/bin/deploy_monitoring_cluster.sh
(including
if ingress is configured) - [CHANGE] Several component versions have been upgraded
- Prometheus:
v2.23.0 -> v2.24.0 - Grafana:
7.3.6 -> 7.4.1 - Prometheus Operator:
0.44.1 -> 0.45.0 - kube-prometheus-stack:
12.8.0 -> 13.7.2
- Prometheus:
- [CHANGE] The following optional Grafana plugins are no longer installed by default:
- grafana-piechart-panel
- grafana-clock-panel
- camptocamp-prometheus-alertmanager-datasource
- flant-statusmap-panel
- btplc-status-dot-panel
- [CHANGE] cert-manager resources
now use 'v1' to align with their use in SAS Viya 4.x
- [FEATURE] The
-
Logging
- [FEATURE] The browser-accessible URL for Kibana included in the output
oflogging/bin/deploy_logging_open.sh
now takes into account ingress
configuration - [EXPERIMENTAL] A new experimental script
logging/bin/getlogs.sh
allows exporting logs to CSV formatDocumentation
- [FIX] The
logging/bin/change_internal_password.sh
script no longer
outputs passwords as debug messages
- [FEATURE] The browser-accessible URL for Kibana included in the output
1.0.4 - February 15, 2021
-
Overall
- Improved documentation for overall deployment process
- Improved documentation related to use of TLS
- Removed references to TLS in ingress sample (samples/ingress); TLS enabled ingress shown in TLS sample (samples/tls)
-
Monitoring
- [FIX] ENABLE_TLS should set proper port and targetport for v4m-prometheus service
- [FIX] Remove memory limit on kube-state-metrics
- [FIX] Kubernetes Cluster Dashboard disk usage not working on EKS
-
Logging
- Moved Helm chart from deprecated
stable/fluent-bit
tofluent/fluent-bit
- Fluent Bit version upgraded from 1.5.4 to 1.6.10
- Moved Helm chart from deprecated
1.0.3 - January 15, 2021
-
Overall
- Significantly improved documentation for deployment customization
KEEP_TMP_DIR
option added to keep the temporary working directory
around for troublshooting purposes- There is now an early check for
kubectl
cluster admin capabilities
-
Monitoring
- Component versions upgraded
- Helm Chart: 11.1.3->12.8.0
- Prometheus Operator: 0.43.2->0.44.1
- Prometheus: v2.22.2-> v2.23.0
- Grafana: 7.3.1->7.3.6
- The application filter on the SAS Java Services dashboard is now sorted
- The Perf/Node Utilization dashboard now uses node names instead of IP
addresses to identify nodes
- Component versions upgraded
-
Logging
- Moved Helm chart from deprecated
stable/elasticsearch-exporter
to
prometheus-community/elasticsearch-exporter
- Improved handling of log message fragment created due to excessively long
log messages (>16KB) - FIX: Eliminated hard-coded namespace in change_internal_password.sh script
- Moved Helm chart from deprecated
1.0.2 - December 15, 2020
- Fixed breaking script error in TLS
- Minor tweaks to SAS Java Services and Perf/Node Utilitzation dashboards
1.0.1 - December 14, 2020
- Overall
- [BREAKING CHANGE] - The default passwords for both Grafana and Kibana
are now randomly generated by default. The generated password is logged
during the initial deployment. It is possible to explicitly set each
password via environment variables oruser.env
files. - TLS support has been enhanced with improved logging and more accurate
checking of whencert-manager
is required - Helm 2.x has reached end-of-life and support for it has been removed
- [BREAKING CHANGE] - The default passwords for both Grafana and Kibana
- Monitoring
- The
KubeHpaMaxedOut
alert has been modified to only trigger if the
max replicas is > 1
- The
- Logging
- Refactored deployment/removal scripting internals
- Added new dashboards & visualizations to Kibana
- Added support for non-standard Docker root
1.0.0 - November 17, 2020
This is the first public release.
-
Overall
- Minor edits and cleanup to README files and sample user response files
-
Monitoring
- Grafana version bumped to 7.3.1
- Prometheus Operator version bumped to 0.43.2
- Prometheus version bumped to 2.22.2
- Prometheus Pushgateway version bumped to 1.3.0
0.1.3 - November 11, 2020
-
Overall
- Helm 2.x has reached end-of-life and is no longer supported. Helm 3.x is now required.
- Support added for the SAS Viya Workload Node Placement
- By default, monitoring and logging pods are deployed to untainted nodes
- A new flag,
NODE_PLACEMENT_ENABLE
supports deploying pods to appropriate
workload node placement nodes
-
Monitoring
- Several helm charts have moved from stable to prometheus-community.
- The prometheus-operator helm chart has been deprecated and moved to kube-prometheus-stack.
- SAS Java and Go ServiceMonitors converted to PodMonitors to properly support merged services
-
Logging
- Support for SAS Viya move to Crunchy Data 4.5
- Support for changing retention period of log messages
- Node anti-affinity for Elasticsearch replicas
- Support for multi-role Elasticsearch nodes (including sample
to demonstrate usage) - Additional documentation on using TLS
- Removed traces of support for ODFE "demo" security configuration
- Alternate monitoring solution(proof-of-concept): Fluent Bit ==> Azure Monitor (Log Analytics workspace)
0.1.2 - October 20, 2020
- CHANGELOG
- Monitoring
- Support for sas-elasticsearch metric collection
- Refreshed Istio dashboard collection
- Samples refactored out of monitoring/logging directories into a top-level
samples
directory. Additionally, each subdirectory is structured to be
compatible withUSER_DIR
customizations. - A new sample,
generic-base
has been created as
a template for customization. It contains a full set of user response files
available to customize. - Documentation for the samples has been improved
- Logging
- Kubernetes events are now stored in the index associated with the namespace
of the source of the event instead of a global (cluster) index - Multiple fixes to RBAC scripts
- Kubernetes events are now stored in the index associated with the namespace
0.1.1 - September 22, 2020
0.1.0 - September 16, 2020
- Initial early access release
- See README files for details