Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: fix scopes and required parameters for IAR #603

Merged
merged 1 commit into from
Dec 11, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 5 additions & 11 deletions docs/deployment/openshift/resources/imageanalyzer/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,8 +8,9 @@ To start the FalconImageAnalyzer installation using CrowdStrike API Keys to allo

> [!IMPORTANT]
> You will need to provide CrowdStrike API Keys and CrowdStrike cloud region for the installation. It is recommended to establish new API credentials for the installation at https://falcon.crowdstrike.com/support/api-clients-and-keys, required permissions are:
> * Falcon Container CLI: **Write**
> * Falcon Container Image: **Read/Write**
> * Falcon Images Download: **Read**
> * Sensor Download: **Read**

Example:

Expand Down Expand Up @@ -46,7 +47,7 @@ spec:
| registry.type | Registry to mirror Falcon Image Analyzer (allowed values: acr, ecr, crowdstrike, gcr, openshift) |
| registry.tls.insecure_skip_verify | (optional) Skip TLS check when pushing Falcon Image Analyzer to target registry (only for demoing purposes on self-signed openshift clusters) |
| registry.tls.caCertificate | (optional) A string containing an optionally base64-encoded Certificate Authority Chain for self-signed TLS Registry Certificates |
| registry.tls.caCertificateConfigMap | (optional) The name of a ConfigMap containing CA Certificate Authority Chains under keys ending in ".tls" for self-signed TLS Registry Certificates (ignored when registry.tls.caCertificate is set) |
| registry.tls.caCertificateConfigMap | (optional) The name of a ConfigMap containing CA Certificate Authority Chains under keys ending in ".tls" for self-signed TLS Registry Certificates (ignored when registry.tls.caCertificate is set) |
| registry.acr_name | (optional) Name of ACR for the Falcon Falcon Image Analyzer push. Only applicable to Azure cloud. (`registry.type="acr"`) |
| imageAnalyzerConfig.serviceAccount.annotations | (optional) Configure annotations for the falcon-iar service account (e.g. for IAM role association) |
| imageAnalyzerConfig.azureConfigPath | (optional) Azure config file path |
Expand All @@ -63,10 +64,6 @@ spec:
| imageAnalyzerConfig.resources | (optional) Configure the resources of the Falcon Image Analyzer |
| imageAnalyzerConfig.updateStrategy | (optional) Configure the deployment update strategy of the Falcon Image Analyzer |


> [!IMPORTANT]
> All arguments are optional, but successful deployment requires either **client_id and client_secret or the Falcon cid and image**. When deploying using the CrowdStrike Falcon API, the container image and CID will be fetched from CrowdStrike Falcon API. While in the latter case, the CID and image location is explicitly specified by the user.

### Auto Proxy Configuration

The operator will automatically configure the sensor's proxy configuration when the cluster proxy is configured on OpenShift via OLM. See the following documentation for more information:
Expand Down Expand Up @@ -137,7 +134,7 @@ To uninstall Falcon Image Analyzer simply remove the FalconImageAnalyzer resourc

```sh
oc delete falconimageanalyzer --all
```
```

### Sensor upgrades

Expand All @@ -153,7 +150,7 @@ To upgrade the sensor version, simply add and/or update the `version` field in t
falcon-image-analyzer 0.8.0 1.0.9
```

This is helpful information to use as a starting point for troubleshooting.
This is helpful information to use as a starting point for troubleshooting.
You can get more insight by viewing the FalconImageAnalyzer CRD in full detail by running the following command:

```sh
Expand All @@ -179,6 +176,3 @@ To upgrade the sensor version, simply add and/or update the `version` field in t
### Additional Documentation
End-to-end guide(s) to install Falcon-operator together with FalconImageAnalyzer resource.
- [Deployment Guide for OpenShift](../../README.md)



16 changes: 5 additions & 11 deletions docs/resources/imageanalyzer/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,8 +8,9 @@ To start the FalconImageAnalyzer installation using CrowdStrike API Keys to allo

> [!IMPORTANT]
> You will need to provide CrowdStrike API Keys and CrowdStrike cloud region for the installation. It is recommended to establish new API credentials for the installation at https://falcon.crowdstrike.com/support/api-clients-and-keys, required permissions are:
> * Falcon Container CLI: **Write**
> * Falcon Container Image: **Read/Write**
> * Falcon Images Download: **Read**
> * Sensor Download: **Read**

Example:

Expand Down Expand Up @@ -46,7 +47,7 @@ spec:
| registry.type | Registry to mirror Falcon Image Analyzer (allowed values: acr, ecr, crowdstrike, gcr, openshift) |
| registry.tls.insecure_skip_verify | (optional) Skip TLS check when pushing Falcon Image Analyzer to target registry (only for demoing purposes on self-signed openshift clusters) |
| registry.tls.caCertificate | (optional) A string containing an optionally base64-encoded Certificate Authority Chain for self-signed TLS Registry Certificates |
| registry.tls.caCertificateConfigMap | (optional) The name of a ConfigMap containing CA Certificate Authority Chains under keys ending in ".tls" for self-signed TLS Registry Certificates (ignored when registry.tls.caCertificate is set) |
| registry.tls.caCertificateConfigMap | (optional) The name of a ConfigMap containing CA Certificate Authority Chains under keys ending in ".tls" for self-signed TLS Registry Certificates (ignored when registry.tls.caCertificate is set) |
| registry.acr_name | (optional) Name of ACR for the Falcon Falcon Image Analyzer push. Only applicable to Azure cloud. (`registry.type="acr"`) |
| imageAnalyzerConfig.serviceAccount.annotations | (optional) Configure annotations for the falcon-iar service account (e.g. for IAM role association) |
| imageAnalyzerConfig.azureConfigPath | (optional) Azure config file path |
Expand All @@ -63,10 +64,6 @@ spec:
| imageAnalyzerConfig.resources | (optional) Configure the resources of the Falcon Image Analyzer |
| imageAnalyzerConfig.updateStrategy | (optional) Configure the deployment update strategy of the Falcon Image Analyzer |


> [!IMPORTANT]
> All arguments are optional, but successful deployment requires either **client_id and client_secret or the Falcon cid and image**. When deploying using the CrowdStrike Falcon API, the container image and CID will be fetched from CrowdStrike Falcon API. While in the latter case, the CID and image location is explicitly specified by the user.

### Auto Proxy Configuration

The operator will automatically configure the sensor's proxy configuration when the cluster proxy is configured on OpenShift via OLM. See the following documentation for more information:
Expand Down Expand Up @@ -137,7 +134,7 @@ To uninstall Falcon Image Analyzer simply remove the FalconImageAnalyzer resourc

```sh
kubectl delete falconimageanalyzer --all
```
```

### Sensor upgrades

Expand All @@ -153,7 +150,7 @@ To upgrade the sensor version, simply add and/or update the `version` field in t
falcon-image-analyzer 0.8.0 1.0.9
```

This is helpful information to use as a starting point for troubleshooting.
This is helpful information to use as a starting point for troubleshooting.
You can get more insight by viewing the FalconImageAnalyzer CRD in full detail by running the following command:

```sh
Expand Down Expand Up @@ -183,6 +180,3 @@ End-to-end guide(s) to install Falcon-operator together with FalconImageAnalyzer
- [Deployment Guide for EKS Fargate](../../deployment/eks-fargate/README.md)
- [Deployment Guide for GKE/GCR](../../deployment/gke/README.md)
- [Deployment Guide for OpenShift](../../deployment/openshift/README.md)



16 changes: 5 additions & 11 deletions docs/src/resources/imageanalyzer.md.tmpl
Original file line number Diff line number Diff line change
Expand Up @@ -8,8 +8,9 @@ To start the FalconImageAnalyzer installation using CrowdStrike API Keys to allo

> [!IMPORTANT]
> You will need to provide CrowdStrike API Keys and CrowdStrike cloud region for the installation. It is recommended to establish new API credentials for the installation at https://falcon.crowdstrike.com/support/api-clients-and-keys, required permissions are:
> * Falcon Container CLI: **Write**
> * Falcon Container Image: **Read/Write**
> * Falcon Images Download: **Read**
> * Sensor Download: **Read**

Example:

Expand Down Expand Up @@ -46,7 +47,7 @@ spec:
| registry.type | Registry to mirror Falcon Image Analyzer (allowed values: acr, ecr, crowdstrike, gcr, openshift) |
| registry.tls.insecure_skip_verify | (optional) Skip TLS check when pushing Falcon Image Analyzer to target registry (only for demoing purposes on self-signed openshift clusters) |
| registry.tls.caCertificate | (optional) A string containing an optionally base64-encoded Certificate Authority Chain for self-signed TLS Registry Certificates |
| registry.tls.caCertificateConfigMap | (optional) The name of a ConfigMap containing CA Certificate Authority Chains under keys ending in ".tls" for self-signed TLS Registry Certificates (ignored when registry.tls.caCertificate is set) |
| registry.tls.caCertificateConfigMap | (optional) The name of a ConfigMap containing CA Certificate Authority Chains under keys ending in ".tls" for self-signed TLS Registry Certificates (ignored when registry.tls.caCertificate is set) |
| registry.acr_name | (optional) Name of ACR for the Falcon Falcon Image Analyzer push. Only applicable to Azure cloud. (`registry.type="acr"`) |
| imageAnalyzerConfig.serviceAccount.annotations | (optional) Configure annotations for the falcon-iar service account (e.g. for IAM role association) |
| imageAnalyzerConfig.azureConfigPath | (optional) Azure config file path |
Expand All @@ -63,10 +64,6 @@ spec:
| imageAnalyzerConfig.resources | (optional) Configure the resources of the Falcon Image Analyzer |
| imageAnalyzerConfig.updateStrategy | (optional) Configure the deployment update strategy of the Falcon Image Analyzer |


> [!IMPORTANT]
> All arguments are optional, but successful deployment requires either **client_id and client_secret or the Falcon cid and image**. When deploying using the CrowdStrike Falcon API, the container image and CID will be fetched from CrowdStrike Falcon API. While in the latter case, the CID and image location is explicitly specified by the user.

### Auto Proxy Configuration

{{ template "proxy.tmpl" . }}
Expand Down Expand Up @@ -111,7 +108,7 @@ To uninstall Falcon Image Analyzer simply remove the FalconImageAnalyzer resourc

```sh
{{ .KubeCmd }} delete falconimageanalyzer --all
```
```

### Sensor upgrades

Expand All @@ -127,7 +124,7 @@ To upgrade the sensor version, simply add and/or update the `version` field in t
falcon-image-analyzer 0.8.0 1.0.9
```

This is helpful information to use as a starting point for troubleshooting.
This is helpful information to use as a starting point for troubleshooting.
You can get more insight by viewing the FalconImageAnalyzer CRD in full detail by running the following command:

```sh
Expand Down Expand Up @@ -162,6 +159,3 @@ End-to-end guide(s) to install Falcon-operator together with FalconImageAnalyzer
{{- else if eq .Distro "openshift" }}
- [Deployment Guide for OpenShift](../../README.md)
{{- end }}



Loading