Konstruct 0.5.2
Released: May 2026
Highlights
- Delete environments — Team Admins and Platform Admins can now remove an environment from the UI, and Konstruct cleans it up across both GitOps repos (Platform and Applications) automatically
Delete an Environment
Through 0.5.1, environments could be created but not removed — stale dev-feature-x and one-off test envs had to be cleaned up by hand in Git. 0.5.2 adds a Delete action to the environment row in the Environments list and on the environment detail page.
Who can delete:
| Role | Can delete |
|---|---|
| Platform Admin | Any environment, including Global |
| Team Admin | Environments in the organization they administer |
When you confirm deletion, Konstruct runs a three-phase cleanup so you don't have to touch either GitOps repository manually:
- Platform GitOps — Konstruct removes the environment's
45-env-*.yamlfile from your platform GitOps repository. This is what tells Argo CD the environment no longer exists. - Argo CD drain — Konstruct waits for Argo CD to finish removing the applications that were syncing into the environment's folder, so nothing keeps reconciling after the environment is gone.
- Application GitOps — once Argo CD has drained, Konstruct removes the environment's folder from your application GitOps repository.
Deletion is permanent. The environment's name becomes available for reuse once the cleanup completes.
Upgrade
Update targetRevision to 0.5.2 in your Konstruct Argo CD Application manifest, keeping the required global values from 0.5.0:
spec:
source:
chart: konstruct
repoURL: oci://europe-west2-docker.pkg.dev/civo-com/charts
targetRevision: 0.5.2
helm:
values: |
global:
selfHosted: "true"
bootstrap: "false"
Commit and push — Argo CD syncs the new version automatically.
You can delete environments created on 0.5.1 and earlier as soon as the upgrade finishes; no migration required.