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
value: "http://appsec-service.crowdsec.svc.cluster.local:7422"# if using our helm chart, and running the appsec in the "crowdsec" namespace
85
+
value: "http://crowdsec-appsec-service.crowdsec.svc.cluster.local:7422"# if using our helm chart with "crowdsec" release name, and running the appsec in the "crowdsec" namespace
86
86
- name: APPSEC_FAILURE_ACTION
87
-
value: passthrough # What to do if the appsec is down, optional
87
+
value: "passthrough"# What to do if the appsec is down, optional
88
88
- name: APPSEC_CONNECT_TIMEOUT # connection timeout to the appsec, in ms, optionial
89
-
value: 100
89
+
value: "100"
90
90
- name: APPSEC_SEND_TIMEOUT # write timeout to the appsec, in ms, optional
91
-
value: 100
91
+
value: "100"
92
92
- name: APPSEC_PROCESS_TIMEOUT # max processing duration of the request, in ms, optional
93
-
value: 1000
93
+
value: "1000"
94
94
- name: ALWAYS_SEND_TO_APPSEC
95
-
value: false # always send requests to the appsec, even if there's a decision against the IP, optional
95
+
value: "false"# always send requests to the appsec, even if there's a decision against the IP, optional
If set, enable appsec mode and forward the request to this endpoint for analysis.
371
371
372
-
Use `http://appsec-service.crowdsec.svc.cluster.local:7422` if you are using our helm chart to deploy crowdsecin the `crowdsec` namespace
372
+
Use `http://crowdsec-appsec-service.crowdsec.svc.cluster.local:7422` if using our helm chart with `crowdsec` release name, and running the appsec in the `crowdsec` namespace.
0 commit comments