Release Notes v0.67

Release v0.67 brings updates like new CLI commands, custom IAM roles for GKE nodes, PSQL RDS support as well as some enhancements and bug fixes.

✨ What's New

  • New CLI Commands in Facets
    Two new CLI commands have been added to the FacetsCLI, enabling users to manage application synchronization more effectively. Refer to the Facets CLI documentation to know more about it.
    • Sync Status Check
      This command allows users to wait for the synchronization status of specified applications. It will also trigger a sync action if the --sync flag is provided.
        $ facetsctl release wait APPS -p <value> -e <value> [--sync]
      
    • Sync Out-of-Sync Applications
      This command lets users synchronize applications that are out-of-sync, aligning them with their deployed state.
      $ facetsctl release sync APPS -p <value> -e <value>
      

🚀 Product Capabilities

  • Custom IAM Roles for GKE Nodes
    Users can now specify custom IAM roles for Google Kubernetes Engine (GKE) nodes, allowing for more restrictive and fine-grained access to cloud resources. This feature provides greater control over what resources GKE nodes can access, ensuring that only the necessary permissions are granted.
  • PSQL RDS Support
    Users can now leverage PostgreSQL (PSQL) with Amazon RDS (Relational Database Service) for enhanced database management and integration.
  • Azure Functions
    Facets now supports using windows instances with Azure functions.
  • Auto-Upgrade of EKS Hardened AMIs with Custom Filters
    Users can now enable the auto-upgrade of Amazon EKS (Elastic Kubernetes Service) hardened AMIs based on tags, with the added ability to pass custom filters for selecting the appropriate AMI for their nodes.
    • This provides flexibility in managing EKS node upgrades by allowing users to define specific criteria for selecting the AMI version.

🐞 Bug Fixes

  • Fixed a bug where the application deployment complete notification did not wait for new pods to be ready.
  • Fixed a bug where white space either in the prefix or postfix in the JSON name added through the blueprint causes a release failure.