azure/siteops
Install Site Ops and use it to deploy, upgrade and troubleshoot Azure IoT Operations on Kubernetes clusters connected to Azure Arc, confirming each plan before it runs.
Deploy Azure IoT Operations (AIO) with Site Ops to one or several existing Kubernetes clusters connected to Azure Arc, optionally with Secret Sync, or enable Secret Sync on an existing AIO instance. Use when the user asks in plain language to install, deploy or set up AIO, IoT Operations or Secret Sync on a cluster or a fleet. Do not use it to upgrade an existing AIO installation (use upgrade-aio) or to install Site Ops itself (use install-siteops).
Find out what Site Ops can deploy from a Scale Kit release or another approved source, what a manifest such as aio-install or secretsync does, which inputs and prerequisites it needs, and what its plan would change, without deploying anything. Use when the user asks what Site Ops or Scale Kit can deploy, what a manifest does, what it needs, or wants to preview a deployment. Do not use it to deploy (use deploy-aio or upgrade-aio).
Install, update or repair Site Ops (the siteops command) from a verified official Scale Kit release with its bootstrap script, enroll the official content source, and fix a siteops command that is not found. Use when the user asks to install, set up, update or check Site Ops, or when another Site Ops skill finds siteops missing or incompatible with a release. Do not use it to deploy Azure IoT Operations (use deploy-aio).
Diagnose and fix Site Ops (siteops) errors and failed Azure IoT Operations deployments, including installation problems, approved source and verification errors, Azure CLI sign in and permission errors, typed input errors, Site selection errors, and failed, unknown or not run operations. Use when a siteops command fails or prints an error, or when the user asks why a Site Ops deployment did not work. Do not use it to start a new deployment (use deploy-aio).
Upgrade an existing Azure IoT Operations (AIO) installation to a newer AIO release with Site Ops, on one cluster or a fleet of saved Sites, by changing each Site's AIO release and running the aio-upgrade manifest. Use when the user asks to upgrade AIO or move it to a newer AIO release such as 2609. Do not use it for a new installation (use deploy-aio), to change AIO settings, or to update Site Ops itself (use install-siteops).