Skip to content

Fix Octopus Server version on Calamari Image Volume page #3206

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
APErebus merged 1 commit into from
Jun 11, 2026
Merged

Fix Octopus Server version on Calamari Image Volume page #3206

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions src/pages/docs/kubernetes/targets/kubernetes-agent/calamari-image-volume.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
layout: src/layouts/Default.astro
pubDate: 2026-06-05
modDate: 2026-06-05
modDate: 2026-06-11
title: Calamari Image Volume
description: How the Kubernetes agent uses Kubernetes Image Volumes to provide Calamari to script pods
navOrder: 35
Expand All @@ -24,7 +24,7 @@ When the Calamari Image Volume feature is enabled, the agent instead mounts Cala

- **Kubernetes**: 1.35 or later. Image Volumes require the `ImageVolume` feature gate, which is enabled by default from Kubernetes 1.35 (Beta) and is GA from 1.36. Clusters running an older version will fall back to the existing transfer-and-unpack mechanism automatically and log a warning.
- **Kubernetes agent**: v3.5.0
- **Octopus Server**: 2026.3.892 or later
- **Octopus Server**: 2026.3.982 or later

## Enabling the feature

Expand Down