Update external-secrets Helm version.

Change Summary

This update involves upgrading the Helm chart version for the external-secrets module from version 0.20.4 to 1.1.1. This change is intended to leverage new features, bug fixes, and improvements available in the latest version.

Technical Details

• File Modified: IaC/modules/external-secrets/main.tf
• Change Made: Updated the version attribute of the helm_release resource from 0.20.4 to 1.1.1.

resource "helm_release" "release" {
  name       = "external-secrets"
  chart      = "external-secrets"
  repository = "https://charts.external-secrets.io"
-  version    = "0.20.4"
+  version    = "1.1.1"
  timeout    = "1500"
  namespace  = kubernetes_namespace.external_secrets.metadata[0].name
}

Key Learnings & Insights

• Reasoning Behind the Change: The upgrade to version 1.1.1 was driven by the need to incorporate recent enhancements and security patches. The older version 0.20.4 lacked several critical features and fixes that are essential for our current deployment strategy.
• Problem-Solving Approach: The team conducted a thorough review of the release notes for versions between 0.20.4 and 1.1.1 to ensure that the upgrade would not introduce breaking changes or compatibility issues.
• Best Practices: Regularly updating dependencies is a best practice to ensure the application benefits from the latest improvements and security updates. This change aligns with our policy of maintaining up-to-date infrastructure components.

Impact Assessment

• System Impact: The upgrade should enhance the functionality and security of the external-secrets deployment. It is expected to introduce new configuration options and possibly deprecate some old ones.
• Performance Implications: While specific performance metrics are not detailed in the release notes, upgrading to a newer version typically includes optimizations that could lead to improved performance.
• Security Implications: The upgrade is likely to include security patches, reducing the attack surface of the deployment.
• Breaking Changes: The release notes should be reviewed to identify any breaking changes that might require additional configuration adjustments or migration steps.

Developer Notes

• Gotchas: Ensure that the new version does not introduce breaking changes that affect existing configurations. Pay close attention to deprecated fields or altered behavior in the new release.
• Edge Cases: Test the deployment in a staging environment to catch any unexpected behaviors before promoting to production.
• Future Improvements: Consider setting up automated checks to regularly scan for updates to dependencies, ensuring the infrastructure remains up-to-date with minimal manual intervention.