Update Kubernetes provider version.

Change Summary

This update involves a consistent change across multiple Terraform configuration files within various modules. The primary modification is the upgrade of the kubernetes provider version from ~> 2.36 to ~> 3.0 in all affected modules.

Technical Details

• Files Modified:
  • IaC/modules/*/init.tf (where * represents various module names such as argocd, cert-manager, cloudflare-tunnel, etc.)
• Change Implemented:
  • Updated the kubernetes provider version in the required_providers block from ~> 2.36 to ~> 3.0.
• Affected Modules:
  • argocd
  • cert-manager
  • cloudflare-tunnel
  • database
  • descheduler
  • external-secrets
  • homarr
  • homeassistant
  • litellm
  • longhorn
  • metallb
  • metrics
  • monitoring
  • n8n
  • octobot
  • open-webui
  • tailscale
  • technitium
  • traefik

Key Learnings & Insights

• Reasoning Behind the Change:
  • The upgrade to kubernetes provider version ~> 3.0 likely includes bug fixes, performance improvements, and new features that are beneficial for the overall infrastructure management.
• Problem-Solving Approach:
  • A systematic approach was taken to ensure all modules using the kubernetes provider were updated consistently. This minimizes the risk of version mismatches and ensures uniformity across the infrastructure.
• Best Practices:
  • Regular updates to dependencies help in maintaining security standards and leveraging the latest features and improvements.
• Trade-offs:
  • Potential compatibility issues with other dependencies or existing configurations needed to be assessed and tested before deployment.

Impact Assessment

• Overall System:
  • The change is expected to enhance the reliability and performance of Kubernetes-related operations across all modules.
• Performance:
  • Possible performance improvements due to optimizations in the new provider version.
• Security:
  • Potential security enhancements from bug fixes included in the new version.
• Maintainability:
  • Simplifies maintenance by ensuring all modules use the same provider version, reducing the complexity of managing different versions.

Developer Notes

• Gotchas:
  • Ensure that all modules are thoroughly tested post-upgrade to verify there are no breaking changes.
• Edge Cases:
  • Pay attention to any custom configurations or scripts that might be affected by the new provider version.
• Future Improvements:
  • Consider automating the version update process for dependencies to streamline future upgrades.