Self-hosted Omni managing a Talos cluster restricts access to networking resources during troubleshooting, specifically OperatorSpecs, LinkSpecs, VolumeConfigs, and machineconfigs. This limitation could slow incident response because runtime insights (e.g., DHCP status) are not readily accessible, and it’s unclear how workflow should differ when using Omni. The user asks whether these resources are effectively covered by VolumeStatus or if there is an equivalent, and how omnictl redactedclustermachineconfigs relates to machineconfigs. They want guidance and possibly enhancements to access or workflow for these resources during incidents and better documentation on conflicts with Omni.
Link: https://app.usepylon.com/issues?issueNumber=785
Self-hosted Omni managing a Talos cluster restricts access to networking resources during troubleshooting, specifically OperatorSpecs, LinkSpecs, VolumeConfigs, and machineconfigs. This limitation could slow incident response because runtime insights (e.g., DHCP status) are not readily accessible, and it’s unclear how workflow should differ when using Omni. The user asks whether these resources are effectively covered by VolumeStatus or if there is an equivalent, and how omnictl redactedclustermachineconfigs relates to machineconfigs. They want guidance and possibly enhancements to access or workflow for these resources during incidents and better documentation on conflicts with Omni.
Link: https://app.usepylon.com/issues?issueNumber=785