Falco #98
Falco #98
Conversation
| resource "kubernetes_namespace" "falco" { | ||
| metadata { | ||
| name = "falco" | ||
| } | ||
| } |
There was a problem hiding this comment.
I would suggest you annotate the namespace to help identify it better in terms of connecting to other resources, k8s relies a lot on annotations to know how to operate in different settings and environments. If we wanted to create a specific network policy for falco, the annotation would probably come in handy,
Example: https://github.com/GSA/datagov-brokerpak-eks/blob/main/terraform/modules/provision-k8s/k8s-network-policy.tf#L2-L9
| name = "falco" | ||
| chart = "falco" | ||
| repository = "https://falcosecurity.github.io/charts" | ||
| version = "1.18.3" |
There was a problem hiding this comment.
Is this the latest version? Anything we should know about this version and compatibility with k8s version or other systems-specific versioning?
|
Also update the terraform.tfvars instructions on configuring the slack_webhookurl, |
|
close this? |
For GSA/data.gov#3799
slack_webhookurlneeds to be added to local fileterraform.tfvarsto have slack notification.Custom Falco rule added for solr security but havn't figure out a way to apply it in the terraform code. remain in draft for now until coming back to fix it.