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-994) Add K8S Cluster name to dynamic volumes created by EBS CSI Driver #444
Prior to the introduction of the EBS CSI driver, dynamically provisioned EBS persistent volumes were tagged with the cluster name. That made it easy to look at the list of dynamically provisioned volumes in an AWS account and know which cluster they belonged to. Along with the introduction of the EBS CSI driver to dynamically provision volumes, that tagging was lost making it difficult to tell which cluster a volume belonged to.
The EBS CSI driver does support tagging by specifying a cluster name value for the k8sClusterId key in it's helm chart.
This update sets that key value to the cluster name when the EBS CSI driver helm chart is installed.
Tests
Scenario
Method
Task
Provider
k8s version
Cadence
tasks
Deploy method
Remarks
1
OOTB
Ansible
AWS
1.25.9-eks
fast:2020
baseline,viya,install
deploy command
Deployment command completed successfully and all pods stabilized. All dynamically provisioned persistent volumes with the ebs csi driver have the cluster name prefix and are tagged with the cluster name
2
OOTB
Ansible
AWS
1.26.4-eks
fast:2020
baseline,viya,install
deploy command
Deployment completed successfully and all pods stabilized. All dynamically provisioned persistent volumes with the ebs csi driver have the cluster name prefix and are tagged with the cluster name
Changes
Prior to the introduction of the EBS CSI driver, dynamically provisioned EBS persistent volumes were tagged with the cluster name. That made it easy to look at the list of dynamically provisioned volumes in an AWS account and know which cluster they belonged to. Along with the introduction of the EBS CSI driver to dynamically provision volumes, that tagging was lost making it difficult to tell which cluster a volume belonged to.
The EBS CSI driver does support tagging by specifying a cluster name value for the k8sClusterId key in it's helm chart. This update sets that key value to the cluster name when the EBS CSI driver helm chart is installed.
Tests