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: docs/spec/v1beta1/imageupdateautomations.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -611,11 +611,17 @@ type UpdateStrategy struct {
611
611
// Path to the directory containing the manifests to be updated.
612
612
// Defaults to 'None', which translates to the root path
613
613
// of the GitRepositoryRef.
614
+
// When a path is specified, sparse checkout will be enabled to limit the checkout scope
615
+
// to the specified directory, reducing clone size and time.
614
616
// +optional
615
617
Path string `json:"path,omitempty"`
616
618
}
617
619
```
618
620
621
+
By default, the `path` is empty, which means that the root of the git repository is used.
622
+
If a path is specified, the controller will use a sparse checkout to limit the checkout scope to the specified directory, which can reduce clone size and time.
623
+
But this can be disabled by starting the controller with `--feature-gates=GitSparseCheckout=false`.
624
+
619
625
**Setters strategy**
620
626
621
627
At present, there is one strategy: "Setters". This uses field markers referring to image policies,
0 commit comments