Understanding Rack and CLI Versioning
We want to ensure that our customers have a clear understanding of our product versioning. In this blog post, we’ll address some common misconceptions and provide guidance on how to manage different versions of our CLI and Rack offerings.
Two Versions of CLI and Rack
Our product offers two distinct versions of both our CLI (Command Line Interface) and Rack. Our v2 Racks run on AWS ECS, whereas our v3 Racks are cloud-agnostic and run on Kubernetes (k8s) in cloud providers' managed Kubernetes offerings. This approach provides our customers with the flexibility to choose the cloud provider that best suits their needs and preferences.
Checking Your CLI and Rack Version
Before updating, it’s essential to know the current versions of your CLI and Rack. You can check the version of your CLI and the currently addressed Rack by running
convox version. To check the version of a specific Rack, use the command
convox rack -r rackName. Knowing the versions will help you make informed decisions about updating your infrastructure.
Updating Your CLI and Rack
To keep your environment up-to-date, you need to update both your CLI and Rack. You can update the CLI by running the command
sudo convox update, and update your Rack with
convox rack update -r rackName. Regular updates ensure that you take advantage of the latest features, performance improvements, and security patches, providing a more stable and efficient infrastructure.
Our v2 and v3 CLIs are designed to be Rack version agnostic, meaning they can control both v2 and v3 Racks. There are a few rare exceptions for commands that are specific to ECS (v2) or EKS/GKE/AKS (v3). This compatibility ensures a seamless experience for users, enabling smooth management of different Rack versions with a single CLI.
v2 Racks can be updated across multiple versions. For each new v2 release, we test a direct update from a Rack version that is at least one year old. This approach simplifies the update process for our customers and ensures that you can easily transition from an older version up to one year old to the latest one without having to perform multiple incremental updates. To view the complete list of available v2 Rack versions, please visit our v2 Rack Version History.
For v3 Racks, it’s necessary to update through every minor version step-wise until you reach your desired version. This is to ensure that no internal Rack or Kubernetes cluster services fall out of sync or experience version incompatibility issues. For example, a Rack on Version 3.6.x would need to update to the latest 3.7.x version before proceeding to the latest 3.8.x version and so on. To update a v3 Rack that is more than one minor version old, you must specify the version you would like to update to, e.g.,
convox rack update X.Y.Z -r rackName. Following this step-wise update process helps maintain stability and minimize potential issues during the update process. For a comprehensive list of available v3 Rack versions, please refer to our v3 Rack Version History.
Known Deprecation Schedule for Amazon EKS and v3 Rack Versions:
|v3 Rack Version||Amazon EKS End of Support||Kubernetes Version|
|3.7.0 - 3.9.3||June 4, 2023||1.22|
|3.6.0 - 3.6.11||February 15, 2023||1.21|
|3.4.0 -3.5.7||November 1, 2022||1.20|
|*latest release at time of this writing|
|**Exact date unknown|
Understanding the versioning is crucial for effectively managing your cloud infrastructure. By familiarizing yourself with the different versions of CLI and Rack, as well as the appropriate methods for updating and checking versions, you can ensure a seamless experience while maintaining a stable and up-to-date environment. If you have any questions or need further assistance, please don’t hesitate to reach out to our support team.