OpenFrame Documentation
Deployment guides, the CLI reference, architecture and admin guides for OpenFrame
Flamingo Raises $4.5M Seed Round · Led by Vertex Ventures, bringing total funding to $6.7M to build the open, AI-native layer for IT and security.
Deployment guides, the CLI reference, architecture and admin guides for OpenFrame
This task covers two related upgrades — updating the openframe command-line tool itself to a newer release, and upgrading the OpenFrame platform (ArgoCD and the app-of-apps) already deployed on a cluster — and is done by whoever operates the cluster, from a terminal with the openframe CLI installed.
openframe CLI installed and on your $PATH. Check with openframe --version or openframe update check.openframe app install — openframe app upgrade upgrades an already-installed platform, it does not install one.openframe binary is writable by your user (an installation made by a package manager or an elevated/admin install may block the CLI's self-update — see Troubleshooting).openframe update) runs only inside WSL2; the native Windows launcher cannot update itself this way.openframe update check. This only reports status and changes nothing.<version>)", "Update available: <current> → <latest>" with the release URL, or (on a development build) "Development build — no release to compare against."openframe update. When a newer version exists you are prompted to confirm with a message naming the direction of the change ("Update", "Downgrade", or "Reinstall" from <current> to <target>); confirm with y, or pass --yes to skip the prompt (for example in a script).openframe update v1.4.0 (replace v1.4.0 with the desired tag). This works both to move up and to move back down to an older tag.openframe update --force.openframe update rollback. This reverts offline, with no download, and also asks for confirmation unless you pass --yes.openframe app upgrade --ref v1.3.0 (replace v1.3.0 with the release tag or branch you want to deploy). Add --context <kube-context> or pass a cluster name as an argument if the platform is not on your current kubectl context.--dry-run to the same command, for example openframe app upgrade --ref main --dry-run.openframe app upgrade --sync instead of --ref.--prune to the sync command: openframe app upgrade --sync --prune. Only do this when you intend that deletion, since it is destructive.openframe app status (see the separate how-to for checking cluster and app status).openframe update check prints one of: Already up to date (<version>)., Update available: <current> → <latest> followed by the release URL, or Development build — no release to compare against.openframe update (or openframe update <version>) ends with OpenFrame CLI is now <tag>.openframe update rollback ends with Rolled back to <version-or-"the previous version">.openframe app upgrade --ref <tag> prints Upgrading OpenFrame to ref "<tag>" and proceeds through the install sequence non-interactively, reusing your existing configuration.openframe app upgrade --sync (force-sync mode) prints Refreshing and syncing the OpenFrame platform... and finishes with OpenFrame platform re-synced.--sync --dry-run, instead of applying anything you see a preview: either All <N> applications are Synced; a force-sync would be a no-op. or a count of applications that would be re-synced, listed as OutOfSync: <name> (health=<health>, sync=<sync>).--ref and --sync are mutually exclusive" — you passed both flags to openframe app upgrade. Decide whether you want to deploy a new ref (--ref) or re-sync the current one (--sync), and drop the other flag.--sync --dry-run) — the target cluster has no installed platform to upgrade; install it first rather than upgrading.openframe update is not supported for the native Windows binary; re-run the Windows installer to update it, since only the WSL-side Linux binary can self-update.<path>: ... not writable (installed with elevated privileges or by a package manager?)" — the directory holding the running binary cannot be written to by your user; reinstall the CLI somewhere you own, or update it with the same elevated method you used to install it.<tag> is not signed (no ..bundle), refusing to update" — the CLI could not verify the release's signature and will not proceed; this is a security check and should not be bypassed except knowingly, by setting the documented insecure-skip environment variable at your own risk.openframe update rollback has nothing to revert to because no earlier update saved a backup; there is nothing further to do.For a related task, see how to check platform health after an upgrade in Check the status of your OpenFrame cluster and apps, or how the platform gets installed in the first place in Install the OpenFrame platform onto a cluster.