Releases: edenlabllc/rmk
Releases · edenlabllc/rmk
rmk-v0.45.6
Release notes:
- Fixed export of RMK_COMMAND_CATEGORY environment variable for all wrapped commands.
rmk-v0.45.5
Release notes:
- Added support for installing config extensions in CAPI management clusters after creation using Helmfile, filtered by labels config=extension and cluster=aws|azure|gcp.
- Added support for multi-tenancy within a single CAPI management cluster, enabling isolated tenant environments with centralized control.
- Added export of RMK_COMMAND_CATEGORY environment variable for all wrapped commands.
- Documented support for multi-provider updates in CAPI management clusters via 'rmk cluster capi update'.
rmk-v0.45.5-rc
Release notes:
- Added support for installing config extensions in CAPI management clusters after creation using Helmfile, filtered by labels config=extension and cluster=aws|azure|gcp.
- Added support for multi-tenancy within a single CAPI management cluster, enabling isolated tenant environments with centralized control.
- Added export of RMK_COMMAND_CATEGORY environment variable for all wrapped commands.
- Documented support for multi-provider updates in CAPI management clusters via 'rmk cluster capi update'.
rmk-v0.45.4
Release notes:
- Added a validation to ensure the presence of the CAPI management cluster before executing capi commands: destroy, provision, and update.
- Fixed AWS MFA config and credential files suffix after refreshing credentials multiple times.
- Fixed path to auth tools for Kubernetes context.
- Refactored template for Slack messages.
rmk-v0.45.4-rc
Release notes:
- Added a validation to ensure the presence of the CAPI management cluster before executing capi commands: destroy, provision, and update.
- Fixed AWS MFA config and credential files suffix after refreshing credentials multiple times.
- Fixed path to auth tools for Kubernetes context.
- Refactored template for Slack messages.
rmk-v0.45.3
Release notes:
- Improved the Backward Compatibility documentation for migrating existing AWS clusters to Kubernetes Cluster API (CAPI).
- Fixed Kubernetes context switch when the recommended home directory (~/.kube) does not exist.
rmk-v0.45.3-rc
Release notes:
- Improved the Backward Compatibility documentation for migrating existing AWS clusters to Kubernetes Cluster API (CAPI).
- Fixed Kubernetes context switch when the recommended home directory (~/.kube) does not exist.
rmk-v0.45.2
rmk-v0.45.1
Release notes:
- Fixed handling of project dependencies.
- Fixed generation of Azure Key Vault names.
- Added provider-specific environment variables for simple cluster detection.
rmk-v0.45.0
Release notes:
- #29 - Added support for AWS Secrets Manager to store SOPS Age keys.
- #29 - Added support for GCP Secrets Manager to store SOPS Age keys.
- #29 - Added support for Azure Key Vault to store SOPS Age keys.
- #29 - Added support for Azure Key Vault resource group name definition.
- #29 - Added support for the AWS provider in Cluster API.
- #29 - Added support for the GCP provider in Cluster API.
- #29 - Added support for the Azure provider in Cluster API.
- #29 - Added support for downloading existing SOPS Age keys.
- #29 - Added the ability to create an SSH key pair for the AWS provider.
- #29 - Added GCP NAT router creation for the GCP provider.
- #29 - Added commands for managing Cluster API clusters to the cluster category commands.
- #29 - Added new configuration arguments for project generation.
- #29 - Added the generation of values for all cluster provider configurations in the project generate command.
- #29 - Added deps scope unconditionally when generating projects.
- #29 - Fixed the inheritance behavior of dependent repositories.
- #29 - Fixed the output of the config list command for sibling project names.
- #29 - Removed the artifact-mode flag and the functionality.
- #29 - Reworked the behaviour of the config init command to align with each cluster provider.
- #29 - Reworked the approach to obtaining the Kubernetes context for all cluster providers.
- #29 - Refactored flags names of project generate and secret manager commands.
- #29 - Refactored the environment variables provisioning for all cluster providers in release category commands.
- #29 - Refactored the k3d list command.
- #29 - Restructured code files for improved organization.
- #29 - Changed root-domain configuration to be managed via the project.yaml file.
- #29 - Deprecated Terraform commands under the cluster category.
- #29 - Improved documentation to describe the new Cluster API provisioning and management logic.