[Release] Kurtosis 0.80.23

[leeederek]

The latest release is 0.80.23. For a more detailed changelog, visit our docs.

Important Metrics Announcement

As of Kurtosis 0.80.23, Starlark package names will no longer be obfuscated in the metrics we collect by default from our users. The Starlark package name is defined in the kurtosis.yml. This change will enable our team to better understand how and where Kurtosis is being used so that we can productively engage and improve Kurtosis for our users. The decision behind this change was not made lightly as we still firmly stand by our promise to: never give away or sell user data, keep user IDs anonymous, and obfuscate potentially sensitive parameters (aside from Starlark package names now), as stated in our Metrics Philosophy. Users can, at any time, opt-out of metrics collection by switching off analytics using kurtosis analytics disable.

Features

• [0.80.23] We've added the kurtosis cloud add CLI command, which enables users to create new cloud instances in our managed cloud infrastructure from the terminal. A KURTOSIS_CLOUD_API_KEY is required. Note that the preferred way fkr using Kurtosis Kloud is through our web-app.
• [0.80.22] We've added the kurtosis import CLI command, which enables a user to start up an enclave with an existing docker-compose.yml file. Currently, this command supports the following keys from docker-compose: environment:, volume bind mounts, ports, image, entrypoint/command, and reservations: cpu.
• [0.80.20] We've added a new CLI command: kurtosis cloud load $INSTANCE_ID which enables a user to load the necessary cloud configuration files from the cloud and automatically switches the context for self-service usage of Kurtosis Kloud. Note that the preferred way for using Kurtosis Kloud is through our web-app.
• [0.80.20] Users will now be prompted to share their emails with our team upon their first start up of Kurtosis. This is entirely optional, but gives our team a way to communicate product updates, gather feedback, and otherwise engage productively with our community. Note that this prompt will only appear on interactive terminals.
• [0.80.16] Users can now view files artifacts and their contents in the Kurtosis frontend. The current iteration of the Kurtosis frontend only supports local Kurtosis (i.e. over Docker locally).
• [0.80.14] Users can now create enclaves in the Kurtosis frontend. The current iteration of the Kurtosis frontend only supports local Kurtosis (i.e. over Docker locally).
• [0.80.14] We've added support for the updating of running services in live enclaves, as part of our investments in idempotent runs. Tactically, this means a user can re-run a Starlark package with modifications to the ServiceConfig object and Kurtosis will update both the service(s) and any dependent instructions (e.g. exec, wait instructions) without having to re-instantiate an entirely new enclave and its services from scratch.

Improvements

• [0.80.21] Kurtosis will now print a messaging asking the user to stop the local engine if one is found to be running before switching to a remote context. Additionally, port forwarding now starts after the remote engine is started instead of when the context gets switched. Both of these changes were made to reduce the likelihood of engine port forwarding port conflicts between a user and a remote Kurtosis engine.
• [0.80.21] Resource fetching over our Docker backend is now a parallelized operation, meaning users will find out when they have resource issues far quicker than before (e.g. required resources exceed available resources). This change is meant to increase the feedback loop speed for users running large enclaves locally.
• [0.80.20] Kurtosis will now start a remote engine with the remote backend configuration file whenever the context is set to be remote. This change was made to improve the user experience for developers who are interacting with remote enclaves in their own cloud infrastructure.
• [0.80.20] Kurtosis will now validate that the minimum CPU and memory required are well under what is available. This validation only happens on the Docker backend.
• [0.80.18] Users can now remove an arbitrary number of enclaves with kurtosis enclave rm. For example, given 3 enclaves named enclave-a, enclave-b, and enclave-c, a user can simply run kurtosis enclave rm enclave-a enclave-c to remove enclave-a and enclave-c only, leaving enclave-b untouched.

Bug Fixes

• [0.80.21] We fixed a bug in Kubernetes where kurtosis engine logs would fail to output the engine logs.
• [0.80.14] We fixed an issue where the APIC would log successfully executed Starlark instruction despite an instruction failing.