Omni Future Issues

[smira]

Nice to have tasks

• Rewrite MachineSetNode controller to use qcontrollers #556
• talosctl common commands to work with Omni #16
• [feature] Alerts and notifications #227
• [feature] Allow disabling of authentication options #3
• [feature] allow for bypassing downgrade check #235
• Metrics for enabled features #22
• [feature] SDK example for using Omni API #901
• When using omnictl include status to the yaml output #902
• [feature] support "bare install" from ISO/pxe #268
• [feature] Send welcome email to new users #313
• [feature] machines distribution across zones #395
• [feature] Modify Raspberry Pi Firmware #537
• [feature] Secrets stored in omni #572
• Templates for account wide resources #903
• [feature] implement omnictl edit #905
• [feature] Add option to set worker nodes to PreferNoSchedule prior to Talos upgrade #846
• Omni audit logs future ideas #694
• [feature] Omni logs export #928
• [feature] Omni to set node-role.kubernetes.io label #751
• [feature] custom Talos readiness probes #1277

UI Improvements

• Config Patch UX #359
• Introduce ExposedServiceStatus and display it on the UI #555

Talos Simulator Testing

• Omni load tests: several huge clusters scaling up and down in parallel #476
• Omni automated load tests: huge amount of single node clusters #477
• Simulate etcd in the Talos emulator closer to the real life #904

On Prem

• upgrade documentation and testing #511

Operations

• [feature] Custom Domain for omni in SaaS model #762