Tinkerbell Sandbox Versions Save

Example deployments of the Tinkerbell Stack for use as playground environments

v0.8.0

6 months ago

What's Changed

New Contributors

Full Changelog: https://github.com/tinkerbell/playground/compare/v0.7.0...v0.8.0

v0.7.0

1 year ago

What's Changed

New Contributors

Full Changelog: https://github.com/tinkerbell/sandbox/compare/v0.6.0...v0.7.0

v0.6.0

2 years ago

What's Changed

New Contributors

Full Changelog: https://github.com/tinkerbell/sandbox/compare/v0.5.0...v0.6.0

v0.5.0

3 years ago

Release

What's Changed

New Contributors

Full Changelog: https://github.com/tinkerbell/sandbox/compare/v0.4.0...v0.5.0

v0.4.0

3 years ago

HOTFIX:

BREAKING CHANGES:

v0.3.0

3 years ago

What's Changed

New Contributors

Full Changelog: https://github.com/tinkerbell/sandbox/compare/v0.2.1...v0.3.0

v0.2.1

3 years ago

This release fixes a problem with boots binaries not right for not x86 machines

What's Changed

Full Changelog: https://github.com/tinkerbell/sandbox/compare/v0.2.0...v0.2.1

v0.2.0

3 years ago

There are not BC breaks coming from the underline components. If you have a running sandbox and you want to update it with this version you just have to checkout v0.2.0 and a docker-compose stop, docker-compose rm, docker-compose up -d is enough.

A few things to know:

  1. We store a cached version of Osie in ./state/webdir/misc. If you do not remove that the new one won't be installed.
  2. tink-server uses migration now. In this way, we can automatically update the database schema if needed. Migration runs as part of docker-compose. So you should see a new container called tink-server-migrations in status Exit, which means that migrations ran on your system.
  3. If you are running sandbox in your own way, just a tip. generate-envrc.sh uses a new file called ./current_versions.sh. It exports a couple of variables that we use to generate our new shiny binaries as well.

Enjoy

v0.1.0

3 years ago