v0.12.11

What's New

Generate Edge Files

You can now run micado edge after deployment of a MiCADO cluster, to generate a script that will connect an edge device to the main MiCADO cluster, called connect_edge.sh. Simply run the script on your edge device.

If available, a container registries.yaml file will also be generated, which should be copied to /etc/rancher/k3s/registries.yaml on the edge device.

Full Changelog: v0.12.10...v0.12.11

v0.12.10

What's New

• Support for setting GCP creds with micado config gcp
• Uses the latest MiCADO v0.12.5

Full Changelog: v0.12.9...v0.12.10

v0.12.9

• Add support for demos
• Change micado deploy to micado up

Full Changelog: v0.12.8...v0.12.9

v0.12.8

What's New

• Better edge support

Full Changelog: v0.12.7...v0.12.8

v0.12.7

What's Fixed

• Bad path on config file recognition

Full Changelog: v0.12.6...v0.12.7

v0.12.6

What's Fixed

• Hotfix a bug on micado config

v0.12.5

What's New

• micado deploy renamed to micado up
• New commands to run YAML/CSAR ADTs: micado start, micado stop, micado info
• New command to edit demos: micado demo
• Under-the-hood improvements throughout

Full Changelog: v0.12.4...v0.12.5

v0.12.4

What's Changed

• Allow user named CB node by @jaydesl in #33

Full Changelog: v0.12.3...v0.12.4

v0.12.3

What's New

• fix an issue with post data for submissions

Full Changelog: v0.12.2...v0.12.3

v0.12.2

What's Changed

• fix: use yaml safe_load by @jaydesl in #32
• fix issue where params weren't passed alongside CSAR submissions

Full Changelog: v0.12.1...v0.12.2