Justin Garrison
Justin Garrison
## Feature Request `talosctl cluster create --omni myomni.siderolabs.com` ### Description I'd like to be able to create Omni nodes for testing in a similar way to local talos clusters. We...
## Feature Request I would like a kernel flag that can enable [grpc api reflection](https://grpc.io/docs/guides/reflection/) for exploring the Talos API and making it easier to build tools that use the...
fixes #49 By not using oneshot service type and not detaching the docker compose command you can use normal systemd tools (e.g. journalctl) for logs. Docker commands still work too.
Explicitly forward required ports so the containers don't run with host networking which also causes the containers to run as privileged.
With Talos 1.10 we now use [systemd-boot for UEFI systems](https://www.talos.dev/v1.10/introduction/what-is-new/#dual-boot-disk-images-and-isos) (not just secure boot) but the default build from the image factory uses the dual-boot imager option which makes very...
Issues and prioritise for September-December 2025
### Problem Description When users have multiple clusters and they want to test configuration changes or upgrades they have to manually create a new cluster, apply the configuration, deploy workloads,...
### Problem Description We need to be able to scrape discovery metrics from an Omni instance in a similar way to how we pull metrics from the discovery service. ###...
### Problem Description Omni can be [deployed on-prem with a container](https://omni.siderolabs.com/how-to-guides/self_hosted/index) but it requires a lot of configuration to get started which could be automated or bundled in a way...
### Problem Description Customers need a way to promote configuration and patching between clusters and nodes. We need a way to allow customers to identify clusters by environment (eg dev,...