Skip to content

Releases: sassoftware/viya4-ark

1.6.0 - November 3, 2021

03 Nov 13:41
a25dc78
Compare
Choose a tag to compare
  • Summary:
    Adding support for RedHat OpenShift
  • Issues Addressed:
    • Pre-install-check tool should expose sample application correctly in OpenShift environment (#150)
    • Deployment Report should not display none existing resource types (#151)

1.5.0 - September 29, 2021

29 Sep 14:12
299223a
Compare
Choose a tag to compare
  • Summary:
    Various bug fixes and enhancements.
  • Issues Addressed:
    • Pre-Install-Check: Update for System Requirements based on Documentation (#79 )
      • See issue (#79 ) for details regarding obsolecense of viya_cluster_settings.properties file
    • Pre_install_check: Does not report all available Storage classes on an Azure cluster (#135 )
    • Update example commands for consistency (#137 )
    • Provide full commands for http vs https example (#138 )
    • Add storage information for internal/external database to the deployment report (#142 )
    • Add validation for values specified in viya_deployment_settings.ini file (#147 )

1.4.0 - August, 13, 2021

13 Aug 14:04
eac1dea
Compare
Choose a tag to compare
  • Summary:
    Various bug fixes and enhancements.
  • Issues Addressed:
    • Add setup files to make viya4-ark pip installable via Git (#110 )
    • Request to add storage information for internal/external database to the deployment report (#115 )
    • Pre_install_check: Migrate hello-ingress manifest to use the networking.k8s.io/v1 API version, available since v1.19 (#118 )
    • Deployment Report: Update supported Ingress definitions (#120 )
    • Pre_install_check: Syntax error in example commands for Known Issues (#124 )
    • Pre_install_check: Correct Error in the instructions to collect the INGRESS HOST (#126 )
    • Pre_install_check: Usage example fails as documented; needs to be python3 (#128 )
    • Deployment Report: Recursion error when generating report (#130 )

1.3.0 - June 7, 2021

07 Jun 19:12
0054e11
Compare
Choose a tag to compare
  • Summary:
    Bug fixes and one enhancement.
  • Issues Addressed:
    • Add Promotion Model to Cadence Information in Deployment Report (#88)
    • pre-install-check report fails due to invalid key in latest deployment (#103)
    • Deployment-Report: Short-lived DaemonSets/Pods can cause intermittent TypeError issue (#107)

1.2.1 - May 12, 2021

12 May 12:47
2dcac88
Compare
Choose a tag to compare
  • Summary:
    Several bug fixes including potential security vulnerability from the version of PyYAML previously pinned.
  • Issues Addressed:
    • LDAP Validator not allowing/performing anonymousBind (#98 )
    • Potential security vulnerability in dependencies: PyYAML (#97 )
    • Deployment Report: Traceback using Kubernetes Server & Client (kubectl) version v1.19+ (#85 )

1.2.0 - April 29, 2021

29 Apr 19:06
9225483
Compare
Choose a tag to compare
  • Summary:
    Introduction of new LDAP Validator feature along with several bug fixes and a couple of enhancements.
  • Issues Addressed:
    • Add LDAP Validator (#33)
    • Add all container logs to download-pod-logs tool for pods in non-ready/non-terminated state (#68)
    • Implement Pre-Install Check permissions for AWS Elastic Block Storage (#72)
    • Deployment Report: Orphaned pods can cause null dictionary keys in the sas_components dictionary yielding sort errors (#74)
    • Issue executing Deployment Report on develop branch using --include-pod-log-snips (#80)
    • Download Pod Logs: Error raised when log line is parsed as JSON but is not structured as a dictionary (#81)
    • Deployment Report: Error generating report against new Ingress definitions (#86)

1.1.1 - April 1, 2021

01 Apr 14:53
670f0b1
Compare
Choose a tag to compare
  • Summary:
    Patch release addressing jinja2 vulnerability based on ReDos issue GHSA-g3rq-g295-4j3m (CVE-2020-28493).
  • Issues Addressed:
    Potential security vulnerability in dependencies: jinja2 (#76)

1.1.0 - February 17, 2021

17 Feb 17:33
6390228
Compare
Choose a tag to compare
  • Summary:
    Fixed several issues. Early validation of Viya 4 ARK pre-install and deployment-report apps on AWS.
  • Issues Addressed:
    • Add Viya cadence version to Deployment Report (Issue #60)
    • Pre-Install Report now reflects when All or some nodes are not in READY state (Issue #62)
    • Kubectl Class needs to handle APIVERSION returned from Kubernetes (Issue #64)

1.0.1 - December 17, 2020

17 Dec 17:56
db0154b
Compare
Choose a tag to compare
  • Summary:
    Bugfix release.
  • Issues Addressed:
    • The pre-install report throws an exception when Nodes in the cluster are not in a ready state (Issue #55)

1.0.0 - November 18, 2020

17 Nov 16:19
f2d4a60
Compare
Choose a tag to compare
  • Summary:
    Initial release of SAS Viya 4 ARK in support of SAS Viya.
  • Issues Addressed:
    • Provide guidance to determine Ingress Host and port (Issues #40 #49 #52 )
    • Check that the kubeconfig file specified with KUBECONFIG environment variable exists. (Issue #47 )
    • Remove Control Plane Information (Issue #45 )
    • Refactor the CPU, Memory, Workers and Storage Class tables and make them easier to read (Isssue #42 )
    • Show the Calculated aggregate “Allocatable Memory” in “GB” on the Summary line (Issue #38 )
    • download-pod-logs TypeError: 'NoneType' object is not iterable exception (Issue #32 )
    • Indicate Permissions Insufficient for Azure Persistent Volume Claims if Storage Classes cannot be read (Issue #29 )
    • Check Permissions for Azure Persistent Volume Claims (Issue #26 )
    • Minimum Kubernetes version update needed (Issue #23 )
    • Deployment Report: Refactor to use LRPIndicator while task runs (Issue #22 )
    • Could download_pod_logs grow an option for --format=json, please. (Issue #21 )
    • Deployment Report: Refactor to use argparse instead of getopts (Issue #20 )