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
Copy file name to clipboardExpand all lines: README.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -563,7 +563,10 @@ def gitopsConfig = [
563
563
564
564
In plain pipelines, the library creates the deployment resources by updating the image tag within the deployment.
565
565
566
-
---
566
+
Note that this works with Kubernetes `Deployment`s, `StatefulSet`s and `CronJob`s. For all other kinds of resources the
567
+
library tries to find the `containers` at the following YAML path: `spec.template.spec.containers`. This might fail, of course. If you encounter a case
568
+
like this, please create an issue. Eventually, we're planning to provide a `fieldPath` option just like in helm releases.
569
+
567
570
568
571
### Helm deployment
569
572
Besides plain k8s resources you can also use helm charts to generate the resources. You can choose between these types
0 commit comments