Release notes - Kubesafe v0.2.0

New features

1. Regex Support for Safe Contexts

You can now use regular expressions to define safe contexts. This makes it easier to manage multiple contexts with similar naming patterns. For example:

kubesafe context add "prod-.*"

With this command, any context starting with "prod-" will be treated as safe, and Kubesafe will prompt for confirmation before executing protected commands.

2. Custom Protected Commands

In addition to the predefined commands, you can now specify custom commands to be treated as safe for specific contexts. This gives you more flexibility in managing what commands require confirmation. Example:

kubesafe context add "my-context" --commands "get,delete,foo,bar"

With this, the commands get, delete, foo, and bar will be considered safe within the specified context.

3. Alias for Removing Protected Contexts

We've added a shortcut alias to streamline context management. You can now use the rm alias to quickly remove protected contexts. Example:

kubesafe rm context "my-context"

Misc

Kubesafe now follows the XDG Base Directory Specification for storing configuration files. Instead of using $HOME/.kubesafe.yaml, the configuration is now stored at: $XDG_CONFIG_DIRS/kubesafe/config.yaml.

For backward compatibility, Kubesafe still supports the old configuration path.