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
|`-s`, `--client-secret <FALCON_CLIENT_SECRET>`|`$FALCON_CLIENT_SECRET`|`None` (Required) | CrowdStrike API Client Secret |
159
157
|`-r`, `--region <FALCON_CLOUD>`|`$FALCON_CLOUD`|`us-1` (Optional) | CrowdStrike Region. <br>\**Auto-discovery is only available for [`us-1, us-2, us-3, eu-1`] regions.*|
160
158
|`-c`, `--copy <REGISTRY/NAMESPACE>`|`$COPY`|`None` (Optional) | Registry you want to copy the sensor image to. Example: `myregistry.com/mynamespace`. <br> *\*By default, the image name and tag are appended. Use `--copy-omit-image-name` and/or `--copy-custom-tag` to change that behavior.*|
161
-
|`-v`, `--version <SENSOR_VERSION>`|`$SENSOR_VERSION`|`None` (Optional) | Specify sensor version to retrieve from the registry. Accepts version strings (e.g., `7.33`, `7.33.0`) or channel keywords: `latest`, `N-1`, `N-2`, `LTS`, `LTS-1`|
159
+
|`-v`, `--version <SENSOR_VERSION>`|`$SENSOR_VERSION`|`None` (Optional) | Specify sensor version to retrieve from the registry. Accepts version strings (e.g., `7.33`, `7.33.0`) or channel keywords: `latest`, `N-1`, `N-2`|
162
160
|`-p`, `--platform <SENSOR_PLATFORM>`|`$SENSOR_PLATFORM`|`None` (Optional) | Specify sensor platform to retrieve from the registry |
163
161
|`-t`, `--type <SENSOR_TYPE>`|`$SENSOR_TYPE`|`falcon-container` (Optional) | Specify which sensor to download [`falcon-container`, `falcon-container-regional`, `falcon-sensor`, `falcon-sensor-regional`, `falcon-kac`, `falcon-kac-regional`, `falcon-snapshot`, `falcon-imageanalyzer`, `falcon-imageanalyzer-regional`, `fcs`, `falcon-jobcontroller`, `falcon-registryassessmentexecutor`] ([see more details below](#sensor-types)) |
164
162
|`--runtime`|`$CONTAINER_TOOL`|`docker` (Optional) | Use a different container runtime [docker, podman, skopeo]. **Default is Docker**. |
@@ -209,13 +207,8 @@ The `-v, --version` flag accepts channel keywords for policy-driven deployments
209
207
|`latest`| Latest sensor version (default) |
210
208
|`N-1`| One release prior to the latest |
211
209
|`N-2`| Two releases prior to the latest |
212
-
|`LTS`| Latest LTS release |
213
-
|`LTS-1`| Previous LTS release |
214
210
215
-
Channel keywords are case-insensitive (`n-1`, `N-1`, `lts`, `LTS` all work). N-1/N-2 step back through releases and exclude LTS tags from consideration. No additional API scopes are required — channels are resolved entirely from existing registry tag data.
216
-
217
-
> [!NOTE]
218
-
> LTS (Long Term Support) sensor release tags are not yet generally available. The `LTS` and `LTS-1` keywords are included ahead of that release and will return an error until LTS-tagged images are published to the registry.
211
+
Channel keywords are case-insensitive (`n-1` and `N-1` both work). N-1/N-2 step back through releases. No additional API scopes are required — channels are resolved entirely from existing registry tag data.
219
212
220
213
```shell
221
214
# Pull latest (default behavior)
@@ -229,17 +222,6 @@ Channel keywords are case-insensitive (`n-1`, `N-1`, `lts`, `LTS` all work). N-1
229
222
--client-secret <FALCON_CLIENT_SECRET> \
230
223
--version N-1
231
224
232
-
# Pull the latest LTS release
233
-
./falcon-container-sensor-pull.sh \
234
-
--client-id <FALCON_CLIENT_ID> \
235
-
--client-secret <FALCON_CLIENT_SECRET> \
236
-
--version LTS
237
-
238
-
# Pull the previous LTS release
239
-
./falcon-container-sensor-pull.sh \
240
-
--client-id <FALCON_CLIENT_ID> \
241
-
--client-secret <FALCON_CLIENT_SECRET> \
242
-
--version LTS-1
243
225
```
244
226
245
227
### Examples
@@ -300,17 +282,14 @@ Example output: `registry.crowdstrike.com/falcon-sensor/release/falcon-sensor:7.
300
282
301
283
#### Example mirroring a version channel to another registry
302
284
303
-
The following example resolves the latest LTS release and copies it to an internal registry, so downstream consumers pull from a controlled mirror.
304
-
305
-
> [!NOTE]
306
-
> LTS tags may not yet be available in the registry. See the [Version Channels](#version-channels) note above for details.
285
+
The following example resolves the N-2 release and copies it to an internal registry, so downstream consumers pull from a controlled mirror.
0 commit comments