This project contains Ansible code that creates a baseline in an existing Kubernetes environment for use with the SAS Viya Platform, generates the manifest for an order, and then can also deploy that order into the Kubernetes environment specified.
Documentation from a past internal ticket indicates that the subject transformer yaml file was removed from the product and is not being delivered. Comments indicate that transformer was originally designed to replace the connect certificate with a customer provided certificate, although that is not a currently supported option. DAC should follow suit and remove its template for that transformer to avoid kustomize build problems that have been identified when including it.
Preserve the addition of V4_CFG_CONNNECT_FQDN to V4_CFG_TLS_ADDITIONAL_SAN_DNS variable
Remove addition of sas-connect-customer-provided-ingress-certificate-tls-certframe-transformer.yaml transformer to the kustomization.yaml per the explanation above.
Tests
Scenario
Task
method
Provider
k8s version
Cadence
tasks
Deploy method
Remarks
1
deployment
Ansible
Azure
1.26.3
stable:2023.06
baseline,viya,install
deploy command
Deployment completed successfully with all pods stabilized. Successful viya_admin login to Viya SASDrive application.
2
kustomize build . -o site.yaml
See remarks below
n/a
n/a
n/a
n/a
n/a
Successful
Post deployment, navigate to the \<$BASE_DIR>/\<cluster>/\<namespace> folder containing the DAC generated kustomization.yaml file and verified that kustomize build . -o site.yaml runs (without encountering the error described in the internal ticket) and successfully generates the site.yaml manifest file.
Re-tested both scenarios using 60acb1f commit with successful results for both.
Changes
Documentation from a past internal ticket indicates that the subject transformer yaml file was removed from the product and is not being delivered. Comments indicate that transformer was originally designed to replace the connect certificate with a customer provided certificate, although that is not a currently supported option. DAC should follow suit and remove its template for that transformer to avoid kustomize build problems that have been identified when including it.
Tests
Post deployment, navigate to the \<$BASE_DIR>/\<cluster>/\<namespace> folder containing the DAC generated kustomization.yaml file and verified that
kustomize build . -o site.yamlruns (without encountering the error described in the internal ticket) and successfully generates the site.yaml manifest file.Re-tested both scenarios using 60acb1f commit with successful results for both.