Skip to content

Commit

Permalink
Merge pull request #299 from cs-pvyas/1.1.8-helm-version-new
Browse files Browse the repository at this point in the history
1.1.8 helm version new
  • Loading branch information
redhatrises authored Jun 20, 2024
2 parents 2e2ac38 + e98d6a2 commit c42d063
Show file tree
Hide file tree
Showing 5 changed files with 28 additions and 14 deletions.
4 changes: 2 additions & 2 deletions helm-charts/falcon-image-analyzer/Chart.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -15,10 +15,10 @@ type: application
# This is the chart version. This version number should be incremented each time you make changes
# to the chart and its templates, including the app version.
# Versions are expected to follow Semantic Versioning (https://semver.org/)
version: 1.1.7
version: 1.1.8

# This is the version number of the application being deployed. This version number should be
# incremented each time you make changes to the application. Versions are not expected to
# follow Semantic Versioning. They should reflect the version the application is using.
# It is recommended to use it with quotes.
appVersion: "1.0.12"
appVersion: "1.0.13"
16 changes: 8 additions & 8 deletions helm-charts/falcon-image-analyzer/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,11 +15,10 @@ The Falcon Image Analyzer Helm chart has been tested to deploy on the following
* SUSE Rancher K3s
* Red Hat OpenShift Kubernetes

## New updates in current release (1.1.7)
- Adding a way to specify log output terminal `log/output:` . Image Support `1.0.12`
use this field to set the output terminal of logs
`1` = stdout ( some cloud providers like GCP assume any output on stderr to be critical err and display on console ) .
`2` = stderr/default ( stderr is the normal output for logs ) . Any other value will be defaulted to stderr
## New updates in current release (1.1.8)
- Adding flag to support sending scan stats/error to cloud `scanStats.enabled` . Image Support `1.0.13`
Set this flag to true to send scan error stats to cs cloud.These events can be searched in investigate>events / advanced events search .
Note that if enabled agent will send an error for image for first time only. Repeated errors for same images will not be sent to preserve network footprint

## Dependencies

Expand Down Expand Up @@ -60,6 +59,7 @@ The following tables list the Falcon sensor configurable parameters and their de
| `exclusions.namespace` optional ( available in falcon-imageanalyzer >= 1.0.8 and Helm Chart v >= 1.1.3) | Set the value as a comma separate list of namespaces to be excluded. all pods in that namespace(s) will be excluded | "" |
| `exclusions.registry` optional ( available in falcon-imageanalyzer >= 1.0.8 and Helm Chart v >= 1.1.3) | Set the value as a comma separate list of registries to be excluded. all images in that registry(s) will be excluded | "" |
| `log.output` optional ( available Helm Chart v >= 1.1.7 & falcon-imageanalyzer >= 1.0.12) | Set the value to for log output terminal. `2=stderr` and `1=stdout` | 2 ( stderr ) |
| `scanStats.enabled` optional ( available Helm Chart v >= 1.1.8 & falcon-imageanalyzer >= 1.0.13) | Set `enabled` to true for agent to send scan error and stats to cloud | false |
| `crowdstrikeConfig.clusterName` required | Cluster name | None |
| `crowdstrikeConfig.enableDebug` optional | Set to `true` for debug level log verbosity. | false |
| `crowdstrikeConfig.clientID` required | CrowdStrike Falcon OAuth API Client ID | None |
Expand Down Expand Up @@ -347,14 +347,14 @@ Registries can be excluded by adding the full registry name in the below section
Namespaces can be excluded in two ways:

1. **Helm Chart Values** : If you are installing IAR on a cluster that is running a lot of pods and would like to exclude them from IAR scanning then use the `exclusions.namespace` param in your `config_values.yaml` for IAR and set the value to be a comma separate list of namespaces that needs to be excluded
e.g.
e.g.
```
exclusions:
namespace: "ns1,ns2"
```

2. **Annotations**: Once the IAR has been installed, any new namespace can be excluded by adding the below annotation to the target namespace spec
`sensor.crowdstrike.com/imageanalyzer: "disabled"`
`sensor.crowdstrike.com/imageanalyzer: "disabled"`

e.g.
```
Expand Down Expand Up @@ -431,4 +431,4 @@ helm show values crowdstrike/falcon-image-analyzer
To uninstall, run the following command:
```
helm uninstall imageanalyzer -n falcon-image-analyzer && kubectl delete namespace falcon-image-analyzer
```
```
7 changes: 7 additions & 0 deletions helm-charts/falcon-image-analyzer/templates/_helpers.tpl
Original file line number Diff line number Diff line change
Expand Up @@ -42,6 +42,13 @@ agentRunmode definition
{{- end }}


{{/*
isKubernetes definition
*/}}
{{- define "falcon-image-analyzer.isKubernetes" -}}
{{- printf "true" }}
{{- end }}

{{/*
tmp-volume volume size definition
*/}}
Expand Down
4 changes: 3 additions & 1 deletion helm-charts/falcon-image-analyzer/templates/configmap.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,9 @@ metadata:
labels:
{{- include "falcon-image-analyzer.labels" . | nindent 4 }}
data:
IS_KUBERNETES: {{ .Values.isKubernetes | quote }}
IS_KUBERNETES: {{ include "falcon-image-analyzer.isKubernetes" . | quote }}
SEND_SCAN_STATS: {{ .Values.scanStats.enabled | quote }}
AGENT_HELM_VERSION: {{ .Chart.Version | quote }}
LOG_OUTPUT: {{ .Values.log.output | quote }}
AGENT_CID: {{ .Values.crowdstrikeConfig.cid | quote }}
AGENT_CLUSTER_NAME: {{ .Values.crowdstrikeConfig.clusterName | quote }}
Expand Down
11 changes: 8 additions & 3 deletions helm-charts/falcon-image-analyzer/values.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -2,9 +2,6 @@
# This is a YAML-formatted file.
# Declare variables to be passed into your templates.

# Do not override anywhere in values - Always true when run in k8s
isKubernetes: true

daemonset:
enabled: false

Expand Down Expand Up @@ -143,6 +140,14 @@ volumes:
log:
output: 2


# Set this flag to true to send scan error stats to cs cloud.
# These events can be searched in investigate>events / advanced events search
# note that if true, agent will send an error for image for first time only.
# Repeated errors for same images will not be sent to preserve network footprint
scanStats:
enabled: false

crowdstrikeConfig:
clusterName: ""
enableDebug: "false"
Expand Down

0 comments on commit c42d063

Please sign in to comment.