You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| Progressing | <iclass="fa-solid fa-circle-notch blue"></i> | Objects in your application are currently in a progressing state |
47
46
| Healthy | <iclass="fa-solid fa-heart green"></i> | The objects in your cluster match what was specified in the last deployment |
48
-
| Unknown | <iclass="fa-solid fa-question grey"></i> | We’re having trouble getting live status updates for this application |
47
+
| Unknown | <iclass="fa-solid fa-question grey"></i> | We're having trouble getting live status updates for this application |
49
48
| Degraded | <iclass="fa-solid fa-heart-crack red"></i> | Your objects experienced errors after the deployment completed |
50
49
| Out of Sync | <iclass="fa-solid fa-arrow-up orange"></i> | The objects on your cluster no longer match what you last deployed |
51
50
| Missing | <iclass="fa-solid fa-ghost grey"></i> | Objects in your application are currently in a missing state |
@@ -116,6 +115,61 @@ The Kubernetes Agent has a new component called the Kubernetes monitor which als
116
115
117
116
During a deployment, Octopus will capture any applied Kubernetes manifests and send them to the monitor. The monitor uses these manifests to track the deployed objects in the cluster, keeping track of their synchronization and health.
118
117
118
+
### Script steps
119
+
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.
121
+
122
+
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.
123
+
124
+
Only the "Run a kubectl script" step will correctly report manifests, regular "Run a script" steps are not supported.
125
+
126
+
:::div{.info}
127
+
You still need to apply the Kubernetes manifests to your cluster. These functions only notify Octopus that you expect the resources to be created.
0 commit comments