Upgrade ami release

[hamzabouissi]

PR Type

Enhancement, Tests

---

Description

• Updated AMI release version across multiple files to 1.30.8-20250123.

• Added a new test for pod creation using a DaemonSet in Kubernetes.

• Introduced a new daemonset.yaml file for testing pod creation.

• Enhanced cleanup and validation steps in k8s-test.sh.

---

Changes walkthrough 📝

	Relevant files
Enhancement	main.tf Update AMI release version in Terraform test configurations tests/main.tf Updated AMI release version to 1.30.8-20250123 in commented configurations. +3/-3      variables.tf Update default AMI release version                                              variables.tf Updated default AMI release version to 1.30.8-20250123. +1/-1
Tests	k8s-test.sh Add pod creation test and cleanup in script                            tests/k8s-test.sh Added a new test to verify pod creation using a DaemonSet. Included cleanup steps for the DaemonSet after testing. +15/-0    daemonset.yaml Add DaemonSet configuration for pod creation testing          tests/daemonset.yaml Added a new DaemonSet configuration for testing pod creation. Included tolerations and a simple Alpine container for testing. +75/-0
Documentation	README.md Update AMI release version in README examples                        README.md Updated AMI release version to 1.30.8-20250123 in example configurations. +4/-4      .header.md Update AMI release version in documentation header              docs/.header.md Updated AMI release version to 1.30.8-20250123 in documentation header examples. +3/-3

---

Need help?

Type /help how to ... in the comments thread for any questions about Qodo Merge usage.

Check out the documentation for more information.

[codiumai-pr-agent-free]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 PR contains tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Duplicate Resources Multiple DaemonSet resources are defined with the same name 'alpine-daemonset-argocd' in the same namespace 'test-pods-creation', which will cause conflicts and deployment issues kind: DaemonSet metadata: name: alpine-daemonset-argocd namespace: test-pods-creation spec: selector: matchLabels: app: alpine-test template: metadata: labels: app: alpine-test spec: tolerations: - key: "glueops.dev/role" operator: "Equal" value: "glueops-platform-argocd-app-controller" effect: "NoSchedule" containers: - name: alpine image: alpine:latest command: ["/bin/sh", "-c", "while true; do echo Running on $(hostname); sleep 3600; done"] --- apiVersion: apps/v1 kind: DaemonSet metadata: name: alpine-daemonset-argocd namespace: test-pods-creation spec: selector: matchLabels: app: alpine-test template: metadata: labels: app: alpine-test spec: tolerations: - key: "glueops.dev/role" operator: "Equal" value: "glueops-platform" effect: "NoSchedule" containers: - name: alpine image: alpine:latest command: ["/bin/sh", "-c", "while true; do echo Running on $(hostname); sleep 3600; done"] --- apiVersion: apps/v1 kind: DaemonSet metadata: name: alpine-daemonset-argocd namespace: test-pods-creation spec: selector: matchLabels: app: alpine-test template: metadata: labels: app: alpine-test spec: containers: - name: alpine image: alpine:latest command: ["/bin/sh", "-c", "while true; do echo Running on $(hostname); sleep 3600; done"] Test Validation The hardcoded pod count check (8 pods) may be unreliable as it depends on the cluster size. Consider dynamically getting the expected pod count based on the number of nodes if [ "$POD_COUNT" -ne 8 ]; then echo "Expected 8 pods, but found $POD_COUNT." exit 1

[codiumai-pr-agent-free]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
Possible issue	✅ Fix duplicate resource names Suggestion Impact: The commit renamed both DaemonSets to have unique names: 'alpine-daemonset-glueops' and 'alpine-daemonset' code diff: @@ -32,7 +32,7 @@ apiVersion: apps/v1 kind: DaemonSet metadata: - name: alpine-daemonset-argocd + name: alpine-daemonset-glueops namespace: test-pods-creation spec: selector: @@ -58,7 +58,7 @@ apiVersion: apps/v1 kind: DaemonSet metadata: - name: alpine-daemonset-argocd + name: alpine-daemonset namespace: test-pods-creation spec: selector: The DaemonSet names are identical which will cause conflicts. Each DaemonSet in the same namespace must have a unique name. tests/daemonset.yaml [10-12] metadata: - name: alpine-daemonset-argocd + name: alpine-daemonset-argocd-1 # Increment for each DaemonSet namespace: test-pods-creation [To ensure code accuracy, apply this suggestion manually] Suggestion importance[1-10]: 9 __ Why: Critical issue: Having multiple DaemonSets with identical names in the same namespace will cause deployment failures and resource conflicts. This must be fixed for the test to work.	High
General	Add timeout for pod readiness Add timeout to pod readiness check to prevent infinite wait in case of deployment issues. tests/k8s-test.sh [9] -POD_COUNT=$(kubectl get pods -n test-pods-creation --field-selector=status.phase=Running --no-headers | wc -l) +timeout 300s bash -c 'until [ $(kubectl get pods -n test-pods-creation --field-selector=status.phase=Running --no-headers | wc -l) -eq 8 ]; do sleep 5; done' || (echo "Timeout waiting for pods"; exit 1) Apply this suggestion Suggestion importance[1-10]: 8 __ Why: Important improvement that prevents test hangs by adding a timeout. Without it, the script could wait indefinitely if pods fail to reach Running state.	Medium

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud