Skip to content

Latest commit

 

History

History
249 lines (177 loc) · 14.4 KB

CHANGELOG.md

File metadata and controls

249 lines (177 loc) · 14.4 KB

Changelog

0.7.0 (2020-01-21)

The promised big update is here! In the last couple of weeks a lot has happened.

Grafana Labs announced Tanka to the public, and the project got a lot of positive feedback, shown both on HackerNews and in a 500+ increase in GitHub stars!

While we do not ship big new features this time, we ironed out many annoyances and made the overall experience a lot better:

Better website + tutorial (#134)

Our new website is published! It does not only look super sleek and performs like a supercar, we also revisited (and rewrote) the most of the content, to provide especially new users a good experience.

This especially includes the new tutorial, which gives new and probably even more experienced users a good insight into how Tanka is meant to be used.

🚨🚨 Disabling import ".yaml" (#176) 🚨🚨

Unfortunately, we had to disable the feature that allowed to directly import YAML files using the familiar import syntax, introduced in v0.6.0, because it caused serious issues with importstr, which became unusable.

While our extensions to the Jsonnet language are cool, it is a no-brainer that compatibility with upstream Jsonnet is more important. We will work with the maintainers of Jsonnet to find a solution to enable both, importstr and import ".yaml"

Workaround:

- import "foo.yaml"
+ std.parseYaml(importstr "foo.yaml")

k.libsonnet installation (#140)

Previously, installing k.libsonnet was no fun. While the library is required for nearly every Tanka project, it was not possible to install it properly using jb, manual work was required.

From now on, Tanka automatically takes care of this. A regular tk init installs everything you need. In case you prefer another solution, disable this new thing using tk init --k8s=false.

Features

  • cli, kubernetes: k.libsonnet is now automatically installed on tk init (#140):
    Before, installing k.libsonnet was a time consuming manual task. Tanka now takes care of this, as long as jb is present on the $PATH. See https://tanka.dev/tutorial/k-lib#klibsonnet for more details.
  • cli: tk env --server-from-context:
    This new flag allows to infer the cluster IP from an already set up kubectl context. No need to remember IP's anymore – and they are even autocompleted on the shell. (#145)
  • cli, jsonnet: extCode, extVar:
    -e / --extCode and --extVar allow using std.extVar() in Tanka as well. In general, -e is the flag to use, because it correctly handles all Jsonnet types (string, int, bool). Strings need quoting! (#178)
  • jsonnet: The contents of spec.json are now accessible from Jsonnet using (import "tk").env. (#163)
  • jsonnet: Lists ([ ]) are now fully supported, at an arbitrary level of nesting! (#166)

Bug Fixes

  • jsonnet: nil values are ignored from the output. This allows to disable objects using the if ... then {} pattern, which returns nil if false (#162).
  • cli: -t / --target is now case-insensitive (#130)

0.6.1 (2020-01-06)

First release of the new year! This one is a quick patch that lived on master for some time, fixing an issue with the recent "missing namespaces" enhancement leading to apply being impossible when no namespace is included in Jsonnet.

More to come soon :D

0.6.0 (2019-11-27)

It has been quite some time since the last release during which Tanka has become much more mature, especially regarding the code quality and structure.

Furthermore, Tanka has just hit the 100 Stars 🎉

Notable changes include:

API (#97)

The most notable change is probably the Go API, available at https://godoc.org/github.com/grafana/tanka/pkg/tanka, which allows to use all features of Tanka directly from any other Golang application, without needing to exec the binary. The API is inspired by the command line parameters and should feel very similar.

Importing YAML (#106)

It is now possible to import .yaml documents directly from Jsonnet. Just use the familiar syntax import "foo.yaml" like you would with JSON.

Missing Namespaces (#120)

Tanka now handles namespaces that are not yet created, in a more user friendly way than `kubectl** does natively.
During diff, all objects of an in-existent namespace are shown as new and when applying, namespaces are applied first to allow applying in a single step.

Features

  • tool/imports: import analysis using upstream jsonnet: Due to recent changes to google/jsonnet, we can now use the upstream compiler for static import analysis (#84)
  • Array output: The output of Jsonnet may now be an array of Manifests. Nested arrays are not supported yet. (#112)

Bug Fixes

0.5.0 (2019-09-20)

This version adds a set of commands to manipulate environments (tk env add, rm, set, list) (#73). The commands are mostly ks env compatible, allowing tk env be used as a drop-in replacement in scripts.

Furthermore, an error message has been improved, to make sure users can differentiate between parse issues in .jsonnet and spec.json (#71).

0.4.0 (2019-09-06)

After nearly a month, the next feature packed release of Tanka is ready! Highlights include the new documentation website https://tanka.dev, regular expression support for targets, diff histograms and several bug-fixes.

Features

  • cli: tk show now aborts by default, when invoked in a non-interactive session. Use --dangerous-allow-redirect to disable this safe-guard (#47).
  • kubernetes: Regexp Targets: It is now possible to use regular expressions when specifying the targets using --target / -t. Use it to easily select multiple objects at once: https://tanka.dev/targets/#regular-expressions (#64).
  • kubernetes: Diff histogram: Tanka now allows to summarize the differences between the live configuration and the local one, by using the unix diffstat(1) utility. Gain a sneek peek at a change using tk diff -s .! (#67)

Bug Fixes

  • kubernetes: Tanka does not fail anymore, when the configuration file spec.json is missing from an Environment. While you cannot apply or diff, the show operation works totally fine (#56, #63).
  • kubernetes: Errors from kubectl are now correctly passed to the user (#61).
  • cli: tk diff does not output useless empty lines (\n) anymore (#62).

0.3.0 (2019-08-13)

Tanka v0.3.0 is here!

This version includes lots of tiny fixes and detail improvements, to make it easier for everyone to configure their Kubernetes clusters.

Enjoy target support, enhancements to the diff UX and an improved CLI experience.

Features

The most important feature is target support (#30) (caf205a): Using --target=kind/name, you can limit your working set to a subset of the objects, e.g. to do a staged rollout.

There where some other features added:

  • cli: autoApprove, forceApply (#35) (626b097): allows to skip the interactive verification. Furthermore, kubectl can now be invoked with --force.
  • cli: print deprecated warnings in verbose mode. (#39) (6de170d): Warnings about the deprecated configs are only printed in verbose mode
  • kubernetes: add namespace to apply preamble (#23) (9e2d927): The interactive verification now shows the metadata.namespace as well.
  • cli: diff UX enhancements (#34) (7602a19): The user experience of the tk diff subcommand has been improved:
    • if the output is too long to fit on a single screen, the systems PAGER is invoked
    • if differences are found, the exit status is set to 16.
    • When tk apply is invoked, the diff is shown again, to make sure you apply what you want

Bug Fixes

  • cli: invalid command being executed twice (#42) (28c6898): When the command failed, it was executed twice, due to an error in the error handling of the CLI.
  • cli: config miss (#22) (32bc8a4): It was not possible to use the new configuration format, due to an error in the config parsing.
  • cli: remove datetime from log (#24) (1e37b20)
  • kubernetes: correct diff type on 1.13 (#31) (574f946): On kubernetes 1.13.0, subset was used, although native is already supported.
  • kubernetes: Nil pointer deference in subset diff. (#36) (f53c2b5)
  • kubernetes: sort during reconcile (#33) (ab9c43a): The output of the reconcilation phase is now stable in ordering

0.2.0 (2019-08-07)

Features

  • cli: Completions (#7) (aea3bdf): Tanka is now able auto-complete most of the command line arguments and flags. Supported shells are bash, zsh and fish.
  • cmd: allow the baseDir to be passed as an argument (#6) (55adf80), (#12) (3248bb9): tk breaks with the current behaviour and requires the baseDir / environment to be passed explicitely on the command line, instead of assuming it as pwd. This is because it allows more go-like UX. It is also very handy for scripts not needing to switch the directory.
  • kubernetes: subset-diff (#11) (13f6fdd): tk diff support for version below Kubernetes 1.13 is here 🎉! The strategy is called subset diff and effectively compares only the fields already present in the config. This allows the (hopefully) most bloat-free experience possible without server side diff.
  • tooling: import analysis (#10) (ce2b0d3): Adds tk tool imports, which allows to list all imports of a single file (even transitive ones). Optionally pass a git commit hash, to check whether any of the changed files is imported, to figure out which environments need to be re-applied.

0.1.0 (2019-07-31)

This release marks the begin of tanka's history 🎉!

As of now, tanka aims to nearly seemlessly connect to the point where ksonnet left. The current feature-set is basic, but usable: The three main workflow commands are available (show, diff, apply), environments are supported, code-sharing is done using jb.

Stay tuned!

Features

  • kubernetes: Show (7c4bee8): Equivalent to ks show, allows previewing the generated yaml.
  • kubernetes: Diff (a959f38): Uses the kubectl diff to obtain a sanitized difference betweent the current and the desired state. Requires Kubernetes 1.13+
  • kubernetes: Apply (8fcb4c1): Applies the changes to the cluster (like ks apply)
  • kubernetes: Apply approval (4c6414f): Requires a typed yes to apply, gives the user the chance to verify cluster and context.
  • kubernetes: Smart context (2b3fd3c): Infers the correct context from the spec.json. Prevents applying the correct config to the wrong cluster.
  • Init Command (ff8857c): Initializes a new repository with the suggested directory structure.