5fb38d3e5f
This has two big visible changes: * `installer` image now contains assets for both `amd64` and `arm64`, so it can be used to generate any Talos image (including RPi on amd64 host) * Talos is using cross-compilation instead of emulation to build non-native architectures: on amd64, Go amd64 compiler produces binaries for both arm64 and amd64 (before this change: Go arm64 compiler via QEMU produces arm64 binaries on amd64) CI implications: we no longer require arm64 nodes. Changes walkthrough: * `installer` container now keeps assets under `/usr/install/<arch>` * Dockerfile build starts forcing toolchain/base image to use the build host native architecture, not target architecture * lots of duplication for amd64/arm64 as we want to combine assets for both arches in a single image (e.g. we have multi-arch amd64/arm64 installer image, each arch has native installer binary, but both arches contain full set of amd64/arm64 assets) * fixed a small bug preventing arm64 on amd64 talosctl cluster create Signed-off-by: Andrey Smirnov <smirnov.andrey@gmail.com> |
||
|---|---|---|
| .github | ||
| api | ||
| cmd | ||
| docs | ||
| hack | ||
| internal | ||
| pkg | ||
| website | ||
| .codecov.yml | ||
| .conform.yaml | ||
| .dockerignore | ||
| .drone.jsonnet | ||
| .gitignore | ||
| .golangci.yml | ||
| .markdownlint.json | ||
| CHANGELOG.md | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| Dockerfile | ||
| go.mod | ||
| go.sum | ||
| LICENSE | ||
| Makefile | ||
| netlify.toml | ||
| prototool.yaml | ||
| README.md | ||
Talos
A modern OS for Kubernetes.
Talos is a modern OS designed to be secure, immutable, and minimal. All system management is done via an API, and there is no shell or interactive console. Some of the capabilities and benefits provided by Talos include:
- Security: Talos reduces your attack surface by practicing the Principle of Least Privilege (PoLP) and by securing the API with mutual TLS (mTLS) authentication.
- Predictability: Talos eliminates unneeded variables and reduces unknown factors in your environment by employing immutable infrastructure ideology.
- Evolvability: Talos simplifies your architecture and increases your ability to easily accommodate future changes.
Documentation
For instructions on deploying and managing Talos, see the Documentation.
Community
- Slack: Join our slack channel
- Support: Questions, bugs, feature requests GitHub Discussions
- Forum: community
- Twitter: @talossystems
- Email: info@talos-systems.com
If you're interested in this project and would like to help in engineering efforts, or have general usage questions, we are happy to have you! We hold a weekly meeting that all audiences are welcome to attend.
Office Hours
- When: Mondays at 17:00 UTC.
- Where: Google Meet.
You can subscribe to this meeting by joining the community forum above.
Note: You can convert the meeting hours to your local time.
Contributing
Contributions are welcomed and appreciated! See Contributing for our guidelines.
License
