Support matrix¶
This page describes current normal execution flows. An adapter method alone is not a fully exposed product capability. See the usage guide for configuration.
Deployment and accounts¶
| Area | Boundary |
|---|---|
| Deployment | One instance and scheduler; SQLite WAL is not replica coordination, and there is no leader election |
| Official image | linux/amd64; the container currently runs as root |
| Administration | One administrator; no registration, RBAC, or tenant isolation |
| OIDC | One provider and one administrator binding; APIs use local JWTs |
| Network exposure | Backend CORS allows all origins by default; use HTTPS and access control in production. CORS is not authentication |
Runtime targets¶
| Target | Normal update path | Persisted pre-update config snapshot | Unified post-update probing | Recovery path |
|---|---|---|---|---|
| Docker / Podman single container | Recreate from inspected configuration | Supported | Supported | Manual rollback with a usable snapshot |
| Docker / Podman Compose group | Grouped recreation / Compose update path | Supported | Not integrated with the same probe pipeline | Manual rollback with a usable snapshot |
| Portainer standalone stack | Stack-file API update | Not generated by normal updates | Not integrated with the same probe pipeline | Restore through Portainer / saved stack configuration |
| Kubernetes workload | Patch image configuration | Not generated by normal updates | Not integrated with the same probe pipeline | Kubernetes-native history and recovery |
| Helm release | Helm upgrade | Not generated by normal updates | Not integrated with the same probe pipeline | Helm history and helm rollback |
Additional boundaries:
- Portainer Swarm, Kubernetes-type, and Git-backed stacks are unsupported. An unavailable Endpoint may fail during a request.
- Kubernetes workloads are limited to Deployment, StatefulSet, and DaemonSet, not Job / CronJob.
- Helm uses Helm 3 and Secret-backed discovery; ConfigMap storage is not covered by current discovery.
- No target automatically rolls back on update or health-check failure. Recovery does not restore persistent volumes or business databases.
- The Portainer adapter has snapshot/recovery methods, but normal updates do not generate snapshots. This does not imply routine UI rollback is available.
See Health checks and rollback for procedures and integrity requirements.
Sources and notifications¶
| Area | Support / limitation |
|---|---|
| Version sources | GitHub, GitLab, Gitea, Helm charts, OCI registries |
| Release channels | stable, prerelease, beta, canary |
| Filtering | Include / exclude regexes match tags, not release bodies or authors |
| Publication time | Depends on upstream metadata; first observed time is not actual publication time |
| Notifications | Webhook only, without custom request headers or durable failed-event replay |
Public-address restrictions for Webhooks and HTTP probes are described in Notification security. They do not apply identically to every kind of runtime network access.
Data and APIs¶
After database migrations, older application versions may not understand the new schema; follow Backup recovery for downgrades. Run history provides diagnostics, not a separate comprehensive audit-log system. APIs have no public stable versioning guarantee; inspect the current instance's /docs before integrating.
Implementation references: Snapshot gating, Grouped execution paths, Image publishing.