[Release] Kurtosis 0.78.0

[leeederek]

Today, we shipped Kurtosis 0.78.0! Read on for a summary of the latest updates since last week. You can always read this info on our website or the full detailed changelog on our docs.

As always, let us know on Discord or here on Github if you've got feedback and/or questions.

Breaking Changes

• [0.78.0] We've added two new flags to the kurtosis run CLI command: the --main-file flag and the --main-function-name flag. The former flag will allow users to explicitly specify the .star file they wish to use for a given run, while the latter lets you specify the function that you wish to use for a given run. Updates to the SDK were also made to enable this, meaning calls using the RunStarlarkScript, RunStarlarkPackage, and RunStarlarkRemotePackage SDK methods will need to be updated to avoid a break. Both flags are optional and will default to main.star and run when a flag is not passed in at runtime, respectively. Read more about this command here.

Features

• [0.78.0] There are now two new Starlark instructions: plan.start_service and plan.stop_service to enable the stopping and re-starting of services for the Docker backend. Read more about these new function calls here and here. Partially addresses #673
• [0.77.3] We've added a new CLI command: kurtosis service exec, enabling users to run arbitrary shell commands from inside the designated user service. Addresses #688.
• [0.77.2] To address a customer need, we've added the ability to specify the minimum resource contraints for services being spun up using Kurtosis within Kubernetes.

Improvements

• [0.77.2] The Kurtosis engine will now auto-restart when a cluster is updated, saving the end user an additional step that often would lead to port conflicts and operational errors. Addresses #646
• [0.77.2] The service name is now printed in the CLI whenever exec is used, making it easier for users to follow along and see what is happening following a kurtosis run (#682).

Bug Fixes

• [0.77.4] We've addressed an issue where the behavior of kurtosis files storeservice in Kubernetes does not match its behavior in Docker, specifically because k8s preserves nesting while Docker does not. For more details, check out #695
• [0.77.2] We've made Kurtosis engine restart error messages clearer and more concise to improve the "k8s context switch" workflow. (#658).
• [0.77.2] Addressed a bug in Kubernetes where kurtosis service logs would fail to call the logs command on a service running in an k8s cluster. (#678).
• [0.77.2] Fixed a bug where the wait instruction and PostHttpsRequestRecipe recipe would not function as intended when a user passed in the --dry-run flag for kurtosis run. (#679).