Getting Started
Upgrades
How to upgrade AIOStack to a newer version using image tags or a rolling restart.
Upgrading to a specific version
If you're pinned to a specific image tag, upgrade by setting the new version in your Helm release:
Terminal
helm upgrade myaiostack aiostack/aiostack \
--namespace aiostack \
--set observer.version=<NEW_VERSION> \
--set outpost.version=<NEW_VERSION> \
--reuse-values
--reuse-values carries over all your existing configuration so you only need to specify what's changing.
Upgrading when running latest
If your deployment uses latest as the image tag, the pods won't automatically pull a new image unless you trigger a rollout. Force a restart with imagePullPolicy: Always:
Terminal
# Restart the observer DaemonSet
kubectl rollout restart daemonset -n aiostack -l app.kubernetes.io/name=observer
# Restart the outpost deployment
kubectl rollout restart deployment -n aiostack -l app.kubernetes.io/name=outpost
# Watch the rollout progress
kubectl rollout status daemonset -n aiostack -l app.kubernetes.io/name=observer
For this to pull a fresh image, the pods must have
imagePullPolicy: Always set. If they're using IfNotPresent, the node will use its cached image even after a restart.Keeping track of releases
AIOStack releases are managed through Aurva. For release notes, upgrade advisories, and guidance on when to upgrade, reach out to your Aurva support representative — they'll keep you informed of new versions and any breaking changes before they affect your deployment.
For general questions: support@aurva.io