Update workflows with new configurations.

Change Summary

This update primarily focuses on refining the CI/CD workflows by introducing a timeout for merge checks and modifying the kubeconfig setup process. The changes aim to enhance the reliability and security of the deployment process.

Technical Details

• default.yml:
  • Added a merge-checks-timeout parameter with a value of 300 seconds. This ensures that merge checks do not run indefinitely, improving workflow efficiency.
• deploy.yml:
  • Replaced the actions-hub/kubectl@v1.35.0 step with a custom script to set up the kubeconfig. The new approach creates a directory, writes the kubeconfig content to a file, and sets the appropriate permissions.
  • Corrected a minor typo in the tg_command by adding a space between --non-interactive and -- apply.

Key Learnings & Insights

• Timeout for Merge Checks: Introducing a timeout for merge checks prevents workflows from hanging, which is crucial for maintaining CI/CD pipeline reliability.
• Secure Kubeconfig Handling: Manually setting up the kubeconfig ensures that sensitive information is handled securely and permissions are correctly set, reducing the risk of exposure.
• Typo Correction: Small typos can lead to significant issues. Always double-check command syntax to avoid unintended behavior.

Impact Assessment

• Reliability: The addition of the merge-checks-timeout parameter enhances the reliability of the CI workflow by preventing indefinite runs.
• Security: The manual kubeconfig setup improves security by ensuring that sensitive data is handled appropriately.
• Maintainability: The changes make the workflows more robust and easier to maintain, as they reduce dependency on external actions and clarify the setup process.

Developer Notes

• Gotchas: Ensure that the kubeconfig secret is correctly formatted and contains valid data before running the workflow.
• Edge Cases: Monitor the merge checks to ensure that the 300-second timeout is sufficient for your specific use case. Adjust if necessary.
• Future Improvements: Consider adding additional logging or notifications for when merge checks timeout to aid in debugging.