🚧

Orka Release Notes

v1.1.0 February 20, 2020

[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.1.0 after your environment has been updated ([how to upgrade](🔗)). Here’s an overview of what changed with version 1.1.0.

## New features

Orka 1.1.0 introduces the following new features.

### Node groups

📘



In Orka 1.1.0, **node groups** are available only through the API. This feature will become available in the CLI in a future release.

**This is a BETA feature.**

You can now reserve Nodes for selected members of your organization using node and user group labels. Nodes with a group label are available for deployment only to users with the matching label. Adding and modifying labels are administrative operations and require authentication with a valid license key.

• You can now apply, remove, and modify a group label for a selected node with `PUT /node/<node-name>/dedicate`.

• You can create a new user and assign them to a user group with `POST /users`.

• You can group and ungroup users with `POST /users/groups/<group-name>` and `POST /users/groups/$ungrouped` respectively.

• Newly deployed VMs automatically inherit the label of the user deploying it.

• You can have both grouped and ungrouped Nodes in the same environment.

  • Grouped nodes are available only to grouped users.

  • Ungrouped nodes are available to all users, both grouped and ungrouped.

  • Grouped users can deploy to all nodes, both grouped and ungrouped.

  • Ungrouped users can deploy only to an ungrouped node.

  • Nodes and users can have up to one group label.

  • Grouping applies to both admin and non-admin level users.

• VMs already deployed on a node before a group label is set are not affected and continue to work as expected.

In Kubernetes, this functionality is sometimes referred to as `Node Dedication`.

### Logging

📘



In Orka 1.1.0, **log inspection and deletion** is available only through the API. This feature will become available in the CLI in a future release.

You can now retrieve and delete a list of all CLI commands and API calls executed against your Orka environment. Viewing and deleting logs are administrative operations and require authentication with a valid license key.

• Administrators can now retrieve all CLI/API logs with `POST /logs/query`.

• Administrators can now delete CLI/API logs using `DELETE /logs`.

### Nested virtualization

**This is a BETA feature.**

You can now run other virtualization inside your macOS Orka VMs, such as Docker containers.

📘



If you want to use nested virtualization in your Orka environment, you need to submit a ticket request in the [MacStadium portal](🔗).

## Improved functionality

Orka 1.1.0 introduces the following improvements.

• Improved [custom port mapping](🔗). You can map a VM port to any arbitrary port on the node when deploying a VM.

• Improved image and ISO lists. Orka filters out temporary files from these lists.

• Improved network stability.

## Bug fixes

Orka 1.1.0 introduces the following bug fixes.

• `orka vm create` now attaches ISOs as expected.

## How to upgrade

📘

Scheduled maintenance window required

This release requires a maintenance window of 30 minutes. Please submit a ticket in your portal account for what time you would like this window to be. Available times must be **Monday through Thursday, 5am to 6pm PST (8am to 9pm EST)**.

1. Submit a ticket through the [MacStadium portal](🔗).

2. Suggest a time for the maintenance window that works for you. The suggested time(s) must be **Monday through Thursday, 5am to 6pm PST (8am to 9pm EST)**.