Feat/update calico

[venkatamutyala]

PR Type

enhancement, configuration changes

---

Description

• Updated the Calico Helm chart version in the run.sh script from v3.27.4 to v3.28.2 to ensure the latest features and fixes are included.
• Modified the calico.yaml configuration file to update the tigera/operator image version from v1.32.10 to v1.34.5.
• Updated the calicoctl tag in calico.yaml from v3.27.4 to v3.28.2 for consistency with the Helm chart.

---

Changes walkthrough 📝

	Relevant files
Enhancement	run.sh Update Calico Helm chart version in script                              tests/run.sh Updated Calico Helm chart version from v3.27.4 to v3.28.2. +1/-1
Configuration changes	calico.yaml Update Calico configuration versions                                          tests/calico.yaml Updated tigera/operator image version from v1.32.10 to v1.34.5. Updated calicoctl tag from v3.27.4 to v3.28.2. +2/-2

---

💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information

[codiumai-pr-agent-free]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

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

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Version Compatibility Verify that the new Calico operator version v1.34.5 is compatible with the cluster's Kubernetes version and other components Configuration Validation Ensure that any new configuration options or deprecated settings between Calico versions v3.27.4 and v3.28.2 have been properly addressed

[codiumai-pr-agent-free]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
Possible issue	Add verification of successful component deployment before proceeding with subsequent operations Add a verification step after installing Calico to ensure the installation was successful and all pods are running before proceeding with node pool deployment. tests/run.sh [26-30] helm install calico projectcalico/tigera-operator --version v3.28.2 --namespace tigera-operator -f calico.yaml --create-namespace +echo "Waiting for Calico pods to be ready..." +kubectl wait --for=condition=ready pods --all -n calico-system --timeout=300s echo "::endgroup::" echo "::group::Deploying new Node Pool" Apply this suggestion Suggestion importance[1-10]: 9 Why: Adding a pod readiness check is crucial for ensuring Calico CNI is fully operational before proceeding with node pool deployment. Without this verification, subsequent operations might fail if Calico isn't properly initialized.	9

💡 Need additional feedback ? start a PR chat

[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