SaaS-simple deployment of Kubernetes - on your own hardware.
Go to file
Andrey Smirnov 5e468413a9
chore: add go.work file
This fixes `gopls` to look up usage correctly across sub-packages in the
same repo.

Signed-off-by: Andrey Smirnov <andrey.smirnov@siderolabs.com>
2024-07-01 21:08:34 +04:00
.github chore: add renovate.json 2024-06-04 00:08:51 +03:00
.vscode chore: initial commit 2024-02-29 17:19:57 +04:00
client chore: bump dependencies 2024-06-26 20:00:58 +03:00
cmd feat: support insecure access to the nodes running in maintenance 2024-06-26 15:37:59 +03:00
deploy chore: add barebones compose file 2024-04-05 12:49:26 -04:00
docs docs: add screenshot and install link 2024-03-29 09:25:06 -07:00
frontend feat: read real IP from the provision API gRPC requests 2024-06-26 16:13:48 +03:00
hack release(v0.38.0-beta.0): prepare release 2024-06-18 20:42:41 +03:00
internal fix: properly clean up stale Talos gRPC backends 2024-07-01 17:09:36 +03:00
.codecov.yml chore: run rekres 2024-05-23 20:34:11 +03:00
.conform.yaml chore: initial commit 2024-02-29 17:19:57 +04:00
.dockerignore chore: migrate to Vite and Bun to build the frontend 2024-06-06 18:40:07 +03:00
.gitignore chore: add go.work file 2024-07-01 21:08:34 +04:00
.golangci.yml feat: handle all goroutine panics gracefully 2024-06-20 21:28:12 +02:00
.kres.yaml chore: add go.work file 2024-07-01 21:08:34 +04:00
.license-header.go.txt chore: initial commit 2024-02-29 17:19:57 +04:00
.markdownlint.json chore: initial commit 2024-02-29 17:19:57 +04:00
.secrets.yaml chore: use new Auth0 app for CI 2024-05-06 12:57:23 +03:00
.sops.yaml chore: use sops for secrets 2024-04-19 14:03:55 +05:30
CHANGELOG.md release(v0.38.0-beta.0): prepare release 2024-06-18 20:42:41 +03:00
CONTRIBUTING.md chore: initial commit 2024-02-29 17:19:57 +04:00
DEVELOPMENT.md chore: drop integration binary from releases 2024-03-08 15:01:44 +05:30
Dockerfile chore: bump go to 1.22.4, rekres 2024-06-20 22:53:14 +02:00
go.mod chore: bump dependencies 2024-06-26 20:00:58 +03:00
go.sum chore: bump dependencies 2024-06-26 20:00:58 +03:00
go.work chore: add go.work file 2024-07-01 21:08:34 +04:00
LICENSE chore: initial commit 2024-02-29 17:19:57 +04:00
Makefile chore: add go.work file 2024-07-01 21:08:34 +04:00
README.md docs: fix a typo in the on-prem installation link 2024-05-27 13:29:36 +03:00
vetur.config.js chore: initial commit 2024-02-29 17:19:57 +04:00

Omni screenshot

SaaS-simple deployment of Kubernetes - on your own hardware.

Release Pre-release


Omni manages Kubernetes on bare metal, virtual machines, or in a cloud. Built on Talos Linux by the folks at Sidero.

Boot from an Omni image. Click to allocate to a cluster. Thats it!

  • Vanilla Kubernetes, on your machines, under your control.
  • Elegant UI for management and operations
  • Security taken care of—ties into your Enterprise ID provider
  • Highly Available Kubernetes API endpoint built in
  • Firewall friendly—manage edge nodes securely
  • From single-node clusters to the largest scale
  • Support for GPUs and most CSIs

Install

Omni is available via a Business Source License which allows free installations in non-production environments. If you would like to deploy Omni for production use please contact Sidero sales. If you would like to subscribe to the hosted version of Omni please see the SaaS pricing.

If you would like to self-host Omni for non-production workloads please follow the instructions in the documentation.

Development

For instructions on developing Omni, see DEVELOPMENT.md.

Community

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

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.

Licenses

The Omni code is released under a combination of two licenses:

When contributing to an Omni feature, you can find the relevant license in the comments at the top of each file.