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.
Apache License 2.0
70
stars
64
forks
source link
fix: (IAC-1052) add MT tags to the 'Set env_path' tasks #451
add multi-tenancy task tags to the set of tasks that will define env_path variable
add env_path to PATH environment for below the line deployment when running DAC as a docker container. Below the line deployment is an internal use only feature.
Tests
See internal ticket for additional details.
Scenario
Method
kubeconfig
Task
Provider
k8s version
Cadence
tasks
Deploy method
Remarks
1
OOTB
provider based
docker
AWS
1.25.9-eks
fast:2020
baseline,viya,install
deploy command
Deployment command completed successfully and all pods stabilized. V4MT_ENABLE: true, V4MT_MODE: "schema", V4MT_TENANT_IDS: "acme",
2
OOTB
provider based
docker
AWS
1.25.9-eks
fast:2020
multi-tenancy,onboard,cas-onboard
deploy command
all three tasks completed successfully with all pods stabilized. sas-cas-server-acme-default-controller is 3/3 Ready and reached Running state
3
OOTB
provider based
docker
AWS
1.25.9-eks
fast:2020
multi-tenancy,offboard
deploy command
offboard tasks completed successfully with other Running pods stabilized. sas-cas-server-acme-default-controller was successfully terminated
4
OOTB
provider based
docker
AWS
1.25.9-eks
fast:2020
viya,uninstall
deploy command
viya uninstall tasks completed successfully
Before adding env_path to PATH for deploy BLT - Deploy SAS Viya task
Scenario
Method
kubeconfig
Task
Provider
k8s version
Cadence
tasks
Deploy method
Remarks
5
OOTB
provider based
docker below-the-line
AWS
1.25.9-eks
fast:2020
viya,install
deploy command
Prior to adding env_path to PATH for docker based BLT deployment, deployment encounters the fatal error below indicating the the aws cli executable was not found
Error for Scenario number 5 prior to change
start: '2023-05-31 18:05:45.778874'
stderr: |-
Warning: 'EXPERIMENTAL_FEATURE_LOCAL_DEPLOYMENT_ASSETS' has been enabled. The behavior for 'EXPERIMENTAL_FEATURE_LOCAL_DEPLOYMENT_ASSETS' may change, or even be removed, in future releases.
Error: Cannot create client for namespace 'deploy'
Caused by:
* Get "https://76E82B98902FD22511963025830C3917.gr7.us-east-2.eks.amazonaws.com/api?timeout=32s": getting credentials: exec: executable aws not found
It looks like you are trying to use a client-go credential plugin that is not installed.
To learn more about this feature, consult the documentation available at:
https://kubernetes.io/docs/reference/access-authn-authz/authentication/#client-go-credential-plugins
After adding env_path to PATH for deploy BLT - Deploy SAS Viya task
Scenario
Method
kubeconfig
Task
Provider
k8s version
Cadence
tasks
Deploy method
Remarks
6
OOTB
provider based
docker below-the-line
AWS
1.25.9-eks
fast:2020
viya,install
deploy command
Successful BLT deployment, all pods stabilized and Running. Successful login with admin user to ingress
Changes
Tests
Before adding env_path to PATH for deploy BLT - Deploy SAS Viya task
Error for Scenario number 5 prior to change
After adding env_path to PATH for deploy BLT - Deploy SAS Viya task