Improved functionality and bug fixes in Orka v1.0.8.
Orka Release Notes
December 20, 2019
Download CLI | API Docs
We’re constantly working to provide you with new features, tools, and plugins, and improve your overall Orka experience. For the latest and greatest, be sure to update your CLI to 1.0.8 after your environment has been updated. Here’s an overview of what changes with version 1.0.8.
- Improved networking within Orka. You should experience performance improvements in deployments, uploads and downloads, and builds.
- Improved CPU provisioning to allow for slight overprovisioning. The last VM deployed to a node can now use less resources than specified in the configuration (for example, you can deploy a VM with 6 cores on a node that has only 5 cores free). You should not experience any performance degradation in such a VM unless the remaining VMs on the node are running at 100%.
- Improved vCPU pinning to limit the occurrence of VMs in a pending state.
- Improved auto-login in the Orka CLI when the token is already cached locally.
- Improved confirmation prompts in the Orka CLI. Yes/No Prompts are now case insensitive.
- Improved VM listing and handling of VMs in an errored state. Orka now lists VMs that are in an errored state. You can remove them with a delete or a purge operation.
- Improved VM scaling. The command no longer times out.
orka user createin the Orka CLI. You can now opt in to log in with the newly created user.
- Improved kube account management in the Orka CLI. You can now use flags and run the commands in direct mode. Run
orka kube --helpfor more information.
- Continued flag improvements for VM operations in the CLI. All VM-related commands now feature more intuitive flags and shorthand.
Renamed VM command options
orka vm create,
orka vm create-config, and
orka vm deploy: The
--vnc-consoleflag is renamed to
--no-vnc-consoleflag is dropped.
orka vm create-config: The
-aflag is renamed to
orka vm create: The
--iso-imageflag is renamed to
orka vm migrateand
orka vm clone: The
-tflag is renamed to
orka vm --helpfor more new and updated flags.
- Sometimes, after scaling down with
orka vm scaleor
PATCH /vm/scale, Kubernetes was erroneously holding onto services and consuming unnecessary resources in the process.
- (Partial fix, complete fix coming in a future release) Sometimes, the Orka CLI prints duplicate output for
orka <COMMAND> --helpand
orka <COMMAND> <VERB> --help.
Updated about 3 years ago