Skip to content

Commit d5834fe

Browse files
committed
Clarify which script steps are supported
1 parent 338b8d4 commit d5834fe

File tree

1 file changed

+8
-1
lines changed
  • src/pages/docs/kubernetes/live-object-status

1 file changed

+8
-1
lines changed

src/pages/docs/kubernetes/live-object-status/index.md

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -117,14 +117,21 @@ During a deployment, Octopus will capture any applied Kubernetes manifests and s
117117

118118
### Script steps
119119

120-
The built in Kubernetes steps will automatically report the applied manifests for deployments, however Octopus needs a bit of help when you're making changes using plain script steps.
120+
The built in Kubernetes steps will automatically report the applied manifests for deployments, however Octopus needs a bit of help when you're making changes using kubectl script steps.
121121

122122
To notify Octopus which Kubernetes resources you want tracked, we have bash and powershell helper functions available to use. You can choose between passing the manifest as a variable, or passing the file path directly instead.
123123

124+
Only the "Run a kubectl script" step will correctly report manifests, regular "Run a script" steps are not supported.
125+
124126
:::div{.info}
125127
You still need to apply the Kubernetes manifests to your cluster. These functions only notify Octopus that you expect the resources to be created.
126128
:::
127129

130+
Available in Octopus server versions:
131+
132+
- 2025.4.10333+
133+
- 2026.1.4557+
134+
128135
#### Bash
129136

130137
```bash

0 commit comments

Comments
 (0)