e782dff4b6
This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [github.com/onsi/ginkgo/v2](https://redirect.github.com/onsi/ginkgo) | `v2.23.0` -> `v2.23.1` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | --- ### Release Notes <details> <summary>onsi/ginkgo (github.com/onsi/ginkgo/v2)</summary> ### [`v2.23.1`](https://redirect.github.com/onsi/ginkgo/releases/tag/v2.23.1) [Compare Source](https://redirect.github.com/onsi/ginkgo/compare/v2.23.0...v2.23.1) #### 2.23.1 #### 🚨 For users on MacOS 🚨 A long-standing Ginkgo performance issue on MacOS seems to be due to mac's antimalware XProtect. You can follow the instructions [here](https://onsi.github.io/ginkgo/#if-you-are-running-on-macos) to disable it in your terminal. Doing so sped up Ginkgo's own test suite from 1m8s to 47s. ##### Fixes Ginkgo's CLI is now a bit clearer if you pass flags in incorrectly: - make it clearer that you need to pass a filename to the various profile flags, not an absolute directory \[[`a0e52ff`](https://redirect.github.com/onsi/ginkgo/commit/a0e52ff)] - emit an error and exit if the ginkgo invocation includes flags after positional arguments \[[`b799d8d`](https://redirect.github.com/onsi/ginkgo/commit/b799d8d)] This might cause existing CI builds to fail. If so then it's likely that your CI build was misconfigured and should be corrected. Open an issue if you need help. </details> --- ### Configuration 📅 **Schedule**: Branch creation - "after 11pm every weekday,before 7am every weekday,every weekend" in timezone Europe/Brussels, Automerge - At any time (no schedule defined). 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/kairos-io/provider-kairos). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4yMDcuMSIsInVwZGF0ZWRJblZlciI6IjM5LjIwNy4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119--> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> |
||
|---|---|---|
| .github | ||
| cli/kairosctl | ||
| internal | ||
| .golangci.yml | ||
| .goreleaser.yaml | ||
| .yamllint | ||
| go.mod | ||
| go.sum | ||
| LICENSE | ||
| main.go | ||
| maintainers.md | ||
| osv-scanner.toml | ||
| README.md | ||
| renovate.json | ||
Kairos standard provider
Kairos standard provider
With Kairos you can build immutable, bootable Kubernetes and OS images for your edge devices as easily as writing a Dockerfile. Optional P2P mesh with distributed ledger automates node bootstrapping and coordination. Updating nodes is as easy as CI/CD: push a new image to your container registry and let secure, risk-free A/B atomic upgrades do the rest.
|
Documentation |
Contribute |
|---|---|
|
📚 Getting started with Kairos |
Provider kairos
This repository hosts the code for provider binary used in Kairos "standard" images which offer full-mesh support. full-mesh support currently is available only with k3s, and the provider follows strictly k3s releases.
Note
The provider-kairos release pipelines have been merged with the kairos ones from version
2.4.0onward. All image artifacts are released from the kairos repository, both core images and standard images (those with the provider).
To use Kairos with mesh support, download the bootable medium form the kairos releases.
Follow up the examples in our documentation on how to get started:
- https://kairos.io/docs/examples/single-node/
- https://kairos.io/docs/examples/multi-node/
- https://kairos.io/docs/examples/multi-node-p2p-ha-kubevip/
Upgrades
Upgrading can be done either via Kubernetes or manually with kairos-agent upgrade --image <image>, or you can list available versions with kairos-agent upgrade list-releases.
Container images available for upgrades are pushed to quay, you can check out the image matrix in our documentation.