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.

Sign up for GitHub

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

Jump to bottom

Add known k8s api callers to vagrant values.yaml and upgrade falco chart to 1.5.0 #1003

Merged
merged 1 commit into from
Oct 14, 2020
Merged

Add known k8s api callers to vagrant values.yaml and upgrade falco chart to 1.5.0 #1003

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 1 addition & 1 deletion deploy/helm/sumologic/requirements.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ dependencies:
alias: prometheus-operator
condition: prometheus-operator.enabled,sumologic.metrics.enabled
- name: falco
version: 1.4.0
version: 1.5.0
repository: https://falcosecurity.github.io/charts
condition: falco.enabled
- name: metrics-server
Expand Down
28 changes: 28 additions & 0 deletions vagrant/values.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,3 +29,31 @@ sumologic:
telegraf-operator:
enabled: true
replicaCount: 1

falco:
enabled: true
customRules:
# Mark the following as known k8s api callers:
# * fluentd and its plugins
# * grafana sidecar
# * terraform provider started in setup job
# * telegraf operator
# * kube state metrics server
# * prometheus
# * prometheus operator
rules_user_known_k8s_api_callers.yaml: |-
- macro: user_known_contact_k8s_api_server_activities
condition: >
(proc.pcmdline = "fluentd /usr/local/bundle/bin/fluentd -c /fluentd/etc/fluent.conf -p /fluentd/plugins") or
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we use both proc names and the namespace?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We could but we'd need to template it because user can configure the destination template for our collection?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For vagrant env for now hardcoding should be fine though

(proc.cmdline = "fluentd /usr/local/bundle/bin/fluentd -c /fluentd/etc/fluent.conf -p /fluentd/plugins") or
(proc.cmdline = "ruby -Eascii-8bit:ascii-8bit /usr/local/bundle/bin/fluentd -c /fluentd/etc/fluent.conf -p /fluentd/plugins --under-supervisor") or
(proc.cmdline = "event_loop -Eascii-8bit:ascii-8bit /usr/local/bundle/bin/fluentd -c /fluentd/etc/fluent.conf -p /fluentd/plugins --under-supervisor") or
(proc.cmdline = "watch_endpoints -Eascii-8bit:ascii-8bit /usr/local/bundle/bin/fluentd -c /fluentd/etc/fluent.conf -p /fluentd/plugins --under-supervisor") or
(proc.cmdline = "watch_events -Eascii-8bit:ascii-8bit /usr/local/bundle/bin/fluentd -c /fluentd/etc/fluent.conf -p /fluentd/plugins --under-supervisor") or
(proc.cmdline = "filter_kuberne* /usr/local/bundle/bin/fluentd -c /fluentd/etc/fluent.conf -p /fluentd/plugins") or
sumo-drosiek marked this conversation as resolved.
Show resolved Hide resolved
(proc.cmdline = "python -u /app/sidecar.py") or
(proc.cmdline startswith "terraform-provi") or
(proc.cmdline startswith "manager --telegraf-default-class=sumologic-prometheus --telegraf-classes-directory=/etc/telegraf-operator --enable-default-internal-plugin --telegraf-image=docker.io/library/telegraf") or
(proc.cmdline startswith "kube-state-metr") or
(proc.cmdline startswith "prometheus") or
(proc.cmdline startswith "operator")