Release notes for stackablectl

A full list of changes is available directly in stackablectl’s changelog.

1.4.0

  • Add STACK and DEMO templating parameters. Have a look at the README.md for details. See stackable-cockpit#432.

1.3.0

1.2.2

  • Add the option for users to customize the behaviour of stackablectl through a user config located at $HOME/.config/stackablectl/config.toml. The first supported option is version.check_enabled which can be set to true or false. See stackable-cockpit#422.

  • Add a new release check which is used in two different ways:

    • A new stackablectl version check command can be used to check if the current installation is up-to-date

    • A check automatically runs for all other commands (in parallel to not block the commands) and the status is reported as part of the final command output.

    See stackable-cockpit#421.

1.2.1

1.2.0

1.1.0

  • We now support idempotent Helm installations for demos and stacks. See stackable-cockpit#386.

  • Ignore failed re-application of Jobs due to immutability in demo and stack installations. The user is now asked if these be deleted or recreated. See stackable-cockpit#386.

  • Default to release build for nix users. See stackable-cockpit#388.

1.0.0

Previously, stackablectl was release alongside each Stackable Data Platform (SDP) release. However, the patch releases from thereon were not related to SDP. We have since decided to version stackablectl independently of SDP, starting at 1.0.0.

  • We have added visual progress reporting to more easily see what the tool is doing at any given moment in time. Previously, it looked like the tool was hanging as nothing was printed out to the terminal during the installation, but only after. See stackable-cockpit#376.

  • Releases can now be upgraded with the new release upgrade command. This makes it easier to upgrade installed operators to a newer SDP release. See stackable-cockpit#379.

25.3.0

  • A new demo called jupyterhub-keycloak was added and is available via stackablectl. The JupyterHub-Keycloak integration demo offers a comprehensive and secure multi-user data science environment on Kubernetes, integrating Single Sign-on Jupyter notebooks with Stackable Spark and S3 storage. The demo can be installed by running stackablectl demo install jupyterhub-keycloak. See demos#155 and documentation#715.

  • Demos and stacks are now versioned and the main branch is considered unstable. stackablectl by default installs the latest stable demo and/or stack. A specific release can be targeted by providing the --release argument. See stackable-cockpit#340.

  • Add new argument --chart-source so that operator charts can be pulled either from an OCI registry (the default) or from a index.yaml-based repository. See stackable-cockpit#344.

  • Use rustls-native-certs so that stackablectl can be used in environments with internal PKI. See stackable-cockpit#351.

  • Use heritage label when looking up the minio-console stacklet. See stackable-cockpit#364.

  • Improve tracing and log output. See stackable-cockpit#365.

24.11.0

  • Bump Rust dependencies to fix critical vulnerability in quinn-proto. See CVE-2024-45311 and stackable-cockpit#318.

  • We now provide additional completions for Nushell and Elvish, support using SOCK5 and HTTP proxies, and have improved the sorting of release versions.

24.7.0

  • a new experimental debug command

  • a pre-built binary for aarch64-unknown-linux-gnu is now available

  • complete error messages are now shown (remedying the truncation of some details in previous releases)

  • use of the latest Go and Rust versions and respective dependencies